The first time you upgrade to Android 12 you must wipe your phone in addition to disabling verity and permission to root it.
Read the Notes in #4, then do #4 'Wipe data'.
Last edited:
[Guide] [November 6, 2023] Root Pixel 4a (5G) Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
- Thread starter Homeboy76
- Start date
Read the Notes in #4, then do #4 'Wipe data'.
The first time I tried to upgrade I did not wipe the data nor did I disable Magisk. I downloaded the latest build, extrated the boot.img file, patched it with Magisk and re-insertedit the now patched boot.img inside the zip and did a flash-all.bat without wipe (removed -w inside the bat file). That's what started this big Ol' mess. This method worked before but not today, thanks google, LOL!
Regardless I am currently on the latest build. I just did a fresh install via adb flash-all.bat WITH wipe.
Again I never disabled Magisk but that was like 2 or 3 flashes ago.
Should I be good now or do I need to do something more.
Thanks
BB
EDIT: I noticerd in part 4 it says:
change fastboot -w update image-bramble-aa9a.999999.999.zip
to fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
I did NOT change this command
Can I just run fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Or should I do another flash. If I do another flash should I do wipe again or not?
Thanks
Last edited:
You need to change this line in the flash-all.bat file:
fastboot -w update image-bramble-sp1a.999999.999.zipto this:
fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zipWiping the phone is necessary if you want to root your phone.
You do not need to flash the vbmeta.img:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.imgJust flashing the vbmeta.img will not allow you to root your phone.
Last edited:
Thank you.
One more question. After doing the above (fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip)and then install Magisk, when I need to flash the patched boot.img do I do it as normal or do I first need to flash the vbmeta.img:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Thanks Again.
BB
Normal:
fastboot flash boot magisk_patched_...imgfastboot rebootYou do not need to flash the vbmeta.img.
Last edited:
THANK YOU!!!
It has been quite the journey but my phone is working with root. Now to tackle safety net.
Magisk 23014, enable Zygisk and enable DenyList on all components of Google Play Services and Google Play Store. Install Universal SafetyNet Fix 2.2.0.
Done.
One week on 12 with Magisk root and all was fine until yesterday. Phone boots for about 1 1/2 minuets, and freezes. The touchscreen does not respond to input and buttons do not work as well. The phone restart in about a minuet or so. but it's goes straight to the Google bypassing a the bootloader in unlocked,press to pause screen. Restarting the phone in safe mode the phone works fine. I assume it's a rouge app but I don;t know which one. I downloaded and ran a Malwarebytes scan that took forever because of the rebooting and it did find and remove a "threat" however that did not fix things.
I guess I will need to reset the phone.
Considering I have Magisk installed, I need to remove magisk first. Can I then use ADB to push the image or do I need to do a full wipe first before ADB.
Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip
Please advise. Thanks in advance.
BB
"Do I need to do this again? fastboot -w --disable-verity --disable-verification update image-bramble-sp1a.999999.999.zip"
Yes.
Not sure if it is Android 12 or my particular phone but I've never been so frustrated. Uninstalled Magiisk, rebooted device, did a factory data reset from within the OS, rebooted, set-up fresh device, enabled usb debugging, flashed latest build with the above commands added into the flash-all,bat file. Rather then profit I would up with a brick. It would boot strait into the bootloade. Going to recovery and trying to do a factory reset resulted in failure. The only solution was to I reboot my PC, change USB ports, and adb sideload the factory OTA. reboot, set-up,enable usb debugging and flash again with falsh-all and the above commands and finally rooted with Magisk. The phome is working again but I am seriously frustrated. If the phone crashes again in a week, I'm going back to 11.
What version of Magisk and Safety net Fix are you using?
I'm assuming you have SDK Platform-tools r31.0.3 installed on your computer?
Currently Canary 23015 and Safety Net Fix 2.2.0
Something weird though is that the modules installed are showing but the modules you can choose and search for are not showing in Magisk. I only run 3 modules that I have backups for so no issue for me at least not yet.
EDIT: Oh crap I WAS on Platform Tools 30.0.5, Oops I wonder if that was the issue for all the problems.
PLEASE tell me I don;t have to do this again, LOL!
I have a spare P3aXL that I am going to do put 12 on. See if it will go smoother with the new Platform Tools
EDIT: I think I have found the issue. Again I wiped the phone and set it up with a fresh install of 12. After some issues I got it to boot on Friday 11-26. I rooted and all was well until last night 11-27 when the same thing started to happen, constant reboots after a the phone was on for a few minuets. Before wiping the phone again and reverting to 11 I thought about everything I did with the phone since Friday 9not much). After some thinking I remembered that although installed via backup/restore I never used the Greenify app untill late Saturday when I opened the app and gave it root privileges. Could this be my problem? I uninstalled the Greenify app and low and behold the phone is back to normal, at least for now. I don't know what it is doing but I assume Greenify is hibernating a vital system app that is causing the phone to freeze and reboot. For now the phone is working good.
Last edited:
An old SDK Platform-tools definitely was part of the problem.
If you want to install modules, install this:
Fox Magisk Module Manager: 0.1.2 (FoxMmm-0.1.2.apk. 2.59 MB)
- A new module manager for Magisk Alpha/Canary
Last edited:
Hello,
The question I am reading the instructions that say if updating from 11 to 12 I must wipe either wipe clean or wipe keep data. The problem is I updated to 12 (when it was in beta mode) (Xfinity model) VZW. So since then, it removed Magisk. So this means I have to start from scratch?
My bootloader is unlocked.
The question I am reading the instructions that say if updating from 11 to 12 I must wipe either wipe clean or wipe keep data. The problem is I updated to 12 (when it was in beta mode) (Xfinity model) VZW. So since then, it removed Magisk. So this means I have to start from scratch?
My bootloader is unlocked.
If your bootloader is unlocked and you want to root your Pixel 4a 5(G), go to the OP and do you 4., • Flash Factory Image Wipe Data
Need a little help from someone more knowledgeable.
I did a full wipe last month from Android 11 to Android 12. I rooted without issue, and have been running fine since. Today I tried to update without a data wipe according to the instructions in post 1. I got everything updated fine, but whenever I try to reroot by flashing the patched magisk boot image, the phone just keeps rebooting into fastboot. If I flash the stock boot image, everything boots up fine, but no matter what I try, I can't get the patched boot image to work.
I'm running the latest canary build of magisk, and have the latest platform tools.
Any help is much appreciated.
I did a full wipe last month from Android 11 to Android 12. I rooted without issue, and have been running fine since. Today I tried to update without a data wipe according to the instructions in post 1. I got everything updated fine, but whenever I try to reroot by flashing the patched magisk boot image, the phone just keeps rebooting into fastboot. If I flash the stock boot image, everything boots up fine, but no matter what I try, I can't get the patched boot image to work.
I'm running the latest canary build of magisk, and have the latest platform tools.
Any help is much appreciated.
After you flash the stock boot.img boot safe mode. Once Safe boot mode is fully booted. Reboot and try flashing the patched Magisk boot img: fastboot flash boot magisk_patched...img
Last edited:
Thank you for the reply, but unfortunately no luck.
In fastboot I flashed the stock boot.img. I then clicked start using the power button. I held volume down to boot into safe mode, waited a few minutes, and then turned the phone off. I waited a few seconds, and then held power+volume down until the phone booted into fastboot. I then flashed the patched boot image using the fastboot flash boot command, and clicked start. The screen went black momentarily, and then came back into fastboot mode with the reasons being "failed to load/verify boot images". From there, the only way I can find to boot successfully is to flash the stock boot image. Once I do that and click start, things boot normally.
You did 4., • Flash Factory Image Keep Data and got this error: "failed to load/verify boot images"
Try
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img[ICODE][/B].
Then flash the magisk_patched...img.
Last edited:
I only have the one magisk app, and can certainly delete that. Is there anything I can do via ADB to make sure I get everything? I know there used to be a flashable magisk uninstaller that saved me once back in the day.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
24[Guide] [November 6, 2023] Root Pixel 4a (5G) Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + MoreIntroduction
Android Security Bulletin—November 2023
Pixel Update Bulletin—November 2023
This Guide is for Pixel 4a 5(G) owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
- Disclaimer
- Prerequisites
- NEW
- Update(s)
- My Other Guides
- Credits/Thanks/Recognitions
(The Instructions listed below are not steps, they are individual sets of instructions for the Pixel 4a 5(G).)
- (NEW) PREVENT/FIX BOOT LOOPS
- Unlock Bootloader/Return Phone to Stock/Lock Bootloader
- Manually Install/Update Factory Image keep data or wipe data
- Manually Install/update the OTA image keep data and root/re-root your phone
- Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
- Extract files from the Factory Image
- Root/Reroot with Magisk and Pass SafetyNet.
- Set Magisk App Update Channel/Update Magisk
- Install/Update Magisk Modules
- Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
- Test fastboot
- ADB Sideload
- Custom ROMs
- Themes, Apps, and Mods
- T.W.R.P. Backup/Restore
3
Do not repeat do not follow these instructions. The information is only partially correct.
I just checked the Factory image and the OTA image pages the only change was the All carriers EXCEPT Verizon has been removed from the images description.
The OP has been updated to reflect the change.
These images work on Verizon Pixel 4a 5g phones.3
This is typically due to multiple Magisk managers being installed, if at any point, Magisk Manager was hidden, and then another Magisk manager was installed, you'd face issues as this.
@dadnammit you should first do is, uninstall all Magisk managers, hopefully you can find the hidden one, or at least you know the package name, if you did not rename the application when you hid, then it should be named settings.
If you have already applied patched boot, then reboot and just install Magisk Manager. and it should detect root.
You can confirm that you're rooted by doing
if you get su, you're rooted.Code:adb shell su
If you are on stock, then just install Magisk Manager and flash the patched boot.
Whatever you do make sure you only have a single instance of Magisk manager.3
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot3
Just checked
It is pointing to the Pixel 4a 5(G) bramble factory image.
Download the latest Factory Image: Pixel 5 - bramble to your Computer. --> pixel 5 (only text)? Fixed! - Disclaimer
PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
