Were you able to recover and flash? The android flash tool has been a great "last ditch" utility, you may be able to skip wiping the phone too.
How To Guide Method to upgrade every month, without wiping data and retaining root
- Thread starter gururoop
- Start date
In the past, I disabled Magisk before flashing a new update by reflashing the stock boot.img. I would then flash-all with -w removed and then reroot with Magisk.
When I tried that approach today, the phone hung on the "Google" screen. I tried going back to the magisk rooted boot.img and the system hung at the same place. I was on the December release.
Thankfully I could get back to fastboot. I ran the flash-all w/o -w for the January update. Everything is good now and I rerooted with Magisk.
Any thoughts on why my old approached failed?
When I tried that approach today, the phone hung on the "Google" screen. I tried going back to the magisk rooted boot.img and the system hung at the same place. I was on the December release.
Thankfully I could get back to fastboot. I ran the flash-all w/o -w for the January update. Everything is good now and I rerooted with Magisk.
Any thoughts on why my old approached failed?
Last edited:
Thanks for the heads up.
I actually have an older MacBook and I've never been able to get shell scripts to work when updating android devices. I end up have to execute each line manually in Terminal. Not the end of the world and this guide worked perfectly updating to Jan from Nov. Thanks OP!
Uninstalling magisk isn't needed but I would recommend to deactivate the modules because you could run into bootloops.
But even that is easy to fix. If you get a bootloop, just reboot into safemode and reboot the phone again. This will automatically deactivate all modules.
Maybe too easy... [looks back, paranoid, expecting the zombies to attack at any minute...]
Definitely disable modules. Some of the modules I had installed caused a bootloop on the Jan release.
Thanks for the tips.
It is wierd that this edited script does not work for me on Pixel 6, I have tried several times, the phone did not boot . Finally I had to managed to remove "-w", then flash-all, then flash patched boot.
The patched boot was renamed just like it shows in the flash-all?
Yes, I did it strictly according that tips. cmd windows also show that the patched boot img was flashed but it failed boot into systme just got a bootloop when powered by android appeared.
Thanks for the guide. Worked first time. No problems. Disabled Magisk modules just to be sure.
Oh damn, this worked for me in Dec, but the Jan version horked itself. It looks like it didn't observe the --skip-reboot and tried to reboot after the update, but before flashing the patched image. Now I get a corrupted message.
edit- or maybe I should not have disabled-verity. I can't remember if it did in Dec or not.
Is it possible to get adb working again without wiping? I can connect, but the device is no longer authorized.
edit- or maybe I should not have disabled-verity. I can't remember if it did in Dec or not.
Is it possible to get adb working again without wiping? I can connect, but the device is no longer authorized.
Last edited:
Same here. How do we fix this?
EDIT: Fixed it by sideloading OTA - no data wipe!
Can't update 1/2020 flash, phone stuck in bootloader please help!
ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!! Hello all, I'm hoping someone has some advice: I downloaded the 1/2020 factory image, removed the -w from the .bat...
forum.xda-developers.com
Last edited:
Unplug your phone.
On windows, go to <user>/.adb folder (it's hidden) then delete adb.key
Go to your phone > developer options > revoke adb authorization
Plug your phone again, it will ask for authorization. Allow it.
Thanks. Unfortunately I can't get into the phone. It just goes straight to recovery.
I wasn't able to figure out a workaround, so I just wiped and started over.
Hate to make this comment, but you guys know that the manual flashing steps haven't really changed much in the last decade, right? I keep seeing random guides popping up that seem a bit more confusing than necessary. Perhaps I'll make a post explaining what to do in the near future or when the next factory image is released. As it seems that a proper guide would be beneficial for some users here.
Just note that my method is for dirty flashing; where you will be keeping your content and root after updating. Shoot me a message if you would want me to throw a step-by-step guide together sooner.
Best of luck all!
Just note that my method is for dirty flashing; where you will be keeping your content and root after updating. Shoot me a message if you would want me to throw a step-by-step guide together sooner.
Best of luck all!
Same here. How do we fix this?
EDIT: Fixed it by sideloading OTA - no data wipe!
Can't update 1/2020 flash, phone stuck in bootloader please help!
ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!! Hello all, I'm hoping someone has some advice: I downloaded the 1/2020 factory image, removed the -w from the .bat...
This worked for you? I couldn't get it to sideload unauthorized.
I keep the flash-all.bat file each month so I know exactly what parameters were used last time. I plan on continuing to disable verity and verification even tho I know it's not required with the new Magisk. There's no downside, (that I know of) and I don't want to risk having to do a wipe.
Once TWRP is available (hopefully soon) all of this will be moot as we can make an image backup before the update and just restore it if something goes wrong.
Once TWRP is available (hopefully soon) all of this will be moot as we can make an image backup before the update and just restore it if something goes wrong.
Yes it worked. I tried the flash-all.bat and it failed again as before, so I sideloaded again (lost root) and then just booted the rooted image and rerooted.
Any idea what we are doing wrong with the January update? I loaded the Dec update with this exact process and it was fine...
I have always flashed the factory zip, not the OTA Zip and never had an issue. I think doing the factory image is the safest way.... Just my thought on kt
Top Liked Posts
-
There are no posts matching your filters.
-
8I don't know why folks continue to have issues updating when a new Android update is released. Despite Magisk having the option to install to an inactive slot for easy OTA updating, I simply avoid it and go the old-school route of updating via sideload to prevent any issues.
In hopes of putting to rest issues some of you face, here is what I do:
- Make a backup of all my important files in case something goes wrong
- Disable any Magisk modules if it makes you feel any safer
- Download the OTA image online and NOT from the system update!
- Reboot to recovery and sideload the OTA by using:
Code:adb reboot sideload- Then, in recovery I load up the file by using:
Code:adb sideload "insert OTA file name here.zip"- Once it finishes, you will be in recovery mode. Select "Reboot to system now".
- Once the system reboots, I unlock the device and let it finish completing the update before anything else.
- Getting the NEW boot.img file from the full factory image
- Copy it to my mobile device
- Open up Magisk and patch the boot.img file
- Copy the patched file to my PC
- Reboot into bootloader using:
Code:adb reboot bootloader
Then, patch the new boot.img using:
Code:fastboot flash boot "patched_boot.img"
Reboot / Done.
I have not had it fail once using this process on stable Magisk and NO "disable" tags. The only reason I can see for anyone to use Canary versions of Magisk or "disable" tags, is if its absolutely required for some modules, ROMs, or kernels you are using. If it's not needed, just leave it alone.
You could technically just dirty flash the entire full factory image using the Android Flash Tool or flash-all.bat script on your PC, but the script file is where I find most folks mess up because they copy and pasted instructions improperly, or there's a line of code they forgot to add or remove without proofreading before running the script. I'd rather take matters into my own hands, even if it means completing more steps to make sure things go smoothly.
Anyway, I hope this helps someone!4
I updated the App, (but not the actual Magisk) to 24306 right before I started. I then copied over the boot.img, patched it with the new App, and copied it back to the PC. I then followed the instructions in the OP.
FYI. I still have "--disable-verity --disable-verification" in my update command line. I know it's not required with the new Magisk, but it's been working since the beginning and I see no reason to change it as I've had zero problems updating every month with it in there.
Best of luck!3So, it was a bit different for me this time. I was experimenting and was rooted with Magisk Alpha (t.me/magiskalpha) on 13 Beta 1 when Beta 2 was released. So, I decided to go back on official Magisk Canary, but I didn't re-root Beta 1 with official Canary. However, I installed the latest Canary apk on Beta 1 and patched Beta 2 boot.img and updated using the method I posted in OP.
I booted fine in Beta 2 but could not open Canary app (as was the case with everyone). I tried clearing data of the Canary app, tried reflashing patched boot.img, tried patching boot.img with Alpha and flashing on both slots before realizing that root wasn't working for anyone on Beta 2.
When update to Canary was announced, I simply downloaded the latest Canary apk, patched Beta 2 boot.img and flashed it in bootloader. Now, I haven't wiped my device in a long time and my verity and verification are not disabled (if there is any way to show that, please let me know and I will share it with everyone).
I was fortunate for not having to disable verity or verification (and in the process wipe data) like others on Beta 1.3
Thanks for the heads up!
For anyone wondering, I was successfully able to update to the May patch with magisk canary 24307.2
Thanks for the guide bro, very useful. Out of curiosity, which Magisk did you use to patch the May boot.img?
Cheers -
66Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling verification and verity and did not have to wipe their phones, but request everyone, who have verification and verity disabled and using this guide, make sure you backup all the data and post your results here (I suggest backing up data anyway for everyone).
Following is a guide to update Pixel 6 Pro (perhaps all Pixel devices) every month, without wiping and retaining root. I tested it on my Pixel 6 Pro from 12.0.0 (SD1A.210817.015.A4, Oct 2021) to 12.0.0 (SD1A.210817.036, Nov 2021). There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google site and extract them in one folder.
2) Extract the boot.img from image-raven-xxxxxxx.zip which was extracted from the image in the above step and patch it in Magisk Manager (latest canary build from https://github.com/topjohnwu/Magisk) on your phone and copy it back to the folder where you extracted the factory image and platform-tools. Rename the copied file to magisk_patched.img
3) Open flash-all.bat in notepad, add --skip-reboot and remove -w from the fastboot update line. Also add the following lines after the fastboot update line to flash the Magisk patched boot.img automatically:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
After editing, the edited part of your flash-all.bat should look something like this:
Code:fastboot --skip-reboot update [****image_name****] fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot flash boot magisk_patched.img fastboot reboot echo Press any key to exit...
Note: [****image_name****] is just a placeholder and needs to be the name of zip file which was originally there in flash-all.bat, do not change that. Be careful to rename the Magisk patched boot.img to magisk_patched.img or in the alternative make appropriate modifications in the flash-all.bat
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Update 1: I updated from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SD1A.210817.037, Nov 2021) successfully using my method, without loosing data and root.
Update 2: I updated from 12.0.0 (SD1A.210817.037, Nov 2021) to 12.0.0 (SQ1D.211205.016.A1, Dec 2021) successfully using my method, without loosing data and root.
Update 3: I updated from 12.0.0 (SQ1D.211205.016.A1, Dec 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022) successfully using my method, without loosing data and root.
Update 4: I updated from 12.0.0 (SQ1D.220105.007, Jan 2022) to 12.0.0 (SQ1D.220205.003, Feb 2022) successfully using my method, without loosing data and root.
Update 5: I updated from 12.0.0 (SQ1D.220205.003, Feb 2022) to Android 12L DP 3 successfully using my method, without loosing data and root.
Update 6: I updated from Android 12L DP 3 to Android 13 DP successfully using my method, without loosing data and root.8I don't know why folks continue to have issues updating when a new Android update is released. Despite Magisk having the option to install to an inactive slot for easy OTA updating, I simply avoid it and go the old-school route of updating via sideload to prevent any issues.
In hopes of putting to rest issues some of you face, here is what I do:
- Make a backup of all my important files in case something goes wrong
- Disable any Magisk modules if it makes you feel any safer
- Download the OTA image online and NOT from the system update!
- Reboot to recovery and sideload the OTA by using:
Code:adb reboot sideload- Then, in recovery I load up the file by using:
Code:adb sideload "insert OTA file name here.zip"- Once it finishes, you will be in recovery mode. Select "Reboot to system now".
- Once the system reboots, I unlock the device and let it finish completing the update before anything else.
- Getting the NEW boot.img file from the full factory image
- Copy it to my mobile device
- Open up Magisk and patch the boot.img file
- Copy the patched file to my PC
- Reboot into bootloader using:
Code:adb reboot bootloader
Then, patch the new boot.img using:
Code:fastboot flash boot "patched_boot.img"
Reboot / Done.
I have not had it fail once using this process on stable Magisk and NO "disable" tags. The only reason I can see for anyone to use Canary versions of Magisk or "disable" tags, is if its absolutely required for some modules, ROMs, or kernels you are using. If it's not needed, just leave it alone.
You could technically just dirty flash the entire full factory image using the Android Flash Tool or flash-all.bat script on your PC, but the script file is where I find most folks mess up because they copy and pasted instructions improperly, or there's a line of code they forgot to add or remove without proofreading before running the script. I'd rather take matters into my own hands, even if it means completing more steps to make sure things go smoothly.
Anyway, I hope this helps someone!7So I notice there are some people, like me, that are a bit confused on how to exactly do this process. I like to be nice every once in a while, so this is my time. I will try to do a step by step process with exactly how I did after reading, and re-reading all the comments on how to do it (with pictures cuz I need pictures to learn haha).
These are the exact steps I took when I updated from .36 to .37
I downloaded the .37 zip, the one for your phone, mine is an unlocked version.
Slapped the .37 zip file into a folder by itself so I can extract it inside that same folder. It should look like this once its extracted inside the same folder.
Then I opened another folder/window with the Platform-tools so I can easily navigate between the 2 folders.
Then I opened the flash-all.bat from the zipped folder, to see what it contains, noticed that it flashes 3 files/images.
“bootloader-raven-slider”
“radio-raven”
“Image-raven-sd1a”
Then close the file as we dont need it right now.
So with this I know that I will need to add those 3 files to the platform-tools folder when I go to actually run the command.
I actually took the .37 boot.img and copied it into my pixel with version .36 still running.
The boot.img is inside the zipped folder and when you extracted it, it will now be viewable along with other files and the zipped folder still there.
copy this boot into the main folder of the pixel
On your Pixel, open Magisk and click install then select patch file, navigate to the boot.img file in your internal storage.
Patch it with Magisk and then take the patched boot.img (which that file will actually be in your downloads folder in your Pixel) and copied it back to my computer.
So as of now, it seems we are able to patch boot.img with current build without having to update then patch then flash. We can just patch on the current build then copy the patch to the computer and run the rest of the steps.
Now that I have the patched boot.img on my computer, I will take all the highlighted files in the picture, plus the patched boot.img over to the Platforms-tools folder and just copy them in that folder.
Here, I’m not sure how everyone else has their folder since I rarely use those tools, so I just add the files and then delete them after I’m done flashing. See picture of all copied in files. (dont forget your patched boot.img)
Now I will open the flash-all.bat that's inside the Platform-tools using Notepad ++ (personal preference).
Edit this file exactly like in the picture. Add the lines exactly how it shows in the picture.
**NOTE** that you need to type the exact patched boot file in there. So, like in this picture, but with YOUR patched "magisk_patched" file as this will have your own ID after 23014.
once you made the edits on this file, dont forget to save it before you run the commands!
Now plug in your phone to the computer.
Make sure you have USB debugging turned on.
Press shift and right click inside the Platform-tools folder and open Command Prompt.
run these 2 commands:
adb reboot bootloader
flash-all.bat
When it's all done, your phone will boot up and you will be on the new .37
Nothing else to add here as it will literally run through everything for you and boot up and you're done.
Hope this helps someone, as I am a visual learner myself.7
holy poop that worked!! i was scared to try it myself but since i have a backup phone with all my data on it, it wouldnt be so bad to wipe the pixel if i messed it up doing it this way! But hey, it actually worked!!
here is the modified flash-all and yes you will need the "ping" line after the update line.
so with this, no need to type extra stuff, just add it all in the flash-all file and run the first 2 commands:
adb reboot bootloader
flash-all.bat
and thats it, the only time consuming part is patching the boot, putting it in the folder with the platform-tools.
