Related
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
I think it's all about what you do with a rooted phone that either makes it a full time job or not just to keep it up and running smooth. Me for instance could really care less about custom roms and what not. I like root just for removing bloatware to make the phone and battery better. And in the case of the AT&T s5 the ability to change my default storage to the external sd card. Once that is done I tweak with it for a week or so finding the best performance settings and enabling tether and then I just leave it alone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I rooted and installed xposed/wanam and no problems whatsoever.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
No issues here, I was happy to root and remove the att and samsung bloatware.
I am also not a fan of touchwiz and that will take a while before we have an unlocked boot loader and are able to load custom roms..
To each their own it is no more of a pain in the ass to run a rooted phone vs a non rooted phone. Im at a loss as to why you think it was that much trouble?
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
I understand where you are coming from, I enjoy root for the ability to use Tibu and remove bloat. I also was like you I had a granfathered plan since 1997, the BellSouth mobility day's. I just recently changed to the Mobile data share plan, after analyzing my data usage for the last couple of years I realized my data was under 12 gigs a month for the whole family. I signed up for the 15 gig data share plan have saved $ 40 dollars or more per month. Just a heads up you may want to look into it. Oh and as for tethering it is included in the mobile data share plan.
I assure you that Xposed and Wanam definitely interfere with some of the phone's processes. In fact, there's a whole thread here that describes the steps you have to take to remove the lag on your phone and allow you to use S Health (which I do). But then, other things get screwy, because the ro.securestorage.support property is set to true because other processes rely on it, so now I have a whole slew of other issues that arise from it.
I can tell you from the outset, all I did was root, install xposed, install wanam, and installed the ISIS Root Bypass module, and then all these issues came from that. I just felt it wasn't worth it, and I can easily freeze/disable/turn off the bloatware so I don't have issues with that, per se.
--Q
The stuff I really wanted root for doesn't cause any ongoing weirdness. I was getting along ok without root but I am a LOT happier now:
- permanently disable the annoying, super-loud boot sound without having to resort to workarounds
- disable the tether provisioning check (my plan includes tethering, but on more than one occasion the provisioning check failed and told me to try later)
- full use of BBS and Greenify to monitor/tame battery suckers
- TiBu for freezing (I don't attempt to delete the bloatware) and backups too
- sdfix to gain full access to my sd card
To me, all of that stuff with the exception of the tether provisioning check really should be possible for everyone if they want it. And the tether check could at least reasonably cache your status.
xposed modules are probably the biggest culprit in rooted-user problems (even more than people deleting stuff they shouldn't), and while I love a lot of the customizations xposed allows (a big one for me was being able to show the setting in the messaging app that says not to turn on the screen when a message comes in - no more pocket-crap for me!), I could live without that. The one xposed module I would say I might miss is Xprivacy. I'm relatively conservative in what I block, but it is amazing the info our apps can have access to.
jdock said:
The stuff I really wanted root for doesn't cause any ongoing weirdness. I was getting along ok without root but I am a LOT happier now:
- permanently disable the annoying, super-loud boot sound without having to resort to workarounds
- disable the tether provisioning check (my plan includes tethering, but on more than one occasion the provisioning check failed and told me to try later)
- full use of BBS and Greenify to monitor/tame battery suckers
- TiBu for freezing (I don't attempt to delete the bloatware) and backups too
- sdfix to gain full access to my sd card
To me, all of that stuff with the exception of the tether provisioning check really should be possible for everyone if they want it. And the tether check could at least reasonably cache your status.
xposed modules are probably the biggest culprit in rooted-user problems (even more than people deleting stuff they shouldn't), and while I love a lot of the customizations xposed allows (a big one for me was being able to show the setting in the messaging app that says not to turn on the screen when a message comes in - no more pocket-crap for me!), I could live without that. The one xposed module I would say I might miss is Xprivacy. I'm relatively conservative in what I block, but it is amazing the info our apps can have access to.
Click to expand...
Click to collapse
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used? I guess the real litmus test here is if my car's bluetooth doesn't get all EFFED up on the phonebook. The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
--Q
PS - I'm not a newb user here...been delving into the guts of phones back when I had the old school Windows Mobile devices
quordandis said:
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used? I guess the real litmus test here is if my car's bluetooth doesn't get all EFFED up on the phonebook. The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
--Q
PS - I'm not a newb user here...been delving into the guts of phones back when I had the old school Windows Mobile devices
Click to expand...
Click to collapse
The only thing I did after I rooted my phone was to get rid of the boot sound and used sdfix to be able to use my sd card. But I was having random problems with some apps not working. I would have to uninstall the app and reinstall it to get it to work again. This was really annoying since I was on a trip and really needed to use the apps without all the bother. So I decided to install xposed to try to fix the problems I was having. That just made everything worse--more apps that I use a lot stopped working. After that I used Kies3 to get back to unrooted stock and reinstalled all my data from backup. I am using silent boot to get rid of the boot sound and adjusting to the way I have to use my sd card now. I plan to wait a while before I try root again.
This will be my first smart phone that I am using unrooted. But everything is working now and I have the most annoying things fixed without root.
Sticking with root. Agreed that it's what you do after root that messes things up. Sometimes when you have the power, you don't stop to think whether you should make changes. Unfortunately the phones are built now where many apps have their hands in others to make the user experience "better". The users in this instance are the general masses who just want a phone to work by statistics. It fails to acknowledge that some people think differently. Sometimes I pick up my sister's phone and wonder why she would have the launcher do what she did but that's her phone.
Would I un-root? That's a firm no good buddy. I appreciate everyone's input in making the rooting process less of a landmine but I would never give up the ability to do what I want at, the time that I want. The first thing I did was freeze att.update.software among other att software. (To the author of the post, att did a pretty good job in making everything work in it's first iteration). Then on to battery extending, greenify and wakelock detector. Finally I will delve into customizing my UI but like the author said, Touchwiz doesn't bother me that much, I just sped things up in the developer's option. Because I'm not a heavy phone user I am now getting about 3 days from my charge and still able to get my message updates albeit on my terms, not pushed to me. Also, not having to see ads anymore? Priceless.
And because of everyone else's efforts, I can still go into UPS in case of those times that I find I can't get access to a charger, which now a days, is not that often.
quordandis said:
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used?
Click to expand...
Click to collapse
For the sd permissions I used this sdfix app from the play store. There are several and they just edit /system/etc/permissions/platform.xml for you, so you could do it manually too.
I have to admit, for the tether provisioning, right now I'm using the option in Wanam Xposed just because it was quick. Supposedly the X Tether module works too. A non-xposed method is here but I didn't try it since the xposed module worked. On my old phone it was as simple as using an sql editor to change the entitlement_check setting in /data/data/com.android.providers.settings/databases/settings.db - I don't see that in the GS5, but it may be that the default is 1 and just adding it with a value of 0 will work.
Another idea I hadn't tried (no need to) was the old standby wifi tether for root users app; it might not work as-is for the GS5 but it's just a frontend for a couple of scripts that might be fairly easy to get working since the basic idea is the same and not magic at all (load the wifi device modules, start the wpa_supplicant on it, start a dhcp server on it, setup routing/iptables, and off you go - none of that needs to check to see if you're allowed; the obvious downside is no fancy gui to start/configure/monitor it). On my old phone, I used this as a framework for my own script that brought wifi up simultaneously with mobile data - not operating as a hotspot, but connecting to my home wireless - and then I could run a socks proxy on my phone and use that from anything on my home network, wireless or wired.
The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
Click to expand...
Click to collapse
That is weird, and if the only thing you did was root, I can't see any reason for something like that to happen.
Edit: this thread has another method for disabling the provisioning check, which looks like a great way if you don't want to use xposed or modify framework.apk.
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
It takes time to learn what you can and can't tweak once you have "root", each device is different, each users needs are different. Where battery life and de-bloating may important to one it might very well be insignificant to another, Development is time consuming and with xPosed and the modules that go with it every time Google comes out with an updated OS or Samsung, HTC,LG or Motorola come out with a device it requires the devs to step back and re-evaluate the code and make appropriate adjustments for the best behavior, modifications for compatibility or in the worst case scenario a complete re-write. We all read (or should read) the disclaimers with every tweak or mod we do and as always if it doesnt work or causes bad behavior we can remove it.
I had small issues at first. Then I used Kies 3 to restore. Started over and immediately rooted. Installed Xposed and all 6 of my favorite Modules. Also did the Tool Kit (Dev Sec) Phone is flying fast and has great battery life. I have no issues at all.
I love root......(( I have the s 5 Active ))
I guess I'm a very conservative rooter. I don't freeze apps unless I know what they are, so there's some on the "safe to freeze" list that I still have enabled. After having CM running on my Galaxy S II Skyrocket for so long, I was really impressed with the S5. Really the only thing I missed was AdFree Android. However having CM made my Skyrocket last a lot longer than it would have on the stock ROM, I only upgraded because the hardware started getting wonky.
So after root, I've only installed AdFree, SDFix, and froze a few bloat apps that were persistently in the running apps list that I couldn't disable in stock form. Really helped with battery life too, I can't use phone much during the day due to my job, but battery life jumped from 75-80% at the end of the day to around 90% if I don't touch it (~85% if I check FB during lunch for a few minutes).
There's a few more tweaks that I would like, but seeing all the issues with Xposed, I'll either deal or figure out a manual change at some point. Maybe I'll research what the ro.securestorage.support module is, since disabling it is really why I haven't tried Xposed. (Yes, I wanted root access, but I don't want to make my phone any less secure than I have to.)
tl;dr If you like the phone is stock form, go easy on the modifications after getting root.
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
Wow, I completely 110% disagree with everything you have mentioned here, this has not at all be my experience at all but then again I'm tech savvy. If I were you I would be buying apple products. I for one of the opinion, if I cant root it, I don't want it and won't pay money for it. That goes for knox 0x1 bootloaders as well. Samsung won't see another dime from me again!
Sent from my iPad using Tapatalk
I'm rooted. I froze at&t's crap, chat on, hangouts, and google+.
freezing ANYTHING Samsung seems to create a huge mess on this device.
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Spot on
Sent from my SM-G900T using Tapatalk
barondebxl said:
Spot on
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Apparently, not entirely true. Here's one for you:
Pre-root, the phone connects just fine via bluetooth to my car. Upon initial pairing, I get a request to allow reading of contact list, phone history and messages. I agree. Car syncs contacts and saves to internal car temp memory (this sync occurs each time the car is turned on and the BT connection is established). Activate voice recognition to "Call Home" - car confirms with audible prompt "Call Home. Say yes, no or correction" to which I would reply "Yes" and then the car would call the contact labeled as "Home" on my phone which it synced.
Now, run towelroot, reboots phone with JUST root (su binary). Phone loads up just fine. Car establishes bluetooth connection. Tell it to "Call Home" everything proceeds as expected. I confirm with "yes" and it proceeds to dial a completely different phone number even though the voice prompt confirmed that I indeed wanted to call "home."
Ok - so I unpair the car from the phone, and delete the phone profile from the car. Decide to start from scratch. Phone pairs with the car and I allow the syncing of contacts, etc as was the case pre-root. Attempt to "Call Home" again and the same weird phenomenon occurs where it will confirm it's calling home, then proceed to dial a completely different contact. Ok. I clear the phonebook and force it to resync the contacts. Same issue. Ok. Unpair car from phone, delete phone from car.
Reboot phone into stock recovery and wipe cache. Try pairing again and do the whole shebang. SAME FREAKING ISSUE WITH THE CONTACT SYCN. Meanwhile, ONLY rooted the phone with the added su binary. No other root-enabled apps installed or used. Haven't even USED su yet to do anything other than run "adb shell" and confirm su works. (didn't even install a root checker).
I decide to UNROOT by installing supersu then using it to unroot. Reboot, unroot successful, no su binary, and remove supersu. Pair phone and car again, go through the steps and lo' and behold! CONTACT SYNC WORKED AND CAR DIALS APPROPRIATE CONTACT.
So, in reference to
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- that's probably true in most cases, just not in this one. I'm not saying it's the root per se, but certainly something about the su binary or how the phone gets rooted through the exploit or something definitely screws something up.......
quordandis said:
Apparently, not entirely true. Here's one for you:
Pre-root, the phone connects just fine via bluetooth to my car. Upon initial pairing, I get a request to allow reading of contact list, phone history and messages. I agree. Car syncs contacts and saves to internal car temp memory (this sync occurs each time the car is turned on and the BT connection is established). Activate voice recognition to "Call Home" - car confirms with audible prompt "Call Home. Say yes, no or correction" to which I would reply "Yes" and then the car would call the contact labeled as "Home" on my phone which it synced.
Now, run towelroot, reboots phone with JUST root (su binary). Phone loads up just fine. Car establishes bluetooth connection. Tell it to "Call Home" everything proceeds as expected. I confirm with "yes" and it proceeds to dial a completely different phone number even though the voice prompt confirmed that I indeed wanted to call "home."
Ok - so I unpair the car from the phone, and delete the phone profile from the car. Decide to start from scratch. Phone pairs with the car and I allow the syncing of contacts, etc as was the case pre-root. Attempt to "Call Home" again and the same weird phenomenon occurs where it will confirm it's calling home, then proceed to dial a completely different contact. Ok. I clear the phonebook and force it to resync the contacts. Same issue. Ok. Unpair car from phone, delete phone from car.
Reboot phone into stock recovery and wipe cache. Try pairing again and do the whole shebang. SAME FREAKING ISSUE WITH THE CONTACT SYCN. Meanwhile, ONLY rooted the phone with the added su binary. No other root-enabled apps installed or used. Haven't even USED su yet to do anything other than run "adb shell" and confirm su works. (didn't even install a root checker).
I decide to UNROOT by installing supersu then using it to unroot. Reboot, unroot successful, no su binary, and remove supersu. Pair phone and car again, go through the steps and lo' and behold! CONTACT SYNC WORKED AND CAR DIALS APPROPRIATE CONTACT.
So, in reference to - that's probably true in most cases, just not in this one. I'm not saying it's the root per se, but certainly something about the su binary or how the phone gets rooted through the exploit or something definitely screws something up.......
Click to expand...
Click to collapse
]
Dunno whats wrong with your setup, but my rooted phone works fine in my wife's Ford and my Subaru.
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Am I the only one that this affects?
Or do some people in this community use a custom Rom that avoids this issue. Any response would be greatly appreciated.
Yeah this sucks, hopefully someone will figure out a work around.
Sent from my SCH-I545 using XDA Free mobile app
kirbnite said:
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Also having this issue and I am pretty pissed off about it. This was the only way for me to watch my beloved Denver Broncos out of network without paying over $100/month for tv I dont need or want.
kirbnite said:
Am I the only one that this affects?
Or do some people in this community use a custom Rom that avoids this issue. Any response would be greatly appreciated.
Click to expand...
Click to collapse
It's affecting everyone - /r/Chromecast/comments/2isxbo/nfl_mobile_no_longer_casts_video/ (I can't post links?)
The change appears to have gone into affect at least yesterday.
It went into affect the moment I updated the NFL Mobile app on 10/6/2014. I am thinking, something could be done. If ruining a custom ROM, couldn't there be a way to ensure what ever flagged is engaged when the Cast Screen sevice is used to always show as off, so nfl mobile does not know it is being used.
This also affects the Samsung Allshare media cast device. (Mirror mode on my Note 3).
kirbnite said:
It went into affect the moment I updated the NFL Mobile app on 10/6/2014. I am thinking, something could be done. If ruining a custom ROM, couldn't there be a way to ensure what ever flagged is engaged when the Cast Screen sevice is used to always show as off, so nfl mobile does not know it is being used.
This also affects the Samsung Allshare media cast device. (Mirror mode on my Note 3).
Click to expand...
Click to collapse
Makes sense. I did try the factory reset but the app says a new update is required...so I'm guessing rolling it back to the pre-10/6 version wouldn't work.
I believe a similar workaround was developed into custom ROMs for hiding HDMI connections but after searching online I can't find anything that references a similar cloak for the screen cast service.
Now, I am not opposed to rooting my phone and using some hdmi adapter. Anyone confirm if there is a ROM that allows the NFL Mobile to stream to the TV in any means necessary.
kirbnite said:
Now, I am not opposed to rooting my phone and using some hdmi adapter. Anyone confirm if there is a ROM that allows the NFL Mobile to stream to the TV in any means necessary.
Click to expand...
Click to collapse
Supposedly the play store app no longer has rooted phone detection, but that update was about a year ago - http://forum.xda-developers.com/showpost.php?p=45088481&postcount=244
kirbnite said:
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm far from an expert on this matter, but it seems to me it has something to do with the permissions enabled by the NFL Mobile app. With screen cast/mirroring, you connect these devices wirelessly and you may need to cloak this connection in order to throw off the NFL app? In any event, I'm having the same issue and was hoping someone could help.
A work around includes an app called screen stream mirror. NowI don't have the link to it, but it requires root. It can be used with a chrome cast to allow you to watch video which you normally wouldn't be able to. Cost is $5.00.
What's this teensie I've read about? Hacking your chrome cast, anyone heard about it?
Thank You. I will be making some modifications
Re:
NFL mobile app now checks to see if the phone has been rooted and/or has the developer options turned on. In either case it will not allow streaming to a bigger screen. Back in August 2014 they banned rooted phones altogether from watching preseason games, then because of an outcry, they have allowed them back in partially to watch from the phone but not project onto a big screen. They also have put a DRM protection in so you cannot set up a mock location with a gps spoofer app.
No audio with the "Screen stream mirror" app.
Sent from my SCH-I545 using XDA Free mobile app
Bradleyd444 said:
No audio with this app
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
It works. If you are rooted, it stands the audio. If not, microphone. Either way, Just enable it in the settings.
kirbnite said:
It works. If you are rooted, it stands the audio. If not, microphone. Either way, Just enable it in the settings.
Click to expand...
Click to collapse
I am rooted, I did enable system sounds but it does not work.
Sent from my SCH-I545 using XDA Free mobile app
Email the developer. They will work with you.
If your audio does not work, I would assume 1 of 2 things.
1. Your media volume on your phone is turned all the way down.
2. Running a custom ROM that is interfering with how the application works.
Does the audio fall to transmit with every application you open on your phone?
Galaxy S4 Google Play Edition, audio plays on the phone but does not cast with the video, have not tried other apps.
Sent from my SCH-I545 using XDA Free mobile app
no sound
I have a Verizon Galaxy S4 and had the same problem. The recommendation that worked for me was rebooting the Chromecast - just unplug then reconnect the power to the Chromecast unit, wait for it to cycle back up and try again.
Three apps installed themselves without my intervention:
Cookie Jam
Drippler
RetailMeNot
They didn't come preinstalled, but just installed themselves today. I was able to uninstall them but they keep coming back.
Any idea what's going on? They do not show up under My Apps in the play store, but I can uninstall them through settings. I did a factory reset and didn't install anything and they still come back.
Mine just did the same thing also. Just got it two days ago too. I've uninstalled them now, and they haven't come back yet, but that is disturbing if you say gotta keeps coming back.
Forgot to mention this, I've already disabled the other app stores except for the Google play store.
Just happened to me as well. Thought I was the victim of some new exploit.
This just happened to me, and it is driving me nuts. I think I tracked it down to a program called DTIgnite. Somehow, a sight I visited or a link I clicked installed this program which essentially gives the controller a backdoor to install anything they want. I dont recall it being in the file directory before, but its there now and it survives a factory reset. Mine started doing it yesterday and I have done about 2 dozen factory resets trying to narrow down the problem I was able to determine that it only downloads these programs (the same thee mentioned) when the sim card is inserted. Without the sim card, and with an active wifi connection, it does not do it. The moment it gets a carrier signal, it begins downloading those three apps in the background. I went to tomobile and got a new sim card, and it still does it, but not if I put the sim card in a different phone. So it lies within my note 4 not my account or the sim card. Furthermore, if you factory reset without the simcard, DTIgnite does not appear in the file directory. Once it is inserted, DTIGnite downloads itself and then these three programs. This leads me to believe that what ever site I visited or clicked on, rooted my phone. Because, how else would it survive a reset unless it was in the root directory?
Now DTIgnite is an app developed by a firm that tries to market its capabilities to carriers in order to give them backdoor access to phones. I think its possible someone licensed the software and repurposed it to install bloat ware of their own for third party companies for profit.
In anycase, because of my work, I cannot have a compromised phone and must replace it now. Thinking about contacting a lawyer and seeing what can be done to the company that makes DTIgnite
raptir said:
Three apps installed themselves without my intervention:
Cookie Jam
Drippler
RetailMeNot
They didn't come preinstalled, but just installed themselves today. I was able to uninstall them but they keep coming back.
Any idea what's going on? They do not show up under My Apps in the play store, but I can uninstall them through settings. I did a factory reset and didn't install anything and they still come back.
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:22 PM ----------
IDIgnite is indeed the problem. I reformated without the Sim, and then without logging into any account I checked the app manager. Within, is DTIgnite, but once it is "turned off" you can insert the sim card and it will not resinstall those three programs. However, this app is not preinstalled which means each one of us clicked on a link that silently downloaded it. Furthermore, I suspect it has been placed in a safe partition on the device or on the ROOT directory itself because it survives a factory reset.
I dont know how to check if my device is rooted, but when I boot in recovery mode it lists me in # manual mode# and I seem to remember the # symbol was significant in the root determination discussion. Again, I am no expert on the matter; so, I can be completly off base here. I recomend you research my findings on your device to see if they are compromised as well.
Now, I just contacted Mandelay Digital, the publically traded company that authors DT Ignite, and let them know that on monday I will consult an attourney regarding there neglegent distribution of their software and have requested they provide steps to uninstall. after my discussion with an attourney, I may come back here to post information regarding a class action if it is feasible.
Well I know you guys have heard this before but porn sites are bad. Lmao. When ya guys click u may be given consent to those other apps to self install. You would have to prove that you did not give consent
BAD ASS NOTE 4
cirrob said:
This just happened to me, and it is driving me nuts. I think I tracked it down to a program called DTIgnite. Somehow, a sight I visited or a link I clicked installed this program which essentially gives the controller a backdoor to install anything they want. I dont recall it being in the file directory before, but its there now and it survives a factory reset. Mine started doing it yesterday and I have done about 2 dozen factory resets trying to narrow down the problem I was able to determine that it only downloads these programs (the same thee mentioned) when the sim card is inserted. Without the sim card, and with an active wifi connection, it does not do it. The moment it gets a carrier signal, it begins downloading those three apps in the background. I went to tomobile and got a new sim card, and it still does it, but not if I put the sim card in a different phone. So it lies within my note 4 not my account or the sim card. Furthermore, if you factory reset without the simcard, DTIgnite does not appear in the file directory. Once it is inserted, DTIGnite downloads itself and then these three programs. This leads me to believe that what ever site I visited or clicked on, rooted my phone. Because, how else would it survive a reset unless it was in the root directory?
Now DTIgnite is an app developed by a firm that tries to market its capabilities to carriers in order to give them backdoor access to phones. I think its possible someone licensed the software and repurposed it to install bloat ware of their own for third party companies for profit.
In anycase, because of my work, I cannot have a compromised phone and must replace it now. Thinking about contacting a lawyer and seeing what can be done to the company that makes DTIgnite
---------- Post added at 11:01 PM ---------- Previous post was at 10:22 PM ----------
IDIgnite is indeed the problem. I reformated without the Sim, and then without logging into any account I checked the app manager. Within, is DTIgnite, but once it is "turned off" you can insert the sim card and it will not resinstall those three programs. However, this app is not preinstalled which means each one of us clicked on a link that silently downloaded it. Furthermore, I suspect it has been placed in a safe partition on the device or on the ROOT directory itself because it survives a factory reset.
I dont know how to check if my device is rooted, but when I boot in recovery mode it lists me in # manual mode# and I seem to remember the # symbol was significant in the root determination discussion. Again, I am no expert on the matter; so, I can be completly off base here. I recomend you research my findings on your device to see if they are compromised as well.
Now, I just contacted Mandelay Digital, the publically traded company that authors DT Ignite, and let them know that on monday I will consult an attourney regarding there neglegent distribution of their software and have requested they provide steps to uninstall. after my discussion with an attourney, I may come back here to post information regarding a class action if it is feasible.
Click to expand...
Click to collapse
It's really not a big deal.
For starters, a random piece of adware did NOT root your device. In order to root, you would need to run commands and codes into your device using a program called ODIN, and unless your phone rebooted, showed a red system menu, then rebooted itself again, it was not rooted. You would also have a root access application like SuperSU or SuperUser.
*****
There's 2 ways to go about fixing the adware...
1. Factory Reset, THEN ODIN back to factory stock, the files (from root accessed files and normal files alike) will be entirely resetted to how the stock .img was created.
2. (Easier way) Root, use Titanium and uninstall the adware application causing the problem. Seeing as I've never had adware on my device, I feel this way would only be a temporary fix.
Needless to say, fix #1 is preffered.
If this is an issue for you (novice problems might I add), use an antivirus designed for your device. There are multiple options in the Play Store.
And a side note for ya, this will not stand up in court, this wouldn't even make it to court; in any way possible. If a lawyer had a nickel for anyone who has ever had adware on their devices that was trying to take a company to court to get some kind of settlement or resolution, lawyers would be very rich people.
You visited a site that infected your device with adware. (Probably pornographic). You'll be wasting your time and money. Based on the fact that you went to the extent to call them and threaten them is even worse, almost childish. They don't care, they probably get calls like that all day, every day.
This is not some random anomaly, it's a virus that was installed into your device due to your Internet browsing / downloading habits.
*****
When you see **** on the ground, rather than yelling at it and rolling around in it, just pick it up and be done.
Same thing happened to me today. I formatted the phone using TWRP and reinstalled stock using Odin. The sim was still in the phone. As soon as the phone connected to the cell network these apps came back!
Next try was to reflash stock with the sim out. The apps were not there. After routing the phone I uninstalled /system/priv-app/Ignite_TMO.apk which is the package for IDIgnite. Thankfully, these apps have not returned since.
What I found odd was that even stock image did not remove these. I did ensure that the microsd card was also not present in the phone so these apps are definitely stored in the internal partition somewhere.
Why are we assuming this is an exploit rather than something T-Mobile shipped in a recent ROM update or in the original image in order to install these bloatware apps?
I think it might be in the ank4, because I just got these when flashing an ank4 Rom.
I know for sure I didn't have them before.
Sent from my SM-N910T using Tapatalk
Unauthorized Apps Downloaded to T-Mobile Samsung Note 4.
I have a T-Mobile Samsung Note 4 which updated on Wednesday, November 26, 2014. Just a few minutes ago, I turned my phone off, then turned it on again and noticed on the status/notification bar a triangle with exclamation mark... and when I pulled down screen it was for 2 apps warning that these apps have high permissions. I did not add these apps and when I looked at my apps I noticed the same 3 listed here were installed on my phone. Cookie Jam (high permissions), RetailMeNot (high permissions) and Drippler. I uninstalled from the Google Play Store. Before uninstalling, I planned to give a 1 star review for all 3 apps downloaded on my phone informing people of these apps, but there was no option for me to review these apps although these apps have reviews from other users. I didn't pay attention to the first two that I uninstalled but when I selected uninstall for the Drippler app, there was a warning "This app was not installed by Google Play Store. Do you want to Uninstall it". After this happened I did uncheck the "Unknown Sources" box under the security option for third party apps. I'm very disappointed that this has happened. I have had too much trouble with this phone and really feel that it was a waste of purchase. The first one I bought was broken and this is the second one exchanged in the store and it has many issues. I only downloaded 1 app (MOOC app) a few hours before this happened, but these didn't download until after I turned my phone off, then back on. The MOOC app listed links to several MOOCs online, and only had 4 reviews. If these same apps are being downloaded to other T-Mobile Note 4 users could this be from a link or a problem with the phone. What are the chances of several people accessing the same link? Does this mean the phone is hacked? If the "Unknown Sources" box is checked, will this stop the downloads without permission? Someone please help. This is an edited response to the above-written. After I wrote the response, I picked up my phone and noticed the Virus Scanner (CM Security) icon was in status bar. It showed there was 1 vulnerability called BroadAnywhere. I searched it on Google and found that it is a very bad virus... Once the virus was cleaned from my phone it seems to be working well. It hasn't been long but so far it seems ok and the apps haven't come back, nor the permissions (which did come back once after deleting apps) and well as a couple other things before the virus scan. Hopefully this will clear the problem. If not, I'll give update.
raptir said:
Three apps installed themselves without my intervention:
Cookie Jam
Drippler
RetailMeNot
They didn't come preinstalled, but just installed themselves today. I was able to uninstall them but they keep coming back.
Any idea what's going on? They do not show up under My Apps in the play store, but I can uninstall them through settings. I did a factory reset and didn't install anything and they still come back.
Click to expand...
Click to collapse
I noticed this happened to me as well,but it only happened after I updated my note to the new update. My wife's phone has not been updated and she doesn't have the app in her applications, so my assumption is it was packages in with the new update.
Sent from my SM-N910T using XDA Free mobile app
There is a preinstalled app labeled "DT Ignite" in the most recent stock rom.
The app is found in /system/priv-app. The file is Ignite_TMO.apk.
Package name is com.LogiaGroup.LogiaDeck.
Just disable it and you guys should be fine.
happening to me too
I can confirm that this has happened to me after the most recent update. Note 4 tmobile version. Disabling "DT Ignite" seems to have fixed it.
First of all, thank you.* Despite your tone it was helpful and reassuring. I have never rooted before and am unfamiliar with the process. If you're willing, I have a few questions that perhaps you can point me in the right direction.
I would like to root and get rid of some applications in general so this isnt exactly off the table, but I would like to begin with a clean factory stock image.
If I do the first method, can I leave it rooted afterwards, or will the act of installing a clean factory stock image unroot the device again?
Also, can you provide a link to a site that offers detailed and trusted steps for either process? Searching google provides several dozen sites each with slightly different methods; what method did you use?
Regarding the tone and assumptions: You do make a lot of assumptions, and you do ooze an air of superiority in your response. I can respect that; this is, afterall your expertise. I just dont think its needed for people to respect your opinion. Assumptions, on the other hand, just lead to people being dismissive of your remarks all together. Its my job to look past assumptions, so they dont bother me much.
Regarding a lawsuite: I live in California and Mandelay Digital is based in California as well. In California you can (edited) sue someone for just about anything: bad thoughts, dressing poorly, beverage too hot etc (all real cases). If there is money to be had, a Lawyer will find a way. Mandelay is publically traded and the author of the software being used; there is incentive there. I will let the attourney make the decision.
Anyway, thank you for your initial response, and any further help you can provide.
---------- Post added at 04:08 PM ---------- Previous post was at 03:41 PM ----------
Looks like I responded too early and should have read the new developments on the thread. It is possible my phone updated thanksgiving and I wasnt aware of it. I did change the battery mid afternoon for family pictures and such, and I noticed the apps (through app2sd notification about some of them being campatible with moving to the SD card) after it booted back up. I just did not see anything about a software update.
With that being said, I suppose it is fairly harmless, though I do not like the idea of such a direct and quite backdoor to installing apps on my phone. I agreed to the initial presinstalled apps, and I am sure somewhere in the initial agreements I may have agreed to unfettered access to my device's selection of apps, but I would still like a more obvious warning of this capability.
I figured it was something that T-Mobile or Samsung had to have snuck in on one of their updates. Luckily I got my phone right before we went on a trip for Thanksgiving. So I haven't had much time to play with it or even Root it yet. I was able to go through all my Apps in the application manager and clear data/turn off all of the apps that I don't want or use, and I haven't had anything reinstall itself without my approval. I have also unticked the unknown sources option, so maybe that helped as well.
I would normally agree that it was some site that performed a drive - by installation, but I haven't used my phone for anything other than taking pictures, and asking Google for directions around Nashville since I got it on Wednesday.
I will definitely be rooting and probably flashing a new rom as soon as I get home though. Having Random apps installed without me knowing is no fun at all.
I've had the new update since the day it was released and never had this problem.
Very disturbing. This is the rights for DT Ignite which is now built into the rom after taking the last update. Did a hard reset and now is part of the rom. Nothing loaded and just logged into the phone. The community should be very upset about T-Mobile sneaking this malware on our phones!
Let me be clear that this is after a hard reset without logging into google, Samsung or a Web page. This crapware is now part of the device if you took the last update.
cirrob said:
First of all, thank you.* Despite your tone it was helpful and reassuring. I have never rooted before and am unfamiliar with the process. If you're willing, I have a few questions that perhaps you can point me in the right direction.
I would like to root and get rid of some applications in general so this isnt exactly off the table, but I would like to begin with a clean factory stock image.
If I do the first method, can I leave it rooted afterwards, or will the act of installing a clean factory stock image unroot the device again?
Also, can you provide a link to a site that offers detailed and trusted steps for either process? Searching google provides several dozen sites each with slightly different methods; what method did you use?
Regarding the tone and assumptions: You do make a lot of assumptions, and you do ooze an air of superiority in your response. I can respect that; this is, afterall your expertise. I just dont think its needed for people to respect your opinion. Assumptions, on the other hand, just lead to people being dismissive of your remarks all together. Its my job to look past assumptions, so they dont bother me much.
Regarding a lawsuite: I live in California and Mandelay Digital is based in California as well. In California you can (edited) sue someone for just about anything: bad thoughts, dressing poorly, beverage too hot etc (all real cases). If there is money to be had, a Lawyer will find a way. Mandelay is publically traded and the author of the software being used; there is incentive there. I will let the attourney make the decision.
Anyway, thank you for your initial response, and any further help you can provide.
---------- Post added at 04:08 PM ---------- Previous post was at 03:41 PM ----------
Looks like I responded too early and should have read the new developments on the thread. It is possible my phone updated thanksgiving and I wasnt aware of it. I did change the battery mid afternoon for family pictures and such, and I noticed the apps (through app2sd notification about some of them being campatible with moving to the SD card) after it booted back up. I just did not see anything about a software update.
With that being said, I suppose it is fairly harmless, though I do not like the idea of such a direct and quite backdoor to installing apps on my phone. I agreed to the initial presinstalled apps, and I am sure somewhere in the initial agreements I may have agreed to unfettered access to my device's selection of apps, but I would still like a more obvious warning of this capability.
Click to expand...
Click to collapse
Yes if you use the first method, it will unroot your device. (If it's rooted, that is. )
I am making a guide but got tied up yesterday, the guide will be up in about 2-3 hours. I will link it here when it's done.
devynbf said:
Yes if you use the first method, it will unroot your device. (If it's rooted, that is. )
I am making a guide but got tied up yesterday, the guide will be up in about 2-3 hours. I will link it here when it's done.
Click to expand...
Click to collapse
Thank you
cirrob said:
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
Here ya go, guide is live.
So yeah, assuming their efforts is successful and they manage to set up their wifi to deny access to rooted devices, is there anyway around this without unrooting?
Apoplectic1 said:
So yeah, assuming their efforts is successful and they manage to set up their wifi to deny access to rooted devices, is there anyway around this without unrooting?
Click to expand...
Click to collapse
There used to be a module called Root Cloack(er) for Xposed frameworks that hides root, don`t know if there is a version for Marsmellow though. Its here on the XDA forums somewhere.
But how? I can't think of any way to detect a rooted/jailbroken phone from a Wifi connection, without you having to install or run some other piece of software/script that would give them that information.
revrenhex said:
But how? I can't think of any way to detect a rooted/jailbroken phone from a Wifi connection, without you having to install or run some other piece of software/script that would give them that information.
Click to expand...
Click to collapse
I'm not sure. I would not put it past my company to make us install such a script in order to access wifi.
Many places are doing this. Detecting root is simple. Even Snapchat and others are doing it. Heck they are even looking for xposed and won't work if detected.
You would be amazed at what info people can get from your device when it's connected to wifi
zelendel said:
Many places are doing this. Detecting root is simple. Even Snapchat and others are doing it. Heck they are even looking for xposed and won't work if detected.
You would be amazed at what info people can get from your device when it's connected to wifi
Click to expand...
Click to collapse
a lot of info sure... But an app running on your phone detecting it, vs detecting that something is installed simply by connecting to their network? Your phone passes along a lot of info... but not installed binaries?
I could see them maybe having a black list, like if you're connecting the the exposed repositories your likely rooted... but if you are not using programs that require root access and communicate over the network, how are they doing this?
scryan said:
a lot of info sure... But an app running on your phone detecting it, vs detecting that something is installed simply by connecting to their network? Your phone passes along a lot of info... but not installed binaries?
I could see them maybe having a black list, like if you're connecting the the exposed repositories your likely rooted... but if you are not using programs that require root access and communicate over the network, how are they doing this?
Click to expand...
Click to collapse
A simple request for the info. Have you ever looked at a logcat and saw everything running. I could be gone for weeks and come home and tell you every device that has ever connected to my network the whole time I was gone and with the right things in place could even tell if they are rooted or jailbroken
I can see the same as the poster above me on our network, it is not hard at all. And if we had such a policy and you used a cloaker I would have you fired.
Their network, their rules. I really don't think you should do this.
zelendel said:
A simple request for the info. Have you ever looked at a logcat and saw everything running. I could be gone for weeks and come home and tell you every device that has ever connected to my network the whole time I was gone and with the right things in place could even tell if they are rooted or jailbroken
Click to expand...
Click to collapse
Can you provide any links or further detail? Obviously by viewing system logs you can tell whats running.... but I have never seen any standard network function to request a connected device to send logs without permission? Google searching the topic provides little info as its saturated with info on how to root, and using root for ad blocking.
Even a brief overview of the setup you would use to check? What are "the right things" and what "place" would the need to be in?
scryan said:
Can you provide any links or further detail? Obviously by viewing system logs you can tell whats running.... but I have never seen any standard network function to request a connected device to send logs without permission? Google searching the topic provides little info as its saturated with info on how to root, and using root for ad blocking.
Even a brief overview of the setup you would use to check? What are "the right things" and what "place" would the need to be in?
Click to expand...
Click to collapse
I wont get into it too deeply as I have my guys that watch this site as well and If they go around my security setup like with exchange pin request or using some devices on my network I will fire them on the spot. Lets just say the router logs everything that is done on the network. Connect your device to your wifi and then watch a logcat. You should be able to see what you are looking for.
Understand that unless approved by me no device can connect to my network. With the right router you can see everything about a device. you wont find much info on google as things like this are kept close to the chest with the IT crowd
zelendel said:
I wont get into it too deeply as I have my guys that watch this site as well and If they go around my security setup like with exchange pin request or using some devices on my network I will fire them on the spot. Lets just say the router logs everything that is done on the network. Connect your device to your wifi and then watch a logcat. You should be able to see what you are looking for.
Understand that unless approved by me no device can connect to my network. With the right router you can see everything about a device. you wont find much info on google as things like this are kept close to the chest with the IT crowd
Click to expand...
Click to collapse
No one here is trying to connect to your network. It's XDA and people are curious. I agree that it's silly to circumvent measures used by the company you work for (assuming you want to keep working there), but I also find it strange that you connect to a network and have that router, etc tell if your phone has a specific binary and apk. Is that what you are claiming happens?
gee2012 said:
There used to be a module called Root Cloack(er) for Xposed frameworks that hides root, don`t know if there is a version for Marsmellow though. Its here on the XDA forums somewhere.
Click to expand...
Click to collapse
This is not possible to limit an android version via network traffic, the best they could do is catch you updating cyanogenmod and ban your mac by guessing that your rooted, but its so much work, its a bunch of empty threats.
mwalt2 said:
No one here is trying to connect to your network. It's XDA and people are curious. I agree that it's silly to circumvent measures used by the company you work for (assuming you want to keep working there), but I also find it strange that you connect to a network and have that router, etc tell if your phone has a specific binary and apk. Is that what you are claiming happens?
Click to expand...
Click to collapse
It can yes. And you are right this is XDA but you would be amazed at what info is not shared here or anywhere except between IT managers or other devs.
Once connected to a network it is not that hard to get everything from a device. This is why all the warnings about connecting to open networks. While Open networks are more of a risk it goes to show that anything can be done.
This has been a practice for a very long time even back to the WM days when roms encluded time bombs that would make the rom not work after a set time and date.
zelendel said:
It can yes. And you are right this is XDA but you would be amazed at what info is not shared here or anywhere except between IT managers or other devs.
Once connected to a network it is not that hard to get everything from a device. This is why all the warnings about connecting to open networks. While Open networks are more of a risk it goes to show that anything can be done.
This has been a practice for a very long time even back to the WM days when roms encluded time bombs that would make the rom not work after a set time and date.
Click to expand...
Click to collapse
It's all smoke and mirrors to me until someone explains how it's possible to read files on a device by a user just connecting to a network and providing no further interaction. Sure you can get the device MAC, name, etc, but that's not how I read your statements. As mentioned in the post above yours, you can guess on network traffic, etc, but I really doubt anyone can "know everything".
Loved the HTC Diamond and TP2 [emoji1]
mwalt2 said:
It's all smoke and mirrors to me until someone explains how it's possible to read files on a device by a user just connecting to a network and providing no further interaction. Sure you can get the device MAC, name, etc, but that's not how I read your statements. As mentioned in the post above yours, you can guess on network traffic, etc, but I really doubt anyone can "know everything".
Loved the HTC Diamond and TP2 [emoji1]
Click to expand...
Click to collapse
Its not guessing network traffic. You can tell exactly what sites they go to. You can tell if they are using a mobile or desktop browser. (same way the carriers do it to prevent teethering)
All it takes is being connected to a network to be infected with a virus. Just how do you think that happens?
No one is gonna explain it. Just like we dont allow talks about network penetration. There are just something that are best not out in public view.
Here is an older example of how they detected jailbroken iphones on school networks.
zelendel said:
Its not guessing network traffic. You can tell exactly what sites they go to. You can tell if they are using a mobile or desktop browser. (same way the carriers do it to prevent teethering)
All it takes is being connected to a network to be infected with a virus. Just how do you think that happens?
No one is gonna explain it. Just like we dont allow talks about network penetration. There are just something that are best not out in public view.
Click to expand...
Click to collapse
I am specifically referring to detecting that a binary and an apk exist on a device SOLELY based on establishing a network connection (not viruses, not websites visited...user does nothing and no new code/software runs on the device). That does not seem probable to me.
It may just be semantics, but that's how I interpreted your original statement.
Of course network admins can see what sites users visit, what browser they use, etc and there is no guessing - only logs [emoji3]. I was using guessing in different sense (ie, you see something "suspicious" and draw conclusions).
Wow.... if i ever get fired after i found out they are 'reading' files on my device... this will be case for a courtn no doubt! I'm sure (at least where i live) the one that fires you based on such actions will have a big problem!
mwalt2 said:
I am specifically referring to detecting that a binary and an apk exist on a device SOLELY based on establishing a network connection (not viruses, not websites visited...user does nothing and no new code/software runs on the device). That does not seem probable to me.
It may just be semantics, but that's how I interpreted your original statement.
Of course network admins can see what sites users visit, what browser they use, etc and there is no guessing - only logs [emoji3]. I was using guessing in different sense (ie, you see something "suspicious" and draw conclusions).
Click to expand...
Click to collapse
If you read the link they showed how to detect cydia which showed them it was jailbroken. The same thing can be done on android.
Droidphilev said:
Wow.... if i ever get fired after i found out they are 'reading' files on my device... this will be case for a courtn no doubt! I'm sure (at least where i live) the one that fires you based on such actions will have a big problem!
Click to expand...
Click to collapse
You would lose. When you agree to use their network you agree to all their rules. This is the main reason for things like Knox. As more and more place move to a "right to work" setup where they dont need a reason to fire you at all. I would be careful about what rules one does break. Gone are the days where we could get away with things like this.
You know this got me thinking. Maybe I will play around with my network and see what I can find out. I have to block root and xposed users anyway so this would be a great challenge. Might be awhile as I revert all my PC back to windows 7.
From an IT perspective, a rooted device provides little to no security. That's why most mobile device management (MDM) products include a feature that let IT block rooted devices from connecting to the secure network or accessing corporate assets. But these products must be able to detect rooted devices before they can block them, and there are ways users can get around those detection mechanisms. Organizations that rely on MDM alone to detect rooted devices should be aware of these limitations.
http://searchmobilecomputing.techta...evice-risks-include-network-access-data-theft
zelendel said:
If you read the link they showed how to detect cydia which showed them it was jailbroken. The same thing can be done on Android.
Click to expand...
Click to collapse
I didn't see a link in Tapatalk or Chrome mobile. As for me, I see no reason why I'd ever want to connect my personal smartphone to my work network. Thanks for the discussion.
zelendel said:
...snip...
Click to expand...
Click to collapse
You made me VERY curious! I will try to call HR department of the company i work for today to ask how this works for us
If i get fired because of this phonecall i will try to get you fired for making me curious
First, I'm just in shock t here's a phone that can't be rooted. It just blows my mind and really, I'm saddened by it. It totally defeats the original idea behind Android - a device that people can root, voiding their warranty, develop - A lot of Amateur dev'd features have been incorporated into Android as it's grown over the years, and modify. Even the Judicial system said end users have the right to do what they want to their device and void the warranty at their own discretion.
However, even if it does ever actually come out and even if VZW DOES carry it and even if I could afford it, which I doubt, I really like th Z force, from what I've seen and read.
So how are you guys who have always used rooted, mod'd devices living without root??
I guess I can learn to give up most of my root required apps, begrudgingly, but TB?? How could I ever transfer my apps and data (MUST have data transferred too) without root??
What about bloatware? It's like giving up sex for me to give up root. Aaaauuuggghhhhh
HipKat said:
First, I'm just in shock t here's a phone that can't be rooted. It just blows my mind and really, I'm saddened by it. It totally defeats the original idea behind Android - a device that people can root, voiding their warranty, develop - A lot of Amateur dev'd features have been incorporated into Android as it's grown over the years, and modify. Even the Judicial system said end users have the right to do what they want to their device and void the warranty at their own discretion.
However, even if it does ever actually come out and even if VZW DOES carry it and even if I could afford it, which I doubt, I really like th Z force, from what I've seen and read.
So how are you guys who have always used rooted, mod'd devices living without root??
I guess I can learn to give up most of my root required apps, begrudgingly, but TB?? How could I ever transfer my apps and data (MUST have data transferred too) without root??
What about bloatware? It's like giving up sex for me to give up root. Aaaauuuggghhhhh
Click to expand...
Click to collapse
There's several Android devices that cannot be rooted, certainly ones designed for Verizon (Droids)
Sent from my Moto Razr M using Tapatalk
sd_shadow said:
There's several Android devices that cannot be rooted, certainly ones designed for Verizon (Droids)
Sent from my Moto Razr M using Tapatalk
Click to expand...
Click to collapse
True that, but I'm not interested in those lol
HipKat said:
True that, but I'm not interested in those lol
Click to expand...
Click to collapse
Well for me the biggest difference is I used to use Playstation controllers, so I had to switch to a gamesir g3s which is the same size and shape but does not require root. Nothing else I do requires root so Im perfectly fine not having it. I miss mhl far more than root since I used it a lot with a bluetooth keyboard and mouse with chrome remote desktop, but I bought a laptop to eliminate that.
I'm really missing the following apps:
Titanium Backup
Ad Blockers that actually work well (AdAway, MinMinGuard, UnbelovedHosts)
Viper4Android
File Browsers that can access the entire filesystem (allowing me to debloat stock apps, among other things).
I can partially work around the ad blockers thing by spending a few extra bucks to purchase some apps that I don't use often enough to have already warranted a purchase, and using DNS66 for non-secure uses (a less than optimal solution, since I can't trust some random server on the internet which could theoretically hit me with a MITM attack...I turn it off whenever security is a concern).
There really is no good workaround for TiBu, V4A, or root file explorers.
But the benefits are that I can now use Android Pay, and don't need to fight with SnapChat every time I need to log back in.
The negatives far outweigh the benefits, and I don't want to ever buy a non-rootable phone again. GFY Verizon.
sn00gan said:
I'm really missing the following apps:
Titanium Backup
Ad Blockers that actually work well (AdAway, MinMinGuard, UnbelovedHosts)
Viper4Android
File Browsers that can access the entire filesystem (allowing me to debloat stock apps, among other things).
I can partially work around the ad blockers thing by spending a few extra bucks to purchase some apps that I don't use often enough to have already warranted a purchase, and using DNS66 for non-secure uses (a less than optimal solution, since I can't trust some random server on the internet which could theoretically hit me with a MITM attack...I turn it off whenever security is a concern).
There really is no good workaround for TiBu, V4A, or root file explorers.
But the benefits are that I can now use Android Pay, and don't need to fight with SnapChat every time I need to log back in.
The negatives far outweigh the benefits, and I don't want to ever buy a non-rootable phone again. GFY Verizon.
Click to expand...
Click to collapse
That's what I wanted to hear. Guess I'll have to pass on this one. No Backup, or V4A is not acceptable for me
The only complaint that I have is that some of the pre-installed apps are not able to be uninstalled. theres 4? or so that I can't get rid of
This is my first non-rootable phone and I have mixed feelings about that. As a stock platform, the Z Force is a great phone and does almost all that I could ask for from a pocket computer. I love having stock Android and like having WiFi calling, though it's a pain to switch back and forth: go into airplane mode, then switch WiFi on to make WiFi calls. Of course, you have to remember to turn airplane mode off when you get back into service.
I also miss Titanium Backup and the ability to completely remove apps I have no interest in having on my phone. All things being equal, I find that I can live without root on this phone. Battery life is great, it's fast, and it gets frequent and regular updates.
Really, no root?
So I just as well stay with my old rooted Droid Turbo. I came here thinking its time I look for a newer Motorola phone, that I can root.
What if I buy an unlocked Z Force? Can it be rooted then?
It seems that the regular Moto Z can be rooted according to this thread:
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
So why can the Force not also be rooted?
Stuck with VZW Malware
I'd like to add to my original list of complaints about not having root.
The topic: AppFlash
Verizon now pushes the AppFlash malware onto every Android device. Without root, it can not be removed properly. I tried to disable the app via Settings, and it "uninstalled" an "update" so now AppFlash doesn't appear in the Apps list, but I still get messages that "AppFlash has crashed" multiple times per day. I work in an area with minimal cell service and no GPS service, and I strongly supect that it's AppFlash that's trying to spy on me, which is causing my phone to be constantly seeking location via GPS and draining my battery. It's only the last month or two that I've noticed it being this bad, and that does seem to correspond with the time that people started reporting the latest wave of AppFlash installations.
Make no bones about it, this is spyware, pushed by Verizon, that tracks your location, calls home to report everything ELSE they've spied on you as well, drains battery rapidly, and can not be removed!
This was the final straw, Verizon. I'm going to move back to iPhone (at least VZW can't crap up iOS too badly, like they can with Android) and then convince my wife to finally fire those VZW bums and switch to T-Mobile or Google Fi.
sn00gan said:
I'd like to add to my original list of complaints about not having root.
The topic: AppFlash
Verizon now pushes the AppFlash malware onto every Android device. Without root, it can not be removed properly. I tried to disable the app via Settings, and it "uninstalled" an "update" so now AppFlash doesn't appear in the Apps list, but I still get messages that "AppFlash has crashed" multiple times per day. I work in an area with minimal cell service and no GPS service, and I strongly supect that it's AppFlash that's trying to spy on me, which is causing my phone to be constantly seeking location via GPS and draining my battery. It's only the last month or two that I've noticed it being this bad, and that does seem to correspond with the time that people started reporting the latest wave of AppFlash installations.
Make no bones about it, this is spyware, pushed by Verizon, that tracks your location, calls home to report everything ELSE they've spied on you as well, drains battery rapidly, and can not be removed!
This was the final straw, Verizon. I'm going to move back to iPhone (at least VZW can't crap up iOS too badly, like they can with Android) and then convince my wife to finally fire those VZW bums and switch to T-Mobile or Google Fi.
Click to expand...
Click to collapse
How is the iPhone working out on Fi?
htcSlide said:
How is the iPhone working out on Fi?
Click to expand...
Click to collapse
Haha, I know, right? Reading comprehension can be hard.
As I said, my plan was to FIRST move back to an iPhone, THEN switch to T-Mobile OR Google Fi (the implication being, that when changing networks, one must obviously either have or obtain compatible hardware). Unfortunately, in my area only VZW has reliable 4G coverage without dead zones in the places where we need service the most. The wife has put her foot down about switching networks for the time being.
At least my iPhone, while older, still has the most recent version of iOS and is unencumbered by Verizon's malware. It's a reasonable compromise at the moment.
Since Z Force seems to be non-rootable, does it mean that camera2 api support level on the phone cannot be improved?
Or is there any way to enable Camera2 API Without Root on this phone?
also, can someone PLEASE help me on this QUERY...
What is Camera2 API support level on Moto Z FORCE
https://forum.xda-developers.com/z-force/themes/camera2-api-support-level-moto-z-force-t3863829
Its so sad not to have root on a very capable device like the Z force