Related
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
I don't remember the actual choices, since mine is already updated, but I do it straight from Magisk Manager app. I think I choose update then the direct install (recommended) option. I believe it then shows the log as it updates and once done gives option to reboot. Once it reboots, you should be on latest (15.3) version of Magisk, and you still have root and pass Safety checks. It has never caused any boot loops for me, just smooth and simple.
HTH!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
like the other response, i am able to upgrade magisk directly from magisk manager (direct install method)
one caveat, i don't know if it's still true, i had an issue upgrading a month or two back and someone on here recommended i set my magisk to the "beta" channel (settings -> update channel). i suspect this is no longer needed, but i left it on the beta channel and have had no issues upgrading magisk every time it notifies me of a new update
Ok, so I can upgrade directly from the app. Great! I guess I was overthinking...
Thanks!
Link contains factory boot, and patched images, bootloader and radio from stated release
August 2020 (canary): https://drive.google.com/drive/folders/1SpBngNA35CnCCF57jK8wjhRUQEeyyCHG?usp=sharing
Tulsadiver module disabler: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867 (i think magisk canary disables modules if you boot into safe mode https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24 )
Way to update without flashing: https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md
here is a guide for getting root: https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
platform tools were updated in july 2020: https://developer.android.com/studio/releases/platform-tools
and a guide for google pay with root: https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248
Hide Google pay, Google play services, Google services framework, clear Google pay data after update and apply module.
old factory and patched images:
July 2020 (canary patch): https://drive.google.com/folderview?id=16-XxwJbT5VIIT1cbDTXIffdOuqwx3XCH
Feb 2020 (beta patch): https://drive.google.com/open?id=1WZ2-tza0IB3oICGFCHuj1GJKJr0nd8a3
Jan 2020 (canary patch): https://drive.google.com/open?id=1_zNt1i2uqbGhfEiWn0O716v9noJdR4uJ
Dec 2019(canary patch): https://drive.google.com/open?id=1JHc86ZOHkyNA0uJ6r43eLqG4oe6KBfGy
nov 2019(canary patch): https://drive.google.com/open?id=14GA7qrPITZ_-jYNDAFuC0bJiaKwGmqRP
oct 2019(canary patch) : https://drive.google.com/folderview?id=16bbXgyWwi8TmJNaih_UvdtXxB8fC5W0t
note: i think you can go into recovery mode to disable modules with canary magisk if you have trouble.
updated OP with nov images
one report of nov 2019 update breaking google pay
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
if you can push the magisk uninstall zip to your device, then fastboot booting into twrp then flashing the magisk uninstall zip that should do the trick.
swieder711 said:
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
Click to expand...
Click to collapse
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
jd1639 said:
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
Click to expand...
Click to collapse
Thanks for the pointer. I wasn't sure if that Disabler would work with the November image.
I ended up reflashing the factory default and than reapplying the correct files. I now have GravityBox running on the Nov Image!
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
ffchampmt said:
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
OP updated to show 19.5.
Had the same issue and ran into the problem getting the modules disabled. Glad you were able to get it up and running.
Sent from my Pixel 3 XL using Tapatalk
i think doing a full uninstall of magisk (removes modules and settings) might be best until twrp or something else comes along...
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
chinesecooler said:
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
Click to expand...
Click to collapse
wait no more!
Woop woop, time for my bi-annually update
dipstik said:
wait no more!
Click to expand...
Click to collapse
Which version of Magisk did you use to patch the boot image? I tried using stable and canary to patch the stock boot image when I updated earlier, but each time it would just reboot straight to bootloader.
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
dipstik said:
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
Click to expand...
Click to collapse
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Face_Plant said:
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Click to expand...
Click to collapse
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
comady25 said:
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
Click to expand...
Click to collapse
It is working for many and not for others. My wife's P3 rooted fine with canary.
jlokos said:
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Click to expand...
Click to collapse
I used this method and it worked with no issues. It was only the second time i used this method but with others having issues with the factory image and patched boot image i thought I'd give it a try.
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk
Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards
So I'm running a Pixel 5 currently, but it sounds like after booting to your patched image, you just need to go grab the Canary version of Magisk from the official GitHub: Magisk 23 Official GitHub.
I've had this happen too after flashing the patched boot image and rebooting back to homescreen.
If you don't install the apk separately it'll try to install Magisk on it's own, but doesn't usually have success in doing so, at least in my experience. So just download the APK from the official GitHub or try the Canary version of Magisk 23. After installing the APK you should be good to go!
If I'm not mistaken, you can grab the APK there or try the "stub-release.apk" for a direct "Canary" version.
The reason I mention the Canary version is because it's like an updated beta, but I've had a lot of success running it myself (Pixel 2XL and Pixel 5).
irxvus said:
Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards
Click to expand...
Click to collapse
The July release works fine with Magisk. Did you have Magisk installed before updating to the July release? If so, did you hide the Magisk app? In that case, you'll have to unhide the app, remove both instances, and reinstall.
If that is not the case, just complete the install as @ProjectAlly said. There is no need to use Canary, though. Currently Canary and Stable are the same.
I've seen recently about a member that rooted Android 14 with no problems. I have followed the steps I always have except using init- b o o t for 13 I did the same procedure on 14 init boot is patched and flashes fine but on reboot no root. Not sure where to go from here. Anyone who has successfully done it have any advice?
Daisymae said:
I've seen recently about a member that rooted Android 14 with no problems. I have followed the steps I always have except using init- b o o t for 13 I did the same procedure on 14 init boot is patched and flashes fine but on reboot no root. Not sure where to go from here. Anyone who has successfully done it have any advice?
Click to expand...
Click to collapse
what version of Magisk are you using?
I imagine it should be a canary version since you are attempting to root Android 14. I have heard that 25206 and 25209 are the ones to use because 25210 and below that isn't those two have severe bugs -- which incidentally shows up as the device not rooted. I've read in other places of this forum that there actually is root access (in those canary versions) to apps, but root isn't detected/established and/or is confirmed in any root checker...
Daisymae said:
I've seen recently about a member that rooted Android 14 with no problems. I have followed the steps I always have except using init- b o o t for 13 I did the same procedure on 14 init boot is patched and flashes fine but on reboot no root. Not sure where to go from here. Anyone who has successfully done it have any advice?
Click to expand...
Click to collapse
You'll have to use either this Pull Request build or Magisk Delta until Canary 25211 comes out. They have a different signature than the other official builds so best to uninstall Magisk and the Magisk app beforehand.
You can find more info about the issue of why Stable Magisk 25.2 or any of the Canary builds aren't fully functional on A14 here.
Lughnasadh said:
You'll have to use either this Pull Request build or Magisk Delta until Canary 25211 comes out. They have a different signature than the other official builds so best to uninstall Magisk and the Magisk app beforehand.
You can find more info about the issue of why Stable Magisk 25.2 or any of the Canary builds aren't fully functional on A14 here.
Click to expand...
Click to collapse
Thanks for this @Lughnasadh! I've never done anything more than stable Magisk, so I wasn't sure how to get a specific build/version of canary; but I knew there was issue after 25206 (except maybe 25209)...
Now I know!
@Daisymae do as Lughnasadh guides...! He'll know better...