Database Users

OP2 cannot upgrade from Oxygen OS 2.2.1/Cannot flash TWRP versions newer than 3.0.2-0

So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.

Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.

Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:

Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!

Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?

Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.

thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.

Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?

Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,

[GUIDE] Root using Magisk, keep stock recovery for OTA

This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.

Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g

kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?

This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.

Ok, but is Xposed etc. possible?

kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

It is really works! Thank you!

gonna check this cause i wanna root the phone but keep enjoying updates

I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial

I bump this because it worked. Quite easy, clean and fast. Thanx!

I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?

masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.

Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?

it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module

Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.

Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??

I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.

Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)

Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse

Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.

Rooting SM-T380 with Pie

I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!

I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.

Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!

Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.

Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..

Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.

Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.

Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.

How do I get a stock backup after flashing magisk? (for ota)

So I've read a bunch of stuff and everything I've read tells me to do the same thing that I've already done. Also those thread seemed pretty old so....
Anyway I need a stock backup so I can perform OTA update but I don't have one. this is what I did
I used msmtool to start over
pushed through setup
unlocked bootloader switch in developer settings
unlocked bootloader in fastboot
updated android
fastboot boot twrp.img
wiped everything
flashed magisk.zip
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
installed magisk.apk
So what step am I missing to save the stock backup so I can uninstall magisk for OTAs?
I had a Pixel for 3 years that had a broken fastboot and so I couldn't unlock the bootloader and never got to learn about the new AB partitioning until now. so I'm a little behind
Thanks

GbizzleMcGrizzle said:
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
Click to expand...
Click to collapse
Unlocking the bootloader can make you fail safety net, much less Magisk if its not set up right. The recovery wont matter.
My guide here is for installing Lineage, however Step 5 will work for OOS too and make you pass safety net. So feel free to install TWRP.
I recommend Funk Wizards Guide on installing TWRP. Also note the section on EFS backups.
Look into TWRP backups, I dont use them, but I know its not straight forward unfortunately.

So when I'm flashing the magisk file in TWRP, does it save a copy of the image it's modifying? And where does it save that image? Also where should i put that image so I can uninstall-> Restore Images?

What is update process for OP6T 9.0.16 > 10.3.3 rooted [Global]

I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global

a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Hello,
Here is a link that will help you out with this update process:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953

a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited

flash713 said:
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited
Click to expand...
Click to collapse
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.

Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
10.3.3 is all that you need. 9.0.17 isn't the only way anymore.

Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
I have a T-Mobile SIM unlock OnePlus 6t and I converted it to an international model so when my conversation was done I was on OOS 9.0.1.1 and I booted TWRP and installed 10.3.4 full rom on both slots and also recovery installer and all just like my previous posts stated and everything went fine. I used mauronofrio's TWRP the version just before the latest 3.4xx when I did this.
I always download quite a bit of various firmwares and also TWRP versions before I start flashing things just in case something goes wrong I already have other things maybe I can use and I don't have to stop and wait for some download to finish... And I'm quite sure you know this but definitely make a backup of everything beforehand to USB or transfer it to your pc just in case you end up needing it as a precaution.
Edit added:
I am assuming that you already unlocked your bootloader... I believe everyone knows to do that that's on XDA forums before you can do anything to any device .. I say this after reading post below me here. I guess I should have said that earlier but I just assume everyone knows that on the forums... My bad. ??
From fastboot on Linux PC:
sudo fastboot oem unlock (then hit enter on keyboard) use volume keys to move to unlock option and your Power button to select it and confirm. For more info see: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Super easy to unlock bootloader just remember it does wipe your device clean so move anything to want to PC or USB stick first...

I would think you could just update oxygenOS to latest then re-root no? Assuming your already bootloader unlocked which it seems like would be the case if you have an obsolete magisk installation.
Edit: re-reading your post maybe it is not unlocked as you failed to root. In this case just unlock then flash the latest fastboot image and then magisk as others have already stepped you through. You will lose data when you unlock so backup first.

So if I'm on 9.0.16 I could flash latest OOS directly from TWRP and then flash magisk? And no data loss? Of course I'm rooted with bootloader unlocked.

Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!

a4abbas said:
Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!
Click to expand...
Click to collapse
It is indeed a tough job. This A/B partition has had a lot of people bootloop/soft bricked their phones.
However, you need not pay anybody anything. If you are on stock, I would've recommended you upgrading it via Oxygen updater (a 3rd party app on the play store) and then using the latest recoveries (TWRP 3.4) and flashing it via Fastboot mode.
It is super easy.