Extract Bootloader and Ubootenv ?

[niabi]

ah this makes sense,

its probably the "sdcard" portion of the Gamestick, since its also a very big partition

Found this on the net

NFTL_Part is nand partition formatted as fat32 (usually) and mounted as media partition or internal nand storage or...

This is probably the second storage because for some reason there is 2 different partitions for storage I can look them up here in a few and list them. I always thought it was weird when I went under storage in settings and saw 2 partitions without an see card or sub storage inserted. Maybe using the gamestick os one partition is used for games one for media idk haven't played a whole lot with the stock software.

[niabi]

NAND Flash Translation Layer seems to be the right one :P

NFTL	NAND Flash Translation Layer
NFTL	Notice of Federal Tax Lien
NFTL	Nursing Facility Transmittal Letter
NFTL	Notes from the Lounge (blog)
NFTL	Nano Fusion Technology Laboratory (Korea)
NFTL	National Freight Transportation Library, Inc.
NFTL	Nottinghamshire Federation of Toy Librarie

For what it is worth....

Sorry

[niabi]

Just to update this thread, thanks to neo4uo for providing the uboot dump, I now have a completely working uboot, how we did it? I made a script (based on Finless MTD dumper) to dump all of the necessary files using dd from recovery and I was able to flash it with no problems. Fully working gamestick now

[no_spam_for_me]

Ok, dd the recovery partition to one file, but how do you extract the uboot out of this one file?
Or how do you handle it?

[niabi]

Ok, so after using Finless MTD dumper I could see this:

dev:    size   erasesize  name
mtd0: 00400000 00400000 "logo"
mtd1: 00800000 00400000 "boot"
mtd2: 20000000 00400000 "system"
mtd3: 20000000 00400000 "cache"
mtd4: 20000000 00400000 "backup"
mtd5: 100000000 00400000 "userdata"
mtd6: 9ec00000 00400000 "NFTL_Part"
mtd7: 003fe000 00001000 "spi"
mtd8: 00058000 00001000 "uboot"
mtd9: 00008000 00001000 "ubootenv"
mtd10: 003a0000 00001000 "recovery"

The one I really needed was uboot, I am not sure yet what SPI is, I always thought it was the same ad uboot :/

so in the updater-script I Called a .sh file that had

dd if=/dev/mtd/mtd0 of=/system/dumpLogo.img
dd if=/dev/mtd/mtd1 of=/system/dumpBoot.img
dd if=/dev/mtd/mtd7 of=/system/dumpSPI.img
dd if=/dev/mtd/mtd8 of=/system/dumpUboot.img
dd if=/dev/mtd/mtd9 of=/system/dumpUbootEnv.img
dd if=/dev/mtd/mtd10 of=/system/dumpRecovery.img

then I had a uboot update zip for the ATV120 and I basically just replaced the uboot and ubootenv, ran the update, crossed my fingers and voila! it worked

Ok, dd the recovery partition to one file, but how do you extract the uboot out of this one file?
Or how do you handle it?

[no_spam_for_me]

OK, the first info is enough, because at post #24 there isn't any uboot listed
So does it mean the updater script with 'cat /proc/mtd' shows more partitions?

http://www.freaktab.com/showthread.php?9233-New-ROM-MTD-format-AML8726-MX-(Jynxbox-M6)&p=224458&viewfull=1#post224458

[niabi]

exactly, the MTD partitions only appear while on recovery, once android has booted, they are hidden.

OK, the first info is enough, because at post #24 there isn't any uboot listed
So does it mean the updater script with 'cat /proc/mtd' shows more partitions?
http://www.freaktab.com/showthread.p...l=1#post224458

[no_spam_for_me]

exactly, the MTD partitions only appear while on recovery, once android has booted, they are hidden.

hehehe, bad, bad, bad... thx, know I understand which problems you had have...