I just bought a op8 but just for fun I wanted to update a custom rom on my op5t. I wiped everything and installed the rom like I've done many others, but it reboots back to recovery. I transferred another rom zip plus gapps, flashed it, but it does the same thing.
I've never encountered this. Is it maybe an issue with the Twrp version? I don't think so because I just updated to a new version a little over a month ago.
Any ideas to get me back to a working phone would be appreciated. It'd be nice to use this phone as a backup if necessary. Thanks.
Hello what rom did you attempt to flash and what version of twrp are you on? Also what android version was the device on before you tried flashing the rom?
Sent from my ONEPLUS A5010 using Tapatalk
Notorious said:
Hello what rom did you attempt to flash and what version of twrp are you on? Also what android version was the device on before you tried flashing the rom?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Sorry. I totally missed your response.
I was on the latest Derpfest and had just updated to what should be the latest version of TWRP (Bluspark) I don't have the phone on me right, but can get the version number later.
I was trying to update to the newest version of Derp which was Android 11, but when that failed I pushed CRDroid to the SD card. It also booted back to Twrp.
Thanks.
Related
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Yep, both factory reset (default wipe) and full wipe of everything but internal storage.
Click to expand...
Click to collapse
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
jd1639 said:
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
Click to expand...
Click to collapse
Currently tried flashing BlissPop to see if problem persists. How long would you say is "too long"?
Occasionally I've seen 20 minutes or more. That's not usually the case but I have seen that.
Currently on 21 minutes with BlissPop booting. Thank you for your help so far, if this doesn't boot in 10 minutes I'll try and flash the stock images. Is there any way to find what phone model I have just using fastboot?
When you boot into the bootloader that screen will tell you the device you have
I know but none of the options from here https://developers.google.com/android/nexus/images?hl=en#bullhead fit. Or are the "MHC19Q" and such just versions of 6.0.1? Sorry for the (probably) stupid question.
tm.tudor said:
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Click to expand...
Click to collapse
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Shyciii said:
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Click to expand...
Click to collapse
Yep, that was it. Thanks a lot!
So I tried installing the elemental x kernel from the app, but after it had finished installing, I ran into a lot of issues. I can't take any pictures ('Low memory, adjust the quality or delete some files'), the file manager says that internal storage has 0.0 bytes available, and I can't download or take screenshots also, gallery says there aren't any pictures and the list goes on. I'm on oxygen os 3.5.3 and I haven't tried anything yet. How do I fix this, and is there any way I can keep my files? Thanks
Are you using the Xposed module called 'installeropt' if you have just uninstall and reboot...
Nope, never used that module, like I said the problem started after installing a kernel.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
If I was you I'd just flash the ota firmware 3.2.4 for oxygen OS from OnePlus website that will restore everything to default so you can start again , the reason I asked about that Xposed module is because when I installed that my apps would not download data so I had to restore my firmware using the method I've just said , as a side note after flashing the original firmware in twrp if it says no OS installed are you sure you want to continue just click yes and then once booted up you are free to root and flash Xposed , I hope this solves your problem.....
Xceeder said:
If I was you I'd just flash the ota firmware 3.2.4 for oxygen OS from OnePlus website that will restore everything to default so you can start again , the reason I asked about that Xposed module is because when I installed that my apps would not download data so I had to restore my firmware using the method I've just said , as a side note after flashing the original firmware in twrp if it says no OS installed are you sure you want to continue just click yes and then once booted up you are free to root and flash Xposed , I hope this solves your problem.....
Click to expand...
Click to collapse
I will give that a try tomorrow since I can't download anything . Will keep you updated, thanks! Btw do you mean clean flash or dirty flash?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Clean flash buddy....
Xceeder said:
If I was you I'd just flash the ota firmware 3.2.4 for oxygen OS from OnePlus website that will restore everything to default so you can start again , the reason I asked about that Xposed module is because when I installed that my apps would not download data so I had to restore my firmware using the method I've just said , as a side note after flashing the original firmware in twrp if it says no OS installed are you sure you want to continue just click yes and then once booted up you are free to root and flash Xposed , I hope this solves your problem.....
Click to expand...
Click to collapse
Good news!
I decided to see what would happen if I booted into recovery and for some reason twrp did recognize the files. I still had the oos 3.5.3 file on there, but I figured it would give an error message when I'd flash it. But I gave it a try anyway and it worked! Everything is back the way it was and I have all of my files! Turns out I was in a lot less trouble than I thought i was. Thanks a lot for your advise![emoji1] [emoji1] [emoji1]
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
That's great news and no problem I'm just glad you've sorted it out , peace....
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
dg89 said:
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
Click to expand...
Click to collapse
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
tiklmypikl said:
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
Click to expand...
Click to collapse
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
dg89 said:
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
Click to expand...
Click to collapse
What verison of TWRP are you on?
tiklmypikl said:
What verison of TWRP are you on?
Click to expand...
Click to collapse
right now it is on v2.8.7.0 and i tried to install the new version but it's not working
Hey guys
I was running stock rom Global v110.7.0 and I recently downloaded and installed the 1.9BGb OTA update for miui V11.0.9.0 and now my phone just boots to recovery.
Phone is rooted and unlocked, using twrp.
any help on getting it back up and running is appreciated.
ended up having to format all data to get the update. overall performance is pretty much the same.
Do not recommend. 1/10 experience.
Updated here, no problems. Stock ROM.
nptls said:
ended up having to format all data to get the update. overall performance is pretty much the same.
Do not recommend. 1/10 experience.
Click to expand...
Click to collapse
This happened to me too once that I believe is because of incompatible images. In your case, you had TWRP and Magisk installed so the boot and recovery img had already been modified. No wonder why the phone failed to boot after the update.
As reminder:
1. Ensure everything is back to stock before attempting any official MIUI update
2. Or try the OrangeFox OTA survival method instead of TWRP