Hi, I unlocked my bootloader, flashed CWM through fastboot, flashed Clean Rom. And now device wont boot past ASUS boot screen, it just keeps rebooting. Is there any help. I believed I followed all the steps.
misscrobb said:
Hi, I unlocked my bootloader, flashed CWM through fastboot, flashed Clean Rom. And now device wont boot past ASUS boot screen, it just keeps rebooting. Is there any help. I believed I followed all the steps.
Click to expand...
Click to collapse
Can you still boot into recovery? also make sure your cwm is the correct version with JB. If you can boot into recovery, flash Asus JB stock rom, let me know if it boot up (this step ensure that you have JB boot loader) and update all the components. Let me know how it goes, then we move to the next step.
Which version of CleanROM?...original or CROMI?
I don't know exactly what I did but got it to work...
Sent from my Nexus 4 using xda app-developers app
Related
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Wiltuz said:
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Hi there, sucks to hear what happened..
I believe you haven't put in enough research, ASUS has a publicly available unlocker for the 300T, why did you use a 3rd party root app?
Can you still boot Android? If you have root and your recovery partition is broken, there should still be a way to overwrite the recovery partition.
If not, this basically looks like a brick, unless you can hook up a debugger during the boot process somehow.
Someone with in-depth knowledge of this device might be able to help you out further, I'm just theorycrafting here.. Best of luck!
I would try using fastboot to reflash stock firmware, which you can download from the Asus website.
You could also try getting into APX mode and using nvflash to reflash it.
Sent from my Transformer Pad TF300T using xda app-developers app
Well earlier this week I was trying to revert back to stock and something must of f'ed up because now I get stuck at the Asus boot screen with the loading circle. I am coming from CyanogenMod 10.1 using TWRP. I was able to flash the stock rom using fastboot but like I stated; it gets stuck at the loading circle screen. Any help?
lightitwithfire said:
Well earlier this week I was trying to revert back to stock and something must of f'ed up because now I get stuck at the Asus boot screen with the loading circle. I am coming from CyanogenMod 10.1 using TWRP. I was able to flash the stock rom using fastboot but like I stated; it gets stuck at the loading circle screen. Any help?
Click to expand...
Click to collapse
Did you flash the correct TWRP afterwards>? You have to wipe the device inside of TWRP after you revert to 4.1 or you will get stuck in a loop. Happened to me too. Also, did the progress bar finish? You should still have fastboot access right?
pyraxiate said:
Did you flash the correct TWRP afterwards>? You have to wipe the device inside of TWRP after you revert to 4.1 or you will get stuck in a loop. Happened to me too. Also, did the progress bar finish? You should still have fastboot access right?
Click to expand...
Click to collapse
Yes i'm 99.9% sure I flashed the correct TWRP. The progress bar DID finish, and yes, I still have access to fastboot.
lightitwithfire said:
Yes i'm 99.9% sure I flashed the correct TWRP. The progress bar DID finish, and yes, I still have access to fastboot.
Click to expand...
Click to collapse
Ok try wiping /data /cache and /dalvik . Should fix you right up. ONLY use the option in twrp though. Do NOT use the wipe in the bootloader menu or you will brick they say.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hey guys,
I recently rooted my Galaxy Tab 2 P3110 , then installed CWM, and then went on to install the Cyanogen Mod 10.1.3. Installation was succesful .I then used the tablet for about 5-6 hrs before i restarted it. Now the tablet is stuck showing the Cyanogen logo. I have waited for an hour and still nothing happened.
When i tried to enter the CWM recovery mode, i end up getting the ODIN screen or the stock recovery mode.
Any ideas as to how i can resolve this issue.
Thanks in advance
Does it bootloop or just stick at boot animation?
If it's stuck at animation you may be able to adb push recovery.
sent using logic and reason from a device forged of witchcraft.
tokenpoke said:
Does it bootloop or just stick at boot animation?
If it's stuck at animation you may be able to adb push recovery.
sent using logic and reason from a device forged of witchcraft.
Click to expand...
Click to collapse
It just stuck at animation.
I don't know the Windows process of an adb flash of recovery.
You can also try to flash it with odin
sent using logic and reason from a device forged of witchcraft.
tokenpoke said:
I don't know the Windows process of an adb flash of recovery.
You can also try to flash it with odin
sent using logic and reason from a device forged of witchcraft.
Click to expand...
Click to collapse
I tried the ODIN method. I first downloaded the stock rom and then used ODIN to flash it. It says Pass in the ODIN App but when the device reboots, i still get the cyanogen logo which goes on forever..!!
I had the same issue with being stuck at the cyanogenmod boot animation. I went back into recovery, did a wipe data/factory reset. Once I did that, I flashed the .zip file from my sdcard and it worked fine. As far as your installation of CWM, you must have not installed it correctly. I use Philz Touch Recovery for my P5113.
Hi,
I was using Phil recovery before and I tried to flash TWRP.
For some reason, after I have flashed TWRP, I cannot get into RCK again and the machine will freeze (the one with 4 icons)
How can I reinstall recovery? It will be good to get it through irdin as I don't know how to fastboot. Can I use erminal emulator to install it again?
I have installed goomanager and when I tried to boot the device into bootloader, it will just freeze on the ASUS screen
Thank you
eatout said:
Hi,
I was using Phil recovery before and I tried to flash TWRP.
For some reason, after I have flashed TWRP, I cannot get into RCK again and the machine will freeze (the one with 4 icons)
How can I reinstall recovery? It will be good to get it through irdin as I don't know how to fastboot. Can I use erminal emulator to install it again?
I have installed goomanager and when I tried to boot the device into bootloader, it will just freeze on the ASUS screen
Thank you
Click to expand...
Click to collapse
If you have 4 icons you are on the wrong bootloader. Tread carefully as you are <--> this close to hard bricking your device now. DO NOT WIPE IT - if you do you've lost it.
You should flash the latest asus stock rom to get your bootloader updated but you will have to do that over fastboot from a pc now...... Instructions are in general I think.
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
t.holley.os said:
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
Click to expand...
Click to collapse
What do you want to do exactly? Restore stock recovery so that you can take the OTA? If you followed either one of the methods on that thread, you should already be stock, i don't get why you booted TWRP again.
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
t.holley.os said:
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
Click to expand...
Click to collapse
Just flash the stock recovery image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
t.holley.os said:
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
Click to expand...
Click to collapse
Press and hold power for 30 second, the device will try to boot but just keep holding the power. Then press and hold vol down and power. It doesn't boot into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
t.holley.os said:
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
Click to expand...
Click to collapse
FYI the TWRP boot loops are due to MTP bug that was never fully fixed from 2860. It's better than it used to be, but still an issue occasionally, especially if connected to power while you try to get in to TWRP.