[Q] AT&T Wifi Tethering restrictions - AT&T LG Optimus G

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.

Related

[Q]Major issues with rooting my prime

So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet
lotsofllamas said:
So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet
Click to expand...
Click to collapse
Update your ADB drivers in device manager with the following
http://forum.xda-developers.com/showthread.php?t=1426502
Make sure USB Debugging is enabled within your TFP's settings (Developer options)
If that does not work then you have done something wrong.
Have a nice day
that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway
lotsofllamas said:
that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway
Click to expand...
Click to collapse
Well if you really want this, I would suggest the following:
We want to verify that your devices is correctly connect with ADB,(assuming you dont have adb set up) so lets set up Android SDK (which is good to do anyway).
http://developer.android.com/sdk/index.html
Download the .exe. Run it. It should create a folder in a location of your choosing, named something like "android-sdk". Browse to that folder, then to the 'tools' sub folder and run the SDK manager, install packages.
Next open the Command Prompt.
For example sake, lets say the location of your AndroidSDK is in the path
Code:
C://users/mike/android-sdk-win/
(Not sure what the sdk folder is actually called)
In the command prompt, enter
Code:
cd /users/mike/android-sdk-win/tools
(again replacing the location and name with the correct ones)
This will change the cmd location to the tools folder.
Then enter
Code:
adb devices
It will then list a device if one exists, if not then your adb drivers are probably not installed correctly.
If you need me to clear anything up, let me know
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
Hmm, I am really not sure. Sounds like you have done everything right.
adb devices is showing no devices which means viperMOD will not work.
When you plug the prime into your computer, on your prime,go to the notification bar and hit on the usb notification (not pc sync, the usb one), and when the settings menu opens up, which box is checked? MTP or PTP? if ones not working, try the other
if all else fails,
try it on another computer maybe?
lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.
demandarin said:
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.
Click to expand...
Click to collapse
It has nothing to do with the Prime time. As he has said, he got the android sdk setup and confirmed that "adb devices" shows no device, which lends itself to his device or drivers not being installed correctly.
Again, nothing to do with vipermod
everything to do with how he is connected (and i think he tried 'unplugging and replugging')
-------------------------------------
Lets Try this. The following may look intimidating but its very straight forward and after its done you will be more adept at adb and everything else (and hopefully be rooted)
1) Start=> Right Click "My Computer" => Properties => Advance System Settings => Advanced Tab=> Environmental Variables
---In the top box, there should be a "PATH" variable, if so hit edit and go to the end of whatever is there (make sure there is a ';' after whatever is there) and type the path to your android SDK tools folder (same folder you browsed to before in cmd)
My PATH Field looks like this
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\; C:\Program Files\Java\jre7\bin
(I also have java linked, this is okay if you do not)
If there is no PATH, just hit 'new'
The above allows you to, from command prompt, type "adb" from anywhere (ie, you dont have to be in the sdk folder which is nice)
EDIT: FLAW: the following app required root womp. I guess keep trying with the USB{
-Go to Device Manager, Uninstall Your TFP, before hitting refresh go to add new devices and select the drivers and what not.
-I will continue to try to think of an alternate method.
}
2)Download and Install this on your prime (NOTE THIS STEP REQUIRES BOTH PRIME AND PC TO BE ON SAME NETWORK)
-This method is ADB over wireless, so you dont need USB to be connected (infact just unplug it for this)
https://market.android.com/details?...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
Open the app and enable it. Note the "IP: port"
type in your command prompt (again if you did step 1, you can do this from anywhere)
Code:
adb connect <yourip:port>
your ip and port should be listed in that app
=> after that, try
Code:
adb devices
It should be there! this allowed you to bypass usb issues. I dont think you can use vipermod, but there is a more manual method we can use
3) Memphroid Root
(information taken from link below)
http://forum.xda-developers.com/showthread.php?t=1461736
memphroid binary
su binary
save both those files somewhere.. for example sake, make it your desktop in a folder called 'memphroid'
Open command prompt and change to the folder memphroid on your desktop
Code:
cd Desktop/memphroid
(the above assumes command prompt defaults at c:\Users\<yourname>\. if not just type in "dir" to get a list of directories that you can cd to)
you are now in the memphroid folder
assuming you did step 2 correct, you should have already connected with "adb connect"
now enter the following in cmd
Code:
adb push mempodroid /data/local
adb push su /data/local
adb shell
One line at a time, the first 2 push the files to the correct locations, the third one puts you into the 'shell' (basically terminal) of your prime (you should see a # now before where you type)
Then enter
Code:
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
Copy all of that and just paste it at once (i think its both at once, not one line at a time)
then type
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
And then here is the rest from that thread. I would just do all of the following except the first two lines starting with 'rm' because you havent rooted before
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
Click to expand...
Click to collapse
look to that thread linked for reference. if you neeed anything clarified or help, just post here. Please read my post carefully, following the step. I tried to be as clear as possible. I have never done the memphroid root before but it looks easy enough
Please hit 'Thanks' button, as I have taken the time to help
Still not able to get root...just tried Debugfs automated root tool and it stalled at "daemon started successfully" im seriously stumped here...

[TUTO] Dead screen, rooted phone, how to remote control

Hello!
First of all, I want to say that even though I'm describing a simple process, it was quite hard to find the answer for me.
I'm a SGS3 International Version (i9300) user and a few days ago I was at work, using flashlight on my device.
Suddenly I did drop my phone and the screen got cracked and the LCD too, making my device locked and from that point I couldn't see my messages, I couldn't backup my apps with Titanium Backup and, well, I needed to speak with a lot of people on Whatsapp. So, I decided to look for a answer at the internet.
I had a pattern lock screen, and I tried to remove the lockscreen with the steps to write on settings.db with sqlite but, no go.
I tried everything. I was using Temasek build with CM11 as base.
It was difficult to go into the phone. I had use the Android Screencast ( from code.google.com/p/androidscreencast ) but, I was only able to see what was on the screen, but with no interaction.
So, here is the best way to get into the phone, when you are ROOTED (IMPORTANT) and USB Debugging enabled:
(NOTE THAT ALL YOUR PHONE DRIVERS [adb drivers] SHOULD BE ALREADY INSTALLED)
Go to Google Play and download from there the app:
droidVNC Server
If you don't have any data enabled, then go to: APK DOWNLOADER
Paste the URL
Code:
https://play.google.com/store/apps/details?id=org.onaips.vnc
And download the app.
Open a prompt command, go to your adb folder, type:
Code:
adb install "type your downloaded apk path"
Go to your notepad app, and create a script with the follow commands:
Code:
adb shell am start -n org.onaips.vnc/.MainActivity
adb forward tcp:5901 tcp:5901
adb forward tcp:5801 tcp:5801
adb shell am force-stop org.onaips.vnc
adb shell /data/data/org.onaips.vnc/files/androidvncserver
Save inside your adb folder with a name like: VNC.bat
Note that I'm running Windows.
If you have another OS, then, run line by line or make your own script.
Now, you can click and run VNC.bat
It will appear a screen saying:
Code:
Waiting for a connection
NOW, it's almost done!!!
Indeed, you just have VNC working on your phone and, with the script you just made some ports to forward to your localhost.
So, you wont need any router or to be connected to a router.
Will be faster than Wireless connection.
So, download any VNC viewer you prefer:
I did use the Real VNC Viewer: Download Here
You will see a screen like this:
{
"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"
}
Type exactly what you see above:
Code:
localhost:5901
And you are good to go!!!
Now you can swype your pattern lock screen and see whatever you would see with your smartphone screen!
See ya!
Hello
Wow - if I could get this to work I would be very glad!
Followed your instructions but get the "error: Device not found, -Waiting for device-" message when I try to install the downloaded APK
I have a SG2 and screen is totaly dead, but when I turn it on I ca nhear the sound playing and the meny buttons have lights. So I now it's working
I appreciate any help you can give me.
Thanks
/Walter
wallerius said:
Hello
Wow - if I could get this to work I would be very glad!
Followed your instructions but get the "error: Device not found, -Waiting for device-" message when I try to install the downloaded APK
I have a SG2 and screen is totaly dead, but when I turn it on I ca nhear the sound playing and the meny buttons have lights. So I now it's working
I appreciate any help you can give me.
Thanks
/Walter
Click to expand...
Click to collapse
Have your device been rooted?
And... with USB Debugging enabled?
If it has... so, you just need to wait for your device to became fully loaded (after boot) and plug your USB cable.
Than, if your USB Debugging is enable for real, open Command Prompt and go to your ADB folder.
Type
Code:
adb devices
It should appear one device at least, something like the image attached:
If does not appear, then USB Debugging is probably off under your developer settings.
Hope I could help!
Great work man!
I hope I never need it, but it's good to know where to find some help...
ploquets said:
Have your device been rooted?
And... with USB Debugging enabled?
If it has... so, you just need to wait for your device to became fully loaded (after boot) and plug your USB cable.
Than, if your USB Debugging is enable for real, open Command Prompt and go to your ADB folder.
Type
Code:
adb devices
It should appear one device at least, something like the image attached:
If does not appear, then USB Debugging is probably off under your developer settings.
Hope I could help!
Click to expand...
Click to collapse
Thanks again
I am almost 100% sure it is on, but I get nothing. I think it might be the drivers that causing this.
tried it with my rooted N7 2nd gen and it worked. When I plugged it in, the PdaNET plinged and said something like "device ready". I dont get that when I plug in the SG2.
If USB not enabled - is it totaly lost then?
/W
wallerius said:
Thanks again
I am almost 100% sure it is on, but I get nothing. I think it might be the drivers that causing this.
tried it with my rooted N7 2nd gen and it worked. When I plugged it in, the PdaNET plinged and said something like "device ready". I dont get that when I plug in the SG2.
If USB not enabled - is it totaly lost then?
/W
Click to expand...
Click to collapse
Well, sure you need to have your drivers installed...
But, if you are rooted... then "supposedly" you already have the drivers installed.
I had one problem though that could be your case:
I had to wait about 2 minutes from turning it on until it shows up. And sometimes I needed to pull out the USB cable and replug it again.
Check your Device Manager (on Windows) if it shows up).
You can try that. If none of this works, than either the USB Debugging option is disabled or your cable is not functional.
Unfortunately, if it is the case, I really don't know what answer to you.
ploquets said:
Well, sure you need to have your drivers installed...
But, if you are rooted... then "supposedly" you already have the drivers installed.
I had one problem though that could be your case:
I had to wait about 2 minutes from turning it on until it shows up. And sometimes I needed to pull out the USB cable and replug it again.
Check your Device Manager (on Windows) if it shows up).
You can try that. If none of this works, than either the USB Debugging option is disabled or your cable is not functional.
Unfortunately, if it is the case, I really don't know what answer to you.
Click to expand...
Click to collapse
Thanks again for your answer
When I find some more time I will have it another go. Otherwise I think I will but an used SG2 and replace the screen. Since the phone have some years now, the used ones are pretty cheap (much cheaper than buying a new screen that is)
I would even settle with a cracked screen - as long as I ca naccess it and copy my data/SMS/MMS etc etc
Thanks again
/W
---------- Post added at 10:16 AM ---------- Previous post was at 09:22 AM ----------
Yay!
it worked, well...I got passed the "adb device" thing. I pluged out the battery, and reconected the USB and then it poped up.
But when I try to install I get this error
"/sbin/sh: pm: not found"
wallerius said:
Thanks again for your answer
When I find some more time I will have it another go. Otherwise I think I will but an used SG2 and replace the screen. Since the phone have some years now, the used ones are pretty cheap (much cheaper than buying a new screen that is)
I would even settle with a cracked screen - as long as I ca naccess it and copy my data/SMS/MMS etc etc
Thanks again
/W
---------- Post added at 10:16 AM ---------- Previous post was at 09:22 AM ----------
Yay!
it worked, well...I got passed the "adb device" thing. I pluged out the battery, and reconected the USB and then it poped up.
But when I try to install I get this error
"/sbin/sh: pm: not found"
Click to expand...
Click to collapse
Take a look at this thread HERE
It might have the answer
ploquets said:
Take a look at this thread HERE
It might have the answer
Click to expand...
Click to collapse
Yepp, I had managed to start the phone in some sort of "recovery mode". But the funny thing is this;
When I did so my PC managed to locate the phone correctly and I could identify it with the "adb devices" command.
But when I restarded the phone (hearing the Samsung tone - knowing it started correctly) I cant use the adc command (and no ping/notification from PdaNet)
Very odd
wallerius said:
Yepp, I had managed to start the phone in some sort of "recovery mode". But the funny thing is this;
When I did so my PC managed to locate the phone correctly and I could identify it with the "adb devices" command.
But when I restarded the phone (hearing the Samsung tone - knowing it started correctly) I cant use the adc command (and no ping/notification from PdaNet)
Very odd
Click to expand...
Click to collapse
So, it did not worked? Probably USB Debugging is not enabled.
My LCD is dead, managed to get the VNC server installed via Google Play on my desktop but this file does not exist on my device:
/data/data/org.onaips.vnc/files/androidvncserver
How do I start the VNC Server on my phone via ADB?
loonieryan said:
My LCD is dead, managed to get the VNC server installed via Google Play on my desktop but this file does not exist on my device:
/data/data/org.onaips.vnc/files/androidvncserver
How do I start the VNC Server on my phone via ADB?
Click to expand...
Click to collapse
I've said this on the instructions.
Go to: APK DOWNLOADER
Paste the URL
Code:
https://play.google.com/store/apps/details?id=org.onaips.vnc
And download the app.
Open a prompt command, go to your adb folder, type:
Code:
adb install "type your downloaded apk path"
Go to your notepad app, and create a script with the follow commands:
Code:
adb devices
adb forward tcp:5901 tcp:5901
adb forward tcp:5801 tcp:5801
adb shell /data/data/org.onaips.vnc/files/androidvncserver
Save inside your adb folder with a name like: VNC.bat
Note that I'm running Windows.
If you have another OS, then, run line by line or make your own script.
Now, you can click and run VNC.bat
It will appear a screen saying:
Code:
Waiting for a connection
I guess you didn't understand what I said the first time: it's already installed. The folder /data/data/org.onaips.vnc exists, but there's no files subfolder in there and no androidvncserver file anywhere on my device.
I'm on CM11...
loonieryan said:
I guess you didn't understand what I said the first time: it's already installed. The folder /data/data/org.onaips.vnc exists, but there's no files subfolder in there and no androidvncserver file anywhere on my device.
I'm on CM11...
Click to expand...
Click to collapse
try to do:
Code:
adb shell
cd /data/data/
ls
and see if there is any folder with org.onaips.vnc
ploquets said:
try to do:
Code:
adb shell
cd /data/data/
ls
and see if there is any folder with org.onaips.vnc
Click to expand...
Click to collapse
It's already installed through Google Play (remotely). When I run adb install it gives me an error that it is already installed:
Code:
3131 KB/s (2084419 bytes in 0.650s)
pkg: /data/local/tmp/org.onaips.vnc.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
However, in /data/data/org.onaips.vnc all I see is this lib symbolic link and nothing else:
Code:
[email protected]:/data/data/org.onaips.vnc # ls -al
ls -al
lrwxrwxrwx install install 1970-01-01 19:00 lib -> /data/app-lib/org.onaips.vnc-1
I also ran a find command to search for androidvncserver at the root level of my phone and did not find anything matching that name.
Any other ideas on how to run this on my phone through ADB? Otherwise I'm SOL...
loonieryan said:
It's already installed through Google Play (remotely). When I run adb install it gives me an error that it is already installed:
Code:
3131 KB/s (2084419 bytes in 0.650s)
pkg: /data/local/tmp/org.onaips.vnc.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
However, in /data/data/org.onaips.vnc all I see is this lib symbolic link and nothing else:
Code:
[email protected]:/data/data/org.onaips.vnc # ls -al
ls -al
lrwxrwxrwx install install 1970-01-01 19:00 lib -> /data/app-lib/org.onaips.vnc-1
I also ran a find command to search for androidvncserver at the root level of my phone and did not find anything matching that name.
Any other ideas on how to run this on my phone through ADB? Otherwise I'm SOL...
Click to expand...
Click to collapse
Ok... i've tested this with my LG G2 and, for my surprise, you are right...
But, the folder org.onaips.vnc/files/ wasn't there.
So, I opened the app and after opening, it seems that the app creates everything.
So, after a successful opening, you will see the files folder and the androidvncserver file.
I guess you can try to start the app with:
Code:
adb shell am start -n org.onaips.vnc/.MainActivity
After using this, then run all the instructions again from the main thread
Lucky!
ploquets said:
Ok... i've tested this with my LG G2 and, for my surprise, you are right...
But, the folder org.onaips.vnc/files/ wasn't there.
So, I opened the app and after opening, it seems that the app creates everything.
So, after a successful opening, you will see the files folder and the androidvncserver file.
I guess you can try to start the app with:
Code:
adb shell am start -n org.onaips.vnc/.MainActivity
After using this, then run all the instructions again from the main thread
Lucky!
Click to expand...
Click to collapse
Thanks! I got the server running, but now when I connect with any VNC client all I see is a black screen. I bet it is because my screen is locked. Do you see your lock screen with VNC and are you able to enter a lock screen pattern? I can press the home button to "wake" my phone up but the VNC viewer still only shows a black screen.
loonieryan said:
Thanks! I got the server running, but now when I connect with any VNC client all I see is a black screen. I bet it is because my screen is locked. Do you see your lock screen with VNC and are you able to enter a lock screen pattern? I can press the home button to "wake" my phone up but the VNC viewer still only shows a black screen.
Click to expand...
Click to collapse
Are you trying to use VNC connected to a wifi router or via USB?
I got this problem trying to use with and IP instead of localhost...
Try with USB exactly like I said on the main thread... It should work! That's why we forward those ports.
And, check if there is any application on your PC trying to use same ports 5901 and 5801
With me, I could see lock screen and could input my pattern to unlock... only thing that didn't work was PC keyboard, I had to insert manually any letter I would want with mouse, using "on screen keyboard"... like we are used to do with our fingers.
Hope it works for you !
Waiting your reply
Enviado do meu LG-G2

Has anyone found a way to root the LG Transpyre?

Having this phone non root is driving me completely insane. No greenifying system apps, bloatware, etc.
Are there any root methods on the computer that root all android phones?
Did you get this rooted yet?
See here: http://forum.xda-developers.com/general/help/lg-transpyre-root-4-4-2-t3021836
Found this to work for me on transpyre
I found this on another web site after almost giving up on my Verizon transpyre vs810pp i followed to the tee with the exception of install su from thr google store cause after root and boot it will b installed so just follow the guide and you to shall have root enjoy and props to the ones that gave us this gift.........
This is not my exploit to take credit for in anyways; and as always do this at your OWN risk. Credits to the creator(s) (I don't know who it is), the finder jgkim, and the translator Unjustified Dev.
Original post here.
A translated post here.
The original posts do not talk about the G3, but it DOES work for the G3. See post #636 and on where it has worked for others besides myself (on this XDA thread.) Tested myself on the VS985 (Verizon G3) and it has worked flawlessly. Others have tested on AT&T G3 (D850) and it has apparently worked fine as well!
I noticed quite a few people upgrading who didn't know much about this, and also quite a few people NOT upgrading because of the lack of root access, well this easy to follow tutorial should help with that. I think the instructions on the XDA post are quite clear and easy to follow, but I decided to post one here out of boredom. Originally I was going to just share the link, but why not? Enjoy.
How to:
Install SuperSU from the Google Play store and install it.
Download these files and extract the contents. I redownloaded all files and packed them together right after to ensure this file is safe. The files are the original rooting-require files along with MFastBoot (Basically adb without the Android SDK installed, it's quick and easier for me since I have not installed the Android SDK). It also includes the latest SuperSU Binary zip straight from the Chainfire website.
Enable USB debugging on your device. (About Phone > Build Number (keep tapping it until it says you are a developer) and then go back to the main settings. Go into developer options and enable USB debugging.)
With your phone screen on: Connect it to your computer via USB cable and put it into PTP mode. (USB debugging should report as on in the status bar.)
With your phone screen on: Hold shift and right click in the folder you extracted and open a command window. (Your phone will soon ask you to allow the computer, hit remember and yes! It may have even asked your prior to this step, just allow it.)
Copy this:
adb push g2_root.sh /data/local/tmp/
Right click in the command window and paste. Hit enter, and wait until it finishes (should take a second.) Now copy this:
adb push busybox /data/local/tmp/
Paste it in the command window and hit enter. Copy this:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
Paste it in the command window and hit enter.
Leave the command window open and disconnect your device. Turn off the device completely. Hold volume up and connect the USB cable to your device without touching the power button; it will go into download mode.
Find which com port your device is connected to (Device Manager > Ports > Your phone will be there, COM(Number) is what you'll need.
Go back your command prompt, and copy this:
Send_Command.exe \.\COM(CHANGEME)
Replace "(CHANGEME)" with the COM port number of your device. Now copy this:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Paste it into command prompt and hit enter.
Enjoy your root access! I don't think you can just do "adb reboot", so just disconnect your device and do a battery pull. Put the battery back in and boot up your device. Enjoy root!

Wpa2 Enterprise

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.

Mobile HotSpot not working

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

Categories

Resources