TF201 in TWRP bootloop/freeze brick - Asus Transformer TF700

I was running version [ROM][N 7.1.2] [ KatKiss - Nougatella #027 ] by timduru on my TF201 for some time and today I decided to upgrade TWRP (from twrp-3.1.0-1-tf201t to twrp-3.2.3-0_KANG-tf201t).
I booted into TWRP, selected install twrp-3.2.3-0_KANG-tf201t into staging partition and then restarted.
After rebooting I ended up in TWRP bootloop.
As TF201 boots, skips fastboot and goes directly into TWRP splash screen then after several seconds without going into recovery it restarts again into TWRP splash screen.
That repeats several times until it freezes in TWRP splash screen. It never goes to recovery or boots into system anymore.
I tried to push Power and Volume Down together or Power button only it still keeps restarting into TWRP splash screen and rebooting. I tried different button combinations when I was in TWRP splash screen, Volume Down and Power restarted and I pushed immediately Volume Up, I got screen with error saying something about encryption error with the button reset. I tried to exit from there pushing Volume button but maybe I accidentally actually selected tablet reset?
During restarts or TWRP splash screen freeze I do not have access to recovery, fastboot or get any adb recognition on Windows (all drivers are installed).
My only possibility is to get into APX connected to my Windows.
Since I can still get it into APX and I have also created and stored my nvflash blobs backup long time ago should I start NvFlash recovery with generated blobs following this thread
Code:
[url]https://forum.xda-developers.com/showthread.php?t=2538028[/url]
or is there anything else I can try?
Any advice would be greatly appreciated.
Thank you all in advance!

Lucky that you have your nvflash blobs! Otherwise I would say it is a hard brick. Although why totally escapes me. A bad recovery flash should not brick it... I haven't heard of a 3.2 Kang version for the 201 though. Sure it is legit??
Anyway, no fastboot, no adb in recovery leaves you only the nvflash option. Good luck!
Post your steps if you don't mind, never saw anybody actually do a nvflash restore...
Sent from my Pixel 2 using Tapatalk

Download 'Minimal ADB and Fastboot' to a Windows 7 computer/laptop (found here): https://forum.xda-developers.com/showthread.php?t=2317790
Enter APX mode and plug your tablet into the computer/laptop and see if the TF201t shows up, fire up Minimal ADB and Fastboot and send the fastboot -i 0x0B05 reboot command to see if ADB is talking to the tablet.
Try this out, if you can flash the tablet from the PC you can wipe it and reinstall the recovery console, reboot and see if the tablet is saved. - NP
---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------
berndblb said:
Lucky that you have your nvflash blobs! Otherwise I would say it is a hard brick. Although why totally escapes me. A bad recovery flash should not brick it... I haven't heard of a 3.2 Kang version for the 201 though. Sure it is legit??
Anyway, no fastboot, no adb in recovery leaves you only the nvflash option. Good luck!
Post your steps if you don't mind, never saw anybody actually do a nvflash restore...
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
There a whole list of 'new' TWRP for the 201 here: https://androidfilehost.com/?w=files&flid=161771 any thoughts? - NP

georgecoat said:
Thank you very much for all your work and new upgrades.
I was running version 27 of this ROM successfully on my TF201 for some time and today decided to upgrade to version 34.
As a first step a decided to upgrade TWRP (from twrp-3.1.0-1-tf201t to twrp-3.2.3-0_KANG-tf201t).
I booted into TWRP, selected install twrp-3.2.3-0_KANG-tf201t into staging partition and then restart.
After rebooting I am in TWRP bootloop.
TF201 starts, goes directly into TWRP splash screen (showing the version of the recovery) then instead of going into TWRP it restarts again.
I tried to push power and Volume Down together or power only it does not react to anything, keeps restarting into TWRP splash screen and rebooting.
I would appreciate any suggestions.
Click to expand...
Click to collapse
For everybody with similar problem I am posting here how I fixed it.
I tried to push Power and Volume Down together or Power button only it does not react to anything, keeps restarting into TWRP splash screen and rebooting. When TF201 boots, skips fastboot and goes directly into TWRP but never loads TWRP and restarts or hang in TWRP splash screen.
In TWRP splash screen I do not have access to fastboot or do any adb.
I can still get it into APX and I have also created my nvflash backups long time ago and I have them available.
I was ready to start brick fix from the beggining.
But before I would get into that I tried last thing:
First I downloaded file djibe Transformer Prime pack v2 : http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
What i did first was that I had to restart Windows 10 64 bit into "Disable Driver control" othervise the driver would not install
Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Installed driver in extracted directory of "djibe Transformer Prime pack v2" pack (android_apxusb.inf).
Once driver installation is completed, reboot PC as usual.
Then I put all necessary files into nvflash folder.
Get ASUS into APX mode (Power and Volume Up, it will restart, hold it until creen is black)
I realised that old exe files are 32 bit, I had to use new nvflash exe files (from the package djibe Transformer Prime TF201 v2.zip) and replace rest with the files I had stored previously when I did blob backups. So everything I used was original folder but exe files replaced with 64-bit versions from the djibe Transformer Prime TF201 v2.zip package. In the last step I used original ASUS firmware downloaded long time go (also in the folder from the time of my blobs creation). This could be still found on ASUS page or here in the forum.
I started cmd window in nvflash folder and run this:
Code:
[B]wheelie --blob blob.bin[/B]
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787bc3ffa13
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Code:
[B]nvflash -r --download 5 twrp.blob[/B]
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
/ 8124520/8124520 bytes sent
twrp.blob sent successfully
After that I was able to get into fastboot finally!
From there I did:
Code:
[B]fastboot -i 0x0b05 flash recovery twrp_tf201t.blob[/B]
sending 'recovery' (7934 KB)...
OKAY [ 2.110s]
writing 'recovery'...
OKAY [ 2.128s]
finished. total time: 4.238s
Code:
[B]fastboot -i 0x0b05 reboot-bootloader[/B]
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.643s
Still no working...
I had to do this:
Code:
[B]fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache[/B]
Code:
[B]fastboot -i 0x0B05 flash system L:blob[/B]
(this was my path - your's may vary depending where you stored your blob)
Code:
[B]fastboot -i 0x0B05 reboot[/B]
Then I started the whole process of flashing the Hairybean bootloader (reboot), then TWRP (reboot) and then the rom 35, gapps, supersu again and I am back to normal.
Thanks : Timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber, berndblb, Nektopoli, djibe and Buster!

Hey guys... so... I am really desperate here. I tried updating my tf201 to nougat following the guide here on the forum but somewhere along the way things went terribly wrong and now the tablet is stuck in the aforementioned bootloop/freeze. I cannot get into fastboot. I can only get into ATX. I DO have my nvflash backup blobs, but even so I am unable to get the tablet from this state. I have tried like 4 different guides and approaches (including the one here, of course), but unfortunately nothing seems to work. I can't get fastboot.
Any ideas?
Things I've tried:
https://forum.xda-developers.com/t/nvflash-recovery-with-generated-blobs-tf-700-t.2538028/
commands like: nvflash -r --rawdevicewrite 0 2944 bricksafe.img (I find it strange that the command runs slowly for the first half of the upload and then it speeds up a lot... but that might be okay, I dunno)
Tried flashing back the original firmware / blob downloaded from asus.com etc. Nothingseems to work.
Please, any help will be greatly appreciated.
EDIT:
Ok. So after a good night's sleep I'm feeling a little less desperate and I can describe in more detail how I managed to get to this proper bricked state.
1) I followed https://forum.xda-developers.com/t/...me-tf201-stock-to-android-7-1-nougat.3486237/ this guide and got all the way to Step 6 (bootloader) at which my tablet started to behave a bit differently than what was described in the guide. It is also important to note, that the tablet display is a little bit damaged - just the first two lines of the display - but unfortunately, that makes reading important info, such as whether or not the device is unlocked, bootloader version etc., impossible.
2) Anyways... Halfway through step 6, just after:
Code:
The tab reboots and launches the HairyBean TWRP recovery (androwook).
My tab loaded back into android instead. So here I thought - with all my stupidity's might - "hmmm, so maybe I didn't unlock it properly" (keep in mind that due to the damaged display, I couldn't check),, and I went ahead and ran the unlock app again. That lead to the Tab's restart and here we are. When I turn on the tablet, it just shows the Asus logo for like half a second and then restarts. Shows the Asus logo again and restarts. And that way forever. Pressing power + volume- does nothing. The only thing that works is power + volume+ which starts ATX and I am able to interact with it using wheelie and nvflash.
3) At this point, I can't remember the exact order of things that I tried, but things I tried are:
Load back my nvflash blobs. I still have those. I followed this guide: https://forum.xda-developers.com/t/nvflash-recovery-with-generated-blobs-tf-700-t.2538028/
Load back stock ASUS firmware downloaded from asus.com
The steps in this thread as described by georgecoat.
At one point I think I tried following this guide: https://forum.xda-developers.com/t/...rick-recover-downgrade-upgrade-tf201.1927818/ and that I'm afraid might have been the proverbial nail in the coffin. So... you see, my nvflash files didn't match the ones described in that thread. SoI thought "hmmm, I have bootloader.ebt, so that's probably the same as his blob.EBT" so I executed
Code:
nvflash.exe -r --download 4 bootloader.EBT
And that I think got me to where I am now... It's cool how sometimes I can amaze myself with my own stupidity... and the worst part is that I'm an IT guy, I work with linux, docker, python a lot.... but android is a complete unknown for me and as I got more and more desperate I tried stupider and stupider things. Oh well...
So... any ideas? Anything goes, really. At this point I might as well use the tablet as a paperweight so really, any ideas are welcome.
Thanks in advance.

Related

[Q] TF300 block on asus logo after cm10 update

I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.
bourrin said:
I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.
Click to expand...
Click to collapse
This is the wrong cwm for your unit; it is for TF201.
This link provides help for your problem. http://forum.xda-developers.com/showthread.php?t=1680570
Look for this heading in the link posted above. - Flashed TF201 Recovery in ROM Manager?
In answer to your question, no.
Good Luck!
The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.
bourrin said:
The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.
Click to expand...
Click to collapse
Without nvflash previously installed I have not heard of anyone getting any use of apx.
My understanding you have three choices to recover your unit.
ADB, Fastboot, and recovery. In your case current recovery is out since we know it is the wrong one, that is unless you can flash the correct one.
I have read of people flashing with adb and fastboot even when the unit appeared not to respond and getting their unit restored.
So give the commands even without a response.
On most units when in cwm recovery adb works.
Also with fastboot commands try ( this example would be to flash twrp recovery )
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
then try
fastboot flash recovery twrp.blob
fastboot reboot
I know the -i 0x0B05 designates our Asus but at this stage your unit does know what it is and may be refusing based on being called Asus, so give the generic command if the normal ones don't work.
I have also read where you use the drivers from tf201 for adb and fastboot and getting their unit to respond. http://downloadandroidrom.com/file/TransformerPrime/drivers
I believe other drivers tried after tf201 were universal naked drivers.http://forum.xda-developers.com/showthread.php?t=1766220
Here is a thread you may fine useful. http://forum.xda-developers.com/showthread.php?t=1936648
Good Luck!
With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?
bourrin said:
With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?
Click to expand...
Click to collapse
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.
tobdaryl said:
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.
Click to expand...
Click to collapse
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.
bourrin said:
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.
Click to expand...
Click to collapse
Good info, thanks. I'll do some work and be back.
Ok. I uploaded what mostly appears to match your command line.
boot.img, recovery.img, and bootloader.bin all from jb 10.4.2.17.
http://www.mediafire.com/?2cpk65c5ddyek36
If you need something more or different please tell me.
Thanks you so much.
Can you just confirm the partition number of each file , please ?
bourrin said:
Thanks you so much.
Can you just confirm the partition number of each file , please ?
Click to expand...
Click to collapse
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)
tobdaryl said:
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)
Click to expand...
Click to collapse
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?
bourrin said:
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?
Click to expand...
Click to collapse
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin​ If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.
tobdaryl said:
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin​ If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.
Click to expand...
Click to collapse
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.
bourrin said:
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.
Click to expand...
Click to collapse
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439
I had forgotten to mention something important.
As you go through trying to sort this problem don't forget to recheck adb and fastboot access. I know it sounds silly but sometimes the most minor change or another reboot will give you access that was earlier missing.
I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?
bourrin said:
I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?
Click to expand...
Click to collapse
I have see that sometimes adb reconize apx mode. Do you know what driver can I use to try this ? Now I have universal_naked_driver_0.7
SAME PROBLEM as Bourrin
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
tobdaryl said:
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439
Click to expand...
Click to collapse
dltabrvo said:
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
Click to expand...
Click to collapse
Sorry, the file expired. Here is a new link for the download. http://www.mediafire.com/?ua7krzmadu3uyc1
Good Luck!

[Q] How to downgrade to jb 10.6.1.14.8?

My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
ericsundiu said:
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
Click to expand...
Click to collapse
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
ericsundiu said:
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
Click to expand...
Click to collapse
Unlocking and rooting are two different things. There is no known root method at this time for the 10.6.1.14.10 firmware. The Unlock Tool should still work.
I don't think it's a question which firmware you have - sometimes it works like a charm and other users cannot unlock at all due to incorrect or incomplete S/N database on Asus servers. At least I have not heard anything that people have trouble unlocking after the last update.
Just download the latest version, v8 I think, install and run it. The worst that can happen is it fails.
Do yourself a huge favor and educate yourself thoroughly before you try to flash custom software to the tablet.
There is little risk in flashing a custom rom IF you do it right. But yesterday night I tried to help someone who did it wrong and hard bricked his tablet. Read 3 times, ask twice, flash once!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot
Click to expand...
Click to collapse
For flashing via adb and the staging partition, Android must be rooted. Fastboot works without root.
I did a clean wipe of my tablet and installed 10.6.1.14.10 onto my tablet.
I have unlocked the bootloader, but when booting up I then have the default recovery and rom supplied by Asus with no root.
I tried motochopper and debugfs method, and as described above neither work, the cmd prompt windows just record failures.
Read this forum regarding what is what (fastboot, root, unlocked etc.) and why you do them
http://forum.xda-developers.com/showthread.php?t=1833212
The way I gave root to the stock rom was by loading into fastboot mode and pushing a twrp image to my tablet off CHROMI rom site. I then used that to root the system. To be honest I did not need to root as I could have just then flashed the CHROMI custom rom which comes with SU anyway....
Get fastboot into a folder and also copy the TWRP recovery img inside the fastboot folder
Attach your device to the PC
Start fastboot mode by switching off your tablet then switching on in bootloader by holding down power on and volumn down
Connect tablet to PC (need approperiate drivers)
Open cmd prompt as admininstrator and goto directory with recovery image in the fastboot folder
Type the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot (though I don't think i typed this if honest, struggling to remember)
Unplug tablet from the PC and reboot into recovery mode
If you got the image of twrp from CHROMI site which includes bootloader also, i think it includes SU, therefore just exit and close recovery and it should ask to install SU. Select yes
Reboot the device
Your device is now rooted, though think you need to run SU in the tablet to get it fully setup.
Sorry this is not 100% perfect, I will recall what I did tonight when at home in front of PC with files.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Click to expand...
Click to collapse
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
M1ster1 said:
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
Click to expand...
Click to collapse
You can try to install from your system, not stock recovery. You need to boot your system normally and look in the lower right corner at your notification. It should notify you that their is an update for you. When you click on it, it will walk you through the update process. You need to make sure that you have only one zip file in your directory which is the Asus firmware that you want to update.
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
LetMeKnow said:
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
Click to expand...
Click to collapse
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (right click on your device, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your phone.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
Good job! Congrats!
And thank you for putting this guide together. That's what I call sharing! :victory:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
It is a nice written How to do list, good job... :good:
You can add these command for fastboot to your list instead of using the power button and volume down..
> fastboot reboot-bootloader # Exit fastboot and reboot into bootloader.
> fastboot reboot # Exit fastboot and reboot to your system
Good job.. :good:
FAILED (InvalidSize)
I am attempting to install a ROM on my Transformer Infinity as it pretty much sucks these days but am a complete NOOB. Have never attempted this with any of my phones or tablets, but figure I would try since these directions are so detailed. After following most the steps you have listed, I get the error below in the command prompt. Can someone please help, I tried searching XDA and Google to no avail. If possible please be as basic and speak in layman's terms b/c all this technical jargon goes right over my head. Thank you in advance!!!
Step followed:
- Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
epps720 said:
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
Click to expand...
Click to collapse
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
epps720 said:
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
Click to expand...
Click to collapse
Actually yes.
Just read in another thread about someone having the same problem as you, getting the incorrect file size error.
Download the TWRP 2.5 blob and try it with that file. I have no idea why, but TWRP 2.6 may cause this error.
At least that bloke got the recovery installed that way. Once you have TWRP, it's easy to upgrade to the latest version.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
I have no idea why, but TWRP 2.6 may cause this error.
Click to expand...
Click to collapse
The blob for TWRP 2.6.3 is bigger than the recovery partition. 2.6.1 should work.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Ive had the same question as the OP, i also have a .10 version, i have a US sku, and i downlaoded said associating item but when I went but when i go to either do it with sd, or intewrnal sd, or how ever. through manual or through android, either method both resulted in error when trying to downgrade, i dont know if its because its a downgrade or what.
Ive some linux experience over the years, and have rooted and run custom roms in the past. im trying to achieve the same as the OP, fix my lag, and more options and tweaks.
I have the .zip of the rom i want whitch i found I liked the xcromi rom, so I downloaded it. so, i can put that in and name it what and how do i do the update than through the volume down + pwr combo into that menu? (not sure what its called) but i can't do sideloads because i can't havbe the ultity to sideload without rooting and i can't root with .10, so i have been trying to get past this single step all night and this morning now.
@M1ster1
Thanks for posting this guide. It doesn't do a perfect job however on the TF700t running Android build 10.6.1.14.10. Tried to use the "fix permissions" option in ROM Manager but failed due to insufficient permissions. I installed CWM Superuser and cleaned up the version of SuperSU (prefer Superuser anyhow)... updated the binaries and still no love when trying to correct the permissions, despite all tests showing the device fully rooted.
After a day of pulling my hair out I finally came across vRoot and after even longer found a guide in English. Ran that, again swapped out the Superuser that went with vRoot and again reinstalled Superuser. Used Ti to install as system app. After reboot ROM Manager was finally able to correct permissions and all is golden again.
Hi ,
My Transformer has 10.6.1.14.10 and I am trying to install TWRP thru fastboot as per "M1ster" instructions.
these are the results I see from my command prompt.
C:\Users\Ken>fastboot devices
015d2bbce7041e07 fastboot
C:\Users\Ken>cd c:\Android-adb
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
OKAY [ 0.066s]
writing 'recovery'...
OKAY [ 3.374s]
finished. total time: 3.441s
c:\Android-adb>
after I reboot and select RDK , i get the sick droid error,
I feel like I have missed something, hopefully somebody can point me in the right direction
Thanks
helihaole said:
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
Click to expand...
Click to collapse
Your "twrp.blob" apparently doesn't contain a recovery - it should be around 6 to 8 MB.

[Q] Bricked TF300T - ADB semi ok, no fastboot, some (strange) options left

I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)
Potential Soultion
Quote:
TheArkive said:
I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)
Click to expand...
Click to collapse
Hi there.
Buster99 kind of had the same problem, and he managed to unbrick it.
All credit goes to Buster99.
Here is his post:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
You guys rock! I'll try that as soon as i get home!!
∫εทт ƒя๑๓ ๓γ αทδя๑ïD
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Quote:
TheArkive said:
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Click to expand...
Click to collapse
Glad to have helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
hatdrc said:
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
Click to expand...
Click to collapse
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I went into fastboot and and erase recovery. Did it. Then I tried to flash recovery and again it locks up. Rebooted and it went straight to CM 10.2 Tried flashing recovery with terminal emulator. Said it was copied. Rebooted went back to CM. Rebooted again to recovery but it went back to CM. Booted to fastboot again and selected RCK. now it says
Booting Recovery kernel image
Booting failed
Unrecoverable bootloader error (0x00000000)
It does boot to CM but now I have no recovery. OmniRom was the one I wanted to flash but at this point I'm thinking im going to have to start from square one. I just don't understand why it doesn't want to flash a recovery
Thank you for your help, you are the man
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was trying to flash the most current blob from the twrp site. I get the following:
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.965s]
finished. total time: 1.965s
fastboot -i 0x0b05 flashe recovery twrp.blob
sending 'recovery' (6448 kb)...
OKAY [ 2.561s]
writing 'recovery'...
OKAY [ 2.394s]
finished. total time: 4.955s
When I erase recovery the green flashing box on the tablet keeps flashing. When I try to flash the recovery the box just stops on what ever shade of green it was on when I hit enter. Also after if I do fastboot devices I get:
???????????? fastboot
hatdrc said:
fastboot -i 0x0b05 flashe recovery twrp.blob
Click to expand...
Click to collapse
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, typo. Should have been flash.
So i unzipped the recovery.img file and placed it in my fastboot folder. I get the same results.
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (6892 KB)...
OKAY [ 2.445s]
writing 'recovery'...
OKAY [ 2.477s]
finished. total time: 4.922s
The green box stops flashing as soon as I hit enter
Could it be that my recovery partition as gotten messed up, would formatting it help you think. Guess there's only one way to find out.
EDIT: Never mind, can't format a 'basic' filesystem
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still a no go. The only recover on there was a flashable zip file. That's why I was trying to get anything on it so I could flash that. I'm at the end of my knowledge. I've always had Samsung so I got use to odin. Never had to use fastboot. I really appreciate your help. Guess its going to have to run CM10.2 and hope it doesn't have a problem
Sent from my SGH-T999 using Tapatalk
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will take a look, and I thank you for the time you have spent with me! If all else fails at least its running and usable for now.
Sent from my SGH-T999 using Tapatalk
Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Hi Buster,
I have a similar problem, but I cant reach the fastboot. I tried to reset and push volume down, connect tablet to PC with volume down pushed, turn off and start the tablet with the volume down pushed, but nothing. My recovery is corrupted, because it doesnt recognize any file in the SD. I tried to type adb reboot bootloader from the pc, but it says "erro: device not found".
Do you have any idea?
Help
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
+needle wont do anything for me cos mine boots to twrp logo and stay there for ever until battery is drained :/ hellp
It's not the exactly the same problem... For me ADB doesnt work.....
ConsoleFreak said:
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
Click to expand...
Click to collapse

[Q] [Question] CWM Installation and brick ?

Hello there,
First of all, thank you for your answer and sorry for my bad English.
I own a Asus Infinity TF700T since one year now which worked on CyanogenMod until today.
I had installed CyanogenMod 10.1 with TWRP and decided to install version 11.
In order to do so, I put CWM 6.0.4.5 in my /download folder with CyanogenMod 11 and the GApps.
I then installed CWM through TWRP (I cant remember which version though...) using VolDown + Power and selecting RCK and tried to reboot.
But it did not work.
It is stuck on the Asus logo with the "device is unlocked" message in the top-left corner of the screen.
Cant even restart with the same old VolDown + Power. If it had worked once, if then went stuck on the same Asus logo, trying to start the recovery.
For now, my TF700T is so bricked. I cant do anything with it but looking at taht fancy Asus logo.
I dont even know if CWM is installed or not since I could not boot on any recovery.
Thank you for your help.
_Daga.
Bootloader Sceen?
_Daga said:
Hello there,
First of all, thank you for your answer and sorry for my bad English.
I own a Asus Infinity TF700T since one year now which worked on CyanogenMod until today.
I had installed CyanogenMod 10.1 with TWRP and decided to install version 11.
In order to do so, I put CWM 6.0.4.5 in my /download folder with CyanogenMod 11 and the GApps.
I then installed CWM through TWRP (I cant remember which version though...) using VolDown + Power and selecting RCK and tried to reboot.
But it did not work.
It is stuck on the Asus logo with the "device is unlocked" message in the top-left corner of the screen.
Cant even restart with the same old VolDown + Power. If it had worked once, if then went stuck on the same Asus logo, trying to start the recovery.
For now, my TF700T is so bricked. I cant do anything with it but looking at taht fancy Asus logo.
I dont even know if CWM is installed or not since I could not boot on any recovery.
Thank you for your help.
_Daga.
Click to expand...
Click to collapse
Can you get to the RCK screen ?? Long hold Power + Volume down...... Dont let up on the buttons till you see the white writing in the upper right corner...
Nah, as I said, I cant boot using VolDown + Power and so cant reach the RCK screen.
:/
I did install the APX drivers and my TF700 is fully recognized in Windows.
I am now trying to fastboot through Windows in order to get this mess cleaned but it seems compromise.
Moreover, I did not previously back up my NVFlash...
It seems I'm in it, huh.
_Daga.
Anybody got an idea which can help me to bring bak to life my TF700T ?
:'(
_Daga
Reset Burton
_Daga said:
Anybody got an idea which can help me to bring bak to life my TF700T ?
:'(
_Daga
Click to expand...
Click to collapse
I have herad of some people not being able to get to there bootloader screen... There is a hole about 2 cm below your sd card push the little button in there with, i used one a my daughters ear ring studs, While trying to boot into bootloader screen....
I tried the Reset Button, but it did not work. The TF700T reboots but is still stuck on the same ASUS logo.
Same "bootloader is unlocked" on the top left corner.
Thank you for your help LJ !
_Daga
This is the ONLY solution for this problem, worked great for me.
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hey kansasboy, thank you for your help !
I cant enter in Fastboot mode, even when using the Reset button + VolDown.
All I see is my TF700T correctly detected in my Windows 8 "Devices". It is in APX.
Anyway, I'll try your trick and hope it will work.
I'll stay in touch.
_Daga
I think you have hard bricked if you can only get to APX mode and you don't have NVflash backups from your device.
Sorry
Your only choice is to replace the mother board, either from Asus or yourself.
I have the same issue.
I'm able to access the tablet through adb and run commands. Can you do that?
Haven't found a solution yet...
archonro said:
I have the same issue.
I'm able to access the tablet through adb and run commands. Can you do that?
Haven't found a solution yet...
Click to expand...
Click to collapse
You have adb but no fastboot????
Try
Code:
adb reboot bootloader
That should boot you into the bootloader and then you can try buster's method to get it back.
It was one of the first things that I tried. Unfortunately the console seems to hang.
I'll try to leave the console opened after it hangs - hopefully it will reboot at some point.
I also tried to dd the twrp blob into mmcblk0p4 but it has the same effect - it hangs.
In case anyone wants an update to what I was saying in the posts above.
I managed to dd the twrp blob into mmcblk0p4. Apparently it takes A LOT to flash it.
archonro said:
In case anyone wants an update to what I was saying in the posts above.
I managed to dd the twrp blob into mmcblk0p4. Apparently it takes A LOT to flash it.
Click to expand...
Click to collapse
A LOT of what? Tries?
Glad you got it sorted! :thumbup:
A lot of time
Hey,
Sorry for the time not answering.
I only got APX on my TF700T, in any case I could reach ADB.
For now, the tablet is in the after-sale service of my seller, here in France.
Hope they'll be able to help me.
I'll definitely stay in touch.

[Q] Power on/Reboot now goes into APX mode

Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??
lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??
lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.
wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....
lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!
wha2do said:
Good to go!
Click to expand...
Click to collapse
??????
Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!

Categories

Resources