yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] ReservedName:
has anyone seen a persistent notification about rebooting to apply the system update? I'm pretty sure it already applied and I have tried accepting the prompt a few times. I'm not sure if it might come back but already two or three times beyond the post update reboot. strange
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
Slightly OT here but how did you manage to get EdXposed running? Can you please link to the modules and Manager used? Ideally, you would be doing a big help if you open a separate thread and mention in detail

Thanks for your time

Edit : Created a thread here

https://xdaforums.com/pixel-4a-5g/help/question-edxposed-android-11-pixel-4a-t4186983
[Google Pixel 4a Guides, News, & Discussion] skyguy126:
I tried following this guide with the Nov 5th update, and I was able to successfully unlock my bootloader and I copied the stock boot.img to the phone, used magisk manager to patch it. Then I did

fastboot flash boot magisk_patched.img

and the phone says device corrupted in red when powering on, and it seems to hang once the Google logo pops up. I tried to fastboot flash boot with the stock image but I still cannot get into the OS. Also as a side note it says boot partition b in the bootloader screen.

Anyone know what might have went wrong or if I'm straight up bricked? I can still access the bootloader.

EDIT: Got the phone to boot by switching to partition A and flashing the stock boot image. Think my boot slot B is corrupt? Any ideas on how to fix?

Also flashing the magish patched image doesn't let my phone boot? Anything I'm missing?

EDIT2: Used Magisk Canary: https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk

to patch the stock boot image and flashed that into partition a and device booted with root! Guess for android 11 you need the latest manager from github.
[Google Pixel 4a Guides, News, & Discussion] digger16309:
I'm A10 and will stay there until ViPER4Android improves and GravityBox (w/EdXposed) is available for A11.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Does this from OP work for Nov patch?
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
I am pretty sure that's not working right now on A11 so the Magisk developer took it out.

I haven't applied November yet. What I did for October was download both the full image and the OTA zip. Patched the stock boot from full image with Magisk and transferred back to computer. Applied full OTA in recovery and then immediately after successful boot went back to bootloader and applied patched boot.img. I didn't manage to reboot fast enough for Play Store to stay certified, and had to clear Play Store data. But Google Pay continued working.
[Google Pixel 4a Guides, News, & Discussion] CSX321:
If you have Titanium Backup, you can freeze Play Store first, so it doesn't have a chance to run before you flash the patched boot image.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
That's a good idea. I did at one point make an attempt to flash the new image and force the phone to power off before completing its first reboot and go back to the bootloader to flash the patched boot. But then it wouldn't boot at all. I think the first boot after install has some important processes that shouldn't be interrupted. So it's best to let that first boot happen and then shut it down ASAP.
[Google Pixel 4a Guides, News, & Discussion] Kill Face:
No Banking

I'm a noob, so I did things out of order, but I now have root and passing safety net... But...

Banking app and Google pay failing (your device is modified...) Any suggestions as to what I might be doing wrong?
[Google Pixel 4a Guides, News, & Discussion] Kill Face:
Works for me using beta update track of Magisk.

---------- Post added at 06:40 AM ---------- Previous post was at 06:37 AM ----------

Update: Google pay and Disney+ now working (not sure what changed), but one stubern banking app refusing to work (Halifax app).
[Google Pixel 4a Guides, News, & Discussion] Gentoo11:
As far as I can tell I did everything correctly and root check programs confirm that I am rooted, but I still can't delete/rename files form the root directory. It is the main reason I even bothered doing all of this. Any ideas?
[Google Pixel 4a Guides, News, & Discussion] JeepFreak:
This was working great for me until the last Magisk update and now I can't get it to pass SafetyNet. I've done the steps over and over; the same thing that has always worked in the past. I'm on Android 11 (RP1A.201005.006) and Magisk dc5e78e1 (21006). Any ideas what I should do to try to get this working again?

Thanks!
[Google Pixel 4a Guides, News, & Discussion] p1086060@nwytg.net:
If I root the pixel 4a, do I have to unroot everytime I want to install the firmware upgrades, and then root again? And would that process wipe the data every time, so that every time I want to upgrade the data will be wiped out?
[Google Pixel 4a Guides, News, & Discussion] dangerhouse:
every unlock and lock wipe data
[Google Pixel 4a Guides, News, & Discussion] p1086060@nwytg.net:
so everytime there's a minor ota upgrade, one needs to wipe data? Isn't that very bothersome? Do people do that or they just wait for major updates?
[Google Pixel 4a Guides, News, & Discussion] CSX321:
I think they meant that any time you unlock or relock the bootloader, it wipes data, which isn't really relevant to your question. You will lose root access when you install an update, but there are a couple of ways to regain it afterwards, which you can read about various places here. I usually download and flash the full firmware when there's an update, removing the -w from the flash-all script so it doesn't wipe data. You can extract boot.img from the downloaded update package, and patch it with Magisk, then flash it in fastboot mode to regain root access.
[Google Pixel 4a Guides, News, & Discussion] p1086060@nwytg.net:
Thank you. So, if understand correctly: if I root, every time I install an update I will need to do a certain procedure to regain root. But this procedure won't involve wiping the data. Does this procedure consist in reflashing the firmware? Or is that just a way of doing it? Is the procedure risky?

Does rooting the pixel 4a void the warranty?

What is the chance of permanently bricking the pixel 4a, in trying to root?
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
If your bootloader is unlocked, its impossible to hard brick this phone. You could soft brick it, but that can always be fixed.

Basically, you can't permanently brick it in this case.
[Google Pixel 4a Guides, News, & Discussion] CSX321:
Here's a post I once wrote describing how I typically install updates and reroot. There are variations possible, and I don't quite exactly do it this way now, but this would still work and should give you something to start with: https://xdaforums.com/showpost.php?p=78624634&postcount=219
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
Right now, the Magisk method on OP doesn't work. Till that is fixed, you would need to unroot and sideload upgrades. Sideload can be a) Full factory image b) Full OTA.

If it's a), I think (not tested) the script calls for wiping the data. You would need to remove that option from the script (-w) as I understand.

If it's b), Wipe /unlock boot loader doesn't happen. That's why it is preferred

Edit: I did b) without wiping

Both options, you would need to patch boot image and root
[Google Pixel 4a Guides, News, & Discussion] :
Hello, can anyone help me. I have already flashed a patched boot.img via fastboot but the Magisk app is still not showing as rooted. I am on latest Nov patch. :confused:
[Google Pixel 4a Guides, News, & Discussion] atbs84:
After having failed to root using the method described on https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/#comment I found this thread.

What happened until now:

- Got my Pixel 4a a few days ago with RP1A.201005.006 release (October)

- Applied the OTA to RP1A.201105.002 (November)

- Installed Magisk Manager (stable) and tried to flash patched_boot.img

- phone said it was corrupted, boot failed, flashing original boot.img didnt seem to work - i don't recall if i flashed both A&B slots - i just used the "fastboot flash boot patched_boot.img" command

- flash_all.bat with November release

- phone was booting up again

- found this thread

- Installed Magisk Canary and flashed patched_boot.img

- phone was booting but no root (AdAway is unable to write hosts file, cannot browse to / etc.)

It seems that some people managed to get root on the Pixel 4a. I wonder if it is even possible with the November release. Any suggestions?
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
You can't root with Magisk stable on Android 11. You need to root with Canary. After root, you may switch back to stable or stick with Canary.

---------- Post added at 09:54 PM ---------- Previous post was at 09:42 PM ----------

Uninstall Magisk manager. Download patched Magisk file from Nov update here: https://androidfilehost.com/?fid=10763459528675576680

Rename file whatever you like,. I named it rootboot.img

Boot to bootloader, fastboot

Fastboot flash boot rootboot.img

Change rootboot to whatever name of file is.

Reboot to system

You are rooted. You will need to install Magisk Manager now to use root. Cheers.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Small correction to this. What I actually did for October was download the full image, patch the stock, transfer to computer, attempted to install the full image without wipe. And when install finished it immediately started booting back into system. I, in a vain attempt to halt that and get back to the bootloader, hard-shutdown my phone and booted into bootloader to install the Magisk image. And it wouldn't boot. So that got me super-scared.

Then I downloaded the OTA and tried that. And upon completion I booted without trying to apply Magisk cause I just wanted proof it worked and I hadn't lost data. It worked, but because I booted, Google Play noticed my non-certified status. THEN I rebooted to loader, applied the patched boot.img, rebooted, passed SafetyNet but had to clear Google Play data. Thankfully Google Pay was unaffected. (I did NOT want to reset GP Services data again because that cleared my COVID tracing data.)

OK so I finally got around to November and I have to say, despite the fact that this means two entire downloads, this really is the safest upgrade path I've found so far:

Download both the full image and the OTA zip.

Extract full image, copy boot.img to phone, patch on phone with Magisk, transfer back to computer

Apply full OTA in recovery (follow Google instructions but don't reboot at the end)

Reboot to bootloader instead

Fastboot flash the patched boot.img

This path allows a safe full upgrade without any risk of booting into system before you have reapplied Magisk. Until Magisk restores support for flashing after OTA, this works for me.

Note that since root I have not actually tried accepting system OTA. I am concerned it might download the wrong one because the SafetyNet plugin is masking it as Pixel 3a.
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
Ok, if that works for you, stick with it. What I posted, works for me with the ota. When taking the ota, I restore boot image with magisk then uninstall magisk, then take ota, I get the already patched boot magisk from link I posted then followe what I previously mentioned. Less work this way, but if it doesn't work for you, stick with what does.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Questions:

- Are you using the Safetynet Magisk module?

- Do you have it configured to identify as another model such as 3a? (I want to know if the downloaded OTA is actually a correct 4a OTA under this scenario)

- Do you allow it to boot unrooted after the OTA or interrupt it in some way to force it back to the bootloader?

- At the end of it all, do Google Play and Google Pay still consider you certified?

- Do you ever have to wipe storage for any Google Play/Pay/Services etc apps to unblock anything after?

---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------

Beta channel works now too and is likely more stable than Canary.
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
Yes, and I actually was able to ota through the system update with the Safetynet module. I'm not sure if restoring boot image through Magisk is what allowed it or not. One thing I do know for sure is, if you don't remove root, the system ota update will fail.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
What's with the name changing? You already changed the name to rootboot, then you say change rootboot to whatever name of files is. You fastboot flashed rootboot, what's they next line for? Don't you just reboot after flashing?
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
I meant if you choose your own name. Flash whatever file your boot.img is called, like below then reboot.

Fastboot flash boot nameofbootfile.img
[Google Pixel 4a Guides, News, & Discussion] bjgood:
This may be a dumb question, but if I unlock the bootloader and root, then later decide not to bother with root anymore and go back to stock, will safetynet work normally or does it detect the unlocked bootloader alone?

I know people have gotten safetynet working with rooted 4a already, but I've seen how it can be a cat and mouse game whenever they update, and want to make sure I have the option to give up if it ends up being too annoying.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Unlocked bootloader definitely causes SafetyNet fail. Even if not rooted.
[Google Pixel 4a Guides, News, & Discussion] NBreunig3:
Anyone else not received the November OTA update yet? I keep checking for updates but it says I am up to date.
[Google Pixel 4a Guides, News, & Discussion] artibart:
Ok then so this might sound like another silly question. If one relock bootloader then SafetyNet will pass, correct? :confused:
[Google Pixel 4a Guides, News, & Discussion] Meth0d:
It does not show up on my phone either, still says up2date with oct patch.

Guess i will manually install the OTA...

UPDATE: After i reverted the boot.img to stock through magisk, the OTA showed up
[Google Pixel 4a Guides, News, & Discussion] trueduke80:
Actually I'm on October update, with unlock bootloader and root with Magisk Canary, how can I update to November update? If someone can explain clearly, I'm little afraid with out TWRP...
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
It might. Kind of a one way street - if you relock without full wipe there might still be things lingering in storage that block you from passing, and if you missed any before relock you might have to wipe again.
[Google Pixel 4a Guides, News, & Discussion] DB126:
Totally unsurprising and reminder to all. Do as one wishes but understand the consequences
[Google Pixel 4a Guides, News, & Discussion] Meth0d:
How is this unsurprising ?

The OP states to "ignore OTA at first", that implies that you would receive the notification and it would show up on system updates.
[Google Pixel 4a Guides, News, & Discussion] DB126:
Must be new at this. Mess with boot.img and all bets are off. That doesn't mean 'bad' things will happen. It simply reinforces that stock assurances don't apply. Regardless of what OP states.

Moving on ...
[Google Pixel 4a Guides, News, & Discussion] T0unet:
Hello,

You could do easily.

- First check the channel update in magisk. Change to beta (beta works well know for patching boot.img)

- Update the manager, update magisk by direct install, update modules if needed --> reboot

(it's better to limit risk of a bootloop)

- After reboot, open magisk manager and uninstall magisk --> Restore images.

- Know you could going to settings --> system --> advanced --> update (you will see the november update)

- Update --- (wait wait wait) and reboot (it's actually impossible to keep root by reflashing from magisk before reboot), after this you have lost root when reboot

- Download the last sunfish for pixel 4a from --> https://developers.google.com/android/images#sunfish

(don't accept any other sources about boot.img) check that the version is the same as the one you just updated.

- Extract boot.img from zip inside the zip archive -> transfert on phone (delete any old boot.img or patched on the phone, to avoid a mistake)

- In magisk manager --> install magisk --> select and patch a file, choose the boot.img.

- transfert the new makisk_patched.img on computer in adb folder for example(look the size, it must be the same as the original file)

- power off phone

- Boot into fastboot by holding Power + Vol Down

- plug phone and open adb

d:\platform-tools>fastboot flash boot magisk_patched.img
Sending 'boot_b' (65536 KB) OKAY [ 1.629s]
Writing 'boot_b' OKAY [ 0.294s]
Finished. Total time: 2.265s

d:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.044s]
Finished. Total time: 0.052s

That's all, your are re-rooted after update.
[Google Pixel 4a Guides, News, & Discussion] ibradbadtz:
My pixel 4a is bricked and corrupted

Hello Sir,

Can you tell me in detail how to unbrick it back? I flashed magisk img then it said it is corrupted. sob sob PLease kindly advise.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Decided to stick with October, since there seems to be no guaranteed method of updating. I may try once December comes out. Sure miss TWRP! Also thinking about going back to my 5T.
[Google Pixel 4a Guides, News, & Discussion] digger16309:
I'm back to my OP5.

I've been staying with A10 on my 4a waiting for some development to catch-up.

Unfortunately, my 4a took on water and the screen is filled with blue dots and splotches.

I think I'll end up with a Pixel 5 because I need water resistance in the long run.
[Google Pixel 4a Guides, News, & Discussion] Recoiled:
Have the same problem, followed step by step and now it says "Your device is corrupt. It can't be trusted and may not work properly."
[Google Pixel 4a Guides, News, & Discussion] dannyboyex:
Make sure you downloaded the factory image for the correct device. I had issues at first because i somehow got the one for the Pixel 4. Did it last night and got stuck until I realized.
[Google Pixel 4a Guides, News, & Discussion] thoughtless22:
I did this and it worked like a charm!:

Download both the full image and the OTA zip.

Extract full image, copy boot.img to phone, patch on phone with Magisk, transfer back to computer

Apply full OTA in recovery (follow Google instructions but don't reboot at the end)

Reboot to bootloader instead

Fastboot flash the patched boot.img

Just updated from Oct to NOV, debating trying the Dec haha
[Google Pixel 4a Guides, News, & Discussion] T0unet:
You could update from november to december with the same process. I just did it with no problem.
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
Glad it helped! Same instructions worked again for December update today.
[Google Pixel 4a Guides, News, & Discussion] codlike:
I'm having a bit of trouble with the December OTA.

Downloaded the OTA, ADB sideloaded it, it stopped at 94% saying it cannot read.

I did the usual, had Magisk installed, but uninstalled it before sideloading the December OTA.I have checked the OTA and its SHA256 hash is fine.

I checked my ADB drivers and there was a November update to r30.0.05, updated those and tried again, it still stopped at 94%.

Looked on the interweb and someone said try uninstalling and deleting your Android USB driver and reinstall, did that, tried again, still stopped at 94%.

The phone also boots AND says it has the December update, and i've repatched Magisk to December, and err so far seems fine ... but it still only flashed 94% of it.
[Google Pixel 4a Guides, News, & Discussion] baaatman:
The OTA was flashed 100% since the status code shown was 0.

Don't worry
[Google Pixel 4a Guides, News, & Discussion] baaatman:
Can someone please share the pathed boot image.I forgot to copy the patched image from phone to PC and I am stuck after flashing the OTA
[Google Pixel 4a Guides, News, & Discussion] arch111a:
How do you correctly update magisk on Pixel4a since patching boot.img and stuff. What are the steps ?
[Google Pixel 4a Guides, News, & Discussion] baaatman:
I was on Nov Build.Just Applied the OTA in Recovery .Root was surprisingly retained.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Just a couple comments. I was on October. OTA will update to Nov., then you need to check for update again and there will be another to Dec. Each update takes almost 20 minutes. I'm now at December! Time to patch boot with Magisk beta 21.1) and do the PC thing.

Actually decided to try not rooted for a while. Only reason I rooted was to get rid of nav bar at bottom and use custom accent. Looks like they added a few more colors, so think I can live with stock.
[Google Pixel 4a Guides, News, & Discussion] jericho246:
After following these instructions that I found on reddit, I'm stuck on the boot logo (G logo with loading bar).

Not sure what I did wrong. Really annoying that I'm most likely gonna have to wipe my data again. But it is what it is.

edit: I managed to re-flash the update without losing data, but I lost root.
[Google Pixel 4a Guides, News, & Discussion] skyguy126:
Does the modified device fingerprint interfere with receiving OTA updates through the settings menu? Is it best to update via downloading the zip from online and sideloading it?

Anyone have luck with flashing the new december update (Nov -> Dec)?

I don't see the OTA in settings and I am wondering if it is due to me changing the fingerprint of my 4a to one of the 3a.
[Google Pixel 4a Guides, News, & Discussion] mbk17:
I was having issues with flashing the Magisk boot image for December getting errors saying it was corrupted or no boot loops. Canary seemed to solve those issues on December rooted with passed SafetyNet. I am assuming using EdXposed will remove SafetyNet and the option to use GooglePay?
[Google Pixel 4a Guides, News, & Discussion] fudi6489:
Hey guys, i`m from Austria Europe and tried to root my Pixel 4a like the manual in the first post.

At first i updated my phone from Oct to Nov to Dec.

At the following steps everything work fine till the point

Reboot your device back into fastboot (see Unlock section above)

Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img'

You're now rooted!

Following fault message:

I don`t know what i am doing wrong.

The downloaded and with magisk patched version is also from Dec and has the correct size from 67mb.

Hoping for help

Cheers

Jürgen
[Google Pixel 4a Guides, News, & Discussion] jericho246:
Hello there,

You gotta specify boot_a or boot_b:

fastboot flash boot_a magisk_patched.img

and/or

fastboot flash boot_b magisk_patched.img

When you type fastboot flash boot (without _a or _b) it should do it automatically but sometimes it just doesn't. Not sure why.
[Google Pixel 4a Guides, News, & Discussion] fudi6489:
Thanks men, this process has worked.

Should the phone restart itself, if everything is fine?

At first i tried only "boot_a" but root checker said "Sorry! Root access is not probably installed on this device.

So i tried "boot_a" and "boot_b" but root checker says the same, i think the phone isn`t rooted at all.

Cheers
[Google Pixel 4a Guides, News, & Discussion] mbk17:
I was having the same issues yesterday. You need the latest platform tools for ADB and Fastboot which you can get here: https://developer.android.com/studio/releases/platform-tools
[Google Pixel 4a Guides, News, & Discussion] mbk17:
Yes the phone should restart and go to initial setup if everything is fine. As I mentioned recently in the thread mine wouldn't boot properly and had to use the Canary build for Magisk. Good luck
[Google Pixel 4a Guides, News, & Discussion] fudi6489:
Omg

I think this is getting to complicated for me.

Dont know what i should install exactly