I see that the September update for the Pixel 3 XL moves us to Android 11.
I have been doing monthly upgrades of Android 10, but moving to 11 is going require a lot of work. I think Magisk canary supports 11. I dont see any support yet for EdXposed and Gravitybox. Since we just got TWRP, I wonder if that will still work with 11.
I plan to wait a few weeks before moving to 11. I hope that EdXposed, GB and TWRP will be updated by then.
What are other Pixel 3XL planning to do?
I tried the Magisk/OTA update to go from 10 to 11 but root didn't stick. Guess I did something wrong. Oh well... I'll patch the boot img later.
Same here. I have to wait until exposed is fully supported.
swieder711 said:
I see that the September update for the Pixel 3 XL moves us to Android 11.
I have been doing monthly upgrades of Android 10, but moving to 11 is going require a lot of work. I think Magisk canary supports 11. I dont see any support yet for EdXposed and Gravitybox. Since we just got TWRP, I wonder if that will still work with 11.
I plan to wait a few weeks before moving to 11. I hope that EdXposed, GB and TWRP will be updated by then.
What are other Pixel 3XL planning to do?
Click to expand...
Click to collapse
Magisk root via canary magisk manager worked fine for me today and have rebooted a few times
Delete
prot- said:
Magical root via canary magisk manager worked fine for me today and have rebooted a few times
Click to expand...
Click to collapse
Canary magisk manager worked for me too.
First Time it didn't show the Magisk-Version but i got root (Adblock worked). Now it shows the right Version (20424)
davion27 said:
Canary magisk manager worked for me too.
First Time it didn't show the Magisk-Version but i got root (Adblock worked). Now it shows the right Version (20424)
Click to expand...
Click to collapse
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
I got Android 11 on Tuesday by opening the system update page in settings.
paulyt989 said:
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
Click to expand...
Click to collapse
After Update to Android 11, i installed Canary Manager (nice blue layout!) and patched the boot.img. Steps are the same i always used to install the patched boot.img: "fastboot flash boot --slot all boot.img"
paulyt989 said:
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
Click to expand...
Click to collapse
[Guide] Root Pixel 3 XL Android 11 (R)
Related
Hello,
I had to go back to the latest version of Nougat, OxygenOS 4.7.5, because it works as root with SuperSu, but I have a problem with Oreo-based OxygenOS. When I flash SuperSu (latest version) with the latest version of TWRP, I restart the phone, but I get stuck on the OnePlus logo, so the phone cannot restart after at least 15 minutes of waiting. Do you have any idea what the problem is? I can't take advantage of Android Oreo by being rooted with SuperSu, it's annoying.
SuperSU hasn't been updated in a while and I assume it doesn't support Android Oreo. I would use Magisk instead. That's what I tried with Nougat and what I'm currently using on Oreo.
Macusercom said:
SuperSU hasn't been updated in a while and I assume it doesn't support Android Oreo. I would use Magisk instead. That's what I tried with Nougat and what I'm currently using on Oreo.
Click to expand...
Click to collapse
Okay, thank you. It's the same root with Magisk?
We7dy said:
Okay, thanks you. It's the same root with Magisk?
Click to expand...
Click to collapse
It's not the same binary but it does the same thing. It will allow apps to gain root access just as SuperSU used to do
Fixed with Magisk. ?
I currently have Magisk 20.3 and Magisk Manager 7.5.1 installed on my 3xl. I open Magisk Manager and check for new version of Magisk, but it doesn't show the latest 20.4. Has anybody updated to 20.4? If so, which version of Magisk manager did you use?
John
jcp2 said:
I currently have Magisk 20.3 and Magisk Manager 7.5.1 installed on my 3xl. I open Magisk Manager and check for new version of Magisk, but it doesn't show the latest 20.4. Has anybody updated to 20.4? If so, which version of Magisk manager did you use?
John
Click to expand...
Click to collapse
Magisk-v20.4.zip is the Beta version. In Magisk Manager settings change the update channel to Beta if you want it.
I'm on stable channel and v20.4 just showed up on my devices as an update. I updated my Nexus 6P and all is good but I'll wait a while before updating my P3XL.
newkydawg said:
I'm on stable channel and v20.4 just showed up on my devices as an update. I updated my Nexus 6P and all is good but I'll wait a while before updating my P3XL.
Click to expand...
Click to collapse
Yup, Magisk-v20.4.zip Stable was released 03/28/2020.
Just updated Magisk to 20.4 and patched boot.img from Mar. I used platform tools 29.0.6 and flashed Magisk.patched img to all slots successfully.
When you update do you have to re flash a patched boot image? I have updated my magisk manager, but not magisk itself bc I was unsure of how to proceed.
[email protected] said:
When you update do you have to re flash a patched boot image? I have updated my magisk manager, but not magisk itself bc I was unsure of how to proceed.
Click to expand...
Click to collapse
Guide
Hello everyone
Please can you help me to root pixel 2 xl - android 11
And is there any custom rom with android 11
We could, but it's important to note that if you have a Verizon Pixel 2 XL, root is NOT POSSIBLE.
Anyway, assuming you have the correct P2XL, the rooting instructions we give here in the forums haven't changed appreciably since they were written. For Android 11, they still apply, with the caveat that you currently have to use the "Canary" version of Magisk (i.e. the development channel version of Magisk) in order for root to work.
How about ????
abughassan said:
How about ????
Click to expand...
Click to collapse
That' indicates you have a Google variant, not a Verizon variant. So you're good to go with unlocking your bootloader, etc.
You should delete that picture as it shows your CSN number.
Guides:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://github.com/topjohnwu/Magisk
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.
Thank you very much for your help brothers
It's done
abughassan said:
Thank you very much for your help brothers
It's done
Click to expand...
Click to collapse
Awesome
abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
Lughnasadh said:
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.
Click to expand...
Click to collapse
Just to point out the obvious to @abughassan, but I thought I made the point @Lughnasadh brings up clear in my previous post. You must have missed it, but it's all good as you got things working.
@Strephon Alkhalikoi
yes pro .. you are right I didn't notice it .. that's my fault thank you very much for your help
Brothes :
Is it possible to change font on P2XL11 ??
abughassan said:
Brothes :
Is it possible to change font on P2XL11 ??
Click to expand...
Click to collapse
You are rooted now mate and android is full of possibilities. Search internet you will surely find a way.
@rajkatiyar07 : Thanks mate ... I tried many ways but it didn't succeed
abughassan said:
@rajkatiyar07 : Thanks mate ... I tried many ways but it didn't succeed
Click to expand...
Click to collapse
Check in magisk thread. I am not rooted now but if i remember correctly there were plenty fonts related modules.
Just not able to root my Pixel 2 XL running Android 11
Lughnasadh said:
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.
Click to expand...
Click to collapse
Brother please help me out. I've tried everything but I am just unable to root my pixel 2 xl running the latest android version (11).
I tried patching the boot image with latest canary build and it always outputs an image file which is of 0 bytes.
Then I tried patching the boot image with latest magisk manager (not canary), it was able to output a file which was around 25 MB in size but flashing it always results in boot loop.
Finally, I tried to patch my boot image using some other device with magisk canary (latest) and the output image was about 25 MB in size but again after flashing it, the device goes into boot loop.
--UPDATE--
I was finally able to root my device by simply flashing the latest magisk zip file (v 21.0) via TWRP
MridulDR said:
--UPDATE--
I was finally able to root my device by simply flashing the latest magisk zip file (v 21.0)
Click to expand...
Click to collapse
Yes, just to clarify for others reading this, topjohnwu pushed Magisk 21 to the beta channel. It should be on the stable channel shortly, so there will soon be no need to deviate from the established rooting instructions we have in the forums.
abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
I had that happen. Unfortunately, the only solution I found was to use the online Google flash tool and flash back to the previous install. Fortunately, it worked. I updated to 11 from there. I may leave it uprooted because currently the Pixel 2 XL is a backup phone and I don't need root currently.
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
I found oxygen updater in Google play store. Is that what you're talking about?
sbcdave said:
I found oxygen updater in Google play store. Is that what you're talking about?
Click to expand...
Click to collapse
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Shanemichealrowland said:
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Click to expand...
Click to collapse
Yes it does, I've been using it since I got my op9pro on 1st April.
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Bunecarera said:
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Click to expand...
Click to collapse
I assume you disable all magisk modules prior updating.
netgar said:
I assume you disable all magisk modules prior updating.
Click to expand...
Click to collapse
Yes.
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA
Click to expand...
Click to collapse
This is rather annoying. Why are we left behind?
the bolt of thunder said:
This is rather annoying. Why are we left behind?
Click to expand...
Click to collapse
I think it's because the Global ota's are being stored on Google servers instead of the OnePlus servers for some reason
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
I updated my BA using oxygen updater (download full os, settings/system/system updates/lokal update) without touching magisk at all. reboot, bootloader, reflash https://mega.nz/file/bNozXKJI#0zNfKtRw1IBqG6ojFuW3830dxXLgewmtsbbh4T4WGzs (I know its 1.1.2.4.4, but it works...) done
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
dreinulldrei said:
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
Click to expand...
Click to collapse
thats what i did first of all, my device didnt boot at all but kept going to stock recovery. afterwards i flashed what i wrote above, everythinx fine now.
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
Click to expand...
Click to collapse
I decided to unroot and take the update. I'll just wait until the full OTA comes to us before rooting. :/
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Flying Fox said:
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Click to expand...
Click to collapse
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
dreinulldrei said:
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
Click to expand...
Click to collapse
schmeggy929 said:
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
Click to expand...
Click to collapse
Thx for your answers!! Nice to be back to Oneplus. Great community here...
Does anyone know if oxygen updater from the play store is a trustworthy source for these OTAs?
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.