yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
First it seems my old habyt from Samsung times let me do things.

Thanks a lot. I had a long research and found ways to solve the problem.

I downloaded a lineage boot.img from some strange website, booted into recovery anf flashed lineageos.

But at all I was not able to install root on phone. One problem is that on every sidte they speak about a boot.img you need, but the download from https://download.lineageos.org/redfin do not contain a boot.img. If I read pages they every time refer to stop android, but I use lineageos and no Stock android. Could someone tell me how I get a boot.img from lineageOS without downloading it from some random Blogs?

On TWRP times it was easy boot it, flash the lineageos than Magisk.zip -> every things work.

If you try to flash first lineageos.zip and then magisk.zip from lineageos recovery (adb sideload .. ) it appears like it works but after reboot I end back in fastboot.

So it seems I have to get a boot.img from lineageos somehow. Could someon help me here?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
boot.img file is in the rom files you linked.

The format is different

First you have to open the zip file and extract the payload.bin

and then you'd have to use a program like payload dumper to extract the various images from it.

View attachment 5737445
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well, you CAN still use TWRP on PIxels...you just can't install it.

The easiest way to do this would be as such:

Copy the LineageOS zip and the Magisk APK to your phone

Reboot to bootloader

Boot (do not flash) TWRP: fastboot boot <TWRP image>

Do not install TWRP!

Install LineageOS through TWRP

Install Magisk through TWRP

Reboot to system

This method can be used to root the factory firmware as well.
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
Good to know. Thank badabing2003

@V0latyle That do not work here. I only get the magisk startscreen.

ADB works but If I open adb shell and

twrp install magisk.zip I get the erro that twrp not run.

I tested magisk 3.6 and magisk 3.7
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
There is no "Magisk.zip". You'd install the APK directly through TWRP.

Also, the current version of Magisk is 25.2. Make sure you're using the official source for Magisk. There are a lot of "copycats" out there that are potentially unsafe.
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
Yes I know. But the Magisk apk has an extrafeature included. If you rename the APK to Zip it cloud patch your system directly from TWRP.

Installation

The Magic Mask for Android

topjohnwu.github.io

It seems this way is deprecated.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's no longer necessary. TWRP is now able to install APKs.
[Google Pixel 5 Guides, News, & Discussion] mightyvenom:
Hello, I am facing an issue with my Pixel 5 running latest stable build 13 and TP1A.221105.002 and rooted with Magisk 25.2 (zygisk + denylist enabled). I am also running USF 2.3.1-V2.0 Displax mod.

The issue I have is that I am stuck on July Google Play System Update. If I go ahead and check for updates the system prompts to install a 650kb update. After reboot, it prompts for another ~56mb update BUT when I try to install that it immediately reboots (without prompt or warning). So it refuses to install the main update, my guess is that I am missing something / doing something wrong with the whole Magisk process - and I can't figure out what.

I need to also mention that I pass basic safetynet attestation. Google play store is showing my device as 'certified'.

Can anyone please help me with this issue?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
I'm not sure if the issue is related to that, can you check at Google and see if your device is detected as Pixel 5 or not.

USF spoofs your device to GSM to pass safetynet.

Have you tried clearing data for Google Play services and Google Play store?
[Google Pixel 5 Guides, News, & Discussion] mightyvenom:
I think it is related to the whole root process since everything else is stock.

I am not sure what you mean by 'check at Google if your device is detected as Pixel 5', I have attached the regulatory info from my settings. Can you please tell me what exactly do I need to check?

And yes, I have already cleared data for both play store and play services and rebooted afterwards.

I am thinking about temporarily revert to stock boot.img and remove root just to see if the play system update goes through...and then re-do the whole magisk process again. What do you think?

Thank you!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I wouldn't worry about the Play system update unless it's causing you problems. I don't know if reverting to the stock boot image will help; Play Services is not part of the kernel so I doubt it. Your Play Store version is the same as mine; I'm on the October Play system update (there doesn't appear to be a November update yet).
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Go to https://myaccount.google.com/ and check device activity, or check your backups if you backup to Google, see if your device is identified correctly.

I have seen many reports that some devices are identified differently (not the same for everyone)

It's possible that, Google thinks you need an update because it is proposing an update for the device its detecting rather than your correct device.

If this does not happen to be the case, then I don't know why you're getting those popups.

It does not hurt trying with stock.
[Google Pixel 5 Guides, News, & Discussion] mightyvenom:
It seems that my phone is recognized correctly (see attachment). So all there's left to do is uninstall magisk and revert to stock boot.img and retry, but I am afraid I will break something in the process - forcing me to factory reset in the end.

Or perhaps I will wait for the next December OTA update and retry then.

Thank you for your help!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you open Magisk, tap Uninstall, then Complete Uninstall, it should restore the unpatched boot image for you. You won't break anything by doing this. I don't think it will help with your Play System issue but I could be wrong.

To re-root, you'll have to flash the patched boot image again with a PC.
[Google Pixel 5 Guides, News, & Discussion] mightyvenom:
Thanks, I will follow this guide.

Will this method keep my magisk settings after I re-root (deny list)? What about the 2 modules I have installed, do I need to disable them before proceeding?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Not sure, and no. Removing Magisk means there won't be anything to load the modules so you don't have to do anything with them.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Uninstalling Magisk would restore the boot partition, the system will not be rooted and hence it can no longer access /data/adb/magisk

but /data/adb/magisk is not removed, it remains on your file system.

Next time you install Magisk, all setttings / modules will be loaded from there again, so no need to worry about it.
[Google Pixel 5 Guides, News, & Discussion] mightyvenom:
Ok so I have a positive update in case anybody is wondering or facing the same issue.

After uninstalling Magisk from the app (complete uninstall) and reboot I have managed to update my Google Play System update to October 2022. So the presence of Magisk / USNF definitely was the culprit. Maybe this is a bug that will be solved in the next version of Magisk, hopefully.

I am curious to see if this issue will occur again on the next (November) play system update. I will update this post once the update is rolling out.

Thanks everyone for your help!
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Good job.

You might want to post it in this thread, I suspect it has more to do with SafteyNet Fix than Magisk.

People there should be able to tell you if its due to it or not.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
So I flashed the UPP1 Android 14 Developer Preview...only complaint in my few minutes of playing with it is that Zygisk does not seem to work. Not sure why.
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Hello,

On a Pixel 5 I have succesfully run all the steps until the OTA update step (I prefer Android 11 and don't need to update).

Then I enabled Zygisk and deny list for all sub components of "google play".

Also installed the safety-net fix module.

In the YASNAC app my phone passes both safetynet checks.

...but I still cannot see Revolut banking app in the Play store. If I go to the app page from the "not installed" menu it says that the Revolut app is unavailable for my device :(
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Did you read the SafetyNet/Play Integrity section in the OP?

Refer to this thread, specifically:

If you go to Play Store > Settings > About > Play Protect certification, does it show "certified"?
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
No, it says that it's not certified :(

But it's weird that I can see/install other banking apps, like Wise, or even Google Wallet.

So there is no way around this? I have to unroot if I want to use Revolut?

ps: I also installed the Integrity api checker app, and fails device & strong integrity.

And run YASNAC again and now it only passes first safetynet check, and I swear it passed both checks before. The only thing I did between these 2 runs was a reboot

ps2: did some more testing, and apparently both "device" and "basic" checks pass after restart, but some time after that, "device" check starts to fail

ps3: not sure if it's related, but after android starts i see a notification with "x google enrollment is running in the background" for like 3 seconds
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
If I install OTA, can I downgrade to Android 11 later if I don't like it or it is not possible anymore?
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
An update- I installed this mod https://github.com/Displax/safetynet-fix/releases

instead of the "official" 2.4 and now both safety checks pass all the time in YASNAC, and both device & basic check pass in the other app all the time.

..but g play still shows that the device is not certified, and still can not see Revolut in play store when I search for it.

Anyone managed to get Revolut in play store on rooted Pixel 5 ? Could it be that Revolut requires the 3rd type of check to pass, the one that is hardware-backed?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
AFAIK there is nothing preventing rollback on the Pixel 5. However I doubt your issue with Play Store certification has anything to do with Android version.

Wipe data for Play Store and restart.

For further support regarding Play Integrity please ask your questions in this thread. Be sure to specify what other mods you're using, if any
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Thanks, that kind of worked, Google play shows as "certified" now.

But Revolut still unavailable. I guess this confirms that Revolut is the only app in the world using the hardware-backed check :)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No. Play Store does not require specific integrity labels for apps. I suspect something else is wrong.

When did the app last work? It might be because you're still on Android 11. It's available for me...

View attachment 5865619
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Today I did a Revolut search again on it again and now it shows up! very weird..

I did not use it on this phone before. I have another Pixel 5, non-rooted, that I use daily and has Revolut installed on it.

The rooted phone I got as a back-up phone after the other one dies. I like Pixel 5 because its the only small phone not made of glass and has enough memory and good feature.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
@ankutsa Were you able to get Revolut working on your device?
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Yes, it seems to work with https://github.com/Displax/safetynet-fix/releases

and by adding Revolut app to deny list in magisk.
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
for the record:

I solved my Problem installing magisk on my Pixel 5.

After Installing Lineageos or any new Update (I still stick on 19.1)

OTA Update Lineageos

I have to reboot to lineageos recovery

Activate adb sideload

download Magisk APK to desktop (If I not already have a copy)

rename it from .APK to .ZIP

adb sideload 'PathTo/Magisk.zip'

reboot phone
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This thread has nothing to do with LineageOS.
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
Sorry, I was not aware that we should not mention this OS in this thread. But I'm not good enough in this subject to be able to say that this behavior to getting root works on all kind of Android OS.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It doesn't. You can only flash Magisk in custom recoveries such as TWRP or LOS Recovery. It won't work with the stock recovery, and all of us who are using the stock OS are just patching the boot image.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I updated to the UPB1 beta, rooted with Magisk 26.1. A few minor bugs that seem mostly related to display drawing.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

there is still no update from google ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What do you mean?

The April update is and has been available.

View attachment 5897177

OTA updates don't always work on rooted devices.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
He probably needs to switch to English to see the update, lots of reports about that.
[Google Pixel 5 Guides, News, & Discussion] Regys:
not for me.
[Google Pixel 5 Guides, News, & Discussion] Regys:
indeed, it is necessary to change the language, but why ?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Perhaps an oversight by Google, perhaps not, only they would know.
[Google Pixel 5 Guides, News, & Discussion] Regys:
I have to take this one ?

hash: e85b956b9d7e08e23b823e8d05c6a43a6c10e3f75c7d746e42c36d35a968703a
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Switch your language to English

View attachment 5897813

I confirmed that the March and April updates are not appearing for other languages.

French:

View attachment 5897815

German:

View attachment 5897817

Spanish:

View attachment 5897819

English is up to date:

View attachment 5897821
[Google Pixel 5 Guides, News, & Discussion] Regys:
Ok, i see,

This is correct for me ? e85b956b9d7e08e23b823e8d05c6a43a6c10e3f75c7d746e42c36d35a968703a
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Just update to April

The checksum is there for you to verify the integrity of the file after you download it, if you so desire
[Google Pixel 5 Guides, News, & Discussion] Regys:
What I mean is, is it the stock one ?

I live in europe
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you don't see your carrier/network mentioned in the build name, just use the global one. Since the T-Mobile build is US only, and Telus is Canada only, you wouldn't use those.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Nice, thanks :)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
How has the August update been working for everyone? Chrome seems to be a bit less responsive and the touchscreen seems to sometimes ignore touches.

Could also be my giant hands and smudgy screen...
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Anyone else having a lot of Bluetooth issues with Pixel 5 ?

The most annoying is not remembering some devices after a disconnect. I have to keeping re-pairing them.

Another issue is not re-connecting to some BT devices (eg. Radiacode) not always working and requiring a reboot to be able to reconnect :(
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Haven't noticed that with mine. The Bluetooth problems I do have are not with the phone; my car's head unit frequently forgets pairings, and my Skullcandy headphones sometimes spontaneously disconnect and won't reconnect until a power cycle. I have zero problems with other Bluetooth devices though.
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
Same here, it doesn't happen with all devices. But the ones that do this work fine with other phones.

What Android version you have? Mine in 11
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I always stay updated, I'm currently on the August '23 update. Why are you so far out of date?
[Google Pixel 5 Guides, News, & Discussion] ankutsa:
because Google usually slows down old phones in subsequent Android versions.

You are not noticing more lag compared to Android 11, or less battery ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No. You're thinking of Apple. Google does not implement forced obsolescence. I used my Pixel 2 for nearly 4 years until I replaced it with my Pixel 5, which I'm still using. I don't game or load my phones up with apps so I never noticed any appreciable performance penalty; I only upgraded because I wanted a 5g phone. I'm still using my Pixel 5 and have zero intentions of upgrading; I had the battery replaced recently which has restored battery life to like new.

Yes, it is true that Pixels only get regular updates to a certain point, but this is true of most smartphones on the market, and with the advent of Treble compliant devices, it's possible to continue performing our own updates.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

The last version android, android 14 is work for root ?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Yes
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
Hi

Which Magisk version do I need to root A14 (patch boot.img)?

Currently I use 25.2 with BCR call recorder, busyBox and Systemless Host modules.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
the latest 26.x
[Google Pixel 5 Guides, News, & Discussion] yurisan:
hello again :) a i'm in the process of flashing factory images again and installing magisk - i will probably follow the instructions from the OP but wanted to know if you were able to update the info on https://topjohnwu.github.io/Magisk/install.html or is it sitll outdated ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Only contributors to Magisk can update the Magisk documents. I am not one of them. The installation guide was updated a few months ago and as far as I'm aware is current. The method for rooting the Pixel 5 has never changed.
[Google Pixel 5 Guides, News, & Discussion] yurisan:
thanks for a quick answer
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Has anyone else had their phone arbitrarily reboot itself overnight and lose root? I was already on the October update so there shouldn't have been a need to update the boot image
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
I can think of one hypothetical scenario that this potentially could happen, but the stars have to be perfectly aligned for it to happen, and it's only a theory.

So before that, do you know if the slot was switched?

If you switch slots and reboot, do you get back to October rooted?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I only update with the factory image, and I always flash it to both slots. I've been running on slot A and have never switched. I found out while trying to use tap to pay at the Costco gas station yesterday, and the first thing I did when I got home was re-root by live booting the patched October boot image, so I didn't do any investigating. Build number didn't change although I doubt it would if just the boot image was updated

What's your theory?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
if you didn't do anything since the OTA update, you should be able to boot to the other slot and it should be rooted and on October.

If that is the case, I'll talk about the theory, because just like I said it is a theory and it might come out as far fetched.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I'm not sure it was an OTA though. Woke up one morning and had to use my pattern to unlock: "Pattern required after device restarts"

As described above I didn't notice until yesterday when trying to use tap to pay, which didn't work because no root = no Play Integrity fix

The only thing I've done is live boot the patched image from the October update and direct install to regain permanent root
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Se what slot are you on now, and try switching to the other slot.

If it boots ok, you got an OTA update.

You can use Boot Control or PF to do the switching
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Interesting, I'm on slot B. I've always been on slot A.

Secret OTA updates? What is the world coming to?!

I must have done this wrong because device is now in bootloader and PF thought it was rebooting to system.

Uh oh, now I have a boot loop

Bootlooped several times and ended up back in slot B.

Tried it again. Reboot to bootloader, switch slots, device boot loops a few times and ends up back in slot B
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Google can force update you anytime, whether you're rooted or not, and there has been many reports that people got updated while they're rooted.

Usually this happens to people that have fallen behind several updates, or if their is a major security update that they want people to be updated to.

It's possible that they want to push people to A14, of course just a hypothesis, who knows what Google want.

Of course their updates are OTA, which means it would be to the other slot, hence why I expect you to have a good bootable rooted slot A.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
K, but, I religiously update as soon as the update is available. I flashed the factory image to both slots as soon as it dropped. Device was happy and never told me there was an update until I discovered it had restarted overnight.

Unfortunately this doesn't seem to be the case. Not sure why but slot A won't boot.

I'm about to sideload the OTA and see if that gets me back to slot A.

I've never understood when you and others have mentioned switching slots without problems. It's never worked for me; either it'll bootloop back to the original slot, or I end up with "No valid slot to boot" in bootloader.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
interesting, so their update actually made your previous slot non-bootable.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I keep editing and adding to my posts lol
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
It will work,

If you use PF, then it's simple,

load OTA, process, select boot, patch boot, flash ota

it will apply to A, and then you should be able to switch to B again

of course you can do it manually as well.

It will work, the requirement is that both slots should have the same firmware.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Ah.

Sideloaded October update, am now on slot A.

Rebooting to bootloader....

Switching slots...

Worked, am on slot B. Ok, switching back to slot A.

I don't understand. Unless they also updated the OTA package. sideloading the OTA should have failed if what I got was indeed an OTA update.

Oddness. Maybe I need to start double checking kernel versions. I don't think Google Play system updates require a reboot, do they?
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Curious when did you first update your slot A to A14?

Here's the theory that I spoke about.

At some point you were on slot A (and let's assume that were still on A13)

Google's update engine wanted to update you to A14, the download starts streaming/ installing, all the tracking/progress is stored in the data partition, you can reboot in between and the download / install will resume in the background.

You then updated to A14 on slot A, this had no impact to the update engine because it has already started the process and it was updating B.

Once the process completed, it rebooted your phone and you ended up on slot B and lost root.