Database Develop

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Link for a clean 10.0.3 Boot.img

Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,

aliensk said:
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
Click to expand...
Click to collapse
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12

lept_2014 said:
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
Click to expand...
Click to collapse
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.

Hey guys,
I managed to resolve the bootloop issue. If anyone has the same issue use the following untouched boot.img
https://xiaomifirmware.com/download/11657/
As I was suspecting, the ones I was using the from the links provided in the forum were too small and this one is 64 mb. After flashing it boots perfectly.
However, unfortunately again I get errors during the update. At least no bootloop

aliensk said:
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Click to expand...
Click to collapse
That Stock BOOT works fine for me. Remember flash it into the right slot for you.

I did flash to to slot B as the getvar current-slot was B but it was still bootlooping until i tried the last one from the link I provided. However, since I am still unable to update, is there a link to download the system.img for 10.0.3.0 just in case i have somehow modified my system? I dont remember to have done anything but just in case.
Thank you.

How will you solve it
Plz...tell me with boot file how fill solve your problem

Varshithpoudala said:
Plz...tell me with boot file how fill solve your problem
Click to expand...
Click to collapse
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful

aliensk said:
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
Click to expand...
Click to collapse
Did you find any way to fix it?

THE root method. (any android version. yes 10 stable)

Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.

<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.

Can't we just flash Magisk on TWRP?

yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.

e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.

There is a new version of twrp, build .27 that is meant to fix backup / restore issues

Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.

e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'

Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.

Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.

UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.

greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.

e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.

greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?

Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching

e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."

e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.

e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.

greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.

"error boot prepare" in fastboot trying to flash magisk patched boot.img

Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?

DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:

Badger50 said:
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Click to expand...
Click to collapse
Thanks for the suggestions. I tried each one. Unfortunately, no luck.

DoughMucker said:
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
Click to expand...
Click to collapse
Bummer man! How about different 2.0 USB A to USB C cables and ports??

Badger50 said:
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Click to expand...
Click to collapse
Just tried that too. :crying:

DoughMucker said:
Just tried that too. :crying:
Click to expand...
Click to collapse
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try

Badger50 said:
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Click to expand...
Click to collapse
I was stable before, but had just tried canary. Same situation.
I'm reading https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605/page6 and wondering if it's related to systemless hosts for adaway which i did not disable.

DoughMucker said:
I was stable before, but had just tried canary. Same situation.
I'm reading and wondering if it's related to systemless hosts for adaway which i did not disable.
Click to expand...
Click to collapse
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.

Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I'm using 012.A1. Google updated their factory image/OTA site and removed the reference to ATT. I had double checked someone else's phone here that got the Dec OTA update and she had 012.A1 after being on 007.A3.
Going to take a break from trying things for a day or so because it's frustrating. Arrghh.
And thanks for the help!

Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?

DoughMucker said:
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
Click to expand...
Click to collapse
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:

Badger50 said:
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Click to expand...
Click to collapse
The first time I successfully patched the November boot.img I did not check off dm-verity. I didn't either for the first time(s) I tried the December image. I only tried, unsuccessfully, with dm-verity checked after you mentioned it here.
I did have the Systemless Hosts module enabled when patching the December image. This is what I was referring to earlier when I mentioned I thought it was related to systemless hosts for adaway. I actually didn't realize that when you enabled that in Magisk Manager, that it installed a module. So I never thought I had a module active, but I did.

To end this saga...after getting root again, I did a Titanium Backup, Factory Reset, and re-rooted by patching boot.img again with Magisk Manager canary. It went smoothly, as it should have originally. Now to restore....

This error seems to occur when you flash a boot.img that doesn't match the exact firmware version.
=> Download the correct, currently installed full firmware package, extract the boot.img and flash it.

Solution
This occurs when you're on Android 11 build and try to install the Android 10 build.
There's a simple fix though, thankfully.
Download the Android 10 ota image for Pixel 4 XL from google, and extract the dtbo.img from it. Flash it using
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
If that doesn't work, you can flash the whole stock Android 10 build and then you can boot whatever you were trying to.
Please click "Thanks" if this worked for you so that others can see.

Same Issue on Pixel 3a XL - please Help
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''

dadu1257 said:
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Post your question on the Pixel 3a XL 'Question and Answer' thread, not the Pixel 4 XL 'Question and Answer' thread.
or
Post your question on the LineageOS 17 thread.

Rooted 4a 5G still on January version, how do I update?

I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?

WhiteAsIce said:
I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
Click to expand...
Click to collapse
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh

Edit: See below.

Tulsadiver said:
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Click to expand...
Click to collapse
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?

WhiteAsIce said:
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
Click to expand...
Click to collapse
Did you leave any modules on your phone?

Tulsadiver said:
Did you leave any modules on your phone?
Click to expand...
Click to collapse
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.

WhiteAsIce said:
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
Click to expand...
Click to collapse
You are rooted with magisk but don't know what magisk modules are?

Tulsadiver said:
You are rooted with magisk but don't know what magisk modules are?
Click to expand...
Click to collapse
The only one I had was a mod to allow safetynet to pass.

My phone is rooted with magisk, so I need to do the monthly updates manually. In order to do this, I download both the OTA and the factory image. I update the phone using the OTA. I extract the boot.img file from the factory image, put it on the pixel after updating and patch it with magisk. Then I copy it to my computer and flash it to the active boot slot as described below.
Too late to help now, but the issue was probably that the pixel has two boot slots, boot_a and boot_b, and it was booting from the wrong one. The -w you used finally is the wipe option and it's done by default unless you remove it, so that's why the phone was wiped.
In my case, I used the following commands to make sure that I flashed to the correct slot and/or booted from the correct slot that had the magisk patched kernel:
fastboot getvar current-slot
fastboot flash boot_a magisk_patched.img
If it's ever necessary, you can manually change the active boot slot: fastboot --set-active=a
If you flash the correct magisk-patched kernel to either slot and set the phone to boot from that slot, your phone will boot up. I learned about this the hard way and now, every month, I just make sure that I flash to the currently active slot and have not had a problem since. One of the nicest things about having a pixel is that they are just about impossible to brick - it's just a matter of redoing things properly.