Pixel 3a xl
Android 10 March update
Having problems rooting
Rooting by patching the boot.img with Magisk patch file causes a bootloop.
Tried rooting by installing Magisk via TWRP but when it tries to boot into TWRP I get an error "failed (remote: 'Error verifying the received boot.img: Invalid Parametery" and it won't boot or install TWRP.
I've tried multiple cables, multiple computers, multiple factory resets, fresh installs, unlocked and relocked bootloader, all with the same result when I try boot into TWRP.
Please help.
Thanks
zachjen said:
Pixel 3a xl
Android 10 March update
Having problems rooting
Rooting by patching the boot.img with Magisk patch file causes a bootloop.
Tried rooting by installing Magisk via TWRP but when it tries to boot into TWRP I get an error "failed (remote: 'Error verifying the received boot.img: Invalid Parametery" and it won't boot or install TWRP.
I've tried multiple cables, multiple computers, multiple factory resets, fresh installs, unlocked and relocked bootloader, all with the same result when I try boot into TWRP.
Please help.
Thanks
Click to expand...
Click to collapse
Lol. There's no TWRP for Android 10 and most likely will never be. That would be your main issue right there
Ok. Yeah that could be a problem.
Anyone know why the boot image patch way of rooting causes a bootloop?
zachjen said:
Ok. Yeah that could be a problem.
Anyone know why the boot image patch way of rooting causes a bootloop?
Click to expand...
Click to collapse
Where you already rooted and then it is bootlooping when you updated to the March release? If so, it is likely because of a Magisk module that you have installed that isn't compatible with the March update. There are threads here that walk you through the process of removing Magisk modules without TWRP.
If this is your first time rooting on this phone and you are getting a bootloop, I suspect it is something wrong with your procedure. Usually a bootloop in that situation is because you are not using the stock boot.img file from the current OS version you are running when you use Magisk to modify the file. For example, if you updated to the March release, but somehow are trying to use Feb release's boot.img file you will get a bootloop.
EDIT - also apparently there may be an issue if you are using the latest Canary Build of Magisk with the March update. There isn't a problem with the current stable build and the March update. If you are using the latest Canary build, then this is likely your issue.
Related
I was attempting to update the kernel on my pixel2 xl to use nathan's kernel with wireguard built-in.
My phone has an unlocked bootloader with the critical unlock as well. I am using the stock Google image from the December update.
I have the latest platform tools installed and verified with at the command line.
I downloaded and confirmed the MD5 sums of the boot and dtbo images, and then rebooted into the bootloader to apply them. After flashing them both successfully I rebooted from flashboot to hang on boot. I attempted multiple reflashes of the images without success.
I then attempted to reflash the previous boot and dtbo images again without success. After doing a bit of investigation I flashed the previous images over both slots a and b by using the --set-active fastboot command. This worked and I was able to get the phone boot successfully. I tried flashing nathans boot and dtbo images using the same method but without success.
Is this because of some mismatch between the ROM and kernel I'm trying to flash? Some of the issue?
Thanks
johnnythunder said:
I was attempting to update the kernel on my pixel2 xl to use nathan's kernel with wireguard built-in.
My phone has an unlocked bootloader with the critical unlock as well. I am using the stock Google image from the December update.
I have the latest platform tools installed and verified with at the command line.
I downloaded and confirmed the MD5 sums of the boot and dtbo images, and then rebooted into the bootloader to apply them. After flashing them both successfully I rebooted from flashboot to hang on boot. I attempted multiple reflashes of the images without success.
I then attempted to reflash the previous boot and dtbo images again without success. After doing a bit of investigation I flashed the previous images over both slots a and b by using the --set-active fastboot command. This worked and I was able to get the phone boot successfully. I tried flashing nathans boot and dtbo images using the same method but without success.
Is this because of some mismatch between the ROM and kernel I'm trying to flash? Some of the issue?
Thanks
Click to expand...
Click to collapse
Have you tried just flashing Nathan's kernel zip in twrp, followed by magisk? Or, do you not wish to root?
Latest nathan's would need you to be on january patch i guess,
CMIIW
So the trick is to be on the same release as the kernel or the device will hang during boot?
Badger50 said:
Have you tried just flashing Nathan's kernel zip in twrp, followed by magisk? Or, do you not wish to root?
Click to expand...
Click to collapse
I was not trying to root, simply to get an updated kernel with the wireguard kernel module installed, so no need for twrp or magisk right? Based on Nathan's kernel install posts I just need the platform tools and an unlocked bootloader, but I'm missing something.
Thanks
johnnythunder said:
So the trick is to be on the same release as the kernel or the device will hang during boot?
Click to expand...
Click to collapse
do you success now? i tried many times, same problem.
johnnythunder said:
So the trick is to be on the same release as the kernel or the device will hang during boot?
Click to expand...
Click to collapse
If it hang on G logo, you just need to force it to another reboot. And it will boot.
At least thats how it always been for me with nathan's kernel
But he indeed stated that due to the nature of pixel 2, mismatch rom and kernel version might work, partially work or not work at all.
So its best to match both
From Nathan's January release:
"Remember, you must be on the January update to use the boot image; the zip should work on December. Enjoy!"
You could always boot into TWRP via fastboot (that way TWRP doesn't stick) then flash Flash kernel.zip, and skip Magisk if you don't want root.
Why do you not want root? Magisk has been passing safety net for the last several versions.
I always flash the zip in TWRP, then magisk. If it hangs at the G, just reboot. The reboot has always cleared the hang the few times it has happened.
I did some searching, but could not see a guide for moving from Magisk rooted 8.1.0 to Magisk rooted 9.0. I believe I need to uninstall Magisk, then install the update, but not sure of the exact process. Also, is it better to wipe the data when going from 8.1.0 to 9.0 or doesn't matter?
Thanks in advance!
There's two ways you can do this.
One, you can sideload the OTA using ADB (if on stock recovery), or you can flash the OTA through TWRP.
Two, you can download the factory image, and manually flash the bootloader and radio, then update /system WITHOUT the -w flag, if you don't want to wipe data.
Any time you flash a software update, whether it's the OTA or the factory image, it WILL overwrite /boot, so you will lose Magisk and any custom kernel and recovery. Simply boot TWRP using fastboot, flash Magisk (and TWRP and kernel if desired), and you'll be good to go.
No need to wipe data. My process for installing OTAs and re-rooting has always been the same and it's no different with the 9.0 update other than one exception I encountered (patching the boot image AFTER updating).
I prefer the boot image patching method:
Download the latest platform-tools from Google
Download both the OTA and full factory images
Extract boot.img from the factory image
If already rooted prior to updating, re-flash current stock boot image
Sideload OTA
Patch the extracted boot image with Magisk (make sure you're on the latest version; 16.7 beta channel)
Flash patched boot image
Normally I patch the boot image prior to sideloading the OTA but it resulted in an endless boot after the 9.0 update.
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
machx1111 said:
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
Click to expand...
Click to collapse
Here's a bit more specific guide for updating to 9.0
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77269862
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.
clambert11 said:
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.
Click to expand...
Click to collapse
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!
sb1893 said:
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!
Click to expand...
Click to collapse
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.
clambert11 said:
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.
Click to expand...
Click to collapse
If your platform-tools are r28.0.1
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- install ElementalX kernel
- tap Add more zips
- select Magisk-18.1.zip
- swipe slider to install
- reboot
Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!
clambert11 said:
Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!
Click to expand...
Click to collapse
I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?
Ivanstein said:
I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?
Click to expand...
Click to collapse
Forget side loading!
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- tap install select Twrp-3.2.3-1.zip
- swipe slider to install
- reboot recovery
- tap install select Magisk-18.1.zip
- swipe slider to install
- reboot
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it
mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.
jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.
Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Sumit Sikder said:
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Click to expand...
Click to collapse
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
I tried the latest v22.1. It worked in Android 11 evolution X ROM but not in realme UI 1! The only reason I installed my Android 10 was because Magisk modules weren't working in Android 11!
oxbowlarry said:
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
Click to expand...
Click to collapse
I have seen another rooting method with ADB and the patched boot image BUT that method first flashes vbmeta.img before flashing the patched boot.img.
Perhaps that is why my boot partition was corrupted because I just flashed the patched boot.img.
Has anyone had success with this rooting method on a Realme 6 pro ?