Related
Hello,
After a failed attempt to install VEGAn-TAB GingerEdition on my Malata Zpad, I followed an advice on a thread to reflash the tablet with nvflash.
I made a big mistake at that time and flashed a Gtablet configuration.
This stuck me in APX mode, without anything on screen (for the first flash operation, I get one line telling I was in this mode, but after that I never saw this line again).
I can put the tablet is in APX mode (lsusb gives: Bus 001 Device 110: ID 0955:7820 NVidia Corp.). I can read slowly some elements using nvflash and --rawdeviceread (552 sectors at a time only) from my Linux computer. If I try to read too many byte, I get "data receive failure NvError 0x120000". I also have to switch the tablet on and off one or two times between each read attempt. Patiently reading sectors and assembling them on the computer with commands like cat, dd, od -x and the like, I get the impression that most of the gtablet configuration has been written (including PT but not BCT, or it was overwritten later), but there were some errors (binary files differ after some hundreds of thousands bytes).
However, most of the commands I send with nvflash fail as never completing or sending only the bootloader and not the other files, or sending the bct and stopping ... I also tried to use --rawdevicewrite but was able to overwrite neither BCT nor PT partitions. In fact, after the rawdevicewrite attempt, now rawdeviceread returns lots of alternating series of ffffffff and 000000. It also seem that if I read at the sectors corresponding to partitions BCT and PT, I get the same patterns, but if I do a --getBCP I get "normal" bytes (first line of od -x shows: 0000000 b380 6840 476e 15b9 23f1 5b07 18d2 8a58 ...). I think the fffff and 0000 are really there and correspond to write errors, but cannot be sure.
I also tried using directly --download to put the BCT partition but got another error: "failed executing command 14 NvError 0x120002 / command failure: partition download failed (bad command)". If I try the same command on partition 4 (EBT, with the bootloader) the bytes are sent but the error becomes "failed executing command 25 NvError 0x120000 / command failure: sync failed".
I don't understand what happens and how I can flash a working configuration again.
I have made some very small progress.
I now can see the following line on the tablet when nvflash has sent the appropriate bootloader (the one I used before was corrupted):
Code:
Entering NvFlash recovery mode / Nv3p server
This bootloader however does not support the --getbct command, it replies:
Code:
Failed sending command 2 NvError 1179650command failure: getbct failed (bad data)
bootloader status: operation not implemented (code: 3) message: nverror:0x1 (0x1) flags: 0
So I have to switch to another bootloader (fastboot.bin, retrieved from an ac100 forum) to get the BCT.
I can use --download without errors, so I tried to download recovery.img from cwm 0.8 into partition 9 as a recovery boot, hoping to repartition my tablet from CWM. No error on download, but nothing happens if I try to reboot in recovery mode (I guess this boot image is used when powering up the tablet while Vol+ is pressed. Rereading the first 94MB of the flash memory, I searched for the header bytes of recovery.img but did not found them (the longest match I found were only 8 bytes long), so I think --download did not download anything.
So I am still stuck with an unusable tablet.
Could someone give me some advice ?
Another strange thing I get is when I try to reset the BCT after having sent the bootloder to the tablet in a previous command. I use:
Code:
sudo ../nvflash --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct --setbct --configfile android_fastboot_full.cfg --odmdata 0xbb0c0011 --create --go
Then I get messages about creating BCT, PT and EBT partitions, followed by a message about BCT being full and unable to add a new boot loader. I'm not sure anything has really been written on the tablet.
Does anyone know how to empty the BCT before attempting to relaunch the previous flash operation ?
It seems I am the only one in this thread and nobody wants to help me.
Current status is that I am still stuck. I can write at some places using nvflash --rawdevicewrite, but not everywhere. Even in the middle of the memory, I had write operations where the first 64kbytes of the write were replaced by ffff, then the following 64k bytes were written properly, and the rest was again replaced by ffff. Trying to write blocks smaller than 64k did not help, it is as if the target sector was corrupted (depite at the beginning it did not contain ffff, but a part of the initial flash).
Then I tried reformating the partitions. Some succeeded, some didn't.
Then I read in nvflash internal help (using nvflash --cmdhelp --format_all) the --format_all would reformat also the BCT an PT partitions, using the provided configfile. It was exactly what I needed! I tried it:
Code:
sudo ../nvflash --configfile android_fastboot_full.cfg --format_all --bl bootloader.bin --go
and it failed with the error messages
Code:
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting all partitions please wait.. bootloader status: partition table is required for this command (code: 8) message: nverror:0x4 (0x4) flags: 0
FAILED!
formatting failed
format-all failed
NvError 0x0
It looks as if the --format_all which should create the partition table needs the partition table, and cannot only use the provided configuration file. This seems rather strange to me, so I may miss something obvious.
Please, help me.
unbricked!
I finally got the device unbricked.
Since I always got messages about full BCT, I finally decided to try to reset it with nvflash --rawdeviewrite. The BCT is at the very beginning of the memory (from block 0 included to block 1536 excluded). It starts with 16 bytes of magic numbers: b380 6840 476e 15b9 23f1 5b07 18d2 8a58, followed by 16 bytes set to 0, followed by the 4080 bytes you find in the various bct files lying around these threads. This pattern seems to be repeated several times, each 64k, so I thought it could hold several configuration (1536 blocks of 2048 bytes each can hold a bunch of such 64k sections).
So I forged a first 64k block from the magick numbers, the zeros, my Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct file and filled the rest with ffff. I wrote this to the tablet and ... it did only write a long series of ffff. So I have finally completely overwritten my BCT with garbage
After that, almost all nvflash operations failed, even simply downloading the bootloader. Error messages were either bad data, or missing partition table, or BCT related.
I tried several bootloaders, fastboot.bin from an ac100 thread the bootloader from the dropbox link in Roebeet's thread here: http://forum.xda-developers.com/showpost.php?p=9603803&postcount=1, and the one from the Malata image in nvflash_t2_mp_wifi_1202.rar. This last one succeeded. Since I had already used this commands a very large number of times and it always failed before, I think this time it succeeded because I had erased the BCT with my bunch of ffff.
Here are the final command I set and its output:
Code:
sudo ../nvflash --bl bootloader.bin --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct --setbct --configfile an
droid_fastboot_full.cfg --odmdata 0xbb0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040432025d7
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
sending file: Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct
- 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct sent successfully
odm data: 0xbb0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: NVC
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: KLO
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 NVC please wait.. done!
Formatting partition 6 MBT please wait.. done!
Formatting partition 7 BLO please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 KLO please wait.. done!
Formatting partition 10 OGO please wait.. done!
Formatting partition 11 SOS please wait.. done!
Formatting partition 12 LNX please wait.. done!
Formatting partition 13 APP please wait.. done!
Formatting partition 14 CAC please wait.. done!
done!
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: boot.bmp
- 1843254/1843254 bytes sent
boot.bmp sent successfully
sending file: boot.bmp
- 1843254/1843254 bytes sent
boot.bmp sent successfully
sending file: logodata.img
| 418176/418176 bytes sent
logodata.img sent successfully
sending file: recovery.img
/ 3362816/3362816 bytes sent
recovery.img sent successfully
sending file: boot.img
| 2758656/2758656 bytes sent
boot.img sent successfully
sending file: system.img
- 152334336/152334336 bytes sent
system.img sent successfully
After that, the tablet rebooted automatically, with the Malata logo.
Last few problems were that it was in chinese and with the touch screen not responding. The touch screen problem was due to not understanding the slider at the bottom of the initialization screen was an unlocking slider and should be moved to activate the touch screen. Then I had to search a little to reset the tablet in english.
The last few days have been tiresome, and I would have appreciated getting some help here ...
There were probably a few who were following this thread (myself included), but couldn't help, because we have very little info on the BCT.
Plus you have a ztab, rather than a gtablet.
Congratulations on you success and persistence, and thanks for posting this info.
I do have one question: how'd you figure out what to use for the odmdata? That's another piece of the puzzle w little info....
Jim
Misty soul said:
I finally got the device unbricked.
Since I always got messages about full BCT, I finally decided to try to reset it with nvflash --rawdeviewrite. The BCT is at the very beginning of the memory (from block 0 included to block 1536 excluded). It starts with 16 bytes of magic numbers: b380 6840 476e 15b9 23f1 5b07 18d2 8a58, followed by 16 bytes set to 0, followed by the 4080 bytes you find in the various bct files lying around these threads. This pattern seems to be repeated several times, each 64k, so I thought it could hold several configuration (1536 blocks of 2048 bytes each can hold a bunch of such 64k sections).
So I forged a first 64k block from the magick numbers, the zeros, my Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct file and filled the rest with ffff. I wrote this to the tablet and ... it did only write a long series of ffff. So I have finally completely overwritten my BCT with garbage
After that, almost all nvflash operations failed, even simply downloading the bootloader. Error messages were either bad data, or missing partition table, or BCT related.
I tried several bootloaders, fastboot.bin from an ac100 thread the bootloader from the dropbox link in Roebeet's thread here: http://forum.xda-developers.com/showpost.php?p=9603803&postcount=1, and the one from the Malata image in nvflash_t2_mp_wifi_1202.rar. This last one succeeded. Since I had already used this commands a very large number of times and it always failed before, I think this time it succeeded because I had erased the BCT with my bunch of ffff.
Here are the final command I set and its output:
Code:
sudo ../nvflash --bl bootloader.bin --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct --setbct --configfile an
droid_fastboot_full.cfg --odmdata 0xbb0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040432025d7
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
sending file: Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct
- 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct sent successfully
odm data: 0xbb0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: NVC
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: KLO
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 NVC please wait.. done!
Formatting partition 6 MBT please wait.. done!
Formatting partition 7 BLO please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 KLO please wait.. done!
Formatting partition 10 OGO please wait.. done!
Formatting partition 11 SOS please wait.. done!
Formatting partition 12 LNX please wait.. done!
Formatting partition 13 APP please wait.. done!
Formatting partition 14 CAC please wait.. done!
done!
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: boot.bmp
- 1843254/1843254 bytes sent
boot.bmp sent successfully
sending file: boot.bmp
- 1843254/1843254 bytes sent
boot.bmp sent successfully
sending file: logodata.img
| 418176/418176 bytes sent
logodata.img sent successfully
sending file: recovery.img
/ 3362816/3362816 bytes sent
recovery.img sent successfully
sending file: boot.img
| 2758656/2758656 bytes sent
boot.img sent successfully
sending file: system.img
- 152334336/152334336 bytes sent
system.img sent successfully
After that, the tablet rebooted automatically, with the Malata logo.
Last few problems were that it was in chinese and with the touch screen not responding. The touch screen problem was due to not understanding the slider at the bottom of the initialization screen was an unlocking slider and should be moved to activate the touch screen. Then I had to search a little to reset the tablet in english.
The last few days have been tiresome, and I would have appreciated getting some help here ...
Click to expand...
Click to collapse
Hi, how did you manage to restore "nvflash_t2_mp_wifi_1202.rar"...I restored my malata smb-a1011 with the nvflash tutorial posted here: http://forum.xda-developers.com/showthread.php?t=861950 but I'm having major problems and I can't use my hardware keys (i.e. Home, Back, Menu)
any help would be appreciated. Thank you!
jimcpl said:
I do have one question: how'd you figure out what to use for the odmdata?
Click to expand...
Click to collapse
I found a link to a Malata image named nvflash_t2_mp_wifi_1202.rar. the file itself can be found using a web search engine, it seems to be available at several places. In this file, the download.bat script reads:
Code:
"nvflash.exe" --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct --setbct --bl bootloader.bin --configfile android_fastboot_full.cfg --odmdata 0xbb0c0011 --create --go
I also read in this post about using 0xba0c0011 and somewhere else about 0xbc0c0011. However if now I search for this I find a reference to an Adam, not a Zpad.
jimcpl said:
I do have one question: how'd you figure out what to use for the odmdata? That's another piece of the puzzle w little info....
Jim
Click to expand...
Click to collapse
Hi Jim,
Following an idea from one of your posts on another thread, I looked at the binary structure of the BCT as it is retrieved using nvflash --read 2 02-BCT.img.
The partition is composed of 24 exact copies of the same 128 kibibytes block. In this block, bytes 4068, 4069, 4070 and 4071 (counting from 0) are 0x11, 0x00, 0x0c, 0xbb, which appear to be the omddata I set, in reversed order.
So it may be easy to recover the good omddata from any working tablet by dumping its BCT partition and looking at these bytes. It would probably be good to gather this information for all tablets in some reference thread.
Hi All,
I'm trying to backup ma gtab tablet from linux using the following command:
Code:
./nvflash --bl bootloader.bin --getbct --bct backup.bct --go
but it gives me the following error
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411c0409fb517
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: backup.bct
backup.bct received successfully
file not found: bootloader.bin
command failure: bootloader download failed
If I try anything else after this tablet get ejected.
Any help would be appreciated
Thank You
LnZ
As the error message clearly says:
Code:
file not found: bootloader.bin
Either copy the bootloader.bin into the directory where you have nvflash, or, change the ``--bl ...'' parameter to locate your bootloader.bin:
Code:
./nvflash --bl [I]/some/path/[/I]bootloader.bin --getbct --bct backup.bct
Hi rajeevp,
I misunderstood the error thinking it didn't find the file on the tablet, that wa since trying the same command on a win machine worked perfectly.
I didn't think it was a path related error.
Thank You
LnZ
Hi, I've googled and checked everywhere but I dont believe i found a post where people re-installed everything with nvflash.
My Samsung galaxy tab only connects APX mode. I think i damaged the bootloader partition(?) with odin when i did not uncheck the 're-partition' box. Since then, the tab is stuck in APX mode only. I've tried draining the power, I've even taken it apart to unplug the battery. I've left it without power, powerbutton taped down and usb stick stuck to the usb adapter to make sure that the power was all drained for at least one week but it still did not work after recharging.
Can anyone help me out by telling me how to use nvflash to reprogram the bootloader partition and re-create the bootloader so that I can use odin or even fastboot to install the new startup and rom. I guess i also need all the files necessary. I've downloaded many bootloader.bin, flash.cfg, flash.bct and they do not seem to work, giving me several errors. I've tried commands like :
nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go.
however, i do not believe i have the correct files and therefore it does not work, ending with errors.
Prior to using odin, the tablet worked just fine. no issues whatsoever except occasional hangup.
Please let me know if there is any place, person or forum which I can contact in order to download the correct files to use nvflash to reinstall just the bootloader partition or everything on the samsung galaxy tab 10.1 and if possible, the command string i should use in nvflash. I've been trying for about a month to get this to work and I believe i have a command string which will work but I do not have the correct files. I'm about to sell this unit on ebay just so I stop trying and wasting my time on it. Oh, or if you know someone who I can pay to reinstall everything through nvflash, that would work too. Thank you for your time.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
can anyone help?
I'm new to the scene, Have you tried checking via cmd if your Tablet is Locked/Unlocked? Only then can you determine if you can proceed to install CWM to save it.
When you said errors, I assume this is 0x4?
Hi, thank you for responding. I have the i/o edition and i believe those are all unlocked. I did manage to get it to work on another i/o tab but it was before i screwed up with odin. What i usually get is similar to this:
"
C:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c11c244202417
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073844220"
If I do
"nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go"
I get :
"
C:\nvflash old>nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --config
file flash.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c11c244202417
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
failed executing command 4 NvError 0x120002
setbct failed NvError 0x0
command failure: bootloader download failed (bad data)
"
The device would then shut off (i hear the sound of it disconnecting from the computer).The problem i'm having is that I'm not sure if the flash.bct, bootloader.bin, and the flash.cfg are correct and I'm not sure if i'm entering the string correctly.
Please let me know what you think or if you can direct me to someone or some website which can help. thank you so much for responding.
Well I'm stuck on the same boat as you, except mine is on the 0x4 and hasn't gotten past the unlocked screen, according to a guide of this device, you need to push CWM to save it, that way you can clear/wipe/flash a stock ROM to save it.
Have you tried pushing the CWM?
Also when it says bad data, Seem's your download is incomplete :|
Hi, i'm sorry I haven't responded. I've been trying to power it down again.
I tried to push CWM but this is what I get
C:\nvflash>nvflash --resume --download 8 recovery-cwm_4.0.0.4-sam-tab-10.1.img
Nvflash started
[resume mode]
file not found: recovery-cwm_4.0.0.4-sam-tab-10.1.img
failed executing command 2147483647 NvError 0x4
command failure: partition download failed
I tried downloading the file many times so I think it the file should be ok. I guess my tab is screwed up. I wish I knew how to reflash everything with nvflash. If you find out how to reflash everything especially the bootloader, please let me know
Misledz said:
Well I'm stuck on the same boat as you, except mine is on the 0x4 and hasn't gotten past the unlocked screen, according to a guide of this device, you need to push CWM to save it, that way you can clear/wipe/flash a stock ROM to save it.
Have you tried pushing the CWM?
Also when it says bad data, Seem's your download is incomplete :|
Click to expand...
Click to collapse
Hi Inky,
I apologise for the super late reply but try my fix that I posted earlier today.
http://forum.xda-developers.com/showthread.php?t=1478361
After what felt like a whole week with 2 dead tablet's they are both finally alive!
Thanks. I'll give it a try and let you know if anything works.
Misledz said:
Hi Inky,
I apologise for the super late reply but try my fix that I posted earlier today.
http://forum.xda-developers.com/showthread.php?t=1478361
After what felt like a whole week with 2 dead tablet's they are both finally alive!
Click to expand...
Click to collapse
I'm still waiting for my galaxy tab to totally discharge. I've waited a week with the power button plugged in but the moment I plug the tab to the computer, the apx device is detected and so I guess it wasnt as discharged as I thought. I'll keep you posted
Inkydink said:
I'm still waiting for my galaxy tab to totally discharge. I've waited a week with the power button plugged in but the moment I plug the tab to the computer, the apx device is detected and so I guess it wasnt as discharged as I thought. I'll keep you posted
Click to expand...
Click to collapse
Yeah scumbag tablet dies in a day but takes a week to drain, taping the power button to be held down should help out, unplugged. makes it less harmful to that electricity bill you'd save up on
Ps- when you drain it try not to charge it more than 2% makes it easier to resume where you may need to redo the draining process incase you mess up
Sent from my GT-P7500 using Tapatalk
Please help!
http://forum.xda-developers.com/showthread.php?t=1831624
this is my original thread please check it out and post there if you can help me with anything in anyway, i've exhausted every possible option i can find on the web..
Thank you
Spamming the forums isn't a good idea.
Any luck finding a fix? My device is now officially stuck in nvflash and I can not get bootloader.bin to download.
Code:
C:\nvflash>nvflash --bct part2.bct --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0288414343ff52d7
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
C:\nvflash>
you check with these files. download through google.
Recovery_P75xx_110710_RemoveUsbDriver.zip (2.87 MB)
Boot-recovery_driver.zip (21.68 MB)
0418_nvflash_user_build.zip (25.59 MB
You'll let me know if you can fix it, bye
So, I didn't flash this originally, and it still boots into CM7 just fine. ROM Manager is installed, it says CWM is successfully flashed and all, but any attempt to boot into recovery will just sit at "Recovery key detected. Booting recovery kernel image."
Obviously the current ROM itself is actually working fine, so what would you suggest be my next step?
Trying to put Flashback 10.3 on it.
Current Recovery: 2.5.1.8
Current ROM: CyanogenMod-7.0.3-Harmony
1. Never use ROM Manager on the gTab.
2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb.
3. To get CWM back, you'll have to use nvflash. Use bekit's original CWM 2.5.1.1-bekit-0.8 or CWM-4.0.1.5 images (ie. not the flashable zip files). See the OP in this thread for the nvflash cmd line to use.
Thanks for the advice. I'm just now coming to terms with this company not having a Micro-USB cable... >.<
Okay, so my screen is blank when in APX mode, it seems. I'm running NVFlash though, and I just have:
Nvflash started
_
It's been that way over an hour now. Tablet doesn't seem to be doing anything, neither does Command Prompt... just a blinking underscore.
Canceled it... retried it... worked quickly (bootloader and recovery "sent succesfully", not sure why it hung up last time. Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before.
Are you sure I have the 1.1 bootloader? Without stock, how can I tell?
ocdtrekkie said:
Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before.
Click to expand...
Click to collapse
What's the nvflash command you typed in and which recovery image did you flash?
Are you sure I have the 1.1 bootloader? Without stock, how can I tell?
Click to expand...
Click to collapse
Like this.
nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img
^- that one.
Not sure if I have a way to get a terminal emulator on this thing. And I don't have ADB here. Lemme see what I can manage.
That command line is correct. Put the tablet back into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The ``--go'' flag will cause bootloader to try to boot into the ROM; otherwise it will just wait for further commands and you'll have to power off the tablet.
If you lose the initial splash screen (the VS birds), then run the same command with a `6' instead of `7'.
Partitions formatted successfully, Go didn't seem to tell it to do anything, still had to turn it off. Still have birds, still won't boot into recovery.
Command prompt paste:
c:\Users\jweisz\Desktop\nvflash>nvflash --bl bootloader.bin --download 9 recover
y-clockwork-4.0.1.5-smb_a1002_bl1.1.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040411fa297
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: recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img
\ 3524608/3524608 bytes sent
recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img sent successfully
c:\Users\jweisz\Desktop\nvflash>.\nvflash --bl bootloader.bin --format_partition
7 --format_partition 12 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040411fa297
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
Formatting partition 7 please wait.. done!
Formatting partition 12 please wait.. done!
Questions:
1. Did the initial splash screen vanish?
2. Can you boot into the ROM?
3. What's the output of the ``dmesg | fgrep ...'' command? CM-7.0.3 should have everything you need to type that command in a Terminal Emulator window and find out the bootloader version.
CM7 has a terminal? Probably shoulda checked for that! LOL!
Yeah, it's gotta be that I have 1.2
<7>[ 5.794813] Shmoo: s_CpuShmoo.ShmooVmaxIndex = 8
Alright, now I have recovery. See, you got me lost here:
rajeevvp said:
2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb.
Click to expand...
Click to collapse
So... Flashback it is then, I guess.
Did you flash a customized CM-7.0.3 for the 1.2 bootloader because the standard one from cyanogenmod.com is 1.1 only?
Anyway, nvflash the 1.2 version of CWM-4.0.1.5.
I didn't flash the CM7 that was on here. Couldn't tell you.
Flashback works well on here. Thanks for all your help. Most of the time if I get a question reply from someone, they give one answer, then never come back to follow up. You're awesome.
ocdtrekkie said:
I didn't flash the CM7 that was on here. Couldn't tell you.
Click to expand...
Click to collapse
Then yours is a one-off. There are 1.2 versions of both CM-7.1.x and CM-7.2.x on the board here, but, I never encountered CM-7.0.3 on a 1.2 bootloader till today. Looks like somebody upgraded to the 1.2 bootloader and then flashed a 1.2 pershoot kernel before handing the tab over to you.
Flashback works well on here. Thanks for all your help.
Click to expand...
Click to collapse
Good luck with your new ROM.
I am a newbie to Android. I recent updated my CMO to ClockworkMod Recovery 5.5.0.X+ in preperation to go to ICS. The cmod upgrade went ok and i booted into the recovery console the first time and everything looked ok. I booted into Android 2.2 and copied the ics rom to root. When i reboot again and did a Power and sound + it would not go into CMOD recovery, it just stayed at the 3 birds. When I did a power sound - it went into APX and my pc detected that their was a device but the tablet file system did not come up. Any ideas, thanks in advance
Put the tablet into APX mode and run this command:
Code:
C:\SOME\PATH> .[B]\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
Then look through p.txt for a partition named MSC. Find out the partition number for that partition. Most commonly it is 7. On some gTabs, it is 6; on a few others it is 8. Then run this command (the tablet should still be in APX mode) assuming here MSC is partition 7:
Code:
C:\SOME\PATH> [B].\nvflash -r --format_partition 7[/B]
Reboot the tablet.
3 birds
thanks for the reply.Tried running the .\nvflash to create the p.txt file. It just "nvflash running" and then just sits there.
ljharder2003 said:
thanks for the reply.Tried running the .\nvflash to create the p.txt file. It just "nvflash running" and then just sits there.
Click to expand...
Click to collapse
That's odd. Try on Linux--I don't want to troubleshoot obscure Windows driver problems too.
You should see messages like these:
Code:
$ [B]sudo ./nvflash --bl bootloader.bin --getpartitiontable /tmp/p.txt[/B]
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0270308341006257
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
| 928940/928940 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Succesfully updated partition table information to /tmp/p.txt
$