Related
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
SafetyNet will always fail if your device is rooted, even with systemless mode.
SuicideFlasher said:
SafetyNet will always fail if your device is rooted, even with systemless mode.
Click to expand...
Click to collapse
anyway to bypass this with another super user tool?
No way aside from unrooting.
[email protected] said:
Hi
I flashed stock image on my device for some reasons and since then no matter which version of Supersu I flash the safetynet is failing.
any suggestions will be very helpful
Click to expand...
Click to collapse
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
ndarkside93 said:
SuperSU will always trip it. Also on a stock image with stock kernel, an unlocked bootloader will also trip it since the latest update
Click to expand...
Click to collapse
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
josephcsible said:
The unlocked bootloader check isn't present on all devices, and doesn't seem to be present on this one. Also, phh's root with Magisk and Magisk Hide currenly passes.
Click to expand...
Click to collapse
Yes magisk will pass, but SuperSU will always fail. It's not looking for the packages installed for magisk, but does look for the packages installed by SuperSU. And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
ndarkside93 said:
And the latest security patches updated safetynet to do a bootloader check, which can be masked by a custom kernel.
Click to expand...
Click to collapse
I can pass SafetyNet without a custom kernel (running stock M4B30X).
josephcsible said:
I can pass SafetyNet without a custom kernel (running stock M4B30X).
Click to expand...
Click to collapse
Yes, and stock was last updated to October patch set. It became universal in the November patches
ndarkside93 said:
Yes, and stock was last updated to October patch set. It became universal in the November patches
Click to expand...
Click to collapse
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
josephcsible said:
But the Nexus 5 is no longer getting security patches (the October one was the last one), so wouldn't that mean that it will never get that check?
Click to expand...
Click to collapse
I suppose that is true.
ndarkside93 said:
I suppose that is true.
Click to expand...
Click to collapse
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Fif_ said:
I don't think so.
Isn't Safety Net part of Google Services?
That will still be updated.
Click to expand...
Click to collapse
SafetyNet itself will be, but to detect an unlocked bootloader, it relies on the bootloader to pass a kernel parameter that it looks at. The Nexus 5 bootloader doesn't pass any such parameter, and a bootloader update (of which there are no more) would be required for it to start.
My device is failing and as a result I am unable to setup Android Pay. Is anyone else seeing this on their phone?
Same issue
I'm rooted with Magisk and I pass.... so that's very odd
Just got an OTA that fixed it.
tw1tch175 said:
Just got an OTA that fixed it.
Click to expand...
Click to collapse
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Howling Wolf said:
Sprint or unlocked U11 ?
I guess unlocked to get an OTA this fast...
Click to expand...
Click to collapse
Yeah, unlocked. It seemed like a day zero ota that rolled out a bit late, it didn't update my monthly security but after it I had an update to my headphone dac and Assistant app.
heslo.rb26 said:
I'm rooted with Magisk and I pass.... so that's very odd
Click to expand...
Click to collapse
How did you do it? I flashed TWRP and Magisk, and then flashed the stock recovery, and I am failing safety net...
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
Let us know
ticklemepinks said:
Let us know
Click to expand...
Click to collapse
Currently not working for me but I didn't flash the stock boot.img before I flashed the new Magisk so that is probably my issue there. Don't really have the time to mess with it currently so it will have to wait. If anyone else manages to get it working, feel free to update us
EDIT: Got off my ass and uninstalled Magisk, flashed the original boot.img and removed the Magisk Manager. Then I restarted the handset and flashed the Magisk v13 beta.... Pass SafetyNet checks no worries!
heslo.rb26 said:
HTCdev to unlock bootloader
Flash TWRP
Flash Magisk
Boom, pass SafetyNet no worries
EDIT: Just read Google has passed an update to SafetyNet and it no longer passes with Magisk V12. Apparently V13 fixes this, will flash soon and report back
Click to expand...
Click to collapse
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
ryanyz10 said:
I figured that out last night too after spending an hour wondering what I did wrong. Enabling Core-only mode on v12 also works, but you get no modules which is kind of pointless. I will try flashing V13.
EDIT:
Just flashed V13, and it still doesn't work.
@heslo.rb26 How did you get it to work?
Click to expand...
Click to collapse
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
heslo.rb26 said:
Uninstalled Magisk
Flashed the stock boot.img
Rebooted and uninstalled Magisk Manager
Back to Recovery and flashed the new Magisk
.....
Profit
Click to expand...
Click to collapse
I think it might have failed because I flashed a module. Don't think you can do that in the current beta and still pass the new safety net.
That could very well be the issue, currently only using Magisk for root, no modules
I had SafetyNet working with v12 but then on the next reboot it failed. I upgraded to Magisk v13 and again it worked for one reboot. Also looks like the OTA is for unlocked models only (not Sprint)... anyone got any others ideas?
Anyone know why I'm not passing SafetyNet?
Previously, it was on 7.1.2 stock with twrp flashed and rooted. Now on 8.0 stock, no root or twrp but not passing SafetyNet.
SafetyNet also dectects unlocked bootloader.
Have you tried this? https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
This requires root, though.
mngdew said:
SafetyNet also dectects unlocked bootloader.
Have you tried this? https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
This requires root, though.
Click to expand...
Click to collapse
i just tried this kernel (stock, with SafetyNet patch) but no luck, unfortunately. something is still tripping SN.
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
poolemit said:
i just tried this kernel (stock, with SafetyNet patch) but no luck, unfortunately. something is still tripping SN.
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
Click to expand...
Click to collapse
I tried the method in that thread. Everything works but suhide. Safety net is still being triggered some how.
gabes100 said:
I tried the method in that thread. Everything works but suhide. Safety net is still being triggered some how.
Click to expand...
Click to collapse
You shouldn't have to root to flash the kernel. You just need to have your bootloader unlocked. Then just boot to twrp and install the kernel.
robocuff said:
You shouldn't have to root to flash the kernel. You just need to have your bootloader unlocked. Then just boot to twrp and install the kernel.
Click to expand...
Click to collapse
I have an unlocked bootloader but have not put a custom recovery or rooted... I'm thinking i may try this method.. is there a walk through?
I know i read that modifying the pixel is more tricky than the old days of android and I do not want to mess it up.. Thanks!
poolemit said:
Anyone know why I'm not passing SafetyNet?
Previously, it was on 7.1.2 stock with twrp flashed and rooted. Now on 8.0 stock, no root or twrp but not passing SafetyNet.
Click to expand...
Click to collapse
Take a look at my couple of posts and links on this page. It is because of an old api that topjohnwu has not been able to fix yet due to his move. It is not actually failing, but not responding to the server correctly. There is also a link for a checker that has been updated and works fine. It is discussed a ton on the Magisk page threads.
https://forum.xda-developers.com/pixel/how-to/9-0-released-t3825746/page4
Hey all, so I iflashed lineageos 17 4.9 kernel by mistake. It slightly heats up my device .
Can I downgrade to 3.18 safely?
If so, how??
Safe to dirty flash this?
https://forum.xda-developers.com/redmi-s2/development/rom-lineageos-17-1-t4042045
One more question:
Some of my apps shows root detection with 4.9 version then crashes but I haven't rooted.
I tried a lotta methods: flashed magisk uninstaller, flashed installer then uninstaller and even use magisk hide feature with magisk installed but none works. Is this because the ROM that I'm using is in Testing Phase? Also it shows SE Linux disabled.
https://forum.xda-developers.com/redmi-s2/development/rom-lineageos-17-1-t4103145
Sorry for not looking properly into description, I'm new to all this stuff
Do clean flash or u can try other roms with 4.9 kernel other rom dosent have this prblm
mohitdabas07 said:
Do clean flash or u can try other roms with 4.9 kernel other rom dosent have this prblm
Click to expand...
Click to collapse
Sorry for late response, i clean flashed n and switched to Cs 3.18, but thanks anway.
So far im liking the os. There is one problem though, Root detection in certain apps problem still persists even though device not rooted. Anyway to solve this problem?
Thanks.
sk971 said:
Sorry for late response, i clean flashed n and switched to Cs 3.18, but thanks anway.
So far im liking the os. There is one problem though, Root detection in certain apps problem still persists even though device not rooted. Anyway to solve this problem?
Thanks.
Click to expand...
Click to collapse
Root it by magisk and use magisk hide
mohitdabas07 said:
Root it by magisk and use magisk hide
Click to expand...
Click to collapse
Ok, i flashed magisk 20.4, then installed magisk manager 7.5.1 and from settings activated Magisk Hide, but root detection still occurs and app crashes after that.
IDK why?
Tapping on safety net check stats on magisk manager shows both ctsprofile n basicintegrity to "true".
Do i have to encrypt my phone to fix this problem? Its disabled atm.
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!