Related
downloaded factory image from googles website
copied latest platform tools to the same directory as the extracted contents of the zip from google.
run the batch file, can boot into android just fine.
reboot to bootloader, use fastboot boot twrp-3.2.3-0-walleye.img
install the twrp zip
android boots fine and i can use my phone normally.
install magisk apk, reboot to recovery, install magisk 16.7 zip, android wont boot
everything was fine until i made a backup last night within twrp. ive repeated the above process idk how many times. any help would be appreciated
EDIT: https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417 is the guide i was using.
EDIT 2: now when i install TWRP and try to reboot to system, it just reboots back to TWRP...
EDIT 3: looking at the contents of my twrp zip, theres a file called magiskboot so what im going to do is reinstall the factory image using the bash script included in the download directly from google, then just flash twrp-pixel2-installer-walleye-3.2.3-0.zip, then install the magisk manager and see what happens. if that doesnt work ill redo the factory image, boot from twrp-3.2.3-0-walleye.img, install magisk, and see what happens without installing twrp.
Can you use Android Q on the pixel A along with rooting?
sillyshyme said:
Can you use Android Q on the pixel A along with rooting?
Click to expand...
Click to collapse
Unfortunately, not. The pixel 3, 3a as well as the xl versions of both currently do not have magisk for Android q. The dev is working on it though. Keep your ear to the ground
Sent from my Pixel 3a using Tapatalk
Yes. The Pixel 3/3a versions use logical partitions in the Q beta. and it sounds like it's taking a major re-write to support it. I believe it is called system-as-root. The developer John Wu has been posting about it on Twitter. https://twitter.com/topjohnwu
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
12paq said:
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
Click to expand...
Click to collapse
It's pushed to the Cannery build https://twitter.com/topjohnwu/status/1144159892430659584
Magisk and TWRP all in the same day!
@pharpe wait TWRP got released?
Tiebe said:
@pharpe wait TWRP got released?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413
did any one successfully root q ?
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
Yeah, can confirm, did this earlier today!
Just a question, did you have the issue that many apps show up in the appdrawer of pixel launcher, even if they shouldnt? (like Google PDF Reader, Sd Maid unlock or sideloaded Pixel livewallpapers etc.)
I guess its because of the bootloader is unlocked (for security reasons)?! Just really weird. No other issues observed till now.
peace!
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
removed
pharpe said:
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
Click to expand...
Click to collapse
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
bejunk said:
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
Click to expand...
Click to collapse
Interesting. I never realize that. I keep all my apps organized in folders so I only go to the app drawer for things I rarely use. I just assumed everything that was installed was in there.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
c_tho said:
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
Click to expand...
Click to collapse
That is my understanding from what I have read but I have not actually done it. You would uninstall via Magisk and it restores the original boot.img that it has backed-up. Then you are back to stock to take the OTA.
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.
Hello y'all, i want to root my phone, i followed several tutorials and installed image file of twrp v 3.2.3 , lazyflasher.zip and magisk.zip . Tried flshing the twrp image file through fastboot, but it is unable to decrypt my data and is asking for a password, installed a later version of twrp v 3.4.0 and tried the same, it was able to decrypt , Now i succesfully entered TWRP and then i first installed the image file but i was not able to install the ladyflasher.zip(error 1 cannot unpack zip file) so i avoided the lazyflasher step and directly tried installing magisk and it said successful, but when my phone rebooted there was no magisk app and my phone is not rooted! Tried with different versions of magisk like v 16 and v 23 , still no effect. Also instead of magisk zip file i installed supersu zip file and still the result is same ( No supersu app on phone and thus not rooted)!
Reflash Stock ROM to get rid off of all mods you applied so far, then retry.
Issue Solved! Thanks for your tip @xXx yYy , but i solved it! Basically the absence of magisk app is not a problem, i manually installed the magisk manager and basically upgraded the magisk version(I flashed v 16 through twrp, magisk manager required v 23 and above) so i clicked install within the app and boom! root access is granted, crazy but anyways it did work , so issue solved