Database Info

[Q] ROM Problem : Stuck on boot logo

This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?

confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth

CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102

I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop

confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.

k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.

Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?

k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout

cannot use recovery after JB

I can get into recovery but after that then to android with red exclamation or usb fastboot screen or fdr screen cold boot. Once I get to red x andy I can go no further. Tried all combo of button pushes and will not go to blue menu for clear cache partition fdr or re start. I am trying to clean cache . It just sits at Andy then after about 5 Min's tab reboots by itself. Have tried about 6 times same thing happens each time, Any idea what is happening or what I am doing wrong or is recovery clean cache partition gone? Thanks
Other wise JB install went smooth no problems and tab is working well . seems smoother . Also kept root with voodoo.

Same here...
I had this same issuethis once, after update with the same intention, was considering either clear cache or to do a full wipe from that level as opposed to doing it through settings. Almost had a stroke u I saw the animated android with the famous (or rather infamous red triangle) Ended up using the one in Backup and Restore in system settings. Think I will try this again, since this concerns me. Anyone else seeing this? If recovery is broken in JB, we have another wait on out hands. Sigh

ditto, starting to see a trend...
Same here, I've had no luck getting past the initial stock recovery screen. Not good.

When you flash OTA update you lose custom recovery.

i have custom recovery installed on JB but it is useless. nothing wants to mount.

ultramegaman963 said:
i have custom recovery installed on JB but it is useless. nothing wants to mount.
Click to expand...
Click to collapse
Same here. Seems as though mount points changed and I can't seem to get adb in twrp...

What is different?
cmdrdredd said:
When you flash OTA update you lose custom recovery.
Click to expand...
Click to collapse
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery

Tomv5314 said:
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Click to expand...
Click to collapse
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.

FreakyPriest said:
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
Click to expand...
Click to collapse
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium

still nothing
xfinrodx said:
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Has anyone been able to get past red exclamation point andy in recovery mode yet?

http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.

FineWolf said:
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
Click to expand...
Click to collapse
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30

merge thread?
amaury48 said:
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
Click to expand...
Click to collapse
Could one of the moderators merge this thread with Red triangle in locked stock recovery ? They are both concerning the same thing thanks Tom

How can I get root and custom ROMming back?

Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob

What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.

aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob

4.4.3 Download failed

I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5

JustinBieber said:
I just recently got the newest update. I downloaded all 99mb of it, plugged in my charger and it rebooted to update my phone. But when it turned on again my phone hasn't been updated, it's still 4.4.2. Checking for updates doesn't work at all.
Anyone have a clue where the download is stored so I can just try to manually flash it?
Stock ROM & Kernel 4.4.2
Rooted
CWM Touch recovery
Sent from my Nexus 5
Click to expand...
Click to collapse
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.

robbham78 said:
I read somewhere that the script will abort if your device is rooted. Not sure if this applies to you.
Click to expand...
Click to collapse
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.

charesa39 said:
Incorrect. Root has nothing to do with it. You will lose root after updating, but it's as simple as flashing SuperSU in your custom recovery to get it back. The reason it's failing is because you have a custom recovery, and are trying to apply the OTA from within Android. If you do that, you have to have stock recovery. If you are stock, just with root, you can flash the OTA.zip using your CWM recovery. The OTA.zip can be found in the /cache directory. I believe it reverts your custom recovery back to stock recovery, but getting it back is as easy as fastboot flashing it.
Click to expand...
Click to collapse
Thanks guys, I didn't know everything had to be stock! plus I found out that xposed will also break the ota

There's an OTA help desk sticky thread in general that tells you everything you need to know
Sent from my Nexus 5 using Tapatalk

Having trouble reverting to stock rom on my shield tablet set to be killed

So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock? And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file? When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom? Sorry for all the questions, I'm pretty new at this. Thanks for the help!

Flash what ever you want in fastboot.
IF you let it boot make sure it's been factory reset, if it connects to WiFi your F****D.
From recovery delete the "TegraOTA" folder/apk from /system/app (or /system/priv-app, I forget). As long as you nuke the updater before it connects to WiFi you're fine.

fro03 said:
So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock?!
Click to expand...
Click to collapse
As the poster above me said, you must flash this with fastboot.
fro03 said:
And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file?
Click to expand...
Click to collapse
You can use whatever image you want as long as you remove TegraOTA.
fro03 said:
When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom?
Click to expand...
Click to collapse
Yes, you can also just flash the custom recovery from fastboot when you are installing the custom ROM. Or you can just not flash a new recovery at all. If you leave your current recovery partition intact you can still flash your custom ROM using fastboot.

weedy2887, sockusminimus
would either of you be up to creating a potential debrick image for this device ?
thanks
m