So in the end, I followed a long XDA thread and now I got everything google pay related in order. SafetyNet pass + certified device.
You will need:
- Magisk with:
- Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
- Now the part that is very important to follow otherwise it will not work :
. Put your phone in Airplane mode
. Clear all data from:
- Google Play
- Google Pay
- Google Play Service: remember, clear ALL data, not just cache even for this one
- Toggle Airplane mode off
Everything should be in order.
----------------- under this line is outdated content -----------------
Alright, so I finally got google Pay to work:
- download Riru module in Magisk
- download and install Riru’s universal SafetyNet’s fix 2.1.2 in Magisk
Enable both modules, restart, enjoy
EDIT: I’m really sorry but I have spoken too fast; although I can pass SafetyNet and add credit cards, NFC paiements attempts actually do… nothing.
Will investigate further…
It’s a really interesting option, but I will wait for the moment the the stockroom is available. So when something went wrong I can reflash te device.
Could you share stock boot_a.img and boot_b.img for A.091 version?
I accidentally flashed boot.img meant for A.067 version and i am stuck with broken wifi
Sure, here you go: Fairphone 4 stock boot images.
boot_a.img is patch level September and boot_b.img November, not sure this will get you WiFi back though. It didn’t work for me when i booted them from RAM, so you probably will still have to enable it manually from the command line. But maybe things are different if you actually flash them.
I must really make this clear, at no point did I flash a boot.img to my device, so you are entering uncharted territory here.
Thank you, I flashed these and it works now
Great news! There’s hope if something goes wrong.
Did you have to mess with kernel parameters or did wifi just work™?
Great! I tried rooting my new FP4 the way Hirnsushi said and it worked! Thanks so much! Was a bit worried some things stopped working (WiFi, SD card) after the first reboot
Now that Magisk is working, has anyone tried installing Xposed (LSposed module) yet?
I’m reluctant to be the first to try, when there is no easy way yet to unbrick if necessary…
I am not going to try it unless there is an unbrick method. I really like an rooted device I always did it with all my mobile phones but I have to be patient…
I am stuck and can not move forward
After point 3: adb reboot bootloader I was in bootloader mode.
After that I entered the command “fastboot boot /path/to/patched_boot.img” got the message:
“< waiting for device >”
Here I did not know what to select on the smartphone with the volume keys?
You need to make sure your computer can see your phone by “fastboot devices” command
If it doesnt, then u may need to install adb/fastboot drivers
@hirnsushi it just worked™ without additional tinkering
Ok, my phone is shown as “Android” in the device manager at this moment. But there is no driver installed. Where can I download the driver for it?
Download “ADB composite driver” (quick search on google should do), manually install driver from device manager using downloaded driver, choose “Android ADB Interface” and device should be visible.
(also you might have to tell your device to trust your computer, a popup should appear when plugging cable)
Ok thanks, already again a piece further.
But already the next problem…
C:\ADB>fastboot boot boot1.img
Sending ‘boot.img’ (98304 KB) OKAY [ 2.165s]
Booting FAILED (remote: ‘Fastboot boot command is not available in locked device’)
fastboot: error: Command failed
Bootloader is already unlocked…
You did enable USB debogging + toggled OEM Unlock on in developper settings right ?
Edit: my bad, didn’t read carefully thought you were trying to unlock bootloader. Message seems to say bootloader is not unlocked. Do you get the warning about having an unlocked bootlaoder when starting device ?
Please check the output of
$ fastboot getvar unlocked
Edit: On a second thought did you maybe accidentally boot into fastbootd instead of fastboot? Make sure you use
$ adb reboot bootloader not
$ adb reboot fastboot.
Yes both are enabled in Developer Options.
C:\ADB>fastboot getvar unlocked
Finished. Total time: 0.003s
Yep, so there’s your problem, the bootloader isn’t unlocked.
$ fastboot flashing unlock again, but remember this will wipe your phone.
Ok now it worked, thanks 1000x
I forgot that you also have to unlock the bootloader with the fastboot command.
Do I see that correctly the phone only remains in the root state until I restart it?
For me actually the ideal option, because I only need root to restore my apps with Titanium Backup. After that no more.
That’s correct. If you don’t install Magisk again once you booted the patched boot.img a reboot will bring you back to where you where before.
I’d still be careful though, make sure you can make a successful adb connection to your phone before rebooting. If you get stranded in a bootloop because Titanium Backup messed something up, there won’t be a pop-up asking you to trust your PC.
Maybe someone else already went through a Titanium Backup restore and knows how well it works. I personally always set up everything from scratch, have been burned enough times in the past
This. Ahah experience talking. I never ever use Titanium backup. I like my device cleanly set up