Database Info

Installed twrp phone reboots to twrp

I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files

cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?

Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal

cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...

alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/

Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)

alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.

phone has lost root issue

I used magisk on my phone for roots right but it has lost roots. I tried to go into recovery to reinstall magisk but recovery isnt booting, when it select advanced it gives me fastboot or recovery options but when I select recovery its goes back to the start again. I have tried to reinstall TWRP using this method
https://www.xda-developers.com/official-twrp-oneplus-6-huawei-p20-pro/
but I then get a crash dump window.
Please can I get some advice how to proceed?
Thanks

Make sure you're using 3.2.3, anything prior to that is not for Android Pie. If you updated your OS that is more than likely the reason you lost root. Make sure that you download TWRP.img and fastboot through the image before you try to install TWRP permanently

dgunn said:
Make sure you're using 3.2.3..............
Click to expand...
Click to collapse
Aha! I did wonder but I followed the guide to the letter as I thought I might brick the phone if I risked the other imgs. I did sort it by using a different TWP file.
Regards

Westindieman said:
Aha! I did wonder but I followed the guide to the letter as I thought I might brick the phone if I risked the other imgs. I did sort it by using a different TWP file.
Regards
Click to expand...
Click to collapse
Good deal glad you got everything working.

I'm on stock android 10 and I have accepted an update I was offered yesterday. It seems everytime I update I have an issue rooting and installing TWRP (last month I was bricked), maybe because I use the last TWRP version I have before the update (currently twrp-3.3.1-1-enchilada). What is the correct process for installing TWRP and rooting again with Magisk? Do I need to get a TWRP update each time?

You have to install the latest one (3.3.18).
Reboot fastboot, type fastboot boot 'recoveryname'.img, once time you are in twrp flash the installer from the inside. Reboot to recovery again and flash magisk.
When you need to update you have two ways:
1 download the full ROM zip and place it in your main storage folder (sd card);
Update via local update but don't reboot;
Open magisk and download and install twrp a/b retention script and don't reboot yet;
Go in the magisk main page and install it as installation in the inactive slot (after OTA);
Reboot and enjoy.
2 download the full zip;
Reboot in twrp;
Flash rom + twrp installer;
Reboot to recovery;
Flash magisk;
Reboot and done.

°Washy said:
You have to install the latest one (3.3.18).
Reboot fastboot, type fastboot boot 'recoveryname'.img, once time you are in twrp flash the installer from the inside. Reboot to recovery again and flash magisk.
When you need to update you have two ways:
1 download the full ROM zip and place it in your main storage folder (sd card);
Update via local update but don't reboot;
Open magisk and download and install twrp a/b retention script and don't reboot yet;
Go in the magisk main page and install it as installation in the inactive slot (after OTA);
Reboot and enjoy.
2 download the full zip;
Reboot in twrp;
Flash rom + twrp installer;
Reboot to recovery;
Flash magisk;
Reboot and done.
Click to expand...
Click to collapse
Some good news, it all went smoothly this time and thanks for your help. Really helpfull into there about updating too. Many Thanks

Westindieman said:
Some good news, it all went smoothly this time and thanks for your help. Really helpfull into there about updating too. Many Thanks
Click to expand...
Click to collapse
Np man. If you wanna make me happy press like button

You know, sometimes its too easy to forget to do that.

Update with root/unlock

I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?

Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.

Anyone know how to root if I'm already on 9.5.6?

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.

I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.

larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.

The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk

larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions

OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you

With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk

skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.

Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi

Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.

Updated to 9.5.9 and now it reboots into TWRP over and over.

I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.

what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.

Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me

I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?

jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?

Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.

equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.

manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.

All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers

Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.

lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.

This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.

sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.

Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.

Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...

mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good

Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.

jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.

schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.

Can't update with root

Hello there.
i posted this post and asked how to update with root.
i did all the below but my phone was wiped, and the whole storage of phone was gone.
now i have another update and i dont want it to happen again, so someone please can help me and tell me how the hell can i update with root?
i found this tutorial but i dont know if its good or not because its old post.
Help me please!

Here's mine...
1. Download a full 2gb+ rom from oneplus updater
2. Once finished, install it via settings / system / system update / gear icon / local update..
3. Wait till it says 100% installed and is now asking you to reboot the phone
4. Do not reboot, instead, hit the back button.. go to magisk manager, hit install / install to inactive slot . Then reboot.
5. After a reboot, you will still be rooted but lose your twrp.. so install TWRP VIA magisk..
6. After TWRP is installed, it will say, unrooted phone. So install MAGISK AGAIN via direct install, then reboot..
????

maor23 said:
Hello there.
i posted this post and asked how to update with root.
i did all the below but my phone was wiped, and the whole storage of phone was gone.
now i have another update and i dont want it to happen again, so someone please can help me and tell me how the hell can i update with root?
i found this tutorial but i dont know if its good or not because its old post.
Help me please!
Click to expand...
Click to collapse
santiagoruel13 said:
Here's mine...
1. Download a full 2gb+ rom from oneplus updater
2. Once finished, install it via settings / system / system update / gear icon / local update..
3. Wait till it says 100% installed and is now asking you to reboot the phone
4. Do not reboot, instead, hit the back button.. go to magisk manager, hit install / install to inactive slot . Then reboot.
5. After a reboot, you will still be rooted but lose your twrp.. so install TWRP VIA magisk..
6. After TWRP is installed, it will say, unrooted phone. So install MAGISK AGAIN via direct install, then reboot..
Click to expand...
Click to collapse
To follow up if you look in magisk there is a twrp retention script to keep twrp after too I flash that then magisk to inactive slot

TheMadScientist said:
To follow up if you look in magisk there is a twrp retention script to keep twrp after too I flash that then magisk to inactive slot
Click to expand...
Click to collapse
i cant understand this because this is what i did the previous time.
i download the update, didnt installed it and install the twrp retention.
after i was doing it i installed the magisk to inactive slot and then reebot, and my phone was gone

maor23 said:
i cant understand this because this is what i did the previous time.
i download the update, didnt installed it and install the twrp retention.
after i was doing it i installed the magisk to inactive slot and then reebot, and my phone was gone
Click to expand...
Click to collapse
That's weird I've done it several times since owning mine and never lost anything

TheMadScientist said:
That's weird I've done it several times since owning mine and never lost anything
Click to expand...
Click to collapse
So I'm not supposed to do anything? All the specified installes that I am supposed to do, for example the installation of TWRP through MAGISK, should this solve my problem and after the restart I actually stay with both MAGISK and TWRP or should I do something/download and install something from beginning? I will now try to do it again in the hope that this time it will work.
edit:
what should i do if i have custom kernel and not stock?

maor23 said:
edit:
what should i do if i have custom kernel and not stock?
Click to expand...
Click to collapse
Here's mine...
1. Download a full 2gb+ rom from oneplus updater
2. Once finished, install it via settings / system / system update / gear icon / local update..
3. Wait till it says 100% installed and is now asking you to reboot the phone
4. Do not reboot, instead, hit the back button.. go to magisk manager, hit install / install to inactive slot . Then reboot.
5. After a reboot, you will still be rooted but lose your twrp.. so install TWRP VIA magisk..
6. After TWRP is installed, it will say, unrooted phone. So install MAGISK AGAIN via direct install, then reboot..
Do 1-6 update... If you want a custom kernel like RZ kernel
Proceed to step
7. After having twrp installes, reboot to twrp, then flash a custom kernel of your liking..
8. Then reboot phone..

santiagoruel13 said:
Here's mine...
1. Download a full 2gb+ rom from oneplus updater
2. Once finished, install it via settings / system / system update / gear icon / local update..
3. Wait till it says 100% installed and is now asking you to reboot the phone
4. Do not reboot, instead, hit the back button.. go to magisk manager, hit install / install to inactive slot . Then reboot.
5. After a reboot, you will still be rooted but lose your twrp.. so install TWRP VIA magisk..
6. After TWRP is installed, it will say, unrooted phone. So install MAGISK AGAIN via direct install, then reboot..
Do 1-6 update... If you want a custom kernel like RZ kernel
Proceed to step
7. After having twrp installes, reboot to twrp, then flash a custom kernel of your liking..
8. Then reboot phone..
Click to expand...
Click to collapse
And does it matter if I download the update via the UPDATER or I can through the settings directly download and just not reebot?

it stops q 86% for a hour only way i can think is fastboot flash-all

ecompton59 said:
it stops q 86% for a hour only way i can think is fastboot flash-all
Click to expand...
Click to collapse
what? i dont understand

ecompton59 said:
it stops q 86% for a hour only way i can think is fastboot flash-all
Click to expand...
Click to collapse
what? i dont understand

find the flash-all for your update the full one and goto fastboot do update that way or use payload dump to decompress the payload to flash just download flash-all

ecompton59 said:
find the flash-all for your update the full one and goto fastboot do update that way or use payload dump to decompress the payload to flash just download flash-all
Click to expand...
Click to collapse
Im sorry but im really dont understand. Why you tell me to do something else from what everyone told me? and how can i be sure it will be better?

maor23 said:
Im sorry but im really dont understand. Why you tell me to do something else from what everyone told me? and how can i be sure it will be better?
Click to expand...
Click to collapse
1. Download full update via 'oxygen updater' app
2. Go to settings/system/system update/ gear icon
/local update and hit 'update'
3. After it's installed - do not reboot - go to Magisk/
downloads and find TWRP A/B retention script and
install it - do not reboot
4. Go to Magisk (home icon) install/ direct install - do
not reboot
5. After that, again Magis /install /install to inactive
slot (after OTA)
6. Reboot
After everything is done, install kernel or whatever - check in that specific thread for install instructions

maor23 said:
And does it matter if I download the update via the UPDATER or I can through the settings directly download and just not reebot?
Click to expand...
Click to collapse
Hmm.. ive forgotten if you can download the full rom via system updater if you're phone has root access.
I didnt bother too. I always download a full update via oxygen updater.. then install it via system updater.. then install magisk to inactive slot, reboot, install twrp via magisk, then install magisk using direct install option, then reboot to twrp.. flash my favorite rz kernel, then reboot :laugh:

ozyk100 said:
1. Download full update via 'oxygen updater' app
2. Go to settings/system/system update/ gear icon
/local update and hit 'update'
3. After it's installed - do not reboot - go to Magisk/
downloads and find TWRP A/B retention script and
install it - do not reboot
4. Go to Magisk (home icon) install/ direct install - do
not reboot
5. After that, again Magis /install /install to inactive
slot (after OTA)
6. Reboot
After everything is done, install kernel or whatever - check in that specific thread for install instructions
Click to expand...
Click to collapse
It seems so easy, but it's exactly what I did before and just deleted my whole phone, everything from everything. It was not even WIPE, it was a total erasure of all internal memory

maor23 said:
It seems so easy, but it's exactly what I did before and just deleted my whole phone, everything from everything. It was not even WIPE, it was a total erasure of all internal memory
Click to expand...
Click to collapse
I don't know what to tell you, I'm using this procedure my self for some time and all the problems that I had was my fault and carelessness...
Back up your device and try again, maybe everything will be alright, if not - I'm not sure how to help you