Related
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
mjp93 said:
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
Click to expand...
Click to collapse
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
I'm travelling and the hotel wifi is super slow. I have the full 5.1.9 and I've tried dirty flashing and clean flashing (I did a nandroid backup first). With a dirty flash the phone boots to the lockscreen but immediately says shutting down and reboots, after the reboot it goes to recovery (stock or twrp whichever is installed). After a clean flash it seems to try to boot then just shuts off and reboots to whichever recovery is installed.
I've set 5.1.8 to download which will take HOURS so I'll report back with any update. I pray this fixes it...
toyanucci said:
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
Click to expand...
Click to collapse
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Pat123 said:
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Click to expand...
Click to collapse
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
5.1.8 should be flashed again over current 5.1.8?
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
MrSteelX said:
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
Click to expand...
Click to collapse
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
toyanucci said:
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
Click to expand...
Click to collapse
I meant take backup through ADB, format everything including data, internal storage, then fastboot flash full ROM zip.
I am having the same exact issue.
Can't restore a nandroid backup. All I get is light blue notification LED. I tried 5.1.8 and 5.1.9. With TWRP right after and without it. Without even magisk. It just bootloops forever. If I install 5.1.9/5.1.8 full zips, twrp, reboot recovery, magisk. It just reboots into twrp. I can't even install any of the full ota zips. It wont get past the android boot animation when I just want to flash the ota zip only. Can't get out of twrp. Luckily I was able to backup everything, but don't know how to proceed further allowing me to regain usage of my phone.
To me, this is sounding like something did not flash right with vendor partition.
if a full wipe of System, data, internal storage, the whole 9 yards doesn't work. The only option I see that should work is the mega unbrick thread. https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
MrSteelX said:
To me, this is sounding like something did not flash right with vendor partition.
Click to expand...
Click to collapse
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
garz said:
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
Click to expand...
Click to collapse
Did you make sure the download was not corrupt before flashing? OnePlus6Oxygen_22_OTA_013_all_1807130145_92ea1c670c0fae.zip MD5 61EAE0DA48C6B3914F48F3E6EA99A74B
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
garz said:
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
Click to expand...
Click to collapse
Funny, I was about post that link but i see you found it first. It is also good that it fixed it for you.
As far as TWRP backups, you only need to backup data. You can just install the full ROM zip file and restore data to get everything back if you have issues with nandroid restore. Just don't forget to flash TWRP before rebooting or you will need to fastboot it again.
Maybe an issue with battery calibration. Try checking the battery when the phone just boots. If it says low battery and because of that its shutting down then its just a software error and just try to turn in the phone with charger connected to check if tgats the problem. If that dosent work try the oneplus 6 mega unbrick guide and return to stock oos 5.1.5 using snapdragon msm recovery tool. For detailed info see tge OP6 unbrick guide on xda. Tell me if it works
toyanucci said:
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
Click to expand...
Click to collapse
One question, when you manually change to slot B, you're in a black screen with blue notification LED right? If that doesn't even go fastboot, how do you get out of that slot into the other one again to the boot-recovery loop?
I'm not sure what I've done wrong. I downloaded the full image of the OS and have flashed it to both slots but neither works. Anyone have an idea of how I can fix it without wiping data? I'm rooted and have TWRP installed.
Well, after flashing multiple times, slot A and B both reboot as soon as the get to the lock screen. Any help?
As I continue my troubleshooting steps, I've tried https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 using the "flash-all-partitions-fastboot.bat" option and still nothing.
Also, I just tried to make TWRP backup and it failed on the user data with "createTarFork() process ended with ERROR: 255"
I followed this guide and it worked perfectly. https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232.
Do you flash the full update in TWRP, then flash twrp.zip?
I was on 5.1.7 update to 5.1.9 with Magisk and TWRP installed. No loss of data.
marcoryn said:
I followed this guide and it worked perfectly. https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232.
Do you flash the full update in TWRP, then flash twrp.zip?
I was on 5.1.7 update to 5.1.9 with Magisk and TWRP installed. No loss of data.
Click to expand...
Click to collapse
Yeah, that's the exact post I followed. Used those files and everything. But still nothing is working like it should.
d3athsd00r said:
As I continue my troubleshooting steps, I've tried https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 using the "flash-all-partitions-fastboot.bat" option and still nothing.
Also, I just tried to make TWRP backup and it failed on the user data with "createTarFork() process ended with ERROR: 255"
Click to expand...
Click to collapse
Isn't the 255 error due to the parallel apps thing!? you have to delete all the user 999 folders I believe.
Eric214 said:
Isn't the 255 error due to the parallel apps thing!? you have to delete all the user 999 folders I believe.
Click to expand...
Click to collapse
Didn't know that, however I did just wipe userdata, flashed new OS, still rebooting...Wiped internal storage and now it works. I have no idea what the problem was. Luckily i back everything up to google.
sounded like your data partition was corrupt
Is your bootloader unlocked? If it is then fastboot roms should work. If it is not then I might try the mega unbrick guide
Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.
only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..
noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.
Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy
I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
did u remove your magisk modules?
Maybe the backup was from slot A and OTA in slot B and something got messed up. In another note there's no need to clean install OTAs from Oneplus, and then having to restore old data is where complications come
Karmonator said:
I had rooted my phone on OOS 9.5.8, installed TWRP and magisk, i updated to 9.5.10 without issues, tried installing TWRP again as well as magisk, and my phone went on a bootloop, after several hours of trying to fix it, i decided to use my twrp backup thinking that would fix the issue, i restore everything and my phone is still bootlooping, any ideas how to fix it?
Click to expand...
Click to collapse
I had this problem, minus the TWRP. I had to reset to factory default to fix it. Goto bootloader and reset system settings. You'll end up back on 9.5.10 stock but you should be able to boot. Pain in the ass but it stopped my loops. I didn't have a x.x.10 backup so I had to start fresh.
Try to remove Magisk using Magisk unninstaller and reinstall 9.5.10 on TWRP without rebooting.
After, install TWRP installer again and THEN reboot.
After you check all is working, install Magisk again in TWRP and then install your Magisk modules again.
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.