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.
With the advent of Blackrose custom HBOOT which gives us S-OFF, we can now resize the MTD partitions of our N1. This method is the one used by lbcoder in the Desire thread where you patch the recovery and boot in order to pass modified MTD partition information which supersedes the one provided by the SPL. Using this, I've managed to increase my userdata partition by ~50 MB by taking ~50 MB from the cache partition.
These instructions are for advanced users only. This will involve hex calculations and command line instructions that are not for the faint of heart. I don't believe it's dangerous though so anyone could still try since I will try to make these instructions as detailed as I possibly can.
What you need:
N1 with Blackrose HBOOT (I'm not sure this is needed though after I read more in-depth about the patch)
hex calculator (or a pencil & paper if you want to do it manually)
adb
fastboot
unpack-bootimg.pl
mkbootimg
recovery.img <- in my case I used ClockWorkMod 5.0.2 from here
boot.img <- taken from CM zip (in my case my KANG)
Partition Layout:
0x000003ee0000-0x000003fc0000 : "misc"
0x000004240000-0x000004640000 : "recovery"
0x000004640000-0x0000049c0000 : "boot"
0x0000049c0000-0x00000dac0000 : "system"
0x00000dac0000-0x0000139c0000 : "cache"
0x0000139c0000-0x00001fe00000 : "userdata"
Partition Sizes in Hex:
0x0000000e0000 : "misc"
0x000000400000 : "recovery"
0x000000380000 : "boot"
0x000009100000 : "system"
0x000005f00000 : "cache"
0x00000c440000 : "userdata"
Step-by-step Instructions:
A>Backup your current system: (OPTIONAL)
*I'm assuming you're using CWM 5.0.2 for the backup step since I tried using 3.X and the restore didn't work
1.) Boot your N1 into recovery using either adb reboot recovery or through the bootloader
2.) Backup your current system (I'm going to assume you know how to use your recovery for this)
B>Calculate new MTD parameter values:
*For this example I'm going to transfer ~50MB of cache space to my userdata partition:
1.) Since I know the cache partition is ~100MB in size, I'll just divide the hex size in 2:
0x5f00000 / 2 = 0x2f80000 <= this will be our new cache size
**Note that there is a minimum of 0x20000 (128k) for a partition and the size must be divisible by it which is why I'm playing safe and just dividing the original number in order to get an easier value for this example.
2.) Add the new cache partition size to the original cache partition starting address to get the new starting address of the userdata partition:
0xdac0000 + 0x2f80000 = 0x10a40000 <= this will be the new starting address for userdata
3.) Get the new userdata size by subtracting the new starting address of userdata with the ending address:
0x1fe00000 - 0x10a40000 = 0xf3c0000 <= this will be the new userdata size
C>Create a new recovery.img file which uses the new values:
1.) Breakdown the recovery.img file into it's kernel and ramdisk components using unpack-bootimg.pl:
.\unpack-bootimg.pl recovery.img
*This will yield 2 files and 1 directory. You can delete the directory since we only need the files.
2.) Rename the kernel from the recovery.img-kernel.gz made from unpack-bootimg.pl to recovery.img-kernel.
3.) Create the recovery-new.img file using mkbootimg with the new MTD command embedded:
mkbootimg --cmdline 'no_console_suspend=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)' --kernel recovery.img-kernel --ramdisk recovery.img-ramdisk.cpio.gz -o recovery-new.img --base 0x20000000
*Note that the values for cache starting address, userdata starting address and userdata size have been changed to the newly calculated values in the previous step.
**This will yield recovery-new.img which will be used in the next steps.
D>Create a new boot.img file which uses the new values:
1.) Breakdown the boot.img file into it's kernel and ramdisk components using unpack-bootimg.pl:
.\unpack-bootimg.pl boot.img
*This will yield 2 files and 1 directory. You can delete the directory since we only need the files.
2.) Rename the kernel from the boot.img-kernel.gz made from unpack-bootimg.pl to boot.img-kernel.
3.) Create the boot-new.img file using mkbootimg with the new MTD command embedded:
mkbootimg --cmdline 'no_console_suspend=1 wire.search_count=5 mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)' --kernel boot.img-kernel --ramdisk boot.img-ramdisk.cpio.gz -o boot-new.img --base 0x20000000
*Note that the values for cache starting address, userdata starting address and userdata size have been changed to the newly calculated values in the previous step.
**This will yield boot-new.img which will be used in the next steps.
E>Flash the recovery-new.img:
1.) Boot into bootloader and use fastboot command to flash the new recovery:
fastboot flash recovery recovery-new.img
F>Make system operational:
1.) Boot into recovery mode.
2.) Erase everything (factory reset)
3.) Either:
- Flash the ROM you took the original boot.img from OR
- Restore the backup you made previously (this only works (or has been tested) on CWM 5.0.2)
4.) DO NOT REBOOT YET!!!
G>Flash modified boot.img:
1.) Use adb to reboot to bootloader directly from recovery: (this is for safety since if you boot from an unmodified boot.img you'll have to start from F again.
adb reboot bootloader
2.) Use fastboot to flash the new boot image:
fastboot flash boot boot-new.img
3.) You may restart normally.
For those who've read this far, everything above has been rendered obsolete! Here's an editor for the SPL itself for the partition sizes:
http://intersectraven.euroskank.com/tools/SPLHexEditor.exe
*Instructions are in dla5244's thread 2nd post.
Try it at your own risk though!
Credits:
dla5244 - for bringing S-OFF to our N1 even after a looong time since its release
Firerat - for the original patch idea
Lbcoder - for coming up with the idea in the Desire thread
Reserved!
(I'm learning to reserve now... )
2 Questions:
Is the userdata space where downloaded apps go?
why didn't you choose any other partition to transfer empty space from?
drzplaya1121 said:
2 Questions:
Is the userdata space where downloaded apps go?
why didn't you choose any other partition to transfer empty space from?
Click to expand...
Click to collapse
1.) Yes.
2.) This is a sample. If you want to transfer from system or to system from cache, this example will show you how to do so.
thank U. Now I have no need to buy a new phone because of constantly running out of memory
Does it mean that every time I flash a new kernel, the whole effort will go waste?
Also, can I use the same procedure for Amon RA recovery??
rjmohit said:
Does it mean that every time I flash a new rom (which obviously has a different boot.img), the whole effort will go waste?
Also, can I use the same procedure for Amon RA recovery??
Click to expand...
Click to collapse
For that you need to do only steps D, F and G. If you flash only a kernel which uses koush's anykernel updater, you don't need to do anything.
intersectRaven said:
For that you need to do only steps D, F and G. If you flash only a kernel which uses koush's anykernel updater, you don't need to do anything.
Click to expand...
Click to collapse
Thanks.
One more silly question
Will the following procedure work.
1. Flash any ROM.
2. Then flash the modified boot.img (which may not belong to that ROM).
3. Then optionally flash the desired kernel.
rjmohit said:
Thanks.
One more silly question
Will the following procedure work.
1. Flash any ROM.
2. Then flash the modified boot.img (which may not belong to that ROM).
3. Then optionally flash the desired kernel.
Click to expand...
Click to collapse
Yeah. That would work since you're replacing the kernel anyways. What's important is that the kernel is compatible with the ROM.
Well done IR cannot wait to resize my data partition..
Okay, I extracted the recovery.img file, now when I try to extract recovery.img-kernel.gz, it gives the following error: not in gzip format. Exactly same happens for boot.img. I tried extracting it with different extractors on windows and ubuntu, nothing worked. Pls help.
I don't like using MTD because over time you will notice lag. If your already using sd-ext then your data is basically not being used. And I believe that cache never gets past 50% usage. Just putting in my two cents
rjmohit said:
Okay, I extracted the recovery.img file, now when I try to extract recovery.img-kernel.gz, it gives the following error: not in gzip format. Exactly same happens for boot.img. I tried extracting it with different extractors on windows and ubuntu, nothing worked. Pls help.
Click to expand...
Click to collapse
That's odd. In my installation, it worked flawlessly. Were there no errors during the run of unpack?
blahbl4hblah said:
I don't like using MTD because over time you will notice lag. If your already using sd-ext then your data is basically not being used. And I believe that cache never gets past 50% usage. Just putting in my two cents
Click to expand...
Click to collapse
intersectRaven said:
That's odd. In my installation, it worked flawlessly. Were there no errors during the run of unpack?
Click to expand...
Click to collapse
Nope. No errors. :-/
rjmohit said:
Nope. No errors. :-/
Click to expand...
Click to collapse
Found the problem. It seems it was never compressed in the first place. Ark sees this and just copies the file without the .gz extension.
*Instructions edited accordingly.
I may sound a bit noobish, but I'm facing one more hindrance:
How exactly do I run the mkbootimg file in the ubuntu terminal? I mean, can you give me the exact syntax?
I was facing a similar problem with the perl script, but then I found a solution on google, but didnt find anything for the mkbootimg. Can I run it under windows cmd?
rjmohit said:
I may sound a bit noobish, but I'm facing one more hindrance:
How exactly do I run the mkbootimg file in the ubuntu terminal? I mean, can you give me the exact syntax?
I was facing a similar problem with the perl script, but then I found a solution on google, but didnt find anything for the mkbootimg. Can I run it under windows cmd?
Click to expand...
Click to collapse
I already posted the syntax in the instructions. You just need to make sure the mkbootimg file has execute permissions in order for it to run.
Updated OP with SPL editor program.
intersectRaven said:
Updated OP with SPL editor program.
Click to expand...
Click to collapse
I tried your program. Everything worked fine. Just that my /cache now shows 290 MB free, while I had resized it to 20 MB!! Is that a bug? /system & /data show proper sizes though. thanks.
rjmohit said:
I tried your program. Everything worked fine. Just that my /cache now shows 290 MB free, while I had resized it to 20 MB!! Is that a bug? /system & /data show proper sizes though. thanks.
Click to expand...
Click to collapse
Is it the display on the program or display on the Android device when booted?
Wait, I found it. It's a bug. Thanks! I'll edit it when I get home. For now, please double check the values by reopening the made file before flashing. If the values are incorrect, please DON'T FLASH!!!
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.
Hello,
I tried to flash Android 4.4 with an updated version of TWRP.
Once the installation was done, my tab hangs at the bootscreen.
I'm seeing the asus logo, but without the text "This device is unlocked"
Lucky me, i have the NVflash, and the blobs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and the imgs
Also i'm able to get in the APX mode
Code:
D:\Tablet Brick safe\tf201_nvflashpack>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07875164040c
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
So what should i do next?
Thanks dor the help.
brantje said:
So what should i do next?
Thanks dor the help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1927818
And boom goes the dynamite..
wickid_d said:
http://forum.xda-developers.com/showthread.php?t=1927818
And boom goes the dynamite..
Click to expand...
Click to collapse
If I don't have blob.bin, can I unbrick my tf201 ?
How can I get this file ?
darkjeff said:
If I don't have blob.bin, can I unbrick my tf201 ?
How can I get this file ?
Click to expand...
Click to collapse
With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little.
wickid_d said:
With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little.
Click to expand...
Click to collapse
I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot.
darkjeff said:
I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot.
Click to expand...
Click to collapse
Have you tried using adb to reboot to it? 'adb reboot-bootloader'? Even if CM (or any rom, for that matter) is just barely starting to boot, you should be able to do this. Once you get to fastboot, follow this guide:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
And then follow the guide in my previous post in this thread and that will at the very least get you back to stock.
And remember, whenever you flash something in fastboot, no matter what it is, use the option '-i 0x0b05'.. Like for recovery 'fastboot -i 0x0b05 flash recovery (name of recovery here)' This will save you more headaches.
Trouble with generating blob.bin with Flatline_tf201.img / CWM
Moved to proper thread
brantje said:
Hello,
I tried to flash Android 4.4 with an updated version of TWRP.
Once the installation was done, my tab hangs at the bootscreen.
I'm seeing the asus logo, but without the text "This device is unlocked"
Lucky me, i have the NVflash, and the blobs.
So what should i do next?
Thanks dor the help.
Click to expand...
Click to collapse
Did you solve it? I think i am in same trouble.
vanquishe said:
Did you solve it? I think i am in same trouble.
Click to expand...
Click to collapse
Mot yet l. Will look into it this weekend. Quite busy with work.
Sent from my SM-N9005 using Tapatalk
I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
1. Stock JB, newest from OTA, untouched
(im from japan, so i think its a JP SKU)
2. Followed guide to unlock + backup blobs + enable nvflash for JB
http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
3. Rooted with motochopper
4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14]
http://forum.xda-developers.com/showthread.php?t=2589554
4.1 Downloaded and transfer following files to sdcard folder
cm-11-20140220-UNOFFICIAL-tf201
pa_gapps-modular-mini-4.4.2-20140227-signed
4.2 Downloaded recovery.img.SOS 2013-12-29 08:42
http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS
4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS
(I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly)
4.4 restart TF, "power+down", select RCK
4.5 Did the following in recovery menu:
a. Backup, but did it to sdcard instead of ext storage
b. wipe data/factory
c. wipe cache partition
d. wip dalvik cache
e. install zip: cm-11-20140220-UNOFFICIAL-tf201
f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed
At step f, the screeen said somthing about insufficient space.
So i thought i would try without GAPPS and selected reboot system now.
5. Got stuck at Asus word in middle of screen
a. Bottom right shows "Powered by nvidia terga"
b. Oddly, top left no longer displays "device is unlocked"
6. Tried to reboot (holding power long time)
a. Screen black out, vibrate
b. Tried to get to fastboot (power + down) but the icons never show
c. Constantly stuck with Asus screen
7. Attempted to follow guide:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
a. "Power + up", apx device shows in windows 7 device manager
b. wheelie.exe --blob blob.bin
c. nvflash.exe -r --download 4 bootloader.EBT
(bootloader.ebt is the output i got previously from flatline)
(my bootloader.ebt is 1,558,608 bytes)
(blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes)
d. This is the log
log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader.ebt
bootloader.ebt sent successfully
e. Device went black screen, device manager does not show APX
f. I power the device up but shows black screen. "power + down" still does not work.
g. However, "power + up" still get APX device in windows.
---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ----------
Im thinking I could try either of the following:
Option 1:
1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed
and try to go as far as I can and pray for the best
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Option 2:
1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T]
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
seems to talk about unlock-token.img,bricksafe.img,factory-config.img
but it is for tf300T
also, i have no idea how to get the following file
"this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run
"Code: nvflash -r --download 5 twrp.blob"
Option 3:
1. Sit and wait for help... no one on MIRC seems to be responding T T
Any ideas?
vanquishe said:
I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
Any ideas?
Click to expand...
Click to collapse
Ok, first off, it IS 0x0b05.. 0b05 is the vendor/hardware hexadecimal ID number, which is why -i (short for ID) when using fastboot. You can verify this by hooking the tablet up to a linux environment and running 'lsusb' in terminal and looking for the Asus line. In Windows, I'm not exactly sure why the 0x gets added at the front. I guess it's just how Windows handles hardware IDs. (source: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ part: (Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05".))
Second, you won't be able to install the full PA Gapps along with CM11 - you're right, there isn't enough room. Use either the micro or mini package. This is talked about in the CM11 thread you mentioned, where I have been frequenting, as of late.
Third, and finally, what exactly are you waiting on? You've done everything correctly as far as I can tell. Just start the process over with reinstalling stock via this guide:
http://forum.xda-developers.com/showthread.php?t=1927818 and you can either flash TWRP through nvflash mode like you did (good job on that ), or via fastboot, and go from there. Whether it shows 'this device is unlocked' or not, at this point, shouldn't matter.. You've run through the nvflash process and created your blob.bin along with the other files.
I hope this helps.
Hi Mates,
Will start looking into it now.
As long i can get TWRP i'm happy, because then i i'm not far from installing a custom rom.
14:55 - Tablet was empty its charging now
16:27 - I'm screwd i think...
D:\Downloads\Tablet Brick safe\Tablet Brick safe\tf201_nvflashpack>wheelie.exe -
-blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07875164040c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
Will keep this post updated about my progress.
vanquishe said:
I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
1. Stock JB, newest from OTA, untouched
(im from japan, so i think its a JP SKU)
2. Followed guide to unlock + backup blobs + enable nvflash for JB
http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
3. Rooted with motochopper
4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14]
http://forum.xda-developers.com/showthread.php?t=2589554
4.1 Downloaded and transfer following files to sdcard folder
cm-11-20140220-UNOFFICIAL-tf201
pa_gapps-modular-mini-4.4.2-20140227-signed
4.2 Downloaded recovery.img.SOS 2013-12-29 08:42
http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS
4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS
(I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly)
4.4 restart TF, "power+down", select RCK
4.5 Did the following in recovery menu:
a. Backup, but did it to sdcard instead of ext storage
b. wipe data/factory
c. wipe cache partition
d. wip dalvik cache
e. install zip: cm-11-20140220-UNOFFICIAL-tf201
f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed
At step f, the screeen said somthing about insufficient space.
So i thought i would try without GAPPS and selected reboot system now.
5. Got stuck at Asus word in middle of screen
a. Bottom right shows "Powered by nvidia terga"
b. Oddly, top left no longer displays "device is unlocked"
6. Tried to reboot (holding power long time)
a. Screen black out, vibrate
b. Tried to get to fastboot (power + down) but the icons never show
c. Constantly stuck with Asus screen
7. Attempted to follow guide:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
a. "Power + up", apx device shows in windows 7 device manager
b. wheelie.exe --blob blob.bin
c. nvflash.exe -r --download 4 bootloader.EBT
(bootloader.ebt is the output i got previously from flatline)
(my bootloader.ebt is 1,558,608 bytes)
(blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes)
d. This is the log
log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader.ebt
bootloader.ebt sent successfully
e. Device went black screen, device manager does not show APX
f. I power the device up but shows black screen. "power + down" still does not work.
g. However, "power + up" still get APX device in windows.
---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ----------
Im thinking I could try either of the following:
Option 1:
1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed
and try to go as far as I can and pray for the best
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Option 2:
1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T]
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
seems to talk about unlock-token.img,bricksafe.img,factory-config.img
but it is for tf300T
also, i have no idea how to get the following file
"this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run
"Code: nvflash -r --download 5 twrp.blob"
Option 3:
1. Sit and wait for help... no one on MIRC seems to be responding T T
Any ideas?
Click to expand...
Click to collapse
Exact same boat, so will try and look for answers now.
Where on mirc, maybe we can help each other.
I will just sit quietly here and wait for anyone with an answer.
(Yes, me too)
vanquishe said:
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Click to expand...
Click to collapse
Yes, that.
I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore.
Xerxes-3.0 said:
I will just sit quietly here and wait for anyone with an answer.
(Yes, me too)
Yes, that.
I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore.
Click to expand...
Click to collapse
I had help from a nice person from IRC. Now my TF201 is up and running again.
I will up the process he guided me once I get home later.
Please thank lj50036 from the CMB team.
It was him that guided me thru the process to unbrick my TP.
-----------------------------------------------
Bricked situation:
1. Last activity before brick: Stock with latest OTA -> Flatline (OK) -> Motochopper (OK) -> Flash CWM recovery (OK) -> Unofficial CM11 (Reboot = bricked)
2. Stuck at ASUS logo on power up/reboot. (Device is unlocked no longer shows on top left corner)
3. Cannot get to fastboot (power + dwn = stuck at ASUS logo)
4. However, can invoke APX mode (power + up = APX device detects in windows)
-----------------------------------------------
Preparation:
1. All the output files from the flatline (blob.bin, unlock-token, bricksafe, factory-config etc)
2. Fastboot,adb,nvflash exe (you should have all these when you did flatline)
3. Enough battery (I left it overnight to charge, since I had no way of checking batt)
4. The stock firmware from ASUS (you should get the same version as the one you had prior to brick)
-----------------------------------------------
Actual process:
1. I was told to put all the files from fastboot,nvflash etc in C root (ie .exe,.img,.dlls, bin etc). I think it is not a must, as long as you have all the files together and dir has no spaces.
2. Unzip the firmware file from ASUS.
My case: the file name is JP_epaduser_10_4_2_18UpdateLauncher, extracted to find JP_epad-user-10.4.2.18. Extract again to find a file called Blob, which is about 500mb.
3. Copy the blob file to C root
4. Open CMD as admin. Make sure you do so as admin.
5. Goto C root, type: cd\
6. Just make sure you can execute the following exe: fastboot, adb, nvflash, type: fastboot
The commands should output the help related info....ie parameters etc
7. Now boot you tablet into apx conneted to your pc from tablet to pc no hubs docks> Device manager shows Asus tranformer prime APX interface.
8. Type: wheelie --blob blob.bin
My output:
C:\>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a49042111
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
My tablet screen shows:
top left: entering nvflash recovering mode / nv3p server
chip uid: 015c7d7a49042111
center: Asus
bottom right owr by...
9. Now it may reboot at the end of this just get back to apx mode on your tablet.
Type: nvflash -r --download 7 unlock-token.img
Output:
C:\>nvflash -r --download 7 unlock-token.img
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
unlock-token.img sent successfully
*My device black out. So i rebooted to APX again as instructed.
10. Type: wheelie --blob blob.bin
11. Type: nvflash -r --download 14 factory-config.img
Output:
C:\>nvflash -r --download 14 factory-config.img
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
factory-config.img sent successfully
*My device black out. So i rebooted to APX again as instructed. An did wheelie again
12. Type: nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Output:
C:\>nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
bricksafe.img sent successfully
*device did not blackout this time. So no need to reboot.
13. Type: nvflash -r --go
Output:
C:\>nvflash -r --go
Nvflash v1.13.87205 started
[resume mode]
14. Power + DWN to try to get to fastboot. Select the USB icon.
*windows device manager should detect fast boot interface
*confirm this by typing: fastboot devices
*my output was: 015c7d7a49042111 fastboot
15. Type: fastboot erase system
Output:
C:\>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.671s]
finished. total time: 2.671s
16. Type: fastboot erase recovery
Output:
C:\>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.929s]
finished. total time: 1.929s
17. Type: fastboot -w
Output:
C:\>fastboot -w
erasing 'userdata'...
OKAY [ 50.110s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 61980278784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 15131904
Block groups: 462
Reserved block group size: 1024
Created filesystem with 11/3784704 inodes and 283616/15131904 blocks
sending 'userdata' (141195 KB)...
Created filesystem with 11/3784704 inodes and 283616/15131904 blocks
sending 'userdata' (141195 KB)...
writing 'userdata'...
OKAY [ 26.179s]
FAILED (command write failed (Unknown error))
finished. total time: 76.878s
*dont be bothered by the error
18. Type: fastboot devices
Output:
C:\>fastboot devices
???????????? fastboot
19. Reboot and get back to fastboot again, check that your device is detected by Type: fastboot devices
Output:
C:\>fastboot devices
015c7d7a49042111 fastboot
20.fastboot erase boot
Output:
C:\>fastboot erase boot
erasing 'boot'...
OKAY [ 1.874s]
finished. total time: 1.874s
21.Type: fastboot erase misc
Output:
C:\>fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
22. Type: fastboot erase cache
Output:
C:\>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.713s]
finished. total time: 1.713s
23. Next cmd takes long time. Type: fastboot -i 0x0B05 flash system blob
* During the writing process of this step you will get the blue bar on your screen.....
Output:
C:\>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.225s]
sending 'system' (537604 KB)...
OKAY [ 90.363s]
writing 'system'...
OKAY [130.010s]
finished. total time: 222.600s
24. Type: fastboot -i 0x0B05 reboot
*this reboot should bring you to stock rom
*will take some time, just be patient
*does not matter if you have usb connected or not
-----------------------------------------------
If you reach here, you should have a fresh TP with stock, except its unlocked.
Hope this helps.
This is great, thank you.
I actually wanted to do this yesterday evening when i found out that the prime has run out of battery (because I'm a genius), but I will do this today.
Ok, it did not work from scratch, but then, I had already another ROM so I made things difficult.
With your checklist, I got to step 13, but still only APX mode. So i did some guessing work.
What I did (in short, assuming I have everything till your step 7 and doing the wheelie everytime):
a) nvflash -r --download 4 bootloader.ebt
b) nvflash -r --download 7 unlock-token.img
c) nvflash -r --download 5 recovery.img.SOS (the modified CWM from namidairo for his unofficial CM11)
d) nvflash -r --rawdevicewrite 0 2944 bricksafe.img (no wheelie afterwards)
e) nvflash -r --go
Now I DO have the option for fastboot but no recovery (unrecoverable boot loader error).
Will continue frfom here.
===
Next: Another bootloader. I tried the blob.EBT from the stock ROM and with this, it actually tries to boot by itself (showing "device is unlocked").
===
Fine. I repeated wheelie and step c), got the blue bar, now I have thew modified CWM v6.0.4.5. Running. Yay me.
Okay, after one try with CM11 ended me where I was starting, I came back to CWM with step a) and b), and now I'm going to bed.
I am stupid and skipped flashing the stock ROM.
Stupid me. Now it works. Weee!
Did I say thank you? I think just one time. Thank you for posting thes extrensive get-youself-out-of-the-dirt-manual.
This thread has the most important info for the TFP I've seen. This info should be shared out to the Brick recovery thread (and linked to the custom ROM threads)! I've been thinking of moving from Androwook to CM11, and the only way I would try it is with a really good grasp on recovering the blob files. So again thanks, this is now bookmarked to my favorites. And especially a huge thanks to Xerxes-3.0 and vanquishe. You both just saved me from my future brick!
I attempted to install Jasmine rom, after it failed twice I tried to recover and failed at that. Then after trying to resinstall twrp i got it into a bootloop and no recovery and no download and no recovery.
I need the following .img for the LG G3 vs985 to try to use the method in the link below:
NEED THESE FILES:
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
http://forum.xda-developers.com/showthread.php?t=2582142
Here are the files from 10b:
http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/stock_partitions/10B
Be careful (those are things that mere mortals like I wouldn't mess with )
THANK YOU!!
markfm said:
Here are the files from 10b:
http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/stock_partitions/10B
Be careful (those are things that mere mortals like I wouldn't mess with )
Click to expand...
Click to collapse
Thank you very much. now i just need to figure out why It wont show me the locations of all those files when i enter the terminal in linux... I'm getting something like this:
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
************************************************** *****************************************
Found invalid GPT and MBR valid; Converting MBR to GPT format in memory.
************************************************** *****************************************
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4746570D-B91E-4A91-917C-D94BCEBD34F3
Partitions table holds up to 128 entries
First usable sector in 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 310512237 sectors (148.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 52430847 25.0 GiB 0700 Microsoft Basic data
2 52430848 314632191 125.0 GiB 0700 Microsoft Basic data
Only this was copied from another post. I am using linux.
Any suggestions?
No idea. What you posted doesn't make sense to me. Hopefully someone else will pop in.
I copied from another post but I am getting roughly the same response when I rum the gdisk Dev command in Linux terminal. It does recognize the device as lg. But it doesn't appear to find the device while running the command to see the list of img files.
Also having trouble coding the file extension to push the img files with dd command.