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
Related
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...
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.
--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.
For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.
I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:
-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.
When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.
What am I missing?
I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")
I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.
Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
Problem finally fixed!
Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
markfm said:
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
Click to expand...
Click to collapse
... no dice.
Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.
Thank you markfm for the extra drivers.
I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.
Done and done!
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
scooterd said:
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You'll have to bear with me because I'm not familiar with Mac file structure.
I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).
I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.
If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.
Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
scooterd said:
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Click to expand...
Click to collapse
No problem at all, happy to help! It sounds like you have everything set up properly, however the terminal doesn't open automatically (you need to do it manually). But you shouldn't need to open the terminal to get ioroot to work, after you've unzipped the ioroot.zip file, simply navigate to the ioroot folder, right-click on ioroot.bat and choose Run as Administrator. That should run through the entire process for you.
If you want to test your adb connection (testing not required for ioroot to work) you'll need to open the command prompt manually. Press Windows Key+R, in the run window, type cmd and press enter, this will open the command prompt. When you're in the command prompt, you'll need to change directory to the location of adb.exe in the bts folder inside the ioroot folder. Mine was in a folder named android on my C drive so the address looked something like this: C:\android\ioroot\bts the command you'll type in command prompt would be: cd C:\android\ioroot\bts then press enter. Then you can type adb devices and see if you're connected properly.
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
---------- Post added at 04:33 PM ---------- Previous post was at 03:46 PM ----------
scooterd said:
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
Click to expand...
Click to collapse
You sir are a genious. After changing my USB cord, I'm rooted and all is well in the world. It's always the little things that matter
My Pleasure! It's the little things that matter and the little things that kill!! I'm glad you're finally victorious!:laugh:
EDIT: Nevermind, I got it to work through Internet>Ethernet.
postal302 said:
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Click to expand...
Click to collapse
Hi, hope this thread is somewhat still alive. sorry for the late add on... please help.
Sorry I'm a complete moron when it comes to rooting and ADB / RSA stuff and have no idea what exactly i am doing but for some reason my macbook won't allow me to authorize my oneplus. the authorize computer dialog box never pops up however i get a notification when my phone is plugged in that debugging is active. developer options have been reset, multiple usb cables have been used, and authorization has been revoked multiple times as well.
Im not sure how to access my adb settings on mac and when i attempt to go into terminal and try kill-server / start-server commands i get error messages as commands are not recognized.
Any help is appreciated as i can no longer use stock rom on OPO and i can't go about rooting my device
Wrong forum area -- this is for the Verizon LG G3 smartphone.
Same here! WITH NEXUS 7
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Jesusmaryqueen said:
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Click to expand...
Click to collapse
It is also possible to overcome the situation, by installing Mobilego software on your PC and follow the instructions accordingly (connecting your android using usb & debugging etc,.). You will get a RSA fingerprint request.. Easy Once it's done, u can close the mobilego software in the PC and open someother software for example Bacon root toolkit for oneplus one etc etc.. Hope this helps
adbkey doesn't exist
I don't know what i did wrong before, but my computer just DOES NOT have adbkey and adbkey.pub anywhere! First, i thought it was my phone's fault. Then, i tested in a different pc, and it worked. How do i generate those keys? There are no helpful answers in the internet yet...
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, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.