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

Bricked (?) ASUS Transformer Infinity TF700T

Hi there,
I need your help urgently.
I received a brand new TF700T and did make it work to support root.
I also did unlock the bootrom protection.
When I tried to install a custom ROM manager (Clockwork Mod) image from:here
The device didn't want to start any more - showing message:
The Device ist Unlocked.
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
But nothing happens anymore (
I can wait for the battery to run empty in this mode.
There' no chance to boot from Micro SD.
The only thing what works at the moment is to connect the device via APX drivers.
I tried to communicate with device via NVFLASH tool
But when trying this - I get the message:
Nvflash started
Unknown Device found
Does any one have an idea where to find appropriate drivers for Nvflash?
Or the parameters to match TF700T?
Thanks in advance!

if you are able to access APX then you still have hope, first of all you need to push custom recovery like TWRP via fastboot mode and then install custom ROM. Most likelly you were to lazy to read a lot information on this forum how to install stuff properlly.
EDIT: if Tf700t has pin hole you should turn it off despite waiting for it to discharge...

nikoltu said:
if you are able to access APX then you still have hope, first of all you need to push custom recovery like TWRP via fastboot mode and then install custom ROM. Most likelly you were to lazy to read a lot information on this forum how to install stuff properlly.
EDIT: if Tf700t has pin hole you should turn it off despite waiting for it to discharge...
Click to expand...
Click to collapse
I did already read a lot - for hours and nights.
But my main problem is: UNKNOWN DEVICE
What does TWRP mean? How do I get fastboot to work?
I'm even not allowed to enter recovery mode.
The device is just recognized as an APX -device...
I can't push or download any custom ROM since I can't communicate with the device in both directions...

For those who messed up really bad and can't boot but are unlocked.
EDIT: I didn't see that you are not unlocked. then you should Power on + volume down, wait, see two icons select wipe, pray to god it helped or not. And if it doesn't boot and you are not unlocked last thing to do is RMA.
You are not allowed to enter recovery because you have stock one with droid dead and red triangle I guess.This is TWRP site and all instructions are here TWRP - Team Win Recovery Project is alternative to ClockworkMod Recovery but better. to get to fast boot turn on your tab holding power on + volume down and then do nothing while it asks to pres up. if you are unlocked you will see 3 icons select usb drive icon. FASTBOOT mode. now follow instructions from TWRP site. after that youl need custom rom zip. if recovery instaled successfuly and you can get into it you'll need to put custom ro into microSD or if you can into internal storage. if you can't conect to pc via cable and start cmd if Windows or terminal if Linux or mac. type
Code:
adb shell
mount /dev/block/mmcblk1p1 /data/media
you will be able to access microSD via recovery (unless it is different than Prime tf201 you will need different command, but give it a try)

nikoltu said:
EDIT: I didn't see that you are not unlocked. then you should Power on + volume down, wait, see two icons select wipe, pray to god it helped or not. And if it doesn't boot and you are not unlocked last thing to do is RMA.
You are not allowed to enter recovery because you have stock one with droid dead and red triangle I guess.This is TWRP site and all instructions are here TWRP - Team Win Recovery Project is alternative to ClockworkMod Recovery but better. to get to fast boot turn on your tab holding power on + volume down and then do nothing while it asks to pres up. if you are unlocked you will see 3 icons select usb drive icon. FASTBOOT mode. now follow instructions from TWRP site. after that youl need custom rom zip. if recovery instaled successfuly and you can get into it you'll need to put custom ro into microSD or if you can into internal storage. if you can't conect to pc via cable and start cmd if Windows or terminal if Linux or mac. type
Code:
adb shell
mount /dev/block/mmcblk1p1 /data/media
you will be able to access microSD via recovery (unless it is different than Prime tf201 you will need different command, but give it a try)
Click to expand...
Click to collapse
Thanks for advise - BUT
I have no choice like selecting Fastboot or USB etc. with volume buttons.
These options unfortunately do not come up anymore.
My device is definetly unlocked. It shows up "Device unlocked" when trying to boot normally.
When trying to go to recovery, with Volume - hold, the device tries to launch to recovery but hangs in status:
Device is Unlocked
Android cardhu-user bootloader (2.10 e) released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel.
I have NO option to go to fastboot! Only way will be APX but nvflas always tell me unknown device.
So I was looking for any other version of nvflash.
In other forum I did find hint for nvflash ICS but didn't find right version yet.
If I only could get communication via APX worked to my device, then I could send data via nvflash and APX...

I assume you can't even go to rom as it bootloops on EEE pad screen not on rom splash screen
1. Did you try Wipe option in (power + volume down, wait 5 sec.)? [it is esential in all situations of trying to recover]
2.ammm... when you enter "adb devices" in your cmd on PC doesn't it show anything (do it while your tablet is on and hangs anywhere, just make sure it is on)? list is empty? if not it shows your device with some random letters and numbers.
Try manually setting your pc. Download android SDK and all packages for Android 4.x then in Device Manager (Control panel) find your Tablet and update your driver to Android ADB interface (you can experiment, till your device is shown correctly via adb devices command).
But first of all make sure you do or did first step. it is common issue among Prime users so maybe it can help you.

nikoltu said:
I assume you can't even go to rom as it bootloops on EEE pad screen not on rom splash screen
1. Did you try Wipe option in (power + volume down, wait 5 sec.)? [it is esential in all situations of trying to recover]
2.ammm... when you enter "adb devices" in your cmd on PC doesn't it show anything (do it while your tablet is on and hangs anywhere, just make sure it is on)? list is empty? if not it shows your device with some random letters and numbers.
Try manually setting your pc. Download android SDK and all packages for Android 4.x then in Device Manager (Control panel) find your Tablet and update your driver to Android ADB interface (you can experiment, till your device is shown correctly via adb devices command).
But first of all make sure you do or did first step. it is common issue among Prime users so maybe it can help you.
Click to expand...
Click to collapse
I would like to exchange email-adresses to enhance communication.
You could also send email to [email protected]
I did try with button combination (power & + button) as well, but device did not wipe.
For now - I'm about to update Android SDK )
Hopefully this works to recognize my TF700T...

If you manage to unbrick please post the information back here it may be helpful to others.

t-liner said:
My device is definetly unlocked. It shows up "Device unlocked" when trying to boot normally.
Click to expand...
Click to collapse
How did you get your TF700 unlocked? Asus hasn't posted an unlock tool for it yet that I could find.

Asus devices have the same unlock tool
Sent from my Transformer Prime TF201 using xda app-developers app

nikoltu said:
Asus devices have the same unlock tool
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
Unlock + Root was never a problem.
I managed it to unlock the device using the TF300T tool / link.
Boot loop was big problem.
I did raise RMA in the meantime. New device is on the way.
Thanks to all repliers.
I will keep off doing this again / wait until xda-experts will provide a working way to CWM TF700T.

My Transformer Infinity isn't bricked, I just can't get it to boot into recovery. (I'm unlocked and rooted, but no custom ROM.) I have tried both CWM and TWRP 2.2.0 with GooManager. The tablet just won't boot into recovery mode. I can hold the Down Volume key and Power button to have the initial boot up menu display. When I press the Up Volume button to boot into recovery mode, it just hangs like the OP talks about. I then have to hold the power button for about five or so seconds to get it to power down again. I can turn it back on and it will boot normally.
I thought maybe something was messed up because I installed busybox, or hacked the Flash Player to work in desktop mode, or tweaked the build.prop file or something. I've put the build.prop file back to default, and removed the busybox apps, but that hasn't resolved the problem. I've tried re-running the unlock tool, but it fails halfway through. I'm not sure if that's normal or not after you've run it once, or an indication of something messed up.
Any suggestions on what else to try or look at are appreciated.
---------- Post added at 06:06 PM ---------- Previous post was at 05:13 PM ----------
UPDATE: I finally got TWRP 2.2.2.0 to work using the following option from the Instruction Page (http teamw.in/project/twrp2/105):
Download - ADB / Terminal method:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
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 to complete installation.

stuck at boot logo
Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced

dough30i said:
Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced
Click to expand...
Click to collapse
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.

gaxiolafm said:
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.
Click to expand...
Click to collapse
Damn u too huh. **** I just got mine for only 2 week old and neva thought I go through this IDK what to do but wait gracefully for the senior member to help or come up with a way for us noobie to unbrick my 650 table...Oh BTW leave it alone then u still lucky if can go thru fast boot mode

I have the exact same problem
anyone has a solution to this problem

gaxiolafm said:
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.
Click to expand...
Click to collapse
That is what it says when you are in fastboot mode, the rest of the job you do with a computer. Also we have had major issues with cwm on the Prime, I would recommend TWRP!
Sent from my Transformer Prime TF201 using xda premium

Same problem
israodin said:
I have the exact same problem
anyone has a solution to this problem
Click to expand...
Click to collapse
Same problem.
Any help? Please! :crying:

[Q] Help Revive my Xoom

Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:

so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:

claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now

Bricked :(

All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?

spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.

The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.

Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later

pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.

Trouble booting into recovery (TWRP)

Hi, this is a first time root for me on my Asus Transformer Pad Tf300t.
I followed the rooting options, and all went as planned.
I then tried to install Google apk's through recovery and it all started to fail from there.
All the apk's were failing after flashing into Cyanogenmod 12.1, so I decided to remove the apk files and reboot. Somehow they were still installed so instead I tried to factory reset the device, but upon doing so I now can not boot into recovery.
All I get is the team win logo screen that stays on for a few seconds flashes off and repeats.
No force reset, not hard reset, nothing.
I have zero experience with the technical side of rooting, and therefore have no ideas how to fix the issue myself. If anyone thinks they can help me, please let me know!

get latest twrp and fastboot binaries (you might have them already for rooting)
boot into bootloader:
a) open terminal and type in:
su
reboot bootloader
b) power down tablet
boot it up with vol- pressed
etier a) or b) should leave you with 3icons (RCK, android, wipe data) - stay on that screen
plug tablet to computer
make sure it is detected by typing this into terminal on your computer: fastboot devices
fastboot erase recovery
fastboot flash -i 0x0b05 recovery path_to_twrp_blob
example:
fastboot flash -i 0x0b05 recovery c:\stuff\twrp.blob
wait till it is done (should see blue bar on tablet screen)
then reboot rablet:
fastboot reboot
let it boot to system, then reboot back to recovery - should work this time (not sure if boot to system is needed at this stage, I had one time issues with recovery when not booted to system first but that might have been faulty flash and not procedure failure)
Sent from my TF300T using XDA Free mobile app

hi, I don't understand the procedure for booting in recovery......I have the following trouble: I updated my TWRP recovery by itself recovery , from 2.8.4 to 2.8.7 following the instruction on the site TeamWin. Afterhand I can't go in the recovery mode e for this I can't flash other Roms. Is it possible to solve this problem?Thank's

Do you have ADB on your computer and does it see you tablet?
If so, while the tablet connected with USB cable, open up Windows command prompt, and issue command:
"adb reboot recovery".
Or within Android, install Terminal Emulator app (I found the best one to be by Jack Pavelich). Open it, type:
"su" and allow root
then:
"reboot recovery"
That will get the tablet, or any Android device, reboot into recovery mode.
Sent from my TF300T using Tapatalk