I have Asus TF101 b90 Eepad. It's locked in a boot loop. I have Rogue XM Recovery 1.3.0 - CWM-based recovery v 5.0.2.7. I've tried to reflash a new stock or modified ROM, but none of the methods found on the forums seems to be working. I cannot write the blob.EBT file, using wheelie+nvflash. It seems to format the EBT partition but locks during writing process, with the message: "Sending file: blob.ebt 65536/1454712 bytes sent" and that's all. I can't even format /data/media folder. Looks like the nv chip is write protected - none of the chmod methods worked. I can use nvflash or ADB so it boots in recovery, i've tried both Linux and Windows 7 nvflash+wheelie with the same result: no changes to ROM, recovery image or anything else. I don't know what hapened prior to boot loop because one of my kids was using the Eepad - i assume it started updating or something. Tablet was rooted but i don't think it was ROM Manager.
Have you tried to wipe all data, cache, and Dalvik-cache?
Sent from my Transformer TF101 using Tapatalk HD
asd25_2005 said:
I have Asus TF101 b90 Eepad. It's locked in a boot loop. I have Rogue XM Recovery 1.3.0 - CWM-based recovery v 5.0.2.7. I've tried to reflash a new stock or modified ROM, but none of the methods found on the forums seems to be working. I cannot write the blob.EBT file, using wheelie+nvflash. It seems to format the EBT partition but locks during writing process, with the message: "Sending file: blob.ebt 65536/1454712 bytes sent" and that's all. I can't even format /data/media folder. Looks like the nv chip is write protected - none of the chmod methods worked. I can use nvflash or ADB so it boots in recovery, i've tried both Linux and Windows 7 nvflash+wheelie with the same result: no changes to ROM, recovery image or anything else. I don't know what hapened prior to boot loop because one of my kids was using the Eepad - i assume it started updating or something. Tablet was rooted but i don't think it was ROM Manager.
Click to expand...
Click to collapse
Since nvflash works, flash the stock ROM.. yous said it gets stuck while pushing ROM right ? Then let tit take time and leave it to work on its own phase and wait for it to finish. In my experience easy flasher/nvflash takes little time to complete. If that doesn't work then try pushing TWRP recovery using nvflash/easy flash.. BTW I also have B90 and nvflash always worked for me..
Sent from my Transformer using xda app-developers app
No results
kenshin1388 said:
Have you tried to wipe all data, cache, and Dalvik-cache?
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
Yes, i've tried theese methods with no results. I can only format SD card - external. After reboot is all in the same place . Nothing changes.
udupa82 said:
Since nvflash works, flash the stock ROM.. yous said it gets stuck while pushing ROM right ? Then let tit take time and leave it to work on its own phase and wait for it to finish. In my experience easy flasher/nvflash takes little time to complete. If that doesn't work then try pushing TWRP recovery using nvflash/easy flash.. BTW I also have B90 and nvflash always worked for me..
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I've left it for hours to write the blob.ebt file but stays like that forever. I've tried to use nvflash --format_partition 4 (in my case is the ebt partition) with no results - it stays saying "formatting" and remains in this state.
I have tried to push other recoveries using ADB push. If a file is written to the SDcard - internal memory, after reboot it delets it. If i try to make another folder on the internal memory it says: "Read only folder" and it doesn't allow to write any files or folders. I've tried chmod with no results. I wanna use RMA for my tablet (i have 2 years of warranty for this - 1 year left but i can't delete the Rogue Recovery so i can return it).\
Thanx for your advices!
asd25_2005 said:
I've left it for hours to write the blob.ebt file but stays like that forever. I've tried to use nvflash --format_partition 4 (in my case is the ebt partition) with no results - it stays saying "formatting" and remains in this state.
I have tried to push other recoveries using ADB push. If a file is written to the SDcard - internal memory, after reboot it delets it. If i try to make another folder on the internal memory it says: "Read only folder" and it doesn't allow to write any files or folders. I've tried chmod with no results. I wanna use RMA for my tablet (i have 2 years of warranty for this - 1 year left but i can't delete the Rogue Recovery so i can return it).\
Thanx for your advices!
Click to expand...
Click to collapse
Try BRK's tool to unroot and flash a stock ROM, following the instructions in the tool.
http://forum.xda-developers.com/showthread.php?t=1688447
No results
sidneyk said:
Try BRK's tool to unroot and flash a stock ROM, following the instructions in the tool.
http://forum.xda-developers.com/showthread.php?t=1688447
Click to expand...
Click to collapse
Thanx for your reply. I've downloaded BRK's tool. It does work. Writes recovery but after restart it's all back in the same place, nothing changes!
Here is an example of nvflash:
D:\backup tablet\nvflashWW\nvflashWW>wheelie.exe -2 --bct transformer.bct --bl
bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
- 65536/1454712 bytes sent >>>>>>> And it remains like that.
Any ideas?
Thanx in advance for your help!
I'm using Windows 7 Ultimate N 32bit edition
I just remembered something. Your blob.ebt file may be corrupt. A few months back I took a nvflash backup of several recoveries so I could keep them on hand. Problem was, when I wanted to flash a copy of TWRP I made it always froze. No other recovery backups did though. Try to get a stock fresh copy of stock Rom and use blobunpack on that.
Sent from my U8652 using xda premium
Download a stock ASUS zip for your fw, fresh, the whole 300+mb file, run blobunpack on it and flash it (ebt portion of blob) through bootloader (EBT) partition or staging (mmcblk0p4) partition.
EDIT: do you have adb access? fully working
asd25_2005 said:
Thanx for your reply. I've downloaded BRK's tool. It does work. Writes recovery but after restart it's all back in the same place, nothing changes!
Here is an example of nvflash:
D:\backup tablet\nvflashWW\nvflashWW>wheelie.exe -2 --bct transformer.bct --bl
bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
- 65536/1454712 bytes sent >>>>>>> And it remains like that.
Any ideas?
Thanx in advance for your help!
I'm using Windows 7 Ultimate N 32bit edition
Click to expand...
Click to collapse
You are able to get the tablet into APX mode? If so, maybe try to redownload the stock firmware from Asus, in case you had a bad download. I used Asus 9.2.1.27 US as I have a US tablet.
No results
kenshin1388 said:
I just remembered something. Your blob.ebt file may be corrupt. A few months back I took a nvflash backup of several recoveries so I could keep them on hand. Problem was, when I wanted to flash a copy of TWRP I made it always froze. No other recovery backups did though. Try to get a stock fresh copy of stock Rom and use blobunpack on that.
Sent from my U8652 using xda premium
Click to expand...
Click to collapse
Thanx again for your reply. I've already tried different versions of stock ROM and blobunpack to extract the needed blob.EBT file. I'ts the same error, stuck at 65536. Anyway, yesterday i got a new mail, a reply from Asus, telling me that the problem may be a hardware memory issue (the memory chip itself, into the motherboard). If i have rooted my tablet and replaced the stock recovery with a custom one do i lose RMA or is still effective? If not, can they change the deffective chip with a new one?
Have a nice day!
Yes, i have ADB access
Thing O Doom said:
Download a stock ASUS zip for your fw, fresh, the whole 300+mb file, run blobunpack on it and flash it (ebt portion of blob) through bootloader (EBT) partition or staging (mmcblk0p4) partition.
EDIT: do you have adb access? fully working
Click to expand...
Click to collapse
Thanx for your reply.
I have ADB acces, in recovery mode, and even APX mode for nvflash. Pushing or pulling files works in ADB but the internal memory seems to be read-only. What can i do to make a full repartitioning of the internal memory? I'm at a point where i wish to do a permanent brick so i can return it to Asus using the RMA.
Have a nice day!
I'm not sure how to execute the binary for fat32 or ntfs, but I know most custom roms come with mke2fs binary with busybody. You could use that to completely reformat the internal memory.
Can get the mountpoint using this or something of the mounted area you need to reformat. I know by default mke2fs reformats to ext4. A quick Google search should return a result.
mountpoint -n /sdcard
Sent from my Transformer TF101 using xda premium
Some results
Thanx, kenshin.
I've managed to get around the "65536/1454712 bytes sent" by modifying the flash.cfg file:
[device]
type=hsmmc
instance=2 >>>>>>>> originally was 3
it sends data much slower but, hey, it works.
So now it's writing the blob files but, at the end, it runs into a new error:
C:\wheelie>cd C:\wheelie\
C:\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x3
00d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile flash.cf
g --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4282368/4282368 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
\ 4044800/4044800 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
C:\wheelie>pause
Press any key to continue . . .
Aaaand, i'm stuck again! I've read about using the wrong version of nvflash so i tried several nvflash executables, including the ones found in EasyFlasher or BRK Rootkit with no results. Older version of nvflash seems to send the blob files and after that the tablet freeze. When i re-start it it's back again, in boot loop, with the original ROM and no other changes!
Again i think that the memory chip is read-only, due some hardware errors.
I can't do nothing to change even one single file in the internal memory using ADB or APX mode.
See this thread. Their answer is post 22. Different device but same problem... hope you can figure it out!
SOLVED
My ASUS TF101 was sent for RMA. They've changed the motherboard. This confirmed that my worst case scenario was true: the eMMC became Read-only and there was no way to restore the tablet. Now it works again and is everything is ok. Thanks for your interrest in assisting me.
Related
I think its done for but I want to be sure. I've used nvflash many times to revert to stock but this time I tried the format rom (http://forum.xda-developers.com/showthread.php?t=974422) just before I tried to revert.
So far I've tried flashing with nvflash following the directions here (http://forum.xda-developers.com/showthread.php?t=861950) using the 1105 and the 1126 images. The format rom still completes but the stock rom gives the following output.
"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: 0x1714400940ffc357
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
/ 3407872/33554432 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Press enter to continue:
I've tried to use nvflash to get CM .8 back but nothing seems to work. I hope someone has an idea on how to recover from this.
Thanks in advance
ok, I fixed my issue and found a new one.
1. I re-downloaded the format
and the 1126 rom files.
2. I re-ran the format rom.
3. I copied the files from "nvflash_gtablet_46_2010112600.zip" into the same directory as the format rom files and ran the new nvflash_gtablet.bat file.
For some reason this time it worked. I tried this before but for some reason it worked this time.
Once I got in I updated to 3588 using the OTA updater and now it only boots in to APX. Seems others are having the same issue. I'll keep trying to get this resolved but if anyone has some insight into this problem I'd love to hear it.
Well, you probably already know, but for the sake of beginning a new, clean thread-
Using nvflash.exe, you can simply
nvflash.exe --bl bootloader.bin --format_partition 2 --go
And it will reboot your tablet without erasing anything important.
Holding down the volume key will get you into recovery mode as well, if you hold it before you press enter.
Hope we can fix this. Im tired of explaining how i fried something and it wont boot with a computer.
So after many hours of searching the forums and web for different possible solutions, and trying them all, I think I'm going to throw in the towel. Mine is still in the 30 days for a return so I think I'll just return it and get another.
All my issues started when I tried the format rom, so that's one I'll not do again.
Good luck to everyone still fighting to get their gtab to boot out of APX mode.
You might have better luck with the 1105 image. I would give that one more try before you give up. You might also need to reinstall ClockworkMod and repartition your internal sdcard.
When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?
notwen said:
When you say you can only get into APX mode, will the unit not power up at all or are you only getting bootloops of the Viewsonic and G-Tablet screens?
Click to expand...
Click to collapse
APX mode is like fastboot mode in other devices.
On the gtablet, it is a blank, unlit screen.
It waits for a command from a host device, and once it gets one, the screen lits up black with a single line of text.
Its as if the unit doesnt power up, but it really does. The only way to tell is to have it plugged up to a computer.
I mean, you can use nvflash to boot it.
And i will try the 1105 image in the next 24 hours and report if it got the device to boot independently.
Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
F:\nvflashtf>download.bat
F:\nvflashtf>cd F:\Chrome DL\nvflash\nvflashtf\
F:\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --co
nfigfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x168
2CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c6208417fd657
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
\ 5085184/5085184 bytes sent
recovery.img sent successfully
file not found: boot.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks
I don't think you're supposed to update after you've rooted
I bricked one that way
Hmm, well things seemed to be fine after doing so. It was just the nvflash which finished me off. I'm new to all this.
Any suggestions on getting it back? I have the whole weekend to try now.
Try redownloading the nvflash files? Maybe the checksum failed.
It seems boot.img was not found, but your download.sh script tries to install it.
it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again
lilstevie said:
it is because you have run nvflash in create mode which partitions and installs the android system, but you don't have an android systems images in the same folder as nvflash and the batch file.
download prime 1.6 nvflash edition, put it in the same folder as these files, and run that script again
Click to expand...
Click to collapse
Thanks! This made a lot of sense after I read it. I downloaded the nvflash edition and ran the download.bat. It found the missing files and copied them to the transformer successfully. I then rebooted the device and was back in action with prime. Appreciate it!
compywiz said:
Hey guys,
I was testing out nvflash and ran the download.bat on my new transformer and now it's stuck in APX mode.
I see when running nvflash, it says:
Now the screen is black and keeps going into apx.
Before running it I had rooted 3.1 and had just updated to 3.2 which worked fine.
Any help please?
Thanks
Click to expand...
Click to collapse
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.
goodintentions said:
Just be glad you didn't put your device in a permanent apx bootloop. You're just missing the android system image.
I've had to deal with a few devices that was somehow put in permanent apx bootloop by their owners. Before I actually got my hands on these devices, I honestly thought they didn't really exist and that it was just users' ignorance. But damn, these devices with permanent apx bootloop are hard to unbrick.
Click to expand...
Click to collapse
Definitely glad. The funny thing is I ran the nvflash because I wanted to see if it worked for getting a clean install, little did I know I would make it cleaner than I wanted :x. I had an idea that I needed to supply the files, but really had no idea where to get them. Luckily lilstevie pointed me in the right direction. I've since updated to Prime HC3.2 and loving it so far.
Glad it's back and working now though!
Hello,
I'm experiencing a problem during an installation of a new fresh rom.
My TF did bootloops (no apparent reasons) on asus boot screen earlier this day.
After trying to restore a backup and wipe all the data via CWM, the device is now stuck on APX mode (black screen).
So I decided to reinstall a fresh prime rom on it via the software brk root toolkit because I can't have an acess on CWM recovery anymore.
I use the nvflash method to install the new rom (as I say I restored my boot and system files but it doesn't change anything) but there is a problem during the flash when formatting the 15th partition (UDA).
Here is what nvflash printed :
_______
C:\Users\asus axel\Downloads\Windows\Win>cd C:\Users\asus axel\Downloads\Windows
\Win\
C:\Users\asus axel\Downloads\Windows\Win>"nvflash.exe" --bct transformer.bct --s
etbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 -
-sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380618741ff50d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361053/1361053 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. -
_____
NVflash is stuck on this position for nearly one hour and the device shut down itself and can't finish the rom installation.
I tried to reinstall via NVflash with several rom (prime 2.1.0, prime 1.6r2, prime 1.4 and stock firmware 3.2) and it print the same error aswell.
I can't get forward ...
Anyone has a solution to reinstall a new rom or to bypass this error? Am I stuck to an APX bootloop? Do I have to send my device to asus to restore the damn thing?
At least I want to have access to CWM again.
Thanks in advance and sorry for my engrish.
Well, I finally manage to install a clean stock rom and now everything works!
I made a full restore first with brk root toolkit and then I apply a stock rom with nvflash.
Thanks to the community which provides me these tools.
My Nigthmares
likweed said:
Well, I finally manage to install a clean stock rom and now everything works!
I made a full restore first with brk root toolkit and then I apply a stock rom with nvflash.
Thanks to the community which provides me these tools.
Click to expand...
Click to collapse
Pardon my english!! I am V. Poor in english
I had the Same problem.. Asus TF101 B70.
Initially My device was going on Boot Loop for no reason , but it used to get resolved whenever I do a (Soft reset Power+Vol Down and then wait for next screen and press Vol Up on the Android Image).
I flashed my recovery to Roach. with easy flasher. Thanks to White Kidney!!! http://forum.xda-developers.com/showthread.php?t=1688012
Then when i flashed with Stock ROM i was hanging up at Formatting No15 UDA.
With Impatience I quit the process and then MY TF was a total brick!! Only APX.. No bootloader nothing.
I learnt about Wheelie / nvflash. I even tried the above procedure of un-blobbing and flashing just EBT. No Luck!!!!.
Then i found this lucky tool by brk
http://forum.xda-developers.com/showthread.php?t=1688447&page=1
This made my life easier (I thought) . I backed up my whole device and then I tried the restore.. But no Luck!!
Then I came back again to Easy Flashed and I flashed the device with ASUS stock WW v9.1..... . .. 27..
YOU NEED PATIENCE.. I told to myself
I waited for a long time in the 15th step Formatting UDA.. I left the process and went out to the Hospital to help my Mom's Physiotherapy Classes. Came back after 1-2 hours.. and my Screen was blank!!! (Both Laptop and TF101)...
Guess which one i turned on first!! My TF101.. And there Voila... I saw the Welcome screen to choose my Language.. I was Smiling like an Angel.. Happy Cheerfull after a full day and night of hardwork..
Then i saw the command prompt to see that NVFlash was successfull..
Dont forget this after you got lucky!!
Ameen XDA said:
Pardon my english!! I am V. Poor in english
I had the Same problem.. Asus TF101 B70.
Initially My device was going on Boot Loop for no reason , but it used to get resolved whenever I do a (Soft reset Power+Vol Down and then wait for next screen and press Vol Up on the Android Image).
I flashed my recovery to Roach. with easy flasher. Thanks to White Kidney!!! http://forum.xda-developers.com/showthread.php?t=1688012
Then when i flashed with Stock ROM i was hanging up at Formatting No15 UDA.
With Impatience I quit the process and then MY TF was a total brick!! Only APX.. No bootloader nothing.
I learnt about Wheelie / nvflash. I even tried the above procedure of un-blobbing and flashing just EBT. No Luck!!!!.
Then i found this lucky tool by brk
http://forum.xda-developers.com/showthread.php?t=1688447&page=1
This made my life easier (I thought) . I backed up my whole device and then I tried the restore.. But no Luck!!
Then I came back again to Easy Flashed and I flashed the device with ASUS stock WW v9.1..... . .. 27..
YOU NEED PATIENCE.. I told to myself
I waited for a long time in the 15th step Formatting UDA.. I left the process and went out to the Hospital to help my Mom's Physiotherapy Classes. Came back after 1-2 hours.. and my Screen was blank!!! (Both Laptop and TF101)...
Guess which one i turned on first!! My TF101.. And there Voila... I saw the Welcome screen to choose my Language.. I was Smiling like an Angel.. Happy Cheerfull after a full day and night of hardwork..
Then i saw the command prompt to see that NVFlash was successfull..
Click to expand...
Click to collapse
Just to make sure you are safe... You have to do this after you got lucky.. Will save you from boot loops..
Get the Sudo access with any of the Custom recoverys.. Install from SD Card option and install SU. then use Terminal emulator or ADB to do the following steps.
http://justanotherdave.ca/2013/07/24/fixing-an-asus-transformer-tf101-stuck-in-recovery-boot-loop/
As with all ASDK tomfoolery, start the adb server
adb start-server
Check to make sure the device shows up
adb devices
Start the required remote shell session
adb shell
Run the follow magic command to make everything happy again
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
And then reboot the device.
reboot
Sorry if this may look like a long post, but i just tried to list all of the details, I really appreciate any help here
- It all started with the latest 9.2.1.24 OTA update, I went through the updates just fine, restarted and back in business.
- Been busy for few days, and didnt touch my tablet, it went out of charge, after recharging it, It started the reboot loop, it powers up , shows the Nvidia logo, then the ASUS logo with the spinning circle for 2 seconds or so then reboot again, ..
- When i lost hope I went into the cold reboot menu and chosen "Wipe All data" , the droid with the rotating cube came up and the loading bar is active under it, i thought it may take a while so i left it "OVER NIGHT" to find it the next morning in the same screen and very hot, restarting it would return to that same droid screen
- My final attempt was using nvflash , and flashed the stock blob.SOS , blob.SOS, blob.LNX, blob.APP (unpacked from asus stock US_epad-user-9.2.1.24.zip file)
- Now it's powering up then get stuck in the ASUS logo screen with the spinning circles (which are actually spinning), and sometime being on this screen it reboots on its won
Notes:
- It's a B90
- It was never rooted, and always updated with ASUS stock OTA updates.
- I didnt face such problem with the previous ICS updates
- I must have tried cold reboot like 6 or 7 times, left it to go out of charge and recharged it again, still the same.
Allways worked for me
ramy_Maia said:
Sorry if this may look like a long post, but i just tried to list all of the details, I really appreciate any help here
- It all started with the latest 9.2.1.24 OTA update, I went through the updates just fine, restarted and back in business.
- Been busy for few days, and didnt touch my tablet, it went out of charge, after recharging it, It started the reboot loop, it powers up , shows the Nvidia logo, then the ASUS logo with the spinning circle for 2 seconds or so then reboot again, ..
- When i lost hope I went into the cold reboot menu and chosen "Wipe All data" , the droid with the rotating cube came up and the loading bar is active under it, i thought it may take a while so i left it "OVER NIGHT" to find it the next morning in the same screen and very hot, restarting it would return to that same droid screen
- My final attempt was using nvflash , and flashed the stock blob.SOS , blob.SOS, blob.LNX, blob.APP (unpacked from asus stock US_epad-user-9.2.1.24.zip file)
- Now it's powering up then get stuck in the ASUS logo screen with the spinning circles (which are actually spinning), and sometime being on this screen it reboots on its won
Notes:
- It's a B90
- It was never rooted, and always updated with ASUS stock OTA updates.
- I didnt face such problem with the previous ICS updates
- I must have tried cold reboot like 6 or 7 times, left it to go out of charge and recharged it again, still the same.
Click to expand...
Click to collapse
1) http://forum.xda-developers.com/showthread.php?t=1622628 (method 2/3)
2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)
Try NvFlash for windows, it's easier and *will* work. Boot into APX mode with power+volume up. Flash the firmware.
So after it started bootlooping, it never went back into any rom?
I'm surprised that nvflash didn't work, but perhaps the bootloader isn't compatible. The nvflash part seems like a classic symptom of bad bootloader mojo. Be sure to flash the appropriate bootloader/EBT, as in, the one that came packaged up with the stock .24 rom. Update the bootloader - depending on your nvflash version it will be bootloader.bin or specified in the flash.cfg file.
sent from my transformer
Thing O Doom said:
Try NvFlash for windows, it's easier and *will* work. Boot into APX mode with power+volume up. Flash the firmware.
Click to expand...
Click to collapse
Thanks for pointing this out, I was trying the linux version.
So .. I just used your new Windows version .. It looks like it flashed just ok ! I used stock blob.* files (I used stock .24 blob file)
Code:
D:\My Folders\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl boot
oader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299506994287477335
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct -
configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
after rebooting it's stuck at the same ASUS logo screen with the spinning circles (not in a rebooting loop, it's just spinning there for ages)
ftlast Laura,
gee one said:
So after it started bootlooping, it never went back into any rom?
Click to expand...
Click to collapse
No it kept restarting over and over
gee one said:
Update the bootloader - depending on your nvflash version it will be bootloader.bin or specified in the flash.cfg file.
Click to expand...
Click to collapse
It's the Wheelie package , i am not sure what's the bootloader version coming with it
ramy_Maia said:
Thanks for pointing this out, I was trying the linux version.
So .. I just used your new Windows version
Click to expand...
Click to collapse
Please no credit to me, I'm not part of androidroot.mobi and did no work on this. All credit to them :3
--
Anyway
That's unheard of for it still not to work, try reflashing each partition individually, and make sure all of your parts start witn MSM - RADIO UPDATE.
EDIT: I attached a bootloader EBT blob that I know works, remove the fileexts and you should be good. blob.ebt.asus is the one you want. the other blob has my changed bootlogo lol.
Thing O Doom said:
Please no credit to me, I'm not part of androidroot.mobi and did no work on this. All credit to them :3
Click to expand...
Click to collapse
Still thanks for making it in one package
Thing O Doom said:
make sure all of your parts start witn MSM - RADIO UPDATE.
Click to expand...
Click to collapse
Which parts exactly ? the blob.* files "these are binaries"
I am planning to do it manually using commands similar to the Linux ones ... are these correct ?
Code:
Starting the NVFlash mode manually with this command
D:\My Folders\Desktop\wheelie>wheelie.exe -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Flash separate blob.* files
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 4 blob.EBT
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 5 blob.SOS
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 6 blob.LNX
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 9 blob.APP
Use the get-partition table command to verify those numbers are correct. (Idk off the top of my head)
Open the blob with a hex editor and there's some intelligible text in there (along with a whole lot of gibberish code too xD)
The one I attached should be fine.
Thing O Doom said:
Open the blob with a hex editor and there's some intelligible text in there.
Click to expand...
Click to collapse
The blob file in extracted from ASUS zip has the MSM - RADIO UPDATE. string ... But the blob.* files generated by blobunpack does NOT have them
Thing O Doom said:
I attached a bootloader EBT blob that I know works
Click to expand...
Click to collapse
I get this error with your file
Code:
D:\My Folders\Desktop\wheelie>wheelie.exe -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299506994287477335
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Code:
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
| 1454788/1454788 bytes sent
blob.EBT sent successfully
[COLOR="Red"][B]bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: flags: 0
command failure: bootloader error[/B][/COLOR]
I take this back, i get the error with the manual flash. I restarted and ran the script reflash_sbkv2.bat, and it reflashed ok without errors
But again stuck at the ASUS logo screen
Now i am starting to think the problem is not with the bootloader but rather the other blob.* files which dont have the "MSM - RADIO UPDATE" in them.
if they don't, then that's the inherent problem right there.
I downloaded other blob files from here
http://forum.xda-developers.com/showthread.php?t=1683311
both the .21 and .24 blob.* files do NOT have that MSM... string at the beginning.
Any idea where i can download valid files ?
Idk, and those should work. I'm atm totally ???
Try blobtools, boottools. To make your own from a stock one.
The individual blob parts, such as blob.SOS and blob.LNX are packed android images and should start with ANDROID!. These pieces are packed up into a blob, which starts with MSM Radio Update and a bunch of header information.
You can use nvlfash to flash the blob parts to individual partitions or you can use the staging partition to flash the whole blob, which will then flash the individual parts to their various partitions, specified when the blob was packed (EBT/SOS/etc.) and the partition table (from the flash.cfg file that was used when the tablet was nvflashed with the --create flag).
Be careful!
EDIT: Not all the blob parts will have the ANDROID! header- I think only SOS and LNX will have them. APP will be an ext4 filesystem. EBT will be a binary file.
Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x37c708542bff297
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!