Database Info

On H83010i, bootloader unlocked not rooted. Want H83020f rooted

I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.

buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.

Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.

buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root

Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?

buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.

Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?

buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.

Magisk + xposed on nougat

Does systemless xposed work on nougat? If so, please provide the links.

BELIEVER PK said:
Does systemless xposed work on nougat? If so, please provide the links.
Click to expand...
Click to collapse
Yes,it does,just install magisk and in downloads search for Xposed modul.Then install and reboot your phone.

Thanks bud.

Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3

RedSkull23 said:
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?

nagrale.prem said:
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
Click to expand...
Click to collapse
Completely uninstall SuperSU, flash through TWRP the unsu.zip available here on XDA thanks to osm0sis, and then flash Magisk.
BELIEVER PK said:
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
Click to expand...
Click to collapse
Of course they works. Every module works, but not GravityBox. It can't work on an heavy Android modification like EMUI as far as I know, so unless that there's a way to make it work while on SuperSU, it isn't possible to use it on EMUI (as stated in module description on Xposed repo).

Failed while flashing magisk zip.
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-Unpacking boot image
-Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done

Need solutions for above error please...

nagrale.prem said:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Click to expand...
Click to collapse
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)

RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu

nagrale.prem said:
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
Click to expand...
Click to collapse
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).

RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
RedSkull23 said:
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
Click to expand...
Click to collapse
I own honor 6x India version. I understand Uninstal process for supersu. Right now I'm using ELITE ROM V7.3 so i don't know bulid no. N all stuff sorry. I know you will help me

Phone stuck in "device is booting now" screen after oreo update

Hi guys,
I tried to update my Bln-l21 from emui 5 (nougat) to emui 8 (oreo) using the guide https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
It worked so I went on to install TWRP from https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079, as suggested in a comment on the guide.
Only then I realized that in order to install Gapps I needed GSM installer, so I downloaded it, but it didn't work because it loaded TWRP instead of the stock erecovery.
I started to panic real bad
I tried reinstalling the firmware using hwota8 (since i had upgraded i figured i had to use that), but it completely destroyed my phone.
Now it wont boot, recovery wont boot and neither erecovery. I can only get it to enter fastboot.
I know, I am a total noob, but PLEASE help me out on this, i'm desperate.
Thank you so much

If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

Before flashing through Hurupdater wipe system Cache Data Internal and Dalvik/ART Cache.

galapagos said:
If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank you for the answer, I was able to boot in TWRP (the one in the original post) and I downloaded Huru, but I'm unsure of which firmware to use. I want to downgrade back to nougat and rebrand back to europe (since the guide in the original post made me change to china).
Thank you again

Just use China and then install a custom ROM

Mannan Qamar said:
Just use China and then install a custom ROM
Click to expand...
Click to collapse
which one should I choose from firmware finder?
Which rom do you recommend?

Bonny96 said:
which one should I choose from firmware finder?
Which rom do you recommend?
Click to expand...
Click to collapse
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5

Mannan Qamar said:
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5
Click to expand...
Click to collapse
Hi, I successfully flashed with Hurupdater and I'm going trough the installation of the pixys rom. The guide says that i need to flash the stock recovery for my device, where can I find it?
Can I pull it from the firmware I used for Huru? If that's the case, how?
Thank you again

I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.

Mannan Qamar said:
I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.
Click to expand...
Click to collapse
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!

Bonny96 said:
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!
Click to expand...
Click to collapse
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.

Mannan Qamar said:
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.
Click to expand...
Click to collapse
I really appreciate your kindness,
I flashed the latest version of magisk available from the official thread using the same TWRP from before (king of mezi TWRP from elemental rom thread) and it looked fine... Yes, the app didn't show up, I will try with the manager and I'll let you know.
[edit] I installed the manager and turns out it actually worked the first time and I'm already rooted!
Thank you again, you've been wonderful!

Glad to help.

[SOLVED] OTA with ROOT...

I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here

The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.

without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???

please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?

Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...

Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?

flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7

k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks

flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb

Thanks.

I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?

flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA

k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks

flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?

flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)

k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?

flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system

btw: method above work for me also while i upgrade from Android10 to Android11 ;-)

How to Root OnePlus 8T Build 11.0.6.8.KB05AA

I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.

rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.

Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.

Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.

You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.

alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.

Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.

rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot

Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!

rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"

Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!

I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.