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

Have NO Recovery

Hi all !
Two weeks ago I somehow lost my recovery...
I had CWM 6.0.2.1 and decided to flash compatible TWRP zip 2.6.3.0 and switch recovery. I think i forgot to wipe something. It did flash it, but not successfully. When I tried to enter the recovery it stucked in "searching RCK" and didn't enter the costume recovery. I rebooted it and it get stucked on the ASUS screen. So now I have 2 options:
(The tablet is off)
1. Turning on- holding POWER- stucked on ASUS boot screen.
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing- I have two options:
2b.a. cold boot - boots normally to the ROM (CM10)
2b.a. wipe data - haven't tried it, but i belive it will wipe my data XD
I've tried PERI and 1ClickTransformerRoot - no results...
In my opinion, the main problem is that the tablet can't reboot normally...
I need your help, I'll apritiate it a lot !
Sent from my SL101 using xda app-developers app

Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.

frederuco said:
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.

sidneyk said:
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
Click to expand...
Click to collapse
Thanks a lot ! It now boots normally !
frederuco said:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I've tried it before and now - didn't worked for me...
Can I try a similar method with CWM ? :fingers-crossed:
Btw. you two are great !

You can do the same with a CWM blob file.
Also, if you have a TF101 (non 3G) you can boot to APX and install using NVFlash (EasyFlasher).
See here for details on how to use EasyFlasher: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Yeah, we know!

DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Should understatements really be allowed? :laugh:

@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?

FIXED
Goggle81 said:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
Click to expand...
Click to collapse
I did what frederuco suggested, just with CWM:
http://forum.xda-developers.com/showthread.php?t=1855686&highlight=cwm
frederuco said:
Download the CWM you want to use.
Unzip so you have the CWM.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/CWM.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
And my slider booted normally :victory:
Good luck mate ! I hope it will work for you :fingers-crossed:

Didn't work for me. Will check it again.
Thanks mate!
Edit: sadly I didn't find the time to do it until know.
Thanks at all! Got recovery back. Now I will flash 4.4.2

I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty

Mirabeau78 said:
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Click to expand...
Click to collapse
Have you tried cold boot?
Read through the OP in order to cold boot into ROM:
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
Click to expand...
Click to collapse
If it worked, download Android Terminal Emulator and type in:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots.
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ su
# dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
# reboot
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery and install KatKiss :highfive:
Big TNX to @frederuco and @sidneyk , if it woks thank them before you thank me, it is their instructions above

2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
in my case
2a. it does enter recovery cwm, but cant format and it doesnt see the sd card - cant mount it.
2b. press nothing
2b.a cold boot - doesnt boot normally. it stays on the asus logo page and the bubbles rotates
therefore i dont know where could i install that terminal

is my situation helpless? (

Mirabeau78 said:
is my situation helpless? (
Click to expand...
Click to collapse
While in recovery, are you able to connect to a PC and get adb access from a CMD prompt if in Windows or a terminal if in linux?
Sent from my SM-N900T using XDA Premium HD app

i have windows and i tried using 1click and it cant find the device. old adb base or something even if is completly updated

I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!

Jeretista said:
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Click to expand...
Click to collapse
Rommanager = not good for Asus tf101. Also, you don't need any app for installing twrp. If you have a working, up to date recovery, you should be able to flash the twrp zip directly from recovery. I recommend my builds of twrp, of course.
Sent from my Transformer TF101 using XDA Premium HD app

NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.

Jeretista said:
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Click to expand...
Click to collapse
Congratulations. Way to stick with it!

[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] Running TWRP on top of CWM with Aroma Installer??

Some of you may be wondering by the title of my thread, "Why in the world would you want to do that? Just install TWRP completely!"
The simple answer to that; I simply can't. I am unable to overwrite my recovery using goo manager/recovery flashes/terminal emulator, etc. And now you must be thinking. "Well just reset your tablet using NVFlash or the ADB Toolkit!" But alas, I just cannot for the one reason that has killed me for the past two years:
No computer will detect my Transformer.
That's right, plugging up my tablet to a computer via USB cable does nothing at all. And no, it is not my USB cable, because I have tried multiple. All I have ever wanted to do was upgrade from Android 4.1, but I cannot, because my current CWM image doesn't fully support it. So this brings us to my first question: Is it possible to run another recovery on top of my current one, just so I can flash a kitkat ROM? Is this even possible? Will it prove ineffective because it's running on top of the incompatible CWM anyway? Any and all answers will be appreaciated. I really wish I could simply use an easy Flash tool, but I just happen to be hated by all devices. Any fix to my recovery issue or my NVFlash/USB cable issue will be GREATLY appreciated! Thank you for your time

What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?

doppelhelix said:
What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?
Click to expand...
Click to collapse
I'm running clockworkmod touch (version 5.something) I don't get any progress bar after flashing a new recovery.zip
if I flash a new recovery.zip, it goes through successfully, but it never actually flashes. I can reboot into android via the "cold-boot" method (booting normally takes me to recovery). I don't know about the su command. I'll get back to you on that.
Edit: u0 [email protected]:/ # is what I get, so no root user. Just u0 with the root pound sign after. That's the only change

creed10 said:
That's the only change
Click to expand...
Click to collapse
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.

doppelhelix said:
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.
Click to expand...
Click to collapse
I followed everything step by step, and it all went just how you described! After nearly two years of having a screwed up tablet, you sir, have helped me resurrect it! I see a donation coming around!

Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru

doppelhelix said:
Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru
Click to expand...
Click to collapse
Sounds great! I will be forever in your debt, kind sir

TF300 boot loop, twrp, no fastboot

Hi druids of android,
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I've updated CM via OTA to the latest available snapshot and after that I've done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can't do any fastboot command to flash recovery or system.
Any fastboot call ends with 'waiting for device'. I call it through sudo and I've configured udev according to wiki.cyanogenmod.org/w/UDEV
I've tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I've found /cache/recovery/recovery.log file. (can't attach whole file because I'm a fresh member)
Partitions were mounted and the loop begins after:
Code:
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
I:Boot command: boot-recovery
I'm fighting with it a few evenings and I decided to ask You for help.

I have the exact same problem. Happened last night after the Wipe Data option.
I have since read that that is a horrible thing to do.
I did try this - http://forum.xda-developers.com/showthread.php?p=63269550&nocache=1#post63269550
But I am unable to get to the fastboot screen still after dd-ing. The data partition dd took hours and hours. Left it overnight.
Help would be appreciated.

SOLVED!
Got TWRP working again!!
Follow this post right under the post of which link is above!
http://forum.xda-developers.com/showpost.php?p=64591975&postcount=88
I was unable to get the adb shell commands working separately after going into #.
So I just put in
Code:
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1"
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1"
This should fix it!

Hello guys.Finally i found solve for my TF300T loop on TEAMWIN logo.I read many threads in XDA forum for this problem but nothing happens .I had no fastboot with adb ,no recovery menu with adb and combinaiton keys until get this command "adb shell recovery --wipe_data" found.First you must install naked drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2139767.Then plug usb tablet to pc(windows) and open cmd and enter the command "adb shell recovery --wipe_data"and press enter.
Sorry for my english

Gonna try this tonight. Did the same thing to my tablet yesterday. I am running the latest TWRP(Kang) and Katkiss MM 6.0.1 ver 24 Did a wipe of the cache and dalvik as I was having some issues. It then started random rebooting into Android. So I went into bootloader screen and tried to start recovery and accidently hit wipe data and got the boot loop. Now it just boots and reboots about 3 times and shuts down. I will try the naked drivers and your commands.

To point out ,that before i found solution fo my tablet,i had no fastbout wih comb-keys .My loop was only on the TWRP LOGO and never restarting or closing alone,until to press power button for 20s about to restart tablet or press reset button + power button for 20s to shut down tablet.I hope find solution and sorry fot my english again.
Thanks to tobdaryl member