Hey guys,
My gTab got into a boot loop randomly (I hadn't even tried flashing) so I had a look on the forums here for a solution. I first tried booting into recovery from an SD card but had no luck, then tried booting clockworkmod but no luck and I finally tried nvflash.
I followed the great instructions from the sticky on this site and managed to re-flash the device. It copies the files across and gets to the reboot stage but the boot loop happens again! It loops a few times and then the tablet turns off and I can't turn it back on. I can reflash the device but it just goes through the same process.
I plugged the tablet into my PC and I can see the detected hardware icon come up. When I hold the power button this icon goes so it looks like the device is reading the power on/power off command but the screen doesn't turn on.
I have looked around everywhere but can't seem to find a solution....
Any help will be greatly greatly appreciated!
Thanks in advance,
Sam
So you were running stock rom? What happened when the boot loop started?
Yeah I was just running a stock ROM. I just turned it on one day and it got to the Tap n Tap screen and then the screen goes blank and then the tap n tap screen comes back up. This goes on about 5 times and then just stops.
I tried doing recovery as per Google's suggestion but had no luck at all. After a nvflash I can't get the screen to come on! When I re-flash it it loads up but does the exact same loop and turns off and wont come back on until I reflash.
I'm guessing I need to repartition the device. I have put the clockwordmod recovery image into the flash (as per another posts suggestion) but I can't boot!
Any thoughts?
You could try and use the format utitilty at http://forum.xda-developers.com/showthread.php?t=974422 and afterwards, go to http://forum.xda-developers.com/showpost.php?p=9603803&postcount=1 which gives great detail about how to use nvflash to restore your Gtablet back to a stock image, which there is a download link for 3588 also.
I usually do it this way if things get out of hand and I want to restart from the beginning with a fresh start. It has not failed me yet. For some, the terms may confuse people, but in all, the people here give good instructions to where most can understand it.
I hope this may help you.
sam0433450 said:
Yeah I was just running a stock ROM. I just turned it on one day and it got to the Tap n Tap screen and then the screen goes blank and then the tap n tap screen comes back up. This goes on about 5 times and then just stops.
I tried doing recovery as per Google's suggestion but had no luck at all. After a nvflash I can't get the screen to come on! When I re-flash it it loads up but does the exact same loop and turns off and wont come back on until I reflash.
I'm guessing I need to repartition the device. I have put the clockwordmod recovery image into the flash (as per another posts suggestion) but I can't boot!
Any thoughts?
Click to expand...
Click to collapse
If you put the CWM recovery image into the nvflash configuration then you don't have to boot all the way. Shut it down then start it up while holding the Volume Up key and it should go into CWM recovery. Then try clearing data and caches. If that doesn't cure your problem then go back in and repartition.
Hey guys thanks for the responses but still no luck.
I can't boot into CWM. Once the NVFlash is complete the tablet restarts, goes into a boot loop and then turns off and I can't get it going again.
I've been googling for hours but can't find anything...
sam0433450 said:
Hey guys thanks for the responses but still no luck.
I can't boot into CWM. Once the NVFlash is complete the tablet restarts, goes into a boot loop and then turns off and I can't get it going again.
I've been googling for hours but can't find anything...
Click to expand...
Click to collapse
Have you tried holding down the volume + key when it reboots at the end of the nvflash? That should intercept the boot process and drop you into recovery before it can loop.
Yeah tried that... Doesn't come up with the "recovery key detected" just goes through to the boot loop
Interesting... Which image were you nvflashing? What version of CWM did you insert?
Also... please post the output from the nvflash.
well I used the nvflash_gtablet_2010110500.zip and not sure what version of CWN i'm using...
At one stage I used the nvflash_gtablet_2010110500.zip to see if it made a difference but same thing again.
C:\Documents and Settings\crolls\Desktop\NVFlash\nvflash_gtablet>"nvflash.exe" -
-bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.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: 0x17141188437fa0d7
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: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent 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
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
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 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: recovery.img
| 3862528/3862528 bytes sent
recovery.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
That's the good one. Would be nice to know which CWM but if it isn't recognizing the recovery key that isn't likely the problem anyway. I'll assume you didn't mess with the BCT and bootloader files... weird one.
Would you happen to have access to a linux machine you could try this from? I wouldn't think it would make any difference but you never know.
nah I don't but if there is absolutely no solution I can build a linux box up.
Fml just my luck.
Hey I just tried another format.
i get the Magic Value mismatch and critical falure:unable to load kernal which is all normal but I then get a unrecoverable bootloader error.
It then turns off and I can't get the errors or anythign to come back up
Is that normal?
Is the bootloader the function that actually turns the tablet on? Could this be corrupt somehow? Any way to maybe fix it?
Been watching this thread waiting for a miracle as I have a similar problem. Except in my case any power down results in not being able to restart except to go into APX and do the instructions in this post. However, if I power down I can't get it to boot except into APX.
Here a few interesting observations that may help:
Attempting to boot normally does cause my computer to at least recognize that a USB device is attached. However, can't actually connect to it.
Reflashing following the above post does result in a "normal" reboot. However, even though it says USB Debugging is enabled cannot connect using ADB (which would be great as then I could wipe).
Now here's a really goofy thought - if we had a flash image that did nothing but go into CWM we would be able to do the necessary housekeeping. Once done we could then try to reflash the full recovery and see if that clears the problem.
dodgeman762 said:
Been watching this thread waiting for a miracle as I have a similar problem. Except in my case any power down results in not being able to restart except to go into APX and do the instructions in this post. However, if I power down I can't get it to boot except into APX.
Here a few interesting observations that may help:
Attempting to boot normally does cause my computer to at least recognize that a USB device is attached. However, can't actually connect to it.
Reflashing following the above post does result in a "normal" reboot. However, even though it says USB Debugging is enabled cannot connect using ADB (which would be great as then I could wipe).
Now here's a really goofy thought - if we had a flash image that did nothing but go into CWM we would be able to do the necessary housekeeping. Once done we could then try to reflash the full recovery and see if that clears the problem.
Click to expand...
Click to collapse
Pretty interesting thoughts and at one stage i was thinking along the sames lines as the CWM only image. I'm not too familiar with CWM but I would imagine that the way it has been coded is that it must recognise recovery mode (power +) to load even if it is the only image on the device... Hopefully I'm wrong...
So here I sit staring at the output from running nvflash.sh and I see that, although it creates the partitions:
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 MSC please wait.. done!
Formatting partition 7 BLO please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
It seems it doesn't send them all (clockworkmod is in place of 09_SOS.img)
04_EBT.img sent successfully
05_MBT.img sent successfully
06_MSC.img sent successfully
07_BLO.img sent successfully
08_OGO.img sent successfully
clockworkmod_recovery_bekit-0.8.img sent successfully
10_LNX.img sent successfully
11_APP.img sent successfully
So it seems partitions 2, and 3 are not sent.
Looking in gtablet.cfg they are configured:
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=02_BCT.img
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=03_PT.img
And the files exist:
02_BCT.img
03_PT.img
So, am I onto something or did I just waste a lot of screen real estate?
Thanks in advance, as always!
Edit - Same result in Windows, too.
Partitions 2 & 3 are BCT and Bootloader (which actually contains a copy of the BCT if I remember properly. They aren't sent the same way as the other images. There should be a block of text before the partitioning that shows them being sent. Not sure why it doesn't show them being written but it is normal behavior.
Sheer guesswork but it feels like some kind of bootloader problem to me. You could try a different bootloader file. I have seen this more when using windows than linux but that could be anecdotal.
Sorry, omitted the top part not realizing it's relevance.
lashing G Tablet with base images...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118840dfe297
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: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent 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
setting device: 1 0
sam0433450 said:
nah I don't but if there is absolutely no solution I can build a linux box up.
Fml just my luck.
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I've been successful using Linux based nvflash with LiveCD's and in virtual environments (VirtualBox) so no need to build a box if you can try one of those options. Up to you if you think it's worth a shot.
Yeah I have a linux VBox set up which i forgot about so I'll try that tonight.
How do you use nvflash with LiveCDs? I was just going to go off the instructions from http://forum.xda-developers.com/show...03&postcount=1
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.
Ok so I got this G-tab off of ebay, and the pics looked like everything was fine. Said it was even running the VEGAn-TAB Rom.
It's delivered and I look it over and going yippe! I power it on, see the three stupid birds and then screen goes to another that said G-tabdevs. It just stuck there. I waited an hour just out of sheerest curiosity while emailing the seller. Finally I turned it off and then the seller says that he doesn't know much of anything save that his friend loaded the ROM for him.
It didn't come with an msd card, but it would boot into CWM. Well that was good enough for me, I need to revive this thing so it would actually boot up.
So I found the site for NVFlash for Dummies and was immidiately set back. I didn't know if this was 1.1 or 1.2. So I started out at the Green level and it went worse from there.
Needless to say this has been a crash course in learning.
Basically the tab is now stuck in APX mode. I turn it on without the - button and it's in APX. The drivers are loaded properly on my Win7 and says that APX is loaded.
I've tried just about every combonation that I could find, flashing CWM only to boot into it...nope
Trying Roebeet's versions...nope.
The NVFlash starts out normally after I execute the .bat file, but inevitably fails.
Here's a copy of the most recent attempt...
C:\Users\Moya\Desktop\NVFlash>"nvflash.exe" --bct gtablet.bct --setbct --bl boot
loader.bin --configfile gtablet.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: 0x1714404642200657
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: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent 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
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
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 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
| 6225920/16777216 bytes sentdata send failed NvError 0x120000
command failure: create failed
Press enter to continue:
Sometimes if I redo this attempt using the files
nvflash_gtablet_2010110500
nvflash_windows_20100500
It'll get further along or will hang up sooner.
I'm completely stumped. I've spent hours reviewing other posts and trying things, but to no avail.
I hate to bring up similar topics especially if there have been documented fixes, but I can't seem to find any that will work for me. So if anyone can lend me a hand I'd be really happy and grateful.
Oh and sorry for the long post.
Well I officially feel like a bloody idiot... why is it that I can network a boat load of computers at my house, fix my work computers without breaking a sweat, chuck ROMS on my droid like it's going out of style and I forget the golden rule of
I D 1 0 T Error
I had to use a USB extension cable and I thought, well what the hell, I'll just plug this bastard right into my computer. So after a 15 minute ordeal of rearranging wires... BAM The damned NVFlash works flawlessly....
I'll be breaking my head against the wall on this for days....
Anyways, MODS if you want you can delete this thread or keep it up so that others might think about jacking the cable directly into an onboard port...who knows it might solve other's similar problems....
I had the same problem. However, it seems that the length of the USB cable is the issue. I have been using a ~9 foot USB cable without any issues but this install would not go through. Like you said, sometimes it would get further than others but would never finish. Luckily, I had a 3 foot USB cable too. I hooked that one up and it worked the first time.
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
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
mrchew1982 said:
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
Click to expand...
Click to collapse
It's not bricked.
No need to open at this point.
The links you have looked at are very good starting point.
you may need to put your tablet in APX mode to NVflash a recovery.
APX is power off. Power on with VOLUME (-) (not vol+) and hold until a black screen pops up.
If you have the correct drivers, your PC should recognize the tablet.
You can run the nvflash.bat at this point
I recommend using the method HERE. This is one of the ORIGINAL NVFlash posts for the GTab. I have also posted my own nvflash folder for windows users HERE there is both a 1.1 and 1.2 bootloader version up there.
APX mode blues
Thanks for the quick replies.
I have re-flashed the tablet using APX mode about 20 times already. Both 1.1 and 1.2 branches. With and without cwm. Multiple tries with each image to make sure that there wasn't an error.
I have used the "FORMAT" flash as well, received the mismatch error. flashed all four versions of roms (1.1, 1.1cwm, 1.2, 1.2cwm) after redoing the "FORMAT".
Still nothing. It hangs on the boot image. If I attempt to enter recovery mode it hangs after displaying the text. Even if I hold volume+ during flashing so that it will go directly into recovery mode after the flash.
I know that it is taking the flash, one of the images that I tried has the Tegra logo instead of the Viewsonic as the boot screen. NVflash completes every time without error.
I am really at the end of my rope here as I haven't been able to find anyone that couldn't get into recovery after flashing.
Thanks for the help, any further suggestions would be greatly appreciated!
p.s. I tried once more tonight using Roebeet's instructions and the NVflash Pixelrider provided just to make sure that i didn't miss a step. Still hanging on the boot screen...
Try this:
1. nvflash back to a stock ROM (1.1 or 1.2). I strongly recommend bekit's original 1.1 images.
2. power off before the gTab boots into the stock ROM you just nvflashed.
3. put gTab into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The tablet will try to boot into the stock ROM (for the first time).
still no luck!
Thank you very much for the reply. Something new to try! Unfortunately it still freezes up.
recap:
Downloaded the "bekit 1105" image (nvflash_windows_20100500.zip)from Roebeet's sticky and the windows version of nvflash. Unzipped both into a folder on my desktop. 30 files weighing in at 202MB. (ADX drivers for Windows7x64 were previously manually installed through Device Manager)
Started gtab with "volume-" button depressed. Screen flashed on with Viewsonic logo then flashed off. Attached usb cable. Heard connection sound from Windows.
Opened folder previously mentioned, double clicked nvflash_gtab.bat. Clicked "Run" on warning popup.
cmd.exe window pops up:
Code:
C:\Users\Desktop\Desktop\bekit1105>"nvflash.exe" --bct gtablet.bct --setbct --bl
bootloader.bin --configfile gtablet.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: 0x1714118842bf5057
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: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent 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
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
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 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
(did not press key yet...)
turned gtab off using power button. Disconnected usb and pressed key to exit NvFlash_gtab.bat window.
Turned gtab on whilst pressing "Volume-". Screen flashes on then goes blank. Windows plays connect sound.
Ran command:
C:\Users\Desktop\Desktop\bekit1105>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: 0x1714118842bf5057
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!
C:\Users\Desktop\Desktop\bekit1105>
Click to expand...
Click to collapse
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Waited 10 minutes. powered off using button, disconnected USB. Powered back on, Viewsonic logo appears, black bar flashes onto bottom of the screen, and...
Nothing else happens!
Waited another 10 minutes. Tried to get into recovery mode using "Volume+", still hangs, even with an image on the microsd card. Tried the whole thing over again, still nothing.
The fact that it never reboots after nvflash has me worried that there is something deeply wrong. Is there a way that I could repartition and totally wipe it via nvflash?
This thing is stubborn! Still hoping to find a solution...
Thank you again for the help!
mrchew1982 said:
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Click to expand...
Click to collapse
The ``--go'' parameter to nvflash will cause the bootloader to try to boot into the ROM after the requested actions complete. Without a ``--go'' parameter, the bootloader will wait to further commands and you'll have to power off. If the gTab did not boot into the ROM with ``--go'' then something is wrong.
BTW, does adb work in recovery mode? Run this command:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
and post that text file here if it was any output.
Right now it looks like I'll have to build a custom recovery for you to test things out. In the mean time, try the procedures in this post one by one. See if any of them help. And, stick to bekit's recovery until we resolve this.
Thank you!
Thank you!
I will setup adb later tonight and give it a try. I was reading up on it elsewhere. It will be interesting to see if it responds.
Would hitting the reset button on the motherboard do any good? I have opened the case before to re-solder the power connector...
Thank you, can't say that enough!
mrchew1982 said:
Would hitting the reset button on the motherboard do any good?
Click to expand...
Click to collapse
Try it.
I have opened the case before to re-solder the power connector...
Click to expand...
Click to collapse
Hmm. Now this can't be coincidence, can it? User raywaldo on this board is reporting the same problem after he soldered wires to fix his loose connector. See this thread where I mention this.
Ordinarily, based on the symptoms, I would've said that this was a bootloader incompatibility problem. But, both of you have done a full nvflash, so that's out. I'm leaning towards a HW fault right now, but, we'll need more data to make a definitive determination.
As I said, try out the other procedures first (and don't have a micro SD card with the CWM update file in it while you're doing those procedures--the stock recovery will try to install update.zip files if it finds them; CWM will not). If none of them work, then I'll send you a custom recovery image which will let us know if the bootloader did actually load and run the recovery/std kernel.
no adb. reset didn't change anything.
Thank you for sticking with me rajeevvp.
I installed the android sdk (and JDK) per the instructions:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
I used SDK manager to download the platform tools and the google usb driver. Followed the instructions to uninstall the NvFlash driver and installed it as a composite ADB per the instructions. When i started the tablet normally it loads the usb storage device drive and assigns it drive letter E: (which never shows up in "My Computer" and says "Device not ready" from cmd prompt).
It would only connect as an ADB device when i put it into APX mode, which i don't think is right...
It showed up under USB deview, but said that the driver was winusb.sys, which doesn't sound right to me either...
used the echo command, ran "adb kill-server" and "adb devices". it didn't show anything connected.
next i tried the command that you posted and it said "access is denied".
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
I am looking for damage on the PCB but haven't found any yet. I will desolder the power connector later tonight and give it a bath in some PCB cleaning spray.
Thanks for your help once again!
mrchew1982 said:
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
Click to expand...
Click to collapse
Try that adb command on Linux; Windows is too much pain--don't want to troubleshoot an "ADB is not working" problem too.
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
Click to expand...
Click to collapse
Go through this thread as well.
OK. Now for some troubleshooting.
1. Remove any external microSD cards, as always.
2. Put gTab into APX mode and run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go[/B]
This will format all the problemmatic partitions and then upload CWM-2.5.1.1-bekit-0.8 with a different kernel onto both the "recovery" and "boot" partitions. The kernel has been modified to print boot-up messages as it does on standard Linux. If the bootloader loads and runs either kernel ("boot" or "recovery") then you should see, first, the 2 penguins logo (one for each processor), and then, the kernel messages below that. After the kernel finishes, /init will run, clear the screen, and print "ANDROID" in small caps, and then CWM should start.
3. Use the bootloader.bin--which is from 1.1-3588, the last VS 1.1 update--and the recovery.img in the zip attachment.
surgery done...
I wasn't happy with the solder joints that I laid on last time, it looked like I might have bridged two of the pads... so I removed the power connector completely only to find that the housing was split down the middle. Found a new connector (perfect match here: http://www.dcpowerjacks.net/catalog/index.php?main_page=product_info&cPath=15&products_id=202), got it today. Cleaned the pads and carefully connected the new one. sprayed everything clean, it looked great afterwords, but no change in behavior... I didn't see anything loose or missing either when I went over it with the magnifying glass.
Ok, reflashed per your instructions. here is the output:
Code:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
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
Formatting partition 7 please wait.. done!
Formatting partition 8 please wait.. done!
Formatting partition 9 please wait.. done!
Formatting partition 10 please wait.. done!
Formatting partition 12 please wait.. done!
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
C:\Users\Desktop\Desktop\bekit1105>
It rebooted into the screen that you described but stopped short of going into clockwork. for a long time the last lines were:
Code:
19.213803 so340010_kbd: probe of so340010_kbd failed with error -1
19.217161
19.217164 I2C Slave is *New*
19.820563 NvOdmMouseDeviceOpen failed
20.019509 android_usb Gadget: high speed config #1: android
I then heard the USB connection sound and windows notified me that a USB storage device had been installed (no drive shows up in "My Computer").
Then it started reprinting an error message about every 5 minutes:
Code:
257.010389 INFO: task cpufreq-dvfsd:286 blocked for more than 120 seconds.
257.013674 "echo 0 > /proc/sys/kernal/hung_task_timeout_secs" disables this message.
257.016995 cpufreq-dvfsd D c050ac38 0 286 2 0x00000000
{continued from reboot}
246.807349 Backtrace:
246.810534 (<c050a11c>) (schedule+0x0/0xc18) from (<c00e1680>) (kthread+0x70/0x90)
246.813892 (<c00e1610>) (kthread+oxo/0x90) from (<c00c8498>) (do_exit+0x0/0x73c)
246.817285 r7:00000000 r6:00000000 r5:0000000 r4:0000000
366.817615 INFO: {then it repeats verbatim}
After repeating 3-4times then it goes to a page with just a bunch of numbers inside of parenthesis on the left hand side (counter overran the buffer?) and no text on the right.
When I rebooted it without the USB attached the last message shown is "NvOdmMouseDeviceOpen failed" before it went into the "INFO" error messages.
Still think its a hardware problem?
I will get a linux boot CD setup to try ADB mode again, but i'm hoping that the messages above will be enough to figure this out.
Thank you, once again, for your time and help.
pictures...
Just in case I missed something, I attached some screenshots.
they are in chronological order, 989 is before the "INFO:" error messages pop up, 990 shows those error messages, and 991 is the final screen with no messages.
Thanks for the screenshots. Judging from the visible kernel messages, this looks very much like a hardware fault. The "so340010_kbd" is the driver for the soft keys to the right of the display. The error messages indicate a failure to communicate with the controller for those soft-keys.
I suggest that you start at those soft-key pads and trace the lines back to their controller chip then scrutinize the circuit traces from this chip all the way back to the CPU. See if everything looks OK.
Try ADB on Linux, but, I don't hold out much hope for getting anything out of it: The kernel looks like it is having serious problems with the hardware--I don't think it has even got around to starting up the user-land processes. And, don't worry about the INFO messages relating to cpufreq-dvfsd. You can disregard them for the moment.
EDIT: A thought just struck me. It's winter-time over there, right. Did you take the proper precautions while handling the board? It's very easy to fry a chip silently this time of the year over there using ESD: walk on the carpet, pick up a load of static electricity, then toast something with a simple touch. I borked a board like that one time I was there.
bricked
i have been having same problems with my g-tab, i tried the modified recovery and was able to get to clockwork. i tried updating to few roms, i have NVflashed 100 times. Everytime i NVflash, it shows the tapNtap boot screen, it cycles through this for 4 to 5 times, then just shuts off. Then i try to start again, get nothing, can only go into APX mode which i can only do NVflash and just does same thing. So i tried the modified recovery, goes to clockwork and tried installing other roms, installs without problem, but when restart system will not boot at all. Just black screen and can only do APX mode... also tried opening case unplugging battery, pressing reset button on motherboard... i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
theterminator69 said:
i have been having same problems with my g-tab,...
Click to expand...
Click to collapse
If you can boot into CWM and install ROMs, then you don't have the same problem. And, that modified CWM was meant to be a diagnostic aid--it was not intended to be a cure for gTab illnesses.
i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
Click to expand...
Click to collapse
Is the data still there after you "Partition SD card" in CWM? Make sure you remove any external microSD cards from the tablet first.
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.