Related
Is it possible to have an unrooted, locked custom ROM? I went back to stock from PA and noticed a drop in performance. However, I need to install Good Enterprise, and it can't be rooted for that.
Thanks
Sent from my Nexus 5 using Tapatalk
What do you mean by a locked rom?
Pretty sure all custom roms are rooted. You may have to stay on stock
Sent from my Nexus 5 using Tapatalk
frozndevl said:
Is it possible to have an unrooted, locked custom ROM? I went back to stock from PA and noticed a drop in performance. However, I need to install Good Enterprise, and it can't be rooted for that.
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You don't need to lock the bootloader, as far as I know programs like Good for Enterprise cannot detect that. I have to run Mobile Iron in it had no idea about the bootloader state.
I run or have run custom ROM's unrooted before. Terminus is the latest one I have run unrooted and had no issues with enterprise setup under mobile iron. I flashed like normal, even supersu and set the phone up using Titanium Backup. Once setup I use supersu complete unrooted function and reboot. Once back up I load up enterprise apps. Haven't had an issue in a long time. Even on custom kernels.
Guess all I need to do is unroot then. Damn, would have saved me a lot of time... At least I'm on lollipop at least now.
Sent from my Nexus 5 using Tapatalk
Sorry, I should have added it doesn't work for all roms. Terminus was just one I could get to work because I don't think he himself modified any system files just let supersu do it. PA, slim, CM may be different as I believe they modify files that mobile iron and the like can detect.
With a shot anyways.
So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.
Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?
Full unroot under the Cleanup section
Sent from my SM-G920F
think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.
Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what
After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F
Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now
I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.
K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.
This probably will be strange question, but I need to try...
My company is using the 3rd party app for access emails from outside network. (you need to have private server inside company, then you will not be able to test it). Issue is that this app does not work on some Custom ROMs.
The developer of this app stated, that app will not work if SuperSU or eXposted is installed and how detection is done is their know-how, so they will not say how it is done. I would be fine with this answer if it would be true.
Here is why I do not believe it is true:
> The app works on any Android 4.4 custom ROM, does not matter if it was rooted or SuperSU was installed
> The app works on any Android 5.0 custom ROM, does not matter if it was rooted or SuperSU was installed
> The app works on some Android 5.1 custom ROMs, but I was not able to figure out why. It work on rooted CM12.1 with SuperSU installed or rooted @temasek Temasek ROM, but it does NOT work on the AICP / SlimLP / Resurection ROMs which all of them include SuperSU
Now I´m on the start line again with Android 6... to find on which ROM the app will work or not...
I already tested these:
> app works on CM13, but this ROM is not so friendly as I used to, I miss a lot of features there
> app works on @temasek Temasek ROM, but almost every second app I try start it FC, so not suitable for use yet
> app does NOT work on @jgcaap [ROM][6.0] CyanogenMod 13.0 Builds [LAG FREE][2015/12/04], ROM not rooted... it required SuperSU to be installed
> app does NOT work on @danieldmm [ROM][CM13][Android 6.0] TugaPower 14.0, ROM not rooted... it required SuperSU to be installed
So, my question is: How the root/SuperSU is handeled by Android 6? I´m not developer, so maybe I´m asking wrong way.
What I would like to understand is, why some ROMs are rooted (have the switch in the Developer menu), when other ROMs require to be SuperSU installed? So, the app works OK on the first "kind" of ROM and it does not on second "kind".
Thank you very much.
Edit: @Heisenberg advised me in past, when I was struggling with A5.1.1 that it might be due to Privacy Guard on Android 5
You are wrong, my rom it's pre rooted with SuperSU 2.56, you can find the acces in Settings, over TugaPower rom.
Enviado do meu A0001 através de Tapatalk
danieldmm said:
You are wrong, my rom it's pre rooted with SuperSU 2.56, you can find the acces in Settings, over TugaPower rom.
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
The problem is that even I did allow the root in the developer menu, the TiberianBackup was still complaining that it cannot get the root access, so I had to install/allow the SuperSU. And then, whey I finally restore the company app from backup ... it doesn't work, probably because the SuperSU.
So, question is why some ROMs can be rooted and no SuperSU is required there (TiberianBackup works OK)?
Examples are: CM12/CM12.1/CM13 or @temasek ROM ... there is no SuperSU and TB still get root access and the company app works there? How come? I would like to understand this :angel:
djha53k said:
The problem is that even I did allow the root in the developer menu, the TiberianBackup was still complaining that it cannot get the root access, so I had to install/allow the SuperSU. And then, whey I finally restore the company app from backup ... it doesn't work, probably because the SuperSU.
So, question is why some ROMs can be rooted and no SuperSU is required there (TiberianBackup works OK)?
Examples are: CM12/CM12.1/CM13 or @temasek ROM ... there is no SuperSU and TB still get root access and the company app works there? How come? I would like to understand this :angel:
Click to expand...
Click to collapse
Maybe because they are using the built in root from stock CM ... And yes over mine, TitaniumBackup work good.
danieldmm said:
Maybe because they are using the built in root from stock CM ... And yes over mine, TitaniumBackup work good.
Click to expand...
Click to collapse
Ahaaaa, so there are differences how to implement the root, ok. Thank you.
So, the company app works only on the "stock CM root", but not on the any other.
Yes, I do not argue with you that TitaniumBackup doesn't work, it works, but both, root and SuperSU, have to be allowed on your ROM.
To be absolutely honest, I like your ROM, but also I need my company app works, but suddenly it doesn't work on your ROM
djha53k said:
This probably will be strange question, but I need to try...
My company is using the 3rd party app for access emails from outside network. (you need to have private server inside company, then you will not be able to test it). Issue is that this app does not work on some Custom ROMs.
The developer of this app stated, that app will not work if SuperSU or eXposted is installed and how detection is done is their know-how, so they will not say how it is done. I would be fine with this answer if it would be true.
Here is why I do not believe it is true:
> The app works on any Android 4.4 custom ROM, does not matter if it was rooted or SuperSU was installed
> The app works on any Android 5.0 custom ROM, does not matter if it was rooted or SuperSU was installed
> The app works on some Android 5.1 custom ROMs, but I was not able to figure out why. It work on rooted CM12.1 with SuperSU installed or rooted @temasek Temasek ROM, but it does NOT work on the AICP / SlimLP / Resurection ROMs which all of them include SuperSU
Now I´m on the start line again with Android 6... to find on which ROM the app will work or not...
I already tested these:
> app works on CM13, but this ROM is not so friendly as I used to, I miss a lot of features there
> app works on @temasek Temasek ROM, but almost every second app I try start it FC, so not suitable for use yet
> app does NOT work on @jgcaap [ROM][6.0] CyanogenMod 13.0 Builds [LAG FREE][2015/12/04], ROM not rooted... it required SuperSU to be installed
> app does NOT work on @danieldmm [ROM][CM13][Android 6.0] TugaPower 14.0, ROM not rooted... it required SuperSU to be installed
So, my question is: How the root/SuperSU is handeled by Android 6? I´m not developer, so maybe I´m asking wrong way.
What I would like to understand is, why some ROMs are rooted (have the switch in the Developer menu), when other ROMs require to be SuperSU installed? So, the app works OK on the first "kind" of ROM and it does not on second "kind".
Thank you very much.
Edit: @Heisenberg advised me in past, when I was struggling with A5.1.1 that it might be due to Privacy Guard on Android 5
Click to expand...
Click to collapse
It works on my rom for a long time.
djha53k said:
but both, root and SuperSU, have to be allowed on your ROM.
Click to expand...
Click to collapse
No, sorry but it's not true, root over my rom it's full controlled by the SuperSU root app and not CM. When was the last time you flashed my rom and wich version? Did you tested run your app with the Xposed module to hide root in Rom?
Enviado do meu A0001 através de Tapatalk
jgcaap said:
It works on my rom for a long time.
Click to expand...
Click to collapse
No, the app does not work on your ROM
danieldmm said:
No, sorry but it's not true, root over my rom it's full controlled by the SuperSU root app and not CM. When was the last time you flashed my rom and wich version? Did you tested run your app with the Xposed module to hide root in Rom?
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
I tested the latest TugaPower 15.0.
Yes, the "root is fully controlled by the SuperSU" is the problem for that app, the SuperSU is detected as security threat and it will not start.
And yes again, the Xposed module is detected by that app too as security threat, so it will not start as well.
So, basically saying, I need to use ONLY custom ROMs, which implement the CM root, no SuperSU or Xposed is allowed.
And there is not many of them and its hard to find one with nice features and cherry-picks.
Question: how do you decide which root will be included in your ROM when you building it?
djha53k said:
No, the app does not work on your ROM
I tested the latest TugaPower 15.0.
Yes, the "root is fully controlled by the SuperSU" is the problem for that app, the SuperSU is detected as security threat and it will not start.
And yes again, the Xposed module is detected by that app too as security threat, so it will not start as well.
So, basically saying, I need to use ONLY custom ROMs, which implement the CM root, no SuperSU or Xposed is allowed.
And there is not many of them and its hard to find one with nice features and cherry-picks.
Question: how do you decide which root will be included in your ROM when you building it?
Click to expand...
Click to collapse
Then you must be doing something wrong... This was the first thing i fixed. use 2.52 version.
jgcaap said:
Then you must be doing something wrong... This was the first thing i fixed. use 2.52 version.
Click to expand...
Click to collapse
OK, gonna test it now... will you posted :good:
Edit: I did tested on the cm-13.0-20151204-jgcaap-bacon.zip ... Downloading the cm-13.0-20151205-jgcaap-bacon.zip now...
jgcaap said:
Then you must be doing something wrong... This was the first thing i fixed. use 2.52 version.
Click to expand...
Click to collapse
Aha, I got it, why it doens't work ...
In TWRP installed:
- cm-13.0-20151205-jgcaap-bacon.zip
- slim pico gapps
But when I pressed reboot I got message> "Your device dost not appeared to be rooted. Install SuperSU now? This will root your device."
So, I have two options...
1) Press> "Do Not Install" ... which will caused that TitaniumBackup will not work, so I will not able to do restore of my apps
2) Swipe> "Swipe to Install" ... which will caused the company app will not work, so I will not able to connect to company emails
Either way is bad for me :crying:
djha53k said:
Aha, I got it, why it doens't work ...
In TWRP installed:
- cm-13.0-20151205-jgcaap-bacon.zip
- slim pico gapps
But when I pressed reboot I got message> "Your device dost not appeared to be rooted. Install SuperSU now? This will root your device."
So, I have two options...
1) Press> "Do Not Install" ... which will caused that TitaniumBackup will not work, so I will not able to do restore of my apps
2) Swipe> "Swipe to Install" ... which will caused the company app will not work, so I will not able to connect to company emails
Either way is bad for me :crying:
Click to expand...
Click to collapse
Download SuperSU 2.52 (not any other version)
Flash zip and have fun.
I'm trying to bring a surprise...
jgcaap said:
Download SuperSU 2.52 (not any other version)
Flash zip and have fun.
I'm trying to bring a surprise...
Click to expand...
Click to collapse
OK, downloaded the BETA-SuperSU-v2.52.zip, so I'm gonna re-flash it again:
- cm-13.0-20151205-jgcaap-bacon.zip
- Slim_zero_gapps.BETA.6.0.build.0.x-20151203.zip
- BETA-SuperSU-v2.52.zip
but I'm skeptic... as the company app detect for SuperSU and Xposed... so, even the TB will work OK, the mail will NOT
... BRB...
jgcaap said:
Download SuperSU 2.52 (not any other version)
Flash zip and have fun.
I'm trying to bring a surprise...
Click to expand...
Click to collapse
Nope, doesn't work :crying:
As expected... app crashed once I enter password... as before or on any other ROM with SuperSU installed
So, let's test another ROM...
Installing the One+ VM13 Android 6.0 Rom for the One by @vinman12... no SuperSU required, so hopefully my company app will works... all fingers crossed...
I really like to know/understand how the root works here ...
djha53k said:
So, let's test another ROM...
Installing the One+ VM13 Android 6.0 Rom for the One by @vinman12... no SuperSU required, so hopefully my company app will works... all fingers crossed...
I really like to know/understand how the root works here ...
Click to expand...
Click to collapse
If you don't flash su then be sure to turn it on in developers options. Also if you don't flash su the su in vm13 tweaks will not work it will just restart the ui. If you do flash su then the su in vm13 tweaks will open su app.
Did you get that
Sent from my A0001 using Tapatalk
vinman12 said:
If you don't flash su then be sure to turn it on in developers options. Also if you don't flash su the su in vm13 tweaks will not work it will just restart the ui. If you do flash su then the su in vm13 tweaks will open su app.
Did you get that
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm not care so much about the "vm13 tweaks", my MAIN issue is to make the company app works and IT IS working, huray :good:
And your ROM has other features which I like, such as: auto unlock once I enter correct PIN, custom-able tiles, etc... :victory:
Thank you :good:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
Remove s health and install like a normal app a older version.
Enviado do meu SM-G930F através de Tapatalk
Basically, what vladmir said. S-Health disables services if you're rooted starting from version 5, so any previous versions will not have this problem. Just Google S-health APK 4.9 or something like that, and install.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 Works well thanks to CuBz90
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
It works just fine on Marshmallow, but if you upgrade to Nougat then you need a custom ROM to make it work.
Removing it and installing it as a non-system app doesn't seem to change anything, and installing an older version didn't help me either.
I've downgraded to 6.0.1 so it doesn't really affect me any more though.
It is very simple to make SHealth working.
First root your device with Magisk using this thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk is able to hide itself from a lot of apps, which won't run if your phone is rooted (i.e. Pokemon go, Mario run...)
If Magisk won't help you then:
install file explorer, it can be ES file explorer,
enable root explorer option (in ES file explorer)
go to /system directory
edit file build.prop
Look for ro.config.tima=1 and change the value to 0
reboot phone and now SHealth will work perfectly
Hello there fellas!
I've recently become owner of the Moto One Vision, just finished installing Magisk & disabled encryption.
Coming form a Xiaomi, the process to update (OTA) involved switching partition and restoring original boot-img of previous version through Magisk, but how do you handle it on this device?
I've only found this comment, do you know if this way to update keeping root is still working? or is there another method?
Also (off-topic), do you know if there's any magisk module (or xposed framework) that lets you control the gesture dead zone area? I only want to activate the back gesture if I'm doing it on the lower half of the screen.
Thanks for the hand ^^
Regards!
nehuy said:
Hello there fellas!
I've recently become owner of the Moto One Vision, just finished installing Magisk & disabled encryption.
Coming form a Xiaomi, the process to update (OTA) involved switching partition and restoring original boot-img of previous version through Magisk, but how do you handle it on this device?
I've only found this comment, do you know if this way to update keeping root is still working? or is there another method?
Also (off-topic), do you know if there's any magisk module (or xposed framework) that lets you control the gesture dead zone area? I only want to activate the back gesture if I'm doing it on the lower half of the screen.
Thanks for the hand ^^
Regards!
Click to expand...
Click to collapse
Good afternoon,
There is an update here: https://forum.xda-developers.com/showthread.php?p=82629961
Regards
Enviado desde mi unknown mediante Tapatalk