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.
Related
perhaps somebody here could be tolerant enough to assist or direct me to concise clear info to such a likely passe situation.
Phone again, stock from VZW and fully updated.
Barnacle installed from market.
I have a few questions;
1)Superoneclick seemed to only install "superuser" on my phone. Does this mean the busy box and abd things, of which I have no idea what to do with, is only accessible via my win7 64 bit pc while the phone is connected to it via usb?
2)How do I optimize this phone with stock rom and remove "bloatware" as well as eliminate intrusive programs? Are there any threads which ID these as well as their functions?
3) Jrummy Droid Overclock installed, several versions in fact, and the best I could do was make the phone extremely laborious and finally reverted back to stock settings before uninstalling. I did have to click the "experimental" box to make it able to scale the stock rom.
Any thread or info as to some failproof settings to make this stock thing work much better/faster?
4) Can this phone, usb tether the data connection without any paid apps or limitations regarding secure sites and such?
Interestingly enough, I'm finding the search functions on this forum to be impossible on my handheld and just about the same from my pc. From the handheld, it wanted me to assemble pix which my touchscreen or keyboard didn't seem to allow.
From the pc, 'no matches found' or something to that affect.
Also, when I was having problems recalling my login info, had almost given up deciding instead to reregister, I got a denial message based on having a verizon wireless IP. Weird.
I'm rereading the beginners info and it would be nice to be able to simply make my stock rom'd droid better.
Feel free to tell me if I'm pissing in the wind and need to just do different roms and or kernals. However, I'd like to just keep it simple for now.
You are able to download Busybox straight from the Android Market: https://market.android.com/details?id=stericson.busybox&feature=search_result
You can tether your phone to create a wireless hotspot, but I'm not 100% sure about USB tether.
skadude66 said:
You are able to download Busybox straight from the Android Market: https://market.android.com/details?id=stericson.busybox&feature=search_result
You can tether your phone to create a wireless hotspot, but I'm not 100% sure about USB tether.
Click to expand...
Click to collapse
Yes and thanks, I snagged barnacle for that. It works fine although I'm either too green to make it secure, or the WEP stuff is broken.
That is why I'd like the option to have a more secure hardwire tether.
I know I can do pda.net and some other apps, it seems to me that it should be able to do that perhaps just with some tweaks.
So when I extracted superoneclick on my pc, I see busybox and such in that file. I just did the one click and nothing else, not even on my phone.
It is interesting how fast such basic topics become inundated with miles of confusing info to bewilder a virtual computer twit.
It looks like what you want to do is basically create a wireless hotspot with your phone? Because I use Wireless Tether for Root Users and I am able to encrypt it and set up a secure connection.
Here's what I pulled from the Barnacle website:
How do I use WEP?
Barnacle support 40 and 104-bit WEP. In Settings find Wireless Security and enable WEP, then type in the key. For 40-bit WEP, type in 5 ASCII characters or 10 hex digits. For 104-bit WEP, type in 13 ASCII characters or 26 hex digits. Passphrase is not supported.
Click to expand...
Click to collapse
skadude66 said:
It looks like what you want to do is basically create a wireless hotspot with your phone? Because I use Wireless Tether for Root Users and I am able to encrypt it and set up a secure connection.
Here's what I pulled from the Barnacle website:
How do I use WEP?
Barnacle support 40 and 104-bit WEP. In Settings find Wireless Security and enable WEP, then type in the key. For 40-bit WEP, type in 5 ASCII characters or 10 hex digits. For 104-bit WEP, type in 13 ASCII characters or 26 hex digits. Passphrase is not supported.
Click to expand...
Click to collapse
Phone Settings? "no "Wireless Security" to be found nor did I readily find anything to do with WEP under the Wireless sections.
Barnacle? Again, no "Wireless Security" section found. There is a "Wireless Encryption" settings section. I did enable it with the app stopped and set a five digit alpha code. Restarted Barnacle and my pc completely disregarded it, connected to it with no input required and the signal still shows as unsecured and public.
I'm pleased that it tethers, I would like to make it secure and I would also like to easily usb it to any laptop or pc sans having to load software on them unless said pc/device was older and didn't automatically recognize this phone, as this new win 7 pc did, where upon loading some drivers would be seem reasonable.
I'm not pc/droid knowledgeable enough to know if this is dreaming but, it seems reasonable that it's usb output could be toggled and be seen as a modem connection.
I'm sure it can, but people use Wireless tethering more than a physical USB tethering.
I've never actually used this, but I've heard of people using it when they need to tether via USB: https://market.android.com/details?id=com.mstream.easytether_beta&feature=search_result
Yes and thanks, I truly appreciate your efforts to help and your tolerance for my ignorance.
I am aware of those various usb tethering programs and I suppose my question is why must software be loaded on a device capable of seeing other usb plugged connections and run them 'plug and play'?
I'll see if somebody with barnacle can assist me with the WEP issue. I've tried it several ways and have had no success. Possibly related, my droid no longer will send MMS. It still receives them, just no longer sends. I wish I could say if that occurred after rooting or after attempting overclocking, but, it happened after one or both.
Wait, does the Easy Tether not require software to be installled on usb tethered device? I was sure it did and after reading the page, it doesn't mention it.
It's still bizarre that I can wirelessly tether now that soc rooted it, but I still have to buy an app to usb tether it, and I was pretty sure, install stuff on device to be tethered.
No problem, anytime!
Honestly, I don't know much about Easy Tether, I've heard about it, but have not delved much deeper into it.
What ROM are you using (if any)? I know that I had some issues with CM7 and a little bit less with Cronos right now, where I send a text message and it hangs with "Sending..." for hours at a time.
How much did you overclock your phone by? What vsel?
Sent from my Milestone using XDA Premium App
phone is stock other than being rooted
I used JRummy's Droid Overclock as it is supposed to overclock a stock rom'd A855 droid.
I tried several several many settings, mostly what was recommended, but none of them seemed to make it better, and if they did, I couldn't seem to make them stick upon rebooting.
Kept all attempts at or below 800MHz.
I'm sure it's my lack of understanding and likely there are some simple settings that will speed it up with just a few clicks as well as save thru a fast and speedy reboot.
i recently installed an MIUI rom and like most of its features but a very big thing its lacking for me is the 'Internet pass through' that i used a lot when i was on stock Sense rom.
can anyone help me with this..?? i need 'Internet pass through' everyday for almost every single hour while i am at home.. is there any app out there which can help me or something else..??
so many views but no reply..
Do you mean that you'd like to use your PC as the phones "modem" and connect through a USB cable? If so it can be done through settings.
I haven't ever used that particular ROM but on my phone using Android Rev its possible by going:
Settings > Connect to PC > Default Connection Type > Internet pass-through
Otherwise if that ROM doesn't have it then maybe search these forums or google "Reverse tethering android"
tried it but nothing..
Definitely looks like a Sense-only feature, unless you want to start messing around with adb, port forwarding and such:
http://blog.mycila.com/2010/06/reverse-usb-tethering-with-android-22.html
I guess you have to decide whether you're brave and/or patient enough to go through all that just to see if it'll work. There definitely isn't an easy fix outside using a ROM with Sense.
doctorsax said:
Definitely looks like a Sense-only feature, unless you want to start messing around with adb, port forwarding and such:
http://blog.mycila.com/2010/06/reverse-usb-tethering-with-android-22.html
I guess you have to decide whether you're brave and/or patient enough to go through all that just to see if it'll work. There definitely isn't an easy fix outside using a ROM with Sense.
Click to expand...
Click to collapse
Proxoid is easier than all that IMO... http://code.google.com/p/proxoid/wiki/installation
Greetings,
I tried to ask this in the NexusRoot Toolkit thread, but I need 10 posts.
My question has to do with Nexus 7 Security and Rooting. Can I turn the developer options back off after rooting, and still have the 'rooted' experience? I'm concerned with any malware infections, and also exploiting the device using a Cellebrite UFED:
w w w .cellebrite.com/mobile-forensics-products/forensics-products.html
I will be encrypting the entire device using Android encryption. Anything to watch out for when enabling encryption, in relation to rooting? Is the max unlock/encryption length still 16 characters on Jelly bean?
Thanks,
RF
Well, you are defending against two different things there.
ufed goes through the usb client mode while you would be defending installed software from the network for whatever malware concerns you might have.
I don't know if anything in user space can defend against a ufed if they want your data bad enough. I have seen it suggested that if you put something like Ubuntu on the device the ufed wouldn't know what to do with it. But I am sure they have plenty of tech specialists who they could then turn the device over to.
A check at a traffic stop might be something you could defend against. But if they have a subpoena and time...well the laws protect them not us.
You could use PDroid to stop apps from having permissions. That seems like the best defense to me for regular everyday data mining. We have not brought it to Jelly Bean yet, but it shouldn't be long.
mateorod said:
Your post
Click to expand...
Click to collapse
Thanks Sir. This is my first Tablet, and my first 'DIY' Unlock & Root. I do currently run Whispercore on a Nexus S though, but that was one click rooting from the installer and I don't touch it. As long as I can power down at a stop, UFED is spinning in the wind with WhisperCore. I want the same functionality from Jelly bean, but am unfamiliar with exactly how it works compared to Moxie's solution. I know that USB Debugging Enabled is an exploitable hole that devices like UFED use, that's why I wanted to know if I can disable all the developer options again, after rooting, with no ill effect.
I also block Android GPS Daemon from communicating, with Whisper Monitor, so hopefully Jelly Bean will have some firewalls able to do this soon.
Thanks for your reply,
RF
You should be alright with malware as long as you're careful what applications and ROMS you're downloading and from where.
Ronaldo Forenucci said:
Thanks Sir. This is my first Tablet, and my first 'DIY' Unlock & Root. I do currently run Whispercore on a Nexus S though, but that was one click rooting from the installer and I don't touch it. As long as I can power down at a stop, UFED is spinning in the wind with WhisperCore. I want the same functionality from Jelly bean, but am unfamiliar with exactly how it works compared to Moxie's solution. I know that USB Debugging Enabled is an exploitable hole that devices like UFED use, that's why I wanted to know if I can disable all the developer options again, after rooting, with no ill effect.
I also block Android GPS Daemon from communicating, with Whisper Monitor, so hopefully Jelly Bean will have some firewalls able to do this soon.
Thanks for your reply,
RF
Click to expand...
Click to collapse
Yes after rooting you can turn it off. (In fact you can turn off developer options completely, and install apps from unknown sources is labeled under security). Only thing you won't be able to do is side load apps or use like titanium backup to restore apps.
Sent from my LG-P999 using xda app-developers app
Ronaldo Forenucci said:
Thanks Sir. This is my first Tablet, and my first 'DIY' Unlock & Root. I do currently run Whispercore on a Nexus S though, but that was one click rooting from the installer and I don't touch it. As long as I can power down at a stop, UFED is spinning in the wind with WhisperCore. I want the same functionality from Jelly bean, but am unfamiliar with exactly how it works compared to Moxie's solution. I know that USB Debugging Enabled is an exploitable hole that devices like UFED use, that's why I wanted to know if I can disable all the developer options again, after rooting, with no ill effect.
I also block Android GPS Daemon from communicating, with Whisper Monitor, so hopefully Jelly Bean will have some firewalls able to do this soon.
Thanks for your reply,
RF
Click to expand...
Click to collapse
I thought whispercore got purchased (by twitter, I think? Maybe?) and is only available for the nexus s. Maybe you plan to sideload it? I haven't personally found a way to try it yet.
But yeah, you can shut off adb mounting. I have actually spent a good chunk of my day looking into how to require a passcode for USB mounting in the kernel, for an unrelated project.
I haven't determined whether the multiuser claims are sufficient. I have muktiuser through botbrew, but that is a little more complicated than what I need there.
You are correct, I have a Nexus S also, running WhisperCore. The N7 will have to run Google's built in implementation of encryption. Thanks for all the replies. I'll Unlock & Root, and then disable Developer Options again. In the 'off state' Google's encryption should protect from UFED type attacks. I'll probably install Avast! (if it runs on the N7) for malware protection.
RF
Yeah from my understanding of UFED your pretty well protected as long as you don't have USB debugging on; so while not ideal, only turning it on when you need it would be the easiest way to secure the device. (along with all the normal stuff like having an actual password etc)
Considering how much apple fanboys tout the iphone's security, its fairly ironic that UFED can still pull some of their info regardless of settings whereas on android if USB debugging is off and a password is used UFED is useless.
I know, right :good: Is max password length still 16 characters? It is on Gingerbread. I wish this thing had a USB slot...I'd love to be able to use my Yubikey with it. I wonder if the NFC Yubikey version would work on the Lock Screen?
RF
Hey, everyone.
I just bought an ATT Samsung Focus S i937 off of eBay. It was locked when I received it, so I plunked down 25 bucks and unlocked it. I'm using it on Telus and so far all is well, except for WiFi connection sharing/tethering.
When I try to enable internet sharing, I get a message saying "Connection not shared. To enable tethering on this device go to (ATT's website) or dial 611."
Basically, it sounds like I need to have an ATT tethering plan to enable this on my phone, but since I'm not an ATT customer, there's not mch I can do.
I was wondering if there is a workaround for this. Please let me know!
Thanks,
Taylor
TaylorofCanada said:
Hey, everyone.
I just bought an ATT Samsung Focus S i937 off of eBay. It was locked when I received it, so I plunked down 25 bucks and unlocked it. I'm using it on Telus and so far all is well, except for WiFi connection sharing/tethering.
When I try to enable internet sharing, I get a message saying "Connection not shared. To enable tethering on this device go to (ATT's website) or dial 611."
Basically, it sounds like I need to have an ATT tethering plan to enable this on my phone, but since I'm not an ATT customer, there's not mch I can do.
I was wondering if there is a workaround for this. Please let me know!
Thanks,
Taylor
Click to expand...
Click to collapse
firstly DO NOT INSTALL THE SAMSUNG UPDATE!! and if updating the OSan have it unlocked already read This Website and use the relock prevent + edit your hosts file
Absolutely back up your device at every stage using This Guide
So follow these steps
unlock the device Here follow the instructions which includes installing the diagnostic tool and install XAP deployer or XAP handler Here or Here With the XAP file deployer in the WP7 SDK
Then install WP7 Root Tools Here
Then install WP Bazaar market Here
Open Root Tools, and give Bazaar higher level privileges
Find WinTT on the Bazaar market and install it
Open Root Tools, and give WinTT higher level privileges
you may need to restart to get WinTT working
go through WinTT and turn on ICS
Done
Wow thanks.
That's very complete. One questions though... I didn't mention this, but I am a registered WP7 dev and can unlock this device using my dev access. Can I load any of the XAPs directly instead of having to crack my phone?
Thanks,
Taylor
Yeah, you have limited access to installing xaps, but you will still need to interop unlock and use root tools to give higher level access to WinTT, so your best starting from scratch,
Sent from my SGH-i937 using XDA Windows Phone 7 App
Unable to understand the process
I have purchased an Samsung Focus S i937 locked to AT&T. I have purchased an unlock code and have successfully unlocked my phone. Im also unable to use the Internet Sharing feature of my phone. Firstly, I am not a technical guy hence im unable to understand the process stated by you. Secondly, I wanted to find out that does following the process given by you, expose my device to get BRICKED as I am able to understand that involved a JAIL BREAK of the device. Does it have any other side effects.? Like effecting the radio signals or any other such problem.
Thanks
abhijeetmohan06 said:
I have purchased an Samsung Focus S i937 locked to AT&T. I have purchased an unlock code and have successfully unlocked my phone. Im also unable to use the Internet Sharing feature of my phone. Firstly, I am not a technical guy hence im unable to understand the process stated by you. Secondly, I wanted to find out that does following the process given by you, expose my device to get BRICKED as I am able to understand that involved a JAIL BREAK of the device. Does it have any other side effects.? Like effecting the radio signals or any other such problem.
Thanks
Click to expand...
Click to collapse
ok, first things first.
You won't brick your device, at worst a hardrest all remove all changes you can do, our device, the focus S, isn't fully unlocked, so there are limitations to the amount of damage you can do by arseing it up. With that behind us you have to learn what you are about to do, there isn't a simple way.
So, start by knowing these basics, then read through the guide, any bits you don't understand feel free to ask.
1, AT&T locked your internet connection sharing, so you must re enable that
2, To enable ICS, you must make changes to the registry
3, Microsoft locked you out of making changes to the registry, so you must gain access to do it
4, AT&T left a security hole allowing us to make changes to allow us to change things like registry
5, using that hole we can install software that will give us more access, that software can then allow us to remove the AT&T lock on ics
These things you must do, there is no magic answer, there has been some short cuts made but this in some cases has had a negative effect, such as losing 3g, doing as I said will not have any effect on your signal or anything else
Sent from my Samsung Focus S using XDA Windows Phone 7 App
Have you guys noticed any of the following....
issues after the above procedures were applied (a big thanks to all the brainiacs who know how to hack this stuff):
Slowed Internet Connection
Lower Strength of GPS Signal
Less accuracy and trouble sometime finding location
Less accuracy while using maps because of the above statement
Not complaining, just curious. Thanks to all.:good:
7carisfast said:
issues after the above procedures were applied (a big thanks to all the brainiacs who know how to hack this stuff):
Slowed Internet Connection
Lower Strength of GPS Signal
Less accuracy and trouble sometime finding location
Less accuracy while using maps because of the above statement
Not complaining, just curious. Thanks to all.:good:
Click to expand...
Click to collapse
theres nothing in the code that should have done that, the XML import only fiddles with interop unlock
im not 100% sure what WTT changes but I know the entries it should be fiddling with and shouldnt make any difference, although its been suggested the ICS code does mess with the 3G signal ive not heard anything at all to suggest that it effects GPS as well.
See This Thread for details, ive copied the relevant bits here but all thanks should go to those on the original thread
Option 1
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
Option 2
Resolve Samsung connection problems
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489# ***DOES NOT WORK ON i937***
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
GPS is a completely passive function, I don't have a problem with this, HSDPA may have issues for reasons unknown but using this method doesn't effect mine, perhaps its carrier specific..
dazza9075 said:
theres nothing in the code that should have done that, the XML import only fiddles with interop unlock
im not 100% sure what WTT changes but I know the entries it should be fiddling with and shouldnt make any difference, although its been suggested the ICS code does mess with the 3G signal ive not heard anything at all to suggest that it effects GPS as well.
See This Thread for details, ive copied the relevant bits here but all thanks should go to those on the original thread
Option 1
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
Option 2
Resolve Samsung connection problems
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489#
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
GPS is a completely passive function, I don't have a problem with this, HSDPA may have issues for reasons unknown but using this method doesn't effect mine, perhaps its carrier specific..
Click to expand...
Click to collapse
Thanks for the info. I'll see if it helps. Just as FYI, the code *#32489# does not appear to work on the i937.
7carisfast said:
Thanks for the info. I'll see if it helps. Just as FYI, the code *#32489# does not appear to work on the i937.
Click to expand...
Click to collapse
indeed, so it would seem, many of the diagnostic codes have been disabled which is a pain, even the ones that are left don't always do what you expect them to do
8773 update
dazza9075 said:
firstly DO NOT INSTALL THE SAMSUNG UPDATE!! and if updating the OSan have it unlocked already read This Website and use the relock prevent + edit your hosts file
Absolutely back up your device at every stage using This Guide
So follow these steps
unlock the device Here follow the instructions which includes installing the diagnostic tool and install XAP deployer or XAP handler Here or Here With the XAP file deployer in the WP7 SDK
Then install WP7 Root Tools Here
Then install WP Bazaar market Here
Open Root Tools, and give Bazaar higher level privileges
Find WinTT on the Bazaar market and install it
Open Root Tools, and give WinTT higher level privileges
you may need to restart to get WinTT working
go through WinTT and turn on ICS
Done
Click to expand...
Click to collapse
What if I have already updated to version 7.10.8773.98, is there any other possible way? I don't need any other features. Thanks in advance.
If you have updated the OS and NOT the samsung firmware then reapply the windows break interop unlock, be sure to keep it off the inernet by disabling all coms and then apply the relock prevent xap. if you have applied the Samsung firmware and didn't have it already unlocked or you didn't have a back up, your screwed
Sent from my Samsung Focus S using XDA Windows Phone 7 App
dazza9075 said:
If you have updated the OS and NOT the samsung firmware then reapply the windows break interop unlock, be sure to keep it off the inernet by disabling all coms and then apply the relock prevent xap. if you have applied the Samsung firmware and didn't have it already unlocked or you didn't have a back up, your screwed
Sent from my Samsung Focus S using XDA Windows Phone 7 App
Click to expand...
Click to collapse
First of all I just want to say thanks that you're trying to help me, but I just didn't understand many things u said, I'm not really into technical stuff, but I'll tell you what info I have, in hope of u helping me better.
I don't live in the US and I bought the phone from ebay and it was unlocked and it works perfectly over 2 carriers here in my country, and I have never encountered any problems with it except for the internet sharing feature.
And about 3 months ago the phone notified my to a system upgrade from version 7.10.7740 to version 7.10.8107 then immediatly to version 7.10.8773.98. now I'm guessing these are OS firmwares not samsung software.
but I've noticed something, when I setup my phone for the first time I used a US hotmail account but before I connect to the internet the ICS feature worked, but once I signed in it gave me the dial 611 or go to att.com/mywireless message.
So I am guessing if I restore the device and sign in with a non US hotmail account may result in the feature to be unlocked. The only thing keeping me from trying this because I'll have to redownload all my apps again and reorganize my contacts again. if there's a way to avoid that or someone has tried it please do tell.
Again thanks for your reply.
kholio88 said:
First of all I just want to say thanks that you're trying to help me, but I just didn't understand many things u said, I'm not really into technical stuff, but I'll tell you what info I have, in hope of u helping me better.
I don't live in the US and I bought the phone from ebay and it was unlocked and it works perfectly over 2 carriers here in my country, and I have never encountered any problems with it except for the internet sharing feature.
And about 3 months ago the phone notified my to a system upgrade from version 7.10.7740 to version 7.10.8107 then immediatly to version 7.10.8773.98. now I'm guessing these are OS firmwares not samsung software.
but I've noticed something, when I setup my phone for the first time I used a US hotmail account but before I connect to the internet the ICS feature worked, but once I signed in it gave me the dial 611 or go to att.com/mywireless message.
So I am guessing if I restore the device and sign in with a non US hotmail account may result in the feature to be unlocked. The only thing keeping me from trying this because I'll have to redownload all my apps again and reorganize my contacts again. if there's a way to avoid that or someone has tried it please do tell.
Again thanks for your reply.
Click to expand...
Click to collapse
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Samsung Firware Update
dazza9075 said:
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Click to expand...
Click to collapse
Dazza,
Kudos for your help as you personally worked with me through this information. Not sure the Samsung update is a concern as I'm running fw2103.11.10.1 and everything works great.
Thanks again.
dazza9075 said:
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Click to expand...
Click to collapse
OS version: 7.10.8773.98
Firmware version: 2103.12.05.2
kholio88 said:
OS version: 7.10.8773.98
Firmware version: 2103.12.05.2
Click to expand...
Click to collapse
im afraid to say your firmware is locked,
2103.11.10.1 is unlock-able, im pretty sure anything from xxxx.12.xx.x upwards is locked down solid
I don't suppose you made a backup? if you haven't then there is nothing you can do
the Samsung firmware update was released as a separate update at the same time as the tango 8773 build, it tried to install on mine after the 8773 build
Found a solution =D
dazza9075 said:
im afraid to say your firmware is locked,
2103.11.10.1 is unlock-able, im pretty sure anything from xxxx.12.xx.x upwards is locked down solid
I don't suppose you made a backup? if you haven't then there is nothing you can do
the Samsung firmware update was released as a separate update at the same time as the tango 8773 build, it tried to install on mine after the 8773 build
Click to expand...
Click to collapse
I'm really sorry for the late reply, was busy at work. but during that time I might have found a "Glitch" or a workaround to enable it and I have tested it many times and it works.
Well there are two ways:
1st one which is a sure thing:
1) Turn off the phone, then turn on again.
2) Once the phone is turned on, immediately go to settings>internet sharing and turn it on and BOOM there you go :laugh:
* I have tried this method over a dozen times and it works every single time
** The point here is that you have to enable it immediately after the phone is turned on, I think it happens because the phone doesn't have enough time to send the info. to the servers to know that it's not enabled by default.
2nd one which was succesful over 75% of the time:
1) Go to Settings>cellular>Turn Off, Wait like 5-10 seconds and turn on again.
2) Go to Internet sharing> Turn on, and enjoy :fingers-crossed:
***I don't know why do they work or how, may be it's a Glitch like I said before but the point is they do work
I hope that I've helped someone out there and Thanks to everyone who tried to help me
kholio88 said:
I'm really sorry for the late reply, was busy at work. but during that time I might have found a "Glitch" or a workaround to enable it and I have tested it many times and it works.
Well there are two ways:
1st one which is a sure thing:
1) Turn off the phone, then turn on again.
2) Once the phone is turned on, immediately go to settings>internet sharing and turn it on and BOOM there you go :laugh:
* I have tried this method over a dozen times and it works every single time
** The point here is that you have to enable it immediately after the phone is turned on, I think it happens because the phone doesn't have enough time to send the info. to the servers to know that it's not enabled by default.
2nd one which was succesful over 75% of the time:
1) Go to Settings>cellular>Turn Off, Wait like 5-10 seconds and turn on again.
2) Go to Internet sharing> Turn on, and enjoy :fingers-crossed:
***I don't know why do they work or how, may be it's a Glitch like I said before but the point is they do work
I hope that I've helped someone out there and Thanks to everyone who tried to help me
Click to expand...
Click to collapse
nice find, ICS is disabled locally only, it doesn't have anything to send, the only thing I can think of that makes sense is that the service hasn't been initialised and doesn't call the reg entries that disables ICS, by turning it on manually ASAP it perhaps catches it out. if you enable it, then disable it, can you still enable it again in that session or do you need to restart?
dazza9075 said:
nice find, ICS is disabled locally only, it doesn't have anything to send, the only thing I can think of that makes sense is that the service hasn't been initialised and doesn't call the reg entries that disables ICS, by turning it on manually ASAP it perhaps catches it out. if you enable it, then disable it, can you still enable it again in that session or do you need to restart?
Click to expand...
Click to collapse
Well I tried that, but there is no definite answer to it, sometimes I turn it on and off on and off many times without needing to restart and throughout the whole day, and sometimes it works once and doesn't at the second try. So it all comes down to luck, but still better than nothing
Now the thing is I'm afraid that when the 7.8 update comes, they would fix this glitch =D Haha.
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