This is what I get for trying to do this before I need to get some sleep. I s-off'd my M8 just a few minutes ago, and installed TWRP. Now I can't get out of twrp. If I reboot it reboots right into twrp. So I tried flashing CWM in fastboot mode, and it still boots into TWRP. However if I go into twrp and select reboot into recovery, it reboots into CWM. So if I go into CWM and select reboot system, it goes to TWRP. Somehow I have two recoveries on here. I'm really tired and would love to get some sleep.
Never mind, just installed a new rom.
Related
(I'm a noob.)
I have a tf101 (sbk2), rooted w/ CM10 and CWM 5.8.3.4. Somehow, during my rooting/recovery flashing process, something got screwed up because it will always boot straight into recovery. In recovery, if I "reboot system now," it will reboot... right back into recovery.
The ONLY way I can get into CM10 is by attempting to boot into recovery (voldown+power during boot), and then letting the prompt time out.
That was strange, but now that I'm trying to install Ubuntu, I come across more problems. I can't install any other recovery - flashing other versions of CWM in Rom Manager say they're successful, but the tab still boots into CWM v5.8.3.4 every time. Nothing seems to get rid of it.
Any suggestions?
Thanks.
Try this
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
I went from stock to unlocked, installed TWRP using fastboot, made a backup of stock, flashed nV RLS 1.1 no problem. Went to install nV RLS 2 today and TWRP screwed up the clean install somehow, it booted, but with FCs everywhere. I booted back to recovery, wiped for another clean install and TWRP did a hot reboot of the sorts, then it would just boot to the boot animation and reboot. Went back into TWRP, tried to restore a nandroid, and it failed. Hot reboot from recovery again. I thought it was just a problem with TWRP, so I installed PhilZ through fastboot. I was able to boot into PhilZ, went to do a full wipe, it started, then hot reboot. I attempted to install nV RLS 2 from Philz, and in the middle of the aroma installer, hot reboot. I reinstalled TWRP through fastboot, and it just does a hot reboot about 3 seconds into it.
I've never had this problem with any other phone. Frustrating. I can't get it to stay in recovery long enough to pull the internal storage to the computer. Any fix for this?
EDIT: Success. I did the RUU back to stock thing, then reinstalled TWRP, then I was able to restore one of my TWRP backups. I posted this at 1:16 AM, and now it's 4:40 am. That was a painful learning experience. I must've messed up one of the partitions somehow. I don't really know.
jova33 said:
I went from stock to unlocked, installed TWRP using fastboot, made a backup of stock, flashed nV RLS 1.1 no problem. Went to install nV RLS 2 today and TWRP screwed up the clean install somehow, it booted, but with FCs everywhere. I booted back to recovery, wiped for another clean install and TWRP did a hot reboot of the sorts, then it would just boot to the boot animation and reboot. Went back into TWRP, tried to restore a nandroid, and it failed. Hot reboot from recovery again. I thought it was just a problem with TWRP, so I installed PhilZ through fastboot. I was able to boot into PhilZ, went to do a full wipe, it started, then hot reboot. I attempted to install nV RLS 2 from Philz, and in the middle of the aroma installer, hot reboot. I reinstalled TWRP through fastboot, and it just does a hot reboot about 3 seconds into it.
I've never had this problem with any other phone. Frustrating. I can't get it to stay in recovery long enough to pull the internal storage to the computer. Any fix for this?
Click to expand...
Click to collapse
what happens if you just do: fastboot boot <recovery name>? i can't say ive had this issue b4, but its something to try
izzaeroth said:
what happens if you just do: fastboot boot <recovery name>? i can't say ive had this issue b4, but its something to try
Click to expand...
Click to collapse
well somehow Philz works for adb purposes. Hot reboot if I try and actually do anything with it though. I'm doing an adb pull /data/media/0 right now. I think I'm just going to do that RUU and factory reset this thing and start over.
edit: fastboot boot twrprecovery.img yields the same results as trying to boot it from the phone.
And from now on TiBu backups are going on the SD card.
Edit: I fixed the problem some 3 hours later. Still don't know wtf happened though. Had to revert completely back to stock to restore a nandroid.
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE (updated with latest omni versions as they became available).
Everything been working fine until two days ago, when Xoom froze. It had happened before a couple of times and a reboot had solved the problem. Did that, and this time it got stuck in a bootloop, only getting as far as the Omni splash screen before rebooting. Few reboots later, nothing improving, and then it didn’t get past the Motorola M splash screen.
Tried booting into recovery, frozen at teamwin splashscreen. Nothing was working. Rebooted few time, same thing. Connected to power, charged til green, left for extra 30 minutes, tried again, same problem. Switched off. Came back to it today and....
All of the following done via Fastboot:
Tried flashing non bigpart TWRP (R.A.H._TWRPv2.6.3), still stuck at teamwin splash screen. Flashed Clockwork recovery, booted into recovery fine, but couldn’t see memory card. Flashed Clockwork recovery touch version, same problem. Flashed back to TWRP non bigpart, and it booted into recovery fine, sdcard mounted fine, seeing all files. Excellent. Decided to reflash bigpart version, used reboot option in TWRP, it tells me there is NO OS INSTALLED.
Ok, that’s a bit odd. Must be corrupted or something, but might explain the original freeze and bootloop and then not even getting to Omni splash screen. Swiped to reboot. Flashed bigpart version of TWRP. Rebooted into recovery. Back to original problem, stuck at teamwin splash screen. Left it for 10 minutes just to be sure. No joy.
Tried retracing steps, flashing Clockwork recovery. Reboot. Teamwin splash screen. WTF? Try flashing Rogue recovery. Reboot. Teamwin splash screen.
Kinda confused. It’s like it’s telling me it’s successfully flashed but it hasn’t actually done anything. Power everything down, disconnect everything. Start again. Flash Clockwork recovery, reboot, displays teamwin splash screen, sticks. Flash TWRP, non bigpart, displays teamwin splash screen, sticks. Reboot. Flash TWRP bigpart. Reboot, displays teamwin splash screen, sticks.
Walk away in disgust so as not to throw something at Xoom.
Ok, TL-DR recap.
Worked fine for months
Two days ago, froze on Omnirom logo, got stuck in bootloop
After few reboots didn’t even make it to Omnirom logo, stuck on M screen
Flashed TWRP recovery, non bigpart, stuck at teamwin splash screen
Flashed Clockwork recovery, got into recovery, no SDcard
Flashed Clockwork recovery, touch version, same problem
Flashed TWRP non bigpart, got into recovery, could see SDcard and files, rebooted from within recovery to flash bigpart version, tells me NO OS installed
Reboot
Now, regardless of which recovery I flash it goes straight to teamwin splash screen and stays there.
Help
Bump
Come on guys, 100 plus views and no replies? Surely somebody has an idea?
At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::
Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
runandhide05 said:
At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::
Click to expand...
Click to collapse
codliness1 said:
Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
Click to expand...
Click to collapse
I'm stuck in TWRP v2.6.3.0(RunAndHide05 Edition) cant mount system, wipe any data tried or install any rom. Tried flashing different recovery via fast boot but stays the same
*No Os installed error
@crazylegs90 did you figure this out man? Im stuck at twrp start screen..
So I rooted and installed twrp on my sis's OPO, then installed Resurrection Remix and it worked fine. She decided to restart her phone and now it's stuck in twrp no matter what. What can I do? I've tried searching and can't find a good forum thread about my situation.
I try to enter bootloader, guess what? Goes back to TWRP.
Install new rom? Goes back to TWRP.
Wipe then install new rom? Goes back to TWRP.
I have adb control, what can I do?
I'm going to try this post and will update soon.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Just realized I can't do this because I can't boot into fastboot and can only boot into twrp.
restore nandroid backup. or flash firmware again.
Found my issue. My volume down button is broken now so it just keeps pressing it when I'm not so it kept going into twrp. Manged to get into fastboot, I just have to kept trying and it just sometimes doesn't press down every second.
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Glomgold said:
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Click to expand...
Click to collapse
Please try to get into "Fastboot Protocol" by holding the button volume down at the time before the boot loop starts newly again. Three icons will appear. The first one, RCK; is blinking. Press volume up and your TWRP should start. Hopefully you have Kang TWRP. If so you may install rom, gapps and SuperSU again by following exactly the install instruction by Timduru here: https://forum.xda-developers.com/tra...t/rom-t3453702.
(Don't forget to do "Format Data" through Kang TWRP as first of all. It takes up to one hour. Be patient and let it run.)
I'm sorry, but if you are really not able to boot into either fastboot or recovery the tablet is bricked for good!
Thank you for advice.
The tablet is up and running again. I wasen't able to boot into Kang TWRP, but I was able to use fastboot. I ran a lot of erase commands that I found in a guide, erase boot, erase recovery, erase userdata etc., afterwards I flashed stock rom. It still wouldn't boot, but I installed Kang TWRP with fastboot and I was able to use TWRP again so I was able to flash a custom rom and it booted up again.
Glomgold said:
Thank you for advice.
The tablet is up and running again. I wasen't able to boot into Kang TWRP, but I was able to use fastboot. I ran a lot of erase commands that I found in a guide, erase boot, erase recovery, erase userdata etc., afterwards I flashed stock rom. It still wouldn't boot, but I installed Kang TWRP with fastboot and I was able to use TWRP again so I was able to flash a custom rom and it booted up again.
Click to expand...
Click to collapse
Congratulations! You did a good job. Seems as if you did the well known "Buster99 Solution" successfully in order to get back on stock rom. Keep it in your mind for ever. It may be also helpfully in other cases of trouble.
odd loop.
Glomgold said:
So I updated to the latest version of KatKiss, did a wipe first (from Kang TWRP), everything seemed fine the tablet booted and everything was working. I powered off the tablet and went on with my day, when I turned it on again it's in a boot loop. I get the ASUS-logo (at least one time I also got the KatKiss-logo), it tries to boot and it returns to the ASUS-logo. I tried to do a wipe in recovery (Kang TWRP) but it doesn't complete, after around 30 seconds it jumps automatically to the ASUS-logo and tries to boot again.
Any solution greatly appreciated.
Click to expand...
Click to collapse
Randomly my tablet started doing the boot loop. It would show the Asus Logo, then the Kattkiss logo and it will go to a screen saying optimizing apps. It would go through and optimize all 1-75 then reboot and start the process again. I unhooked the dock and allowed it to do this until the battery was completely dead. Next day same thing. This tablet has been unchanged OS wise for about 2 years. only used for youtube videos. Super odd that it randomly broke.
It does have a good TWRP version installed v2.8.7.0. So I tried flashing the 7.1 rom, su, gapps and wiped cache/dalvik. Did not correct it. So then did factory reset. Still no go. Now i am doing a full wipe / format. After format i will reinstall katkiss 7.1, su, and gapps. Hopefully i get back to normal after that.
Absolutely no idea what spurred this or what caused the break. Has been completely normal for a very long time. Weird.
Anybody else see anything like this?
thereal35 said:
It does have a good TWRP version installed v2.8.7.0.
Click to expand...
Click to collapse
I don't think so. In order to get this Rom installed on your devise you need Kang TWRP as advised by @timduru https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479.