I had same issue. If you did not update platform tools update to latest version. I spent hours bashing my head on the desk.
I had same issue. If you did not update platform tools update to latest version. I spent hours bashing my head on the desk.
I rooted my device,flash magisk_patched.img with twrpGetting error in fastboot "Enter reason: error boot prepare". Not working for me, on the latest 10 firmware like you.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
My bad wrong boot.img...
---------- Post added at 08:05 AM ---------- Previous post was at 07:36 AM ----------
works fine thx OP!
---------- Post added at 08:43 AM ---------- Previous post was at 08:05 AM ----------
Thanks OP! I have just rooted my Pixel 3 XL using this method, works fine.
I'm getting the same bootloop issue. Any progress?I'm on platform-tools_r29.0.4-windows and MM canary 578a50b4
Im currently using it and it works fineI had it working before I bodged a magisk module install
Theres no way you can run TWRP with rooting using this methodSame exact problem here, anyone have any success after getting into this situation?
Newest October Update + latest Magisk Canary finally did the trick! It booted straight up and let me uninstall the old Edge Sense Module within Magisk that prevented me from installing and booting Magisk for the last couple of weeksI've followed the tutorial step by step, but after flashing the patched boot.img my P3 goes into bootloop. All I can do is flash firmware (without wipe) again to fix it. All updated until Android 10 worked flawlessnessly with restoring magisk modules and the lot. Not sure if it it edge sense module that, when flashing the patched Boot.img gets active and prevents the phone from booting up because it's not compatible with Android 10. Though I have no idea how to get rid of Magisk modules completely now that I can't boot into TWRP anymore and a downflash to Android 9 firmware doesn't work either. Stuck with Android 10 w/o root for now
>adb push boot.img /sdcard/boot.img
boot.img: 1 file pushed. 34.1 MB/s (67108864 bytes in 1.874s)
>adb pull /sdcard/Download/magisk_patched.img magisk_patched.img
/sdcard/Download/magisk_patched.img: 1 file pulled. 3.6 MB/s (31600640 bytes in 8.481s)
>adb reboot bootloader
*wait for fastboot to come up*
>fastboot flash boot magisk_patched.img
Sending 'boot_a' (30860 KB) OKAY [ 0.788s]
Writing 'boot_a' OKAY [ 0.175s]
Finished. Total time: 1.270s
>fastboot reboot
Rebooting OKAY [ 0.040s]
Finished. Total time: 0.059s
>adb pull /sdcard/Download/magisk_patched.img magisk_patched.img
/sdcard/Download/magisk_patched.img: 1 file pulled. 4.3 MB/s (31612928 bytes in 6.989s)
>adb reboot bootloader
*wait for fastboot to come up*
>fastboot flash boot magisk_patched.img
Sending 'boot_a' (30872 KB) OKAY [ 0.809s]
Writing 'boot_a' OKAY [ 0.472s]
Finished. Total time: 1.559s
>fastboot reboot
Rebooting OKAY [ 0.050s]
Finished. Total time: 0.050s
Or use adb, since Magisk Canary b19309 is out:I wish i found this before i wiped my phone.
If you are in a bootloop due to enabling an unsupported magisk module, take a look at this thread.
https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867
hope it helps
I am running latest factory build and Magisk v20. I used the Magisk Manager to create the magisk_boot.img. I have never done an OTA update so everything is still on partition A.I've been holding off on upgrading my Pixel 3 to Android 10, hoping to soon be able to do it with the stable version of Magisk. Everything in this thread is talking about Magisk v19.x ... but mine updated to v20 a few days ago. Is v20 possibly going to let me use the A/B OTA method, or will I lose root (or cause other/worse problems) by doing so?
Answering my own question here ... but it might help someone else in the same situation:I've been holding off on upgrading my Pixel 3 to Android 10, hoping to soon be able to do it with the stable version of Magisk. Everything in this thread is talking about Magisk v19.x ... but mine updated to v20 a few days ago. Is v20 possibly going to let me use the A/B OTA method, or will I lose root (or cause other/worse problems) by doing so?
I did with my pixel 3. Follow the instructions in the op. Worked like a charm. ?Reading all the messages in here I am still unsure about rooting my Pixel 3 on Android 10.
I had Magisk & Xposed, but uninstalled it for the OTA firmware update.
I am now on unrooted Android 10 - how can I install Magisk for root access?
Can I?
Follow the instructions in the OP. It requires an unlocked bootloader. It specifies Magisk Canary, but that is no longer necessary. Stable Magisk has been updated to version 20.0, which incorporates the changes needed for Android 10.Reading all the messages in here I am still unsure about rooting my Pixel 3 on Android 10.
I had Magisk & Xposed, but uninstalled it for the OTA firmware update.
I am now on unrooted Android 10 - how can I install Magisk for root access?
Can I?