Related
So, I downloaded an adbWifi widget, and followed the instruction and - woohoo - it works.
I'm trying to understand how is this secure (if it is at all).
I click with widget and it tells me an IP and a port. I tell adb/Eclipse this ... and it connects. So how come someone out there port-sniffing can't do the same, and connect to my phone?
GaJ
GreenAsJade said:
So, I downloaded an adbWifi widget, and followed the instruction and - woohoo - it works.
I'm trying to understand how is this secure (if it is at all).
I click with widget and it tells me an IP and a port. I tell adb/Eclipse this ... and it connects. So how come someone out there port-sniffing can't do the same, and connect to my phone?
GaJ
Click to expand...
Click to collapse
What wifi network are you using? If it's your own wifi network you control the security with a WEP key or hopefully something better. For example I have my own wireless router at home and I use WEP (to lazy to use something better).
By the way, which adb wifi program did you download and where are the instructions? I would like to try it.
-Vince
Nothing stops anyone on the same network from connecting to your wireless adb session if they know the port.
The best you could do is use a non standard port instead of the default 5555
I know the toggle I use doesn't give the option to choose a port but it is possible and asking the dev as a feature request might get the option. I have never bothered because I only use it on my secure network and don't know anyone irl that would know what adb is.
To start wireless adb with any port from a shell run "adb tcpip <port>" to restart the daemon on the specified port.
I personally think we should be able to password protect adb for if our phones are stolen.
Hoi,
can someone please tell me (us), HOW the Eclipse config must be modified ?
Right now i type in a dos-box the command adb connect <MyTCP>:5555.
When i click RUN in Eclipse it finds the device and all works fine.
I want to use this method permanently, so i am interested in the Config-Solution because my device didn't suck so much energy from the batterie as in WiFi-Mode (awesome effect, isn't it ?)
Doei
If you've never given permissions to a particular computer, it can't connect.
Hi all-
Does anyone know of a workaround for the OS-based restriction on tethering in the E970 stock firmware? I realize it will take a 3rd-party ROM release to fully remove this, which of course depends on an unlocked bootloader.. but in the meantime, is there anything that can be done? Any Play Store app that will bypass this problem?
Or if I call AT&T technical support and point out to them I have an unlocked, non-contract phone and I'm not even an AT&T user.. nor do I even live in the United States, will they provide some sort of unlock? :silly:
I have the Rogers e971 which is very very similar. I am able to tether just fine with the phone using an alternative carrier. Can you list the "restrictions" so we know what you are talking about.
Here you go. I have my Wifi hotspot configured exactly the same as my previous phone, but when I attempt to enable it I get this very helpful message..
I'm told by US friends that this is a restriction on AT&T Android phones, unless you pay AT&T a $10/mo. tethering fee to allow you to use your own data plan as you wish. So as far as I can tell, it's integrated at the firmware level? But I have no way to remove it yet, and I'm not even an AT&T customer. I assume the phone is attempting to verify whether I have 'tethering enabled' on my account.. which of course doesn't exist.
On my S3 there is a" tethering provision" you could disable using TB....nothing of the sort on the LGOG from what I can see.....hopefully someone will figure it out....
Galaxy S III I747
Browse to:
https://play.google.com/store/apps/details?id=com.koushikdutta.tether
Download the tethering app there.
You can thank koush by buying the pro version for $2.99.
---------- Post added at 08:58 AM ---------- Previous post was at 08:56 AM ----------
amrando said:
Hi all-
Does anyone know of a workaround for the OS-based restriction on tethering in the E970 stock firmware? I realize it will take a 3rd-party ROM release to fully remove this, which of course depends on an unlocked bootloader.. but in the meantime, is there anything that can be done? Any Play Store app that will bypass this problem?
Or if I call AT&T technical support and point out to them I have an unlocked, non-contract phone and I'm not even an AT&T user.. nor do I even live in the United States, will they provide some sort of unlock? :silly:
Click to expand...
Click to collapse
AT&T will laugh at you. I'm sorry but that is the reality here in the good ole USA where mega corporations act like feudal lords over the unwashed mass.
I'm on AT&T as well and that ClockworkMod Tether app is listed as incompatible.
EDIT: Nevermind, direct link to the apk works.
I'm on AT&T and native wifi tether works 100% on stock firmware...no 3rd party app needed
Sent from my ARCHOS 80G9 using XDA Premium HD app
xbutchx said:
I'm on AT&T and native wifi tether works 100% on stock firmware...no 3rd party app needed
Sent from my ARCHOS 80G9 using XDA Premium HD app
Click to expand...
Click to collapse
You probably have a tiered data plan that allows tethering. Doesn't work on unlimited plans.
You can try FoxFi from the Play Store, or WiFi Tether from someone here on XDA, I believe is where I got it. WiFi Tether wasn't working on my SG2 after the ICS update, but FoxFi did. Now FoxFi won't work on my OG, but WiFi Tether does. :shrug:
My OG is rooted and boot unlocked, but on the stock ROM, FWIW.
Edit: For typos and clarification. Also why do I have to wait 5 min to edit my post? How is that preventing spam?
Sent from my Nexus 7 using Tapatalk HD
Have any of you gotten the 10$/mo tethering fee tacked on after using these apps? I've heard AT&T is known to do that...
*bump*
Anyone found anything yet?
I know you could just replace the wifi drivers,because apparently that is what was done in the snow jellybean rom, but i dont have the know how to do this.
I would use the snow jb rom, but my signal gets all screwy, and my data speeds slow down drastically. May be just that im on straight talk. Anyways, i would hate to have to convert to nexus, just for wifi tether :/
cr4zy5pacec0w80y said:
*bump*
Anyone found anything yet?
I know you could just replace the wifi drivers,because apparently that is what was done in the snow jellybean rom, but i dont have the know how to do this.
I would use the snow jb rom, but my signal gets all screwy, and my data speeds slow down drastically. May be just that im on straight talk. Anyways, i would hate to have to convert to nexus, just for wifi tether :/
Click to expand...
Click to collapse
I've tethered if needed on every rom with zero issue, but never tried snow's JB
I think you'll have much success with the options to flash lately, and to be honest there is a way in one of the databases that also bypasses/enables the tethering in stock roms but for the life of me, I can't remember where I saw that one. The wifi drivers are in the ... sec lemme check..
system\vendor\firmware\wlan\prima\WCNSS_cfg.dat
and system/etc/wifi/ which has WCNSS_qcom_cfg.ini and WCNSS_qcom_wlan_nv.bin
but I'm not 100% if thats the location on stock rom either way, running a backup and dropping the files in there might be all you need if its really just the drivers, or you could just search for these files in snow's rom, which im assuming you have since you tried it, and then just replacing those in your rom.
Mind the permissions that are currently set, using whatever root file explorer your choice is, i.e. with ES File explorer, long press on the file, it will get a check mark on the right side, then on the bottom right click "more" and select properties.
for all files the permissions are -rw-r-r which you'll see in the screenshots and owner/group both root (scroll to the top when setting them, its the first entry)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pic 1 the properties view, pic 2 is what it looks like when setting permissions, just mirror the check marks, pic three is the system\vendor\firmware\wlan\prima\WCNSS_cfg.dat file, same permissions for it, also notice the two other files with it, they are just links from the system/etc/wifi folder, they are not actually there. I hope this helps you test your theory out, it should be very painless. and like I said, if the files are in slightly different folders, just adjust fire and mirror the locations accordingly.
good luck and please let me know if it really is just the wifi drivers that at&t screwed with, thats good info for future reference.
There are a couple other threads on this that detail specific methods. Since you're not an at&t customer you shouldn't be bound by their restriction!
If you want to use the built-in tethering functionality, you can change a key in the settings.db (something like tether_entitlement_check) using an sql editor. First time I tried editing that db, I trashed it because aSQLitemanager truncated the 91k db file to something like 80k, then I managed to overwrite the good backup with the truncated file also, and I had to do a factory reset. So be careful if you do this, edit a backup copy of the db first and copy it in place, and make an extra copy of the good one. I can't find where I originally read about this but it's similar for all of the at&t phones. I found a command-line sql editor that worked better for me in the end, btw.
wifi tether for root users works too - http://forum.xda-developers.com/showpost.php?p=39411328&postcount=13. I liked that it displayed a live traffic count (the built-in tethering data usage can be seen in the built-in data usage meter on the phone but it's not the same) but that stopped working with the JB update. And I sometimes had to reboot after using it before I could turn wifi back on.
What I usually really want to do is not really tethering - I want my phone connected to my wifi network which also has wired devices, and I want those devices to be able to route traffic through the phone. I wrote a script to connect the phone as a wifi client while mobile data is enabled, then setup the iptables rules to do the necessary NAT, and then I just have to change my wired devices' default gateway to point to my phone's wifi ip address (statically assigned in my router), OR just run a socks proxy on my phone and socksify as necessary on the computer.
Sorry I'm taking so long, somehow my new baby seems to get all my time these days lol.
Anyways, i looked inside the rom and her is what i found in the stock at&t rom.
In the vendor / framework there is only one file, i just went ahead and replaced it with the one in the snow rom.
Going to flash it over later today, and see what happens.
The attached, are what is inside the rom now.
I flashed the rom with the drivers swapped out, and everythinf worked fine, but still cant tether, i have tried the wifi tether app, foxfi, and the built in tethering, but nothing worked. I guess the next step is to try and edit that file.
cr4zy5pacec0w80y said:
I flashed the rom with the drivers swapped out, and everythinf worked fine, but still cant tether, i have tried the wifi tether app, foxfi, and the built in tethering, but nothing worked. I guess the next step is to try and edit that file.
Click to expand...
Click to collapse
I did the below steps & tethering works perfectly on my phone now. It requires rooted device.
Download Android SDK then make a folder on the root of your 'c' drive named android (mine is c:\androidSDK and is the path Ill use in this guide). Extract the contents of the zip file then navigate through the extracted file 1 level until you see the following files: add-ons, platforms, tools, SDK readme, and SDK setup. Copy all those files into the c:\androidsdk folder.
Connecting to and testing the ADB shell connection.
On your LGOG navigate to: settings>applications>developement and select usb debugging as this allows for the shell to interface with your phone. Plug in your epic with the usb cable provided with your phone and wait for drivers to load. Then on your computer hit start and type "cmd" (without quotes) in the search box (vista/7) or select run and type cmd (XP) then hit enter. You now have a virtual MS DOS window open type the following (each line is its own command and hit enter after typing each line):
cd\
cd androidSDK\sdk\platform-tools
adb devices
This should come up with your devices serial number and show that the connection is ready to be initiated.
Running the ADB shell
Make sure your phone is in USB debugging mode, connected to your pc and open a virtual dos window again: hit start and type "cmd" (without quotes) in the search box (vista/7) or select run and type cmd (XP) then hit enter. Type the following to enter the ADB shell (each line is its own command and hit enter after typing each line):
cd\
cd androidSDK\sdk\platform-tools
adb shell
You should now see a "$" (no quotes) and that signifies that you have the adb shell up and running.
Tethering :
With your rooted device, download SQLite Installer for Root from app store. Use the app to download the latest version of SQLite in the default place. The installer will be asking for root access, that's fine.
1.This is important. Go into settings and try to turn on hotspot. It will check with AT&T and subsequently fail to enable.
2.With USB debugging on, plug the phone into your computer and go into the command line and start up adb shell. Once in the phone's shell, type su and then open your phone to give it root access.
3.Type: cd /data/data/com.android.providers.settings/databases
4.Type the following to open settings.db: sqlite3 settings.db
5.Type this query EXACTLY: update system set value=0 where name='tether_entitlement_check_state';
6.Close sqlite by typing (there is a dot in front): .quit
7.Type 'exit' three times and close the shell
8.Restart the phone.
9.Try to turn on hotspot (or bluetooth tethering or USB tethering if you plug your phone in). You might get a warning about how tethering drains the battery, just ignore it and hit ok.
roockstaarr said:
I did the below steps & tethering works perfectly on my phone now. It requires rooted device.
Download Android SDK then make a folder on the root of your 'c' drive named android (mine is c:\androidSDK and is the path Ill use in this guide). Extract the contents of the zip file then navigate through the extracted file 1 level until you see the following files: add-ons, platforms, tools, SDK readme, and SDK setup. Copy all those files into the c:\androidsdk folder.
Connecting to and testing the ADB shell connection.
On your LGOG navigate to: settings>applications>developement and select usb debugging as this allows for the shell to interface with your phone. Plug in your epic with the usb cable provided with your phone and wait for drivers to load. Then on your computer hit start and type "cmd" (without quotes) in the search box (vista/7) or select run and type cmd (XP) then hit enter. You now have a virtual MS DOS window open type the following (each line is its own command and hit enter after typing each line):
cd\
cd androidSDK\sdk\platform-tools
adb devices
This should come up with your devices serial number and show that the connection is ready to be initiated.
Running the ADB shell
Make sure your phone is in USB debugging mode, connected to your pc and open a virtual dos window again: hit start and type "cmd" (without quotes) in the search box (vista/7) or select run and type cmd (XP) then hit enter. Type the following to enter the ADB shell (each line is its own command and hit enter after typing each line):
cd\
cd androidSDK\sdk\platform-tools
adb shell
You should now see a "$" (no quotes) and that signifies that you have the adb shell up and running.
Tethering :
With your rooted device, download SQLite Installer for Root from app store. Use the app to download the latest version of SQLite in the default place. The installer will be asking for root access, that's fine.
1.This is important. Go into settings and try to turn on hotspot. It will check with AT&T and subsequently fail to enable.
2.With USB debugging on, plug the phone into your computer and go into the command line and start up adb shell. Once in the phone's shell, type su and then open your phone to give it root access.
3.Type: cd /data/data/com.android.providers.settings/databases
4.Type the following to open settings.db: sqlite3 settings.db
5.Type this query EXACTLY: update system set value=0 where name='tether_entitlement_check_state';
6.Close sqlite by typing (there is a dot in front): .quit
7.Type 'exit' three times and close the shell
8.Restart the phone.
9.Try to turn on hotspot (or bluetooth tethering or USB tethering if you plug your phone in). You might get a warning about how tethering drains the battery, just ignore it and hit ok.
Click to expand...
Click to collapse
Tried this but sqlite3 settings.db doesnt open settings.db
Where am I going wrong?
harshmehta29 said:
Tried this but sqlite3 settings.db doesnt open settings.db
Where am I going wrong?
Click to expand...
Click to collapse
Download sqleditor pro free(see pic)
Afterwards go to com.android.provider.settings.
Afterthat go to settings
Then system
Then look for
Tether entitlement state check and change value to 0. Save, reset and voila!
Sent from my LG-E970 using Tapatalk
luisoman2000 said:
Download sqleditor pro free(see pic)
View attachment 2563287
Afterwards go to com.android.provider.settings.View attachment 2563289
Afterthat go to settings
View attachment 2563290
Then system
View attachment 2563303
Then look for View attachment 2563304
Tether entitlement state check and change value to 0. Save, reset and voila!
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Works perfect thanks a lot
roockstaarr said:
Connecting to and testing the ADB shell connection.
On your LGOG navigate to: settings>applications>developement and select usb debugging as this allows for the shell to interface with your phone. Plug in your epic with the usb cable provided with your phone and wait for drivers to load. Then on your computer hit start and type "cmd" (without quotes) in the search box (vista/7) or select run and type cmd (XP) then hit enter. You now have a virtual MS DOS window open type the following (each line is its own command and hit enter after typing each line):
cd\
cd androidSDK\sdk\platform-tools
adb devices
This should come up with your devices serial number and show that the connection is ready to be initiated.
Click to expand...
Click to collapse
I'm typing the command "cd androidSDK\sdk\platform-tools" and I keep getting back:
"The system cannot find the file path specified"
Not sure what I'm doing wrong, I've copied the appropriate files into the root file I created.
I have a Samsung Galaxy S III and I have a problem which occurs on all the roms I have tried so far: Paranoid Android, Cyanogenmod and Ultimarom: When using Automateit to frequently turn wifi on and off, wifi breaks after a while (no fixed time, sometimes there are days without problems), which means wifi can not be turned on again, neither manually, nor automatically. When turning it on, no networks are shown. The only fix is a reboot.
Now I am looking for a solution which could avoid the reboot. I want to now if there are shell commands to restart/reload the wifi module manually. Then I could use the Automateit-Shell extension to frequently do this automatically. Does anyone know how to do this?
Samba
sambahb said:
I have a Samsung Galaxy S III and I have a problem which occurs on all the roms I have tried so far: Paranoid Android, Cyanogenmod and Ultimarom: When using Automateit to frequently turn wifi on and off, wifi breaks after a while (no fixed time, sometimes there are days without problems), which means wifi can not be turned on again, neither manually, nor automatically. When turning it on, no networks are shown. The only fix is a reboot.
Now I am looking for a solution which could avoid the reboot. I want to now if there are shell commands to restart/reload the wifi module manually. Then I could use the Automateit-Shell extension to frequently do this automatically. Does anyone know how to do this?
Samba
Click to expand...
Click to collapse
From terminal on your phone:
1.
Code:
su
ls /sys/class/net
It will list your interfaces. For wlan it will probably be wlan0.
Then:
2.
Code:
ifconfig wlan0 down
For bringing it up:
3.
Code:
ifconfig wlan0 up
Tried on my stock 4.3 now, works ok for going down. But it automatically brings it up after ~ 10 secs.
Hi I can't connect to the Wlan Network at our university, which is using wpa2 enterprise.
When I click on the network nothing happens. On askubuntu I found something, but I don't know in which file on my phone I have to put the text in.
http://askubuntu.com/questions/586300/creating-a-wpa2-enterprise-connection-on-ubuntu-touch
Yes, WPA2 Enterprise isn't supported by the GUI yet.
The file you need to save that to needs to be called
Code:
/etc/NetworkManager/system-connections/<your network's id>
Replace <your network's id> (including the brackets) with the ID of your Wifi network. In the example it would be "eduroam".
(Please note that you need to save the file as root, i.e. using sudo.)
I tried it yesterday with the file, but it didn't worked. But I am not sure if the file is correct for our network.
I followed this guide http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ and now I get a connection. Only username and password have to be changed.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Sorry if this is a semi-hijack, but this seems the most relevant place for my question. I can't get access to my uni's wi-fi either (aquaris ubuntu edition phone), and I was wondering if anyone knows if the functionality for wpa2 is going to be added in the near future? I don't have ubuntu on a desktop atm and I don't want to have to install it just to tinker with my phone, which also seems a little bit daunting to me, worried I will explode my phone or something.
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
jonny-boy said:
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
Click to expand...
Click to collapse
That'd be great, although I've no idea what I'm doing with this sort of thing, would it be possible for you to explain it to me in idiot terms? I'm not familiar with putty or this kind of exercise
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
jonny-boy said:
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
Click to expand...
Click to collapse
So far I can't get the adb shell to recognise the phone is there, it just keeps saying "error: device not found" so I'm kinda stumped right now
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
jonny-boy said:
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
Click to expand...
Click to collapse
Did that, still says Error: device not found =/
Garatolla said:
Did that, still says Error: device not found =/
Click to expand...
Click to collapse
Tried it on my friend's linux pc as well and it still says error device not found, guess I'm just going to have to wait for them to officially add in wpa2 functionality. Welp, back to my old phone for a while then, thanks for the help jonny-boy
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Yup, I managed to find out about that before I first started trying to figure out how to fix this unfortunate situation
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Garatolla said:
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Click to expand...
Click to collapse
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
nikwen said:
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
Click to expand...
Click to collapse
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Garatolla said:
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Click to expand...
Click to collapse
Great that it finally worked.
Hi guys so I got the ATT version of LG V10 and I unlocked it. after put in my T mobile simcard everything works fine except for I wasnt able to get mobile data. So i set up a new APN and now mobile data is working fine with 4g Lte. However, when i tried to turn on my mobile hotspot, I kept getting this error.
Authentication was unsuccessful.
There is a temporary network problem that prevents the enablement of the Mobile Hotspot function. Please retry later.
I tried messing with the set ups and restarting and about all the things i can think of but still cant fix the error. if somebody know how to fix this please help me.
Thank you very much
SOCONFUSED123 said:
Hi guys so I got the ATT version of LG V10 and I unlocked it. after put in my T mobile simcard everything works fine except for I wasnt able to get mobile data. So i set up a new APN and now mobile data is working fine with 4g Lte. However, when i tried to turn on my mobile hotspot, I kept getting this error.
Authentication was unsuccessful.
There is a temporary network problem that prevents the enablement of the Mobile Hotspot function. Please retry later.
I tried messing with the set ups and restarting and about all the things i can think of but still cant fix the error. if somebody know how to fix this please help me.
Thank you very much
Click to expand...
Click to collapse
Hello, I was just wondering if you ever found a solution to this problem? I am thinking about unlocking my AT&T LG V10 and switching it over to T-Mobile but I would hate not being able to use the phone as a mobile hotspot on T-Mobile.
Please let me know if you found a solution, thank you.
Possible solution
In case anyone is interested, I found that the following helped my laptop to connect to my mobile hotspot and have interent access.
1. Download Settings Database Editor from Google Play
2. Scroll down to find "tether_entitlement_check_state" under the System Table and set it to "0" without the quotations.
3. Then you will need to download adb onto your computer. This tutorial is helpful: https://forum.xda-developers.com/showthread.php?t=2141817
3. Once you install adb onto your computer you will want to follow the steps about opening the cmd function as administrator and type "adb devices" in lowercase and no quotations so that your computer can find your device. If it cannot find the device then you will need to download the necessary drivers to your computer. This can be found at the lg main website. I just downloaded all of them.
4. Once it can find your device then type in adb shell. However, if it cannot find your device you may need to switch some things up like under Tethering in your phone, turn on the USB tethering. Type the command adb device once more. This should allow your computer to find it and authorize it.
5. Once device is found and authorized type in adb shell. Once that commands registers, then type in the following: "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" without quotations.
6. Now you should be able to go back to the Settings Database Editor app, change to global table and scroll down to find "tether_dun_required" and set that to 0. (You may find it helpful to also add these prompts in the adb command prompt as well by typing "settings put global tether_dun_required 0" without quotes after the adb shell command)
7. Now your laptop should be able to connect to your mobile hotspot (once it's set up and turned on your lg v10) If it still doesn't have internet access even though it's connected then you need to follow the steps from this website: https://www.digitalreborn.com/fix-android-wifi-tethering-dns-responding/
Yay! Success it should all work. Note I did not find the DNS Changer described in the above link. I just went to google play and typed in DNS Charger and picked the one that popped up first and followed the instructions, turned on my VPN and once it was set up and connected I had internet access on my laptop through my mobile hotspot! However, you will need to go through all these settings again if either phone or laptop restarts. I haven't figured out how to make phone and laptop to keep these changes. Hope this helps someone because it took me forever to figure this out. Shalom.
Solved
combat_chicka said:
In case anyone is interested, I found that the following helped my laptop to connect to my mobile hotspot and have interent access.
1. Download Settings Database Editor from Google Play
2. Scroll down to find "tether_entitlement_check_state" under the System Table and set it to "0" without the quotations.
3. Then you will need to download adb onto your computer. This tutorial is helpful: https://forum.xda-developers.com/showthread.php?t=2141817
3. Once you install adb onto your computer you will want to follow the steps about opening the cmd function as administrator and type "adb devices" in lowercase and no quotations so that your computer can find your device. If it cannot find the device then you will need to download the necessary drivers to your computer. This can be found at the lg main website. I just downloaded all of them.
4. Once it can find your device then type in adb shell. However, if it cannot find your device you may need to switch some things up like under Tethering in your phone, turn on the USB tethering. Type the command adb device once more. This should allow your computer to find it and authorize it.
5. Once device is found and authorized type in adb shell. Once that commands registers, then type in the following: "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" without quotations.
6. Now you should be able to go back to the Settings Database Editor app, change to global table and scroll down to find "tether_dun_required" and set that to 0. (You may find it helpful to also add these prompts in the adb command prompt as well by typing "settings put global tether_dun_required 0" without quotes after the adb shell command)
7. Now your laptop should be able to connect to your mobile hotspot (once it's set up and turned on your lg v10) If it still doesn't have internet access even though it's connected then you need to follow the steps from this website: https://www.digitalreborn.com/fix-android-wifi-tethering-dns-responding/
Yay! Success it should all work. Note I did not find the DNS Changer described in the above link. I just went to google play and typed in DNS Charger and picked the one that popped up first and followed the instructions, turned on my VPN and once it was set up and connected I had internet access on my laptop through my mobile hotspot! However, you will need to go through all these settings again if either phone or laptop restarts. I haven't figured out how to make phone and laptop to keep these changes. Hope this helps someone because it took me forever to figure this out. Shalom.
Click to expand...
Click to collapse
This worked for me, but I have a couple clarifications to add.
First, in case it wasn't clear, this does NOT require root to work. But after restarting the phone and/or uninstalling Settings Database Editor these steps need to be repeated again and again. Not that big a deal if u don't restart your phone often but still a pain in the neck. For me it's still preferable over rooting and installing a custom rom though so I'm very appreciative for this solution.
Also, finding the LG v10 adb drivers was the most time consuming part of the process. I found working ones here
Drivers also attached in case link goes dead