Rooting these is easier than some people make it out to be on other Pixel forums, so I figured I'd write up a simplified Root guide for Android 12 here as I don't see one for the 3a XL, but this does apply to all Pixel's that can upgrade to Android 12. Every other tutorial I see tells you go go through and flash Android 11 with Google Chrome, then unlock the bootloader and flash 12, then use the chrome browser flashing to disable verification. Disabling verification is 1 line of code and flashing vbmeta.img. No reason to do all that extra work when it can be done in a few minutes.
I'm not responsible for bricked devices or lost data, do this at your own risk. This tutorial is assuming your Bootloader is ALREADY UNLOCKED. If not, its fairly simple and there's tons of guides on it
This Tutorial was originally written for the Android 12 BETA. Google themselves stated to disable verification and verity with the BETA, but the official Android 12, this step MAY NOT BE NEEDED. Simply try it honestly. if it doesn't bootloop, you don't have to disable verity with vbmeta
What's needed:
- Magisk Manager (here: https://github.com/topjohnwu/Magisk/releases/)
- Fastboot ZIP from Google (here: https://developer.android.com/about/versions/12/download)
- ADB/Fastboot and Drivers installed (new installer: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/)
- Unlocked Bootloader
Instructions
1.) Make sure your bootloader is unlocked, and USB Debugging is enabled.
Download the Fastboot ZIP from google for your device. Open it with 7Zip (or your preferred program), then open the Zip file found in that extracted in 7Zip and pull out boot.img and vbmeta.img
2.) Install Magisk Manager on Device and put the boot.img on your internal storage
3.) Use Magisk Manager to patch the Boot.img file
4.) Drag and drop the magisk-patched.img somewhere on your computer. This is the rooted boot.img
5.) Reboot device to Bootloader and first disable boot verification with the code below
-- To get vbmeta.img, you can pull it out of that Fastboot Zip from Google for Android 12. Simply open the image-xxxxx-xxxxxxx.zip and extract it from there
Code:
fastboot --disable-verity --disable-verification flash vbmeta <drag your vbmeta.img to CMD window>
6.) Once that's done, flash your patched boot image
Code:
fastboot flash boot <drag your magisk-patched.img to CMD Window>
7.) You're rooted!
Update Oct 29, 2021 added above about official android 12 vs beta android 12 (when this was originally written)
Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)
tails618 said:
Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)
Click to expand...
Click to collapse
Since your bootloader is unlocked, it shouldn't wipe anything
tails618 said:
Assuming this works as it's supposed to, and my bootloader is already unlocked, will this wipe my data? (Pixel 4a)
Click to expand...
Click to collapse
Hey did this work for you on Pixel 4a? I just flashed beta 4 and I haven't tried rooting yet.
Makishima said:
Hey did this work for you on Pixel 4a? I just flashed beta 4 and I haven't tried rooting yet.
Click to expand...
Click to collapse
Sorry it took so long to reply - yes, it did.
KaptinBoxxi said:
Rooting these is easier than some people make it out to be on other Pixel forums, so I figured I'd write up a simplified Root guide for Android 12 here as I don't see one for the 3a XL, but this does apply to all Pixel's that can upgrade to Android 12. Every other tutorial I see tells you go go through and flash Android 11 with Google Chrome, then unlock the bootloader and flash 12, then use the chrome browser flashing to disable verification. Disabling verification is 1 line of code and flashing vbmeta.img. No reason to do all that extra work when it can be done in a few minutes.
I'm not responsible for bricked devices or lost data, do this at your own risk. This tutorial is assuming your Bootloader is ALREADY UNLOCKED. If not, its fairly simple and there's tons of guides on it
What's needed:
- Magisk Manager (here: https://github.com/topjohnwu/Magisk/releases/)
- Fastboot ZIP from Google (here: https://developer.android.com/about/versions/12/download)
- ADB/Fastboot and Drivers installed (new installer: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/)
- Unlocked Bootloader
Instructions
1.) Make sure your bootloader is unlocked, and USB Debugging is enabled.
Download the Fastboot ZIP from google for your device. Open it with 7Zip (or your preferred program), then open the Zip file found in that extracted in 7Zip and pull out boot.img and vbmeta.img
2.) Install Magisk Manager on Device and put the boot.img on your internal storage
3.) Use Magisk Manager to patch the Boot.img file
4.) Drag and drop the magisk-patched.img somewhere on your computer. This is the rooted boot.img
5.) Reboot device to Bootloader and first disable boot verification with the code below
Code:
fastboot --disable-verity --disable-verification flash vbmeta <drag your vbmeta.img to CMD window>
6.) Once that's done, flash your patched boot image
Code:
fastboot flash boot <drag your magisk-patched.img to CMD Window>
7.) You're rooted!
Click to expand...
Click to collapse
What you seemed to have missed the whole part about the vbmeta.img part? Where you you get that??
prot- said:
What you seemed to have missed the whole part about the vbmeta.img part? Where you you get that??
Click to expand...
Click to collapse
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot
KaptinBoxxi said:
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot
Click to expand...
Click to collapse
Awesome thanks!
For Android 11 I always need a custom kernel to avoid freeze cause of the systemless hosts file. Do U do the same in 12? What kernel?
prot- said:
Awesome thanks!
For Android 11 I always need a custom kernel to avoid freeze cause of the systemless hosts file. Do U do the same in 12? What kernel?
Click to expand...
Click to collapse
Honestly, when I flashed this, I didn't do anything except the vbmeta and the android 12. If its a GSI, I would think maybe a custom kernel is needed, but this isn't a GSI if you're doing it right to a pixel. My 3A XL is still running 12 just fine with root, no custom kernel
KaptinBoxxi said:
Honestly, when I flashed this, I didn't do anything except the vbmeta and the android 12. If its a GSI, I would think maybe a custom kernel is needed, but this isn't a GSI if you're doing it right to a pixel. My 3A XL is still running 12 just fine with root, no custom kernel
Click to expand...
Click to collapse
With systemless hosts enabled?
prot- said:
With systemless hosts enabled?
Click to expand...
Click to collapse
yep, enable it with every device i root
KaptinBoxxi said:
You get vbmeta from the Fastboot zip file in the image-xxxxxxxxx.zip that you extract. I'll add it to original post. I didn't realize I forgot
Click to expand...
Click to collapse
Does vbmeta.img change with each new monthly release? If so, then flashing vbmeta.img with the --disable-verity and --disable-verification flags will need to be done as part of the update process. Correct?
Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Try this: Reflash vbmeta without the flags
Code:
fastboot flash vbmeta vbmeta.img
Leave your patched boot image alone and see if you boot. If you end up in bootloader with
failed to load/verify boot images
this confirms that disabling verity/verification is necessary.
V0latyle said:
Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Try this: Reflash vbmeta without the flags
Code:
fastboot flash vbmeta vbmeta.img
Leave your patched boot image alone and see if you boot. If you end up in bootloader with
failed to load/verify boot images
this confirms that disabling verity/verification is necessary.
Click to expand...
Click to collapse
I've had hit or miss results to be 100% honest. I never do anything differently. I've rooted dozens upon dozens of Pixel's. Sometimes its needed, sometimes it isn't.
In this case its needed because of Android 12 BETA GSI was being used. Since Android 12 Official is out, it may not be needed
KaptinBoxxi said:
I've had hit or miss results to be 100% honest. I never do anything differently. I've rooted dozens upon dozens of Pixel's. Sometimes its needed, sometimes it isn't.
In this case its needed because of Android 12 BETA GSI was being used. Since Android 12 Official is out, it may not be needed
Click to expand...
Click to collapse
I believe this has more to do with Boot Image Header v4, not GSI. I could be wrong.
V0latyle said:
I believe this has more to do with Boot Image Header v4, not GSI. I could be wrong.
Click to expand...
Click to collapse
Well even google stated to disable it during the beta. They didn't provide avb_keys at first with the beta, which was strange which is why i said to do it on this tutorial
V0latyle said:
Can someone confirm whether disabling verity and verification is absolutely necessary on the Pixel 3? I believe this issue is specific to the 4a 5g, 5, 5a, and 6 series, and should not affect the 3/3XL/3a/4/4XL/4a.
Click to expand...
Click to collapse
I have the 3a and was able to root normally without disabling verity and flashing vbmeta.
mulperi said:
I have the 3a and was able to root normally without disabling verity and flashing vbmeta.
Click to expand...
Click to collapse
This issue only affects 765G and Tensor devices - the 4a 5g, 5, 5a, 6, and 6 Pro. All other devices are NOT affected.
Will this method work on a pixel 3a XL on Android 10
Related
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first.
How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
Ah thank you...
Already tried with flashing disable DM verity but it failed and make me need to flash original boot.img file.
How can I so stupid not to flash vbmeta.img?
And yes, with this method I can confirm root with Magisk run smoothly.
:good::good::good:
What is your widevine level after that?
Maciejbbb said:
What is your widevine level after that?
Click to expand...
Click to collapse
L3 of course
nullxception said:
L3 of course
Click to expand...
Click to collapse
Is it reversible or can you hide it with magisk module like on some phones?
Maciejbbb said:
Is it reversible or can you hide it with magisk module like on some phones?
Click to expand...
Click to collapse
Reversible ? I don't know, can't confirm that.
Also there's still no patched widevine module that works for realme6pro.
Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?
Muhammed159753 said:
Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?
Click to expand...
Click to collapse
No, that 65mb is size of the whole partition block, not the actual size of the whole files inside of it.
If you try to manually unpack the boot.img, and then repack it, the size will go down to around that.
@AT nullexception Thanks for your reply. So Can I flash magisk patched boot image after flashing vbmeta.img? Will my phone get bootloop?
Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?
Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.
SignatureBoy said:
Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.
Click to expand...
Click to collapse
Here my boot image files magisk_patched
SignatureBoy said:
Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?
Click to expand...
Click to collapse
/////////////////////////////
Which version of magisk.zip did you flash?
Muhammed159753 said:
/////////////////////////////
Which version of magisk.zip did you flash?
Click to expand...
Click to collapse
20.1
---------- Post added at 08:51 PM ---------- Previous post was at 08:49 PM ----------
Felix Siahaan said:
Here my boot image files magisk_patched
Click to expand...
Click to collapse
Thank you so much but i am afraid to flash it again as it was really hard to revive it back i had to send it to Service center, and pretended that the newest update has done all issues.
They were not agreeing to flash as bootloader was unlocked then after so many request they agreed and said do not update the fone to lastest update.
Boot loader is unlocked so tell me how can i do the root session STEP BY STEP please
and also if you have the MBN version of the stock rom then give me the link as MSMDOWNLOADTOOL does not work without Paid ID and Password.
nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible
kkrraazzyy said:
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible
Click to expand...
Click to collapse
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever
To deactivate verify boot every time patched vbmeta need to flash. Is it ok to flash same vbmets v2 for all future updates
Thans
nullxception said:
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever
Click to expand...
Click to collapse
Is it ok to flash same vbmets v2 for all future updates
Not working on A25
Will this work on all versions of the realme 6 pro?
I've got the rmx2063 version and I want to root it with magisk' will I be able to do it after doing this?
Many thanks
So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!
Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.
That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out
If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply
Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!
Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?
@TringQuack What's your current state with A53?
Running GSI? Stock?
ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock
@TringQuack How do I know if the build is compatible with A13?
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP
Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.
Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.
Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen
binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.
You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.
Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?
I followed this guide exactly: https://topjohnwu.github.io/Magisk/ota.html
Before starting the guide, I had a pretty new Pixel 7 Pro with the latest version of Magisk successfully installed (with bootloader UNLOCKED) and some small Magisk modules to tweak things (iOS emojis). I made sure to restore boot images and got the "restoration complete" toast message.
I saw the notification for the November update, downloaded and installed it. I did NOT reboot after that. I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
My device rebooted, and showed me the bootloader unlocked screen, then showed me the "your device is corrupt" warning and said "press power button to continue". I pressed the power button and my device is now stuck on the Google logo.
Has this happened to anyone else? And is there any way to fix this (preferably without data loss)?
Pritster5 said:
I followed this guide exactly: https://topjohnwu.github.io/Magisk/ota.html
Before starting the guide, I had a pretty new Pixel 7 Pro with the latest version of Magisk successfully installed (with bootloader UNLOCKED) and some small Magisk modules to tweak things (iOS emojis). I made sure to restore boot images and got the "restoration complete" toast message.
I saw the notification for the November update, downloaded and installed it. I did NOT reboot after that. I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
My device rebooted, and showed me the bootloader unlocked screen, then showed me the "your device is corrupt" warning and said "press power button to continue". I pressed the power button and my device is now stuck on the Google logo.
Has this happened to anyone else? And is there any way to fix this (preferably without data loss)?
Click to expand...
Click to collapse
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?
Freak07 said:
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
Click to expand...
Click to collapse
Glad you're on our forum Freak!
Pritster5 said:
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?
Click to expand...
Click to collapse
Remove "-w" from the flashall.bat, I believe that ensures you keep data.
I'm also a bit confused by this step: "flash it via fastboot on your device with nov firmware." Are you saying that I should flash october init_boot.img onto my phone, which already has the Nov firmware installed? Or do I have to merge the Oct init_boot.img into the Nov firmware (full factory image TD1A.221105.001)
Pritster5 said:
I'm also a bit confused by this step: "flash it via fastboot on your device with nov firmware." Are you saying that I should flash october init_boot.img onto my phone, which already has the Nov firmware installed? Or do I have to merge the Oct init_boot.img into the Nov firmware (full factory image TD1A.221105.001)
Click to expand...
Click to collapse
yes, you flash the old outdated init_boot via fastboot on november firmware.
afterwards you flash back the correct one for november. that will hopefully clear the avb bug you´re experiencing.
You flash only this img, not anything else. do precisely the steps I described. you don´t have to flash the full firmware, as you already updated to november if I read your initial post correctly and OTA to november was successful.
Pritster5 said:
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?
Click to expand...
Click to collapse
no it has not been fixed.
no, with the steps detailed there´s no data loss.
I wouldn´t recommend updating your phone with the magisk flash to inactive slot method. That´s not working for most people on p6 and p7 devices.
Pain-N-Panic said:
Remove "-w" from the flashall.bat, I believe that ensures you keep data.
Click to expand...
Click to collapse
the method I described doesn´t involve using that script. no data will be lost.
I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
Click to expand...
Click to collapse
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61
Freak07 said:
yes, you flash the old outdated init_boot via fastboot on november firmware.
afterwards you flash back the correct one for november. that will hopefully clear the avb bug you´re experiencing.
You flash only this img, not anything else. do precisely the steps I described. you don´t have to flash the full firmware, as you already updated to november if I read your initial post correctly and OTA to november was successful.
no it has not been fixed.
no, with the steps detailed there´s no data loss.
I wouldn´t recommend updating your phone with the magisk flash to inactive slot method. That´s not working for most people on p6 and p7 devices.
the method I described doesn´t involve using that script. no data will be lost.
Click to expand...
Click to collapse
devsk said:
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61
Click to expand...
Click to collapse
If what @devsk states is true, you also need to flash back stock boot.img from november firmware via fastboot @Pritster5.
fastboot flash boot boot.img
Since magisk can patch init_boot.img´s, I assumed it would account for pixel 7 pro, having ramdisk inside init_boot instead of boot.img. It´s a bad design choice by magisk app to show this option to users on Pixel 7 pro in that case. :/ but even on pixel 6, the forums are full of people running into issues with that method.
devsk said:
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61
Click to expand...
Click to collapse
Where can I see what devices are supported for that method? I assumed that the guide worked for anyone with A/B partitioning. It would be helpful if there was a notice of this somewhere on the guide or any other obvious place.
The easiest way to recover is to follow that guide and flash the whole ROM (it will fix both the boot and init_boot partitions). *Make sure* to remove -w from the flash-all.bat or flash-all.sh, whichever one you are using. This part is important. "-w" command line argument wipes your data and you don't want that.
I just updated my p7p using this method this afternoon and it worked fine.
Pritster5 said:
Where can I see what devices are supported for that method? I assumed that the guide worked for anyone with A/B partitioning. It would be helpful if there was a notice of this somewhere on the guide or any other obvious place.
Click to expand...
Click to collapse
That link is specifically for p7p
devsk said:
That link is specifically for p7p
Click to expand...
Click to collapse
Oh I meant where can I see what devices support the Magisk "Install to inactive slot" guide.
You said "The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition."
How are you aware of this? Did you find this out by reading the code itself or was there a notice of this somewhere?
Pritster5 said:
Oh I meant where can I see what devices support the Magisk "Install to inactive slot" guide.
You said "The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition."
How are you aware of this? Did you find this out by reading the code itself or was there a notice of this somewhere?
Click to expand...
Click to collapse
Actually, this got me thinking and I looked at the code. Looks like the magisk code (the bash function find_boot_image) seems to be doing the right thing by treating init_boot ahead of boot partition.
Do you have the logs from that run of "Install to inactive slot"?
devsk said:
Actually, this got me thinking and I looked at the code. Looks like the magisk code (the bash function find_boot_image) seems to be doing the right thing by treating init_boot ahead of boot partition.
Do you have the logs from that run of "Install to inactive slot"?
Click to expand...
Click to collapse
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
EDIT: Should I just use the Android flash tool instead if I don't have access to ADB? Or should I instead just follow Freak07's steps since his steps don't require adb access?
Pritster5 said:
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
Click to expand...
Click to collapse
Just restore your device by flashing the whole ROM. This will get rid of magisk and you should have no problem booting back into the system. You will have lost the root at that point. Once inside, transfer the init_boot.img into /sdcard and run magisk and ask it to patch that. Bring the patched file to your PC, and flash it to init_boot partition like the guide says. At that point, you should be able to boot back into the system and root should be good.
I did not disable Magisk modules and it worked fine. I have magiskhide props, shmiko, systemless hosts, zygisk - lsposed, universal safety net fix.
If you have trouble with Magisk modules, you can recover by booting into Safe Mode (restart and press down volume and keep it pressed). Magisk detects the Safe Mode and disables the modules. Done that many times.
Pritster5 said:
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
EDIT: Should I just use the Android flash tool instead if I don't have access to ADB? Or should I instead just follow Freak07's steps since his steps don't require adb access?
Click to expand...
Click to collapse
in the end it doesn´t matter how you do it.
Flashing the complete firmware with -w removed or using the web flasher might be easier as it´s kind of a one click solution.
However simply flashing entire november firmware, might not get you out of the avb corruption loop. It might but, but it might not depending on what went wrong. If it´s the bug that I think it is, avb gets cleared when flashing an older outdated init_boot.img.
You can try to just flash the entire nov firmware with any of the methods suggested. If it doesn´t clear the avb corruption bug, flash back older init_boot from oct firmware, followed by current init boot as I originally suggested.
Freak07 said:
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
Click to expand...
Click to collapse
Ok so I did this part:
"I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still."
And it works, however when I go to "About Phone" the build number is still the October version. Is this expected, given that I flashed the october init_boot.img onto a phone with November firmware? Or did my phone perhaps reboot into the older partition which the phone ran before switching to the inactive slot?
EDIT: Even after flashing the november init_boot.img after temporarily reverting to the october init_boot.img, it's still showing that I have build TD1A.220804.031 installed.
"followed by current init boot as I originally suggested."
Should I reboot back into fastboot mode again to do this?
Thank you guys so much for the help so far btw, I'm already back up and running and just need to finish the steps you mentioned.
@devsk Here are the logs you wanted: