Related
My university has a dedicated 802.1X connection specifically for mobile devices that I've been able to hook my Samsung Intercept (rooted, running 2.2) up to. The directions for connecting any Android platform to the connection is fairly straightforward:
Use these settings:
• EAP Method: TTLS
• Phase 2 authentication: PAP
• CA Certificate: (leave as N/A)
• Client Certificate: (leave as N/A)
• Identity: <GW NetID>
• Anonymous identity: (leave blank)
•Wireless password: <NetID password>
Click to expand...
Click to collapse
The thing is though, the NC's wireless tab doesn't allow for EAP Method input or Phase 2 authentication. Is there any way for me to access those protocols and connect?
MashableMe said:
My university has a dedicated 802.1X connection specifically for mobile devices that I've been able to hook my Samsung Intercept (rooted, running 2.2) up to. The directions for connecting any Android platform to the connection is fairly straightforward:
The thing is though, the NC's wireless tab doesn't allow for EAP Method input or Phase 2 authentication. Is there any way for me to access those protocols and connect?
Click to expand...
Click to collapse
Same as Android always is... Configure it as much as you can, then use this app to configure it all the way: http://www.appbrain.com/app/wifi-advanced-config-editor/org.marcus905.wifi.ace
Downloaded the suggested app, but for some reason whenever i moddify the protocols they snap right back as soon as i navigate away from the page. Any suggestions?
Same happened to me. It's the phase 2 encryption (PAP) that always snaps back. Tried on Nookie without any problem (just stock froyo wifi functionally, not by configuring wifi advanced configuration editor). So the there should be no hardware issue. I bet B&N's crippled OS lacks support for PAP.
MashableMe said:
Downloaded the suggested app, but for some reason whenever i moddify the protocols they snap right back as soon as i navigate away from the page. Any suggestions?
Click to expand...
Click to collapse
Haven't had any issues with my Nook Color and 802.1x/PEAP/TKIP/RADIUS/MS-CHAPv2.
In wifi advanced configuration editor it ways revert phase 2 to MS-CHAPv2, so I guess that's the only one B&N implemented, which also explains why it works in your case.
RasputinAXP said:
Haven't had any issues with my Nook Color and 802.1x/PEAP/TKIP/RADIUS/MS-CHAPv2.
Click to expand...
Click to collapse
Crap, you're right.. But not quite. Phase2 doesn't seem to save right at all.. If you set it to None, you can't set it back to any of them...
Could try editing the wpa_supplicant.conf file
Tried that but instructions on nookdevs are not very clear. Can you point me to a more thorough documentation?
khaytsus said:
Crap, you're right.. But not quite. Phase2 doesn't seem to save right at all.. If you set it to None, you can't set it back to any of them...
Could try editing the wpa_supplicant.conf file
Click to expand...
Click to collapse
jianglai said:
Tried that but instructions on nookdevs are not very clear. Can you point me to a more thorough documentation?
Click to expand...
Click to collapse
Well, probably the easiest way is this, since the tool I mentioned doesn't work.. Sucks, because it does work on my Nexus One. But if the protocols aren't supported this obviously won't magically make it work, but I doubt that's really an issue.
First off, turn off wifi if you can.. If you're using wifi adb, then turn off wifi and back on when you complete this..
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf
(edit wpa_supplicant.conf)
adb push wpa_supplicant.conf /data/misc/wifi/
However... You'll PROBABLY have to fix its permissions, as I suspect they'll be wrong, and if so, wifi won't work at all until you do. So here's how you'd fix that:
Code:
adb shell
su
cd /data/misc/wifi
chown system.wifi wpa_supplicant.conf
chmod 660 wpa_supplicant.conf
I suggest toggling wifi on/off again... If you have any issues, double check your file ownership and permissions.
BTW, if you're really adventurous, you could do it directly in vi Unless you know how to use vi, use the above...
Code:
adb shell
su
cd /data/misc/wifi
vi wpa_supplicant.conf
Great! So what I did is to connect to our network through setting-wireless. After entering username and password it just says remembered but never tried to connect. And in wifi advanced configuration editor even though I could choose TTLS and PAP, the PAP part always snaps back to default when I leave the editor, which makes me think it might be a permission problem. So i pulled the .conf file, edited it and pushed it back then changed ownership and permission as you suggested, everything works perfectly since then!!! Thank you so much!
BTW, in adb shell it seems I do not have vi... All I installed is the basic SDK as suggested in nookdevs, is there anymore packages I should install to have more tools like vi?
khaytsus said:
Well, probably the easiest way is this, since the tool I mentioned doesn't work.. Sucks, because it does work on my Nexus One. But if the protocols aren't supported this obviously won't magically make it work, but I doubt that's really an issue.
First off, turn off wifi if you can.. If you're using wifi adb, then turn off wifi and back on when you complete this..
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf
(edit wpa_supplicant.conf)
adb push wpa_supplicant.conf /data/misc/wifi/
However... You'll PROBABLY have to fix its permissions, as I suspect they'll be wrong, and if so, wifi won't work at all until you do. So here's how you'd fix that:
Code:
adb shell
su
cd /data/misc/wifi
chown system.wifi wpa_supplicant.conf
chmod 660 wpa_supplicant.conf
I suggest toggling wifi on/off again... If you have any issues, double check your file ownership and permissions.
BTW, if you're really adventurous, you could do it directly in vi Unless you know how to use vi, use the above...
Code:
adb shell
su
cd /data/misc/wifi
vi wpa_supplicant.conf
Click to expand...
Click to collapse
jianglai said:
Great! So what I did is to connect to our network through setting-wireless. After entering username and password it just says remembered but never tried to connect. And in wifi advanced configuration editor even though I could choose TTLS and PAP, the PAP part always snaps back to default when I leave the editor, which makes me think it might be a permission problem. So i pulled the .conf file, edited it and pushed it back then changed ownership and permission as you suggested, everything works perfectly since then!!! Thank you so much!
BTW, in adb shell it seems I do not have vi... All I installed is the basic SDK as suggested in nookdevs, is there anymore packages I should install to have more tools like vi?
Click to expand...
Click to collapse
Woot, it worked! I mean.. You're welcome!
Aha, vi must have come from the busybox I installed maybe.... Perhaps the one from Titanium?
Thanks a lot for these directions, as soon as I got adb working it worked perfectly! I first tried to do this using on-device apps since I was having trouble installing ADB, and that didn't work. This just proved that it is absolutely necessary to use adb to do this. Regardless, it works, i'm happy!
Another Workable Idea...
So my work has 802.1x EAP PEAP authentication for the wifi. I tried the advanced wifi editor, but that didn't work. Tried editing the wpa file, that didnt work. When I connected I was always being rerouted to a screen to download a certificate for authentication.
So I used the HC SD bootable rom and was able to manipulate the wifi settings like you can on your android phone, and connect to the wifi. When I pulled out the SD and rebooted into Autonooter 3.0 the authentication stuck and now the 802.1x wifi network is rocking on.
Just thought you all might like an update.
bnole said:
So my work has 802.1x EAP PEAP authentication for the wifi. I tried the advanced wifi editor, but that didn't work. Tried editing the wpa file, that didnt work. When I connected I was always being rerouted to a screen to download a certificate for authentication.
So I used the HC SD bootable rom and was able to manipulate the wifi settings like you can on your android phone, and connect to the wifi. When I pulled out the SD and rebooted into Autonooter 3.0 the authentication stuck and now the 802.1x wifi network is rocking on.
Just thought you all might like an update.
Click to expand...
Click to collapse
Considering you made wifi changes in HC on your SD card then booted your stock, nothing "stuck". Each time you connect your wifi will re-authenticate, in fact it'll re-authenticate on some systems multiple times per hour.
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
What was the isssue first? You couldn't see the login page? I know school and coffee shop allow you to connect to their wifi but you have to go to a login page first and accept the cert before accessing the network. Just curious because my wife today told me that she had issue accessing the school wifi on the unroot nook. The login page didn't come up. I am going to try it out with mine (currently running cm7 nightly build).
Sent from my PC36100 using XDA App
Perhaps you should take up this issue with your school's IT Department. Just mention that you are trying to connect an android device to their secure wireless.
Ah, I just read that you figured out. Well, still pass your method to the IT Department so that they can share it with other students and perhaps create some documentation.
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
if your school has a guests network you can connect into that and just login to their webportal using your id login
my school does this but im not sure if all schools do this
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
Thanks for your post. I do have a similar problem (i.e., not having the log in screen after connecting to the "open" WiFi on campus) and will try your method later today. Will be back with the results
madtopcoder said:
What was the isssue first? You couldn't see the login page? I know school and coffee shop allow you to connect to their wifi but you have to go to a login page first and accept the cert before accessing the network. Just curious because my wife today told me that she had issue accessing the school wifi on the unroot nook. The login page didn't come up. I am going to try it out with mine (currently running cm7 nightly build).
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My issue was that I couldn't simply log on to the campus wifi network with the nook color (rooted) and the IT department said I needed to wait until Barnes and Noble issued an update to the software so I could change the required settings needed for their network. I tried the guest wi-fi network but that didn't work either, so I thought I would just try to figure it out myself. Which I did and I thought I would pass it along. I'm going to let the IT department know what I did in case anyone else comes to them looking to put their nook on the network. One caveat though is the nook color has to be rooted. I don't think you access the necessary file unless it's rooted. : )
branjosef75 said:
My issue was that I couldn't simply log on to the campus wifi network with the nook color (rooted) and the IT department said I needed to wait until Barnes and Noble issued an update to the software so I could change the required settings needed for their network. I tried the guest wi-fi network but that didn't work either, so I thought I would just try to figure it out myself. Which I did and I thought I would pass it along. I'm going to let the IT department know what I did in case anyone else comes to them looking to put their nook on the network. One caveat though is the nook color has to be rooted. I don't think you access the necessary file unless it's rooted. : )
Click to expand...
Click to collapse
Yeah, I'm at UIC as well and had similar problems connecting to UIC-Wifi on my Nexus One while it was still running 2.1... the ACCC (Campus IT) gave me the run-around on all this stuff for a while... let me tell you...
It has something to do with versions earlier than Android 2.2 only partially supporting 802.1x Authentication or something like that... I ended up doing something similar to what you just described to the wpa_supplicant configuration file in order to get it to work... after I described this to the Campus IT department, they "informed" me that they would be unable to support this method because it required the phone to be "jailbroken" (LOL! ) anyway... long story short... works okay now...
Just ordered myself a nook color yesterday.... good to know this is possible!
I'm excited to get started screwing around with it...
redstar3894 said:
Yeah, I'm at UIC as well and had similar problems connecting to UIC-Wifi on my Nexus One while it was still running 2.1... the ACCC (Campus IT) gave me the run-around on all this stuff for a while... let me tell you...
It has something to do with versions earlier than Android 2.2 only partially supporting 802.1x Authentication or something like that... I ended up doing something similar to what you just described to the wpa_supplicant configuration file in order to get it to work... after I described this to the Campus IT department, they "informed" me that they would be unable to support this method because it required the phone to be "jailbroken" (LOL! ) anyway... long story short... works okay now...
Just ordered myself a nook color yesterday.... good to know this is possible!
I'm excited to get started screwing around with it...
Click to expand...
Click to collapse
i had the same exact situation you did but with my evo.
but you dont need to do this anymore. you can connect just fine thru the wifi settings.
http://www.uic.edu/depts/accc/android/index.html
edit: i take that back. doesnt work in 2.1. works in 2.2 just fine though
Does anyone have any more info on a fix for this? My gf's NC is running CM7 Nightly14, and she can't connect to USC's wireless network- apparently the login screen won't come up, so she can't sign in.
She was able to while she was running the stock software, so i'm wondering what has changed.
xeren said:
Does anyone have any more info on a fix for this? My gf's NC is running CM7 Nightly14, and she can't connect to USC's wireless network- apparently the login screen won't come up, so she can't sign in.
She was able to while she was running the stock software, so i'm wondering what has changed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=988802
Check out my thread.
I couldn't connect to my school's network (SDSU) so I pushed those files in [Problem 1] and it worked after that!
Try it!
Thanks a lot. It is great. Very easy and helpful. Thanks again. You should post it on ACCC.
This should work with other wireless connections, if you know the SSID.
As for down here in champaign, try this (I'm not getting my nook color until sometime over spring break, so this is a guess):
network={
ssid="IllinoisNet"
key_mgmt=WPA2-EAP IEEE8021x
eap=PEAP
identity= "INSERT YOUR USER NAME (UID)"
password="INSERT YOUR ACTIVE DIRECTORY PASSWORD"
phase2= "auth=WPA2"
priority=14
}
That's the best to my knowledge. CITES doesn't like to disclose much about anything online, so I pulled most of this from the windows xp setup configuration.
Good work!!!
Sent from James' OCed Nook Color
Interesting. My university uses a WPA(2?), PEAP system that requires a THAWTE certificate, but the nook color -- both on stock rooted, and CM7 connected fine with username and password. Your network looks similar to ours, but its a good tip you've posted, adding it manually may help in the case of other similar networks as well.
Quick update: I updated my gf's NC from CM7 Nightly 19 to 31, and now it's connecting to her university's wireless- not sure what the devs changed, but it's working great now!
If you still haven't been able to get it working with the above hacks, try updating to the latest CM7, it may work for your school as well.
Thank you.
I tried this on my rooted nook color (stock 1.2) It didn't work.
branjosef75 said:
So I have been looking for a way to get on my university's wireless network. I've searched the internet and saw a few people on various forums who were at the same school (University of Illinois at Chicago) looking to do the same thing, but with no luck. There was a lot of information out there but none that really worked, so I spent a few hours today messing with the nook and was able to do it. Here is what I did.
Through Root explorer I accessed... /data/misc/wifi/ wpa_supplicant.conf and holding my finger over the file, I chose "open in text editor"
I added the following information.
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I did not need a Thwate certificate or anything like that. Worked like a charm and now I can access the university's wifi from the nook. I know this is kind of a very specific post , my apologies, but I don't know if it might help someone else down the road as a starting point to get onto their network if the general tricks and tips don't work.
Click to expand...
Click to collapse
I just tried it on nook color(stock 1.3 rooted). It did work. I first tried to log in our wifi before changing that file. Then I opened the file, and it becomes
network={
ssid="UIC-WiFi"
key_mgmt=WPA-EAP IEEE8021x
eap=PAP
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
}
I changed it like him and also added another line(scan_ssid=1):
network={
ssid="UIC-WiFi"
scan_ssid=1
key_mgmt=WPA-EAP IEEE8021x
eap=TTLS
identity= "INSERT YOUR USER NAME"
password="INSERT YOUR PASSWORD"
phase2= "auth=PAP"
priority=14
}
I noticed that I was able to connect once (the first time), and then could not reconnect afterwards. My Kubuntu netbook and iPad did not have this problem. After opening /data/misc/wifi/wpa_supplicant.conf as recommended, I immediately saw the problem: the password isn't being saved for my WPA2-Enterprise network. All the other networks had a password field, if applicable. Go figure...
Thanks for the hint! It appears that this may be a more general problem than you thought (I did not test this yet, but will do so tomorrow.)
Ok,
So, I, along with a few others, pay for the Unlimited Mobile HotSpot and want this app to work as other (root) tethering apps only allow Ad-Hoc.
Here's what I did to get it to work on my Windows 7 x64 Computer as of just a few moments ago and I do plan to work on this issue to get this figured out.
I've discovered that the /data/misc/dhcp/udhcpd.conf file is what controls the DHCP addressing for the 4gMobileHotSpot App. Within this app, I discovered (in the Modded ROM (as of now, I have Gingervolt1.1)), that the "Option DNS" addresses were completely wrong. This was apparent from the get go as they were internal IP address starting with 192.168.x.x.
The steps to get this app working on Windows is:
0 - Be Rooted (Sorry, just had to point the obvious out in Step 0)
1 - Use the market and download/install the Text Edit (Paul Mach) App
2 - (TESTed and Working), Use AntTek (root) Explorer and navigate to:
/data/misc
3 - Long Press the udhcpd.conf file and select to open with the Text Edit App
4 - Change the 'option dns' from 192.168.x.x to 66.174.92.14 69.78.96.14 and save/exit
5* - In Windows, set the IPV4 Properties to:
Use Following Address:
IP Address: 192.168.1.5 (or anything in between start and end range in text file)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Use Following DNS server addresses:
Preferred DNS Server: 66.174.92.14
Alternate DNS Server: 69.78.96.14
6 - Start 4gHotSpot App
7 - Tell Windows to Connect and you should be connected.
NOTE: It is late and I know that this will become clearer as time goes on and since I have to work in the morning, this is the best I came up with in a few minutes after figuring out that the hang up was with this file, in which I knew it's been a DHCP issue all along. Why this file is changed with the Modded ROMs is beyond me and I doubt MT changed this, so likely it is something to do with the DE-odex or some other modification of this app and it's initialization. Just deleting the CONFIG file will only cause it to write a new one with the wrong values again.
For those who do use this app, it is known to stop responding at times and I am going to look into that. I'm thinking this is a DNS issue and will try some other DNS Servers (8.8.8.8 I believe is a Google public DNS)..
In the meantime, this is a start for anyone to add to this that has more DHCP/DNS/Network experience. I don't have another android device handy to test the connectivity, so will have to get that figured out.
Key point here is, is that the 4gHotSpot App gets corrupted with the Custom ROMs and for some reason sets up wrong DNS servers in the Config file.
Hope to see some thoughts, additions, fixes, to this problem with this being pointed out, from others. I will continue to work on it throughout this next week after work.
Last Note: The DNS server numbers came from the original Config prior to rooting/modding. Also, I do know that is it redundant to have them in the config file AND the Windows Properties. It's just that setting Windows to 192.168.1.1 (option router in the Config file) didn't work. Again, will work on cleaning this method up and simplifying.
-Cybie
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
displacedbuck said:
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
Click to expand...
Click to collapse
Ok, so here's what I did after reading your post:
1 - Corrected the path (Sorry, it was late and I missed that /dhcp portion of the path).
2 - Deleted "option router 192.168.1.1" from udhcpd.conf file
3 - Deleted "option dns x.x.x.x x.x.x.x" from udhcpd.conf file
Set Windows up with the Following:
Static IP : 192.168.1.2
Subnet : 255.255.255.0
Gateway : 192.168.1.1
DNS Servers : 4.2.2.1 & 4.2.2.2
That worked.
So, what I am seeing if I try to use DHCP on Windows is that the 4gHotSpot gives the computer 192.168.16.x addressing even though the config file is set to give out 192.168.1.x addresses (x=2 through 254). It also gives Windows 3 DNS servers that are local IP addresses and will never go anywhere.
What to do now? Figure out what is being changed with the Custom ROMs that is causing the app to act like that. In fact, it will act like that when I restore back to Stock GB Rooted via restore from backup in CWM, but I have yet to test deleting the config file and restarting 4gHotSpot to test. I will do that over the weekend as I don't have a lot of time I can have my phone down during week. But I do plan to up to the GingerVolt1.3 tonight.
As of right now, I am using my windows machine connected to the 4gHotSpot App to write this post. Also, I don't know about the iPhone/iPad and possible settings. If you can Force (Set a Static IP) then follow what I did up above, but you will also need to set the DNS servers and not sure you can do that on an Iphone/iPad.
The DNS Servers I listed are found on a public list and are also said to be Verizon DNS servers...
The other problem I found and is an issue with the app, is using auto b/g/n will cause the hotspot to lose connectivity. When in that mode, I connect at 65Mbps, but it drops down to 6Mbps and stalls and fluctuates. I set it to 'g' only and get a SOLID 54Mbps connection just like the tether apps.
SPEED TEST Results: 18.35 Mbps Down, 10.66 Mbps Up without a glitch.
Obviously this app works with DHCP addressing as STOCK. So, I will begin my Android Development with figuring out one of two things. Either get this app to work as it's supposed to, or create a root app with 'Infrastructure' based on whatever I can find in the coding for this app if I can figure out a way to decode it.
I personally hate the idea that you can't connect other android devices to AdHoc and also annoys me to have to manually connect Windows since it doesn't seem to have the ability to automatically connect to AdHoc Networks. Linux does perfectly fine with auto connect AdHoc, go figure. Android is Linux Based, yet can't AdHoc, but provides an AdHoc as an access point for other devices. weird, lol.
Let me know if any of this helps, but do know I am going to continue to figure this out. I'm sure de-odexing the app had something to do with it as I'm sure Verizon did their best to keep this app from being hacked for free HotSpot service.
-Cybie
Thanks for the detailed response.
I'm going to try again. I won't be able to try until tonight or tomorrow morning when I have time to play with it and roll back if necessary.
I'll let you know if it works or I find out anything else.
Before you install a ROM and have the app working, try connecting your computer and get the values (ip, dns, gateway, etc.) That the app dhcp assigns and post that. Rooting the phone alone shouldn't break the app either. By getting those values posted, would help and also save me from downgrading just for that purpose. Knowing that it works with without a mod is one thing,. So my focus is working on getting it to function with a modded ROM.
It's strange that i can get the app to work if i force the connecting device to values (static settings), but this doesn't help with certain devices and needs to connect via dhcp.
-Cybie
Sent from my VS910 4G using XDA App
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
displacedbuck said:
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
Click to expand...
Click to collapse
These number are from your connected device? What device are you connecting that give you such numbers? I'm not familiar with the iPad and how it displays connection details. Is that what that is from?
I'm still able to connect after updating to GingerVolt1.2 and manually installed 4gHotSpot app. I just got home with little time to work on this project for the night, so I will update what I can if any changes in getting things to work.
-Cybie
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
displacedbuck said:
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
Click to expand...
Click to collapse
Sounds good. Those numbers will help.
I will add, though, that someone posted a way to get the wifi tether to work with the Revolution, here in the forum. The problem, though, is that it's connection via 'n' mode, which would be great, except it drops out. If you try to download something that's fast (or going to speedtest sites), you will find that that happens and what everyone is complaining about the HotSpot app not working. All that needs to be done is changing it to 'g' only mode and a solid connection.
Anyhow, I will see if I can figure out how to get that app working on 'g' only mode also, and if I do, then I will just use that app instead. Otherwise, I plan to continue to figure out the 4gHotSpot App
-Cybie
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
jamRwoo said:
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
Click to expand...
Click to collapse
Sorry for the delay. Been working extra hours at work and haven't had the energy to do much with this past couple days.
Anyhow, no, I don't intend to try to get it working for those who do not pay. Why? There are apps out there for this and the only reason I was trying to get this to work properly was for the fact that it would be nice to have the proper connection for those who do pay. I say that because the HotSpot app actually has a faster wifi connection (using n mode) than the tether (root) apps out there, with the exception of the one posted at:
http://forum.xda-developers.com/showthread.php?t=1339150
Unfortunately I am having the same issue with the HotSpot and that app (using infrastructure mode) when connecting. They both to link up at 65Mbps. In fact, I got 72Mbps with the wifi Tether app from the link, but like the HotSpot app, I have issues with the connection dropping out using 'n' mode.
The HotSpot app will allow you to set it to 'g' only mode, though only get a 54Mbps link speed, but sustains a solid connection with no drop outs. Others say they don't have that issue, so it may just be my wifi adapter??? I am going to test it on my laptop, but if I remember, I did have that same issue with the laptop, so maybe it's just my phone??
Either way, I am going to be doing what I can to get 4gHotSpot to work correctly with rooted/modded ROMs. Strange thing is, rooted, it still works fine. After installed modded ROM, it fails to work. And if I restore back to factory rooted via CWM, it still doesn't work. You actually have to restored/flash back to total stock. After that, you can root with it working, but not after installing a ROM.
-Cybie
Any luck with the fix?
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
ALTANertive said:
Any luck with the fix?
Click to expand...
Click to collapse
I've been doing testing. Please read below for some more of my findings.
sgschwend said:
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
Click to expand...
Click to collapse
I've noticed something very strange with the HotSpot and Rooting.
If you root, the HotSpot continues to work. But, if you reboot after rooting, that's when the failures begin. So, I am thinking that the files are being overwritten. I've been able to test with clean root, root with tether app, and restore without root.
Without root, the HotSpot continues to work fine as I have been using it for the past two weeks as I need it for my new WiFi Tablet. There is the WiFi app the allows for Infrastructure, but that also allows devices to connect via N-Mode, where I have issues of the data dropping out. Forcing b/g only on my HotSpot app, I have very reliable service.
I am planning (after my trip) to root my phone, copy some DHCP files before ANYthing can be changed and before rebooting. Comparing these files and seeing if anything changes there. If so, that will allow me to create a simple app to restore these files back to stock, either automatically, or through 'starting' of the app.
I haven't forgotten about this issue and It's something that I am needing to figure out. The problem is time right now. For the past few months, I had to work a job in order to keep bills paid. That job took a lot of my hours I used to have to figure things out. I am going to be having limited time available, but do plan to work on it some more in the next few weeks, especially since i want my Tablet to work flawlessly with my phone, as that is my ONLY source of internet and I DO pay for the HotSpot service.
-Cybie
Thanks for the update.
Like you I also pay for the 4g hotspot. I jumped on it when they offered the unlimited for $30.
Now that I've tried the gingervolt rom and the supercharger script I don't think I can go back. It just feels like a totally different phone.
I haven't had as much need for it recently so I haven't tried one of the other tethering apps.
Thanks for plugging along on this.
Yes, thanks for looking at this.
Here is some more observations:
Using your set ip and other setting I can get the hotspot to work. Two of my devices are not able to set a fix address without rooting them. So they do connect but only my PC will download a web page.
Here is the address my Revo is setting on the other two devices: 192.168.16.30 and .31.
Ok, so here's an update to this issue.
I have tracked the problem down to a failure to write to the udhcpd.leases file within the /data/misc/dhcp folder.
So, I did some searches on the net about a few things, but there's not much information regarding the "paid" HotSpot feature vs the (Root) Tether Apps.
What I did comes across, though, is there seems to be some sort of issue with certain versions of busybox relating to the udhcpd.conf. I also found the file that gives the 192.168.16.x addresses. But, by the time I found it, the phone already goofed up the HotSpot app settings and things weren't working. So, next round of factory restoring via LGNPST/Tot, I will seek into that and see what I can find out.
It's weird that the 4g HotSpot app will work flawlessly on the initial boot (Rooted, ROM'd, and even OC'd). But, after a reboot of the phone (once or twice), it becomes corrupted and non-working. It's going to be related to some sort of permissions issue and some file that is able to be corrupted/changed with the root/superuser access. I had similar results with fresh restore and JUST root, so the ROM's have nothing to do with it as far as I am concerned at this point.
In case you might ask. I Refreshed phone to total stock, rooted, and then, all at one shot, installed Gingervolt 1.3, OC, and Hotspot before rooting phone. HotSpot worked fine until the next reboot, where it did work for a few minutes then Kaboom! Nodda.
If someone can access (pull) the /system/var/lib/misc/udhcpd.leases file from a fresh stock phone, or even first-time booted, rooted phone, I would appreciate that as this file may be something in question, but my file was already changed by the time I found it.
-Cybie
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
sgschwend said:
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
Click to expand...
Click to collapse
EDIT: When you copy these files, Don't view them until you zip up a copy first. They could potentially get corrupted. not likely, but with the way it's going with this 'project', who knows.
adb pull /data/misc/dhcp datadhcp (This will copy files from phone to a created directory called datadhcp)
Also, and more importantly, this is what I am really wanting:
adb pull /system/var/lib/misc varmisc (copies to created varmisc folder)
AND
adb pull system/etc/dhcpcd dhcpcd (copied to dhcpcd folder)
The created folders and files will be in the same 'dos' directory you have adb in. You can use the folder in which the all in one root is from MT if you are wondering where to get that by any chance.
Those would be a big help in getting thing figured out. At least, if those are the culprits.
NOTE: In order to have non-corrupted files, these have to be pulled from a fresh restore via LGNPST / Tot method. A restore via nandroid backup will not work. those files, once corrupted, seem to remain so, even after a restore for some odd reason, unless you were lucky enough to not have them corrupted prior to backing up, which would likely mean you rooted, rebooted into recovery and backed up before rebooting into your phone.
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
Click to expand...
Click to collapse
Please clarify on this. Are you referring to starting the 4gHotSpot, shutting it down, and then starting a (root) Tether App??? If so, I haven't really had that issue because once I have to use the root apps to tether with, that usually means my HotSpot won't work at that point. I will say, however, I have had an issue where the HotSpot didn't want to shut down. I just go into Services/App Management and force a shutdown instead of a reboot. A bit quicker....
-Cybie
I will take a run at copying this stuff later today.
On the hotspot bug. Even before rooting, or upgrading to GB there was this bug, and it is still there after GB.
Once the hotspot has been started and then the user shuts it down it appears to shut down. Then the tethering (the application that came with the phone) is initiated it looks like it is tethering but the hotspot icon comes on after the phone has finished tethering and indeed it is running that way too.
I tried this five time last night: Restored the hotspot both application and data (titanium app), installation part of the application would fail but T said it was complete. Launched the application and two of the five times the PC had the correct IP address, the other three times it had the corrupted ones. Also when the PC did come up correctly the second device's IP address was corrupted. So I may need to fiddle a bit to fine the uncorrupted files after restore.
Perhaps someone else could help with copies the files too?
[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Cynagen said:
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Click to expand...
Click to collapse
Have you tried a different firmware?
The Dark Lestat said:
Have you tried a different firmware?
Click to expand...
Click to collapse
I've tried V10K, V10D, V20A, V20P, V21D, and V21E, none of them restored the bluetooth (original issue), and so far V10K, V20P, and V21E have not restored the Wifi.
On V21E under settings, it's always showing as "Turning off..." under Wi-Fi. So it's definitely a hardware lockup. Is there anyway to do a full hardware reset on these things? I don't care about opening it, I'm not with AT&T anymore so the phone is mine, and frankly, I just want it to work.
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
What ROM are you currently on? Baseband as well.
The Dark Lestat said:
What ROM are you currently on? Baseband as well.
Click to expand...
Click to collapse
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Cynagen said:
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Click to expand...
Click to collapse
I would say that you should try going back to FroYo and checking those addresses again.
The Dark Lestat said:
I would say that you should try going back to FroYo and checking those addresses again.
Click to expand...
Click to collapse
I've gone back to FroYo without any change to Wifi or Bluetooth, but I'll go back to V10K and check the CP again.
Explanation
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
Please Explain Tutty. I get into the hidden screen and tried the download and nothing was downloaded, this is my first smartphone and do no that there is no MAC address for the bluetooth device. it is the only thing not working. Thanks in advance for the help.
4th Update 5/2/2013 - Found a bug... Nothing that would affect the overall functionality, but it could cause some users to think that their phone is successfully connected via USB debugging, when it really isn't.
Update: 5/2/2013 - Per user requests, adding link to VirtualBox download site on the original post.
3rd Update 5/1/2013 - I changed the code that 'finds' the exploit file to make sure it get executed successfully. It's now using the "PATH" environment to do this. This is more reliable than the actual Linux 'find' command I was using before. Also added some additional instructions to clarify some steps based on feedback from users. Finally, added code to detect if the network adapter is not configured correctly. It will alert the user to configure the network adapter properly in the VirtualBox application.
2nd Update 5/1/2013 - I added some lines to the script to stress the importance of pressing one of the three hardware buttons on the phone (Volume up, Volume Down, or Power) once the exploit has been executed. After discussing this with the author of the exploit, this is an important step to obtaining root.
UPDATE 5/1/2013 - New and improved .ova file. Contains improved logic in the exploit script to help with some of the problems that have been encountered by users.
If you've had trouble rooting, please download the new version and try again!
Hey folks, I'm a UNIX admin by profession, so I took the challenge over the weekend to come up with an easy root process for Bionic stock Jelly Bean, specifically for those who aren't familiar with Linux.
I decided to build a Linux VM under Oracle VirtualBox on my Windows PC. This seemed like the logical choice since VirtualBox is free, a relatively small download, is easy to install and it's easy to import VMs.
My first attempt was using CentOS Linux. It worked, but the file required for users to download was over 450MB... Back to the drawing board!
Started looking for very small Linux distros and found Tiny Core Linux. This worked well. The file required for download is 50 MB.
Everything you need to root the Bionic is here and it is automatic. The process will walk you through connecting to the Samba file share, connecting the phone in USB debugging mode, and OF COURSE, it will run the process to root the phone.
Here are the steps:
1) Install Sun VirtualBox on your Windows PC.
http://download.virtualbox.org/virtualbox/4.2.12/VirtualBox-4.2.12-84980-Win.exe
Note: We've had one report that this file also works with VMWare Workstation and VMWare Player. If you don't want to install VirtualBox feel free try the file with VMWare.
2) Download the VirtualBox .ova file containing the Linux VM from one of the following links:
http://www.knite.net/Bionic/Root_Bionic_JB_20130501-4.ova
http://www.mediafire.com/?a2i6forosp77xrd
https://dl.dropboxusercontent.com/s...fhiAIiSwc0jD1AdVFNY27QdoeKP9ot_7IdDetSvw&dl=1
3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)
4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)
5) Follow the instructions on the Linux console.
That should do it. If you need help I will be monitoring this thread.
Willing Tester
I am not familiar with Linux but I am familiar with root, supersuser, recovery, and fxz/rsd lite. I am up for a new phone next month so I am willing to try this on my Bionic. This doesn't sound too hard....(famous last words). Will try on my Windows 7 laptop.
Will report if this works. Won't be able to until later today.
Thank you OP!
Found a problem with the script. Should work now. Download and import again, if you've already downloaded. I also managed to get the download down to 46MB by defragging and compacting the .vmdk file.
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1
Downloading new link now. Haven't tried to root yet. I'm at work right now.
Do you have any other suggestions before I start? I don't have to be completely stock do I...? (all stock apps, no superuser, etc.) I am on stock jelly bean 4.2.1, ver. 98.72.22.XT875.Verizon.en.US, stock recovery...but I did use OTA Rootkeeper so I have a (semi-functioning) superuser install. Do you suggest starting fresh with fxz?
I will be home in a couple hours to give it a try.
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Great, I just wanted to do something to make it easier for everyone, since so many seemed to be struggling with Linux.
lc75 said:
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Click to expand...
Click to collapse
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
TechnoHippie said:
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Click to expand...
Click to collapse
marty45714 said:
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
Click to expand...
Click to collapse
Ok that's gonna be my problem then ...I'll give it a shot when I get home and I'm not connected to my office network.
USB 3.0?
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
I am struggling with the directions and feeling dumb about it... Not sure what to put for the "Host IP Address"
EDIT: Restarted the virtual machine and it gave me the information I needed. The first time around the field was blank.
I appear to still lack root because the SU app wants to update the binary and fails to do so.
I'm not sure, but one thing you can check. When the Linux console is up in the VirtualBox window, there is a section in the lower, right hand corner of that window that shows a bunch of icons. Click the USB icon and very that you see your Bionic as an option for hardware that is connected to your laptop.
Also, I'm making an assumption that you have the Motorola UBS drivers already loaded on your Windows system before you even started this whole process. Maybe I shouldn't make that assumption???
cakessi said:
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
Click to expand...
Click to collapse
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
MNEman13 said:
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
New link. See original post. I have it on Mediafire now.
dcmcc99 said:
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
marty45714 said:
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
Click to expand...
Click to collapse
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
MNEman13 said:
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Click to expand...
Click to collapse
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
marty45714 said:
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
Click to expand...
Click to collapse
Here are some tips that I posted for someone over on Droid Forums. Hopefully some of this will help us figure out what is going on:
Need you to do some investigation. Run the exploit again. Once your phone is connected to the SMB share and the Linux script verifies the connectivity, press Ctrl-C to break out of the script and return to the Linux command prompt. Make sure your phone is connected to USB. From there execute the following commands and share the output with me:
sudo ash
cd /home/guest/share
./adb.linux shell
(if you execute the above command and DO NOT see this prompt: [email protected]_targa/ $
then you have USB connectivity issues and need to make sure you get your phone successfully connected
to VirtualBox and the Linux VM)
ls -l /storage/rfs0
I want to see the output of the "ls" command to verify that the SMB share is being mounted to /storage/rfs0
This can cause the exploit to fail is it's not.
If you see no output from that command, run this command:
find /storage -name pwn
If you get that far and this looks good. Can you type:
su -
and see if you get a root prompt? A root prompt means your prompt will end with '#' instead of '$' before the cursor.
If you do get this, it could be that your Superuser app is simply broken and need re-installed.
The command that the exploit runs to root the phone, once you get this far is:
/storage/rfso/pwn 1
You can try running that manually and see what happens.
caskieadam said:
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
Click to expand...
Click to collapse