Related
i have been playing with this application for the past 4 hours
and it will JUST NOT connect! im pretty sure ive reached that point
where you keep trying everything u can, but eventually you end up with
a web of mistakes and have no idea where to begin to finish...so, lets
get to it...
- i am at school. i live across the street from campus, far enough to
where my g1 wont pick up the wifi signal, so configuring the app via
wifi isnt even an option...
so i go to the FAQs and there seems to be a way to operate the program
via the cell network without using a router...great because i dont
have one...but when i read the instructions, it starts telling me
stuff ABOUT a router...
"2.Log into your router and go to the port forwarding section (it
might be called NAT settings, or Application and Gaming). "
...where am i supposed to go to do this? i have set up ICS, i have
googled google for "port forwarding" "nat settings" "nat configuration
in windows xp", ive even used the BS help and support that comes with
windows, im going nowhere. can somebody PLEASE help me figure this
out? i want to use gmote over t-mobiles internet connection, and it seems like you can do this from what the FAQs told me...any help will be appreciated
Yeah the faq doesn't make sense, have you tried the developer directly or checking their google group? They are pretty quick to respond
On my home pc i just needed to know the ip addresss of my machine. Since this is a campus network, its possible that only particular ports are open. the port that gmote uses may be blocked.
The FAQ is a little confusing, but its not that difficult to work out
That is true, given that bittorrent and Ares are known for not running on campus...how do I figure out what ports ARE open?? I guess google will help
cant you just connect to the ip number of your computer?
Thats what Im trying to do, but Im now assuming that the ports are blocked because I cant get thru no matter what. I ran netstat and tried to figure it out but it was Russian to me
From what I understand of the program, you have to be on the same network. I may be wrong, but if you are on a different subnet, then you're SOL.
Like I said, could be wrong, but that's what I heard.
Ok, so I just upgraded to Froyo, flashed Perception build 10. But, I can't get MobileAp to work. Like, it'll run and I can find the network on my laptop, but no internet access once I've connected
Ideas?
froyo has a built in wireless tether. try using it instead
settings>wireless and network>mobile ap
mtrsttr said:
froyo has a built in wireless tether. try using it instead
settings>wireless and network>mobile ap
Click to expand...
Click to collapse
That's what I am using, and it's not working. I can join the network, but no internet access
No ideas?
Firebird kernel 24
Have you tried connecting with anything besides your laptop? An ipod or another device? I have always been able to connect with my windows devices but it can take a few minutes after connecting before internet access is obtained.
Aster you able to tether via usb?
You can also try using an app from the market to see if it will work if you haven't already.
http://code.google.com/p/android-wifi-tether/
It's in the market. I use it instead of mobileap cause it allows me to secure my wifi and allow only those who I know to connect. Mobileap is completely open to any and all. I'm sending this post from my hp laptop tethered to my captivate.
@bobarone....click mobile ap settings to enable secure connection. default is usually set to open
newter55 said:
Have you tried connecting with anything besides your laptop? An ipod or another device? I have always been able to connect with my windows devices but it can take a few minutes after connecting before internet access is obtained.
Aster you able to tether via usb?
You can also try using an app from the market to see if it will work if you haven't already.
Click to expand...
Click to collapse
Thanks for your mention of Windows, because I just tried it on my Mac and that's what would not work. My iTouch worked fine though.
Any ideas on making it work with my Mac? if not that's not a big deal as that's not what I'll be using it for primarily, just wondering.
Thanks for your help, didn't even think about it!
Regards
Smith
Hmmm...i thought mac's "just worked" honestly I know nothing about them, every time I get a new laptop I say I am gonna get an apple but wind up with windows.
was just in best buy last week and the new ones look sweet so perhaps this summer I will finally make the leap.
newter55 said:
Hmmm...i thought mac's "just worked" honestly I know nothing about them, every time I get a new laptop I say I am gonna get an apple but wind up with windows.
was just in best buy last week and the new ones look sweet so perhaps this summer I will finally make the leap.
Click to expand...
Click to collapse
Well... Macs are harder to break. lol idk if they 'just work' haha but only reason I even have an apple is because it's fast as hell for school work, and when I got it was before I learned linux so I thought it was the only Windows alternative. Learning linux has made most of this 'more advanced' adb stuff cake because I know all the shell commands haha
I would still recommend one though simply because you'll be relatively hard pressed to find a laptop with such high specs for that price anywhere else. That, and you can multiboot so you can decide what you like best. That was the deciding factor for me lol.
But thanks a lot for your help, this makes me feel much better. I use my wifi tether for work because the upload speeds suck hard and I never get jack done if I don't lol, so I'm happy this works!
Regards
Smith
No problem....glad to be of assistance
newter55 said:
@bobarone....click mobile ap settings to enable secure connection. default is usually set to open
Click to expand...
Click to collapse
Can't get the save button to come up. Tried changing it, but save is greyed out, just cancel as an option.
From a phone
How many characters/numbers are you trying to use? Minimum appears to be eight though I never paid attention til now, the code I have always used just happens to be sufficient.
Is there a way to analyze what is wrong with someone's ROM and fix it without having to abandon the ROM to a different one, or waiting forever for someone else to maybe fix it? I've had to go to quite a few different ROMs as of late to get the functionality that I'm looking for because things didn't work with many ROMs, they had things broken. I would rather just learn how to fix them and then even post a fix for everyone. Devs, is this possible or would this only be something that the ROM COOK could do? Two recent examples include:
1. USB Tethering connecting to my PC, giving my PC a LAN IP, but not being able to get anywhere on my PC while my phone is still able to surf.
2. Bluetooth AD2P hiccups.
Then also add more functionality, like EPST functionality in Froyo and Gingerbread.
I've done a bit with logcat but as of yet is difficult for me to understand. I've successfully used debugging tools on Windows however in order to fix problems with applications that were hanging up on bad files, dlls, etc.. Was hoping I could learn how to do it with Android. Any help is appreciated.
petermg said:
Is there a way to analyze what is wrong with someone's ROM and fix it without having to abandon the ROM to a different one, or waiting forever for someone else to maybe fix it? I've had to go to quite a few different ROMs as of late to get the functionality that I'm looking for because things didn't work with many ROMs, they had things broken. I would rather just learn how to fix them and then even post a fix for everyone. Devs, is this possible or would this only be something that the ROM COOK could do? Two recent examples include:
1. USB Tethering connecting to my PC, giving my PC a LAN IP, but not being able to get anywhere on my PC while my phone is still able to surf.
2. Bluetooth AD2P hiccups.
Then also add more functionality, like EPST functionality in Froyo and Gingerbread.
I've done a bit with logcat but as of yet is difficult for me to understand. I've successfully used debugging tools on Windows however in order to fix problems with applications that were hanging up on bad files, dlls, etc.. Was hoping I could learn how to do it with Android. Any help is appreciated.
Click to expand...
Click to collapse
If you don't understand what the logcat is telling you, you will have a hard time writing any code for a fix. Might want to invest in a "linux for dummies" book and start there. I think there is even a book like that for android programming out now, iirc...
nandroids are for
sissies
Redundant posts cleaned out.
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.
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