Related
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
GatorRuss said:
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
Click to expand...
Click to collapse
Hi! Any luck with beating mobile iron?
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Broadscope said:
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Click to expand...
Click to collapse
I had a similar issue in my non-rooted M8. MI started working after I did a factory reset .
Hello Forum!
In my S3 Neo I would like to use apps like Unlock with WiFi, SkipLock, etc..
Unfortunately, the mobile device repeatedly in a boot loop and is completely blocked. About Samsung findmymobile I can unlock it again. Currently I have rooted the device, unfortunately no change.
Have you an idea where the error is?
I only speak German and hope that Google has my request translated correctly!
Device is a SM-N916S from Samsung (Galaxy Note 4 S-LTE Exynos 5433 ver.) for anyone that's wondering. It's current state : Completely stock with no root. USB debugging disabled. No Samsung Account linked to device. Can't change password through ADM. No more guesses left for the password anymore, any more will reset the phone.
So yeah. For the past few days I've been trying to bypass Android Device Manager's remote "Lock" feature that's meant to keep your data safe from thieves. As for why? Long story short : I tried to pull a prank on my brother by remotely locking his device through ADM. I have since forgotten the password (it was a random combination of letters and numbers that I thought I could remember, but obviously not.) and trying to set a new password through Android Device Manager just gives me the infamous "Since Google has verified that a screen lock is already set, the password you entered won't be needed." error message.
Now, if this was a phone that belonged to me, I would just install a custom recovery and remove the password with a password disable zip, but unfortunately, that is not an option here. I probably forgot to mention that I CANNOT void the warranty (as in trip the KNOX counter) under ANY circumstances and would very much like to avoid a factory reset. Am I out of luck here? Or is anyone here aware of a method that can be used to bypass the ADM lock / or a way to backup data with usb debugging disabled. Thanks.
use smart switch to go back to stock firmware
SrikarPrayaga said:
use smart switch to go back to stock firmware
Click to expand...
Click to collapse
Hi, could you explain what you mean by this? Does smart switch work even when the phone is locked? And what would going back to stock firmware do? Thanks.
Hello group!
I have a question before getting started with my new phone
DETAILS:
from "About Phone"
Android version: 6.0.1
Baseband version: G935VVRU4API3
Kernel version: 3.18.20
Build number MMB29M.G935VVRU4API3
I have not yet entered my google credentials, no wifi access points, and the phone is in "Airplane Mode". I expect that a Verizon system update (to Nougat?) will start soon after I turn off airplane mode & enable wifi.
I HAVE on my Win10x64 computer, properly installed Samsung drivers, installed Samsung Smart Switch, did a test backup (settings only), enabled developer mode (phone) and turned on USB debugging (phone)
I'm upgrading from a rooted Galaxy S4 (running Android 4.3), and although I plan to root my new S7E in the future, I think I will run stock for awhile. Although I did no rom installs on the S4, (had safestrap & a small rom installed in one of the partitions, but rarely used it), I will miss TiBu for a while, Tasker advanced stuff, root options in the AutoApps suite.
I also understand removing bloatware is a little easier these days for unrooted phones.
QUESTION:
Is there any recommendation that I should do/save/copy/settings to this phone before I continue?
After reading the MM & N threads on rooting (great work) I believe I can root in the future using Odin, ADB, etc.
Actually, as I read this, I'm thinking, "This is a stupid question, the phone is unrooted, I can't provide anything useful to the group!"
But, any advice would be appreciated.
Thanks,
Chris
ChrisAC said:
Hello group!
I have a question before getting started with my new phone
DETAILS:
from "About Phone"
Android version: 6.0.1
Baseband version: G935VVRU4API3
Kernel version: 3.18.20
Build number MMB29M.G935VVRU4API3
I have not yet entered my google credentials, no wifi access points, and the phone is in "Airplane Mode". I expect that a Verizon system update (to Nougat?) will start soon after I turn off airplane mode & enable wifi.
I HAVE on my Win10x64 computer, properly installed Samsung drivers, installed Samsung Smart Switch, did a test backup (settings only), enabled developer mode (phone) and turned on USB debugging (phone)
I'm upgrading from a rooted Galaxy S4 (running Android 4.3), and although I plan to root my new S7E in the future, I think I will run stock for awhile. Although I did no rom installs on the S4, (had safestrap & a small rom installed in one of the partitions, but rarely used it), I will miss TiBu for a while, Tasker advanced stuff, root options in the AutoApps suite.
I also understand removing bloatware is a little easier these days for unrooted phones.
QUESTION:
Is there any recommendation that I should do/save/copy/settings to this phone before I continue?
After reading the MM & N threads on rooting (great work) I believe I can root in the future using Odin, ADB, etc.
Actually, as I read this, I'm thinking, "This is a stupid question, the phone is unrooted, I can't provide anything useful to the group!"
But, any advice would be appreciated.
Thanks,
Chris
Click to expand...
Click to collapse
You can try using smartswitch on your phone. Go to to the Samsung apps store and download smart switch. I think that will help you transfer stuff to your new device.
If you are wanting to backup your s7 you need to download smartswitch on your computer and do a backup.
it will save settings, apps, and other things for you.
If you are wanting to restore information onto your phone when you first set it up it should have mentioned something about a transfer where you would've touch the two phones together using NFC and they would transfer settings and other info.
zimgir124 said:
You can try using smartswitch on your phone. Go to to the Samsung apps store and download smart switch. I think that will help you transfer stuff to your new device.
If you are wanting to backup your s7 you need to download smartswitch on your computer and do a backup.
it will save settings, apps, and other things for you.
If you are wanting to restore information onto your phone when you first set it up it should have mentioned something about a transfer where you would've touch the two phones together using NFC and they would transfer settings and other info.
Click to expand...
Click to collapse
Thanks zimgir124,
I did install the smartswitch on the PC, and it backed up both the S4 & S7 pretty well. It would not backup my sms though (perhaps because the file is huge, goes back to 2010)
As for transferring settings, the NFC transfer sounded interesting, but I chose to redo the apps manually. I really wanted to keep only my sms, mms, & call log, so I used MyBackup Pro (since I couldn't use TiBu) which worked splendidly.
Using 4g only (wifi not yet enabled), I re-installed many of the apps individually, & set them up from scratch. Then I started learning the ins & outs of Android 6. This is SO different from the 4.3 I am used to!
Once I was comfortable, I connected to my home wifi network. Sure enough, within 15 minutes, the phone was prompting me to download & update to Android 7.0
To this point, the phone is running very smoothly, and the battery life is pretty good. This is my first android phone where the battery is not user replaceable. I also miss the IR blaster on the Galaxy S4. I saw no reports of it being added to the new S8 (which is why I chose the older, less expensive S7E)
I read your continuing guide on rooting, and I'm sure I'll take the plunge (again)
Again, thank you for your response
Chris
OK guys, sorry I know this has been brought up a bit, but I've been determined to find a solution. I've been trying to get Samsung Pay to work. More specifically because I use it a lot and have a Gear S3 that I want it to work with.
Yes I did research before I rooted, and it appeared there were many solutions to this problem, but I've tried them all and none have worked. I just want to see if anyone at all has got this working. Maybe I can update with different things everyones tried as we go. I feel like there HAS to be a way to make this work. If anyone has gotten this to work in any way, please post!
My Phone: SM-G950F
Knox Status: 0x1 (Faked 0x0 by Magisk)
ROM: Renovate Ice 5.1
CSC Version: SPE (Spain)
From my research, the SPE seems to be open to Samsung pay along with some others. I have encountered different error messages with different combinations of software, hiding Samsung Pay in Magisk, etc. It might just be due to newer and older version of Samsung Pay
Things I've tried:
Fake 0x0 with Magisk, v13.6, 13.7, 14.0
Hide root status with Magisk
1.3.7 Samsung Pay Gear Plug-In (I found somewhere that said this version works, although it just keeps updating for me)
Moved /system/xbin/busybox to SD card
Error message I'm receiving on latest software: Access Denied: Samsung Pay has been locked due to an unauthorized modification. Tap the link below to call customer service and unlock Samsung Pay (RD-SXA).
Note, I have not tried calling customer service yet, that will likely be my next step. I will just tell them I bought the phone on eBay and I'm getting this message. I doubt there is anything they can do, but it's worth a try.
Please don't grill me, I know basically everyone claims this is NOT possible with 0x1 due to hardware fuse, etc. I know this community is strong and I've seen people pull off the impossible before, just hoping to get this to work so my S3 Gear doesn't become a paper weight.
The actual functionalities of Samsung Pay (MST for example) are handled by trusted apps running in secure world. Root in normal world does not affect anything there. Saying that we can fool normal world apps, we still can't fool the TA running in secure world. So even though Samsung Pay app can launch, it won't be able to function in the end.
OK, I have an update. I was able to get Samsung Pay (mobile version) to work! The regular version still gives me an error, but if I launch from my watch, it pulls the mobile version instead.
Here's what I did:
**NOTE: This only works if you have a Gear S3, I have not been able to get the full version of Samsung Pay to work on the phone yet.
1. Boot into recovery
2. Wipe all partitions except the SD Card and OTG
3. Installed Renovate Ice 5.1
4. Select Custom CSC during install and chose "214 Spain"
5. At the end of setup, don't reboot, flash magisk again manually (It's installed in the ROM, however this is the only way I found to get the icon to show up)
6. Open Magisk Manager
7. Click Menu and go to "Magisk Hide"
8. Search for "Pay" and check all apps that show up
9. Update all apps and connect S3 as a new device (you can restore apps/settings)
10. Use root explorer to /system/xbin and move busybox to your SD card (Make sure it doesn't exist on internal storage, if it's present, app will fail)
11. Launch Magisk Manager again and search for "Pay", again make sure all are checked, for me there was another new Gear version that I had to check to hide
12. Reboot the phone
13. Hold down top button on S3 to launch Samsung Pay
14. Proceed through wizard and add a card or "Launch" Samsung Pay on the phone from the S3
15. The Samsung Mobile app should open correctly on the phone and let you add cards etc.
If you try to add busybox back and reboot, it will not work. And again, the actual "Samsung Pay" app on the phone does NOT work, I still get an error. Maybe it's not possible.
schwags said:
OK, I have an update. I was able to get Samsung Pay (mobile version) to work! The regular version still gives me an error, but if I launch from my watch, it pulls the mobile version instead.
...
If you try to add busybox back and reboot, it will not work. And again, the actual "Samsung Pay" app on the phone does NOT work, I still get an error. Maybe it's not possible.
Click to expand...
Click to collapse
Nice findings! So Gear S3 has stand alone pay capability even with non-Samsung devices?
idler1984 said:
Nice findings! So Gear S3 has stand alone pay capability even with non-Samsung devices?
Click to expand...
Click to collapse
I'm not sure about non Samsung devices. All I'm saying is there are 2 versions of Samsung Pay on the S8, one standard version that you would use if you didn't have a Gear S3 and another version that s triggered from the S3 but then runs on phone. That's the one I can get to work.
Sent from my SM-G950F using XDA-Developers Legacy app
Does this method work with renovate 7.2? I have followed the steps and appears denied access
Same problem here, and I live in Spain too!
Does it work with other rom?
I have an sm 930f with 0x1 status, also. since the error message has changed and suggests "call customer service to unlock samsung pay at 0330 726 7729" I just got off the phone with UK customer service.
1. agent didn't know anything about unlocking samsung pay
2. since I reside in the U..S he suggested I had to call U.S customer service which I have already done and they know nothing about unlocking samsung pay. Perhaps there's a change in the works but not yet.
I wonder what happens if the flash counter hits 0x9. One more flash and it hits 0x10 or does it go back to 0x0??