[Q] Q: Detection of Rooted Devices by Security Appliances - Droid Incredible Q&A, Help & Troubleshooting

My question is an academic one, of sorts.
My workplace has recently permitted the use of personal devices at the workplace, and they are using a Mobile Iron appliance to "secure" and manage these devices.
A recent change to these appliances resulted in my rooted Incredible being blocked access to the system. The one answer I cannot seem to get a clear response on is how this was detected, as my device had been working in this capacity before a recent change to both the back-end appliance and the client on the device. Clearly, though, this is not the case for all devices, as I know of someone who is still successfully using a rooted Samsung Galaxy S.
I tried a couple of iterations to determine how it detected my rooted device, and, at this point I have returned it to stock with S-OFF. I am pretty confident that the latter is what triggered my device being detected and blocked.
So, anyone have any insight as to how these appliances/devices detect root? Are they inspecting at the hardware level as opposed to a scan of applications?
Looking forward to the discussion.

Assuming superuser no longer on the device?
Sent from my ADR6300 using XDA Premium App

Correct. I returned the device to stock FroYo (2.2), with no SuperUser.

On the sd card there is a log file that says s-off maybe it see that

That must not be the case, as I did not format my SD card when I returned to stock. The soff.log file is still there.
So, perhaps it is not looking at that low a level. Given what I am seeing, though, it is certainly not looking at the applications either.

jasonjthomas said:
That must not be the case, as I did not format my SD card when I returned to stock. The soff.log file is still there.
So, perhaps it is not looking at that low a level. Given what I am seeing, though, it is certainly not looking at the applications either.
Click to expand...
Click to collapse
I'm no expert by any means but I would think that its some type of script that runs asking for access permission to the phone that only a superuser would have. I have an authenticator for a blizzard account that always pops up with a message that running it on a rooted phone is dangerous, so I'm asuming there is some type of script imbedded in the app that lets it know its on a rooted phone by querrying for su access. Why your buddies phone is not being blocked has me stumped.

Related

Is there any way to disable MTP, only charge?

As title.
How can I disable MTP and only charge the phone when connecting it to the USB?
I would like to have this option as well, but I do not believe it is possible.
Curious - what is your reasoning for wanting charge only?
EDIT: The way the "Connect As" UI is set up really bugs me. One would think that since they utilized check boxes on this menu that you would have the option of selecting or de-selecting both options. Oddly enough their check boxes function as radio buttons and you are required to select one or the other...
Enter via adb shell or a term emulator with su privilage:
Code:
setprop persist.sys.usb.config adb
This is temporary and will revert after a reboot. To make permanent you can script this into init.d or edit your default.prop
Sent from my Galaxy Nexus using XDA App
is there any non-root way? i am currently sitting in the library and the girl in front of me lets me charge my nexus on her laptop, but the thought of her beeing able to see all of my photos is kinda discomforting ...
Or you can use Tasker with Secure Settings.
Root! And use a fast charge enabled kernel.
This will also cause your phone to think it's plugged into an AC rather than USB...and thus draw more power.
Jubakuba said:
Root! And use a fast charge enabled kernel.
This will also cause your phone to think it's plugged into an AC rather than USB...and thus draw more power.
Click to expand...
Click to collapse
Exactly. Easiest option.
so that's the reason it takes so long ... but she's gone now and i've found an ac plug. my nexus is just a week old and i don't have had any crashes etc. yet so i won't root in the near future. i rooted my sgs after 6 months and used cm7/9 for another 6 months. this slowly destroyed my internal sd to a point where i only got 70 € for my sgs on ebay ... i think i've learned my lession.
dr_eos said:
so that's the reason it takes so long ... but she's gone now and i've found an ac plug. my nexus is just a week old and i don't have had any crashes etc. yet so i won't root in the near future. i rooted my sgs after 6 months and used cm7/9 for another 6 months. this slowly destroyed my internal sd to a point where i only got 70 € for my sgs on ebay ... i think i've learned my lession.
Click to expand...
Click to collapse
I don't know how you managed that, I flashed my nexus s literally thousands of times, never had a problem.
I honestly don't know how you destroyed the sdcard by flashing a rom.
that problem (which occures more often with the captive) affects some people http://forum.xda-developers.com/showthread.php?t=1447303 there is no permanent solution.
Encryption eh!?!
Seen a couple of threads recently with problems relating to encryption.
Is encryption necessary?
Do you people work for the CIA or MI6 or something?
Are you all guarding information important to national security??
just read the thread, everything is explained there. nobody uses encryption, android "thinks" the internal sd card is encrypted because it cant't mount it.
dr_eos said:
that problem (which occures more often with the captive) affects some people http://forum.xda-developers.com/showthread.php?t=1447303 there is no permanent solution.
Click to expand...
Click to collapse
You will not experience that on Nexus devices as they have unlockable bootloaders which, when unlocked, allow you to use the "fastboot erase" command, which allows you to wipe completely most partitions.
Sent from my Galaxy Nexus using Tapatalk

[Q] Security

I'm interested in hearing about the security that other Android users employ on their devices. I don't ever have anything particularly sensitive on my device, but certainly data and images that I wouldn't want other people to have access to should my device be lost or stolen.
Obviously the first starting point is a lock screen code which I already have in place. I use a four digit pin code, and realise from playing around with it that after five incorrect attempts the device will make you wait 30 seconds before trying again. Is this the only restriction, or does the time get longer, or trigger something else after more attempts?
Secondly, I have a number of photographs stored on the SD card. Thinking about it this is a big security issue as someone could simply take it out of the phone and plug it straight into a laptop and go through the data.
The next issue is the encryption of the phone itself. I know that there is an encryption option built in, but I'm of the understanding that the password has to be the same as the lockscreen code. Which seems far from ideal as a 4 digit pin for the lockscreen code is convenient, but probably not strong enough if you're encryping data.
Finally, the option of a remote wipe. I've used a variety of apps in the past, but haven't installed any since installing my latest ROM. What do people use?
I'm interested to hear any input about what people use on the device, or what ways I could increase the security of my device.
Anyone getting hold of your phone can easily get to your data unless you encrypt them.
The best bet I think would be to install the EDS app or the Cryptonite app (both available on the Play). The latter has the capability to open and mount a Truecrypt container.
(I think you have to create the container first on a PC, but since I don't use Cryptonite, I can't be sure of it).
For remotely wiping your phone, I heard Avast! Antivirus app has the best reviews; and it's free.
Sent from my GT-I8150 using xda app-developers app
pepoluan said:
Anyone getting hold of your phone can easily get to your data unless you encrypt them.
The best bet I think would be to install the EDS app or the Cryptonite app (both available on the Play). The latter has the capability to open and mount a Truecrypt container.
(I think you have to create the container first on a PC, but since I don't use Cryptonite, I can't be sure of it).
For remotely wiping your phone, I heard Avast! Antivirus app has the best reviews; and it's free.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Why do you favour EDS/Cryptonite over the built in Android encryption method. They seem to offer more flexibility to me. Will they encrypt the whole phone, or just a new, special folder? Like an encrypted zip file in a way.
I've installed Avast and am in the process of setting it all up.
creative-2008 said:
Why do you favour EDS/Cryptonite over the built in Android encryption method. They seem to offer more flexibility to me. Will they encrypt the whole phone, or just a new, special folder? Like an encrypted zip file in a way.
I've installed Avast and am in the process of setting it all up.
Click to expand...
Click to collapse
I prefer not all of my SD Card to be encrypted, since encryption is taxing to the CPU. Truecrypt containers will be mounted as a folder, so it's what I wanted: a space to store files which will be encrypted, without needing to encrypt the whole phone.
TrueCrypt also needs to be manually mounted; Android encfs gets automatically mounted on boot.
Plus, TrueCrypt containers have been known to stump even three-letter organizations.
Sent from my GT-I8150 using xda app-developers app
pepoluan said:
I prefer not all of my SD Card to be encrypted, since encryption is taxing to the CPU. Truecrypt containers will be mounted as a folder, so it's what I wanted: a space to store files which will be encrypted, without needing to encrypt the whole phone.
TrueCrypt also needs to be manually mounted; Android encfs gets automatically mounted on boot.
Plus, TrueCrypt containers have been known to stump even three-letter organizations.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thanks for sharing you knowledge with me.
I'm going to give the TrueCrypt approach a go. I'll probably set up a small area on the SD card first with some documents and photos and see how that works out.
There are other areas though that I wouldn't want a thief to have access to, such as my messages or perhaps my recent photos? I assume these can't be stored in the TrueCrypt container, but would be protected by encrypting the whole phone with Android's method.

External SD Card not writeable in TB on 8.4?

I know it's early on but I rooted my Samsung galaxy tab 8.4 and I am trying to do a backup of my apps and I cant do a backup to my external sd card. TB is saying it isn't writeable. I have used the back button and such to manually change the directory. I'm familiar with doing that. I can backup to internal storage but obviously I don't want to waste the space when I have a 64gb micro sd card. Thanks for the help.
bckrupps said:
I know it's early on but I rooted my Samsung galaxy tab 8.4 and I am trying to do a backup of my apps and I cant do a backup to my external sd card. TB is saying it isn't writeable. I have used the back button and such to manually change the directory. I'm familiar with doing that. I can backup to internal storage but obviously I don't want to waste the space when I have a 64gb micro sd card. Thanks for the help.
Click to expand...
Click to collapse
I can confirm the same issue. I've verified that the root directory is set to R/W using "Root Explorer" from the play store. For some reason, I can't get TB to see it as R/W, though.
Saving other items to the external card seems to work just fine. Camera saves there, no issues. Weird.
leatherneck6017 said:
I can confirm the same issue. I've verified that the root directory is set to R/W using "Root Explorer" from the play store. For some reason, I can't get TB to see it as R/W, though.
Saving other items to the external card seems to work just fine. Camera saves there, no issues. Weird.
Click to expand...
Click to collapse
It will get figured out soon enough. im just happy to be able to do a titanium backup. Lots of work installing stuff
I couldn't even create a Nova backup to the external SD card
Sent from my SM-T320 using Tapatalk
CAR1977 said:
I couldn't even create a Nova backup to the external SD card
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
It is a 4.4 permissions issue. I found a possible fix if it works I will post it.
This worked for me. You have to be rooted to do it though.
http://forum.xda-developers.com/showthread.php?t=2617921
nrage23 said:
It is a 4.4 permissions issue. I found a possible fix if it works I will post it.
This worked for me. You have to be rooted to do it though.
http://forum.xda-developers.com/showthread.php?t=2617921
Click to expand...
Click to collapse
Confirmed, this works. Nice find!
Where did you find root?
Sent from my GT-I9505 using XDA Premium 4 mobile app
uberboyd said:
Where did you find root?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Root was achieved yesterday. CF Auto Root
i am rooted and using es file explorer. when i try to save it a box keeps coming up saying an error occurred cannot save.
got it. have to mount the system.
bckrupps said:
i am rooted and using es file explorer. when i try to save it a box keeps coming up saying an error occurred cannot save.
got it. have to mount the system.
Click to expand...
Click to collapse
Root explorer works much better for modifying root directory the ES does.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
Root explorer works much better for modifying root directory the ES does.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Yea thats what i figured out. So nice to be able to back up to the sd card and the process literally took a minute. Cool find.
I was able to fix this issue by simply installing Folder Mount. When you first open folder mount will offer to repair this permission issue for you. I said yes and it worked. Folder mount also stated this is specific to Sammy 4.4 roms... Just an FYI. Thought I would share.
Sent from my SM-T320 using Tapatalk
Unfortunately, it's not something that Samsung decided to do, it's something Google started back in Android 3.2 and is now apparently asking OEMs to follow their lead on - or else the OEMs aren't reading the codebase much, which I think is also a problem.
The external storage permssions were spotted and commented on by Chainfire (he who gave us root, hallowed be his name ) in 2012!
https://www.xda-developers.com/andr...-preventing-write-access-to-external-storage/
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
I'm not 100% on this, but I think that the Samsungs are one of the first sets of devices to get KitKat and to have sdcards. (don't know what the status of the gpad 8.3 is) It will be interesting to see if the Gpad 8.3 does the same thing; I'm pretty sure the Tegra Note did, and then EVGA pulled back on their KitKat update due to bugs, of which this was one (glad they called it a bug, but if they'd looked at the code before implementing the changes...)
This issue goes way beyond the sdcard. Remember when your device could be connected to your computer and turn up as a mass storage device, not a media player or a camera?
The MTP protocol originally implemented by Google was hugely troublesome on that score when it was first introduced. There were absolutely insane failure modes. To get an accurate readout of what was on your device you couldn't disconnect from your computer and reconnect, you couldn't disconnect, reboot the Android device and reconnect - nope, you had to reboot your computer.
I haven't thoroughly tested failure modes but at least the warning on copy from PC to Android works correctly now.
When first implemented by Google, file deletions on in Android were not reported to the computer connected to it if they occurred while connected. So you could move a folder and then try to copy files that didn't exist, and Android wouldn't report the file was not there.
This is an example of silent failure, which is the worst possible failure mode. It gets beaten into the heads (or once did) of programmers that you always produce and report an exception on failure. Not doing so is negligent and might be actionable depending on the context.
I just deleted a file from the Samsung and it's taken more than 30 seconds for the Windows system to get information on what's on the Samsung.
Great - I also couldn't enumerate my local disk drives while I waited, more than 3 minutes (i7-2600k, 8 G ram - not a PC side issue!) I finally disconnected and reconnected the USB cable and was able to get my disks to populate immediately on disconnect, and an accurate poll from the Samsung on reconnect.
I suspect that Google's 'fix' for the not-notifying-on-delete bug is to throw a disk not ready message back at the host system.
So, why does Google not see any of the following as important?
- easy local disk mounting
- viable sdcard use
- well-written MTP implementation
I don't think it's about the cash - sure, Google's selling a few books and a few movies and such, but they're really an advertising broker; the revenue from that isn't why they're worth gazillions.
I think it's actually much more insane than that: Google is all about big data and the supremacy of databases over all else.
Including files themselves - Google wants to drive toward a world where files don't exist, only pointers in databases exist.
http://glasskeys.com/2011/02/28/why-google-uses-mtp-instead-of-usb-file-transfer-on-android-3/
is a perspective on MTP that is essentially diametrically opposed to mine - it's quoting Google as pointing out that there is both simplicity and allegedly a greater degree of security from MTP.
The security comes from the filesystem retaining 'nix style ACLs and helping to maintain sandboxing between applications by not exposing storage as a fat32 filesystem and thereby giving up granular access controls.
---------
(As an example of silent failure that I think may be the subject of civil litigation: the flaw that broke SSL/TLS validation on most Apple devices - phones, tablets and OS X based computers. If you look at the code, it's blindingly clear what happened.
http://appleinsider.com/articles/14...pdate-is-present-in-os-x-fix-coming-very-soon
http://arstechnica.com/security/201...aw-in-ios-may-also-affect-fully-patched-macs/
This flaw may well explain the Snowden documents that indicate that the NSA has access to any Apple device at will. When those documents were first being reviewed, there were two responses:
- it isn't true
- Apple is in bed with the NSA.
Ignoring a bug that easy to spot in a functional test for years tends to make me wonder if the second explanation may not hold water.)
Hopefully this can help someone. I couldn't edit my *.xml file even though I am ROOTED. But I found this:
https://play.google.com/store/apps/details?id=nextapp.sdfix
and it worked!! Now Titanium Backup is able to write successfully to my sdcard.
The app works great. I would recommend it for anyone on 4.4
Sent from my SM-T320 using XDA Premium HD app
PRESOLVED: My Tab is possessed by the devil!
When I tried to write a file to my Galaxy Tab Pro 8.4's external SD card with Astro and it wouldn't work I was flustered. A little research turned up the crippled SD support in KitKat and how to fix things with the simple platform.xml hack. I did that, and all was right with the world again.
Then I got another 8.4, and actually cloned the first one to the second one with a nandroid backup. I also moved my SD card from the first to the second. Eventually I sold the first one and am just left with the second one. But somewhere along the way I lost the ability to write to the SD card, and I can't get it back!
The hacked platform.xml file was of course cloned along with everything else, but it just doesn't work. What's just as bad, or worse, is that apps which should write to external SD even without the hack (and which did, prior to this issue developing), such as Samsung's My Files, and Root Explorer, also are no longer able to!!!!
So to try and fix things, I flashed this ROM to my Tab: http://forum.xda-developers.com/showthread.php?t=2698460 But I still can't write to external SD, even with My Files!
Here's another problem, which may or may not be related: I also can't write to the external SD with the Tab connected to my computer. With a small file, the progress bar immediately jumps to 100% but then freezes and after a long time the copy times out with the message, "The device has either stopped responding or has been disconnected". With a large file the progress bar plods along, first at a normal speed but gradually getting slower and slower, until at some point it stops moving and the copy times out.
Please, I beg of you, help me exorcise my demon Tab!
SOLUTION: Before actually posting this plea for help, I re-formatted my SD card (in the Tab) and all functionality is restored. I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair.
Good on you for posting the problem and the solution. I doubt you'll be the only person to experience this.
Sent telepathically to my Galaxy S4
droidmark said:
... I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair....
Click to expand...
Click to collapse
From that comment it seems we need more bald users as no risk testers.
Sent from my Nexus 10 using XDA Premium HD app
droidmark said:
When I tried to write a file to my Galaxy Tab Pro 8.4's external SD card with Astro and it wouldn't work I was flustered. A little research turned up the crippled SD support in KitKat and how to fix things with the simple platform.xml hack. I did that, and all was right with the world again.
Then I got another 8.4, and actually cloned the first one to the second one with a nandroid backup. I also moved my SD card from the first to the second. Eventually I sold the first one and am just left with the second one. But somewhere along the way I lost the ability to write to the SD card, and I can't get it back!
The hacked platform.xml file was of course cloned along with everything else, but it just doesn't work. What's just as bad, or worse, is that apps which should write to external SD even without the hack (and which did, prior to this issue developing), such as Samsung's My Files, and Root Explorer, also are no longer able to!!!!
So to try and fix things, I flashed this ROM to my Tab: http://forum.xda-developers.com/showthread.php?t=2698460 But I still can't write to external SD, even with My Files!
Here's another problem, which may or may not be related: I also can't write to the external SD with the Tab connected to my computer. With a small file, the progress bar immediately jumps to 100% but then freezes and after a long time the copy times out with the message, "The device has either stopped responding or has been disconnected". With a large file the progress bar plods along, first at a normal speed but gradually getting slower and slower, until at some point it stops moving and the copy times out.
Please, I beg of you, help me exorcise my demon Tab!
SOLUTION: Before actually posting this plea for help, I re-formatted my SD card (in the Tab) and all functionality is restored. I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair.
Click to expand...
Click to collapse
Just wanted to add a postscript for anyone who might have a similar issue. I thought this problem was solved, as described above. Then a few days later when I booted up my tab, the SD card was shown as blank/unformatted. At that point I did some more digging and determined that it was actually a counterfeit 32GB card, based on an 8GB card. Got a refund, threw it in the trash and ordered a new 64GB card. Caveat emptor!

Strange "RootPA" app on my HTC 10. Is it a potential security issue?

Im using a HTC 10 (EU variant). Today i was scrolling through "Netguard" (if you dont know it, its an app to prevent other apps from internet access), since i configured it to show system apps it displays way more apps than the normal app overview in the settings. In there i found an app called "RootPA" and one called "root", which seems strange since i didnt unlock the bootloader or root on my own. The details in the RootPA entry say "com.gd.mobicore.pa", no idea if thats helpfull to determine the origin of this mysterious app.
Can you help me with this?
Did you Google it?
I did, but the results were not realy usefull. I found someone with a modded Galaxy S3 who deleted a RootPA on accident and broke stuff, but that ssems unrelated. Are there any things i could do to find out more about the app installed on my phone without root?
I cant say its something I've ever seen. If this person in the past removed it, and it broke stuff, that would suggest that it may have been a system app and he was rooted. From what I managed to find on google, it is part of a security suite (mobicore) used by networks to monitor what the state of the phone is, presumably incase something happens, and it was the user fault, and they know for a fact because they have logs of what the phone has done.
[ACCESS_NETWORK_STATE] Allows applications to access information about networks
[INTERNET] Allows applications to open network sockets. (i.e send information)
[READ_EXTERNAL_STORAGE] Allows an application to read from external storage.
[READ_PHONE_STATE] Allows read only access to phone state.
A friend of mine got his HTC 10 2 days ago, ill ask him to look for this app. Its unlikely we would have the same virus/whatever installed.
Edit: He just reseted his 10 (due to missing language options, but thats another topic), but still found "root" and "rootPA" on his phone, so its preinstalled (although i still dont understand whats its purpose).
RootPA is provides service for provisioning secure applications that run on ARM trustzone and t-base OS (formerly mobicore). It is preinstalled in some vendors Android devices (search for this string on the internet: htc-devices-to-incorporate-trustonic-t-base-tee), but mostly unused as far as I know. The source code of some versions is available on the Internet (e.g. on github /Faryaab/android_hardware_samsung_slsi_exynos5410/tree/master/mobicore/rootpa).
It has nothing to to with rooting or unrooting the device.
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Illfidusoon12 said:
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Click to expand...
Click to collapse
PA route..... .rootPA ......2 different things. Hacked ? Unlikely, I think some OCD is kicking in. Want to be clean? RUU the device and do not restore anything

Minimal work required to get back my bluetooth tethering? XT1635-02 OTA Nougat

I have determined that I at least will need to unlock my bootloader which I am already loathing since that means everything on my phone will get reset. We also don't even have signed firmware for this device. I don't care about root, but I also don't use any of this pay nonsense. I do play a certain game that will moan about my phone being modified though. I was already looking at the nougat thread regarding root and passing everything but I'm not interested in magisk and the headache that comes with having to deal with safetynet updates.
Far as I understand:
1. Get TWRP, can I get away with just booting it and not actually flashing?
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
2. I guess tomparr's zimage kernel zip found here: https://www.androidfilehost.com/?fid=457095661767134479 is required since the system is going to be changed for what I want to do
3. Steps somewhere a long the lines of this http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
a. Add the net.tethering.noprovisioning=true line
b. Open Terminal emulator on your device and issue the following commands one-by-one:​su
settings put global tether_dun_required 0
exit​
If I am understanding anything wrong or anyone wants to point me at anything else to read that would be great.
[rant] What an annoying experience this has been, before a few hours ago I praised motorola(lenovo) for what an amazing phone this was, that is until I got that ridiculous update pushed to my phone. Yes, it is definitely snappier and more responsive, but I'm not giving up functionality because the developer of the dammed OS caved into pressure from carriers. I bought an unlocked phone an no carrier has any right to restrict any of my phones features just because they think they can. I work in an office where login into the wif is a thing and I will have multiple devices with me sometimes, so I used to just bluetooth tether the other devices from my main phone and not have to deal with mutliple logins, there are also times when out and about where my gf's signal isn't great and she will use my data to be able to keep using her phone. DAMMIT THIS IS FRUSTRATING.... [/rant]

Categories

Resources