Database Users

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!

magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.

worked for me perfectly

pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.

Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.

pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.

Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

H901 T-Mobile Nougat v30b TWRP flashable update.zip

If you have already upgraded to Nougat using the manual method I posted, you don't need to flash this. If you do, you will get all the bloat back (again), and have to flash your su bin (again), but it isn't going to break your phone.
This is for the H901. Make SURE you have an ACTUAL H901, and not one of the half / half H901 / F600 phones.
If you are still on MM (any version), NOT LP, then you can use this to upgrade (or clean install -- just do a wipe) to Android 7.0 Nougat. This is from the official KDZ that was released on July 18th.
When you flash this, all the carrier bloat / LG bloat / crap / garbage, will come back. You will also lose root until you flash the su bin of your choice. That is the point of this, you WON'T lose TWRP, so you can still root...
Any questions, don't hesitate to ask.
Lastly, when I have time, I will be releasing a version that is already debloated...
Download v30b_update.zip
SHA1: 4ae9338b9301f4b56437ec761b678c8706c90bc7
If you want the FULL Nougat experience -- that is ALL of the v30b firmware except the stock recovery (we don't want to lose TWRP do we?), then flash this as well.
If you flash this, then you might as well delete all of your MM backups that you made with TWRP because you can no longer restore to MM using your backups (you can flash back to MM -- just not with the backups).
If you choose to ignore this, and decide to restore a MM backup, you will brick your phone.
Download full_nougat.zip
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
Known working (tested by me) SU binary: download SuperSU 2.82.
SHA1: d980effb25a8f23bc944d6b1015923f310038031
It has also been confirmed by multiple users that Magisk 12+ works, but I have not confirmed that myself.
This will not wipe ANY of your data / apps / or anything else you may have on your phone. That is why it is an UPGRADE and not a CLEAN install
If you want to do a clean install, just do a full wipe, and then flash.
If you downloaded any of my failed attempts (really -- a typo in a ui_print line?!?!?), and don't want to download the whole zip again, you can download this zip. It is the META-INF directory. You will need to unzip the broken v30b_update.zip, and then extract this over top of the META-INF dir, and then zip it back up.
Make sure you use recursion, and make sure you unzip it on TOP of the META-INF dir, not inside it -- or you will end up with META-INF/META-INF/com/google/android. Won't break your phone, but won't flash either.
-- Brian

Thank you so much man you just made my day...
it will be nice if you can share the recommended SU zip...

Any of the current SUs will work. I am using SuperSU 2.82 (hell, there may be a newer version, but it works, so I don't bother), but I know that Magisk will work as well.
-- Brian

seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?

having the same problem too bad for me !!
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
Just opened the zip file and notices META-INF folder is empty there are suppose to be some files in there which helps flash a file...

Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian

Well THERES the problem. I uploaded the bad copy. I zipped without recursion the first time. Thought I nuked that copy. I am uploading the proper version now -- ya know -- with an ACTUAL META-INF dir
-- Brian

JiggyTox said:
seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?
Click to expand...
Click to collapse
runningnak3d said:
Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian
Click to expand...
Click to collapse
if you can only share meta-inf folder, I think it will work if you just copy files into the zip. that'll be awesome!!

OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian

Thanks a ton for the work you do helping keep this device alive.
I couldn't wait so I went ahead and unzipped the original update.zip and did the other method of pushing the three images via adb, and it works perfectly! thanks a lot again!

idk
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.

runningnak3d said:
OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian
Click to expand...
Click to collapse
thanks man :highfive:

DroxOh said:
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.
Click to expand...
Click to collapse
Getting the same error as well

Well, what the crap. Edify script is ... or should I say WAS, one of the simplest things in the world. Now that I am off work and don't need my phone, I can actually test this before I post an updated zip.
The only thing I can guess is that the v10 doesn't let you flash from the zip itself, so I am going to extract the files to /tmp and then flash them.....
I will post an update as soon as I have this working. This has never been an issue before.....
-- Brian

Thanks Bro. But, I want to turn off big cores Lg v10 H901 Android 7.0. You can create file off core.zip? Plz....

Help me! when i try to flash it, i get the next msg: Updater process ended with ERROR: 6
---------- Post added at 04:35 AM ---------- Previous post was at 04:23 AM ----------
Tell me something, if i update with LG Bridge.... i will lose the TWRP or Just the root ? I net to update to nougat now :/

You will lose both. I did before I found this thread.
Sent from my LG-H901 using Tapatalk

My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone

Ash.... i hope that we can get a solution to make the zip works....

huy chuong said:
My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone
Click to expand...
Click to collapse
As far as I know you cannot rollback to MM from Nougat. Just have to wait and see if someone is able to create a rooted and debloated kdz or .tot Nougat Rom for our H901. I tried to use Dirtycow method to root but the fastboot commands do not work.
Sent from my LG-H901 using Tapatalk

[GUIDE][Magisk] Install Magisk on Mate 9 Running Oreo (Huawei Treble Devices)

Seeing the different people having issues installing magisk and passing safetynet running Oreo trying to do it using TWRP, I've decided to post this guide to help simplify the process for some and allow magisk to install and pass safetynet successfully.
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Original credits and thanks go out to topjohnwu and his original guide found at: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Prerequirements
Must be running Andriod Oreo
Unlocked Bootloader
Copy of your Update.app
Huawei Update Extractor (download in attachments) to extract and get your ramdisk.img
Instructions
***Recommed to use via fastboot method...
If your device does have TWRP support with decryption, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!

Reserved

This method is working good.... Have been using it since.....!

Wirmpolter said:
Seeing the different people having issues installing magisk and passing safetynet running Oreo trying to do it using TWRP, I've decided to post this guide to help simplify the process for some and allow magisk to install and pass safetynet successfully.
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Original credits and thanks go out to topjohnwu and his original guide found at: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Prerequirements
Must be running Andriod Oreo
Unlocked Bootloader
Copy of your Update.app
Huawei Update Extractor (download in attachments) to extract and get your ramdisk.img
Instructions
***Recommed to use via fastboot method...
If your device does have TWRP support with decryption, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Click to expand...
Click to collapse
Thanks a lot Man! It works! After of so many tries!

toto2011 said:
Thanks a lot Man! It works! After of so many tries!
Click to expand...
Click to collapse
Glad it helped you out and worked.

Great guide, thank you! Worked like a charm. The stock ramdisk.img for L29C567B360 is attached.

Cavi_ said:
Great guide, thank you! Worked like a charm. The stock ramdisk.img for L29C567B360 is attached.
Click to expand...
Click to collapse
Great to hear that. Thanks for posting that. I will add it to the OP.

Wirmpolter said:
Great to hear that. Thanks for posting that. I will add it to the OP.
Click to expand...
Click to collapse
Why modules didnt appear in my magisk modules?

toto2011 said:
Why modules didnt appear in my magisk modules?
Click to expand...
Click to collapse
Hmm, that's a strange one. Can you go to settings in magisk and post some screen shots?

Wirmpolter said:
Hmm, that's a strange one. Can you go to settings in magisk and post some screen shots?
Click to expand...
Click to collapse
Yeah! So strange!

toto2011 said:
Yeah! So strange!
Click to expand...
Click to collapse
There is the problem... Uncheck the box beside Magisk Core Only Mode. Should solve the issue.

Wirmpolter said:
There is the problem... Uncheck the box beside Magisk Core Only Mode. Should solve the issue.
Click to expand...
Click to collapse
Thanks a lot man It works

toto2011 said:
Thanks a lot man It works
Click to expand...
Click to collapse
No problem. Yep, I installed that module too. Only if viper worked. Lol

Wirmpolter said:
No problem. Yep, I installed that module too. Only if viper worked. Lol
Click to expand...
Click to collapse
I flashed the p20 pro cmera module but after rebooting nothing change in the cmera setting...

toto2011 said:
I flashed the p20 pro cmera module but after rebooting nothing change in the cmera setting...
Click to expand...
Click to collapse
Yeah, I did not notice any changes either with mine so not sure if there is something we missed then. Maybe we have to remove the camera app first before installing it. I don't know for sure

toto2011 said:
I flashed the p20 pro cmera module but after rebooting nothing change in the cmera setting...
Click to expand...
Click to collapse
the one posted at ******.com he got like these

How could get the stock ramdisk.img for L29C567B367?
Thanks
Sent from my PH-1 using Tapatalk

rogconnect said:
How could get the stock ramdisk.img for L29C567B367?
Thanks
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
-Download your firmwares update.zip from http://pro-teammt.ru/firmware-database/
-Search for your firmware, example used below : MHA-L29C567B367.
-Click on the "filelist" next to your firmware, copy and paste the full links in new tabs to download 'update.zip'.
-Then extract update.app from update.zip. Download and Open Huawei Update Extractor, go to settings tab and disable both checksum.
-Open update.app in Huawei update extractor and extract ramdisk.img.

wancyber said:
-Download your firmwares update.zip from http://pro-teammt.ru/firmware-database/
-Search for your firmware, example used below : MHA-L29C567B367.
-Click on the "filelist" next to your firmware, copy and paste the full links in new tabs to download 'update.zip'.
-Then extract update.app from update.zip. Download and Open Huawei Update Extractor, go to settings tab and disable both checksum.
-Open update.app in Huawei update extractor and extract ramdisk.img.
Click to expand...
Click to collapse
where do i get Huawei update extractor?
---------- Post added at 09:57 AM ---------- Previous post was at 09:51 AM ----------
i see the download link here, its fir Microsoft Windows. what do i use on Linux?

Attached RAMDISK.img for MHA-L29C567B366.
https://mega.nz/#!Pfw1SLRT!-0YL-YkJb6uwsaWxMETgRAhEPtaLDv5EJ4RxtjyvV9o

OTA Update for Rooted/Bootloader Unlocked

Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb fastboot flash "stock boot.img"
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
adb fastboot flash "patched image to inactive slot (no idea how yet, sorry! Will add command)"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only 11 hr shift arguing with doctors to actually provide care instead of leeching insurance, and insurance to pay the damn medical claims instead of baton passing them to patients).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked. If it didn't work, or you encountered error(s), let me know and I can link them in so others can learn.
Disclaimer 2:
The above step(s) is assuming you've used pbanj's method for getting Magisk. Apparently I should add this as there's the "conventional" and "unconventional" method for Magisk. Had no idea since there was no guide available informing people otherwise at the time of making this step-by-step guide.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE some time, and its thread for the above steps.
googlephoneFKLenAsh for details of what I was missing in my initial steps.
sic0048 for making the root confusion apparent, and making a modified boot image method (the pbanj Magisk) here and his guide for rooting here.

Wdenton said:
Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
fastboot flash "patched image"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE amount of time, and its thread for the above steps.
Click to expand...
Click to collapse
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".

I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?

I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.

sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.

alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
Great point, difference between downloading a patched boot image vs patching yourself is not clear as to how it affects the OTA update...

alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
duh1 said:
Unless I'm misunderstanding the process, seems like Magisk is missing a checkbox to backup the unpatched boot image prior to creating a patched image, for future OTA updates...
Click to expand...
Click to collapse
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.

alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images?

duh1 said:
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images.
If that is indeed the case we should be able to just install the OTA normally through the system update button without having to uninstall Magisk and get rid of root first. Then as the Magisk tutorial states cancel the reboot go into the Magisk manager and reroot. Has anyone tried this on a rooted phone?
Click to expand...
Click to collapse
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.

sic0048 said:
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.
Click to expand...
Click to collapse
It's smaller as the OTA only contains the partitions that have changed such as system and boot. The other partitions are probably cloned over from the active slot to the inactive slot.
As I mentioned previously, the Magisk tutorial does not account for not having a backup of the stock boot image when you download the patched boot, so to remove boot prior to installing the OTA, you must manually flash the stock boot.

googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)

sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
sic0048 said:
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
Thanks to all, was not expecting this much reply in this short amount of time, at all.
I made this step by step guide because no dedicated thread really was readily accessible in one place. Hopefully this inspires others to make guides.

googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Click to expand...
Click to collapse
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?

duh1 said:
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?
Click to expand...
Click to collapse
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.

googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
Difference is downloading the patched image vs patching it yourself. Wasn't clear how that created the issue. Well written, thx for pointing it out.
So if anyone patches the new version boot image before uninstalling Magisk, they'll get an error. Likewise, patching the current boot image in the manager will allow the uninstall to work correctly...

googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.

pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.

ritchea said:
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.
Click to expand...
Click to collapse
ya pretty much. every time the phone updates the active slot changes. I'm currently updating my root thread so everything is clearer and in one place.

pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?

duh1 said:
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?
Click to expand...
Click to collapse
correct. i had no issue with it, and i friend is the one who told me about it as that's how she installs her updates even though she could use the magisk method

[Guide] How to ROOT OnePlus8T (CN/IN/EU/International) KB2000,KB2001,KB2003,KB2005

DISCLAIMER​
I have only tested this on my OnePlus8T Indian model - KB2001
Huge thanks to @topjohnwu for his magic.
YOU NEED TO UNLOCK YOUR BOOTLOADER!
In case you brick your device, use this unbrick guide
If you get into a boot-loop by flashing problematic magisk modules, consider using the patched recoveries from my post HERE to remove the modules.
Manual ROOT procedure​Skip to step #6 and then #10 if you do not want to use the payload dumper tool and want to directly patch and flash the stock images for your variant and Build version!
If you haven't updated OxygenOS yet, download it via the system updater. It will be stored in /sdcard/.Ota folder in your internal storage ( /sdcard/.Ota/OnePlus8TOxygen_15.I.16_OTA_0160_all_2010150110_84be0c.zip )
The size should be >2GB. If it is not, it's probably an incremental OTA, not a full one. This guide will NOT work on incremental OTA Zips.
DO NOT Reboot or else you will lose the file
Copy the ZIP file over to your PC
Download the Payload Dumper
Alt dumper for windows only:
https://androidfilehost.com/?fid=818070582850510260
1.Put payload.bin to "payload_input" folder
2.Run payload_dumper.exe
3.Successfully extracted img files are in "payload_output" folder
Extract the zip in the folder where you downloaded the payload dumper.
Follow the instructions in the readme of payload dumper, and extract the OTA images:
Code:
python payload_dumper.py payload.bin
You will get a boot.img file in the output folder.
Proceed with installing the OxygenOS update and reboot the phone.
Download and install the latest magisk canary release to your phone : https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Copy over the boot.img file created by payload_dumper to your internal storage
Open Magisk Manager > Select Install > "Select and patch a file"
Browse and select the boot.img file.
Magisk will create a patched boot.img file in /sdcard/Downloads/magisk_patched.img . Copy this file over to your PC.​
Reboot to fastboot mode
Code:
adb reboot bootloader
Either flash the patched magisk_patched.img in the active slot or temporarily boot into it if you are skeptical.
I recommend to BOOT first and then perform a direct install via magisk as it is more reliable to patch the active slot.
To flash:
Code:
fastboot flash boot magisk_patched.img
To Temporarily boot into a rooted system (RECOMMENDED!!):
Code:
fastboot boot magisk_patched.img
If you used the fastboot BOOT method, next you'll have to open magisk manager again, and this time, perform a "Direct Install".
This will install magisk on the active boot slot and the next reboot will give you root.
How to update OTA and KEEP ROOT
It is advised to disable all magisk modules to be safe!
epr said:
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished to install, reboot and you stay rooted with newest OTA.
Click to expand...
Click to collapse
For the curious / impatient, Here are the OTAs / boot images for the different 8T Versions
All patched images are removed to ensure users perform the steps 6 - 11 of the guide and also not trust images patched by others.
To find your model and build to download the right file:
Bash:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
adb shell getprop ro.build.display.id
KB2001_15_201015
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
11.0.6.8 - 11.0.10.10
KB05DA - India Folder on AFH
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
11.0.6.9 - 11.0.11.11
KB05BA - EU Folder on AFH
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
OOS 11.0.6.8 - 11.0.11.11 : https://androidfilehost.com/user/?w=settings-dev-files&flid=329462
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
It's also a good practice to backup a few important partitions once you're rooted.
I used ADB shell, but you can use any terminal emulator from the play store (Termux)
adb shell
[email protected]:/ $ su
[email protected]:/ #
Now run:
Bash:
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemdump of=/sdcard/modemdump.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist_bkp of=/sdcard/persist_bkp.img
Other Misc Stuff for my reference!​
If after flashing a custom kernel, you see Sim cards not working:
FullOfHell said:
Be sure NOT to have a magisk patched image on both boot slots. That causes this behavior
Click to expand...
Click to collapse
Recovering lost app data after a failed boot:
Download and flash one of my adb-patched recoveries from my post here
Reboot to recovery, enter the password, open adb shell
Create a tar bundle of the app via tar -czvf MiXBackup.tgz data/data/com.mixplorer/silver and adb pull it to your system
*Or* the entire /data partition via tar --exclude /data/media/0 -czvf /data/media/0/data.tgz data/ (You CANNOT restore all of /data like this due to encryption stuff! but you can extract one app at a time and test)
Reinstall the app , reboot to recovery, adb push, and extract via tar xf MiXBackup.tar
Repo of Oxygen OS Builds
OOS Unbrick tool
ADB Enabled OOS Recovery
Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS
Widevine discussions
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2000_Magisk_15.H.16_OTA_0160_all_2010150101_4101.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.1.2.KB05DA.img
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.3.4_BOOT_MAGISK.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.4.5_BOOT_MAGISK.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.5.6_BOOT_MAGISK.img
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
MAGISK patched boot.img which you can flash/boot directly - boot_magisk_patched_11.0.1.2_EU.img
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2003_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thanks @rage302) - magisk_patched_11.0.3.4_KB05BA.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thank @rage302) - magisk_patched_11.0.4.5_KB05BA.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - magisk_patched_11.0.5.6_KB05BA.img
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258

I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer

JWhetstone02 said:
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
Click to expand...
Click to collapse
Yep, the procedure will stay the same. I would recommend waiting for someone to upload the OOS OTA zip or Oneplus to provide a direct download link.
However, if you are on the same build version, you try to patch the KB2001 boot.img and just use the fastboot boot method instead of flashing the patched image.
If it boots, you're in luck. If it doesn't, force reboot back into stock OOS.

Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?

5nickers said:
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
Click to expand...
Click to collapse
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260

DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else

5nickers said:
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
Click to expand...
Click to collapse
Also share the OTA zip too, please

If anyone can provide the OTA or patched img for the KB2005 that would've great, I was too quick to update [emoji2363]
Oh well, I guess I'll need to wait a little longer
Sent from my KB2005 using Tapatalk

DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
After rooting and making the safetynet pass, does the widevine remains L1 like OP8 and OP8Pro? Or it becomes L3 like older OP devices?

I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?

Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing

epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
What model is this for? ... Or would it matter?

Yeah please clearly state which version all these OTAs are from.

5nickers said:
Yeah please clearly state which version all these OTAs are from.
Click to expand...
Click to collapse
Just wanted to give Wykillin a little help...
Payload.properties from his OTA says: ota_target_version=OnePlus8TOxygen_15.O.16_GLO_0160_2010150057
Hope this makes it a little bit clearer...

Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA

DroidFreak32 said:
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
Click to expand...
Click to collapse
Hi. Could you please answer my earlier question? Thank you

theincognito said:
Hi. Could you please answer my earlier question? Thank you
Click to expand...
Click to collapse
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!

DroidFreak32 said:
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
Click to expand...
Click to collapse
Yeah. Both OP8 and OP8 Pro can retain L1

DroidFreak32 said:
PS: For the curious / impatient, I have uploaded the OTA ZIP here (md5sum d1a944205b91898a84b082c57ebac5a8 ):
https://drive.google.com/file/d/18kTOttFEfQN04JHt_7bkoHN3MWa4ZKo4/view
Click to expand...
Click to collapse
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.

zellleonhart said:
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
Click to expand...
Click to collapse
It will. Though I suggest that you flash the EU variant over the Indian variant (cleanest OOS variant).
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
@DroidFreak32
Magisk patched boot image for OOS 11.0.1.2 EU variant (from the full OTA zip - OnePlus8TOxygen_15.E.17_OTA_0170_all_2010150108_77edc51b51680.zip)
https://androidfilehost.com/?fid=10763459528675567936