Database Info

Boots to OS but immediately shuts down and reboots to recovery

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?

Booting/Recovery issues, Need help. (yes I researched)

Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?

eracet said:
Going to try to give as much information as possible so it will help me figure this out.
I have been working with Renovate module and rom/ Different magisk etc.
The display within the settings has been always messed up and crashes upon using.
So someone suggested a factory reset.
Pre-reset. I did a nandroid backup as well as Titanium backup , and google sync just in case.
Then everything was fine. But had some issues with Magisk installer. Basicly it was not correct and root didn't work correctly.
Flashing some module updates and newest Renovate update.
Then going back to reboot, all of a sudden it goes into fastboot mode.
Tried restarting in recovery , and it would not. It always wants to go to fastboot mode.
Posting and getting some advice (Thanks) they said I bricked my phone.
I tried everything I could to get data that I did a backup of off my phone (This is where I with it was micro SD)
Finally got into TWRP VIA fastboot boot ( had to change active slot) and it was encrypted.....
Booted again using Bluespark via fastboot (Think it was slot b this time) and was able to get a full SD backup onto PC.
Thinking this is going good, I flashed bluespark into slot b?.
Well it never took, and just showed a white light on top , the notification light.
Tried a few flashing VIA fastboot, and last thing I did was fastboot boot an official TWRP, to a slot that worked.
Tried Msmdownloadtool, and various other ways to get stuff going.
Tried Fastboot flashall and fails as well
Can anyone help me get the phone back so recovery works or help in any way?
Click to expand...
Click to collapse
UPDATE: When booting into TWRP 3.2.2.0 it gives me encrypted files. When booting into TWRP 3.2.3.0 it gives me non-encyrpted files and asks for password.
Booting anything to slot A gives me a load error. failed to authenticate.
Update2: Now I cannot get Bluspark TWRP or stock recovery to load VIA Fastboot. Only TWRP 3.2.3.0 works and loads correctly
Update 3: Keep having to do different versions of TWRP to get anything going, even tried OTA and did not work.
Update 4: Phone wants to boot into Qualcomm HS-USB Diagnostics mode when light is on.

Found you
Next time tag me
I'm the same guy on the oneplus forums
Send me a private message here or on the oneplus forums and I'll take it from there

Update: I have resolved the issue. Please do not post any further comments on this because
The issue is already resolved, duh

There is apparently no way to restore a Nandroid backup under OOS 9.0.4...???

So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW

MetroWestMA said:
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
Click to expand...
Click to collapse
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
perhaps some remarks:
if your' phone is "empty" as you stated i recommend to first install factory image / stock rom latest OOS, i.e. 9.0.4
make nandroids of each partiton speparately and also restore them separately while don't nandroid the images, and cerrtainly don't restore those, only common partitions like system, boot, vendor, data.
system and vendor are present as normal partition as well as image partition, don't touch the later in any way.
all this only works if you restore on a phone that was bootable before you restore, for restoring to empty phones there are other procedures via fastboot commands and or stock rom via stock recovery if it's on device, else ADB comes in handy.
last but not least if you restore you have to restore everything, not only one partition especially not only system partition, won't work well or not at all depending.
1. Modem if corrupted, else not needed
2. EFS if corrupted, else not needed
3. Vendor start here if the previous rom was running well and make sure it's not been altered or you have to correct vendor backup in case you have more than one
4. System
5. Boot
6. Data
good luck

magnamentis said:
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
good luck
Click to expand...
Click to collapse
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW

MetroWestMA said:
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
Click to expand...
Click to collapse
the last restore i did on 9.0.3, since then i gave up on custom roms since OOS rooted + a few useful apps make OOS close to perfect for me
i'd not delete the thread, many reported issues with nandroids because the normal procedure to take one single backup and restore from twrp to an empty device does not work, one always need to first flash stock OOS to a clean slate before installing anything else or restoring anything.
and backups should be in increments not one single backup like it was possible on single slot devices.
restoring one single partition usuelly ends up in a mess except boot partition, boot, efs and modem can be restored as standalone restores without issues in most cases while flashing a kernel + magisk is still easier and safer than restoring a boot partition.
as to setttings i dunno what you mean, exactly and as to encryption, my device is and has bee encrypted at all times.
it's most important to use twrp- recovery by blue_spark, official standard recovery has issues ( at least always had as long as i tried using it) especially with verification in TWRP on encrypted devices. there is a risk to end up encrypted without any way to boot back into system or into twrp menu, hence use blue_spark's and all is well, user error exempt of course

Since reinstalling everything is going to take forever (at least another 4 hours)...I am going to disable encryption and do some more testing. I am now more certain than ever, no-one has successfully restored a NANDROID on an encrypted OOS 9.0.4 phone ever.
I am going to disable Force Encryption and AVB 2.0/dm-verity and try my restore again -- maybe then I can use one of my NANDROIDS. But doing this on an encrypted phone seems impossible. I guess if you use a screen PIN you files are still vulnerable to someone that knows bootloader and / or recovery, but I'll have to live with that.... Not being able to NANDRIOD restore is a killer...

I know is an old discussion but I believe we still have this issue. I have a 6T, oos10.3.6 and neve succeeded to restore a nandroid backup. Does anyone found a working solution?
Thanks

Fastboot loop/No TWRP on default slot but can change slot and access TWRP.

New to the A/B slot root scene, apologies. I also searched but couldn't find an answer for something matching this exact specificity . I know its fixable but I cant figure out what would be best to do.
I am (or was) running TWRP/Magisk on 10.3.4 Stock OOS. broke the OS boot and it will only goes right into fastboot, no TWRP anymore, doesn't even show the warning from OP when booting a rooted OP device.
Weighing my restore options, I changed the active slot with the fastboot command and that slot was able to boot into TWRP just fine, however, the mounting folder that's usually emulated/o (SDcard) was just a bunch of folders with random text and capitalization.
I have a TWRP backup (around 8GB) . Can i just change the active slot back to the non active one and restore to the other? I am concerned i will break it worse or restore it to the wrong slot somehow. If i restored it to both slots, would that be ok?
edit: I connected my TWRP backup and wasn't able to force the restore to another slot. The backup includes Boot, System, Data (excluding storage) and EFS. I could "swipe to restore" at any moment but unsure how that would effect everything seeing as the backup was done on Slot A and now I am on slot B.
I read you should flash the 10.3.4 full while staying on the same slot but was having issues getting it to upload to the phone (no drive mounts on my computer OS on the default slot, only can do so when i change slots) I have a very recent titanium backup i can restore once i am back in, either way.
I am just not 100% exactly how to get myself back up and running.
Lastly, i only started rooted again after a 10-15 year break because I got real sick of the background data the official OOS build was sending. I was interested in converting to LineageOS with gapps form Micro (if it can pass safetynet) but Open to any ROM that could assist in stopping the official background activity. I would love a ROM that can pass safetynet, help with the battery life on my aging OP6 and hopefully keep rocking on Android 10.
Thank you to everyone or anyone that reads this and assists. I know it must be annoying to read what may just be the same question over and over but this exact issue was hard to find another experiencing with the latest OOS.
Take care.

I ended up trying to restore the TWRP backup to the different slot, this put both slots in a fastbootloop. i then flashed all partitions with a fastboot image of 10.3.4 and this fix my phone and got it back up in running. i rooted again, flashed twrp and then tried to restore the TWRP backup again and it completed successfully, however, both slots were back to bootlooping.
i will just wipe all again, root/magisk and then install titanium to restore my full backup of that. Im sure ill be coming to a new issue trying that too, but who knows.

I fixed it the way i wanted (off the backup i made with TWRP) by restoring my backup (without EFS this time, per the tips on the devs website, rebooted into fastboot, flashed the OOS 10.3.4 fastboot image (WITHOUT -w to keep my user files), let it run. when it rebooted i had everything back from the TWRP backup!.
all i did then was boot the TWRP image, flash its zip, then flashed magisk again and rebooted.
All is well! (until Slot B issues rear their ugly head) I really hope to flash both and move to a custom ROM but saying encrypted is more important to me than I thought it was.
I hope anyone who finds themselves in the same stupid situation is helped by this come day.
PS. titanium backup is really not a system restore feature like I thought it would be when you are encrypted. TWRP was my only viable solution and so happy this worked. Ill be running that weekly, for sure.

Question What is the best way to recover files on OOS 12 while bricked

Hi everyone. So I am on OOS 11 and the main reason I am on OOS 11 is because of TWRP. I like to tinker and mess around with the phone. I have bricked the phone about 8 times. I have always been able to recover files via TWRP so I didn't want to move to OOS12 simply because I didn't want to back up everything every time I try a new module or tweak and etc.
However, OOS 13 is coming and I really don't want to stay on OOS 11 forever. So I am reaching out to get advice and ideas from the community on what is the next best thing to recover files if I soft brick the OP 9. Is there an alterative recovery that will give me access to files?

I've been working without twrp since my oneplus 7t, for example, and I back up my data (internal storage) on my pc and my apps with both google backup and swift backup.....
and since there is no twrp for oos 12, the only option left is to flash mods via magisl, which in turn has the advantage that if you flash a module that causes a bootloop, you can remove it when booting via adb (and even if you have a module flashes and it is not deleted in a bootloop, then you just flash the stock boot.img and can boot into the system without root and then save your data )

ChrisFeiveel84 said:
I've been working without twrp since my oneplus 7t, for example, and I back up my data (internal storage) on my pc and my apps with both google backup and swift backup.....
and since there is no twrp for oos 12, the only option left is to flash mods via magisl, which in turn has the advantage that if you flash a module that causes a bootloop, you can remove it when booting via adb (and even if you have a module flashes and it is not deleted in a bootloop, then you just flash the stock boot.img and can boot into the system without root and then save your data )
Click to expand...
Click to collapse
I do use Magisk module for most parts but there has been a number of times where restoring stock boot.img or removing modules does not fix soft bricks. On the plus side, when this happens, usually it just require a factory reset (no data wipe) and it boots back up. What I am worried about is if I am forced to us MSM.

you can take precautions such as making regular backups and synchronizing your data that is in the internal memory, e.g. with your pc (as I said before, i back up my apps with google and swift backup)
I've bricked my cell phone a few times, but I have to say I've always gotten it to work with fastboot/fastbootd (tried a few things).

ChrisFeiveel84 said:
you can take precautions such as making regular backups and synchronizing your data that is in the internal memory, e.g. with your pc (as I said before, i back up my apps with google and swift backup)
I've bricked my cell phone a few times, but I have to say I've always gotten it to work with fastboot/fastbootd (tried a few things).
Click to expand...
Click to collapse
Looks like that is the best thing to do when we can't use TWRP, I guess I just need to me more cautious and backup anything important. I have been spoiled with TWRP for all these years. Thanks for responding.