[Stock/Rooted Boot Images] Pixel 4a [NOV 02]

Zlatty

Senior Member
Oct 7, 2011
607
54
48
SFBA
www.zlatkounger.com
got her done, however, i am still not passing ctsProfile. any ideas? running 10 (QD4A.200805.003)
I got nothing for cts
In Magisk, install the MagiskHide Props Config module;

Execute command 'su -c props' using a terminal app on the phone;

Choose 'Force BASIC key attestation' option from menu;

Choose from fingerprints list' -> 'Google', 'Google Pixel 3a', although a Nexus fingerprint will likely work as well. View attachment 5086411View attachment 5086413View attachment 5086415
Wonderful. Google pay works on my rooted 4a. Now to do this with my other magisk phones. Thank you!
 
  • Like
Reactions: ToHellWithGA

Zlatty

Senior Member
Oct 7, 2011
607
54
48
SFBA
www.zlatkounger.com
Thanks guys, got the steps added to the OP, should hopefully be good now :good:
You do not need to do:
Code:
Choose from fingerprints list' -> 'Google', 'Google Pixel 3a', although a Nexus fingerprint will likely work as well
When you choose a fingerprint it defaults to Pixel 4a, and all you have to do is confirm and then reboot. Source: just did this :cool:
 

aohus

Senior Member
Sep 10, 2010
411
65
0
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.

Anyone know if it is possible to sideload magisk as a zip?
i get same issue.

edit: i was able to resolve by modifying to: fastboot flash boot_a desiredbootimage.img
 
Last edited:
  • Like
Reactions: HolyAngel

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
You do not need to do:
Code:
Choose from fingerprints list' -> 'Google', 'Google Pixel 3a', although a Nexus fingerprint will likely work as well
When you choose a fingerprint it defaults to Pixel 4a, and all you have to do is confirm and then reboot. Source: just did this :cool:
i get same issue.

edit: i was able to resolve by modifying to: fastboot flash boot_a desiredbootimage.img
Thanks! Got the OP updated :good:
 

nogods

Senior Member
Dec 10, 2014
70
9
0
I tried two terminalo apps - typing in 'su -c props' (without the quotes) then hiting the return key does nothing - what am i missing?
 

DesertVelo

Senior Member
Jan 21, 2011
392
162
73
nevermid - the third time woirked....but ctsProfile still shows false
I had the same issue. Use the instructions in post #61 and select Pixel 3a from the list of devices. Only when using 3a, I was able to pass. Good luck!

Sent from the singletrack...
 

nogods

Senior Member
Dec 10, 2014
70
9
0
I had the same issue. Use the instructions in post #61 and select Pixel 3a from the list of devices. Only when using 3a, I was able to pass. Good luck!

Sent from the singletrack...
Thank you for that clarification.

I selected the 4a fingerprint because it was on the list of fingerprints. Before I re-try using the 3a fingerprint I wonder if anyone can tell us the impact if any of picking a fingerprint different from the actual phone and why the 4a fingerprint doesn't work.
 

mustbevick

Senior Member
Nov 6, 2010
149
32
48
you have to go under Magisk Manager and might have to turn on and off MagiskHide / reboot and then set the fingerprint. Took a few times but it finally worked. Good luck
 

nogods

Senior Member
Dec 10, 2014
70
9
0
ok - here is how i got ctsProfile to true after my first attempt picking the pixel 4a fingerprint:

1. under Magisk ->> Settings I restored Magisk Manager with the original package name.

2. restarted my phone

3. Under Magisk ->> Settings I again hid Magisk Manager.

4. The I ran the su -c props command in a terminal emulator - it responded that I had a 4a Pixel fingerprint - I choose to keep it and chose the reboot option

5. after the reboot ctsProfile now shows True.

BTW - even before doing that I was able to signup for an add a card to google pay - i had never used google pay on any phone before, so I'm wondering if the "false" report for ctsProfile before i went through these steps was incorrect.
 

insink71

Senior Member
Nov 9, 2010
610
251
0
Greenville, SC
teamblueridge.org
So there are two hides in Magisk Mgr settings.. repackage as another name.. then an additional toggle a lil further down.. I tried both.. still no love. Maybe I'll try nexus 5 -> Pixel 3a -> Pixel 4a migration and see if I get a 'true' hit.
Another thing I've noticed is the bootloader message comes up on every boot since unlocking bootloader/rooting. Is that fairly common? If I get cts to true will it go back to quick restart? Now that I'm thinking, do I need to relock the bootloader to get cts = true? Hehe.
On a third note, did anyone else notice a Google library deinstalling itself after/around root? Attached screenshot, second from the bottom. Could this have anything possibly to do with the ctsProfile = false?
 
Last edited:

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
Another thing I've noticed is the bootloader message comes up on every boot since unlocking bootloader/rooting. Is that fairly common? If I get cts to true will it go back to quick restart? Now that I'm thinking, do I need to relock the bootloader to get cts = true? Hehe.
This is totally normal. DO NOT RELOCK BOOTLOADER ON MODIFIED DEVICE. You'll softbrick if you do and it'll be hard to flash the factory images. Just stay unlocked if you need root/custom stuff. If you don't then reflash factory images and then relock and can ignore xda. Usually someone comes along and mods the bootloader to remove that text but it doesn't matter, doesn't hurt anything.
 

aohus

Senior Member
Sep 10, 2010
411
65
0
quick heads up.

I am on Verizon but installed the global version of the factory images, because i thought i had bought global version of the Pixel 4a. Lo and behold the version i have is for verizon, so make sure that you select the right factory images.
@HolyAngel if you can remodify the steps and change it back to 'fastboot flash boot desiredrecovery.img' that would be best.

The issue was that I flashed the wrong factory images...
 
Last edited:

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
quick heads up.

I am on Verizon but installed the global version of the factory images, because i thought i had bought global version of the Pixel 4a. Lo and behold the version i have is for verizon, so make sure that you select the right factory images.
@HolyAngel if you can remodify the steps and change it back to 'fastboot flash boot desiredrecovery.img' that would be best.

The issue was that I flashed the wrong factory images...
Ah fun times.. I updated the OP and separated out the 10 and 11beta flashing since some of the beta people reported they HAD to do boot_a to get it to flash properly on there. Thanks for the heads up :good: