yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] HeadOfMax:
That worked. I swear that was the first thing I tried and it did not work. Thank you.
[Google Pixel 4a Guides, News, & Discussion] SirFronts:
I have been there before just earlier installing DU

I could swear I was typing the right commands then it just worked and I don't feel like I changed any of the commands lol
[Google Pixel 4a Guides, News, & Discussion] tcat007:
21 Beta all good, no bootloops. Just need TWRP. Nice having backups when there's an issue.

Still curious why Playstore is not certified after root.
[Google Pixel 4a Guides, News, & Discussion] ZeuBug:
Thanks for this guide :)

will it be the same for pixel 5?
[Google Pixel 4a Guides, News, & Discussion] jakelewis:
That same Google developers quote says:

"Locking bootloader will wipe the data on some devices"

Can you please confirm whether re-locking the bootloader on Pixel 4a does or does not wipe user data, (or any other effects on root etc )?

Thanks, Jake
[Google Pixel 4a Guides, News, & Discussion] jakelewis:
No Google Pay for sure. Play Store will take note, but still functions.

Other applications can also check that this profile has failed, and may choose to totally or partially restrict functionality, but I don't have a list of what those apps might be.
[Google Pixel 4a Guides, News, & Discussion] SirFronts:
I don't use google pay and my bank app is working I just used the hide feature but I'm still not passing safety net but still works
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
Consistently getting a "Failed" here -- have the Canary version of Magisk, and download the boot.img from Google (the 200720.011 sunfish) and pulling out just the boot.img. Running the Select & Patch, moving the magisk_patched back to my machine, and flashing in fastboot. Sends the file, says OKAY, then "FAILED (remote: Failed to write to partition Not Found)" then just ends. Thoughts?
[Google Pixel 4a Guides, News, & Discussion] Xowz:
Had the same problem at first. Your adb binaries are probably out of date, try grabbing the new platform tools from Google and retrying the flash. Fixed it for me.
[Google Pixel 4a Guides, News, & Discussion] bassmannate:
Getting the same issue here on a US purchased 4a. Would rather not have to re-root after every monthly security update.
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
Thanks! almost got there, i thought. That did let me start pushing the patched version, but the file patched myself results in a bootloop. when I use the patched file posted the other day, that is successful for me (takes under 2 seconds, done, reboot). However, if I try to verify I am rooted by opening Titanium Backup, it's a no-go....

EDIT: Good to go! Just refreshed Magisk again with updates, re-patched the boot image, re-flashed it, and this time bingo! Changing the updates of magisk over to canary within the app and updating was my only difference. Thank you for whomever recommended that a few pages back!
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
So, I'm on 200720.011

When I try to flash the patched boot I get the error "no valid slot to boot"

I have tried to manually flash to both A/B slots. Still no luck.

When I flash back to the original boot.img, the phone starts back to booting.

I'm on magisk installer 8.0.0: am I missing something?
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
So it sounds like nobody here has been able to get Magisk to flash to inactive slot after OTA. Is that correct?
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
How did you end up getting edXposed running? That will be my ultimate goal for a few tweaks - not worried about SafetyNet
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
This is an hard to answer question.

Considering that fastboot flashed to boot, boot_a, and boot_b successfully; my educated guess is that Magisk fails to patch the img.

What can I add is that original boot.img is ~60MB, while patched one is ~30MB. In my memory, it's normal, but maybe the information is relevant.

Moreover, a couple of times I got an empty magisk_patched.img (0B), especially when phone was still linked to PC.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
No what I mean is, based on this thread, nobody is seeing the option in Magisk to install into inactive slot after OTA. Which means they have to patch and flash manually.

The 30 vs 60 MB thing is a red herring. I successfully flashed a 30MB patched boot.img last time. It's just a compression or padding difference I believe.
[Google Pixel 4a Guides, News, & Discussion] rzracer2:
Am I the only one getting 0kb patched boot images with Oct update? This is happening to the 4a as well as my P2-XL. Annoys me that Magisk manager will NOT let you patch unless you first update to the latest version. If anyone has patched the Oct boot image I'd love to have a copy. Thanks
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
As I said a couple posts ago, I noticed the same problem. Repatching (possibily with the chord disconnected) created me the (not working) img file
[Google Pixel 4a Guides, News, & Discussion] rzracer2:
Sorry I missed your post about the issue, guess I'll go back to Sept until it gets sorted.

---------- Post added at 01:57 PM ---------- Previous post was at 01:52 PM ----------

I also patched the 4a boot on my P2 before I updated the P2 and it gave me a patched boot file and flashed fine. Magisk manager showed Magisk was installed but there was actually no root. I thought I found a workaround but not.
[Google Pixel 4a Guides, News, & Discussion] Enddo:
just tried it out and that is the current result with Manager v 8.0.1 (304) and Magisk v 21.0 (21000)

so yea, this is a known issue - https://twitter.com/topjohnwu/status/1303574238796808192
[Google Pixel 4a Guides, News, & Discussion] tcat007:
I got a patched image the same size using Magisk 21 (beta). But the Oct update through OTA didn't update. I haven't tried fastboot with PC yet.
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
Quick update: I updated MM to 8.0.1 (Magisk 21) and now it patched perfectly
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Did you update? What process? I just made a patched image with 8.01. Did you just use phone or fastboot on PC?
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
It was my first root on this device, so I had to go through the whole "factory boot.img -> create patched img -> flash with fastboot" thing.

The problem is that with the previous version of magisk, the the patched img didn't work properly
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Still no "install to inactive slot" option with 8.001. Tried the OTA update again, then install Magisk and boot. Still shows Sept update. I'm ok with Sept until someone posts a method that works.

If I hit reboot within the OTA update screen it should update, right? Just lose root, then need to fastboot the patched image on a PC, right? No data loss?
[Google Pixel 4a Guides, News, & Discussion] timjon:
That worked for me, yes. I just reflashed the previously rooted boot.img - which I suppose might be risky if it was changed in the OTA, but seemed fine for me. No data loss, it just restored root.

I'm not an expert, but if you're worried about the boot.img potentially being out of sync, you could probably download the newest images from the google site, use magisk manager to patch the boot.img from that, and flash that instead. Or just pull the newest images and compare to the boot.img you already have to see if it differs.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Thanks. Did you uninstall Magisk first? I have the patched boot from the OTA (.006). Probably safest to just uninstall Magisk then reboot, then apply OTA. Then fastboot the patched image.
[Google Pixel 4a Guides, News, & Discussion] jakelewis:
That was indeed risky. Was your previous installation an 11 beta? Jake

---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------

To answer my own question, it is a bit immaterial as to whether relocking wipes the user data, as unlocking next time an OTA is needed will certainly wipe it.

I guess Magisk's, (now seemingly unavailable), "install to inactive slot" method also required an unlocked bootloader?
[Google Pixel 4a Guides, News, & Discussion] tcat007:
If I just uninstall Magisk, reboot, then install OTA from phone, will I lose data?

Do I need to hit restore images first, then uninstall in Magisk?

Edit:. I just uninstalled Magisk and rebooted. Booted to Sept security.

Hit OTA update on phone, about 15 minutes later, hit reboot, 5 minutes later opened to Oct security. Nothing lost (except root).

I'll fastboot the patched boot image later.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
So my phone hasn't received the OTA yet.

If I wanted to flash it myself from the stock October 2020 image, and not get my data wiped, and get Magisk back in there... what should I do? I haven't tried this on an A/B device before and some of the partition names are new to me.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Well, I fastboot flashed the patched image file, booted fine, but no root. Guess I'll switch to Canary and try it, but beta 21 should be compatible.

Very odd... I switched manager to canary, patched the .006 boot image. I went to bootloader and think I accidently hit the power button because it rebooted before I did anything. I decided to look at MM to make sure it was still there, and canary showed Magisk 21 was installed (rooted!). So I uninstalled manager canary and installed manager beta 8, and all looks good and rooted. I say odd because I'd previously rebooted and was still not rooted. Hopefully the bugs in Magisk will get worked out.
[Google Pixel 4a Guides, News, & Discussion] nindustrial:
Did you try Canary?
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Ok I got the OTA notice. It occurs to me that the message says:

Security update available Improve the security of your device (Pixel 3a)

3a? Oh right, the attestation fix is identifying the phone as 3a. But does this mean it's downloaded the wrong device's OTA?
[Google Pixel 4a Guides, News, & Discussion] Renovatio33:
MM 8.0.1 the issue. I guess Canary would have worked the same
[Google Pixel 4a Guides, News, & Discussion] Jep56:
Bricked?

Followed instructions. After flashing Magisk_patched.img, phone will not boot, just remains in fastboot?:cyclops::cyclops::cyclops:
[Google Pixel 4a Guides, News, & Discussion] rbouza1:
Reflash stock boot
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Well... I had a fright but I pulled through.

Downloaded full stock ROM, extracted boot.img, patched on-devices, pulled back to computer.

Attempted to follow the full "flash-all.bat" minus the -w so it would not wipe.

After everything finished the phone went to reboot and I stopped the boot cycle to get back into bootloader and flash the patched boot.img. (This might have been my mistake - maybe it stopped something from finishing properly.)

Then I tried to boot and it just flipped back to bootloader. Tried reflashing stock boot.img, same. Damn.

OK so then I downloaded the Full OTA of the new release and followed THOSE instructions right from Google. Many nail-biting minutes later... Yay! It finally booted. Nothing wiped. EXHALE. Thankfully Google Pay did not clue in immediately that I no longer passed SafetyNet.

I immediately rebooted to bootloader again and flashed the patched boot.img. Phone booted into system properly. Still passing SafetyNet.

... this is making me really really wish we had a custom recovery
[Google Pixel 4a Guides, News, & Discussion] rG-:
Ok, so here is what worked for me:

- tried patching boot.img with stable Magisk 8.0.1--> Bootloop

- i noticed that the failed patched image is also much smaller then the original one (32MB instead of 60 something MB) -> thats how you already see if it will work or not.

- reflashed boot.img to restore functionality

- changed update channel in Magisk Manager to "beta" and tried it again --> worked!
[Google Pixel 4a Guides, News, & Discussion] rbouza1:
So with 8.01 magisk I patched a boot and it ended up being 62mbs or so. I'm gonna flash it later and see
[Google Pixel 4a Guides, News, & Discussion] tcat007:
That's what I did. It ended up showing no root, but somehow ended up rooted after installing Canary MM and rebooting. Really not sure what really worked, but just showed rooted after messing with it.
[Google Pixel 4a Guides, News, & Discussion] Jep56:
Which canary?

Exactly what file is to be used from here:

If you're having issues, try canary build instead: https://github.com/topjohnwu/magisk_files/tree/canary

app-debug.apk or stub-release.apk...those are the only apps there
[Google Pixel 4a Guides, News, & Discussion] codlike:
i used the app-debug.apk
[Google Pixel 4a Guides, News, & Discussion] gtown:
I have successfully unlocked the bootloader and rooted both Koodo carrier provide Pixel 4a's!

Just left with the Android 10 it came with.

I have not attempted the safety net yet but so far love the phone. Magisk is up and running!
[Google Pixel 4a Guides, News, & Discussion] defTwitch:
Posted this in stock/rooted boot images thread but perhaps this is the right place (sorry for a double post):

So soft bricked my phone. If someone can help me get back on track. Using win10 laptop. Got a 4a I bought from google. Verizon sim inside it from my old essential phone.

I think the issue is I took the OTA to go to 11. Then when I started doing things I didn't use Canary version of Magisk.

What I've done:

Enabled OEM unlocking

did fastboot flashing unlock

android came back up

I installed Magisk (but realize now it was NOT canary)

I made my own image using the build that matches my phone from this thread:

Rooted Boot Image - Global - rp1a.200720.011

I ran Magisk Install on that. Took the new "patched" image and copied it to my computer.

I went into fastboot... did a fastboot flash boot (with the image I created).

Now I'm stuck in a bootloop. Google logo comes up but nothing happens.

I've tried flashing multiple stock / root images. I tried going to google's page and pulling the latest stock image for my phone and flashing that.

I've tried erasing a/b and then flashing again.

No matter what I do at best the Google logo sits there forever. Some stuff I've flashed just causes it immediately to go back to fastboot and my phone says it is now corrupt.

I assume I'll be ok. I just need to get a working flash on here and do things correctly / use Canary version but I can't see to flash anything now the phone will accept.

Any suggestions greatly appreciated! Need a phone!

Also tried doing a flash-all.bat with a full download from google of:

sunfish-rp1a.200720.011-factory-1a38c5a6.zip

Same deal. If I restart phone it says it's corrupt. If I continue the Google logo comes up and just sits. Phone doesn't progress. Only way out is to just force it back into bootloader.
[Google Pixel 4a Guides, News, & Discussion] defTwitch:
I think it was all that windows was still pointing to an old version of adb / fastboot from when I was playing with custom roms with my essential phone.

As soon as I ran "adb version" and saw where it was pointing I nuked that... fixed variable for where windows pulls the executable from and was able to get it back up and running.

aka... user error!

Enjoy your day!
[Google Pixel 4a Guides, News, & Discussion] Dr.Tautology:
Just had a nightmare trying to root my new pixel4a. Thought I would share to save anyone the same problems/mistake. I had previously set up the device stock on the Sprint network using ESIM. I then decided to go ahead and root, so I unlocked the bootloader/factory reset. This is when my issues started. After running through the setup I was unable to download the ESIM again. I kept getting an error saying that I needed to contact customer support to activate my device. After many hours of troubleshooting with support they were able to get my phone back to a state where it was able to receive calls and messages, however the mobile data was not working. After a long time of troubleshooting I decided to go ahead and try to erase the ESIM and then re-download it. This option is in settings>network>Mobile Network>Advanced>Erase ESIM. This will apparently wipe your entire device and number from your Sprint account. DO NOT DO THIS. I logged into my sprint account and sure enough, my device and number were completely gone. The service rep said he needed to escalate a ticket to get this fixed, but what a colossal mistake on my part. I also found it slightly ironic that these companies don't trust us enough to have superuser access to our devices, but there is a single button anyone can press that will wipe your account off their network. Pray for me friends. This has been a terrible experience and has made me question whether it's even worth the trouble anymore. I went ahead and re-locked my bootloader in the meantime and will probably keep it that way.
[Google Pixel 4a Guides, News, & Discussion] digger16309:
Not sure what I'm doing wrong. I've tried patching the boot.img with both 21 Beta and Canary and end up getting an error in the bootloader. I have to re-flash the boot.img to recover.

I keep getting a "no valid slot to boot" error.

Perhaps the OTA update that I took by mistake is corrupted somewhere because a patched boot.img won't from the October update won't take.
[Google Pixel 4a Guides, News, & Discussion] NBreunig3:
Hi everyone! Just bought the Pixel 4a (unlocked) from Amazon after my Pixel 2XL decided to no longer recognize my touch input. I have been out of the loop on rooting for a few years now but excited to get back into it. My only area of concern is that I will be using Verizon. I realize it is the unlocked version so unlocking the bootloader won't be a problem. I just want to make sure if I do unlock it, and then stick in my old Verizon sim (from my Pixel 2XL), it will properly activate. Anyone using a Verizon sim care to talk about their experience. Thanks.
[Google Pixel 4a Guides, News, & Discussion] DB126:
Works fine; immediate activation. Don't root/unlock for 72 hrs (best practice). Rooting has lost much of its luster of late due to more capable devices/roms and pending hardware attestation which forces kludgey workarounds. I miss the capability/flexibility; not the headaches. Pick your poison wisely.
[Google Pixel 4a Guides, News, & Discussion] rbouza1:
Make sure to get oem unlocking checked in dev settings before you try. Once unlocked it'll work fine. I use us mobile which uses verizon and it's fine
[Google Pixel 4a Guides, News, & Discussion] rG-:
Heres is another update from my site:

regarding safteynet:

I followed the instructions on first page: worked flawlessly!

Passed safty net on latest OTA with Android 11 rooted.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Worked here too. A bit of hit and miss on rooting, but it's nice to be rooted. Probably could have lived with stock, but ability to use Accent Color Creator, Custom Font Installer, and Full Screen Gestures is just better.
[Google Pixel 4a Guides, News, & Discussion] Pollie81:
On my rooted OnePlus Nord my Dutch banking app didn't work. It somehow detects the unlocked bootloader or rooted state.

Does anyone know if that's the same on the Pixel 4a?

Or is there anything you can do to keep root and a working banking app?
[Google Pixel 4a Guides, News, & Discussion] bobbarker2:
On your site? What are you referring to?

And the only way to pass safetynet rooted is with magiskhide props module and setting device attestation enabled and changed device id to a device without hardware attestation.. pixel 3a is a good choice.

---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------

Are you using magiskhide on the app?
[Google Pixel 4a Guides, News, & Discussion] Pollie81:
Yes and i changed the name of the manager.

But i only checked magisk hide in the settings, i didn't flash the props module. Could this be the cause?

Or should any banking app work with this procedure mentioned in OP?

Cause then I'll just give it a try..
[Google Pixel 4a Guides, News, & Discussion] crackerjack1957:
Don't change manager name, follow instructions in 1st post

Passing SafetyNet

As was discovered some time ago, google is switching to a hardware attestation method for safetynet. Fortunately, at the time of writing, there is a workaround thanks to [MENTION=4667597]Didgeridoohan[/MENTION]:

Enable MagiskHide in magisk manager

Download/Install his MagiskHide Props Config module from the magisk module repo

Reboot

Open terminal app on your phone and type 'su -c props'

Select 'Force BASIC key attestation'

This will make your device appear to be a different one in some instances and by default, this is Nexus 5. I prefer it to look like a newer device that doesn't have hardware attestation (Pixel 3a). So choose:

'Pick from fingerprints list' -> 'Google' -> 'Google Pixel 3a'

Reboot and verify you should hopefully pass safetynet!
[Google Pixel 4a Guides, News, & Discussion] tcat007:
I left it at default 4a, and all is good. Playstore even became certified.
[Google Pixel 4a Guides, News, & Discussion] crackerjack1957:
Safetynet fails with attestation check in Magisk with 4a even if Gpay still works

Mine passes with 3a & Gpay works also so I'm leaving as is.
[Google Pixel 4a Guides, News, & Discussion] T0unet:
- I had the 32 Mo boot.img problem with 8.0.2 Magisk.

- The boot.img restore did'nt work. (Don't understand why, corrupt already there)

- Restore full flash 11.0.0 (RP1A.201005.006, Oct 2020) -> All good

- Finally flash boot.img after last canary release => That's ok

So now i had the problem about bluetooth and spotify freeze and cut sounds. There are lot of post about it on reddit, and community spotify forum. But no clear workaround.

No time for downgrade to 10. :crying:
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Passed here.
[Google Pixel 4a Guides, News, & Discussion] crackerjack1957:
You on Android 11 or 10

On 10 here........ could be the difference
[Sony XA2 Ultra Questions & Answers] thetao:
Is there a way to know which band the phone is currently using? This is a completely stock H3223. I found threads like https://xdaforums.com/crossdevice-dev/sony/check-band-connecting-xperia-t2914376 but those service codes apparently don't work on newer phones. There is some real-time tower data under *#*#4636#*#* at the bottom of "Phone Information" but none of it appears to be what I want.
[Moto G Power Guides, News, & Discussion] Bobthahog:
I purchased a Motorola Moto G power directly from the Google site and paid full price but every time I type in my bootloader unlock key it says my device is ineligible. Does it have to be a certain amount of days after I purchased it for it to be eligible? I have tried it numerous times and it just will not work. Can anyone please offer some advice? It's model number XT2041-4. I have had this device for at least a couple of months. Someone has some info to offer that would be great. Motorola hasn't even updated their page because the newest models it shows is the G7 series.
[Moto G Power Guides, News, & Discussion] excelsus85:
Do you type the key right? If so, some phones can't be unlocked, you have to wait to Motorola update the page. Do you put the right region page for your phone?
[Moto G Power Guides, News, & Discussion] Bobthahog:
Yes I have went through at least 5 times and wrote down twice so I know the unlock key is right. It might be that I owe money still. I got on a deal for $150 that being hundred dollars off the regular price but then I hardly used it and money got tight so I canceled service trying to save money and my dumbass canceled it 7 days too early and I lost out on my promo discount of $100 so actually I still owe $96. That could be what's holding it back. And plus Motorola needs to update their page. I'll wait till that last payment comes out and then try it again. Actually I think the payment came out today.