Database Info

[HELP] Gone into rebooting loop then .. Wont boot !!!

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.

Nvflash partition download failed on TF101

Hello,
I used wheelie and nvflash to read my 14GB partition. Then I made a small change and is now trying to write it back.
Except it stops 1.5GB into the process.
./nvflash -r --download 15 /zebra/tf101.ext4 Nvflash started
[resume mode]
sending file: /zebra/tf101.ext4
/ 1487405056/14372306944 bytes sentdata send failed NvError 0x8
command failure: partition download failed ​
Is there a way to get nvflash to continue a download that failed ?

nroets said:
Hello,
I used wheelie and nvflash to read my 14GB partition. Then I made a small change and is now trying to write it back.
Except it stops 1.5GB into the process.
./nvflash -r --download 15 /zebra/tf101.ext4 Nvflash started
[resume mode]
sending file: /zebra/tf101.ext4
/ 1487405056/14372306944 bytes sentdata send failed NvError 0x8
command failure: partition download failed ​
Is there a way to get nvflash to continue a download that failed ?
Click to expand...
Click to collapse
A limitation of nvflash is that you cannot write partitions over 4GB back to the device. the only way to do this would be to put the partition on a microsd and dd it back into place from recovery via adb

I have this problem too. I would like to try lilstevie's advise in the next few days, i will go back here to share what's happing.
EDITE 1: found a solution here

[solved] Help with NVflash? Reflash failing

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!

[Q] NVFLASH after restore seems tablet is bricked

While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?

orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin

rigidsh said:
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin
Click to expand...
Click to collapse
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.

Looking for some help on this...
Hi!
So you got the TF300T into APX mode and ran these commands?:
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
...Did you have the files on your PC or on the tablet themselves? Also, how do you get the twrp-ICS.img? I've got the openrecovery-twrp-2.2.2.0-tf300t-ICS.blob file. Do I change it to twrp-ICS.img somehow?
Sorry if this seems like a dumb question. I want to get back to ICS bootloader from JB but finding instructions has been kind of tough. Your post is the first I've found that helps!
Thanks!
-Rob
orion42 said:
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.
Click to expand...
Click to collapse

First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.

THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
orion42 said:
First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named)
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.
Click to expand...
Click to collapse

robcomet1 said:
THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
Click to expand...
Click to collapse
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817

Will do! Still haven't had a chance to do it yet. Will let you know.
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse

Finally got a chance to do this to my pad and it worked great! Thanks again for the help my friend! I'm back on CM10 as we speak! :victory:
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse

orion42
As you said information about restore with NVFlash is sparse. Could you create a thread with the proper information that others can follow to recover their units? I don't have NVFlash but have seen numerous threads where people needed help as you provide.
Thanks!

orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.

rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
I can't believe you posted that! Have you by chance seen how many bricks there have been on nvflash due to lack of info?
Your guide is good for creating files but no mention of how to use them. Everyone doesn't have your knowledge and insight.
Maybe it is time to reveal the secrets of nvflash. It could be a good thing but as it stands it is a brick maker due to lack of knowledge and help.

rayman said:
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM

uumeshh said:
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM
Click to expand...
Click to collapse
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
http://forum.xda-developers.com/showthread.php?t=2012033

rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Yes, of course, how mindless of me not to know those commands but now I can run them. But wait, I just remembered, I already successfully downgraded to ICS 2 months ago using the mindless method. Incidentally, I never said it was a good idea but rather it was the only idea someone as mindless as me could come up with. How could it possibly have worked? I just got lucky I guess.

tobdaryl said:
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
UI for blobtools - http://forum.xda-developers.com/showthread.php?t=2012033
Click to expand...
Click to collapse
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?

uumeshh said:
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?
Click to expand...
Click to collapse
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.

tobdaryl said:
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.
Click to expand...
Click to collapse
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !

hunterr986 said:
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !
Click to expand...
Click to collapse
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.

tobdaryl said:
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.
Click to expand...
Click to collapse
Thank you for your reply.
I have a TF300T !
Unfortunately i do not have the blob.bin . I did not create it while unlocking my device.
So after unlocking my device my friend tried to flash a rom buring which he wiped out everything, flashed and rebooted. After which it got stuck in an infinite bootloop at Asus Logo.
I can get into APX mode so i did a lot of research and realized that i dont have the blob.bin !
so i am trying every possible tutorial before declaring it as bricked.
Is there a way i can unbrick it ? The main problem is that it doesnt have fastboot or adb access.
PS: I came across a petition on the internet asking asus for giving access n all ... I am assuming its for letting people like me without blob.bin to unbrick theor devices ! Am i right ?

[GUIDE][BRICKED] [BOOTS ONLY TO RECOVERY][All ASUS TRANFORMERS]

This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ...

Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog

Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME

@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...

LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
Fixed let me know if you see anymore ..
Thx @LetMeKnow

LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
I am going to get to this once you have fastboot back and you can boot with hardware buttons then its just like @Buster99's
guide but there is one very important command that he leaves out ..
I will post the rest of the guide after bit ...
Thx Josh

Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770

_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx _that I did update the OP with the correct bootit.ko ...

lj50036 said:
Thx _that I did update the OP with the correct bootit.ko ...
Click to expand...
Click to collapse
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...

I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..

lvrijn said:
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
Click to expand...
Click to collapse
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.

berndblb said:
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
Click to expand...
Click to collapse
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !

lvrijn said:
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
Click to expand...
Click to collapse
Great to see you up and running...:good:
I did add a Troubleshooting post number 3
The Josh

berndblb said:
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
Click to expand...
Click to collapse
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
The bootit.ko module comes from the source of the kernel code..
Also the /misc partition is a full partition as shown here ..
Code:
mmcblk0p3
Offset: 1292369920 (0x4d080000)
Size: 2097152 (0x200000)
File system size: 512 * 4096 = 2097152 (fully occupies partition)
Linux rev 1.0 ext3 filesystem
Not mounted
Permissions: GID system can manipulate
Contains: Empty file system
Purpose: Recovery /misc
Referenced by: /system/lib/libandroid_runtime.so recovery ramdisk: /etc/recovery.fstab
Note: File system is referenced in recovery as emmc, not ext3!
Thx Josh

lj50036 said:
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
Click to expand...
Click to collapse
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.

_that said:
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
Click to expand...
Click to collapse
Nothing like _that to put you in your place....

lj50036 said:
Nothing like _that to put you in your place....
Click to expand...
Click to collapse
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!

awilson77584 said:
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
Click to expand...
Click to collapse
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:

LetMeKnow said:
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thx!

Back up and running! Thanks!!!