Database Info

After OTA update phone shutdown on startup

Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance

Just in case, I successfully got on the fastboot and then used "fastboot" command to boot on TWRP. I am now making a backup of "/sdcard".
But I would really like to not have to make a factory reset... Is there a solution to avoid this?

Flash ROM and flash Twrp
Reboot
Shutdown
Boot on twrp
Flash magisk
Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake [emoji6]
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

I succeeded in fixing it by installing twrp and doing... I don't really remember what lol, but I was able to uninstall Magisk and reinstall it with twrp, now everything works again!
"Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake"
Yeah, I thought it was the most safe way to update but it seems that I was clearly mistaken.
Thank you anyway!

I've updated like that a couple of times now and it always work. Most likely you had modules that made you not being able to boot.

hey, the error is that you need START the update using the standard OTA interface (don't reboot), and then go to magisk, and install to second slot. Afterwards it will reboot. What you did is configure your phone to boot from the second slot but the update wasn't ready or something like that. I don't know the technical details but I did the exact same thing on the last update, and I've learned from my mistake
In that case, you can change the slot using fastboot, I think that's what I ended up doing. It took me like a whole afternoon to figure out the mistake. I'm hoping this warning is useful for future updates.

It will be useful yes, thank you for the clear explanation!

noom4_5 said:
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Click to expand...
Click to collapse
Flashing magisk uninstaller fixes this.

*system error* said:
Flashing magisk uninstaller fixes this.
Click to expand...
Click to collapse
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?

tamamma said:
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213/page5
If you are on Android 10 beta 1

Installing OTA after TWRP + Magisk = fail to boot

I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?

These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot

RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?

Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.

whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!

Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.

Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".

I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).

I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick

RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).

Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread

RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.

Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.

What did I do wrong during the update?

Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?

Did you uninstall Magisk modules First?

null0seven said:
Did you uninstall Magisk modules First?
Click to expand...
Click to collapse
I didn't. The whole point of doing it the way I did was to eliminate the need to uninstall the modules.
Could that be what went wrong?

YES.

null0seven said:
YES.
Click to expand...
Click to collapse
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?

JohnsNotHome said:
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
Click to expand...
Click to collapse
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot

Arden144 said:
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Click to expand...
Click to collapse
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.

JohnsNotHome said:
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
Click to expand...
Click to collapse
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368

The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again

mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Interesting.. I think I'll just follow this method. This was all in the name of saving time.

mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Arden144 said:
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Thank you so much for this. I think I understand now.
I hope I haven't caused any problems to the slots thing on magisk with the mistake I made.

1. Uninstal Magisk mods.
2. Flash Oos in System > Update > Local Update. DON'T reboot.
3. Open Magisk > Downloads > TWRP A/B Retention script. Instal it.
4. From Magisk reboot to twrp. Flash Magisk 19.3 stable.
Reboot to system. You should be updated and rooted.

broke my phone because I was lazy

So I updated my phone to the newest firmware (international version) but I didn't look up how to do it properly because I thought it would be like the op8pro I was wrong
I disabled my xXx module, ran the update and with magisk 20.1 I installed to the inactive slot and it rebooted with no problem. but then not researching what to do next I just switched my module back on and it is now stuck on a boot loop
So my question is, is it going to be possible to restore the phone and keep intact the data or I'm just gonna end up swiping it clean in the process.
Thanks

Ar3olaa said:
So I updated my phone to the newest firmware (international version) but I didn't look up how to do it properly because I thought it would be like the op8pro I was wrong
I disabled my xXx module, ran the update and with magisk 20.1 I installed to the inactive slot and it rebooted with no problem. but then not researching what to do next I just switched my module back on and it is now stuck on a boot loop
So my question is, is it going to be possible to restore the phone and keep intact the data or I'm just gonna end up swiping it clean in the process.
Thanks
Click to expand...
Click to collapse
Delete the magisk modules in root/data/ADB/modules .... Using TWRP

@soka said:
Delete the magisk modules in root/data/ADB/modules .... Using TWRP
Click to expand...
Click to collapse
My twrp is gone do I install it with the one click root app ?

Ar3olaa said:
My twrp is gone do I install it with the one click root app ?
Click to expand...
Click to collapse
Hopefully you have an unlocked bootloader.
Flash TWRP.img using fastboot
fastboot boot TWRP.img

Upgrade to android 12

What is the process to upgrade and keep root? Is it the same (flash magisk into partition a/b after upgrade?)
Thanks

kevkid said:
What is the process to upgrade and keep root? Is it the same (flash magisk into partition a/b after upgrade?)
Thanks
Click to expand...
Click to collapse
after flashing the ROM, you need to flash magisk.zip.. that's all brother

Spuffyffet said:
after flashing the ROM, you need to flash magisk.zip.. that's all brother
Click to expand...
Click to collapse
Isn't it possible to install magisk to inactive slot after update and before reboot any more?

epr said:
Isn't it possible to install magisk to inactive slot after update and before reboot any more?
Click to expand...
Click to collapse
Yes, you can do that as long as you do a manual install. Not if you let the System Update do a "download and install".

BillGoss said:
Yes, you can do that as long as you do a manual install. Not if you let the System Update do a "download and install".
Click to expand...
Click to collapse
So if I want to update from OOS11 to OOS12 I have to download the full image, do a manual install via system - updates - local upgrade, install magisk to inactive slot and reboot?
The way it used to be (system downloads the full image and installs it - magisk to inactive slot - reboot) is no longer working? Why? Isn't it the same?

epr said:
So if I want to update from OOS11 to OOS12 I have to download the full image, do a manual install via system - updates - local upgrade, install magisk to inactive slot and reboot?
The way it used to be (system downloads the full image and installs it - magisk to inactive slot - reboot) is no longer working? Why? Isn't it the same?
Click to expand...
Click to collapse
What you're proposing may work (the OOS 12 OTA is a full image). But with incremental OTAs you can't let the system download and install and then install Magisk to inactive. It breaks the installation.
So, your phone - do it your way and let us know the result. That we all learn something out of the process.

BillGoss said:
What you're proposing may work (the OOS 12 OTA is a full image). But with incremental OTAs you can't let the system download and install and then install Magisk to inactive. It breaks the installation.
So, your phone - do it your way and let us know the result. That we all learn something out of the process.
Click to expand...
Click to collapse
OK, thanks.
I'll try with the OTA as soon as OOS 12 is available for my region (EU, KB2003).

epr said:
OK, thanks.
I'll try with the OTA as soon as OOS 12 is available for my region (EU, KB2003).
Click to expand...
Click to collapse
I went back and read what I said in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/ which was:
You also need to know that if you let System Update download and install a delta update, then you cannot make any changes to the updated partitions until after the phone has rebooted otherwise the update will fail.
Click to expand...
Click to collapse
So you're ok with doing what you suggested.
Ah, the joys of getting old and forgetful!

BillGoss said:
I went back and read what I said in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/ which was:
So you're ok with doing what you suggested.
Ah, the joys of getting old and forgetful!
Click to expand...
Click to collapse
Same fits to me.
Not the youngest anymore...