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

Tf101 recovery problem

This just now happens. I just recently today had the problem that cmw recovery 5.8.3.4 wouldn't let me boot into my ROM ( gummy). I finally got in by cold boot. I tried flashing roach through cmw and it wouldn't stay. I just tried oneclickrecovery and adb won't reconize my tf101... my tf is a b90 and the only computers I have are a windows 7 32bit, and a new mac.... so is there a way to nvflash
Sent from my Galaxy Nexus using xda premium

Nvflash for sbkv2 windows was released, you can check that out if you like
but if you can't get adb drivers working, you may have trouble with apx drivers.. Give the universal naked drivers thread a look see.

Thing O Doom said:
Nvflash for sbkv2 windows was released, you can check that out if you like
but if you can't get adb drivers working, you may have trouble with apx drivers.. Give the universal naked drivers thread a look see.
Click to expand...
Click to collapse
Is there a way to flash a different recovery thought terminal emulator?
Sent from my Galaxy Nexus using xda premium

Sure is, download/transfer the recoveryblob to /sdcard/
then run:
su
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
Done!
unless you used ROM manager to flash (no-no) which can cause weird issues like flashes not sticking, in which case see roaches recovery thread for a diff of the fix.

Thing O Doom said:
Sure is, download/transfer the recoveryblob to /sdcard/
then run:
su
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
Done!
unless you used ROM manager to flash (no-no) which can cause weird issues like flashes not sticking, in which case see roaches recovery thread for a diff of the fix.
Click to expand...
Click to collapse
Word... Yea I used ROM manager but why haven't they fixed their issue with it?.. Thanks for all the help man... Really appreciate it
Sent from my Galaxy Nexus using xda premium

Brick!!!!

Can anybody help me i think i just bricked my phone and all i did was:
1. install beans 50 gb rom
2. start a titanium backup
3. iterupte it and unistall for the pro version
4. try again and now it won't let me go nowhere but in recovery mode or download mode
5. tried odin back but it keeps failing at system.img Ext 4 and in recovery i can't mount anything
Please if anybody knows how to help it would be greatly appreciated

I had the ODIN issue with EXT happen to me too. Once I ran ODIN on another PC it worked perfectly.
Sent from my Galaxy Nexus using Tapatalk 2

That doesn't seem like a full brick to me either...
Sent from my SCH-I535 using xda premium

Yea this has never happend to me I'll try to use a different computer but i think it's a problem with the cwm recovery it simply won't let me boot into anything else after some trouble shooting i've realized i can flash through my external sd just not my internal one but i still come back to the recovery.

Marcismo55 said:
I had the ODIN issue with EXT happen to me too. Once I ran ODIN on another PC it worked perfectly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just tried this and im still getting the same error system.img Ex 4 Fail! anybody else that can help me

You might want to add specifics like what version Odin and what drives you're using too.
Sent from my SCH-I535 using xda premium

I used Odin 1.85 to get myself out of a jam like this.
Used root66 and Odin 1.85. Worth a shot
Sent from my SCH-I535 using xda premium

sorry im using for drivers Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0 and odin 3.07
-update i just tried odin 1.85 and i'm still failing at the same place
boot.img
NAND Write Start!
recovery.img
system.img.ex4
Complete(Write) operation failed.
All threads completed. (succeed 0/ failed 1)

I don't think that you bricked, so take a deep breath and go to:
http://forums.androidcentral.com/ve...5-guide-restore-back-clean-factory-stock.html
Odin the stock kernel 1st which will take you through a factory boot. Then Odin the stock rom and you should be back and working again.
I've pushed mine to probably as close to a brick as possible and have used this every time to get back. Let me know how you make out....

jcool13 said:
I don't think that you bricked, so take a deep breath and go to:
http://forums.androidcentral.com/ve...5-guide-restore-back-clean-factory-stock.html
Odin the stock kernel 1st which will take you through a factory boot. Then Odin the stock rom and you should be back and working again.
I've pushed mine to probably as close to a brick as possible and have used this every time to get back. Let me know how you make out....
Click to expand...
Click to collapse
The problem is he can't Odin anything. It almost sounds like something happened to his file system and he needs to format it. Do we have a pit file for this phone?

piiman said:
The problem is he can't Odin anything. It almost sounds like something happened to his file system and he needs to format it. Do we have a pit file for this phone?
Click to expand...
Click to collapse
I think you're likely right. Hopefully this phone does not have the emmc glitch the last galaxy s ii had.
Sent from my SCH-I535 using xda premium

that's what it seems like I can't use odin since it fails and in recovery i get the E: Can't mount /cache/recovery/command as an error at te bottom. I have been googling this up and down but since the people who actually solved it have different phones and files it looks like I'm stuck. Just tried fastboot, odin using samsungs stock, and trying to use adb just delete the recovery altogether but i can't do anything. if anybody doesn't mind and you've recently flashed or don't mind erasing your phone can you type the commands in:
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/mmcblk0p14_system.img bs=4096
RECOVERY
Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/mmcblk0p18_recovery.img bs=4096
USER DATA
Code:
dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/mmcblk0p15_userdata.img bs=4096
CDMA MODEM
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/mmcblk0p1_modem.img bs=4096
LTE_MODEM
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/mmcblk0p12_modemst1.img bs=4096
LTE_MODEM2
Code:
dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/mmcblk0p13_modemst2.img bs=4096
CACHE
Code:
dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/mmcblk0p17_cache.img bs=4096
BOOT
Code:
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/mmcblk0p7_boot.img bs=4096
At least this way i think we'll have the files needed but at this point i don't think none of them will help me or anybody with this problem. Either i have a corrupted recovery or the cache folder has been corrupted.

can you reformat the internal sd in recovery?

nope not thru the recovery won't mount but if i have an external sd its able to read it

sorry mods for bumping this again and this will be my last time can anybody help me in my situation either my cache is corrupted or it my recovery but due to that i am unable to boot normally anywhere except recovery and download mode. The other reason is because I believe my phone is not a complete brick and that it's fixable but of course since i really don't know alot about android I have no clue what to do now. I have tried odin but it fails are their any suggestions please?

Check pm.
Sent from my SCH-I535 using xda premium

joka10 said:
sorry mods for bumping this again and this will be my last time can anybody help me in my situation either my cache is corrupted or it my recovery but due to that i am unable to boot normally anywhere except recovery and download mode. The other reason is because I believe my phone is not a complete brick and that it's fixable but of course since i really don't know alot about android I have no clue what to do now. I have tried odin but it fails are their any suggestions please?
Click to expand...
Click to collapse
You may want to start thinking of restoring stock recovery (you could dd it with ADB) and resetting your flash counter and giving VZW customer service a call. It really sounds like you nand got toasted somehow and since it happened after you rebooted I don't feel it is the ROOM that did it so I'd see if they would replace it over the phone.
Did you try the older Odin someone suggested?
You may also want to ask in the IRC channel #verizons3, someone there may have some ideas.
---------- Post added at 01:20 PM ---------- Previous post was at 01:19 PM ----------
joka10 said:
that's what it seems like I can't use odin since it fails and in recovery i get the E: Can't mount /cache/recovery/command as an error at te bottom. I have been googling this up and down but since the people who actually solved it have different phones and files it looks like I'm stuck. Just tried fastboot, odin using samsungs stock, and trying to use adb just delete the recovery altogether but i can't do anything. if anybody doesn't mind and you've recently flashed or don't mind erasing your phone can you type the commands in:
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/mmcblk0p14_system.img bs=4096
RECOVERY
Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/mmcblk0p18_recovery.img bs=4096
USER DATA
Code:
dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/mmcblk0p15_userdata.img bs=4096
CDMA MODEM
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/mmcblk0p1_modem.img bs=4096
LTE_MODEM
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/mmcblk0p12_modemst1.img bs=4096
LTE_MODEM2
Code:
dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/mmcblk0p13_modemst2.img bs=4096
CACHE
Code:
dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/mmcblk0p17_cache.img bs=4096
BOOT
Code:
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/mmcblk0p7_boot.img bs=4096
At least this way i think we'll have the files needed but at this point i don't think none of them will help me or anybody with this problem. Either i have a corrupted recovery or the cache folder has been corrupted.
Click to expand...
Click to collapse
Have you tried doing this yourself just to see what you get?

are you talking about just shelling it hmm no i haven't
and as for the older odin yes i have no avail, and with adb the problem i was coming into is since I'm in recovery i can't use the command "su" making alot of the commands i found useless but of course i have very limited knowledge on android so maybe i just did something wrong. Do you have any commands you can recommend.

Did you look at anything in this post?
http://forum.xda-developers.com/showthread.php?p=29961927
Sent from my SCH-I535 using xda premium
Just trying to help with clues, don't know if it'll help.

I don't have an s3 but i had an infuse so maybe heimdiall works, that is what fixed my infuse's brick
Sent from my A501 using xda app-developers app

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] 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