Related
Just tested it this morning as all is working well. Now we are officially in the supported device (along side with Pixel 2 and 2XL). Thus means that we can now patch boot.img on the fly using Magisk Manager when there's an OTA update.
Steps would be the same as Pixel 2 series as our phones apparently using the same partition and logic method as the Pixel 2. Mentioned here : https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I would suggest anyone who uses magisk snapshot build to upgrade to this latest version for proper magisk patching without TWRP. For minimal issue :
1. install magisk manager 5.4.1 (your current app will prompt for update usually, if not sideload from the official magisk beta xda forum.)
2. Uninstall magisk using the manager app, this will restore your boot.img backup. DO NOT REBOOT, just tap close.
3. Tap update/install magisk. It will then ask which method of installation. Choose install right now (recommend).
4. Reboot and wait, latest magisk should be installed after reboot.
Note : if the backup boot img is not stock, not available or is already patched. You'll need to boot to fastboot, flash your current build boot img. And then boot twrp to flash the magisk 14.5 flashable zip.
Full details here : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Since TWRP is unbootable under this build, you have to use patched boot trick to root this phone.
However, only Magisk 17.1 is usable on this build, Magisk 17.2 - 18.0 can't be installed properly.
So I made a custom update channel that fixed to Magisk 17.1 to assist me.
This guide requires unlocked bootloader - still, I won't introduce how to unlock it here, please Google for it.
Click to expand...
Click to collapse
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
OK, thanks for the info.
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
I hope you can build TWRP for Android P variant of Chinese and it works on non-unlockbootloader. Like you used to do with Oreo? .Thanks
This did not work with TA-1021 while i have pi installed with twrp and patched boot with magisk 16.1 but it do not work not even root access just keep recovery unchanged(twrp).
It says deviceid locked ple if i patch boot with 17.1 what to do! google pay and banking apps dont work.
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can we use official TWRP recovery (3.2.3 made for PLE)
On pie 612H CN - OF YOUR HOMEBREW
and also on 612H ww ??
Please tell
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Can we install this TWRP recovery on Chinese firmware (or ww firmware of ta-1003)or it can be flashed only on PLE versions
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can I install D1C-612H-WW over 612H-CN using OST ??
OST show that the image is broken
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
On rebooting Android root gone????
dont work for me
edit: worsk now over ND1-612C-0-00WW , but for firm official for n5 (612h-0-00WW ) not works, ist patched the xploit for magisk 17 and up
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
Please help I have working 1003 ww pi installed on Ta-1021 and initially rooted using Chinese twrp with magisk later I tried to install update of twrp recovery got crashed and could not enter recovery tried to flash with Qualcomm tools can enter into Edl phone detected but frimware files doesn't flash some errors. Now result is I can operate my phone magisk 16.1 installed but useless. Banking apps don't work. Factory reset don't work. *#*#874#*#* says file not found (may be because I don't have recovery). Ost la as usual don't work. Please help!
Please help me i am on oreo version .. and i have flashed twrp recovery on my nokia 6 (TA - 1021) ..
THE Problem is when i reboot to recovery it's not booting in twrp but it's booting on custome recovery ..
I need pc everytime , if i want to boot it on twrp .
I have to run command every time to boot in on twrp recovery ..
Is there any way to directly boot it on twrp recovery not in custom recovery ? Please help me
@hikari_calyx Does fastboot boot work for you on pie? For me, it does not. Almost shat my pants thinking my TWRP doesn't work but it does in fact work, just fastboot booting it does not work.
Finally got the official pie update on my TA-1033. (unlocked bootloader)
The standard versions of TWRP 3.2.3.0 / Magisk 17.3 / Magisk Manager 6.0.1 worked perfectly.
As above, "fastboot boot" doesn't work, but "fastboot flash" etc. does.
Happy days.
Not working for me please can you tell the procedure step by step as i tried your steps but didn't happen anything please
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Not working i have unlocked bootloader but i tried to flash twrp and it's not booting on it any other solution please let me know .
Can you help me please my device is showing me this on my recovery , what's an issue please reply as soon as possible i can't even apply update through sd card or adb it's not detecting everytime it entered to this menu .. please help me
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
vineet09i said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
Click to expand...
Click to collapse
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Emmykay223 said:
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Click to expand...
Click to collapse
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Yes but twrp is not booting on my pie build because it is showing "failed to find device for partition system" and i am unable to apply update through sd card or through adb i don't know why so i am thinking to follow this steps hope it will work.
vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Why any module is not installing by magisk it's showing me unable to extract, i followed each and every steps as mentioned above and rooted my Nokia 6 again but it's not installing any module what's the reason behind it?
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
joemossjr said:
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
Click to expand...
Click to collapse
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
i.Design said:
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
This didn't work. I was able to at least see my storage now and installed OTA via TWRP > TWRP installer > Magisk to update Slot B now I'm having the same issue in both slots.
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
I have downloaded the 11 update via OxygenUpdater using VPN (Location is set to France)
Since i diden't get the update on my real location.
Rebooted to TWRP->Flashed 11 update->Flashed TWRP->Rebooted to TWRP>Flashed Magisk>Flashed Kernel>Rebooted to System.
Everything seems to be working.
Try this simple and straight forward method,
Download the full zip 9.5.11, not the update zip but full zip,
Transfer to phone storage,
wipe only dalvik cache and data, DO NOT WIPE SYSTEM OR VENDOR, OR INTERNAL STORAGE,
Flash the oos zip,
Flash twrp, Reboot recovery,
Flash oos zip file again followed by twrp,
Reboot recovery,
Flash magisk 19.3,
Now Reboot system,
Do not click on any slots in twrp let the system select the appropriate slot, system will take some time to boot also will Reboot itself, but will boot eventually,
hope this helps, cheers.
How this helps, worked for me, I don't have T-Mobile version
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
OP7PRO, stock ROM, stock kernel
This has been ABSOLUTELY working for me and how i was used doing it back in the days..
*After switching off all modules in Magisk and do a system reboot to apply this..
(Do I have to mention it's probably best, when updating to disable any password/fingerprint protection when rebooting AFTER FLASHING OTA, TWRP and Magisk in recovery?)
*I didn't use local update setting.
*What's on in developer options?
-OEM Unlock allowed
-Advanced reboot
-USB Debugging
*Don't know if having these developer settings otherwise would interfere, I just try to write it down as specific as of how i did this.
*Also: I didn't even bother looking at A/B partitioning and where to install what, please correct me if i could be wrong, but using this method worked for me and also when installing TWRP zip in recovery, the log showed A/B sloth solution success when installing.
*Not using substratum themes etc., but I want to say it's probably best to go as clean as you can anyway, since you can always go back being beautiful afterwards I guess?
So try remember where you left off being a makeup loving customiser and momentary revert being as clean as possible.. at least for maybe 20 minutes okay?
How I did it:
-Download the OTA update zip on your phone (full update file zip just shy of 2 Gb) using oxygen updater app in Google playstore.
(Don't install the systemsoftware zip from the oxygen updater once downloaded), you're going to install the systemsoftware.zip in TWRP recovery as opposed to update via Magisk to install the new systemsoftware).
-Download TWRP (INSTALLER!!) have this ZIP on phone (Find it by reading some posts about TWRP Installer zip or use link below)
*I used: twrp-installer-3.3.1-4-guacamole.zip
https://dl.twrp.me/guacamole/ (for TWRP zip)
-Download Magisk zip
*I used: Magisk-v19.3.zip
(So far 3 zip files, have them somewhere pretty obvious on your phone)
-Boot into recovery (I did this by using this option in Magisk manager)
Then:
-Flash the update OTA ROM.zip (just shy of 2Gb)
*DON'T REBOOT*!!!!
-Go back in TWRP recovery menu, Flash TWRP Installer zip
-Still in TWRP recovery menu go back, Reboot to recovery
-Back in TWRP, flash Magisk zip
-Clear Dalvik cache (not sure if this is actually still needed)
-Reboot system normally, enable Magisk modules you want, reboot system...
Updated to 9.5.10 works
Updated to 9.5.11 works
Updated to 10.0.0 works
I can't find the full zip for 9511 anywhere
joemossjr said:
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
Click to expand...
Click to collapse
I ended up having to reformat to deal with the encryption issue. After reformatting I was able to boot to slot b and am at .11 now!
I'm really hoping this ordeal fixed whatever the problem was so that future OTA's aren't this much of a headache. I'll keep the tips in mind. I'm just glad to have a working device at .11 with root even if I have to re-install all of my apps etc.
virtyx said:
I can't find the full zip for 9511 anywhere
Click to expand...
Click to collapse
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
smariob said:
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
Click to expand...
Click to collapse
just came up now
what i normally do is flash full zip
reboot
then reboot fastboot and boot twrp, then flash twrp then magisk.
i like the OS boot first time without twrp or magisk, just habit i guess
everything working fine, nightscape also
EDIT:
i think SWAP has been turned off in 9.5.11
it no longer displays in ElementalX app (with stock kernel)
What did I do wrong?
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
I don't know why people have such difficulty?
1. Get the full zip via Oxygen Updater or some other method.
2. Do a local install vis the settings. DO NOT REBOOT.
3. Install Magisk via the "Install after OTA" from Magisk Manager.
4. Reboot
5. You will now have the slot rooted that you updated.
6. Run the local install again. This will install to the other slot. It will fail the first attempt. Do it again.
7. Install Magisk via the OTA option and reboot.
You have now updated both slots and rooted them.
If you would like TWRP or custom kernels, follow those instructions.
If you install TWRP, you MUST install Magisk in the same slot or you will get a boot loop for that slot.
That is the reason why I keep both slots at the same OS level and rooted with TWRP installed.
What country guys you are from that you are getting update? Im in USA and still got nothing.
netgar said:
What country guys you are from that you are getting update? Im in USA and still got nothing.
Click to expand...
Click to collapse
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Krsmqn said:
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Click to expand...
Click to collapse
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
netgar said:
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
Click to expand...
Click to collapse
Yeah, meant magisk modules, sorry. But looks like you got it anyway. ?
All update methods to 11 failed.
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Magisk working on final android 10
oscar1823 said:
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Click to expand...
Click to collapse
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
alliance1975 said:
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
Click to expand...
Click to collapse
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
sic0048 said:
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
Click to expand...
Click to collapse
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
omiCar said:
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
Click to expand...
Click to collapse
I installed it while still Pie.
sic0048 said:
I installed it while still Pie.
Click to expand...
Click to collapse
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
I made the mistake of having Magisk set to beta instead of canary when I did the Magisk OTA update, but no issues with the regular boot image patching method.
Simply follow the guide linked above and you should be fine.
omiCar said:
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
Click to expand...
Click to collapse
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
Got it to work.
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
sic0048 said:
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
All you really need to do is flash Pie back on the phone and start the process over. I realize that seems like a long process, but it really isn't that hard. Just be sure to backup any important data off phone before you start because installing Pie should wipe the phone.
Click to expand...
Click to collapse
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Thanks for the response, I will download the Andriod 10 and flash it into my phone, hopefully it will work
darkmeridian said:
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
I agree that normally that would work.
However, simply replacing the boot.img file doesn't completely uninstall Magisk. That is why there is a Magisk Uninstaller zip that can be used with TWRP. It normally isn't needed, but it is a great way to completely wipe Magisk if you are having issues. Obviously that isn't an option on Android 10 currently because TWRP doesn't work yet.
Hopefully he doesn't have any issues moving from stable to Canary Magisk versions. But if he does, he will likely have to flash a full factory image to completely wipe the phone and reinstall everything without traces of Magisk
flow5673 said:
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Click to expand...
Click to collapse
This worked for me. Thanks
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
If you experience manager telling you that Magisk isn't installed after installing it through fastboot, uninstall manager and reinstall it. Deleting app data won't do the trick. Strange bug but I encountered that in the Q beta
Anyone else having issues with the canary build? I hard reboot and it shows magisk not installed, then I reboot again and its installed again?
Also Android Q is hella laggy for me?
Currently doing a full fresh image install
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Velcorn said:
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Click to expand...
Click to collapse
For now I disabled the unused apps. Similar behavior also in pie. One update app remover wouldn't work but titanium would, the next update the reverse would happen. I think the apps need updating so as to work with Android 10.
omiCar said:
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
Click to expand...
Click to collapse
I don't have a video but you can look up the individual steps. You want to do the OTA through ADB sideloading. Then patch the stock boot.img with Magisk Canary, which was linked to above, and then flash with fastboot.
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Uninstall and reinstall Canary Magisk Manager (NOT DEBUG). I had both force encryption and preserve avb CHECKED. Then patch boot.img and flash using fastboot.
I've been using below steps to update my OP6 while preserving root. Thought of sharing with you all
I've been using this method for all recent updates like 9.0.9 ->10.3.0->10.3.5->10.3.6->10.3.7->10.3.8->10.3.9->10.3.11->11.1.1.1
My OP6 info:
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
Steps:
enable system update app if it's disabled
nandroid backup (optional)
enable any disabled system apps like youtube
- download OTA updated zip: via Oxygen Updater App -> Full Update option
- Install it: System Settings -> Local Upgrade option (don't reboot).
- Once installed: go to Magisk -> run TWRP retention script from osm0sis (don't reboot).
- Again in Magisk, install magisk -> install to inactive slot (don't reboot yet).
- Then on modules list, disable all modules and then finally...
- Reboot, this reboot will take some minutes...
- after reboot, re enable all modules and everything will work perfectly.
The System Updater and Magisk do all the work, never ever once having to boot into recovery.
JerryGoyal said:
I've been using below steps to update my OP6 while preserving root. Thought of sharing with you all
I've been using this method for all recent updates like 9.0.9 ->10.3.0->10.3.5->10.3.6->10.3.7->10.3.8->10.3.9->10.3.11->11.1.1.1
My OP6 info:
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
Steps:
enable system update app if it's disabled
nandroid backup (optional)
enable any disabled system apps like youtube
- download OTA updated zip: via Oxygen Updater App -> Full Update option
- Install it: System Settings -> Local Upgrade option (don't reboot).
- Once installed: go to Magisk -> run TWRP retention script from osm0sis (don't reboot).
- Again in Magisk, install magisk -> install to inactive slot (don't reboot yet).
- Then on modules list, disable all modules and then finally...
- Reboot, this reboot will take some minutes...
- after reboot, re enable all modules and everything will work perfectly.
The System Updater and Magisk do all the work, never ever once having to boot into recovery.
Click to expand...
Click to collapse
Hi guys How I can #root OnePlus 6 in oxygen os 11.1.1.1??? said: And how install #TWRP OnePlus 6 in oxygen os 11.1.1.1??? Can't install TWRP in android 11 crashed OnePlus 6 The in Oxygen os 11.1.1.1 very slowly #speed phone OnePlus 6 and very slowly and poor Network? Don't use high speed Network? Don't use high speed phone? Please help me Thanks
JerryGoyal said:
I've been using below steps to update my OP6 while preserving root. Thought of sharing with you all
I've been using this method for all recent updates like 9.0.9 ->10.3.0->10.3.5->10.3.6->10.3.7->10.3.8->10.3.9->10.3.11->11.1.1.1
My OP6 info:
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
Steps:
enable system update app if it's disabled
nandroid backup (optional)
enable any disabled system apps like youtube
- download OTA updated zip: via Oxygen Updater App -> Full Update option
- Install it: System Settings -> Local Upgrade option (don't reboot).
- Once installed: go to Magisk -> run TWRP retention script from osm0sis (don't reboot).
- Again in Magisk, install magisk -> install to inactive slot (don't reboot yet).
- Then on modules list, disable all modules and then finally...
- Reboot, this reboot will take some minutes...
- after reboot, re enable all modules and everything will work perfectly.
The System Updater and Magisk do all the work, never ever once having to boot into recovery.
Click to expand...
Click to collapse
Super useful, thank you!
Very helpful!
Thank you JerryGoyal
Your method worked perfectly!
fullbazak said:
Hi guys How I can #root OnePlus 6 in oxygen os 11.1.1.1??? said: And how install #TWRP OnePlus 6 in oxygen os 11.1.1.1??? Can't install TWRP in android 11 crashed OnePlus 6 The in Oxygen os 11.1.1.1 very slowly #speed phone OnePlus 6 and very slowly and poor Network? Don't use high speed Network? Don't use high speed phone? Please help me Thanks
Click to expand...
Click to collapse
I've got the same issue
fullbazak said:
Hi guys How I can #root OnePlus 6 in oxygen os 11.1.1.1??? said: And how install #TWRP OnePlus 6 in oxygen os 11.1.1.1??? Can't install TWRP in android 11 crashed OnePlus 6 The in Oxygen os 11.1.1.1 very slowly #speed phone OnePlus 6 and very slowly and poor Network? Don't use high speed Network? Don't use high speed phone? Please help me Thanks
Click to expand...
Click to collapse
Let me know here if you find a fix for installation of TWRP under 11.1.1.1 please?
With rooted version 10.3.x I updated this way without any problems:
How to Update Your OnePlus 6 or 6T Without Losing Root — No Computer Needed
One of the biggest downsides to rooting is that it can be a pain to update every month with each new security patch. With other phones, you might have had to fully unroot the device, maybe flash a stock recovery, or potentially even flash all the factory images to get a new update. Thankfully...
oneplus.gadgethacks.com
* Download full stock rom (same as from OxygenUpdater), latest TWRP (now 3.5) and lastest Magisk (now 23.0) onto sdcard of device.
* Reboot into TWRP recovery
* Flash stock ROM and then TWRP without intermediate reboot
* Reboot into TWRP recovery again
* Flash Magisk
* Reboot normally.
I left all disabled system apps such as e.g. Youtube app, disabled. I did the update manually without using Oxygenupdater, the latter only for verifying the MD5 of the ROM.
Can this also be done with flashing 11.1.1 ROM ?
JerryGoyal said:
I've been using below steps to update my OP6 while preserving root. Thought of sharing with you all
I've been using this method for all recent updates like 9.0.9 ->10.3.0->10.3.5->10.3.6->10.3.7->10.3.8->10.3.9->10.3.11->11.1.1.1
My OP6 info:
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
Steps:
enable system update app if it's disabled
nandroid backup (optional)
enable any disabled system apps like youtube
- download OTA updated zip: via Oxygen Updater App -> Full Update option
- Install it: System Settings -> Local Upgrade option (don't reboot).
- Once installed: go to Magisk -> run TWRP retention script from osm0sis (don't reboot).
- Again in Magisk, install magisk -> install to inactive slot (don't reboot yet).
- Then on modules list, disable all modules and then finally...
- Reboot, this reboot will take some minutes...
- after reboot, re enable all modules and everything will work perfectly.
The System Updater and Magisk do all the work, never ever once having to boot into recovery.
Click to expand...
Click to collapse
Sorry, please explain "modules list". In what context is this please?
Quick note. Do not re-enable Smali Patcher if that was one of your previously enabled modules. The framework used to create the patch was from the previous android OS version, so it'll just spin when booting. To fix it follow the official recommendation from the smali patcher FAQ which is Boot into TWRP > Advanced > File Manager > navigate to data > adb > modules > select the module directory (in this case "fomey.smalipatcher" > folder icon in the bottom right > delete.
mermaidkiller said:
With rooted version 10.3.x I updated this way without any problems:
How to Update Your OnePlus 6 or 6T Without Losing Root — No Computer Needed
One of the biggest downsides to rooting is that it can be a pain to update every month with each new security patch. With other phones, you might have had to fully unroot the device, maybe flash a stock recovery, or potentially even flash all the factory images to get a new update. Thankfully...
oneplus.gadgethacks.com
* Download full stock rom (same as from OxygenUpdater), latest TWRP (now 3.5) and lastest Magisk (now 23.0) onto sdcard of device.
* Reboot into TWRP recovery
* Flash stock ROM and then TWRP without intermediate reboot
* Reboot into TWRP recovery again
* Flash Magisk
* Reboot normally.
I left all disabled system apps such as e.g. Youtube app, disabled. I did the update manually without using Oxygenupdater, the latter only for verifying the MD5 of the ROM.
Can this also be done with flashing 11.1.1 ROM ?
Click to expand...
Click to collapse
Have you used this method earlier in earlier versions
Hi @JerryGoyal need TWRP retention script which you have mentioned in your post, kindly share the link here
mermaidkiller said:
With rooted version 10.3.x I updated this way without any problems:
How to Update Your OnePlus 6 or 6T Without Losing Root — No Computer Needed
One of the biggest downsides to rooting is that it can be a pain to update every month with each new security patch. With other phones, you might have had to fully unroot the device, maybe flash a stock recovery, or potentially even flash all the factory images to get a new update. Thankfully...
oneplus.gadgethacks.com
* Download full stock rom (same as from OxygenUpdater), latest TWRP (now 3.5) and lastest Magisk (now 23.0) onto sdcard of device.
* Reboot into TWRP recovery
* Flash stock ROM and then TWRP without intermediate reboot
* Reboot into TWRP recovery again
* Flash Magisk
* Reboot normally.
I left all disabled system apps such as e.g. Youtube app, disabled. I did the update manually without using Oxygenupdater, the latter only for verifying the MD5 of the ROM.
Can this also be done with flashing 11.1.1 ROM ?
Click to expand...
Click to collapse
Which TWRP version and Magisk version did you use?
A very big thanks to you bro!
Before Updation:
--------------------
My OP6 info:
v 9.0.9
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
After Updation:
------------------
Now My OP6 info:
v11.1.1.1
TWRP: 3.2.3-x | blu_spark v9.91 (But its not accepting the password, so not decrypting)
Magisk: 23.0
Any suggestions regarding TWRP to work.
I have been using the same method for updating open betas. Now there is official november update.. Is it possible to update to official rom from open beta using this method without losing data and root?
Static-xy said:
Which TWRP version and Magisk version did you use?
Click to expand...
Click to collapse
Usually the latest (3.5 resp. 23).
So now I want to use the same way, by re-flashing TWRP (probably a newer version) after the new stock ROM, but before reboot.
@JerryGoyal kindly share twrp retention script and twrp link here which you used
JerryGoyal said:
I've been using below steps to update my OP6 while preserving root. Thought of sharing with you all
I've been using this method for all recent updates like 9.0.9 ->10.3.0->10.3.5->10.3.6->10.3.7->10.3.8->10.3.9->10.3.11->11.1.1.1
My OP6 info:
TWRP: 3.2.3-x | blu_spark v9.91
Magisk: 23.0
Steps:
enable system update app if it's disabled
nandroid backup (optional)
enable any disabled system apps like youtube
- download OTA updated zip: via Oxygen Updater App -> Full Update option
- Install it: System Settings -> Local Upgrade option (don't reboot).
- Once installed: go to Magisk -> run TWRP retention script from osm0sis (don't reboot).
- Again in Magisk, install magisk -> install to inactive slot (don't reboot yet).
- Then on modules list, disable all modules and then finally...
- Reboot, this reboot will take some minutes...
- after reboot, re enable all modules and everything will work perfectly.
The System Updater and Magisk do all the work, never ever once having to boot into recovery.
Click to expand...
Click to collapse
Thank you.
After the whole process is completed what to do with TWRP retention script module
should we uninstall it
Does the method in the OP work for updating from 11.1.1.1 to 11.1.2.2? Or is it only for updating from earlier versions of Oxygen to 11.x?
ashish1989 said:
After the whole process is completed what to do with TWRP retention script module
should we uninstall it
Click to expand...
Click to collapse
????
@JerryGoyal .
Hi, I am on OP6 on OOS version 10.3.5 with Magisk root version 21.4 and twrp recovery. Also XXX nolimts Rom installed. I have no issues with the current version of OOS, and have disabled the update with 'Xxx nolimits' rom. I am unable to use banking apps since the Magisk hide apparently doesn't work for them. Only 'phonepe' works till now, but it's only a matter of time when they behave like 'yono sbi' app too. I have heard that this is because of the safetynet check failure. I have tried installing the module 'universal safetynet fix' but it didn't work. I have an unlocked bootloader as well, I don't know if that is relevant. Please help.