yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] LGHT:
Looking to get a phone around the same size as my S10e so I can get root and install custom apps and was considering the Pixel 4a. However I just noticed that Verizon locks the phones so don't get the phone from them?? I did some research on their site and found this..

"It’s illegal in the U.S. to unlock a phone without the carrier’s consent, so never pay a 3rd party who promises to hack the lock code. But don’t worry — carriers must give the code to consumers at no cost, so long as they meet certain criteria. Among wireless carriers, Verizon provides an unlocking policy that’s both generous and straightforward. To combat theft and fraud, Verizon locks all prepaid and postpaid devices for 60 days (check out the full Device Unlocking Policies). After that time, Verizon automatically removes the lock and will not lock phones again at any time."

Does this mean I just need to ask for a code or wait the 60 days to root the phone if I get it from Verizon? I only ask because I can get a new phone for $80 under my companies account.
[Google Pixel 4a Guides, News, & Discussion] 12paq:
Yes.

You need to use Magisk canary.
[Google Pixel 4a Guides, News, & Discussion] Mr.Demous:
I managed to fix my problem after a lot of tinkering. I found out that SmaliPatcher Secure Flag module was the culprit that was causing the bootloop.

I flashed the stock boot image, initiated a safe mode reboot (I couldn't get into safe mode with the button combo after flashing the patched image) and then went directly into the bootloader, flashed the patched image and booted into safe mode. I ran "adb shell magisk --remove-modules" while in safe mode(this command didn't work when my phone was stuck in a bootloop). I then rebooted my phone and it booted up normally with magisk installed and working and all the modules deleted.

Thanks for your help @Typhus_ , I appreciate it.

@tohypnos , This is exactly what I ended up doing last night and it worked perfectly. I wish you posted this info a little earlier, could've saved me a lot of time. :D
[Google Pixel 4a Guides, News, & Discussion] tohypnos:
Ah-hah! It was a coincidence just I had an earlier night due to the time difference then:)

It's anyway nice to hear that the same solution works. In my understanding, Magisk automatically disables all modules if you boot with the safe mode, and remove modules command is not necessary (in fact, I didn't need it.)

I always saw and tried that command but didn't come up with the idea of flash Magisk during the boot process to the safe mode. I recommend adding this procedure to the guide if some others succeed getting out of bootloops issue.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
So today I did my update directly from January to March patch including Magisk. Only modules I had installed were the Props and kdrag0n module. Applied full OTA and then flashed patched boot.

Had a weird-ass experience. Some kind of file system mount failure. Apps would not load, and adb shell couldn't find the storage, with error: /system/bin/sh: cd: /sdcard: Transport endpoint is not connected

Anyway safe mode worked. Rebooted into regular mode and all was fine but SafetyNet did not pass. But then realized that Safe mode triggers a disable of all Magisk modules and also of MagiskHide. Re-enabled just kdrag0n and MagiskHide, and rebooted. SafetyNet passing again. Had to clear Play Store data for it to pick me up as certified again. Pay does not seem to have noticed the blip so fingers crossed on that one - I know it has a tendency to check on a regular basis instead of all the time.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
I'm tired of waiting for March ota. I have this file: sunfish-ota-rq2a.210305.006-57b707c5 on my phone. All I need to do is boot to recovery and "apply from sd card", right? No pc required. I can the flash March patched boot image if I want root from a pc.
[Google Pixel 4a Guides, News, & Discussion] Typhus_:
Yeah, in theory yes, that file you have is the OTA update. But, it's strange that, if it is, then why isn't already installed?

On the other hand, since you're going to connect the phone to your PC to flash the Magisk patched image, why won't you just download full factory image from Google site and install it through fastboot? That way it's guaranteed it will update.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Well I tried and failed. I had downloaded the ota file from Google. When applying from SD Card in recovery, error "could not mount sd card". Booted back to February fine. I'll try the factory image later.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
And dont forget to drop the "-w" i.e. dont wipe when applying the full firmware.

Thats the way I did Jan, Feb and march. Although for Jan I forgot to remove the -w and learnt my lesson.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
I find that installing the downloadable full OTA over ADB (see official Google instructions) is much easier than flashing the full ROM in fastboot. The former is a one shot operation and has never failed me. The latter is more complicated as it reboots again into "fastbootd" to install userspace items, which has sometimes glitched out on me leaving it unbootable.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Adb sideloaded, no real issues. Odd, PC got to 94% with message "failed to read command: No error". But phone said 2/2 completed successfully. About says March 5, so must have worked.
[Google Pixel 4a Guides, News, & Discussion] bobbarker2:
Yes as I said in my original post, I did that. I think one of those ainur audio mods makes system nods outside of Magisk as I saw a lot of errors pertaining to audio in the infinite boot loop.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Sorry, didn't read all your post history, carefully.

The other place to check for mods are in the post-fs-data.d and service.d scripts, and possible the settings.
[Google Pixel 4a Guides, News, & Discussion] bobbarker2:
I've been through it all and ended up having to do a factory reset. Then it updated fine. Must have been specific to my system and the only thing make affecting system behavior would be modules. With everything removed, it should have worked which is why I think some module made an actual change to my system that was outside of Magisk.
[Google Pixel 4a Guides, News, & Discussion] ekowwillis:
I've tried to follow the steps on rooting my Pixel 4a 5G with Android 12 Beta 1 but to no avail.

Please has anyone been able to achieve root? Kindly share the steps.
[Google Pixel 4a Guides, News, & Discussion] Ruttix:
Would anyone care to explain how to take an OTA with Magisk?

I'm confused as to whether I should flash the entire ROM or just the OTA and also about changing the flash script in either one?
[Google Pixel 4a Guides, News, & Discussion] a1291762:
The "least strps* way is

Download the factory restore zip

extract it

edit the flash-all script to remove the -w flag

run the script

unzip the file next to it

upload boot.img to the phone

Use Magisk manager to patch it

download it

Reboot to bootloader

Fastboot flash patched_boot.img

I use fastboot boot boot.img and flash from Magisk manager instead. It means Magisk manager can un-root you by itself.

Sorry for the vagueness but my PC isn't here so I can't check on file names. Should be obvious...
[Google Pixel 4a Guides, News, & Discussion] Ruttix:
Thank you.

This would keep all as is on my phone, as in not reset it?
[Google Pixel 4a Guides, News, & Discussion] a1291762:
The -w you are removing tells fastboot to wipe user data. By removing it you keep user data.
[Google Pixel 4a Guides, News, & Discussion] Zaxx32:
Been watching this thread and doing all I can not to 'pull the trigger' and finally root after waiting months hoping for a TWRP? Magisk sustainable root solution...lol

Just want to wait a few more days to make sure everything still works ok with this June update so I can gain confidence that I can do my July update without screwin' it up somehow!

Everything was so much simpler when I did my 'single slot' Moto G5+. Then I got the G7 thinking everything would be same as with G5+. Gave up waiting on the G7 and got the 4a assuming I'd have it made...smh

Sorry for the ramble...but just wanted to thank you guys for figuring out the best way to update after root. Heh...have my bootloader unlock key at the ready, waitin' for this update to drop. Don't mind the wipe knowing I won't need to repeat, fingers crossed!
[Google Pixel 4a Guides, News, & Discussion] AliMusa:
When trying to root using powershell, I put my patched boot.img file in my platform-tools folder, and open up powershell from that folder. However, when I run the command, I get an error saying that it failed to write to partition. This is the error I get:

fastboot flash boot magisk_patched-23000_AVQT0.img

target reported max download size of 268435456 bytes

sending 'boot' (65536 KB)...

OKAY [ 1.500s]

writing 'boot'...

FAILED (remote: Failed to write to partition Not Found)

What could I possibly be doing wrong? I've downloaded the latest platform-tools
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
Heyy!! I tried this method today for june update. I havent rooted my phone yet and my phone booted fine with flashh-all script. I am facing one problem though. When I connect my usb to phone there is no notification to select transfer files option or adb option. That notification is gone. Any help?
[Google Pixel 4a Guides, News, & Discussion] a1291762:
That's not a current fastboot because it doesn't know how to turn 'boot' into 'boot_a' or 'boot_b' based on the current slot.

If you can't upgrade to the current fastboot, you can try one of these options.

1. Find your current slot and boot that:

fastboot getvar current-slot # will be 'a' or 'b'

fastboot flash boot_a magisk_patched.img # or boot_b

2. Boot the patched image and get Magisk Manager to do the permanent installation.

fastboot boot magisk_patched.img

# use Magisk Manager to install (direct)
[Google Pixel 4a Guides, News, & Discussion] a1291762:
I have no idea...

Is USB debugging still enabled in Settings -> System -> Advanced -> Developer?

Can adb see the phone?

Do you have Settings -> Connected Devices -> USB? Mine is set to "USB controlled by this device" and "Use USB for No data transfer".

I get 2 notifications when I connect USB. one for ADB and one for regular USB.

Maybe you need to disconnect and re-connect the cable?
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
yeah i too used to get those 2 notificatins. now theres none. my device is detected though. and i see my devicewhen i use adb devices command. just no notification and hence i cant use transfer files option. i tried everything reconnecting, rrdtarting mobile , laptop etc.
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
still no notification but i found a setting in developer option to connect file transfer when i connect my phone to usb. so at least file transfer also working and usb too. just no notification.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
It is possible to hide notifications...

Maybe you accidentally did this for the USB notifications? I have no idea what "app" they are attached to though... System Events or SystemUI probably...
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
that might be a case ... and i too dont have any idea lol
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Doh! I'm an idiot. I can find out when I get home and plug my phone in 🤦‍♂️
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
reached home yet? lol
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Had a ... Bad few days. Long story.

Anyway, it's Android System and I can't even disable these notifications, though I can customize them...
[Google Pixel 4a Guides, News, & Discussion] kiritoxd:
Hi, i see that this guide is for the stock pixel 4a firmware only but is there anyway to get magisk in GSI roms as well?
[Google Pixel 4a Guides, News, & Discussion] thedemon786:
sorry to hear that man. hope you get better days now. i guess i wont wipe my phone and wont flash the file again. no notification but my phone is connecting to adb and in transfer file mode. so no probs i guess
[Google Pixel 4a Guides, News, & Discussion] andyxo:
Problem with rooting June 2021 OTA RQ3A.2106.05.005 with Magisk 23.0 (is using 23.0 the problem?) Please read below...

So it's June 2021 now and Android 11 latest OTA Update is RQ3A.2106.05.005 (5 Jun 2021). I am a new Pixel 4A (4G) owner (coming from Lollipop) following the root steps carefully as I could but also realizing that the guide in the original post is somewhat old and written for what worked last year and other posts in this thread were written for older (pre-June 2021) OTA updates.

So unlocking the bootloader was easy. Rooting seemed to be easy too but now am not able to get either Root Explorer/ES File Explorer/Solid Explorer to perform "root-required" tasks. So I guess I better explain what I did to root this device and hopefully one of you root geniuses can pls tell me how to fix this and/or where I went wrong...

-- Downloaded the whole RQ3A.2106.05.005 2GB file (Pixel 4a Sunfish) and extracted the boot.img

-- Did the boot.img patching with Stable Magisk 23.0 because I read in this thread that the stable works now *(the big ?)*

-- Did the fastboot cmd stuff (Win7) with this command : fastboot flash boot magisk_patched-23000_POZm8.img

-- This is the only thing that cmd said after I did this: (Is this correct? Is this what it should have said?)

E:\Pixel Stuff\platform-tools>fastboot flash boot magisk_patched-23000_POZm8.img

Sending 'boot_a' (65536 KB) OKAY [ 1.544s]

Writing 'boot_a' OKAY [ 0.296s]

-- So rebooted and a simple root checker app available from play store said yes, I have root. Well, am not so sure about that which I discovered soon after...

-- First test I did to make sure I have root is to fire up Root Explorer and try to enable r/w in a root-required folder. It asked for Superuser which I granted but Root Explorer failed by not allowing me to enable r/w access nor copy a file/create a folder into a r/w protected folder even though I granted Superuser access to it. "System/usr/keylayout", for example.

-- So did some more reading and thought that perhaps I need to do the whole SafetyNet Fix to get Root Explorer to work properly. So followed all those steps and yes, now I am passing all the Magisk "Check SafetyNet" checks. All Blue, Success.

-- Rebooted phone a few times. Go back to Root Explorer and still no dice. Can't do root-required tasks. Thinking Root Explorer might be the culprit, tried ES File Explorer & Solid Explorer. Also no dice after granting root access to them, also says fail fail fail. Both these apps are the newest versions as of today.

-- This is now where I have stopped. Have done nothing else to phone until I get this thing properly rooted with file explorer access. No magisk modules are installed.

Okay guys, what did I do wrong and please tell me how to fix this please or what I can try? What can I check to see if I am properly rooted? My limited expertise has run its course...

​
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Your device is read-only for many "root-required" paths, on older devices. You cannot modify partitions such as System. The fact that you have not explicitly stated which paths, gives me the impression that you are probably trying to do doing something beyond root. To modify these RO paths/partitions, they have to be done systemlessly, through magisk.

As a side, instead of your other explorers, try MiX, and set the namespace in Magisk to global.

https://xdaforums.com/t/app-2-2-mixplorer-v6-x-released-fully-featured-file-manager.1523691/unread

You also appear to be mixing between the Jun firmware with the older May update.
[Google Pixel 4a Guides, News, & Discussion] andyxo:
Hi DJ, thanks for your reply and again thanks for supplying me with that V4A for Android 11 file via pm yesterday...

So regarding my file explorer probs above, after much research I didn't know that we are not allowed to do the things we took for granted in rooted lollipop anymore (lollipop was my last phone, rooted with Kingoroot, making a big jump to 11, I know ;-) so I am way behind in Android & Magisk knowledge wise, so I hope you can forgive that. So it does seem I have rooted my 4a correctly which is some good news at least because the whole reason for this is to use V4A.

And DJ, while I have your kind attention, regarding that Android 11 V4A version you gave me... can I now attempt to install that version with Magisk v23 installed? Or must I downgrade Magisk first while hopefully not losing root by doing that... Cheers!
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Viper works with Magisk v23.0

Where did you read that you need to downgrade Magisk?
[Google Pixel 4a Guides, News, & Discussion] andyxo:
I don't remember where I read that... I have been reading so much trying not to make mistakes & screw my new phone ;-)

So today installed that version of V4A that you highly recommend for Android 11 and after the reboot I had no system sounds, my music app wouldn't open & system settings kept locking up. Yikes! So uninstalled it and after rebooting the problems went back to normal, thank god.

So reinstalled it again, and now seems to be working okay or at least I haven't lost my system sounds yet again after multiple reboots with V4A enabled. Then had to figure out where to put my revolver file because there is no option where to point the storage to like in older V4A versions. Finally find it under Android>data>com.pittvandewitt.viperfx

First thing I noticed is how different (less bass, less oomph) this version of V4A sounds on my Pixel 4a with my bluetooth headset versus the V4A v2.5.0.5 on my old cheapo rooted Lollipop phone I got six years ago even though they both seem to have the same V4A driver 2.5.0.4. I got both phones set up with same V4A settings, Convolver & DDC and with same music player (also with same settings) and they sound so radically different with the same bluetooth headset. Great on the old cheapo phone and quiet & crappy on the Pixel 4a. I don't know why this is or what to do about it.... any ideas?

Edit : Also, using your permissive.sh file caused me to get "no driver found" when going to V4A after a reboot... replacing that permissive file back to the original and rebooting no change so had to uninstall V4A again and then reinstall again...
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Then be careful, simply asking such a question puts doubts in people heads, and now someone else is going to believe that "they read somewhere" you have to downgrade Magisk., Naybe edit yur original post with a strike through on the question.

I have had a history of weird boots with my Pixel 4a. Totally unrelated to sound, and more commonly with the older firmware builds. I am strill comming to terms with the phone nopt totally booting until after I have unlockied it. Thiosmay also affect your results.ie how long between the boot and when you unlock it.

The sound that comes out of viper is TOTALLY dependent on your settings/config. I have a pretty good sound system in my car, and I also have a lot of experience with digital sound, and I know how to configure my Viper (for rme) such that my rear view mirror will vibrate when a heavy bass song comes on and the volume is up (the car came stock with subwoofers). Its all in your settings. Maybe the default settings are less aggressive OR the dials are less responsive at the lower settings, but I have had no issues getting more than enough bass than my stereo could handle. For your test, simply lower the sub freq to 40Hz and the type to Subwoofer, and move the Bass Gain over half way, and push the Bass frequencies up in your Eq,. You will have more bass than your stereo could handle at louder volumes.

You can play with the delay (ie extend it) on the permissive script. I have now moved it into a separate script, as part of my many boot scripts. You can even test theeffects of manually switching a few minutes after boot. This app lest you manually switch using a UI (as well as many MANY other things) You can fiund it in the menu under Current State>SELinux Status

[APP][TOOL] TeMeFI comprehensive system Administration

TeMeFI This app provides/returns a bucket load of information regarding your device and the currently running ROM, and much, much more. And hence the name "TeMeFI"; as its Too Much F????? Information. The F stands for whatever your comfortable...

xdaforums.com

I have never used Bluetooth audio with viper, I thought that it may of actually by-passed viper, for at least some. Again, it may just be the settings that will need to be different to what you previously used.

Comparing the sound difference between one version and another is pointless without adjusting the options/setting, which is where the change MAY actually be. They may of changed some knob from linear to log. The sounds thesame, but the settings/slider will be different.
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
okay so i may have tried to rush an update, or rush and hope for the best? One way or another, got stuck :). Pixel 4a, had not taken an update since Sept 2020 (liked it how it was, ultimately was annoyed I was unable to update my camera app).

I updated Magisk to the latest, "uninstalled" via magisk, took the OTA to do the install.

Loaded the boot.img direct from google to the phone, patched it with Magisk, and moved it back to my computer. trying to flash with ADB and getting "boot partition is smaller than boot image" - it's trying to use partition A, if that matters. Thoughts/tips?

Also - is it worth using the Chrome Flash Tool? seems interesting - with options to force flash all partitions (is that a good thing?) and also a "Force Debuggable" which indicates it enables adb root - either a good path forward? phone is usable at this point just would like to get magisk and root back

edit - tried patching one more time from magisk then applying the patch and seem to be in trouble. it gives me "sending xxxxxx, writing xxxxx" both to boot)a, both OKAY, finishes with my total time....then fastboot reboot and it cant get past the google logo. once it does, it goes back to fastboot mode and cant boot out of it..

EDIT EDIT - used the chrome recovery tool and it got everything installed as needed! Have not tried to root again (yet :-)) but back running stable
[Google Pixel 4a Guides, News, & Discussion] andyxo:
Hi, did you get your boot problem sorted? I just flashed RQ3A.2106.05.005 with Magisk 23.0 a week ago on my Pixel 4a (4G Sunfish) and for me had no problems installing it or booting with it for the week.. do you want me to upload it for you?

Edit : Never mind, narrowed down my intermittent boot "no sound" problems I mentioned in a post earlier in this thread to the patching of the boot file with Magisk 23. Finally after much troubleshooting I removed Magisk 23 (removed root) and now my phone sound is stable again. So gonna try to do the whole root procedure again but this time with magisk manager 8.0.2 & Magisk 21... wish me luck lol
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
What timing just came back to add an update! I had to swap my sim for the day because couldnt focus on it, but last night i hooked it up and used the Chrome Flash Tool - took a bit, but everything came right back up (sigh of relief). So back running, but havent re-tired Magisk yet but will give it some testing later this afternoon!

that sound issue would be frustrating! Good luck!