Hi. Did you figure it out? Same is happening with my 4xl.After flashing the patch Magisk file my phone won't restart into system it keeps going back to fastboot mode. Now when i click on start in fast boot nothing happen .
Hi. Did you figure it out? Same is happening with my 4xl.After flashing the patch Magisk file my phone won't restart into system it keeps going back to fastboot mode. Now when i click on start in fast boot nothing happen .
Short answer, no.Just got my pixel 5 and there is an update , should i take it ?.
I downloaded the latest Factory image for my device from google's website , extracted the boot.img and flashed it vi fastboot and rebooted system which work now. I then got the updated magisk apk for my device, add the boot.img i use from the factory image to my device via PC then use magisk to patch that boot.img . Transfer that patched boot.img to my PC put it in the folder i use adb and fastboot from then reboot to bootloader and flashed it via fastboot.
Weird, I did the same, but whenever I flash the patched boot image I get bootloop. Magisk 22 canary here. Can't figure it out.I downloaded the latest Factory image for my device from google's website , extracted the boot.img and flashed it vi fastboot and rebooted system which work now. I then got the updated magisk apk for my device, add the boot.img i use from the factory image to my device via PC then use magisk to patch that boot.img . Transfer that patched boot.img to my PC put it in the folder i use adb and fastboot from then reboot to bootloader and flashed it via fastboot.
Phone booted up fine after and i got root.
Same here - Flash March Update - Boots fine.
Patch Boot.img and flash to the device and it just boots to recovery saying Data is corrupt *_*
I assume Magisk is potentially an issue here.
The QD1YQ is the Google Store version of the P5.At the moment, I get LOCKED when I "adb reboot bootloader".
I can't figure out if there's any hope of unlocking the bootloader. I've seen suggestions that the answer is a definite maybe. I seem to have made the mistake of thinking this Pixel 5 is carrier agnostic, but I guess it's not. I bought the phone as an "open box" eBay, with AFAIK no indication being tied to a particular carrier. The model is QD1YQ - any guesses as which carrier uses this model number?
The QD1YQ is the Google Store version of the P5.
Is there any chance of unlocking the bootloader with the OEM option greyed out?
PS G:\Pixel5\XDA\sdk> .\fastboot devices
09091FDD4006RD fastboot
PS G:\Pixel5\XDA\sdk> .\fastboot flashing unlock
FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed
You only need the magisk module universal safetynet fix.Do i just need the bypass fix or hide connfig props + bypass fix?
I flashed factory image from April and than I flashed patched boot.img. After I flashed props choose pixel 3a and 11. Than I reboot & flash the fix but still can't bypass
You only need the magisk module universal safetynet fix.
Go to the first post and go trough all instructions described at:
"For Safetynet you have to do the following steps"...
And I recommend to uninstall the props module to switch the device-fingerprint, because at the moment it isn't needed for the p5.
Regards![]()
Nope same steps, I'm using LOS 18.1 as well.I'm still unable to pass safetynet despite following the steps above, however part of this may be due to the fact that I'm also running lineage os on it. Are the steps different for that rom?
Well. That would of been great info 14 pages ago! Kept testing in Magisk and it failed, testing with another app passes! Thank you for that info!Nope same steps, I'm using LOS 18.1 as well.
Install magisk 22.1, install safetynet fix from github link, enable magisk hide and inside disable google play services and other google services.
Currently you can't check safetynet inside magisk app, you get Safetynet API error. Just install another safetynet check app like safetynet test:
![]()
fastboot devices
fastboot flashing unlock
fastboot flash boot "magisk_patched Build 21005.img"
A suggestion, please add that those having issues with the flash command failing to WRITE can try putting ./ before the command and that should work.
hm not working for me. P5 is unlocked.
C:\>fastboot flash boot "magisk_patched Build 21005.img"
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.419s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.500s
Do:
./fastboot flash boot "magisk_patched Build 21005.img"
If you flash the factory image, it also flashes vbmeta. To avoid doing it twice, change the line in the batch file that readsHello all,
Maybe this might sound obvious for many, but better safe than sorry, so here it goes:
If if flash factory image (A12 public release) via fastboot, using the bat file in its original state, this is without removing the "-w", Ill be on A12 with wiped data. After this, is it safe to just patch and flash boot.img or is it also necessary to flash vbmeta with disabled flags?
Thank you in advance.
fastboot -w update redfin-image.zip
fastboot --disable-verity --disable-verification -w update redfin-image.zip