Database Info

Device stuck in bootloop?

Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!

You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.

Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...

undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.

Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...

undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.

Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.

undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!

[Q] TF300TG Boot/Recovery Problem

OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard

Bump?
riclin54 said:
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Click to expand...
Click to collapse

No-one able to help here??
Would really appreciate some guidance before I blow the tablet away completely!
riclin54 said:
Bump?
Click to expand...
Click to collapse

riclin54 said:
Would really appreciate some guidance before I blow the tablet away completely!
Click to expand...
Click to collapse
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
f69m said:
First of all go to the bootloader screen by holding power and vol-down.
Double-check the Asus version of your bootloader at the top of the bootloader screen and pick the right TWRP version for it:
For Asus v10.4.*: any TWRP *-jb.blob
For Asus v10.6.1.8.*: only TWRP 2.4.4.0-4.2.blob
For Asus v10.6.1.15.*: any TWRP *-4.2.blob
Hope this is clear enough!
Click to expand...
Click to collapse

Thanks for your suggestion Rhian. However I've not yet sorted this. Perhaps a little more info from me will help you help me
The device is running 'Android cardhu-user bootloader <1.0.0 e> released by "WW_epad-10.6.2.3-20130402" A03'. It was unlocked with Asus Unlock_v7 whilst still running ICS and has had Superuser-3.2-RC3-arm-signed.zip installed.
Currently, on initial power up, the device boots straight into TWRP v2.5.0.0 Recovery. I can execute TWRP commands - however there seems to be an issue with access to partitions. Although I can mount the System partition - Cache & Data as well as Micro SDcard and SD-Ext are unmountable (neither can I see block devices in /dev that relate to these). I am however able to access a shell via adb. Further, both volume toggles appear to be operating as they should.
Rebooting from TWRP alerts that "Root permissions appear to be lost". I have attempted to reinstall Superuser but this has not resolved the matter.
"adb reboot boot-loader" will reboot the device into fastboot mode with the boot screen noting "Key driver not found .. Booting OS" and the version info above. From here, I have attempted to use adb to replace TWRP 2.5.0.0 with version 2.4.4.0. Although the adb commands complete without error, the new recovery is not written and the existing 2.5.0.0 remains in place.
From the Fastboot screen on the device, it can be forced to boot Android where everything seems to operate normally and with all partitions and filesystems appearing to be accessible.
All this suggests to me that there is either a problem with the bootloader itself, or less probably, that there is an issue with one or more of the partitions which is interfering with the boot process. There is however a better than even chance that I'm wrong.
I'm considering reformating and replacing the partitions one by one - however this seems rather extreme and in any case, I've not been able to locate an ASUS source of the partitions images yet.
Doing my head in here Rhian - any suggestions?
Thanks,
Richard
Rhian said:
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
Click to expand...
Click to collapse

Recovery issue
Hi, i have the latest 10.6.1.15.3 rom. I've installed twrp 5.0.0, 4.2 recovery. Now, i can enter to recovery, but if i want to make something, do nothing. It seems, twrp don't see the sd card. Any idea?
Thanks

[Q] tf300t

Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!

Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(

noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!

This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app

noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!

Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.

[Q] Softbricked or not?

I know this question has been posted before, but after hours of reading and googling, I can't find a solution, so hopefully somebody can point me in the right direction (which is hopefully not asus support...)
I've had custom roms on my tf700t before but tonight made a mistake when trying something new.
Using fastboot, I used the command 'fastboot erase system -w', thinking that after that I could flash another custom image. That didn't work and what I have now is a device that won't boot.
When booting it shows
'Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.8-20130514" A03'
I can still get into APX mode and I can boot in the Recovery mode which is CWM v6.0.2.3.
I used abd push to send the latest stock rom from the asus website to the device. I saved it in /emmc/ and was then able to select the file from CWM. When I choose to install the file, it installs correctly.
However, after reboot the device just gets stuck with the asus logo. It doesn't boot.
The one million dollar question is of course: can my device be saved, without sending it for repair?

[SOLVED]
So, I just to flash the device with a complete CyanogenMod config, using their website on how to install CM11 on the TF700T.
What I did was:
- upload the bootloader using fastboot
- upload custom recovery using fastboot
- upload CM11 using adb push
- install CM11 using CMW 6.0.4.7
And behold, my tablet boots again!
Looks like there is light at the end of the tunnel after all I might still choose a different ROM, but at least it boots!
So let this post be useful for those who have the same problem -> it is possible to solve it!

I need help with this tablet - few questions

Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?

stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS

Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.

Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)