Howto - Root your bramble with Magisk

[WhiteAsIce]

Have you tried hiding the apps in Magisk? Do you want safetynet for a specific app that won't launch/complains about being rooted? Try MagiskHide in Magisk Manager if you haven't. Exclude those apps to hide root from them.

Yep, I have those options on, but I still cannot pass Safetynet. I'm trying to get Google Pay to work. I've seen others say they got Google Pay to work by passing Safetynet/hiding root.

 

[GoldElocks]

Yep, I have those options on, but I still cannot pass Safetynet. I'm trying to get Google Pay to work. I've seen others say they got Google Pay to work by passing Safetynet/hiding root.

If you haven't already try following this guide for passing safetynet on the 4a. You'll need the magisk props config module. This worked for my 4a and should work for the 4a 5g as well but mine doesn't arrive until later this week so haven't tried it yet.
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773

 

[WhiteAsIce]

If you haven't already try following this guide for passing safetynet on the 4a. You'll need the magisk props config module. This worked for my 4a and should work for the 4a 5g as well but mine doesn't arrive until later this week so haven't tried it yet.
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773

I tried that. I changed the setting to Pixel 3a as listed. However, my bramble still cannot pass safetynet.

 

[Voodoojonny]

I tried that. I changed the setting to Pixel 3a as listed. However, my bramble still cannot pass safetynet.

Hey I also can't pass Safetynet, but... It's only a cts error. Basic integrity is right. So you shouldn't have any problems. I tried Magisk hide probs without success. So now we need to wait for TWRP to be able to flash universal safetynet fix.

 

[syckman]

When I try to flash the boot file in the OP (./fastboot flash boot boot.img), it's about to write 'bootb', then I get this:
FAILED (remote: Not allowed to flash (bootb))

Didn't see anyone else here with this issue so I must be doing something silly - any idea how to fix? TIA

 

[VerneVerne]

When I try to flash the boot file in the OP (./fastboot flash boot boot.img), it's about to write 'bootb', then I get this:
FAILED (remote: Not allowed to flash (bootb))

Didn't see anyone else here with this issue so I must be doing something silly - any idea how to fix? TIA

From my perspective, the best bet is to extract the boot from the monthly zip and just patch it yourself via magisk

Edit: oops, didn't see that it was not allowed to flash bootb

 

[lmt1979]

When I try to flash the boot file in the OP (./fastboot flash boot boot.img), it's about to write 'bootb', then I get this:
FAILED (remote: Not allowed to flash (bootb))

Didn't see anyone else here with this issue so I must be doing something silly - any idea how to fix? TIA

You have to flash the appropriate boot.img for your build that you're currently running. Pull down the shade all the way or go into Settings, About Phone, and get the build number (it will look like 11.0.0 (RD1A.201105.003.C1, Nov 2020) or 11.0.0 (RD1A.200810.022.A4, Oct 2020). Download that build from https://developers.google.com/android/images
Take the boot.img from the factory image you downloaded ( you need to extract it from the zip file) and put it on your phone. Patch it with magisk manager, then transfer it back to your computer to fastboot flash it. Make sure your adb, drivers, platform tools is all updated.

I got the phone on the 18th and had similar issues. Bunch of links and stuff on this post:
https://forum.xda-developers.com/pixel-4a-5g/help/magisk-boot-img-patching-flashing-t4191955

 

[GoldElocks]

Received my bramble today and unlocked bl and rooted without issue. Used magisk hide, rename magisk manager, and magisk hide props config and changed to pixel 3a XL and I'm completely passing safetynet and was able to setup Google Pay.

 

[syckman]

I got the phone on the 18th and had similar issues. Bunch of links and stuff on this post:
https://forum.xda-developers.com/pixel-4a-5g/help/magisk-boot-img-patching-flashing-t4191955

Really appreciate your thorough reply!

I did follow the instructions on your other thread yesterday night and it just didn't work for me. Did everything you suggested (created patched boot.img in magisk, updated driver, installed platform tools - that all went fine) and still get the same error you did:
FAILED (remote: Failed to write to partition Not Found)

Spent enough time on this for now so temporarily giving up and will try again in a few days/weeks.

 

[TKruzze]

I have the T-Mobile version (50% off with trading in my OnePlus 6T). Got them to do the SIM unlock and then did a factory reset and was able to unlock the bootloader. Then, I flashed the latest November Factory ROM to make certain anything from TMobile was gone.

After that did the Magisk boot.img patch and set props (using module) to Pixel 3a and passed SafetyNet no problem. Even set up Google Pay. It's great to be back on Google software, but this screen is vastly inferior to what I had on the 6T.

 

[SirVilhelm]

I have adb working but when I get into the bootloader I cannot see the device anymore, are there drivers that need to be installed?

 

[xplode196]

Same - I have PowerShell telling me it's <waiting for any device>. Tried 2 different cables connecting the Pixel to my laptop.

Also made sure the Pixel has USB Debugging enabled. And checked the unlock option in Developer Options.

 

[SirVilhelm]

Same - I have PowerShell telling me it's <waiting for any device>. Tried 2 different cables connecting the Pixel to my laptop.

Also made sure the Pixel has USB Debugging enabled. And checked the unlock option in Developer Options.

I have adb working but when I get into the bootloader I cannot see the device anymore, are there drivers that need to be installed?

I ended up having to install the Google USB driver
https://developer.android.com/studio/run/win-usb

This worked

 

[xplode196]

I ended up having to install the Google USB driver
https://developer.android.com/studio/run/win-usb

This worked

Yep I started going down the same road. Unfortunately Windows says it thinks its drivers are better. When trying to manually override it, Windows says the .ini file isn't supported by the plugged in device

 

[SirVilhelm]

When I try to flash the boot file in the OP (./fastboot flash boot boot.img), it's about to write 'bootb', then I get this:
FAILED (remote: Not allowed to flash (bootb))

Didn't see anyone else here with this issue so I must be doing something silly - any idea how to fix? TIA

You get this figured out? I can't flash anything in bootloader, even official monthly won't flash, same error.


edit: had to use the official adb tools and not the "quick ADB"

 

[xplode196]

You get this figured out? I can't flash anything in bootloader, even official monthly won't flash, same error.


edit: had to use the official adb tools and not the "quick ADB"

I'm stuck at this part now. Where did you get the official ADB tools? I installed Android Studio but not sure what to do here

 

[SirVilhelm]

I'm stuck at this part now. Where did you get the official ADB tools? I installed Android Studio but not sure what to do here

Do a search on your C drive. It installs under c:\users appdata but I doht have the exact path right now. Search for adb.exe under c;\users

 

[syckman]

You get this figured out? I can't flash anything in bootloader, even official monthly won't flash, same error.


edit: had to use the official adb tools and not the "quick ADB"

Haven't tried again, but just saw your post and downloaded the official tool on another computer, used that to try again, and finally got it to work - so thank you so much!!

 

[rspkt]

I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.

Rooted my device using the canary build successfully but I also failed both basicIntegrity and ctsProfile SafetyNet checks. I modified the props also and now only pass basicIntegrity but still fail the ctsProfile check. Not sure what else to do to try and address this for now. The props config module documentation says if you fail both initially it's likely you might be unable to remedy this (currently anyway).

EDIT: I managed to solve the issue. After running props config again and selecting 'Force BASIC key attestation' and restarting, my device now passes both basicIntegrity and ctsProfile checks successfully. As quoted from the earlier guide:

Passing SafetyNet
As was discovered some time ago, google is switching to a hardware attestation method for safetynet. Fortunately, at the time of writing, there is a workaround thanks to @Didgeridoohan:

• Enable MagiskHide in magisk manager
• Download/Install his MagiskHide Props Config module from the magisk module repo
• Reboot
• Open terminal app on your phone and type 'su -c props'
• Select 'Force BASIC key attestation'
  This will make your device appear to be a different one in some instances and by default, this is Nexus 5. I prefer it to look like a newer device that doesn't have hardware attestation (Pixel 3a). So choose:
  'Pick from fingerprints list' -> 'Google' -> 'Google Pixel 3a'
• Reboot and verify you should hopefully pass safetynet!

 

[entropism]

Dumb question, it's been a while since I had a rootable device: What happens when an OTA update gets released? Will it update and we just have to just re-flash the modified boot image? Or will we have to flash the update manually and start the whole process over again?

 

[NikoZBK]

Dumb question, it's been a while since I had a rootable device: What happens when an OTA update gets released? Will it update and we just have to just re-flash the modified boot image? Or will we have to flash the update manually and start the whole process over again?

After the update is installed, you should retain root if you go back into magisk manager and install magisk to the other slot after OTA update, just make sure you don't reboot before you do so