yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5a] CarinaPDX:
I updated a couple of weeks ago with no problems. I have given up on using the OTA update or trying to preserve root. I downloaded the factory image to my computer, extracted boot.img and transferred it to my 5a, then patched it with Magisk and transferred it back to my computer and then uninstall/restore images in Magisk. Then I removed the "-w" from the script and ran it to update the OS. Reboot. Use fastboot to boot with the patched boot image, run Magisk and patch directly the boot.img. Reboot and your finished.

I think some of the problems experienced relate to the fact that this update includes updates to the bootloader and the radio (modem), which needs to be done before the OS update. The included script does that; updating the OS before the other updates is likely to cause problems. And failure to update the radio can easily cause connection problems as the OS expects to be working with the new firmware, not the old.

There are two scripts included, one a shell script. Just be certain that you remove the "-w" in the script you are using before proceeding: -w wipes your disk and you don't want to lose your Home data I presume.
[Google Pixel 5a] CarinaPDX:
I just updated with the October security patch and everything seemed to go smoothly. I removed Magisk, took the OTA, then after reboot I shut down and used fastboot boot with a patched image to start the phone, and finished with a Magisk direct install. Just one problem: no internet access. I can connect to 5G or WiFi but have no internet availability. I will flash the full factory image and hope that works. Very strange...
[Google Pixel 5a] V0latyle:
This has been covered in the OP. I don't use the script but it is important to ensure the bootloader and radio are updated if necessary. The system image checks the bootloader and radio versions.

I actually recommend against using the script, because of the importance of learning how to use ADB and fastboot. Complacency is a good way to make a mistake.

That is odd. Do you happen to have custom DNA servers set, or something else associated with your connection such as a VPN?
[Google Pixel 5a] CarinaPDX:
The first two quotes were for the 12>13 upgrade, which I see that I failed to mention. Version upgrades are typically more complex and I think it best to just install a factory image, however one chooses to do it.

I thought a simple security update would not cause problems but that is not the case it seems. I have not messed with the DNS settings AFAIK (I can't even find them); on previous phones I have used an app for using custom DNS servers. I change the DNS servers at my gateway so that DHCP provides them to all connected devices. I also have used VPNs in the past but not on this phone - I am using wireguard on my computer and have yet to learn how to set up WG on Android.
[Google Pixel 5a] V0latyle:
The "safest" way is always via OTA.

Speaking of OTAs, try sideloading the update, see if that fixes your issue. Not sure if it will TBH...failing that, the only thing I can really suggest is a data wipe
[Google Pixel 5a] CarinaPDX:
I downloaded the factory image and used "fastboot update <system image>" (which restored internet access). Then patched the boot.img with Magisk (25205) and lost internet access again. I tried a couple of times and it is repeatable. I can't imagine what else could be the problem other than Magisk. Am I the only one that has internet access problems with the October security plot and Magisk? I guess I will have to live without root for awhile...
[Google Pixel 5a] V0latyle:
Magisk Canary is basically the test channel. Try Stable 25.2 and see if it works.

Also, double check your Magisk modules. What modules are you using? Are you using private DNS or anything?
[Google Pixel 5a] CarinaPDX:
Last night I realized that it might be the AdAway module (I normally don't even think about it being there - it just works). It directly affects the DNS process. So I will be removing AdAway and re-installing Magisk and see if that works. It would be disappointing as I really appreciate not being inundated with ads, but first I have to narrow it down before it can be fixed.
[Google Pixel 5a] V0latyle:
Do you mean systemless hosts?

You can toggle AdAway on or off, and you may want to consider disabling host lists as well as using custom DNS just in case the DNS servers you're trying to use are blacklisted. I personally use CloudFlare: 1.1.1.1 and 1.0.0.1. Not quite as fast or reliable as Google (8.8.8.8, 8.8.4.4) but DNS requests are not logged or stored.

I am using 4 lists:

AdAway official hosts

Energized Spark

Pete Lowe blocklist

Steven Black unified hosts

I don't have any problems with Internet connectivity. Try using a custom DNS server and just the AdAway official host list and see if you still have the same problem. Also, test to see if it's specific sites you have a problem with. Try a VPN as well.
[Google Pixel 5a] MattsyGravy:
Are the steps the same for Android 13? Had to RMA my phone and Google sent me the phone with 13 installed. I see guides for the 6 with 13, just want to make sure there aren't any issues when I get home to get everything set back up again.
[Google Pixel 5a] V0latyle:
Everything is exactly the same. Don't try to use an older version of Magisk. No special instructions for barbet.
[Google Pixel 5a] xmsjshou:
Thanks for the guide! I followed all the steps, and it worked on well my device for Android 13.

Yet I got an issue - whenever I reboot my device I lose my Magisk root.

In this case, I have to go back into the bootloader and boot with the patched image again...

Is there any solution to the "root lost issue after reboot"?

(for the same device I remember when it's Android 12, no issue after reboots)
[Google Pixel 5a] V0latyle:
Sounds to me like you've just been live booting the patched image, instead of flashing it. This is fine, but if you want root to persist after a reboot, you need to launch Magisk, tap Install, then Direct Install.

This was outlined in the OP.
[Google Pixel 5a] LagMaster420:
About to try this in 2023. My Pixel 5a does have OEM Unlocking greyed out. Going OTA route first.
[Google Pixel 5a] V0latyle:
If you are unable to enable OEM Unlocking, OTA (automatic or sideload) is your only option for update.
[Google Pixel 5a] LagMaster420:
I tried to adb sideload an OTA for Android 12, but my phone complained and aborted the installation with the following message:

ERROR: recovery: Current SPL: 2022-10-5 Target SPL: 2022-02-05 This is considered a downgrade

ERROR: recovery: Denying OTA because it's SPL downgrade

I'm working around the downgrade block by sideloading a newer OTA. Hopefully, my Pixel doesn't block this one.

I successfully sideloaded an OTA, but unfortunately my OEM Unlocking button is still greyed out

Connecting to the internet allowed me to enable OEM Unlocking for some reason. Advanced Google spyware of some sort?
[Google Pixel 5a] V0latyle:
Yeah, you can't sideload an older version

Lol no. This is things working exactly as intended. Since Google uses the exact same firmware for both unlocked and carrier locked variants, the ability to enable OEM Unlocking is maintained via an IMEI whitelist in the cloud.
[Google Pixel 5a] CongestedHangman:
i was on december security patch when i rooted my pixel 5a with magisk (Android 13). still now i have not received the january ota update. manually checked lot of times...(i know i can sideload ota any time)

should i wait for february?
[Google Pixel 5a] V0latyle:
It's pretty normal for rooted devices to not be able to update via OTA. Either sideload the update or flash the factory image without wiping.
[Google Pixel 5a] CarinaPDX:
I didn't realize that. I see that I am still on the November security update, and even with Magisk uninstall (restore images) the system reports that no updates are available. I had been uninstalling Magisk, taking the OTA, booting rooted image from computer, then re-installed Magisk. It is not a problem to install with fastboot but I am surprised that with Magisk removed that the OTA update still does not show.
[Google Pixel 5a] LagMaster420:
That's still a very invasive feature. An IMEI whitelist for unlocking bootloader means that I have to ask Google's """cloud""" for permission before I can unlock bootloader. That's not very nice. And it clearly counts as spyware.
[Google Pixel 5a] V0latyle:
No, it doesn't. As I explained, the firmware is the same, and since carrier locking is managed by IMEI, it's checked against the cloud. If you have an issue with carrier prevention of bootloader unlocking, don't buy a carrier variant. It's that simple. This same scheme is used by many OEMs including Samsung - the OEM Unlocking toggle is generally not visible at all until the device connects to the Internet, then after the bootloader is unlocked, Knox Guard/Vaultkeeper still prevents modified binaries from loading until it's able to check again.

None of this described mechanism uses any other information from your device but your IMEI. If you're that concerned about privacy, you probably shouldn't be using a smartphone - or at the very least, you should be using something like CalyxOS.
[Google Pixel 5a] thestallion:
Happy to report that everything is working fine with a Pixel first updated with OTA to June 2023, then unlocked the bootloader and rooted via boot.img patch.

Thank you for the guide.
[Google Pixel 5a] CarinaPDX:
It has been a few months since the last update was pushed out to my phone and I just got the July update. I did the Magisk "restore images", then took the OTA update. As has been the case lately I had to re-root by first booting using fastboot and a patched boot.img. It seems that there has been a change in the boot.img so I had to download the factory image, extract the current boot.img, patch using Magisk, and then boot from it before having Magisk do a direct root. The previously patched boot.img did not work for temporary boot as the bootloader does not allow booting from earlier releases. No problem; just a heads up.
[Google Pixel 5a] V0latyle:
I use Pixel Flasher so I always patch the new boot image anyway
[Google Pixel 5a] CarinaPDX:
Now that I am comfortable with the update process, a new way... :cool: . It looks great, once understood and set up it should be easy. Next time... Thanks for the recommendation.
[Google Pixel 5a] pawlik79:
How do we root android 14?
[Google Pixel 5a] V0latyle:
The same way as before. Just make sure you use Magisk 26.1.
[Google Pixel 5a] CarinaPDX:
No problem. I removed Magisk ("restore images"), took the OTA update to 14, then rooted. I have been rooting by downloading the factory image, extracting boot.img, having Magisk patch the file and then transferred it back to my computer. I then use flashboot to boot the patched image, and while running using this boot on the computer I used Magisk to directly patch in the phone. Reboot and enjoy.
[Google Pixel 5a] SideSkroll:
Has anybody in this thread faced the "black screen" pseudo brick of their phones? Is their ANY WAY to recover from it? I was just browsing in chrome and all of the sudden the screen went black and it will not turn back on. I've tried rebooting (30 seconds power button), all buttons at once. Letting the battery drain etc and NOTHING brings it back.

The phone still accepts commands through adb though. I can reboot it, enter fastboot etc. I have even reflashed the phone (non destructive) by using google's website and it completed succesfully).And i can hear and feel the haptic feedback when I connect it or charge it etc. It appears to be only the screen....

I know this isn't the right thread but I'm desperate by now. And I don't even live in the US so their "extended warranty" os meaningless to me.

Any help would be INSANELY appreciated.

Thanks.
[Google Pixel 5a] CarinaPDX:
This doesn't sound like a brick at all: everything is working as intended, except the screen. Sometimes a screen failure really is a screen failure... It could be the OLED screen itself, or in the screen driver circuit. Either way I doubt that this is repairable without access to parts. Time for a new phone?
[Google Pixel 5a] SideSkroll:
But this is an issue that a lot. A LOT of 5a owners are facing more and more every day. So it's probably not just "bad luck" on my part.

I thought it probably was only the screen but rven though the phone appears to "work" find my android can't find it ironically and it doesn't ring if I try to call or message....

So I'm not sure at this point. The phone is 16 months old. There is NO EXCUSE for this crap. At this point I'm mostly interested in recovering my data and throwing this POS to the curb. I will NEVER buy any Google product again. This is the THIRD time it happens to me. First it was with one of their "on live" (or however theyre called) routers. One night after an update it bit the dust. Gone. 1 year it lasted. Then it was one of those "nests". Only god knows what happnned to it it just died. And now this phone. Google should dissapear from the manufacturing pool. It it OBVIOUSLY not an isolated incident.

Anyway, any way to recover my data blindly?

Thanks for replying though.
[Google Pixel 5a] CarinaPDX:
This is the wrong thread for this discussion. If you know that it is a common problem then either find a thread on it or open one yourself. And then state what you know precisely: you initially said " It appears to be only the screen...." and then later added other problems - not helpful.

Normally you can access the phone's file system with your computer's file manager, but only after putting the phone in that mode (in Settings/Connected Devices). Whether you put the phone in that mode remotely with ADB or Fastboot I do not know. Again, a thread on this problem might get the attention of the devs.

Good luck.
[Google Pixel 5a] ominiscience:
Can anyone help me with pixel 5a persist.img file?
[Google Pixel 5a] V0latyle:
Download the factory firmware and extract it.
[Google Pixel 5a] ominiscience:
I have the factory image. How do i go about extracting?
[Google Pixel 5a] V0latyle:
Actually, let's start over. I just looked at the firmware for my wife's 5a. There is no persist.img. Why do you think you need it? What were you messing with in the first place?
[Google Pixel 5a] ominiscience:
From factory image zip, I have:

Bootloader barbet

Flash-all.bat

Flash-all.sh

Flash-base.sh

Radio barbet

Imagebarbet.zip (unzip gives: android-info.txt

Boot.img

Dtbo.img

Product.img

Super_empty.img

System.img

System_ext.img

System_other.img

Vbmeta.img

Vvmeta_system.img

Vendor.img

Vendor_boot.img)

Which is the persist file?
[Google Pixel 5a] V0latyle:
I just said there isn't one.

Persist is a partition that should never be modified or removed under any circumstances. It contains things like IMEI, WiFi MAC address, etc.

Why do you think you need it? Did you mess with something you aren't supposed to?
[Google Pixel 5a] ominiscience:
I was having problems with my Wi-Fi. So i got some persist file online and tried it with it.

Sensors are completely messed
[Google Pixel 5a] ominiscience:
Apparently. Then I found out it could be backed up.

Some tutorial on YouTube.

"Howto backup & restore efs, modem and persists partitions on any Google pixel"
[Google Pixel 5a] ominiscience:
Could you help me with a backup?
[Google Pixel 5a] V0latyle:
No.
[Google Pixel 5a] ominiscience:
Alright, thank you.
[Google Pixel 5a] V0latyle:
Just fair warning, what you did is not advisable.

You flashed a critical partition of your phone with a random file you got online. It is too late to create a backup, and the only way to Fix your phone is to take it to a professional, who will replace the main board. The information in your persist partition is unique to your phone, and if you did not create a backup before you flashed it, that information is toast.

Sometimes we have to learn the hard way...
[Google Pixel 5a] ominiscience:
Thank you for the information. But it is not unique.

I'll get a backup and fix it.

Thank you.
[Google Pixel 5a] ominiscience:
People make the back up all the time before custom rom flashing and share it to others who need it. Kind of like the one I got online.

Only modem is unique. And people even share that too.
[Google Pixel 5a] V0latyle:
From one of our very knowledgeable members:
[Google Pixel 5a] ominiscience:
"Most"

"Likely"

"Exactly"

I just need to fix my phone.

That's all.
[Google Pixel 5a] V0latyle:
We can't help you with that. Contact Google, see if you can have it repaired.
[Google Pixel 5a] ominiscience:
If you can back up your persist.img, I'll be grateful.

I just need to fix my phone.

This is the tutorial to follow.

You need termux and root and script file (already downloaded)
[Google Pixel 5a] ominiscience:
Or

1) Have a rooted Google Pixel 5a 2) Install Termux from the Play Store 3) Open it, and type “su” to grant root access 4) Run, “dd if=/dev/block/by-name/persist of=/sdcard/persist.img”
[Google Pixel 5a] V0latyle:
I'm not willing to do this, because it contains information specific to my wife's phone. You shouldn't have tampered with yours
[Google Pixel 5a] pndwal:
Writing....

If they share, the will generally be giving you their IMEI number(s), and I believe it's actually illegal to use false IMEI in many jurisdictions... Also mac, SN, WiFi, BT and other unique identifiers...

Anyway, is your device booting now?... A full ROM contains a generic persist image and should be enough to get device booting if it's not... Dirty flash (Nb. Full OTA archives may be more complete than basic Factory images, I'm not sure... On Xiaomi, fastboot ROMs are more complete than ROMs for update engine.)... Then you can report what doesn't work...

If you're lucky, ROM flash may restore unique numbers corrupted values from persist.bak (many Xiaomi devices have this) etc... I don't know if Pixel duplicates critical partitions however... Anyway, please report if boots, what doesn't work etc...

Wrong... EFS, FSG modem and more can contain unique values... Still not sure persist doesn't...

Maybe they do... 😆 PW

Edit: I've edited the above as my recall was bad... I won't need to comment further on this matter as this members handle perfectly sums up what he/she knows...
[Google Pixel 5a] ominiscience:
Don't say what you don't have knowledge of to veer others off course.

It doesn't change imei or whatever you wrote there. It set communication parameters for hw devices. Wi-Fi, touch, fingerprint, audio, sensors etc.

Doesn't in it self contain modem values. Modemst1 and 2 does.
[Google Pixel 5a] pndwal:
Ah yes, you may be right... My memory was rusty on this so did a bit of checking... Corrupt /persist (alone) can certainly cause loss of network signals however...

Interestingly, from just a little digging I find that the real issue may be simply getting /persist, /persist.bak etc to flash from ROM archive... Eg it seems that these images are present in Xiaomi 'fastboot' (ie. factory image) ROMs, but, at least from 2016, are skipped when flashing from fastboot... They will only be flashed in EDL mode...

Haven't seen how this works on Pixels, but guess it may be similar... If you can locate the images in factory ROM you may need to flash from EDL to repair...

Hope it gives clues... PW
[Google Pixel 5a] ominiscience:
Found a backup I made some while but forgot.

This might help someone.

Here:

Pixel 5a persist.img file for anyone who needs it 👍🏻

Available on request.
[Google Pixel 5a] PremiumISM:
Would you mind sharing file ?
[Google Pixel 5a] ominiscience:
Not at all.

Here:
[Google Pixel 5a] PremiumISM:
Thanks. Currently, I don't have WiFi, No IMEI on my phone, I hope it'll work. Most of all, QPST tool shows "No Phone"
[Google Pixel 5a] ominiscience:
Thank the Lord.

Ok. Just make a backup of your persist first before writing.
[Google Pixel 5a] PremiumISM:
Did you stuck on the similar problem before?
[Google Pixel 5a] ominiscience:
It's advisable to keep a backup.
[Google Pixel 5a] PremiumISM:
I flashed my own device QCN file and all this happened, and I have been stuck for more than a week.
[Google Pixel 5a] PremiumISM:
Unfortunately, my device is not allowing me to flash this file.

EDIT: I flashed persist through TWRP but nothing changed, WiFi is still not working. I believe the reason QPST is not working is somehow relates to WiFi
[Google Pixel 5a] ominiscience:
Pixel 5a xqcn file.

Pixel-5a-G4S1M.xqcn

drive.google.com
[Google Pixel 5a] PremiumISM:
I already have this file, but not able to flash it because QPST is not able to make connection with my phone. My assumption is the phone must have a WiFi connection. When the WiFi will work I'll be able to restore my phone.
[Google Pixel 5a] ominiscience:
Ok.
[Google Pixel 5a] Androiduser2390:
How would you backup the EFS without root or TWRP (stock method)
[Google Pixel 5a] GrandAdmiral:
I'm not using Canary and really don't want to (just prefer using Magisk stable). Is the guide above no longer of use for users like us since you've revised the OP?
[Google Pixel 5a] V0latyle:
Canary is generally quite stable, even if it isn't advertised as such. It's updated much more frequently too.

If you insist on using stable, you're going to have to continue disabling verity and verification every time you update.

For the sake of ease and simplicity, not to mention the potential to lose the ability to root without a data wipe, I highly recommend you upgrade to 23016.
[Google Pixel 5a] GrandAdmiral:
Ugh... ooooook. You've talked me into it. Now I need to find those instructions and link to place in.
[Google Pixel 5a] V0latyle:
Link to the latest canary is in the OP.

To pass SafetyNet, this configuration is working for me:

Magisk 23016, Zygisk + DenyList enabled

DenyLIst enabled an all components of Google Play Services and Google Play Store, as well as any financial/DRM apps (these won't trip SafetyNet but sometimes use root detection methods of their own)

Universal SafetyNet Fix 2.2.0 (must use this version with Zygisk)

MagiskHide Props Config 6.1.2 (automatically installed with DenyList I believe)
[Google Pixel 5a] GrandAdmiral:
My biggest concern has been the loss of MagiskHide. Is DenyList a suitable replacement for you?
[Google Pixel 5a] mac62:
DenyList appears to do essentially the same thing as MagiskHide. From a user perspective, I see no difference.
[Google Pixel 5a] V0latyle:
Yes. It's been working great for me.
[Google Pixel 5a] undermark5:
The guide mentions a master root image yet I do not see one offered in the downloads or am I missing something?
[Google Pixel 5a] pbanj:
i have to ask why you have people doing a bunch of stuff for updating using the factory image. all they have to do is rename the patched boot.img back to boot.img, and toss it back in the zip it was extracted from. then you just remove the -w from the end of the provided install script and run it. no need to flash the radio or bootloader as the install script will do that for you.

removing the -w stops it from wiping the device.
[Google Pixel 5a] V0latyle:
You are indeed missing something; keep reading.

Because not everyone (such as myself) likes to use the flash script. I don't recommend renaming the patched boot image to its original name as it becomes easy to confuse with the original boot image.

Additionally, some folks prefer to update via OTA. Unless you use an unpacker, you can't easily extract the boot image from the OTA; there is a way to dump the boot image from /boot using TWRP and ADB but the point of this guide is simplicity. Having a master boot image means that after installing the OTA, whether through Android or ADB sideload, you can simply boot the rooted image and use Magisk to patch /boot.

This guide is just that - a guide. Anyone including yourself may use the information for their own process. I am not going to change my instructions for the sake of someone else's preference.
[Google Pixel 5a] GrandAdmiral:
Yeah. I never rename the boot image just for the sake of ease. I got through everything using the OTA option with no problem.

If I could offer one suggestion, I would suggest notating in the instructions that even if you go the OTA route, you still need the factory image to get the boot image out for patching. Other than that, your guides are great no matter which option selected.