Related
Has anyone seen in the news the electronic readers the government is using which is capable of illegally stealing all private information from any type of smart phone?
Can anybody create a mod that will block a device like this from being used on the Nexus one?
http://www.prisonplanet.com/cops-us...l-cellphone-data-from-innocent-americans.html
Do you really believe what you read?
Say, 16GB of photos&data on iPhone, 1.5 minutes, count required transfer rate - quite simple - and then tell me, what kind of wireless connectivity does this "device" use to "steal data from unsuspecting people"?
Then ask yourself the first question again.
Now, if you look up the stated device's manufacturer site, http://www.cellebrite.com/forensic-products.html, you'll see that even in their photos it's perfectly clear this device has to be connected by wire to the phone. Does anyone in their right mind willingly connect the phone by USB to some device with unknown functionality? In that case, no, the data can't be protected.
Now, if you go even one more step further, and open the "supported devices" catalog on the site, you'll see that the only thing that can be done wireless to the iPhone is extracting phonebook - and I'm not sure about the requirement to allow the BT connection - but if you look up Nexus One, you'll see that it definitely has to be attached by wire to do anything with it.
And now back to the first question: do you believe everything you read?
Jack_R1 said:
Do you really believe what you read?
Say, 16GB of photos&data on iPhone, 1.5 minutes, count required transfer rate - quite simple - and then tell me, what kind of wireless connectivity does this "device" use to "steal data from unsuspecting people"?
Then ask yourself the first question again.
Now, if you look up the stated device's manufacturer site, http://www.cellebrite.com/forensic-products.html, you'll see that even in their photos it's perfectly clear this device has to be connected by wire to the phone. Does anyone in their right mind willingly connect the phone by USB to some device with unknown functionality? In that case, no, the data can't be protected.
Now, if you go even one more step further, and open the "supported devices" catalog on the site, you'll see that the only thing that can be done wireless to the iPhone is extracting phonebook - and I'm not sure about the requirement to allow the BT connection - but if you look up Nexus One, you'll see that it definitely has to be attached by wire to do anything with it.
And now back to the first question: do you believe everything you read?
Click to expand...
Click to collapse
But, it's on the internet, why would the internet lie? Are you calling the internet a liar?
I believe that if you soak your phone in warm, salty water overnight it will block this device - haven't tried though, so I can't confirm...
Umm... those Cellebrite devices are very real, and Michigan police are/were using them. The have the ability to pull the data off of thousands of different types of phones, over USB. I've never see Android specifically listed on their site, but I'd be willing to bet their devices can pull data from Android too.
That being said, I can't believe people are handing over their phones. This whole thing stinks of illegal search and seizure. But, they're getting away with it by saying the person willingly handed over their phone (even though I'd bet they're being coerced), There would be absolutely no way I'd hand my phone over to any LEO with out seeing a warrant first.
I was just mulling this over in my head... and I think the only way to block something like this would be to disable the data port on the phone. What that would involve from a software stand-point, I have no idea, and may not even be possible with how the hardware/software is designed... but that is basically the only way I'd see it to be possible.
Removing the USB driver (device functions) from the kernel would be enough, I believe.
In order for adb to work, you have to enable usb debugging. Wouldn't that be a requirement with this device, also?
ok just because I pulled this from prison planet doesn't mean its not true, it was the most convenient link at the time and hours later it was on front page of yahoo and all the major news sites. it would be easy for a police man to take your phone from you and hook it up to whatever they want.
Yep, saw it tonight on NBC Nightly News with Brian Williams. Looks scary with some cops not using warrants to get your phone on a traffic stop...
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I booted into the bootloader, then used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery ).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
organophosphate said:
Allowing The WiFi Setup Step To Be Skipped (Dangerous):
...
9. YOUR TABLET WILL FAIL TO BOOT IF YOU SKIP THIS STEP: adb shell chmod 755 /system/build.prop
...
Click to expand...
Click to collapse
Shouldn't this be 644?
Also, in case anyone wants to know, you can bypass activation after connecting to a WiFi network - you do not need to tie the tablet to your Google account.
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
cwoggon said:
Shouldn't this be 644?
Click to expand...
Click to collapse
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
nextelbuddy said:
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
Click to expand...
Click to collapse
Well, in my opinion, less is more
organophosphate said:
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
IIRC, this would have been helpful to a gentleman who was looking to bypass WiFi activation awhile back. I applaud little workarounds such as this... you never know when this information might be useful.
cwoggon said:
Well, in my opinion, less is more
Click to expand...
Click to collapse
True.
I was dissatisfied with the original approach because of the risk of causing boot failure, so I refactored the implementation to avoid the problem altogether. The updated procedure should be cleaner & more efficient.
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
ehh i still have to disagree with you there. this isn't the same as wanting to install a custom ROM.
installing custom ROMS and Kernels have true benefits whch are optimization and customization that stock does not offer aka more choice.
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice. as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
I know that many custom roms and kernels give me the ability to inccrease speed and add more options in the operating system that i am looking for hence i will choose to flash a new rom and kernel.
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Im not trying to be argumenative just to do it, im trying to determin your real actual justificaton for wanting this besieds "
its my device let me do what i want" because at no point did i say nor did anyone else say they wanted to flash new roms and kernels because it was their device and they wanted to do what they want, they did it because those options benefitted them in a way that the stock experience did not.
Just because someone is on XDA does not man they are here ot hack their device to pieces. there are many reasons people come to XDA..
talk and interact with others that have a love for media devices
ask questions about their devices
learn from others on how to modify their devices
completely change their devices
just to name a few.
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
nextelbuddy said:
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice.
Click to expand...
Click to collapse
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
nextelbuddy said:
as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
Click to expand...
Click to collapse
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
nextelbuddy said:
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Click to expand...
Click to collapse
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
nextelbuddy said:
Just because someone is on XDA does not man they are here ot hack their device to pieces.
Click to expand...
Click to collapse
Then this procedure is obviously not for them. That's perfectly okay.
nextelbuddy said:
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
Click to expand...
Click to collapse
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
organophosphate said:
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
Then this procedure is obviously not for them. That's perfectly okay.
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
Click to expand...
Click to collapse
Im only one person. I can appreciate your work into finding a valid work around and am in no way attempting to take that from you and im sure there will be many that will be happy and thankful with your hard work. Dont take what I said as any sense that this is how the community feels please.
keep on with your work!
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
nextelbuddy said:
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
lex1020 said:
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
Click to expand...
Click to collapse
That's a good reason!
Absolutely agree that you should be able to skip that step. AND no valid reason needed. Unless Google can show a valid reason for not letting you skip that step. I'm sure most of us have watched the Google, (and Facebook) 'net' close in around us. When I started on Android I thought it was so cool how it was all tied to Google and was cross device. Now I'm like: Google would you just get out of my way, I'll be more than happy to click on 'you' when I need something from you.
The latest insult is that annoying "Keep Shopping" prompt in the Play store. Clicking Back, and Keep Shopping does the exact same thing. I shouldn't have to do either. Since I used to be dropped back to the same place anyway.
While the initialization does require a Wi-Fi connection it does not require an Internet connection. I was able to connect to my printer Wi-Fi network and let the waiting bar run for 2-3 minutes then the initialization would continue to completion.
I didn't like this Google forced initial setup either but at least no information was broadcast this way. The Nexus 7 is very useful even when not connected to the Internet.
Chicken and egg
organophosphate said:
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery </path/to/clockworkmod.img>).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
Click to expand...
Click to collapse
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
violincello said:
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
Click to expand...
Click to collapse
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That's exactly what I did. I was sitting in a parking lot after purchasing my N7 and didn't have a hotspot nearby. I wanted to play with my tab for a few before heading home so I just fired up WiFi Tether on my Rezound.
Sent from my Nexus 7 using xda app-developers app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Click to expand...
Click to collapse
Absolutely. As I mentioned in the OP, this isn't the fastest solution. Hell, you can probably tell I don't even recommend it for common scenarios.
That said, the approach *does* work. Before I started this I searched and was unable find any other way to accomplish the specific goal of skipping/disabling WiFi connection during initial setup. Therefore, when I was finally able to get it working I wanted to document it for the community.
dr.m0x said:
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I tweaked the OP to indicate this more clearly.
Simply
Andie00 said:
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
Click to expand...
Click to collapse
When it happened to me, i just restarted it. It then booted to the homescreen.
In case you didn't know, Google has silently implemented FREE tracking for almost all androids. It also allows you to erase the phone if you feel that it's necessary, all you have to do is enable it as a device admin. I realize there have been apps on the market for a long time now that do this (and more) however Google doesn't require you to install or update any apps to use this service and from my brief testing it seems to work amazingly well right off the bat.
Go here and bookmark: https://www.google.com/android/devicemanager
it's about time they did this. i've hated having to install lookout or avast for decent location and remote wipe. now, that is more. further proof why you don't need an AV on your phone.
The only thing missing that I would like to see in future updates would be the ability to remotely lock the device so that a thief would have a harder time fooling around with the phone before you can track it. I've been using Where's My Droid for a long time but it lost the web interface tracking a while ago and that's been a bummer.
Is there any way to uninstall this useless feature? I never use GPS in my phone (because of the horrible reception, also because I am able to navigate without it), and also do not lose it.
Also, I already encrypted my device, so people can't do anything with it when they find it.
Also, whilst I am at it, I really do not like the way google forces their "content" down the wide opened throat of the community. I did not like the way they went with google services framework, and how you can't do jack sh*t without it, and I do not like the updates and "progression" they make.
Soo, any idea on how to get that off my phone?
Cheers!
PS: Everything I wrote is my own opinion, and if yours differs, at least RESPECT mine. If not, I could not care less about yours and do not get upset if I make fun of it. (Just in case some fanboy tries to attack me )
IRKONIK said:
Is there any way to uninstall this useless feature? I never use GPS in my phone (because of the horrible reception, also because I am able to navigate without it), and also do not lose it.
Also, I already encrypted my device, so people can't do anything with it when they find it.
Also, whilst I am at it, I really do not like the way google forces their "content" down the wide opened throat of the community. I did not like the way they went with google services framework, and how you can't do jack sh*t without it, and I do not like the updates and "progression" they make.
Soo, any idea on how to get that off my phone?
Cheers!
PS: Everything I wrote is my own opinion, and if yours differs, at least RESPECT mine. If not, I could not care less about yours and do not get upset if I make fun of it. (Just in case some fanboy tries to attack me )
Click to expand...
Click to collapse
you can disable the google play services in a custom ROM (i think it's built-in to android 4.2.2) but it'll break the YouTube app, and as you said, you're limited without it. as far as like older ROMs go (ICS, GB, etc.), the app isn't built-in and you can uninstall it.
I personally find google play services somewhat useful (especially now with the ADM), and i use YouTube occasionally so i need it for that, but we all have our own opinions, as you said, and I'd personally like to keep things civil.
and if you hate the services that much, you can actually reflash the ROM you're using without Gapps. it will be a limited experience, but the Play Services won't be there
IRKONIK said:
Is there any way to uninstall this useless feature? I never use GPS in my phone (because of the horrible reception, also because I am able to navigate without it), and also do not lose it.
Also, I already encrypted my device, so people can't do anything with it when they find it.
Also, whilst I am at it, I really do not like the way google forces their "content" down the wide opened throat of the community. I did not like the way they went with google services framework, and how you can't do jack sh*t without it, and I do not like the updates and "progression" they make.
Soo, any idea on how to get that off my phone?
Cheers!
PS: Everything I wrote is my own opinion, and if yours differs, at least RESPECT mine. If not, I could not care less about yours and do not get upset if I make fun of it. (Just in case some fanboy tries to attack me )
Click to expand...
Click to collapse
Other than what was already said I don't think there's a way to remove it, but just look at it this way... it doesn't take up any space and won't just activate by itself, so it's really not inconveniencing you in any way. I understand you don't want to be force-fed features that you don't want, and I absolutely respect that, but for many (myself included) this was a long overdue feature that will no doubt help many many users. This kinda stuff comes with the territory of owning a 'connected' device like a smartphone, so if you really want to get off the grid, just go back to a dumb-phone (yes they still exist).
Sorry for the "rant", but these updates cost me money, since I don't have a flatrare on my phone. (And Android OS still uses my data, whilst I have it turned off. Which is strange)
I actually do own "a few" dumb phones, one for calling, one for getting called, one for SMS.
So I am off grid, at least a little bit.
I actually never understood that feature. As I stated above, I am not the kind of person that loses stuff (OK, maybe sometimes my manners ) nor did I ever had something stolen from me. People tried, but never succeeded.
I am looking forward to Replicant, so I can finally shove my middle finger up Googles fat back-ends (of the wafer. Also it is somehow connected to the fat file system. Not what you thought )
Some day.. Soon.
IRKONIK said:
Sorry for the "rant", but these updates cost me money, since I don't have a flatrare on my phone. (And Android OS still uses my data, whilst I have it turned off. Which is strange)
I actually do own "a few" dumb phones, one for calling, one for getting called, one for SMS.
So I am off grid, at least a little bit.
I actually never understood that feature. As I stated above, I am not the kind of person that loses stuff (OK, maybe sometimes my manners ) nor did I ever had something stolen from me. People tried, but never succeeded.
I am looking forward to Replicant, so I can finally shove my middle finger up Googles fat back-ends (of the wafer. Also it is somehow connected to the fat file system. Not what you thought )
Some day.. Soon.
Click to expand...
Click to collapse
Replicant is available for the galaxysmtd (international galaxy s). it's not fully functional though, because there aren't a ton of open-source libraries and drivers available. if you want replicant on this phone, you gotta learn how to code, and how to build from source.
supernexus is kinda like replicant except it uses a lot of closed-source libraries that make things work. as i said, just don't flash the google apps package. it's basically a clone of the Nexus firmware, as you get all the AOSP components, nothing more or less. oh and also, very minimal google integration without Gapps
How does it work
So does Android Device Manager track the phone or tablet by the hardware signature or by Google account? I ask because I lost my Nexus 7 last Monday and immediately changed my Google Account password. Now when I try to track the Nexus 7 using Android Device Manager it shows that it has not been used since last Monday.
Capt-Capsaicin said:
So does Android Device Manager track the phone or tablet by the hardware signature or by Google account? I ask because I lost my Nexus 7 last Monday and immediately changed my Google Account password. Now when I try to track the Nexus 7 using Android Device Manager it shows that it has not been used since last Monday.
Click to expand...
Click to collapse
Hardware i reckon, when i used this it let's me choose which device I've used with my Google account. It sees phone as different again when I've flashed a new ROM.
Crawshayi said:
In case you didn't know, Google has silently implemented FREE tracking for almost all androids. It also allows you to erase the phone if you feel that it's necessary, all you have to do is enable it as a device admin. I realize there have been apps on the market for a long time now that do this (and more) however Google doesn't require you to install or update any apps to use this service and from my brief testing it seems to work amazingly well right off the bat.
Go here and bookmark: https://www.google.com/android/devicemanager
Click to expand...
Click to collapse
CM Team Announces CyanogenMod Account For Remote Device Wipe/Tracking, Dual-Release Branches For Better Security
Posted by Ryan Whitwam in News
http://www.androidpolice.com/2013/0...ng-dual-release-branches-for-better-security/
CM guys still finding ways to 1-up google android :silly:
.
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