I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
Related
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..
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.
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.
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.
CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited