yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] a1291762:
The partition that the update dies on gets written to logcat. I'll dig up the info.

I haven't actually been offered the Feb update yet and I only started using this phone in January, so I haven't got to go through an OTA yet. Hopefully any day now...

On my last phone, I had to restore all of boot, system and vendor due to installing TWRP. This is how I figured out that those were the affected partitions. Possibly on the Pixel the output is a little different...

If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions.

adb logcat | grep update_engine
...
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470683:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
07-01 06:52:38.470 E/update_engine(935): [0701/065238.470931:ERROR:delta_performer.cc(995)] Expected: sha256|hex = A4AD686D7BF628486668446221D0089BF5915DBC1158C83D30A06222FE7D2ACB
07-01 06:52:38.471 E/update_engine(935): [0701/065238.471002:ERROR:delta_performer.cc(998)] Calculated: sha256|hex = 4CADBE88EC1C019913A0B416EB9031840D4BA6B2287A3FC814A2B8B7F9871F7D
07-01 06:52:38.473 E/update_engine(935): [0701/065238.471072:ERROR:delta_performer.cc(1009)] Operation source (offset:size) in blocks: 0:5221,5461:405,5869:1,5873:343,6221:589
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473233:ERROR:delta_performer.cc(1191)] ValidateSourceHash(source_hash, operation, source_fd_, error) failed.
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473340:ERROR:delta_performer.cc(298)] Failed to perform BROTLI_BSDIFF operation 187, which is the operation 0 in partition "boot"
07-01 06:52:38.473 E/update_engine(935): [0701/065238.473411:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
07-01 06:52:38.739 E/SystemUpdate(15410): [Execution,NonStreamingAbApplyAction] Installation failed with error code: 20.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
I got the jan OTA on the date, but I still have not been offered the feb release. do we get notified of the release while we are rooted?
[Google Pixel 4a Guides, News, & Discussion] a1291762:
I rebooted after restoring images (to un-root for science!).

I was not offered the Feb update.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
FYI: I downloaded the full image, and stepped through the flash-all.bat file, removing the wipe parameter. It all installed fine, and kept my data, and now I am running the feb firmware ✌ I then installed the latest stable Magisc, and rebooted, and it all looks good.

Also, after I flashed it I went in to check that I was running the 5 feb firmware, and it dawned on my today was the 6th, so it would only really be logical that at best I would of been offered the new firmware yesterday at the earliest. I was obviously a little eager, but at least now I know I can manually apply the patches without loosing all my setup. i.e. do a "dirty flash" of the stock ROM.
[Google Pixel 4a Guides, News, & Discussion] T0unet:
You could update february update with the same process, the only difference is that now you could keep the stable channel on magisk as the 21.4 is Ok now. ;)
[Google Pixel 4a Guides, News, & Discussion] Dav3m45:
So I've got a question: I got this phone last fall, rooted, and have been on the November update ever since. The only reason I rooted was to enable tethering (through this process https://xdaforums.com/t/how-to-native-tethering-on-rooted-pixel-4-xl.3993405/)

So my question is will I be able to uninstall Magisk and take the updates with my build.prop edited? Or will I have to change it back? Thanks in advance, I appreciate all the work you guys do.
[Google Pixel 4a Guides, News, & Discussion] mbk17:
I just made a new patched boot image and rerooted with the Feb release, hopefully March OTA will work.
[Google Pixel 4a Guides, News, & Discussion] Coldtrain6989XD:
Didn't work for me on my 4a says failed cts profile but everything else is fine.
[Google Pixel 4a Guides, News, & Discussion] Coldtrain6989XD:
Same still didn't work for me.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Are you saying the ROM fails to flash/boot? or that you fail to pass CTS Profile / Safety net?
[Google Pixel 4a Guides, News, & Discussion] crackerjack1957:
Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Google Pixel 4a Guides, News, & Discussion] rjm12rjm12:
This did work for me also, the v.1.1.1 version. I tried a newer version and that did not work.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
The safety net fix v1.1.1 didn't work for me either.

Magisk stable 21.4

Feb A11

SELinux: Enforcing

However, I dont do any banking or play pokimon go or such on my phone, so i haven't noticed where it affects me, as yet.
[Google Pixel 4a Guides, News, & Discussion] Royalfox:
I just got today my 4a and followed this guide. Am stock rooted on latest Feb and i do pass safetynet.

I'm using universal safety fix v1.1.1 alongside magiskhide props config and its all great! Tysm ❤️
[Google Pixel 4a Guides, News, & Discussion] Zackptg5:
Just updated the guide with the following changes:

MagiskHide Props Config has been replaced with Safetynet-fix

OTA updates are no longer possible temporarily - inactive slot install has been disabled until things are figured out due to some new google updates to the ota process. You'll need to patch boot img like before instead
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Got a Magisk Manager update which I installed. Now it says Magisk has an update. Can I just hit update or should I leave it alone?
[Google Pixel 4a Guides, News, & Discussion] Zackptg5:
Direct update went fine for me but be by your PC just in case
[Google Pixel 4a Guides, News, & Discussion] Royalfox:
I can also confirm here direct update worked without a hassle am no latest SuperiorOS
[Google Pixel 4a Guides, News, & Discussion] Pixelman27:
I've had my Pixel for a few days had no trouble unlocking the bootloader but rooting has proven impossible.

I'm on Android 11(RQ1A.210205.004), and whenever I tried to flash the patched boot.img I always got stuck on the same error, which told me that the boot image was bigger than the boot partition size. Could any kind sould post the patched boot image for the latest build? I've been searching for it everywhere but I can't find it.

And thanks to everybody who has been participating in this thread, it's been incredibly helpful!
[Google Pixel 4a Guides, News, & Discussion] nss357:
Try to use mine. Just patched it yesterday, and it worked fine for me. The latest build, 11(RQ1A.210205.004).
[Google Pixel 4a Guides, News, & Discussion] Pixelman27:
It worked, thanks a lot!

It worked, thanks a lot!
[Google Pixel 4a Guides, News, & Discussion] oldseddie:
Thanks for the help. I still cannot root my Phone. It shows same error "failed....partition not found'. I have updated Majisk and retried several times with the same results. Perhaps I have an old Fastboot. Where did you get your copy?
[Google Pixel 4a Guides, News, & Discussion] Royalfox:
Get the latest from here:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 4a Guides, News, & Discussion] frank93:
so what’s the correct order to do it then, when planning an update? do we just "not take the OTA" from anywhere, but download the complete new stock firmware from google, patch the boot.img using magisk, and do a "complete update" (without a wipe) via flash-all.bat?

or will this ..

.. work? i guess i’m just hisitating because it says "OTA not possible anymore" ..

thanks in advance!
[Google Pixel 4a Guides, News, & Discussion] Zackptg5:
The OTA upgrade method isn't possible anymore (https://topjohnwu.github.io/Magisk/ota.html). To take an ota now, just take it like a normal ota on an unrooted phone, then do the patch boot img method again (repeat those steps used to initially root)
[Google Pixel 4a Guides, News, & Discussion] frank93:
okay, i guess i wasn’t sure if an official OTA (offered via system) will "work" (due to the boot image being patched at that time). you’re saying it will, right?

and after taking that OTA my device will be unrooted, and THEN i’ll patch the boot image just like the first time and reboot again?

(or in short .. switch on "automatic system updates" in developer options, take the OTA, reboot, then back to bootloader, flash the new magisk-patched-boot.img, reboot, that’s it?)

sorry for being a bit slow, i’m just panicking so i don’t brick anything. :-)
[Google Pixel 4a Guides, News, & Discussion] Zackptg5:
Yup :)
[Google Pixel 4a Guides, News, & Discussion] T0unet:
@Zackptg5, Thanks for the first post update. ;)

I think you could add the ota update tutorial when rooted.

Something like this - https://xdaforums.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/post-83968705

Only difference, no more need of the beta channel Magisk since 21.4
[Google Pixel 4a Guides, News, & Discussion] Ruttix:
Say, would taking an OTA and rooting afterwards wipe all data?
[Google Pixel 4a Guides, News, & Discussion] tcat007:
Didn't for me.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
an OTA should not wipe your data. However, I always do a backup before I do any major changes. Nprmally to catch the cases where IIIII stuffup a syep and accidenta;y trigger a wipe or put myself in a place where I have to do something that will wipe my data.

Flashing the FULL firmware will.

Unlocking your bootloader will.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
How do you do a back up without TWRP?
[Google Pixel 4a Guides, News, & Discussion] bobbarker2:
Stuck at bootlogo, help please.

I've always done the following to update:

1. Download factory image from google

2. Extract boot.img and patch using Magisk. Copy patched_boot.img to PC.

3. Disable/Uninstall all Magisk modules

4. Reboot

5. Reboot to bootloader

6. Flash factory image from google but edit flash-all.bat "fastboot -w update image-sunfish-rq2a.210305.006.zip" to "fastboot update image-sunfish-rq2a.210305.006.zip" - removing the "-w" so it doesn't wipe user data.

7. Let phone boot, then reboot to bootloader.

8. fastboot flash boot patched_boot.img

And then I have updated and achieved root. I've had this phone since launch and done it this way for every update. But this time phone will not boot after flashing patched_boot.img. I followed instructions for v22 and unhid Magisk also. I was on V22 before flashing March update too.

Anyone have similar situation or advice on why this time its not working?

During google boot animation I can adb, I've even done

adb shell

magisk --remove-modules

just in case I forgot to disable/uninstall a module and it was causing a problem but no difference.
[Google Pixel 4a Guides, News, & Discussion] frank93:
wow - i was in the same situation! with android 10 i always/usually updated more or less exactly like this - using the complete firmware, not even disabling magisk, but instead editing flash-all.bat: removing the wipe parameter at the end, and flashing the patched boot.img directly afterwards (within the batch/script). it worked just perfectly UNTIL android 11 came along, when i started to have the same results just like you describe: stuck at the google-"g"-logo, and back to bootloader. no matter what i tried, even with disabling magisk and/or trying to reboot first before patching boot.img .. like, a "clean" stock firmware upgrade, same result. and just the same with an ota-sideload. flashing back the "current" firmware at that point always got me back running the device again. but no upgrade. i ASSUME i ****ed something up while updating an earlier version, flashing something to both slots instead of (the correct) one, but that’s just a wild guess, can’t really confirm.

(until today i’ve got no idea what caused this, and didn’t find a workaround. i ended up getting a new device (!), updating to android 11 there and installing everything from my backup & from scratch until i was happy. sold my old device for "nearly as new", so my investment was €40 and a lot of time "only". :) before i sold it, i finally was able to update that older device to android 11 using the built-in "reset phone"-feature (wiping everything), so .. still not sure what caused all of this, but it doesn’t matter too much anymore.)

not much help here, i imagine. but sympathy for your case, at least, for what it’s worth ... :)
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Notice I used the tern "backup" and not nandroid. ;)

I backup my Calls, SMS, Apps & their Data, and various exports of my settings/config. I also have a folder on my PC of all the Magisk modules I have installed and apps not on the playstore and therefore not linked to my PlayStore account. Then I can flash the original firmware and restore the "backups".
[Google Pixel 4a Guides, News, & Discussion] Typhus_:
Your procedure is exactly the procedure I always do, nothing wrong there.

Now, you may have been facing a stupid bug that I've already identified earlier upon my tests. I did noticed it since usually I'm always with the phone connected to my PC with Android Studio open after applying an OTA and rooting it again, so I catch the logcats.

Try to run this at boot as soon as boot animation starts and you're able to "talk" through adb:

pm grant com.android.systemui android.permission.READ_CONTACTS

See if that helps.

Yes, I know..."WTF!?" right?
[Google Pixel 4a Guides, News, & Discussion] jackbob1234:
hello i cannot pass safetynet using the Safetynet-fix module. anyone managed to pass safetynet? also is the magisk app messing up anyones systems as in when you open it, it never opens and then you cant open any other app.
[Google Pixel 4a Guides, News, & Discussion] tcat007:
I'm still on February with no issues. Magisk is at rev 22.0 which eliminated the manager app. Universal Safetynet Fix 1.1.1 works for me.
[Google Pixel 4a Guides, News, & Discussion] Mr.Demous:
Did you find a fix for this?

I also tried this and it didn't help. Still stuck on G logo after flashing magisk patched image
[Google Pixel 4a Guides, News, & Discussion] Typhus_:
Which Magisk version did you use to patch the boot.img?

Did you try to use the one I've shared HERE?

One other thing, one of your previous installed modules could be causing issues. Have you tried to remove them all, or disable them, before trying to boot?
[Google Pixel 4a Guides, News, & Discussion] Mr.Demous:
I tried Magisk 22.0 and the latest canary (22004), both of them didn't work. I also removed all previous modules from magisk. Don't know what else to try.
[Google Pixel 4a Guides, News, & Discussion] Typhus_:
Weird.

You need to capture a logcat and check what could be wrong.

Having the Magisk patched boot.img running, while booting up connect your device to your PC and run:

adb logcat > log.txt

Look for "FATAL" on the log.

You could also force boot into safe mode. While seeing the boot animation, keep pressing the volume down button. That will force your device to boot into safe mode. Magisk will detect that mode and it will disable all modules (if any installed).

If nothing works, you can just flash latest stock through fastboot. Delete the "-w" flag on the update command inside the flash-all.bat to retain your data.

If not even that does the tick, then you have no choice but to completely wipe your storage. Use flash-all.bat keeping the "-w" flag.

Cheers!
[Google Pixel 4a Guides, News, & Discussion] bobbarker2:
Thanks for the advice. If it happens to me again I'll try it but I'm not sure that will fix it as I was watching the log cats as well and was watching all critical system processes die and try and start again only to die again.

I think some module I was using, maybe audio related, changed something in my system - which of course defeats the purpose of Magisk.

I got impatient and just did a factory reset. All set now. I was a bit disappointed by Swift backup's restore capabilities. Lots of apps were broken and required clearing of data or reinstall. I wish titanium backup developers would make the project active again.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Magisk has a shell command to disable all modules in case of boot-loops caused by a module.

adb wait-for-device shell magisk --remove-modules

from https://www.didgeridoohan.com/magisk/Magisk by @Didgeridoohan
[Google Pixel 4a Guides, News, & Discussion] tohypnos:
I had failed getting root after updating to 11. Many trials failed while CRC of my own patched img does match with an uploaded img on the Internet.

I finally came up with a solution and now get Magisk work. I hope this helps people who failed applying Magisk with bootloops.

1. Prepare patched boot img as well as the PC.

2. Push the power button and tap Power off longer. Then, click ok to reboot to safe mode.

3. Before rebooting, push vol- and go into fastboot.

4. Flash patched boot img: fastboot flash boot xxx.img and fastboot continue.

5. Now the device starts with the safe mode disabling all Magisk modules, some of which was actually causing bootloops.

6. Reboot normally. Then, the phone starts still all Magisk modules inactive.

7. Remove or update outdated modules and enjoy root again;)

This procedure is based on (or exactly the same) with a safe mode solution which you can find the link above but I couldn't make it before because I was fully rebooting before applying a patched img.

In case you failed something, just flash-all (Note: don't forget to remove -w) and try from the beginning.
[Google Pixel 4a Guides, News, & Discussion] os_man:
We already know that, nothings is different, you guys are funny.
[Google Pixel 4a Guides, News, & Discussion] Wulfegang:
Will leaving the fingerprint as 4a and failing ctsProfile give me any problems later on? Even though ctsProfile says false my Google Pay seems to still work and unsure what else it may affect. Me being stubborn about having my phone identified in things like backing it up to Google makes me not want to change it to something like the Pixel 3a.
[Google Pixel 4a Guides, News, & Discussion] Jabotical:
The problem I ran into was that Netflix disappeared until I picked the 3a fingerprint. And supposedly things like banking apps/paying via NFS can have issues, though I didn't actually confirm that.
[Google Pixel 4a Guides, News, & Discussion] bcote311:
Thanks so much for this guide! Worked perfectly!
[Google Pixel 4a Guides, News, & Discussion] JeepFreak:
Soooo... I've enabled unlocking in developer tools, but when I reboot into fastboot mode I can't get the 'fastboot flashing unlock' code to work. It responds with 'FAILED (remote: Unrecognized command flashing unlock)'.

No, I'm not including the quotes. =)

'fastboot devices' does give me the right response with the phone's serial number. 'fastboot getvar all' seems to give me the right response too and 'fastboot reboot' reboots the phone.

Is my bootloader locked?? I got my 4a directly from Google.

I'm using Ubuntu 20.04 and my package manager says I've got the current version of fastboot, but here's the response of 'fastboot --version': fastboot version 1:8.1.0+r23-5ubuntu2

Any help is appreciated! I can't find much info out there that I haven't tried.
[Google Pixel 4a Guides, News, & Discussion] Displax:
Very old. Use the latest platform-tools package: https://developer.android.com/studio/releases/platform-tools
[Google Pixel 4a Guides, News, & Discussion] nogods:
I downloaded and installed the latest magisk props. Then I used the 4a fingerprint. So far no problem with my bank apps, no problem with google pay, and no problem with netflix.
[Google Pixel 4a Guides, News, & Discussion] JeepFreak:
Thanks. That did the trick. I should have just downloaded the latest instead of trusting the repos.
[Google Pixel 4a Guides, News, & Discussion] mishka1984:
I hope I haven't screwed myself

I decided to buy a Pixel 4a so that I could have a phone to do development on that had all the blobs available as well as documentation so that I could focus more energy on learning Android internals without the fight that harvesting them from OEM distributions etc. I decided to get it financed but as I was going through the process I realized that their underwriter was essentially going to send me a credit card good only at the google store that had 0% interest rate on phone purchases and some ridiculously high rate on other things in the google store. So I backed up and chose the option to buy a line from Verizon so they would finance it.I still ordered and received the phone from google and I bought my insurance directly from google as well. The phone was shipped and arrived. I was stoked. I had just completed a `repo sync` on the AOSP source trees.... So I turn on the shiny new gadget and go through the setup so I could enable developer options... and mother f*ck3rrr!!!%^#!$

Under Dev Options I see it: "OEM unlocking Unavailable on carrier-locked devices"

I'm about to go get a cable so I can look at fastboot. Sorry for venting. Sooooo frustrated at this. Wish me luck!
[Google Pixel 4a Guides, News, & Discussion] quangtran1:
Sorry for your trouble, but this is why I don't buy from Verizon, or a Verizon-specific device even from the OEM. I buy / manage 300+ phones for the enterprise. I know what Verizon does as far as locking bootloader. I've been a loyal Verizon customer for 28 years now, when it just started to buy out small cell providers and I enjoy the red carpet treatment from them, but I don't buy phones from them. I stopped getting phones from Verizon since the Samsung Note 4. Instead, I'd go to Best Buy and get the unlocked version. BB gives more perks anyway, although VZW does give me a $100 credit for every new line I open when I buy that phone at the corporate store. However, the inability to unlock bootloader isn't worth $100. I'm confused about your math on the Google Card issue though. Zero percent interest is zero percent interest, whether you used the Google offer or you pay the monthly installments to Verizon.
[Google Pixel 4a Guides, News, & Discussion] DB126:
Nope - in absence of a hack (which there are very few) bootloader can not be unlocked on a Verizon branded handset. Return and purchase fully unlocked varient direct from Google or retail; lots of good financing options available. I use Verizon as a carrier but never purchase carrier branded devices.
[Google Pixel 4a Guides, News, & Discussion] Steve One:
Oh damn, I bought mine from Verizon. So I'm pretty much screwed from unlocking and rooting?
[Google Pixel 4a Guides, News, & Discussion] mishka1984:
I'm going to have to. Either that or I'll just have to suck it up and focus on These low end Motorolas that I have. I honestly know better than to continue doing dev work on my daily driver. I've burned myself more than once for sure.

I did have one of those ridiculous false hope moments working with fastboot when I was able to sideload the global Google ROM onto it but it didn't pan out.
[Google Pixel 4a Guides, News, & Discussion] Steve One:
Does anyone know if Verizon updates pixels when google releases it or is it months later?
[Google Pixel 4a Guides, News, & Discussion] mishka1984:
They claim that the pushes for updates are going to be coming directly from google.
[Google Pixel 4a Guides, News, & Discussion] quangtran1:
Google handles monthly updates itself.

View attachment 5093019
[Google Pixel 4a Guides, News, & Discussion] Steve One:
Thank goodness for that!
[Google Pixel 4a Guides, News, & Discussion] fronto:
The standard Magisk select and patch file root method posted here worked great on Android 10.

However, tried it twice already and cannot get

Android 11

((RP1A.200720.011) to boot with patched boot image. Has anyone had success with this yet?