Guide to Update OOS ROM on rooted phone without loosing TWRP - OnePlus 5T Guides, News, & Discussion

Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.

Reserved

Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.

Lossyx said:
Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.
Click to expand...
Click to collapse
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.

kapil_dheer said:
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.
Click to expand...
Click to collapse
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.

FMXP said:
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.
Click to expand...
Click to collapse
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.

kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.

paour said:
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.
Click to expand...
Click to collapse
Yep, same here, I've also flashed TWRP img right after flashing the ROM, just to be sure it's still there, then Magisk zip and custom kernel, everything works fine, no bootloop here.

kapil_dheer said:
Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.
Click to expand...
Click to collapse
Thank you so much after trying everything and still getting bootloop your method worked.. ?? thanks for such easy solution

kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop

Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.

Lossyx said:
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.
Click to expand...
Click to collapse
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.

I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?

perama said:
I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?
Click to expand...
Click to collapse
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!

rquinn19 said:
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!
Click to expand...
Click to collapse
Thank you very much my friend!

BigBrosMo said:
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.
Click to expand...
Click to collapse
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk

jmtjr278 said:
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Wiped caches in between ya. I don't use substratum but I do use xposed though Magisk. I think it has to do with that but am not certain. At any rate, I just use the uninstaller (it's two extra clicks) and don't have any more problems. This was back in January that I had these flash/bootloop problems. Maybe it's not an issue anymore but I just have my routine and it works so...

My steps are when i was in 5.1.1 OOS ( I modified some system parts so downloaded full 5.1.2 OOS firmware)
Removed Pattern/Password (For Safety)
Enter TWRP
Wipe Cache
Wipe Dalvik Cache
Wipe System
Flash 5.1 .2
Install TWRP.img
Flash Magisk
Flash No Verity zip
Reboot
No PC needed. Yea its booted and all apps are there. No data lose..

Flashing uninstaller was not successful when I tried to install 5.1.1 and 5.1.2.
Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse

I use the simple method of downloading the full Update ZIP to my phone, rebooting to TWRP, clearing caches, flashing the Update ZIP, flashing Magisk, clearing caches and reboot. That way always worked for me.
No need for such a complicated process based on my experience.

Related

Stuck in Boot Animation

Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Sui77 said:
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Click to expand...
Click to collapse
Do you have twrp? If yes, flash stock rom.
WesTD said:
Do you have twrp? If yes, flash stock rom.
Click to expand...
Click to collapse
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Sui77 said:
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Click to expand...
Click to collapse
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
WesTD said:
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
Click to expand...
Click to collapse
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
I use aosp bases.
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Sui77 said:
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Click to expand...
Click to collapse
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
WesTD said:
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
Click to expand...
Click to collapse
Also Root Explorer, root granted.
Sui77 said:
Also Root Explorer, root granted.
Click to expand...
Click to collapse
Can you just leave the 5 sec screen alone? You can kill your phone, and there doesn't seem to be anything you can do really.
If you're insistent, you can find it under Themes Apps and Mods, called "We remove the inscription that the bootloader is unlocked" made by NFound1.
And about the restriction to modify the system, connect your phone to a PC with ADB, fire up ADB and configure it (USB debugging, ADB over network if you have the option, permit the connection) and issue 'adb reboot disemmcwp' (disable emmc write protection, that is. Write it just like that or your phone will reboot and you will still have the protection active).
The phone has its difficulties and all but it's easy to work with once you get the hang of it. And, you know, your big cores don't just die all of a sudden, which is a good thing!
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Sui77 said:
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Click to expand...
Click to collapse
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Choose an username... said:
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Click to expand...
Click to collapse
I tired to flash a B5 an B5 bootstack with TWRP 3.1.1 -> not able to boot
Then i flashed, according to your guide, the stock recovery and now the device seems to be really bricked.
After the ZTE logo a lying robot appears for half a second and after that, the device is dead.
Can't boot into TWRP, can't use adb, EDL, ...
Ok, managed to get back TWRP.
But I really don't know how so solve my issue of how to come back to stock :crying:
Flashed a B05 stock (zip) and B05 bootstack and Magist....stuck in boot animation (AXON picture collage).
Fu....
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
to go back to stock, download the full zip of any version you want, and download stock recvovery from b08, you have flashed it.
from twrp, format data, and try to boot, if you cannot, reflash b09 recovery from twrp, select image and the recovery you download, then go to stock recovery and update from sdcard. it allways work for me, if you stuck in boot animation again, reboot recovery and wipe data.
after you succesfully boot, reboot edl, and reflash twrp, the version you were using before witn axon7tool, thats all
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
Just follow my guide for that. If you flash the B04 recovery (the one i provided) you shouldn't have any trouble
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Sui77 said:
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Click to expand...
Click to collapse
What B05 bootstack? You have to use the universal bootstack and the A2017G modem file...
Both are on the LOS thread. It seems weird that carbonROM would even boot without the universal bootstack though

Slot_A-B How to Flash Roms/Magisk/Kernel 8.1???

How To Flash Roms with the Ridiculous Slots... yep. You're a rookie again because these things are going to drive you onto a drunken crazy bender... You'll probably wake up in Mexico married to someone you've never met and tied in with the Chicago Mob in debt for a quarter million. THIS IS WHAT WORKS FOR ME. I do the same thing Every time and have done this wrong so many times I've lost count.
Note number 1...
You have or know how to use adb and fastboot basics... if not... Of not Google the Adb and fastboot set up for your devices and/or PC/Laptop etc... There are a lot of forums and Q&A on setting this up to get fastboot cmds running. You should be familiar regardless and at least have the stock flashall.bat for a Google Stock IMG JUST IN CASE. I am assuming everyone is already at the install for TWRP and is working with 3.2.0-0 only. You cannot flash roms without it. Any other version for 8.1 will NOT work at this time...
Note number 2...
Roms will vary. Some may include the vendor image and you don't need to flash it. Some may include gapps and you don't need to flash those... Some may include everything and have you flash to slot_a and that is all. In other words do what the OP says, they built it. They know what's in it and how it works.
Here's the trick... It doesn't mean you can't do these in any other way but you will NOT get stuck if you follow some simple rules...
Roms only flash while in Slot_A
Gapps only Flash in Slot_B
Kernels only flash in Slot_B
Magisk only flash in Slot_B
IMG Flash to Slot_B
TWRP 3.2.0-0 ONLY
TWRP 3.2.0-0 to either slot
Do NOT EVER Flash anything other then TWRP, Rom Gapps and Vendor until GOING through first boot. Yes you can but it increases your issues.
Always always always double check between every install the status of your Overlays folder. Before every rom install Mount System then Go to File Manager and Delete that folder from Slot B before you boot to Slot A to flash the rom. This can hold Data from Magisk and Mods that get all tore up Everytime... It also happens when you reflash Magisk or dirty flash a rom. I'm going to put together a fresh flash below and I'll get into that a little later.
So from stock Google image...
Clean flash... MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Either... Reboot recovery (you'll be in slot B) if you already have TWRP installed....
Or....If you're just booting TWRP for the first time...from bootloader you fastboot boot (not flash really the terminology is BOOT) TWRP-3.2.0-0-marlin.img (you'll be in slot B)
Read your bootloader screen or go to TWRP 3.2.0-0 Reboot menu to find out which slot you're in.
FLASHING YOUR FIRST ROM...
note... Most are going to require before flashing your coming from stock. Just do it. At least the initial install... Dirty flash or clean flash after that without going back to stock but you don't have to flash the stock image.
Ready... You're in slot b remember...in order here...
- Wipe Data System Cache
- Flash TWRP 3.2.0-0 the ZIP
This is why you can't have your lockscreen on... If you didn't listen just go back to your bootloader and start over with the flash-all.bat. Sorry but I warned you... You can't get anything to flash at this point because you can't decrypt 3.2.0-0.
- Go to MOUNT then make sure your system box is checked
- Go to ADVANCED and then File Manager and make sure you have no overlay folder. If you do... click on it and hit delete from the options on the bottom portion of TWRP.
- HIT HOME and Go to the actual reboot menu choice (Not the swipe reboot system)
-Click on slot_A and then reboot back into recovery. ...NOTE... I usually don't use the reboot recovery option.(reboot recovery seems wonky and doesnt work for me all the time) I reboot system and just hold volume down until I hit the bootloader and the choose recovery in the bootloader options...
You ARE in Slot A now... Right... You can Double check in the bootloader or TWRP in the reboot menu.
- if you really really really like to wipe you can wipe Data system and cache in Slot_A... I never do from slot_a but to each their own.
- Flash rom and flash TWRP 3.2.0-0. Nothing else.
- Reboot back to recovery again.
You ARE in slot B. Yep automatically... When a rom is flashed it goes to the opposite slot. And reboots you there on the next recovery reboot so DO NOT GO change your slot to B unless an OP actually directs you to do so.
So... We're in slot B
- Flash Gapps and Vendor... nothing else until after you boot up.
Yeah yeah... You want to be rooted... Well boot up first and we'll hopefully be able to walk through that too.
Your booted up. Go to your development options and double check to make sure USB Debugging is enabled... Really whatever, you're really pretty safe if you have Your fastboot drivers and they must be installed because you installed TWRP to get this far so if something goes wrong from here we can still always do the flash-all.bat so your phone shouldn't implode and brick out.
Reboot recovery. Yep you're in slot B... You should now always boot recovery to slot_b unless you mess something up and get stuck in a loop. I've seen it but couldn't duplicate. It was always me flashing out of order.
GAINING ROOT... MAGISK INSTALL
- Choose the zip, flash and reboot.
Nothing further needed, make sure it's compatible with 8.1 and at least 15 to 16 are Oreo compatible. Easy right.
Well even when I'm updating... the wonderful Overlay folder can get jacked. I'm pretty sure I've heard it laugh at me as I stuck in bootloop after bootloop... If you delete the overlay folder anytime BEFORE you update to the next version of Magisk you'll be ok
UPDATING MAGISK...
So if you're on 15.3 and you want to get to 16.0 without getting stuck or having issues on boot.
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
MAGISK AND KERNEL
To get Magisk and a kernel going can give you to madness. It gets a little tricky. But honestly devs have really really improved the process. If you're rooted already most you can flash reboot into the rom reboot to recovery again and then do this again...
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
For the most part the current kernels do not blow out your Recovery anymore however some do. In fact the only one I know that will is Noexezshades. Probably spelled that wrong but you'll catch my drift if you read his OP.
SERIOUSLY YOU BETTER ALREADY HAVE BOOTED INTO YOUR ROM FOR THE FIRST TIME.. You'll hate your life if you set this up during your initial install.
INSTALLING KERNEL WITH MAGISK
- Reboot Recovery (hahaha. Ha. You turned your fingerprint scanner on... Reboot and turn it back off)
- Flash Magisk
- Reboot
I know... right now you're saying WTF... I didn't flash the kernel. This is just a fail safe... Points in Any Kernel need Root to install... I haven't had issues but really probably because I always flash Magisk first.
If you already had Magisk installed start here.
Now we're going to Flash the kernel. It's going to unroot you so we'll just immediately install Magisk I recommend always installing Magisk after a kernel because it also Patches the boot otherwise there are times when patching the boot.img is required however I believe most DEVs have surpassed that FOR MOST KERNELS.
- Reboot recovery (Dang. You forgot to turn off your fingerprint sensor again, sorry life's rough turn off your lockscreen again)
- Flash kernel
- Reboot system
- Reboot recovery (you might lose TWRP however every Newer version I'm using--- unless noted by the OP--- is working at present)
- DON'T flash Magisk... No dont flash Magisk. If you were following along you can see you need to go delete the overlay folder before you flash Magisk it will almost always go bad at this point if you don't delete the overlay folder
- Flash Magisk
- Reboot.
Hopefully you learned what's happening now in the background. I try to explain things from a user level and do this as part of my daily work every day. I don't understand things unless someone tells me what's going on along the way and keeps me partially entertained...
Talk amongst yourselves or don't post Anything. The goal is to take the issues out of the day to day so the devs aren't getting the questions.
I'm gonna have to read this post a couple of times to get the hang of it. I'm kind of a newbie.
Great post. Thank you for the write up. Helps to understand twrp when dealing with two partitions
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Sent from my Pixel XL using Tapatalk
pkelly517 said:
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Click to expand...
Click to collapse
It'd be neat if I could edit my post from the XDA app. My screen and back glass broke... then the earpiece blew out so I was awaiting parts and haven't been online
I need to go away from the option of even flashing TWRP at kernel install. As everyone updates their kernels... I see it starts a looping issue now. Everything else is solid.
overlay folder
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
-Happy Feet- said:
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Mikkey81 said:
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Click to expand...
Click to collapse
Thanks for your help, great explained for an pixel Beginner.
Gesendet von meinem Pixel XL mit Tapatalk
beezza said:
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
Click to expand...
Click to collapse
Go to TWRP.
Open Mount and click to Mount System
Open Advanced and then choose File
If you find a folder in your root named 'overlay' tap on it (select it) and then click on delete.
If it's not there.... great. You've probably never rooted. It'll cause some bootloops once in a while, sometimes it doesn't matter. It's more important to do this at the point of flashing a room because you most likely will not get a fresh install to boot up if you're rooted.
Quick Note: This file carries over Magisk root data and gets messy as you update Magisk or reflash it.
I tried installing latest magisk on android "P" and was on Slot-B and it wouldnt install, error...
changed to slot-A and then it installed..
Magisk v16.3 (1630)
Thanks for info. good stuff i am new to pixel coming for my old friend nexus 6
just fyi I downloaded and flashed twrp-3.2.1-2-marlin before reading this and just happen the passcode thing for me is not a problem. Had to enter it twice the first time using twrp but now just once. works fine.
I don't give nearly enough appreciation where it's due but I gotta hand it to you... By far the best guide ever! Thank you!
Very good details and advice. I'm having far else problems by following these steps. Thanks for all your work.
commenting here to save this for future.
thank you OP!
hoping this thread is still alive. . . is there a recommended factory image to restore to? do i need to flash the factory on both slots? is it best to flash -the factory system.img on a particular slot? In the end which slot to --set_active=?
And how do the SLOTS come into play for doing a TWRP backup and doing a TWRP restore ?

Can't Boot after OTA Open Beta 5 -> 6

Hi, I just dirty flashed my phone through OTA from OB5 to OB6. I currently can't boot into my phone, but recovery and everything works.
I'm using twrp 3.2.1.0 codeworx. I can boot into my lockscreen but the moment it loads it says "Shutting down". If I install Magisk 16.0 it just tries to boot, then fails and jumps to recovery.
At least my data isn't encrypted anymore, but what can I do about this? When I try to sideload the OB5 ROM it says can't read zip.
Also it's interesting how my recovery gets reset every time that happens.
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
SventraPopizz said:
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
Click to expand...
Click to collapse
Thanks for the suggestion. I also feel a feeling that it's substratum because I made the mistake of updating with layers still installed. I tried flashing the substratum rescue zip, both legacy and non-legacy, and also deleting the file as you suggested but I'm still getting that immediate "shutting down" error.
chazarss said:
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
Click to expand...
Click to collapse
For my personal experience, I took the OTA and had no problems rebooting. I'm also fully stock with no root or custom recovery; I don't know if that affected my flash and reboot. I bought my OP5 used from Swappa. When I got it, I clean flashed the OB5 and then today I took the OTA for OB6.
I was on ob05, twrp 8.71. Received ota, full zip, on the phone. Dirty flash workt fine for me. Phone booted ok. Of course, recovery was gone. Reflash recovery. Reboot to recovery. Flash Magisk 16. All ok.
Bootloop was caused by https://forum.xda-developers.com/oneplus-5/themes/op5-oos-oreo-official-fix-blue-3rd-t3727238/ for me. After disabling the module with https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 it's booting properly

Root lost after 9.0.13

Hey guys.
Just updated to 9.0.13 last night and today I saw that my root was gone.
I was rooted with Magisk, and did the same as usual. Uninstalled Magisk, downloaded and install the update from System, and after that I Installed Magisk on the second partition (after OTA update) just like in the tutorial..
Any solutions to regain root without wiping the phone ? I already fuc*d it up last month and lost everything .
Regards,
Switiz
In my case it installs magisk after updating and everything worked fine. Reinstall it from the TWRP and it should work.
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Switiz said:
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Click to expand...
Click to collapse
How did you get root without flashing magisk inside of twrp? And if you did the update that came thru your phone that's why you lost root.. from what I read it's best to always flash full stock. No partial updates
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Thank you. I will try when I get home.
I update using the tutorial from the page you provided :/.
"Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete."
It's not the first time. I don't know why this time it didn't worked..
After booting in twrp and installing Magisk, after reboot, I still don't have root :|
https://imgur.com/a/hjGwQkR
Try this
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238
OhioYJ said:
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Click to expand...
Click to collapse
Thanks for this link.
Not sure if you've managed to fix this issue, but I've never used to the uninstaller. I boot into TWRP and flash the full system image and then reboot back into TWRP and flash Magisk onto the active partition. If you don't reboot inbetween then you end up flashing Magisk to the current (old) partition rather than the new upgraded partition.

Always boot in recovery mode after an update

Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?
yes
null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage
you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server
Have you tried formatting data?
Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?
fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.

Categories

Resources