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..
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.
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards