Extract Bootloader and Ubootenv ?

[niabi]

following the info on this post:

http://forum.androidgadget.co.uk/showthread.php?tid=174&pid=964#pid964

I could get my stick back and runing, but Bluetooth and Wifi don't work :/ I guess I will need a proper uboot from Gamestick, but no luck yet on that

luck was on my side, as as soon as I got it back up, one of the pads on the RS232 lifted :/ so I won't be doing that again, even if I wanted to hahahaha

[niabi]

I used an SD card and selected the firmware in the recovery menu (with a usb keyboard)

I basically did all that you just listed but for some reason I get the android about halfway thru it aborts the installation but does not give an error, it gives the magic 7f45 so IDK. I am using a usb flash drive, should I be using a sd card instead?

[neo4uo]

I have a build enviroment setup on a linux box i need to compile us a custom cwm recovery for this damn gamestick its a shame no one will answer you or me back for the image files you need. I sent them an email and started a thread in their developer forum asking for the source of their rom lol. I will try flashing it with that software with an sd card later. I would like to pick thru that rom and disable to auto updates just to make it harder to brick. There has to be a way in linux at least to dump the files you need. Do you have an extra gamestick?

[niabi]

Well I got the stick back and runing, but now the wifi does not find any networks, and the bluetooh doesn't pair with anything either :/

do you know if the ubootenv has anything to do with this?

Thanks a lot for all of your help!

If you have a working device you can dump the recovery...
Run

cat [B]/proc/mtd[/B]
cat [B]/proc/partitions[/B]
ls -al[B] /dev/block/mtd/by-name[/B]

in terminal and see what you get...
To dump you have to use this

dd[B] if=/dev/block/mtdblock[I]XYZ[/I] of=/mnt/external_sd/recover.img[/B]

and an SD card...

I hope you can use this recovery dump at "special" SD card...


Maybe you also find the uboot with this way, but I don't think so at the MX...???

[no_spam_for_me]

Well I got the stick back and runing, but now the wifi does not find any networks, and the bluetooh doesn't pair with anything either :/

do you know if the ubootenv has anything to do with this?

Thanks a lot for all of your help!

No, sorry, no idea... I never had a deeper look at it...
Maybe Finless can give an answer...

[niabi]

Thanks, hopefully Finless reads this and can give me some insight

No, sorry, no idea... I never had a deeper look at it...
Maybe Finless can give an answer...

[Finless]

Wifi and BT consists of a couple things.

1) The correct drivers must be in /system/modules if it is not in the kernel
2) Wifi supplicant file must be the correct one
3) In boot.img there is a init.rc and possibly init.amlboard.rc in there are the lines or deffinitions for setting up wifi/bt

Now I do not know this stick but the kernel that is in boot.img maybe the problem too. Depends if the wifi drivers were compiled into the kernel or not.

Bob

[niabi]

Thanks for the reply. Well it seems I am screwed then :/ since I flashed the original FW and the problem still persists, it never finds any WiFi connection and Bluetooth never pairs :/ they both turn on and off with no problems.

seems weird, because the only thing I did was flash another uboot(granted I had to do a lot to recover it after), before that, Wifi was working correctly

Wifi and BT consists of a couple things.

1) The correct drivers must be in /system/modules if it is not in the kernel
2) Wifi supplicant file must be the correct one
3) In boot.img there is a init.rc and possibly init.amlboard.rc in there are the lines or deffinitions for setting up wifi/bt

Now I do not know this stick but the kernel that is in boot.img maybe the problem too. Depends if the wifi drivers were compiled into the kernel or not.

Bob

[niabi]

Bob; you have way more experience with this than me so this might sound stupid, but bear with me :P

I have access to another gamestick, I checked my current MTD and it is exactly the same MTD as the other one (working), if I copy all those MTD from one to the other using dd, will this work? have yo done something similar to this before?

root@android:/ # cat /proc/mtd
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: 00008000 00001000 "ubootenv"
root@android:/ #

both have the exact same MTD, but one has a different bootloader and recovery

does this sound stupid/crazy/ or is it doable/genius? :P

Wifi and BT consists of a couple things.

1) The correct drivers must be in /system/modules if it is not in the kernel
2) Wifi supplicant file must be the correct one
3) In boot.img there is a init.rc and possibly init.amlboard.rc in there are the lines or deffinitions for setting up wifi/bt

Now I do not know this stick but the kernel that is in boot.img maybe the problem too. Depends if the wifi drivers were compiled into the kernel or not.

Bob

[no_spam_for_me]

Dump using dd will work (no question, no problem), BUT you can't use dd to write to the MTD's because the system is running... so you must have to use a SD to flash the dumps (is only a kind of dd (write_raw_image("xyz,xyz");) ...
BTW: nice to see you can get the "ubootenv", but I don't know the "NFTL_Part" and where to find the recovery (and maybe also the "uboot")???

[niabi]

ahh, I see, I will check how to do this then.

I am also wondering how to get the uboot, I saw a script that finless wrote to get it, but I haven't test to see if it will work on my stick.

I contacted the manufacturer and they told me they will get back to me on Monday, so I am going to wait and see if they send me a proper uboot on Monday


btw: what exactly is NFTL?

Dump using dd will work (no question, no problem), BUT you can't use dd to write to the MTD's because the system is running... so you must have to use a SD to flash the dumps (is only a kind of dd (write_raw_image("xyz,xyz");) ...
BTW: nice to see you can get the "ubootenv", but I don't know the "NFTL_Part" and where to find the recovery (and maybe also the "uboot")???

[no_spam_for_me]

... btw: what exactly is NFTL?

I mean I also have no idea what

mtd6: 9ec00000 00400000 "NFTL_Part"

is

[trebor]

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

[neo4uo]

Re: Extract Bootloader and Ubootenv ?

Duplicate sorry

[neo4uo]

Re: Extract Bootloader and Ubootenv ?

I mean I also have no idea what

mtd6: 9ec00000 00400000 "NFTL_Part"

is

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.