Related
So I just updated my pixel to Android 10. And besides the issue with getting TWRP to work, I've been trying, and failing, to get Magisk installed.
I havn't tried the newer Magisk beta yet. Does anyone know if this would work instead?
Thanks
it works with me with the latest TWRP and Magisk
henk-jan said:
it works with me with the latest TWRP and Magisk
Click to expand...
Click to collapse
Okay, so with TWRP 3.3.0 with the no-pin workaround, I wasn't able to install magisk 19.3. However, I was able to get the Beta 19.4 to work.
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
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.
rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"
Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!
I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!