HOWTO: How to use nvflash to get the BCT from your Gtab - G Tablet General

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

Related

Magic Number Mismatch

Hey guys,
I was tired and on accidentally put the most recent clockwork recovery onto my G-tab when i was reinstalling the Vegantab 5.1 Rom.
After the install it rebooted into a black screen that said "Magic Number Mismatch:" in red.
I have used NVflash before and I went ahead and reinstalled clockwork v08 Bekit.
I got this message:
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflash --bl boot
loader.bin --download 9 clockwork.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171440424380b1d7
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
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
sending file: clockwork.img
| 3862528/3862528 bytes sent
clockwork.img sent successfully
Even after this the device still gives me the "Magic Number Mismatch:" message.
I read the other threads and none of those solutions worked, nor did most of them apply to me since I can't even boot into clockwork.
any help would be appreciated
You will need to flash the "recovery partition" using nvflash.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Thanks man! That did the trick.
From there i was able to reflash the older version of clockwork and my ROM.

[HELP] G2x boot to recovery failed.

I rooted the phone and installed the recovery image using nvflash,
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: ----- removed --------
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: recovery-star-test2.img
\ 4306944/4306944 bytes sent
recovery-star-test2.img sent successfully
After that I try to boot into recovery and I get /!\ and andriod logo, I dont see the CWR menu. Can some one please help. I repeated the nvflash process a few times and I get the same result. But I am able to boot into the stock Andriod (2.2) just fine.
I have also tried the ext4 version
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: --- removed ---
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: p999-4.0.0.2-external-recovery.img
| 3565568/3565568 bytes sent
p999-4.0.0.2-external-recovery.img sent successfully
and when I go to ROM Manager and select boot to recovery, I see the new splash screen, and then /!\ with green logo. No CWR menus.
With phone off, hold volume down and power. Keep holding until you get past the initial LG boot screen then let go. It should drop you into CWM.
Btw, forget about Rom Manager.

[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...

[Q] G2X won't turn on!

I have a problem with my g2x that can't be turned up, it stuck when I flash the NVflash "G2X_V21E_00_NVFlash". I did get through once then it's error again. Then I followed the same instruction but I have no idea why I can't pass through. I hope people can help me with this and tell me how or experience that they had it and solved it. Anyway, thank before the hand, I'm really appreciated your help.
Here the message I got when I tried to flash the NVFlash with G2X_V21E_00_NVFlash.
"C:\Users\Free\Desktop\Download\Software\Android\LG G2X\G2X_V21E_00_NVFlash>.\nvf
lash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --set
bct --odmdata 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl
fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20c143e0b5d7
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"
Did you try doing it with the battery out and holding the volume buttons down until it gets past the bootloader?
Sent from my LG-P999
I did but it never go pass through it. It just stop at the " waiting for bootloader to initialize ". I tired dozen of time but it never works.
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
===== STEP 1 - Flashing ClockworkMod Recovery 5.0.2.0:
download the 5.0.2.0 clockworkmod recovery image
place recovery-clockwork-5.0.2.0-p999.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
navigate to folder with nvflash.exe in it at command prompt, for me cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". You can let go of the volume buttons at this point. Once the files are sent and the program is finished running in the command window, you CAN just pull the USB cord or be safe and just wait a few extra minutes, however it will still say "upgrading.
Click to expand...
Click to collapse
Hope that helps somehow....
kuhla said:
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
Hope that helps somehow....
Click to expand...
Click to collapse
I have no idea it's still not working any thank for your replying.
Maybe try re installing the LG and APX drivers?
Sent from my LG-P999

Help: GEO ecopc Tablet is bricked

I am a Venezuelan citizen and in my country buy a (GEO-ecopc) tablet.
The tablet data are:
Processor: nVidia Tegra-2 250 1 GHz (T20)
DRAM: 1 Gb DDR2 (H5PS2G83AFR-S6C (DDR2 256Mx8))
Hard Disk: 16 Gb emmc-nand (Kingston KE4BT4B6A)
Screen: 10.1" Capacitive Multi Touch (1280x800)
Android: v2.2 (Kernel: 2.6.32.9)
Name: Ventana
Model: N10G
MCU: 1.70.2
Please I need help.
When I use the nVFlash get this error:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x170061844300e257
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: GEO_ecopc.bct
- 4080/4080 bytes sent
GEO_ecopc.bct sent successfully
odm data: 0x360d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
\ 906888/906888 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
failed executing command 17 NvError 0x120002
command failure: create failed (bad data)
bootloader status: BCT is full; no more bootloaders can be added (code: 16) message: nverror:0x4 (0x4) flags: 0
I love my tablet but, I can not unbrick. Please helpme...

Categories

Resources