Database Info

Recovery problems

I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.

xxwckdxx said:
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
Click to expand...
Click to collapse
how long has it sat there? sometimes you have to give it a few minutes after going thru all that.

By the way if i dont try to boot into recovery it loads fine how can i reload the reocvery?

Probably 5 minutes and no go

How were you loading it in the first place? Have you checked to see if its on your card? When pushing the image, are you using the exact image name, i.e, v1.6.2-(color).img.? Also, are you holding the end-home keys at the same time long enough to see it come up?

when i first was trying i opened the terminal i had on the phone and typed flash_image recovery /sdcard/recovery-1.6.2.img and it kept comming up with bad filename(wwhich i had renamed the file to that so i dont know why) then i put it in the tools folder and tried the same from commander and it got me to here ;\

What method are you using? Try amon ras or the method used to push it to your card thru root.

havent heard of amon ras.....i just pushed it to the sdcard again and tried the same command and end up with the same thing iam trying to unroot again

nope came up with bootloader error for the unroot

tried using kitchen to reroot but it comes up with errors

Okay, these are Amon RAs methods just depending on what your using:
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.imgvia fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Or thru adb try this:
cd C:\android-sdk-windows\tools
adb shell
adb push recovery-RA-heroc-v<name>/sdcard
adb shell reboot
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.

to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it

VoLoDaR1 said:
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
Click to expand...
Click to collapse
I had 1.2.3 or whatever it was thats why i was gonna just shoot to 1.6.2 i had done it before but i dont know what happened this time. I tried the way thru adb and it has been sitting so far 10 minutes and it is still sitting at the boot screen

The first one wont work i cant get into recovery.....the second one i get "fastboot is not recognized as a internal command"and the third is the one i have been trying....

im not sure man i had trouble flashing it also try renameing it to something simple like 1.6.2.img and go to better terminal emulator type in su enter than type in the comands to flash it
flash_image /sdcard/1.6.2.img enter
do not enter mount-a before this this was the problem i was having after you hit enter just type in reboot recovery and you should have 1.6.2 also maKE sure this file is the only file on your sd card that helps good luck man let me know what happens

yeah i renamed it to recovery-1.6.2.img and i just downloaded better terminal but how do you get the keyboard up?

just tap the screen

do you have g talk

sent pm to you

ieatstarz1 said:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
Click to expand...
Click to collapse
This is what worked for me.
The 1.6.2 version did exactly to me like it is doing to you. I couldn't boot in to the recovery screen.
Sooo. I pushed the 1.5.2 image to the sdcard and then I
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
I was then able to boot into the 1.5.2 recovery
I then pushed the 1.6.2 image again and then it worked.

Recovery Problem.

I have problem with CWM v5.8.3.4, while i flash, restore, back, everything it still back to recovery mode, can`t do nothing.

CWM v5.8.3.4 -- Here is your problem, you used ROM manager to update recovery. There are red flags on this pretty much everywhere Dx
You've gotten into the bootloop, see my PERI tool (Link in sig) and try and run the bootloop-fix there, if you can get adb working. You can also try it manually (Again, adb permitting) in roach2010's recovery touch thread, he provides the fix there.
If you can't get adb working at all, you need to NvFlash back to stock, wheelie thread is again in my signature.
Good luck.
--
By the way, you can get back into Android by Cold-booting the system. Hold volume-down, then press power and keep holding volume-down till it boots. Don't press volume-up or anything else, that'll put you back into recovery.

I was tryin` but while i want to flash someting apx turning off and can`t do nothing :/ Erm, how to fix can`t use my tablet about 1 month

Hi,
have you tried coldbooting ?
Hold power and volume down. Should get you out of recovery.

Yes, i do mate, and can`t do nothing. It dont see sd card and tablet memory :/

Okay I have the same problem, i used the cursed Rom Manager and now im stuck in the endless boot cycle, I can cold boot and I have tried to flash roachs cwm but nothing. Ive read where roach gives a code that might fix it, but i have no ideal what to do with that code or how to use it, and i see where thing o doom said the fix is in his signature but im not having much luck with that either. If you could maybe explain to me how im supposed to use roaches code or post the link that explains it here, I would sure appreciate it. Thank you.
Sent from my Transformer TF101 using XDA Premium HD app

Any ideas please? :/

Start an adb shell session with your computer connected, or in a terminal app on your tf, then run roaches fix (type it in) to the terminal app/adb shell session.

"then run roaches fix" u mean write app/adb shell session ?
And now i got another problem:
"E: Can`t mount /sdcard/
Biggest problem for now, i can`t turn on debuging :/

okay I opened terminal emulator on my tablet and typed in roaches fix exactly like it says
adb shell dd if=/dev/block/mmcblk0p3
and this popped up
*daemon not running. starting it now on port 5038*
*daemon started successfully*
error: device not found
255 [email protected]:/ $
what am i doing wrong? thank you so much for your continued help
Ive also tryed the peri and easy recovery with no luck, I think my bigest problem is i dont understand the adb thing, ive tryed searching about it and im lost.

That's the wrong dd command, dd consists of an if=/ then an of=/
Try this.
adb kill-server
adb start-server
adb devices
(you should see the tf, if not, bad drivers/not working connection, fix that first)
adb shell
su (Grant superuser permissions, if you can, and you'll see a # sign)
dd if=/dev/zero of=/dev/block/mmcblk0p3
reboot
Then flash a new recovery by:
Download and extract recoveryblob from recovery.zip
adb kill-server
adb start-server
adb devices
adb push C:\path\to\recoveryblob /sdcard/
adb shell
su (you'll get # sign again)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot

I have to thank you for your patience and continued help with my problem, but with that being said I must inform you that I am still completely lost. Im not a developer and I would not even consider myself remotely knowledgeable in the subject. I was just wanting a nice custom ROM and I had found one with cyanogen mod 9 but I messed up by using the Rom manager and now I'm screwed.
I can cold boot into my tablet, and on my tablet I have this computer emulator program, which i can type in the codes you mentioned, but I'm pretty sure that is not correct. what i need is a program like that on my computer, so far I found this link regarding adb, but I'm not sure if it is right direction.....
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
if this is the wrong direction, can you please point me in the right direction? again I am sorry for my ignorance and when this is all done I will be sure to buy you a freaking case of beer. Thank you

You can run the adb commands on your TF using the emulator app, but you'll need to directly download the recoveryblob used to flash.
Open terminal and run roach's fix (except instead of typing adb shell, you just start from su, then run the dd command from there, since you're already in the tf's 'shell')
so
su
dd if of etc
reboot
Then you'll need to reflash a recovery, so download Team Rouge's Recovery.zip then use ES file explorer app (download that) to extract the file called 'recoveryblob'. Take that file called 'recoveryblob' then copy it out of the downloads folder (still using ES file explorer) hit the favorites button then hit /sdcard/ (You don't need a microSD card to do this, /sdcard/ [For whatever reason ..] is the Internal storage. [/removable/microSD/ is the external]) then paste the recoveryblob right in /sdcard/.
Open up the terminal emulator and run
su
dd if=/sdcard/recoveryblob/ of=/dev/block/mmcblk0p4
reboot
That should give you recovery! (Then you can reflash a ROM or do whatever you need/Enjoy not having to cold-boot everytime)
Sent from my Tf101atron9000 using XDA Premium HD

Im stuck w8ing for You at Skype: )

Thanks for your info. TF now up and running without the need to cold boot. For information, I did not use a Rom Manager to flash the rom, I used CWM to flash the Gummy Rom.

I finally got my tf101 fixed and I learned something new. I just wanted to thank Thing of Doom for all of the help he offered me and without ever asking anything in return. Thanks.....

If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere

Thing O Doom said:
If anyone wants to know, here's what I did to fix nefem's completely FOUBAR TF101g.
First I tried NvFlash, then right at the flashing stage realized it's a tf101g Sbkv3, so that was out X.x
Then I uninstalled all the drivers and reinstalled them with PERI, got ADB working through recovery.
I had him try and flash a .zip file for a new recovery so I could run Roach's fix, but for whatever reason the CWM wouldn't mount the Internal storage (mmcblk0p7 or /sdcard/) so I manually pushed the recoveryblob to /sdcard/ and it seemed to work, but when I ran dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 it couldn't mount and find it.
The next thing I tried since internal was acting funky was looking at the log, I noticed that the directory was /system/sbin so I just pushed the recovery to there, adb push recoveryblob /system/sbin, then ran the same dd command with that directory and it worked. Then I just ran roach's fix normally and rebooted, he had rouge recovery!
That was the first part, his internal was still borked for some reason and Rouge couldn't mount it.
I tried various ADB mounts and they all failed, so eventually he put a MicroSD into his phone (or something else) I placed the ARHD superswipe script and a ROM w/ Guevor's kernel on there, then since rouge reads external, superwipe was able to completely format internal storage. From there it was an easy wipe and flash. Once we got a working ROM on there, we noticed that it was still getting stuck at the Eee pad logo (He could cold-boot). So I figured that his bootloader was still messed up, so we took the latest Tf101G stock blob, used the handy Rayman's blob tools to pull out the EBT (bootloader partition) blob, then directly flashed that with dd again through adb: dd if=/sdcard/blob (Removed the EBT extension, important) of=/dev/block/mmcblk0p4
Reboot, and finally it was booting optimally!
It was a tad of trial and error (The internal storage thing really had me confuzzled) but it all got fixed up in the end.
Hope this helps someone somewhere
Click to expand...
Click to collapse
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.

datfinedude said:
I am having the same exact problem as him with the same amount of programming expertise....I was woundering if you could walk me through it personally as what you've typed above seems like it's in a different language. Thanks very much in advance.
Click to expand...
Click to collapse
Sure if you'd like.

My Skype name is Datfinedude
Sent from my Triumph using xda premium

[Q] Stuck in TWRP 2.1.1 with no Sideloader

Hi All,
I wanted to change the stock ROM on my tf700t so I downgraded to V10.6.1.14.8 from V10.6.1.14.10 installed unlocker and installed GooManager. Now when GooManager went to InstallOpenRecovery Script it got stuck on the 'download has started' screen. I looked for alternative options and found out that you could install via the ADT/SDK options using latest twrp.blob file. So I went to the twrp site and got latest blob file but rather stupidly they list the oldest at the top and the newest at the bottom?. So I ended up installing the 2.1.1 version using adb terminal via these instructions:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
Now I did this but I didn't put the Roms that I wanted into the default SD Card first and this version of TWRP doesn't support microSD or ADB Sideload. It now just keeps rebooting into TWRP and when I connect to PC in TWRP the PC just recognizes the driver as Transformer but none of the ASUS drivers work. I have no idea where to go from here, backup doesn't seem to work....?
I've been looking around but seems perhaps I've hit a unique issue.
Any help on how I can progress from here to get the latest version of TWRP or indeed any decent ROM - I was originally going for cm-10.2-20131112-NIGHTLY-tf700t.zip and googleapps.
Help would be most appreciated.
Thanks,
Kavster

also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide - cannot get boot recovery now just boots into TWRP...
android.sc/update-asus-transformer-pad-tf700t-to-cm-10-2-android-4-3-jelly-bean-rom
am I screwed..???

Kavster76 said:
also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide
Click to expand...
Click to collapse
This option causes the bootloader to force starting the recovery until the wipe is done. The problem: The ancient recovery that you flashed cannot access the eMMC due to bootloader incompatibilities.
So your only chance to unbrick now is to get adb shell access working, then try "adb reboot bootloader" and see if you can get back to the bootloader menu. Then choose Android and run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1

The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.

Kavster76 said:
The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.
Click to expand...
Click to collapse
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502

flumpster said:
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.? Can I also install new version of TWRP..??
Cheers...

Kavster76 said:
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.?
Click to expand...
Click to collapse
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974

_that said:
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?

Kavster76 said:
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?
Click to expand...
Click to collapse
I'd use fastboot to flash a proper version of TWRP now.

OK So clicking Android has taken me back to 4.2.1. Think I'll do some more reading before messing about with it again - Thanks for all your help - Much Appreciated !!!!!

Trying to get back to the latest TWRP I have renamed openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob I then put it in /sdcard root copied it over and ran the following:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12212+1 records in
12212+1 records out
6252648 bytes transferred in 3.658 secs (1709307 bytes/sec)
[email protected]:/ #
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.

Kavster76 said:
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.
Click to expand...
Click to collapse
Meaning he has to flash TWRP in fastboot not in adb shell - correct?
If yes - how is it different?

So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.605s]
writing 'recovery'...
OKAY [ 1.482s]
finished. total time: 4.087s
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Surely that should of worked..?

Kavster76 said:
So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.
Click to expand...
Click to collapse
OK Cheers (sorry wasn't sure what post you were on about), all sorted now phew...
Backing up system now and I'm ready to install latest CyanogenMod...

_that said:
run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1
Click to expand...
Click to collapse
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Thanks!

berndblb said:
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Click to expand...
Click to collapse
In theory, yes. However, when asking the bootloader for supported partitions (fastboot getvar all), "misc" is not among them, so I don't know if it really works.

Latest CyanogenMod all installed and looking good....
Thanks for all the help (I have added thanks) !!!
Kavster.

about qoute #8
hi friend.I have this problem too but my phone is samsung i9001.as you said,I downloaded the file and extracted it and then conected my phone to the pc and went to this path {start*accessories*command prompt} and entered the command "adb push bootit.ko" ,but responsed " adb is not recognised as an internal or external command, operable program or batch file" . I m too unhappy now,because my phone just boot to TWRP and like Kavster I have used TWRP 2.2.1 without adb sideload option.please help to rescue my phone.tanks dear friend

[Q] How to upgrade from CM10 Nightly

I have had this on the tablet for a while. It is very laggy and too slow to be useful. I tried to install the TWRP recovery (from CWM) and it does not take. I always come back to CWM. I tried using dd to write the TWRP recovery (copy to root of SD card, dd if=/dev/zero of=/dev/block/mmcblk0p3 then dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 (after I had extracted the twrp.blob to the sd cadr)) no luck. So, I wiped it and tried to install KattKiss. It gets stuck booting. I get the 4 dots that go round and round and the logo, but it never boots. So, I went back through the CM10 instructions (http://wiki.cyanogenmod.org/w/Install_CM_for_tf101) and I have 'joy' (definition: it boots and runs), but am wondering what is 'wrong' that I cannot load another ROM image. This is an old machine and there are a lot of meandering threads on XDA and none seem to work for me. I am not averse to 'starting over', but would like some guidance. I have rooted and rom-ed an atrix 4g, sgs2 and sgs3, but this is a bit different. I read that there is a bootloader unlocker for some tf101s, but those links are dead. I see lots of references to goo manager to assist with recoveries and such, but those links are dead as well.
Any help appreciated.
Keith

so I finally figured out how to stop it from recovery looping.
Cold booted it then 1) changed to su (sudo su), I'm running Linux 2) adbshell, 3) echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 4)
reboot and voila, it will reboot to cm10.
Code:
sudo su
adb shell
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Now to get kitkat installed. Is there anything else I am doing wrong before I try it again?
Keith

[Q] twrp failed install tf101

I have a tf101. Tried flashing the newest twrp, and it failed. Here are the details.
Current bootloader: US_epad-9.2.1.27-20120615
Flashed from this recovery: ClockworkMod Recovery v5.8.3.4
Flashed this new recovery: signed_twrp-2.8.1.1_tf101.zip
Installation was reported as successful. I rebooted into Android as instructed. After it had completely booted, I rebooted again and tried to go into recovery, but the device just sat there at the EeePad logo screen. I was able to cold boot into Android using the power-downVolume combination. Instructions on this forum at showpost.php?p=46806749&postcount=187
said to first enter a terminal and type this:su
dd if=/dev/zero of=/dev/block/mmcblk0p3
My result was: /dev/block/mmcblk0p3: write error: No space left on device
4097+0 records in
4096+0 records out
2097152 bytes transferred in 0.455 secs (4609125 bytes/sec)
In spite of the error, I went on. The page said to download twrp.blob and install like this:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
However, that link was no good (404 error).
So I went to the TeamWin Project page for this device at:
twrp2/109
They gave this link to download the latest .blob file:
twrp2/tf101
Which took me to a page listing five versions of openrecovery-twrp, the latest of which was:
openrecovery-twrp-2.3.2.3-tf101.blob
Instructions:
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
I did all this and it still have the same result. So I examined the file signed_twrp-2.8.1.1_tf101.zip and found that it contained a file called twrp.blob. I copied this to /sdcard of the device and tried the same above instructions to flash that.
This didn't work either.
I'm still stuck at the logo, unless I use the key combination to boot into Android.
My bootloader, when I press power-downVolume, gives me the option to "wipe data". I have not done this out of concern I might not be able to boot into Android afterward.
However that seems to be my only next step unless I can find some ideas here.
Somewhere in the middle of all this, I did manage to get out of the loop, and the device now boots directly into Android (I'm running a CyanogenMod v10nightly). But it reboots itself all the time-- not very stable, and I'm looking forward to installing the 4.4.4 KatKiss rom, which is what got me started trying to install twrp.
Can you guys offer any help? Thanks.

Does it reboot immediately or do you have time to open the terminal and enter
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot