[Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More

[jjlane86]

I did both 34.0.3 and added the environment variable too. I am thinking what I missed was not disabling Magisk modules before flashing factory image, so it kept interfering pre boot and avoiding the full wipe. I did a factory reset and all seems good, but should I try again after factory resetting?

 

[mangojain]

If there is no TWRP for Android 13, how do i get rid of the encryption on the phone? Magisk is installed and i can view the root folders, but i can't paste, delete or modify any file.

 

[Homeboy76]

I did both 34.0.3 and added the environment variable too. I am thinking what I missed was not disabling Magisk modules before flashing factory image, so it kept interfering pre boot and avoiding the full wipe. I did a factory reset and all seems good, but should I try again after factory resetting?

@jjlane86
If the factory reset wiped all your data, why would you try again with SDK Platform-tools r.34.0.3?

 

[Homeboy76]

If there is no TWRP for Android 13, how do i get rid of the encryption on the phone? Magisk is installed and i can view the root folders, but i can't paste, delete or modify any file.

Have you read this?

 

[jjlane86]

@jjlane86
If the factory reset wiped all your data, why would you try again with SDK Platform-tools r.34.0.3?

Because I did not know if the Factory reset maybe left Magisk enabled somehow, which was in the back of my mind because of that blurb about disabling magisk modules and DO NOT install a second version of magisk...It was just a thought. It appears the factory reset worked so far though as I have been able to re-root, modify/add some custom props, and use Cellular band locking functionality. Play Store hasnt certified device yet tho...might look into that later.

 

[mangojain]

Have you read this?

That is a solution for for encryption, but won't work the other way.

 

[V0latyle]

@Homeboy76 not sure if you were aware, but Play Protect is not the same as Play Integrity.

While I do believe that the Play Store's Play Protect ceritication corresponds with MEETS_DEVICE_INTEGRITY, I'm not 100% sure.

What I AM sure about is Play Store will not tell you your device is failing. You can be failing BASIC_INTEGRITY and DEVICE_INTEGRITY, and Play Store will still show "Device is certified". This does not seem to change until all Play Store data is cleared.

Why this is a problem: You could be passing pre update, then failing post update, and Play Store will still report your device as certified.

Solution: Either use Play Store Developer Options to confirm Play Integrity is passing BASIC and DEVICE labels, or use a 3rd party app such as Integrity Checker or TB Checker. I personally prefer to use Integrity Checker because the responses are instantly apparent, no need to read the JSON output from Play Store

 

[Homeboy76]

@Homeboy76 not sure if you were aware, but Play Protect is not the same as Play Integrity...

I am aware they Play Protect and Play Integrity are not the same. I do appreciate the information you provided.

 

[Homeboy76]

Update
XDA members are reporting more issues with SDK Platform-tools 34.0.3

Use SDK Platform-tools 33.0.3

 

[Homeboy76]

Update
[MODULE] [MOD] Universal SafetyNet Fix by Displax
v2.4.0-MOD_1.3

• Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp!
• Ignore props changing on Xiaomi.eu. This fixes randomly attestation failings. So strange ROM...

 

[Homeboy76]

Magisk Canary Update - notes.md:
Download: app-release.apk

 

[Homeboy76]

Magisk Canary (a8c4a33e) (26103)
Is not working for everyone, it has some issues that need fixing: Use, attached,
Magisk Canary app-release_47d2d4e3-26102.apk until it (26103) is fixed.

 

[rand0macc3ss]

Hello, I recently upgraded my redfin pixel from Android 11 to 13. Before doing so, I went into Magisk and did an "uninstall and restore img from backup" or whatever that dialogue says. I did use magiskhide, and possibly some safetynetfix module. I am 80% certain I didn't use other modules. I do not think I disabled these modules, and instead I uninstalled the magisk app (which was renamed to MyFirstApp).

I then flashed factory image (without wipe) to both slots.

Now whenever I try to flash a patched boot.img I get a bootloop. Then it drops me into fastboot (reason: no valid slot to boot).

What I have tried:

• Verify platform-tools. Indeed I am running 33.03
  
  
• Check if old magisk app (renamed to MyFirstApp) is somehow lingering. It is not. It does seem to have uninstalled completely. Doesn't show up in any app lists, doesn't show up in TB checker, etc.
  
  
• Tried using Magisk Canary app-release_47d2d4e3-26102.apk to newly patch the original boot.img.
  
  
• Tried same as above, but before flashing uninstalling the Magisk Apk
  
  
• Tried to boot into twrp without flashing it (there is no working Android13 version, but hoped to at least get a root shell to check for lingering modules). Did not work. Got a root shell, but all directories seemed empty. Not sure If I need to decrypt my phone or something.
  
  
• Tried to uninstall modules with magisk --remove-modules command via adb. Command not found (and also I don't have root so not even sure if that would work)
• Note: after each failure resulting in boot loop, I reflash original boot.img and I am able to start the phone just fine. Flash does not fail. Looked at Magisk log after patching boot.img and everything went ok. No issues reported in log.

My suspicion is that I had some Magisk modules that needed to be disabled, and since I didn't directly disable them before doing "Uninstall and restore img from backup" and uninstalling the app itself, those modules stayed behind and are causing a problem.

The issue is, I don't know how to get into /data to check/delete modules and I no longer have root (so no permissions in /data). I know it was probably foolish, but I thought "uninstall completely and restore boot.img from backup" (or whatever that dialogue says) would also take out the modules.

Was also foolish to attempt this from memory instead of finding a guide . I used to do this all the time from memory and never ran into issues, but guess I got rusty after a while and forgot a step.

Sorry if that was too much background, just want to help someone help me.

The ask: how can I at this point go uninstall magisk modules? (Assuming that is my issue). Can't fastboot to TWRP and flash magisk uninstall zip (if that is even still a thing) because TWRP is not a thing for Android13 redfin.

I don't want to install custom firmware or otherwise wipe my phone, but won't go into detail unless someone asks because this post is already quite long. Is there something else I can boot into temporarily to get a root shell and delete the modules? Have googled for alternatives, but found nothing promising.

 

[rand0macc3ss]

Hello, I recently upgraded my redfin pixel from Android 11 to 13. Before doing so, I went into Magisk and did an "uninstall and restore img from backup" or whatever that dialogue says. I did use magiskhide, and possibly some safetynetfix module. I am 80% certain I didn't use other modules. I do not think I disabled these modules, and instead I uninstalled the magisk app (which was renamed to MyFirstApp).

.........

New thing I tried: I tried flashing vendor_boot.img from LineageOS to boot into that recovery, sideloaded uninstall.zip (which was just renamed from magisk manager apk). Did not work
__________
Have a new idea. Going to rollback to A11, reinstall old version of Magisk I had, basically retrace my steps except not screw up this time Hopefully that works. Will report back if it is successful.

 

[Homeboy76]

...Is there something else I can boot into temporarily to get a root shell and delete the modules? Have googled for alternatives, but found nothing promising.

Have you tried booting Safe mode?
Just boot Safe mode, then reboot. All Magisk modules will be disabled/removed.

 

[rand0macc3ss]

Have you tried booting Safe mode?
Just boot Safe mode, the reboot. All Magisk modules will be disabled/removed.

So that is really cool information that I did not know I tried it and unfortunately still getting a bootloop so at this point I don't know what the issue could be or what I could try.

• went into safemode, so magisk modules should be off.
• flashed latest stock image to both slots
• patch boot.img and adb flash boot patch_boot.img
• bootloop

 

[Homeboy76]

So that is really cool information that I did not know I tried it and unfortunately still getting a bootloop so at this point I don't know what the issue could be or what I could try.

• went into safemode, so magisk modules should be off.
• flashed latest stock image to both slots
• path boot.img and adb flash boot boot.img
• bootloop

I'm assuming you are using Google's stock firmware and not a custom ROM.

Open a Command prompt in the SDK Platform-tools r33.0.3 folder (the folder with fastboot.exe in it):
fastboot flash boot --slot all boot.img

 

[rand0macc3ss]

I'm assuming you are using Google's stock firmware and not a custom ROM.

Open a Command prompt in the SDK Platform-tools r33.0.3 folder (the folder with fastboot.exe in it):
fastboot flash boot --slot all boot.img

Indeed, I stay mostly stock and just slightly tamper once I have root And I did already do that (flash original boot.img) but I just get a bootloop any time I try to root. At this point don't know what the issue is. I might try downgrading to last months version of a13 and see if that allows me to flash patched_boot.img without a bootloop. Because at this point there is no other Magisk Manager app, and no modules since I booted into safe mode. So nothing should be causing an issue.

Thanks for the help Good lookin out.

 

[Homeboy76]

Indeed, I stay mostly stock and just slightly tamper once I have root And I did already do that (flash original boot.img) but I just get a bootloop any time I try to root. At this point don't know what the issue is. I might try downgrading to last months version of a13 and see if that allows me to flash patched_boot.img without a bootloop. Because at this point there is no other Magisk Manager app, and no modules since I booted into safe mode. So nothing should be causing an issue.

Thanks for the help Good lookin out.

Delete the magisk_patched...img you have and repatch the boot.img with the magisk app.

1. Disable all the modules in Magisk before you repatch it.
2. Make sure the boot.img you patch it with is from the same month as the Factory/OTA image on your phone i.e., if the Factory/OTA image on your phone is July 2023, extract the boot.img from the July 2023 Factory image.

 

[rand0macc3ss]

Didn't realize I would have to patch boot.img again once modules were disabled. Had repatched before, but not since disabling modules. Thanks a million @Homeboy76 !