Database Info

HOWTO: How to use nvflash to get the BCT from your Gtab

Hi,
If anyone has tried, but had problems retrieving the BCT (boot configuration table) from their Gtab, FYI, I was able to use nvflash to get the BCT from my Gtab! When I had tried previously, I kept getting an error saying that the command didn't exist.
I think that the "trick" is that you HAVE TO do it on the same/FIRST command line where you send the boot loader to the Gtab, i.e., it looks like --getbct doesn't work when you do a --resume/-r. Here's my outputs:
Windows:
=======
E:\Ziptemp\Viewsonic-BEKIT-RESTORE\Windows>nvflash --bl bootloader.bin --getbct --bct jl-bct-win.bct --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
retrieving bct into: jl-bct-win.bct
jl-bct-win.bct received successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
E:\Ziptemp\Viewsonic-BEKIT-RESTORE\Windows>dir
.
.
01/29/2011 03:08 PM 4,080 jl-bct-win.bct
Ubuntu:
======
[email protected]:/nvflash# ./nvflash --bl bootloader.bin --getbct --bct jl-bct.bct --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
retrieving bct into: jl-bct.bct
jl-bct.bct received successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
[email protected]:/nvflash# ls -al
.
.
-rw-r--r-- 1 root root 4080 2011-01-29 11:56 jl-bct.bct
.
.
You'll notice that the .bct files in both cases are 4080 bytes, so I think it's the "real" BCT (not the partition that is labelled as "BCT" in the partition table). That (4080 bytes) is the same size as the ones in Bekit's dropbox.
For the above, I used the nvflash/nvflash.exe from Bekit's dropbox in both cases. I'm assuming it'd work the same with the nvflash from the Nvidia SDK also...
[Note: per another thread:
1) nvflash.exe --getpartitiontable using nvflash.exe from Bekit's dropbox outputs binary
2) nvflash.exe --getpartitiontable using nvflash.exe from the Nvidia SDK outputs text
1) (Linux) nvflash --getpartitiontable using nvflash.exe from Bekit's dropbox outputs text
]
The bootloader.bin was also the one from Bekit's dropbox.
FYI, how to get this working was actually "hinted at" by tcrews in a thread (search for "guidance" in this forum). I had seen it, but hadn't paid much attention, but I noticed this morning that he had the --bl on the same command line, so figured I'd try that.
Jim

[Q] stock recovery

Anybody know if the stock recovery is available? I have to return my phone for an exchange and cant with clockwork on it. after my 14 days are up can i still get an exchange due to reboots and lcd bleeding?

crazythunder said:
Anybody know if the stock recovery is available? I have to return my phone for an exchange and cant with clockwork on it. after my 14 days are up can i still get an exchange due to reboots and lcd bleeding?
Click to expand...
Click to collapse
Yes you can. You actually have one year warranty on the phone.
Sent from my LG-P999 using XDA App

moshe22 said:
Yes you can. You actually have one year warranty on the phone.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
that's from the manufacturer
Sent from my LG-P999 using XDA App

I've had to exchange devices before and Tmobile will just exchange it for you they basically act as the manufacturer from what i can tell. I even bought a Slide off ebay (it was NIB) but after a slight gravitational incident the screen stopped working, called Tmobile and they sent me a replacement no problems (of course i didn't mention the battle with gravity). So I would think you should be fine..

nustherapy said:
I've had to exchange devices before and Tmobile will just exchange it for you they basically act as the manufacturer from what i can tell. I even bought a Slide off ebay (it was NIB) but after a slight gravitational incident the screen stopped working, called Tmobile and they sent me a replacement no problems (of course i didn't mention the battle with gravity). So I would think you should be fine..
Click to expand...
Click to collapse
I've exchanged my vibrant at least six times since january, for minor issues and they never ask any real questions, also got a new battery from them
Sent from my LG-P999 using XDA App

G2X Factory Firmware
There's a factory firmware posted on this thread (http://forum.xda-developers.com/showthread.php?t=1037120) for the G2X. The zip file contains 2 BIN files. I tried extracting (via ExtractNow) and mounting (via Virtual Clone Drive) the bin files to no avail. I was hoping that there would be a recovery image lying somewhere inside those files.

http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
Flash it with nvflash just like you did CWM:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img

ctso said:
http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
Flash it with nvflash just like you did CWM:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img
Click to expand...
Click to collapse
Many thanks as always!

ctso said:
http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
Flash it with nvflash just like you did CWM:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img
Click to expand...
Click to collapse
Thanks!
Sent from my LG-P999 using XDA Premium App

i keep gettiung this....
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
c:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc _x8.
bct --bl fastboot.bin --download 5 part5.img
Nvflash started
unknown command: _x8.bct
if i take out the _x8.bct i get this...
c:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc --b
l fastboot.bin --download 5 part5.img
Nvflash started
but it just sits there. and i see nothing on the phone. ????
any tips would be greatly appreciated.

i guess i'll just flash the factory firmware. that will remove the clockwork recovery,correct?
the nvflash error bothers me though. i hate when i can't get something to work. i hate even worse asking for help

crazythunder said:
i keep gettiung this....
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
c:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.
bct --bl fastboot.bin --download 5 part5.img
Nvflash started
unknown command: _x8.bct
if i take out the _x8.bct i get this...
c:\nvflash>nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc --b
l fastboot.bin --download 5 part5.img
Nvflash started
but it just sits there. and i see nothing on the phone. ????
any tips would be greatly appreciated.
Click to expand...
Click to collapse
You can not take that out. Check that there's no space between _final_emmc and _x8.bct. Based on your post, there's a space between.

anyone have a link to download the factory firmware?

p8585 said:
anyone have a link to download the factory firmware?
Click to expand...
Click to collapse
I guess you missed reading this right?
http://forum.xda-developers.com/showpost.php?p=13119243&postcount=6

joackie27 said:
I guess you missed reading this right?
http://forum.xda-developers.com/showpost.php?p=13119243&postcount=6
Click to expand...
Click to collapse
link in that thread isn't working

joackie27 said:
You can not take that out. Check that there's no space between _final_emmc and _x8.bct. Based on your post, there's a space between.
Click to expand...
Click to collapse
i copied it out of someones post. i'm gonna search for it and ask the op to correct it. thanks for pointing that out. i got it sorted out anyways. back to stock recovery and firmware.
actually, it's page one of this thread, doh!
that's odd. in the post with this command, there is a space. that's where i copied it from. but if i quote the op, it shows no space. something to be aware of. i've done this alot and never encountered anything like that.

p8585 said:
link in that thread isn't working
Click to expand...
Click to collapse
Yeah it's down. I downloaded it early this morning at work. But I'm home now.

How Long Must I Wait
ctso said:
http://mirror.dal.tdrevolution.net/ctso/g2x/part5.img
Flash it with nvflash just like you did CWM:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 part5.img
Click to expand...
Click to collapse
Ok, so i've flashed and it was successful and i've been waiting on the "S/W Upgrade" screen for about 20 mins
Is that normal or am I missing a step?
How long do i have to wait?
Thanks

i know i can do the stock nandroid backup. then flash the stock recovery. then use soc to unroot. and my device will be like new.
i've just been looking for an easier way to flash those damn bin files lol. i got closer today.
the first step was the stock recovery part5.img which was successful.
C:\Users\crazythunder\Desktop\G2X\ROOT\nvflash files\NVFlash>nvflash --bct 1108_
Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --downloa
d 5 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884206433fa2d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: part5.img
/ 5242880/5242880 bytes sent
part5.img sent successfully
C:\Users\crazythunder\Desktop\G2X\ROOT\nvflash files\NVFlash>nvflash --bct 1108_
Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --downloa
d 5 LGP999AT-01-V10f-310-260-MAR-27-2011+0_AP.bin
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02884206433fa2d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
this is the part that's failing me. i got an error with the cp.bin file as well.
i guess it's just easier to do it with the stock nandroid backup, then unroot.

Has anyone found a solution to this?

[Q] nvflash

Last nigh I left my transformer at 25% battery power in flight mode.
This morning was not able to switch my Transformer on.
After trying all possibilities to enter recover mode without success, I decided to use NVflash and reflash prime_v1.4.
However NVflash exits with the following error. What can go wrong?
Any idea how to fix this?
Regards,
Nikola
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA xA532EEB 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags:
0

same error :s

Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Click to expand...
Click to collapse
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)

Kasimodo said:
Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)
Click to expand...
Click to collapse
This is the content of download.bat
cd %~dp0
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
I tried with different versions of Prime but the same error happens.
Is there any other way to get some more logging/debug info from the bootloader or to check if the emmc memory is not broken or locked.
Regards,
Nikola

I think there is a problem with your internal SD. Because the next command after creating partitions is to format partitions.
But have you tried to download another nvflash.exe?
Otherwise I don't see anything else

battery is too low

Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...

tnp0511 said:
Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...
Click to expand...
Click to collapse
Exactly the same behavior here.
I will try to charge it tomorrow with another charger.

Make sure to run in a cmd window so that you can see why it's exiting

Run from cmd window
AustinMartin said:
Make sure to run in a cmd window so that you can see why it's exiting
Click to expand...
Click to collapse
The run has also been done from a cmd window:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --go
It is always exiting with:
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags: 0
Also interesting to notice that when I run without --create and without --go but with --sync
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --sync
The output is
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
but I never get the prompt back.

Is your TF101 rooted?

Kasimodo said:
Is your TF101 rooted?
Click to expand...
Click to collapse
Yes, it was rooted. 1 mount ago i flushed prime1.4 using the same procedure (nvflash + prime1.4). everything worked OK until sunday morning when the TF101 would not switch on.
Regards,
Nikola

Argh. I'm afraid that there is a physical problem.
If it was mine I will try to unroot it to see. Anf after the best is to contact Asus for return.

any other idea ?
otherwise return to Asus on Saturday

im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"

uman01 said:
im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"
Click to expand...
Click to collapse
+1
what can we do?

DTrainMusicVein said:
+1
what can we do?
Click to expand...
Click to collapse
You probably have an SBKv2 tablet which you can't use NVFlash right now

baseballfanz said:
You probably have an SBKv2 tablet which you can't use NVFlash right now
Click to expand...
Click to collapse
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance

DTrainMusicVein said:
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance
Click to expand...
Click to collapse
Yes you're B50 should be SBKv1.
You do have all the needed files in the nv flash folder?

I believe so, I have downloaded the rooted and unrooted US versions of the ICS NVFlash and I am going to try the WW next? Any other tips? Its still failing on me...

[solved] Help with NVflash? Reflash failing

Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x37c708542bff297
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!

Need bricked G2x help, NVFlash not working

My phone won't turn on at all and whenever I plug my phone up to the computer by holding down both volume buttons without the battery I use NVFlash and I keep getting this
C:\Documents and Settings\Austin\Desktop\New Folder (3)\G2X_V21E_00_NVFlash>.\n
flash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --s
tbct --odmdata 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --b
fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c700843610417
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize

Anything would help

how did it get there?
You post this in the wrong section btw... expect a warning from a moderator

Sorry someone in another thread told me to post it in here.

it seems like you already have a thread going in the Q&A section. That is the right section, there is no reason to post this here in DEVELOPMENT. Many people are trying to help you already so just follow their steps and it is POSSIBLE to brick this device. Make sure you follow the steps very carefully for NVFlash, if you follow it step by step and unable to recover then your device is bricked.

khanh1289 said:
it seems like you already have a thread going in the Q&A section. That is the right section, there is no reason to post this here in DEVELOPMENT. Many people are trying to help you already so just follow their steps and it is POSSIBLE to brick this device. Make sure you follow the steps very carefully for NVFlash, if you follow it step by step and unable to recover then your device is bricked.
Click to expand...
Click to collapse
+1
Don't double thread your problem. People are trying to help you in your original thread.
The advice given there is same you'll get here, except here were gonna smack you for starting a new thread in the wrong section. Lol
:banghead:
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.