Without a custom recovery, and without an updated suhide, is it possible to trick SafetyNet into working?
I'm running the latest ElementalX kernel, which worked while I was not rooted, because it disabled the unlocked bootloader check, but once I rooted, the response validation fails.
While we wait for a custom recovery, is there a way to hide root with a kernel modification or some other method?
Not that I know of because when you go to root using the fastboot boot boot-to-root.img image that Chainfire provides all it's doing is modifying the current boot image so whatever modification that was done to, say, ElementalX kernel (I'm using Sharky myself) it basically modifies something else or conflicts with a modification that will cause the SafetyNet check to fail with no way to work around it. So you will either have a working SafetyNet or you won't depending on what's more important to you. (I'm assuming you're concern about SafetyNet because of Android Pay so it basically comes down to what's more important: Android Pay or root). Don't think that will change any time soon unless there's a major breakthrough on getting a custom recovery and start seeing roms with su cooked in that allows for bypassing SafetyNet.
Related
My question is about systemless root. Has any effort been done to get that working on the Z00A?
Systemless root is normally created for Nexus devices where their bootloader detects system partition if it's modified or not, then prevents the end user from booting. Later discovered that systemless root is also able to not trip Knox or break OTA support on Samsung devices.
Systemless root isn't useful on our device, because our bootloader detects kernel and recovery and prevents the end user from booting if these files are unsigned unless the bootloader is unlocked.
Sent from my GT-I9500
Hello,
at the moment I have a HTC 10 with normal root and xposed.
But I would like to have the option of installing OTA updates and I have some question:
- Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
- Can I still flash a custom kernel and other mods in TWRP?
- What do I need for systemless root and systemless xposed?
- Are there any disadvantages?
And it would be awesome if someone could give me a full guide how to do this.
I would start with flashing a RUU, but what should I do after that?
Thanks in advance!
I can't say anything about systemless Xposed, but I've been wondering about it. Main thing I want to know is if it will play nice with Android Pay. Right now, I'd rather have Android Pay than Xposed, but I'd like both.
As for systemless root, yes, you can still flash custom kernels thru TWRP. I'm running @flar2's Elemental X and have run them both successfully on LeeDroid and Venom. Some mods may have to have some special prep if they're not baked into a rom, such as AdAway, to work properly with systemless root.
The disadvantages to systemless root, to this point have been you can't run Xposed on it (not sure how it works now), and root is broken on some poorly coded apps, like ES File Explorer.
The easiest way to install systemless root now is just to install a rom. Put TWRP on and pick a rom. Both LeeDroid and Viper have options for systemless root. You're up and working out of the box with nothing special to do.
Superguy said:
I can't say anything about systemless Xposed, but I've been wondering about it. Main thing I want to know is if it will play nice with Android Pay. Right now, I'd rather have Android Pay than Xposed, but I'd like both.
As for systemless root, yes, you can still flash custom kernels thru TWRP. I'm running @flar2's Elemental X and have run them both successfully on LeeDroid and Venom. Some mods may have to have some special prep if they're not baked into a rom, such as AdAway, to work properly with systemless root.
The disadvantages to systemless root, to this point have been you can't run Xposed on it (not sure how it works now), and root is broken on some poorly coded apps, like ES File Explorer.
The easiest way to install systemless root now is just to install a rom. Put TWRP on and pick a rom. Both LeeDroid and Viper have options for systemless root. You're up and working out of the box with nothing special to do.
Click to expand...
Click to collapse
Have a look at this: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
That's the reason why I'm asking - OTA is working, but Android Pay not (for me it doesn't matter. I never used android pay).
But I want to stay on Stock ROM, no Custom ROMs. I just want the ability to download and install OTA updates.
Edit: Well, I see that I still need stock recovery for OTA updates. It doesn't make sense to install systemless root, because I have stock system-image backup and stock recovery.
Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
Maik268 said:
Have a look at this: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
That's the reason why I'm asking - OTA is working, but Android Pay not (for me it doesn't matter. I never used android pay).
But I want to stay on Stock ROM, no Custom ROMs. I just want the ability to download and install OTA updates.
Edit: Well, I see that I still need stock recovery for OTA updates. It doesn't make sense to install systemless root, because I have stock system-image backup and stock recovery.
Is there any advantage between system and systemless root except OTA/Android Pay? Or is it still better to use system root?
Click to expand...
Click to collapse
I am in the same position, just got the phone and want to install systemless root, systemless xposed and systemless Adaway... Mainly the reason I want this is because I dont want to s-off (you cant flash newer firmwares that come with updates) or I dont want to restore system and performing update after that... I just want stock rom with elementalx and those xposed goodies I want it so that when I get a notification about update, I dont need to backup anything, flash anything, just install update regularly like all normal people BUT still after update have root and xposed
I think its possible, but I have to do a little research before I get on with it.. Now first step is unlock bootloader
CrazyCypher said:
I am in the same position, just got the phone and want to install systemless root, systemless xposed and systemless Adaway... Mainly the reason I want this is because I dont want to s-off (you cant flash newer firmwares that come with updates) or I dont want to restore system and performing update after that... I just want stock rom with elementalx and those xposed goodies I want it so that when I get a notification about update, I dont need to backup anything, flash anything, just install update regularly like all normal people BUT still after update have root and xposed
I think its possible, but I have to do a little research before I get on with it.. Now first step is unlock bootloader
Click to expand...
Click to collapse
Even with systemless root you have to restore stock recovery to use OTA updates
Well, I have a look at this next weekend when I have some more time.
Or I just try a custom ROM... :laugh:
Maik268 said:
Even with systemless root you have to restore stock recovery to use OTA updates
Well, I have a look at this next weekend when I have some more time.
Or I just try a custom ROM... :laugh:
Click to expand...
Click to collapse
Yes but the amazing thing is that after you flash everything you want, you can immediately restore stock recovery and have stock recovery all the time after you have everything systemless
Then if you want to flash something you flash TWRP.. otherwise you just leave re-flashed stock recovery
CrazyCypher said:
Yes but the amazing thing is that after you flash everything you want, you can immediately restore stock recovery and have stock recovery all the time after you have everything systemless
Then if you want to flash something you flash TWRP.. otherwise you just leave re-flashed stock recovery
Click to expand...
Click to collapse
Hello, I will receive my HTC 10 on Friday, and I all I want is to root and install Xposed Framework (A kernel would be nice too, but it's not a must) but I do want to receive OTA's and not having to flash the Rom each time that I want to update...
So if I root my phone Systemless, will I be able to Install Xposed (and a kernel) so when I receive an OTA, I just flash the stock kernel and install the update, then flash twrp again, without losing root or my data?
If so, how do I systemless root?
Thanks! :good:
Hi
I'm currently running a fully stock (used to be running 6.0, then 5.0, then rooted + twrp then fulmics.... before discovering that safetynet didn't like that) and was wondering if there is a way to get root without having safetynet detecting anything, on either 5.x or 6.x
I've seen suggestions to install TWRP and then flash a systemless supersu or magisk, but in order to install TWRP, I need to be rooted, plus I think (?) having TWRP installed would trigger safetynet, but don't quote me on that.
I've been thinking about whether it's possible to set up root methods like this or this install supersu systemlessly, but I don't understand enough to be able to do that by myself.
edit: bootloader is locked... I'm not sure you can unlock it?
Thanks for any help
Max
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
dr1445 said:
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
Click to expand...
Click to collapse
Your best bet would be to do some more reading "new one".... While your misunderstanding of the relation between root and su have me thinking that you are not ready to root yet. On a serious note, Magisk is a excellent alternative for SuperSu. Head over to the Magisk forums and read up for more info.
being a user not developer, i have no intention to modify software code, there for i do not require root. su is useful to run certain apps, like twrp manager to grant permissions. i like the linux sudo command better on my pc, but that is just one operators opinion and my not even be feasible on google firmware. i got into this with a nex 4 wanting to get onboard with ubuntu phone to ditch all the commercial and media bloat. since i had the nex 4 as a development phone why not try a custom rom and update to 7.1? after a few go rounds i got 14.1 installed. my adventures with the nex 5x and 6p and SuperSU both lead to a bricked phone, which i learned to get operational. basically nothing ventured nothing gained.
su is the command used to gain root access. If you've installed either SuperSU or Magisk you have rooted your device.
The current Magisk works well on the current Oreo image for the Nexus 5X. The bonus is that you can use apps that refuse to work if they think the device is rooted.
dr1445 said:
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
Click to expand...
Click to collapse
For me, stock 8.1, sr5 works. Stock rom is oem, but it doesn't have to be the whole oem, you can have a stock rom and twrp, so basically system and the kernel remain stock but recovery can be something other than stock, and so on...
Sent from my Nexus 5X using Tapatalk
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
-=ApA=- said:
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
Click to expand...
Click to collapse
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Aldenar said:
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Click to expand...
Click to collapse
You didn't have to factory reset - just have to return to stock before ota - that's required because boot partition is changed by rooting and ota fails... So basically fastest method is flashing stock boot image before ota, making new one with magisk after ota and returning with full root
calinorg said:
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
Click to expand...
Click to collapse
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
-=ApA=- said:
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
Click to expand...
Click to collapse
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Aldenar said:
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Click to expand...
Click to collapse
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
-=ApA=- said:
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
Click to expand...
Click to collapse
Latest, so 1.1.1. As proof, see screenshots
Aldenar said:
Latest, so 1.1.1. As proof, see screenshots
Click to expand...
Click to collapse
Awesome, thanks!
EDIT: Also working for me just fine.
Any luck on 12.1.5.x or even 12.5 beta?
Illuvitar said:
Any luck on 12.1.5.x or even 12.5 beta?
Click to expand...
Click to collapse
12.5.1.0 was fine, now trying with 12.5.5.0
12.5.5.0 needs Universal SafetyNet Fix module update (i'm using 2.1.1), otherwise SafetyNet check will fail! With 12.5.1.0 it's still working fine with Universal Safetynet Fix 1.1.1 tho.
You will also need to install Riru to use Universal SafetyNet fix 2.1.1
Update:
12.5.12.0 still working. Had to rename magisk.db tho and reinstall Magisk 23.0.
Make sure not to update Magisk beyond version 23!