First of all didn't realize I posted this in the wrong area last time, my bad.
Device SMG930V
ROOT yes
ROOT method ENG BAT AP then root script
Android 7.0
Security patch latest
Question
Is there any possible way to install xposed to hide root so I can play south park? I've checked a root method post that claims you can but the root method sent my phone in a boot loop, a very fast loop.. So the rest seems fishy, can anyone confirm a xposed installation for my device? Please and thank you!
Xposed modifies the boot image which requires an unlocked bootloader, the G930V is snapdragon and has the bootloader locked, so you can't put Xposed on the 930V
Xposed also trips safetynet worse than root, it wouldn't hide anything.
You can check if Magisk Hide can be installed on snapdragon models, but from memory that too also needs an unlocked bootloader.
Crap, so is there a successful way to hide the root from certain apps yet? Are hands are tied if a game detects root
Beanvee7 said:
Xposed modifies the boot image which requires an unlocked bootloader, the G930V is snapdragon and has the bootloader locked, so you can't put Xposed on the 930V
Xposed also trips safetynet worse than root, it wouldn't hide anything.
You can check if Magisk Hide can be installed on snapdragon models, but from memory that too also needs an unlocked bootloader.
Click to expand...
Click to collapse
Related
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
ndarkside93 said:
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
Click to expand...
Click to collapse
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Sent from my sailfish using XDA Labs
nednednerb said:
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Click to expand...
Click to collapse
Very true, but on the pixel with the November update, safety net checks for bootloader unlock, but I think Franco kernel can hide it to pass the check, if there is no root.
Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Nope
Flash stock
farid993 said:
Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Click to expand...
Click to collapse
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
MAX 404 said:
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
Click to expand...
Click to collapse
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
farid993 said:
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
Click to expand...
Click to collapse
Hi
Option 1 Systemless root and systemless SuperSu ( Chainfire) no xposed (rovo89) , no system modification, no R/W systems, no TWRP , unroot from SuperSu , OTA possible
Option 1.1 use Flashfire guide here
Option 2 ( have not tested it) fake system status
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
*Detection* said:
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Click to expand...
Click to collapse
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
*Detection* said:
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
Click to expand...
Click to collapse
+ 1 guys
After rooting is very hard to keep system "clean" enough ....if you meet the conditions is possible.....but to my by far *Detection* suggestion is easier...
status spoofer i have not tried ( I have a custom rom) ......
Can anybody confirm that with unlock bootloader only (no root yet), that android pay works or not on stock rom?
I'm tempted to at least setup twrp while i'm still on 20a but then if android pay don't work even before root then I might not do it. Thanks.
hchchchc said:
Can anybody confirm that with unlock bootloader only (no root yet), that android pay works or not on stock rom?
I'm tempted to at least setup twrp while i'm still on 20a but then if android pay don't work even before root then I might not do it. Thanks.
Click to expand...
Click to collapse
Android pay won't work if you unlock your bootloader only, but if you unlock your bootloader and install magisk for root it works I would set up TWRP, install magisk for root and also recommend installing the Asgard v4.5 kernel. Then in magisk manager you need to go-to settings and check magisk hide (and don't use built in busy box with magisk hide enabled) and check safety net. If you pass, you can use Android pay.
jeffsga88 said:
Android pay won't work if you unlock your bootloader only, but if you unlock your bootloader and install magisk for root it works I would set up TWRP, install magisk for root and also recommend installing the Asgard v4.5 kernel. Then in magisk manager you need to go-to settings and check magisk hide (and don't use built in busy box with magisk hide enabled) and check safety net. If you pass, you can use Android pay.
Click to expand...
Click to collapse
Has anyone tried this and been able to confirm if it works?
Also, will a T-mobile branded LG G5 that is "carrier" unlocked "only" work with Android pay? If not, do you need to go through the same process of unlocking the boot loader, rooting, and installing magisk? Cheers and thanks in advance for any feedback!
Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Baradoura said:
Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Click to expand...
Click to collapse
Normal root modifies files on your system partition so that you can have root access. On stock firmware, this breaks dm-verity and causes you to fail SafetyNet checks making AndroidPay and some other apps no longer work. It also prevents you from taking OTA updates because it is no longer recognized as stock firmware. Even if you fully unroot, you will still not be able to take OTA updates because the phone "remembers" that you modified system files and fails dm-verity. The only way to get back to original firmware and take OTA updates is to reflash your entire firmware, wiping all user data in the process.
Systemless root works by intercepting files at the kernel level before the phone fully boots and replaces system files. Once the helper apps are installed you can pass the SafetyNet checks, but you will still not be able to receive OTA updates. The major benefit to systemless root is that you can reflash your stock boot.img (kernel) and your phone will be back to stock firmware, you will bass dm-verity and SafetyNet checks, and you can take OTA updates all without losing any user data. It is very easy to switch between systemless root and stock unrooted by simply flashing the necessary boot.img.
My guess is that since you're on a custom ROM you have normal root. To learn more about systemless root, take a look at Magisk.
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Baradoura said:
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Click to expand...
Click to collapse
No, you are on systemless if you use slimx.
Are you sure ? I don't want to try some risky method to know
Baradoura said:
Are you sure ? I don't want to try some risky method to know
Click to expand...
Click to collapse
You can't have custom kernel and use android pay, just forget about it.
Hey, does TWRP breaks the SafetyNet? Can I install TWRP without getting a SafetyNet error?
simon151102 said:
Hey, does TWRP breaks the SafetyNet? Can I install TWRP without getting a SafetyNet error?
Click to expand...
Click to collapse
TWRP doesn't, but unlocking your Bootloader to get TWRP on your phone does. To hide the unlocked Bootloader state, your Kernel needs to be patched. Most custom Kernels are patched for this reason and hide the Bootloader state.
There are other things that might cause safetynet to fail. Older Root methods like the LOS SU Addon, or selinux being in 'Permissive' mode.
Magisk Hide is usually the cure for most safetynet problems.
Dirk said:
TWRP doesn't, but unlocking your Bootloader to get TWRP on your phone does. To hide the unlocked Bootloader state, your Kernel needs to be patched. Most custom Kernels are patched for this reason and hide the Bootloader state.
There are other things that might cause safetynet to fail. Older Root methods like the LOS SU Addon, or selinux being in 'Permissive' mode.
Magisk Hide is usually the cure for most safetynet problems.
Click to expand...
Click to collapse
So does Unlocking bootloader on my A5 2017 breaks the safetynet?
simon151102 said:
So does Unlocking bootloader on my A5 2017 breaks the safetynet?
Click to expand...
Click to collapse
As @Dirk clearly stated it depends on your kernel.