Database Develop

SuperSU and SafetyNet / Android Pay

This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.

Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?

0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk

Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/

shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.

Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1

Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.

NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.

Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk

Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?

dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.

russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?

I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!

efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.

Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.

secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.

Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?

Why is the Permission system so bad?

Hi there, I recently got this phone and I am wondering why is the phone's permission system so horrible? The dialogues show up asking for permissions but you can only press Deny. You have to manually go to their Security App and then set Permissions from there in a very asinine roundabout way.
Is there a way to get around that and use the simpler android permissions management system like in CM?

That's just how MIUI works, you can flash CM if you have unlocked bootloader and TWRP installed.

proag said:
That's just how MIUI works, you can flash CM if you have unlocked bootloader and TWRP installed.
Click to expand...
Click to collapse
Yeah I might someday but what I mean to say is, this system looks like it was meant for older Android versions and just carried over so shouldn't they be overhauling it now? It's just painful to use.

Request for Root on NWS2.170620.003 Security Patch level July 1, 2017

hi,
i am new in these forums,
i searched over the web and also tried many root methods, but none worked.
root method for NXH19X is not working for me i tried multiple times.
the main error i am getting is "unable to mount /system; no such thing found" in TWRP
i also tried multiple Supersu files official ones and unofficial ones as well.
after some research i found out about new file system squashfs FS
then i tried this rom which supports EXT4 File System
here is link: https://forum.xda-developers.com/g-watch-r/development/rom-ext4all-g-watch-r-skin1980-t3589917
but it didnot work out as well,(get boot looped)
so flashed stock rom and now on latest update as told earlier,
so its my request, i need help. if someone please come up with any working method to root latest stock rom and security patches(build number and security patch in title)
why stock rom?
i personally like stock rom and it is working fine for me.
why root?
i have root on my phone (one plus one), i felt like i am unable to use my watch on full potential without root.
and we all like root that's why we are here right
thank you
(i actually don't know the how to write any threads so bear with me please) :fingers-crossed:

This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post

Grumps said:
This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post
Click to expand...
Click to collapse
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.

Talwinder8872 said:
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.
Click to expand...
Click to collapse
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...

Grumps said:
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...
Click to expand...
Click to collapse
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,

Talwinder8872 said:
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,
Click to expand...
Click to collapse
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,

Talwinder8872 said:
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,
Click to expand...
Click to collapse
Dont worry be believe you haha

Does iRoot work?

I have just moved to XZ1c from Z3c. Rooting the Z3c was so easy, flashtool, bit of old firmware and an exploit and you were away.
Seems that it's much more tricky now.
There is an 'OEM unlocking' option in the developer options, not sure what that does.
Does anyone know if iRoot works and if it's possible to disinfect your phone and replace it with SuperSU afterwards?
I can see lots a couple of generic Sony 'how to's' in the guides thread, but no feedback from anyone who's done it with a real life XZ1c.

Didgesteve said:
There is an 'OEM unlocking' option in the developer options, not sure what that does.
Click to expand...
Click to collapse
That's to allow you to unlock the bootloader, but with no MM ROM available we're unable to back up DRM keys, but with no TWRP.img as yet either flashing a Superuser.zip might be hard. I'm in no rush to root so haven't tried hotbooting a TWRP.img from another ROM.

Iroot / vroot whatever you call it
not sure what happened with the original software but in the present this is nothing but belated adware and spyware it is pure spy when actually not even as well a virus it will not root but gives a false message that it has rooted and install a bunch of crap well on your PC as well as Android device on Android device it will automatically start downloading a bunch of jar files and install some virus apps Android OS if it is sensitive will complain that this seems to be a Malware none of the virus programs including Norton and other hochos will detect this it has to be manually removed file by file folder by folder do not under any circumstances install this so called rooting software

Yes, iRoot is working 100% fine. Good luck.
(I lied, its a malicious app, stay away)

Dean F said:
Yes, iRoot is working 100% fine. Good luck.
Click to expand...
Click to collapse
This is definitely not true!
There is actual no way to root a xperia XZ1 Compact without unlocking the bootloader.
At the XZ1 section you can find manuals how to get root.
But read them with care, because you loose your DRM Keys and you never get them back!
Here some stuff to read:
https://forum.xda-developers.com/xperia-xz1/how-to/how-unlock-sony-xperia-xz1-bootloader-t3758742
https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375
https://forum.xda-developers.com/xp...nel-sony-xz1-compact-16-january-2018-t3736068

Dean F said:
Yes, iRoot is working 100% fine. Good luck.
Click to expand...
Click to collapse
iRoot is 100% spyware and IMEI cloning
I rooted my phone with Xperiafix, worked perfectly, full stock functions restored. Perect pictures.

I lied.

Didgesteve said:
iRoot is 100% spyware and IMEI cloning
I rooted my phone with Xperiafix, worked perfectly, full stock functions restored. Perect pictures.
Click to expand...
Click to collapse
thanks for the info (and sorry for the earlier typos.... I talk to my phone but sometimes it becomes deaf ... iPhones I have to say Have a sharper pair of ears than do the best Androids )
just wondered if that Xperia fix website is free or paid service I don't mind either way but it just helps to know .. the biggest problem with locked bootloader is that you cannot Mount system as read write and so on reboot even if you rooted you will lose root. this is where I am stuck right now

sieger007 said:
thanks for the info (and sorry for the earlier typos.... I talk to my phone but sometimes it becomes deaf ... iPhones I have to say Have a sharper pair of ears than do the best Androids )
just wondered if that Xperia fix website is free or paid service I don't mind either way but it just helps to know .. the biggest problem with locked bootloader is that you cannot Mount system as read write and so on reboot even if you rooted you will lose root. this is where I am stuck right now
Click to expand...
Click to collapse
Xperiafix is $20. But it comes with support from sToRm// who wrote it. So if you have any issues, you go back to the website and raise a ticket and he'll help you.
Once you have the correct ADB drivers installed (more difficult than it sounds, Windows10 makes this very tricky), it's pretty much automatic. Start the software, follow the instructions.
You end up with the latest TWRP installed and Magisk systemless root. This works on any version of firmware you have installed.
If you want some reading on how to set the drivers up, have a look at the original thread, although this is in the XZ premium forum, the Xperiafix also works on compacts.

Question Hide status bar time clock?

Anybody know how to hide status bar time? In previous android versions,there used to be an option to hide clock but can't find on android 12. BTW, unrooted OnePlus 10 Pro global edition. Thanks

You can use system UI for that

You can use system UI for that

dladz said:
You can use system UI for that
Click to expand...
Click to collapse
I tried to use it but was unable to provide the app necessary permissions. Currently, I am unrooted, adb command mentioned in the app for the required permissions did not work for me. I have been using this app for years but on rooted phones. I will try it again. Thanks
Update: There is another System ui tuner app by Bryan that worked just fine without any permissions

Gr8man001 said:
I tried to use it but was unable to provide the app necessary permissions. Currently, I am unrooted, adb command mentioned in the app for the required permissions did not work for me. I have been using this app for years but on rooted phones. I will try it again. Thanks
Update: There is another System ui tuner app by Bryan that worked just fine without any permissions
Click to expand...
Click to collapse
Yep you'll definitely need to provide them permissions or root.
Is adb working? Can you say adb devices and get a feedback code?
Also why not root? It's a OnePlus, the one phone you can root without repercussions.

I have always rooted my phones for the last 16 years and most likely will root this one too. But quite honestly, at least for my needs, benefits of root vs.complexity of rooting process, steps necessary for each upgrade is not there. Lack of official twrp, issues r/t Titanium backup, etc are not encouraging. That being said, the moment I see a good custom ROM for this phone, I know I will root again. Thanks

Gr8man001 said:
I have always rooted my phones for the last 16 years and most likely will root this one too. But quite honestly, at least for my needs, benefits of root vs.complexity of rooting process, steps necessary for each upgrade is not there. Lack of official twrp, issues r/t Titanium backup, etc are not encouraging. That being said, the moment I see a good custom ROM for this phone, I know I will root again. Thanks
Click to expand...
Click to collapse
Funny you should say that, so have I, and in all honesty you mustn't have seen the guide I made on rooting as it's extremely clear.
Plus as from the 8 pro on wards, you simply do not need twrp, period..it'd be nice to have MSM, but we already have fastboot enhance which is actually better as it doesn't relock the bootloader .
Titanium also hasn't worked correctly for a while, it has issues with restoration.
Swift back up works perfectly for those needs and it can back up to the cloud..
I'm not going to go into the benefits of rooting but just getting rid of ads is massive for me, I couldn't stomach a device which allowed them.
But you do you

ROMs are coming soon btw

Guide to updating, rooting, Magisk and fastboot enhance.
You don't need twrp
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com