A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Quevvy said:
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Click to expand...
Click to collapse
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
cmendonc2 said:
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
Click to expand...
Click to collapse
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Quevvy said:
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Click to expand...
Click to collapse
No, you need nvflash backups to use APX mode. Since you can't get to the recovery menu, I can't think of any other solutions....?
Same here
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
boggessb said:
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
Click to expand...
Click to collapse
You would have to open it and replace the motherboard with a new one like this:
http://forum.xda-developers.com/showthread.php?t=2368372
With a new part like this:
http://www.ebay.com/itm/like/390706401658?lpid=82
Related
My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? I CAN get into APX mode.
Yes, wiping the data will brick your device if you don't have a working recovery.
sparky28000 said:
Yes, wiping the data will brick your device if you don't have a working recovery.
Click to expand...
Click to collapse
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
jrfaulkin said:
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
Click to expand...
Click to collapse
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
jeroen.wit said:
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
Click to expand...
Click to collapse
Unfortunately, APX and nvflash is not available for the TF300T currently. As I understand it, you're required to record some information and your Secure Boot Keys (SBK) prior to bricking to be able to access APX. Otherwise, your only recourse is to contact Asus and start the RMA process.
I'm recording my developments over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=2 (my post is at the bottom)
I think I'm going to hold out until someone figures out the NvFlash process as described here:
http://androidroot.mobi/technical/tf-secure-boot-key/
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
gypsyshaw said:
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
Click to expand...
Click to collapse
The difference in your situation is that you were able to access the boot loader. My boot loader is wiped. I don't get the option to select Wipe Data/Fastboot, etc. I'm stuck in a mode where I think the only option is to low-level flash the bootloader after re-initializing all of the partitions.
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
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.
Hi,
After enjoying a successful CyanogenMod install of the stable 10.1.3 I tried to update it with the Dec. 1 daily. I had planned to use TWRP recorvery to install it manually but after downloading it to the phone with the CyanogenMod update utility, it offered to install it automatically so I foolishly trusted it. Now I have an HTC One S in either a boot loop or displaying a fuzzy blue screen. I cannot get to TWRP recovery regardless of what buttons I hold down. Can anyone help?
joelalor said:
Hi,
After enjoying a successful CyanogenMod install of the stable 10.1.3 I tried to update it with the Dec. 1 daily. I had planned to use TWRP recorvery to install it manually but after downloading it to the phone with the CyanogenMod update utility, it offered to install it automatically so I foolishly trusted it. Now I have an HTC One S in either a boot loop or displaying a fuzzy blue screen. I cannot get to TWRP recovery regardless of what buttons I hold down. Can anyone help?
Click to expand...
Click to collapse
If you have this fuzzy blue screen, it means that you are on a wrong kernel. Since it's not possible to flash kernel through recovery when istalling the rom, you have to flash it manually.
So, boot into the bootloader and flash the correct kernel. Then it should work.
And how is it possible that you can't get to recovery? When you hold VOL down + POWER, you get to bootloader and from there you can access the recovery.
same here..
joelalor said:
Hi,
After enjoying a successful CyanogenMod install of the stable 10.1.3 I tried to update it with the Dec. 1 daily. I had planned to use TWRP recorvery to install it manually but after downloading it to the phone with the CyanogenMod update utility, it offered to install it automatically so I foolishly trusted it. Now I have an HTC One S in either a boot loop or displaying a fuzzy blue screen. I cannot get to TWRP recovery regardless of what buttons I hold down. Can anyone help?
Click to expand...
Click to collapse
I'm having the same problem, have you found a solution?
I can't evern get to bootload...
How is it possible that you can't get to bootloader? VOL down + Power should do it. Then, just navigate to bootloader and with USB connected to PC you can flash the kernel and there you go...
Thats what I thought too. But somehow, for the first day, no matter who tried it, bootloader wasn't possible. After trying several times I asked others, because there was no logical explanation to me, why it wouldn't work.
A day later, it worked, now I'm having some problems with the SD card, but I guess as soon as I have time this can be fixed too. Thanks for your help, though!
You're welcome
Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?
You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.
try and unplug from USB when you reboot