I'm just getting sick of waiting. I tried unlocking the bootloader 30 days ago when it told me to wait 720 hours and now 30 days later I need to wait additional 360 hours?
now is is possible to unlock the bootloader without waiting, like just straight up installing twrp without playing the waiting game?
hard to explain, I hope you get what I mean
I guess no. Unlocking bootloader is performed with token which is generated on xiaomi's servers.
pissgoat said:
I'm just getting sick of waiting. I tried unlocking the bootloader 30 days ago when it told me to wait 720 hours and now 30 days later I need to wait additional 360 hours?
now is is possible to unlock the bootloader without waiting, like just straight up installing twrp without playing the waiting game?
hard to explain, I hope you get what I mean
Click to expand...
Click to collapse
on lg g4 we used to innejct root by injecting a rooted system. img not sure about RN5
Should it possibly try again, also had a remaining waiting time of 290 hours.
Habs today again with the latest MiFlash tool and digs loosely ..... unlock
the Bootloader went without problems .... for whatever reason
sorry for my bad english
You can root your phone using Magisk Manager to patch boot.img and re-flashing Miui.
onliner said:
You can root your phone using Magisk Manager to patch boot.img and re-flashing Miui.
Click to expand...
Click to collapse
And how will you install magisk without unlocking bootloader? Nonsense
Incogn said:
And how will you install magisk without unlocking bootloader? Nonsense
Click to expand...
Click to collapse
From Magisk thread:
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Sometimes it is good to investigate before speaking, have a good day :fingers-crossed:.
onliner said:
From Magisk thread:
Via Magisk Manager:
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Sometimes it is good to investigate before speaking, have a good day :fingers-crossed:.
Click to expand...
Click to collapse
First time im hearing of this. Im 90% sure that wont work, as it shouldnt allow you to flash unsigned boot.img on locked bootloader. Heck, im 99.9% sure it wont work. So yeah, its good thing to investigate before speaking lol
onliner said:
From Magisk thread:
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Sometimes it is good to investigate before speaking, have a good day :fingers-crossed:.
Click to expand...
Click to collapse
similar to pushing whole rooted system.img back in the days there was no magisk.
Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
Code:
fastboot-devices
fastboot flash bootloader new-bootloader-image (then reboot into bootloader)
fastboot flash radio new-radio-image (then reboot into bootloader)
fastboot flash update new-update-image (then reboot into twrp)
fastboot boot twrp-image
2.
In TWRP Decrypt data and install Magisk newest release
3.
Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update
ericedg said:
Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
2. In TWRP Decrypt data and install Magisk newest release
3. Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + January 2019 Security Patch
'If Stock'
Do #4 'keep data'' then do #8 to root/Reroot
'If Custom ROM'
Read #11
The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.
dhufford81 said:
The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.
Click to expand...
Click to collapse
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.
smartymcfly said:
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.
Click to expand...
Click to collapse
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!
dhufford81 said:
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!
Click to expand...
Click to collapse
TWRP had the ability to flash the OTA update on P2XL. It might be something that works again P3XL in the future.
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Step 2:
so the phone booted, and I ran the update again. This time I had no issues installing it.
Step 3:
i extracted the new Boot.img from the rom downloaded by LMSA
I re patched the new boot.img with magisk, rebooted again, and and the update was complete.
this was done on the eu g8 power , for update qpe30.79.124 , but i guess this will work on all versions since the process is the same ...
for people reading this, and don’t have root / want root, just read this thread:
Confirming success with this. I downloaded the whole ZIP, extracted boot.img and used Magisk App's built-in feature to mod the boot img. Afterward, I reflashed boot partition via fastboot. Thanks, all!
Success on Sophia RETUS 80-51-5. Flashed 80-51-3 stock boot with fastboot, took update, extracted BOOT from 80-51-5, modified with Magisk and flashed the mod with fastboot. Back up and running.
I have twrp installed. Will this work?
No, I don't believe so.
3dekstron said:
I have twrp installed. Will this work?
Click to expand...
Click to collapse
As far as I know you will also have to flash the stock recovery before updating... not sure if the recovery has to match the stock rom build, like the boot.img does. You could also flash the entire latest stock rom using LMSA to update.
pjottrr said:
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Click to expand...
Click to collapse
What does this mean (from above) and what results are to be expected?
I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
Click to expand...
Click to collapse
I'm guessing that a fail is expected since original boot.img is no longer installed (ie, rather the patched version is installed). Hopefully someone can elaborate
Also in the case of the Magisk systemless root method, will OTA announcements occur even though they can't be installed without first unrooting?
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
TaZeR369 said:
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
Click to expand...
Click to collapse
I just did that with a sofia retus phone on Android 11 for the new security update.
RPM31.Q1-54-13 to RPMS31.Q1-54-13-2.
1. Uninstall all Magisk modules and reboot
2. Uninstall Magisk and hit restore image
3. Uninstall Magisk completely and phone reboots
4. Accept OTA update (nervously)
5. Patch boot image with Magisk
6. Flash patched image with minimal adb and fastboot
7. Success!
this process does replace vanced youtube with factory youtube and youtube music, but it's easy to just replace them again in vanced manager.
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
V0latyle said:
DO NOT take the automatic OTA if you are rooted.
Click to expand...
Click to collapse
Well, that explains why I haven't been able to update boot with my patched file.
First I've heard of it and not sure I'm ready to wipe everything and start over.
Sucks to be an early adopter.
Thanks for the post.
Hi ! Thanks for the thread .
Just one question ?
Why they had "--slot=all" for flash vmbeta and patch boot.
ggkameleon said:
Hi ! Thanks for the thread .
Just one question ?
Why they had "--slot=all" for flash vmbeta and patch boot.
Click to expand...
Click to collapse
The OTA is an out of band update, meaning it installs to the inactive slot. I like to command a flash to both slots just to be safe. It may not really be necessary, but again, better safe than sorry.
V0latyle said:
The OTA is an out of band update, meaning it installs to the inactive slot. I like to command a flash to both slots just to be safe. It may not really be necessary, but again, better safe than sorry.
Click to expand...
Click to collapse
Ok Thank you I understand... Just I do it now. Have a good day
ggkameleon said:
Ok Thank you I understand... Just I do it now. Have a good day
Click to expand...
Click to collapse
NO U
V0latyle said:
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Boot Verification.
On Android 12, disabling verity and verification will require a data wipe if it hasn't been done before. What seems to "lock" the state of boot verification is booting into system; so, if you perform an update, or flash vbmeta without the disable flags, then reboot into Android, you have essentially enabled boot verification and will require a wipe to disable it again. Confusing, I know.
Click to expand...
Click to collapse
So, for all slow dumb ****s like me:
No permanent root possible on my 4a 5G when updating from A11 to A12 without a wipe?
Or is this tutorial the workaround for that?
Or is this tutorial the workaround for flashing patched boot for the monthly security updates for A12 so I don't have to wipe each month?
Or, I'm just a slow dumb ****?
¯\_(ツ)_/¯
j-a-d-z said:
So, for all slow dumb ****s like me:
No permanent root possible on my 4a 5G when updating from A11 to A12 without a wipe?
Or is this tutorial the workaround for that?
Click to expand...
Click to collapse
As it seems, yes. But I have a theory if you want to be a test subject....
j-a-d-z said:
Or is this tutorial the workaround for flashing patched boot for the monthly security updates for A12 so I don't have to wipe each month?
Or, I'm just a slow dumb ****?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
This is meant for updating but still applies the first time you root on A12.
V0latyle said:
As it seems, yes. But I have a theory if you want to be a test subject....
This is meant for updating but still applies the first time you root on A12.
Click to expand...
Click to collapse
What does your "yes" stands for? Yes, no permanent root without wipe? Or yes, that may be the workaround?
If I wanna be your test subject, what could go wrong in the worst case scenario? (or the "Wurst-Käse-Szenario", as we like to say here in Germany )
Would I still be able to fastboot boot the magisked boot image to gain temp root and backup my in-app data?
j-a-d-z said:
What does your "yes" stands for? Yes, no permanent root without wipe? Or yes, that may be the workaround?
Click to expand...
Click to collapse
I mean yes as in "yes, it appears that wiping /data is required when disabling vbmeta for permanent root".
j-a-d-z said:
If I wanna be your test subject, what could go wrong in the worst case scenario? (or the "Wurst-Käse-Szenario", as we like to say here in Germany )
Click to expand...
Click to collapse
Das ist mir Wurst.
The sausage cheese scenario is that you lose your data and have to wipe anyway. What I have in mind is this: Reflash vbmeta with the disable flags while on Android 11, die Daumen drucken, see if it requires you to wipe /data. If not, proceed to dirty flash factory image with disable flags and see if the upgrade is successful.
j-a-d-z said:
Would I still be able to fastboot boot the magisked boot image to gain temp root and backup my in-app data?
Click to expand...
Click to collapse
Temp root does work on Android 12. And if my idea sorta works but you still get Rescue Party after upgrading to Android 12, then you should just be able to reflash /vbmeta and /boot with the stock images and use temp root.
I would advise, however, that if you're interested in trying my idea, make sure to back up your data first.
V0latyle said:
NO U
Click to expand...
Click to collapse
Thanks for all your search and works The month update after first wipe work fine .
V0latyle said:
The sausage cheese scenario is that you lose your data and have to wipe anyway. What I have in mind is this: Reflash vbmeta with the disable flags while on Android 11, die Daumen drucken, see if it requires you to wipe /data. If not, proceed to dirty flash factory image with disable flags and see if the upgrade is successful.
Click to expand...
Click to collapse
Does this vbmeta reflash warn me that a wipe is required before it does anything?
So can I update A11 to A12 and retain root as long as I don't boot into the system before flashing vbmeta.img and boot.img?
j-a-d-z said:
Does this vbmeta reflash warn me that a wipe is required before it does anything?
Click to expand...
Click to collapse
Reflashing vbmeta doesn't wipe your data. If you disable verity and verification, when they were previously enabled, the system will not boot, and you will instead land in Rescue Party - a screen telling you that your data may be corrupted.
So, when we say that a data wipe is required, it means you must do it yourself.
dneill2006 said:
So can I update A11 to A12 and retain root as long as I don't boot into the system before flashing vbmeta.img and boot.img?
Click to expand...
Click to collapse
As far as we know, no. The problem is, as I stated above, the first time verity and verification are disabled on Android 12 requires a clean system. We have not found a way to be able to keep data and re-root following an upgrade. You can keep your data and either go unrooted or use temporary root, or you can wipe data for permanent root.
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.
Q: "If verity/verification are disabled, do I need to enable them now?"
A: No. The only thing you have to do is update to Magisk 23016.
Q: "Will enabling verity/verification wipe my data?"
A: No.
I will be updating the OP to reflect this.
V0latyle said:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.
Click to expand...
Click to collapse
So I did upgrading from latest 11 to latest 12 some minutes ago. Booted, patched boot.img with magisk 23016 and flashed the patched image to get back root. Worked like a charm just like any update before. So no more wipe needed.
So, it's time for the good old pal Stinky Wizzleteats and his song about being happy. That's right, it's the happy, happy, joy, joy song:
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
┌(・。・)┘♪
j-a-d-z said:
┌(・。・)┘♪
Click to expand...
Click to collapse
(ノಠ益ಠ)ノ彡/(.□ . \)
V0latyle said:
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has.
If you have already disabled verity/verification, you do not need to re-enable them; they are enabled by default when the /vbmeta partition is written, unless the "--disable-" options are used. The only thing you have to worry about next update is literally just updating your device.
DO NOT substitute Magisk Stable, as it does not yet include the necessary fixes for this device!
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
"Installed" shows the version of patch in the boot image. If this says N/A, the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
Prerequisites:
Unlocked bootloader
Latest SDK Platform Tools
Spoiler: Deprecated - this is now irrelevant
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Verified Boot.
Verified Boot on Android 12 devices, at least Pixels with the SD765G and Tensor, is tied to device encryption. Therefore, disabling Verified Boot requires a wipe, if it was not previously disabled.
To make this clear:
Verified Boot is disabled by flashing /vbmeta with disable flags:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Verified Boot is enabled by flashing /vbmeta without flags:
Code:
fastboot flash vbmeta vbmeta.img
Booting the device essentially "locks" the vbmeta state.
I know this is confusing, Bear with me:
If you previously disabled vbmeta, you MUST ensure it is disabled again when you update, BEFORE you boot. If you do not, you will have to wipe to regain root.
Unfortunately, the update process enables Verified Boot by default, because it writes /vbmeta without flags.
This means that the automatic OTA, or any other update process without intervention, WILL enable Verified Boot, which will require a wipe to disable!
****
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Canary
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to complete. Your device will reboot without root as the OTA overwrites the patched boot image.
Reboot your device to bootloader.
Boot the master root image (See note 1)
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to bootloader".
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Check the "Skip reboot" box.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet
This is my configuration:
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Services
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
MagiskHide Props Config 6.1.2
Universal SafetyNet Fix 2.2.0
Note 1: If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
Note 2: If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Click to expand...
Click to collapse
Already rooted, do I need to uninstall magisk and delete all modules? Then OTA Android 12, and then install 230016.
proac said:
Already rooted, do I need to uninstall magisk and delete all modules? Then OTA Android 12, and then install 230016
Click to expand...
Click to collapse
First, update Magisk to 23016. Do this from within the Magisk app.
Next, follow the instructions under "Initial Root" to patch the boot image. You can then use any method to upgrade to Android 12; after you have upgraded, flash the patched boot image. I recommend using the factory image method seeing as you will have already downloaded the factory image.