Database Info

[Q] Transformer TF101G unable to boot to recovery.

Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.

PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.

PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.

dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?

PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?

recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60

mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!

Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.

hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80

baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?

Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?

I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?

Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)​/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.

Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?

Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.

Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again

You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!

Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again

Yep. Mine was also barked after I upgraded CWM from ROM-Manager.

mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery

[Q] Custom recovery fails to load on TF700

First, thanks to anyone in advance who can help me get TWRP on my TF700. Some info:
ROM: Asus stock build JR003C.US_epad-10.4.4.25-20121228 (4.1.1, rooted)
Bootloader: US_epad-10.4.4.25-20121228 (unlocked)
Since I am rooted and unlocked, I took the simple approach of installing GooManager. In GooManager I used the Install OpenRecoveryScript menu item. GooManager downloaded and flashed openrecovery-twrp-2.5.0.0-tf700t.blob.
I then rebooted into recovery from GooManager. TWRP does not load. Instead, I get a picture of the android robot lying on its back with a red triangle and "!".
I tried repeating the above twice just to make sure and the behavior was the same.
So instead of GooManager I tried installing TWRP via fastboot. Holding down power and volume- together I booted into the bootloader selection menu and selected fastboot mode. I have all the ADT tools installed. I installed openrecovery-twrp-2.5.0.0-tf700t.blob using fastboot:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf700t.blob
fastboot succeed writing the recovery. However, when I reboot and select RCK from the bootloader I still get the red triangle screen.
I've repeated flashing TWRP via fastboot several times with the same results.
I must be missing something simple. Thanks in advance for your help.

http://forum.xda-developers.com/showthread.php?t=1833212
[How-To] All-In-One Guide For Asus Infinity (TF700) [25/03/2013]
Sent from my EVO using xda premium

lmaugustin said:
I must be missing something simple. Thanks in advance for your help.
Click to expand...
Click to collapse
What you did doesn't look wrong. Are you sure your bootloader is unlocked?
You could also try the third way to install TWRP, via the staging partition: Move the blob to the device and run these commands in an adb shell:
su
dd if=/sdcard/openrecovery-twrp-2.5.0.0-tf700t.blob of=/dev/block/mmcblk0p4
Then reboot. The bootloader should show a blue (slightly broken) progress bar when it copies the recovery from the staging partition to the recovery partition.

_that said:
What you did doesn't look wrong. Are you sure your bootloader is unlocked?
You could also try the third way to install TWRP, via the staging partition: Move the blob to the device and run these commands in an adb shell:
su
dd if=/sdcard/openrecovery-twrp-2.5.0.0-tf700t.blob of=/dev/block/mmcblk0p4
Then reboot. The bootloader should show a blue (slightly broken) progress bar when it copies the recovery from the staging partition to the recovery partition.
Click to expand...
Click to collapse
Thank you. This wasn't the problem, but prompting me to go into a shell and poke around a bit did solve my problem.
I noticed the number of bytes written on the dd looked odd, so I checked the md5sum. It was a corrupt twrp download.
I downloaded the TWRP image file again, verified the md5sum, flashed it, and it worked.
My apologies for bothering everyone with the thread.

[Q] Unable to boot out of TWRP

I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.
Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.
I can provide any other info necessary, but I have no idea what further to do with it.

greymonk said:
I was attempting to install a ROM on my Transformer TF300T and I've apparently done something severe to it.
Right now I have TWRP 2.6.3.0 on it. I've apparently broken the /data, /cache, and internal storage, they're all unable to mount now. I cannot user the PWR and VOL DOWN buttons to get to fastboot anymore, it just ignores the fact that i'm holding those buttons down and only boots into TWRP. I can't choose the ADB Sideload option in TWP, it fails because of the broken partitions. I am able to connect to it in adb from my desktop, and I can push files to it, but I haven't been able to find anything that lets me fix the partitions or fastboot.
I can provide any other info necessary, but I have no idea what further to do with it.
Click to expand...
Click to collapse
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.

cmendonc2 said:
Try using fastboot as soon as the Tablet boots into the loading screen of TWRP. That worked for some people.
Click to expand...
Click to collapse
I tried this, fastboot doesn't seem to see it.
I also tried pushing an earlier blob of TWRP, 2.5, just to see if the if it would do that much. It doesn't seem to work. It still has 2.6.3.0 installed, even though it looked like it was responding properly.
Code:
C:\android_sdk\sdk\platform-tools>adb shell
~ # ←[6ndd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12896+1 records in
12896+1 records out
6602856 bytes (6.3MB) copied, 0.091592 seconds, 68.8MB/s
~ # ←[6n
It also has the weird ~ # ←[6n as a prompt in the adb shell.

Type adb reboot bootloader
Sent from my GS3 on Carbon KK using Tapatalk 4

ebildude123 said:
Type adb reboot bootloader
Click to expand...
Click to collapse
That worked. I just need to, presumably, rebuild the /data and /cache partitions, I assume?

Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.

greymonk said:
Well, I think I've completely killed it now. I think I had originally put the wrong TWRP onto it. I tried pushing the correct one to it with fastboot, and now it will either 1) do an infinite boot loop, or 2) boot to the fastboot screen but 'fastboot devices' does not see it. I can't see what else I can do with it at this point.
Click to expand...
Click to collapse
Shoot me an email at [email protected] we can continue there... Thx lj

lj50036 said:
Shoot me an email at [email protected] we can continue there... Thx lj
Click to expand...
Click to collapse
Dude, thanks again. I really can't thank you enough for resurrecting this thing. :victory:

[Q] error entering recovery ! triangle

I am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks

Grem135 said:
I am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks
Click to expand...
Click to collapse
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.

cmendonc2 said:
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.
Click to expand...
Click to collapse
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?

Grem135 said:
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?
Click to expand...
Click to collapse
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.

cmendonc2 said:
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.
Click to expand...
Click to collapse
Thanks for the help. I finally can boot into recovery. It took a bit to realize sdcard meant internal memory not the microsd like on my phone.
Thanks button hit. :good:

[Q] Stuck at twrp

Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!

nicklefloss said:
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
Click to expand...
Click to collapse
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

jsho31 said:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Thanks but that doesnt work because my phone doesnt register on ubuntu

nicklefloss said:
Thanks but that doesnt work because my phone doesnt register on ubuntu
Click to expand...
Click to collapse
you use the terminal command via TWRP, not your lcomputer