Hello All
I have a VS985 G3. I dropped it flat on the face and shattered the glass. I have a replacement ordered will be here tomorrow. I have a backup on my device and can access twrp using power and volume keys.
The problems begin here. I can not interact with the phone via the touchscreen to do another backup to my external sd. I can not for the life of me get my device recognized by adb. I can not transfer the current backup to my computer either because with the phone locked, I guess it wont read the storage on the phone, Cant unlock because welll I cant interact with screen. I have sdk installed and done so correctly because that is how I rooted this device to begin with. I know ADB was enabled in settings also. Yes path is correct to (C:\Android\sdk\platform-tools>adb devices #
Usage: adb devices [-l]
C:\Android\sdk\platform-tools>adb devices [-l]
Usage: adb devices [-l] ) is all I can get.
I downloaded LG USB drivers from LG site and still no dice on being recognized by ADB through command prompt.
My original thought was to disable the knock code through ADB ( dont even know if it possible)???
Second I thought I might be able to get my backup done through twrp but cant interact with screen to change storage location to external SD in TWRP. Im lost and dont know what to do from here.
Without adb working you're kinda Sol
Rockin Illusion 4.5 Verizon LG G3
OTG Cable and a mouse will get it done
Ful13rTruth said:
OTG Cable and a mouse will get it done
Click to expand...
Click to collapse
doesn't work for me :/ the mouse work but i can't open the knock code
DamiDev said:
doesn't work for me :/ the mouse work but i can't open the knock code
Click to expand...
Click to collapse
Do you have any smart unlocks like trusted places enabled? or maybe you could sneak past lock screen if you have google now set to run from lock screen?
Doesn't knock code require you setup a backup pin? can you use the mouse to fail at knock code and enter pin?
Related
Hello, when I go to use the ioroot for my LG G2 LG-D800 (Kernel Version 3.4.0) (Build Number KOT49I.D80020u) (Software Version D80020u) I click on the rar file, then click on the ioroot folder, then I click on the ioroot.bat and the cmd comes up and says:
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I have the LG suite installed, debugging enabled and accepted RSA key fingerprint. I put it on PC software to try it and It doesn't recognize that my phone is even hooked up or anything. Wondering what is going on. It's like it's having a communication issue. I think I have covered everything to ask.
Samsung Galaxy Legend said:
Hello, when I go to use the ioroot for my LG G2 LG-D800 (Kernel Version 3.4.0) (Build Number KOT49I.D80020u) (Software Version D80020u) I click on the rar file, then click on the ioroot folder, then I click on the ioroot.bat and the cmd comes up and says:
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I have the LG suite installed, debugging enabled and accepted RSA key fingerprint. I put it on PC software to try it and It doesn't recognize that my phone is even hooked up or anything. Wondering what is going on. It's like it's having a communication issue. I think I have covered everything to ask.
Click to expand...
Click to collapse
If the PC did not recognize the phone then the RSa key wouldn't have shown up. Check your device manager for any other driver issues.
Having trouble rooting LG G2
es0tericcha0s said:
If the PC did not recognize the phone then the RSa key wouldn't have shown up. Check your device manager for any other driver issues.
Click to expand...
Click to collapse
I checked in device manager and there is no problems with any drivers anywhere. Now when the RSA key comes up, does it only show on the phone or does it show on the computer also?
Phone. The g2 can be finicky showing it sometimes. It can come up quickly and get hidden behind the Charge / MTP / PTP interface. You only need to do it once until you reset or revoke permissions in the Developer Options. If it came up, then your connection works. It will not pop up otherwise.
Having trouble rooting LG G2
es0tericcha0s said:
Phone. The g2 can be finicky showing it sometimes. It can come up quickly and get hidden behind the Charge / MTP / PTP interface. You only need to do it once until you reset or revoke permissions in the Developer Options. If it came up, then your connection works. It will not pop up otherwise.
Click to expand...
Click to collapse
Well I know it did come up and I check the little box and hit okay but why does it show in cmd all this stuff?
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I tried hitting enter and nothing happened. ADB should already be enabled unless it isn't and I have to enable it some where and I have already accepted the RSA. I even tried reinstalling the LG suite but that didn't help. I have rooted tabs and a few other phones before but this one is a pain but then again I am pretty much a newb tho. I even tried Kingo Root and that failed also.
Samsung Galaxy Legend said:
Well I know it did come up and I check the little box and hit okay but why does it show in cmd all this stuff?
Enable ADB connection..
Developer Options unlocked ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue...
I tried hitting enter and nothing happened. ADB should already be enabled unless it isn't and I have to enable it some where and I have already accepted the RSA. I even tried reinstalling the LG suite but that didn't help. I have rooted tabs and a few other phones before but this one is a pain but then again I am pretty much a newb tho. I even tried Kingo Root and that failed also.
Click to expand...
Click to collapse
That's just the default stuff - like a check list. I don't think there is an issue with your adb connection because you saw the RSA key on the phone. That does not come up with out the adb connection. What mode are you on the phone? It should be charge to start.
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
munish1 said:
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
Click to expand...
Click to collapse
You have any proof that it actually works for the G2? They don't have a list of surported devices. Also, many people aren't comfortable with using Chinese rooting tools that don't have much documentation. It's irresponsible to suggest methods that aren't listed as known working without a disclaimer at least. As long as they are using the right version of ioroot (25) then it'll work.
Having trouble rooting LG G2
munish1 said:
Forget. All reply. Use. On. PC root genius. And install. USB. Driver. And. Adb. Installer. That. He. Are. Rotted
Click to expand...
Click to collapse
Root Genius did not work, neither did Kingo Root......WTF here is going on?
Samsung Galaxy Legend said:
Root Genius did not work, neither did Kingo Root......WTF here is going on?
Click to expand...
Click to collapse
Because those programs aren't the ones to root your device. You have the right program. You need ioroot v 25. I reread the first post and it seems that you are trying to run the program from inside the rar file. Did you extract it from the rar first??
Having trouble rooting LG G2
es0tericcha0s said:
Because those programs aren't the ones to root your device. You have the right program. You need ioroot v 25. I reread the first post and it seems that you are trying to run the program from inside the rar file. Did you extract it from the rar first??
Click to expand...
Click to collapse
I'm having trouble tho trying to find ioroot v 25?
Samsung Galaxy Legend said:
I'm having trouble tho trying to find ioroot v 25?
Click to expand...
Click to collapse
What version were you using??
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
But using the right tools will make life much easier and less frustrating.
Having trouble rooting LG G2
es0tericcha0s said:
What version were you using??
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
But using the right tools will make life much easier and less frustrating.
Click to expand...
Click to collapse
Using just named ioroot from XDA.
So my Nexus 4 had a faceoff with the driveway yesterday and the touch screen is dead. The phone seems to work fine otherwise. I was hoping to access my phone via USB to get a few files and read an unread SMS message. The problem is that for me to use any adb shell commands or USB debugging tools or anything, I need to be able to click on the authentication popup on the phone, which of course I cannot do. Is there any way to get around this? The device is rooted, and clockworkmod is installed, if that helps. USB debugging is also enabled. It's just the authentication I cant do. I'm also not afraid of command lines. I'll give anything a try.
The only idea I've found so far is maybe a USB OTG mouse, but I'd rather do it today from my computer than wait for an adapter to arrive in the mail. Any other suggestions?
Thanks
Hi
I do have a basic knowledge of bootloaders, rooting etc (have done all that on various Android phones), but with my new LG G5 H850 Unlocked European phone, I'm stumped. I have activated the unlock OEM in Dev Options, have enabled USB Debugging, installed who knows how many LG drivers, USB drivers, ADB drivers, etc, yet the DOS window can't see the phone.
I have a Windows 8.1 laptop. When I type adb devices into my Dos window, it can't see the phone (nothing comes up in the list). I type ADB reboot bootloader & it just says "Error: Device not found". In my laptop Device Manager it shows as a G5, it shows in Device Manager as the various Android devices when I change the various USB options from charge to photos, to file transfer, etc, I can happily move files between the phone & laptop within Windows Explorer, but my laptop just doesn't seem to see it within DOS.
I can't even manually boot the phone into Bootloader using the vol key & on/off switch, but I guess that'll take practice (even have trouble taking screenshots that way).
I guess I can't root without unlocking the bootloader? I've tried one-click root & King root, but both fail.
I'm obviously being a complete pratt & missing something somewhere (& am sure I'll kick myself if/when I find out).
Thanks
rockluvva said:
Hi
I do have a basic knowledge of bootloaders, rooting etc (have done all that on various Android phones), but with my new LG G5 H850 Unlocked European phone, I'm stumped. I have activated the unlock OEM in Dev Options, have enabled USB Debugging, installed who knows how many LG drivers, USB drivers, ADB drivers, etc, yet the DOS window can't see the phone.
I have a Windows 8.1 laptop. When I type adb devices into my Dos window, it can't see the phone (nothing comes up in the list). I type ADB reboot bootloader & it just says "Error: Device not found". In my laptop Device Manager it shows as a G5, it shows in Device Manager as the various Android devices when I change the various USB options from charge to photos, to file transfer, etc, I can happily move files between the phone & laptop within Windows Explorer, but my laptop just doesn't seem to see it within DOS.
I can't even manually boot the phone into Bootloader using the vol key & on/off switch, but I guess that'll take practice (even have trouble taking screenshots that way).
I guess I can't root without unlocking the bootloader? I've tried one-click root & King root, but both fail.
I'm obviously being a complete pratt & missing something somewhere (& am sure I'll kick myself if/when I find out).
Thanks
Click to expand...
Click to collapse
try to use driver from link below
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
now while making sure usb debug is enabled, try to see if in device manager in windows, you have the proper driver selected
I remember one time Windows did use a generic ADB driver that did not work with my G5 so this might be your case also
alternative way of testing is by trying to install a virtual machine and see if you can read it from there
most of the cases this is windows fault (you I know Microsoft douh)
gwolfu said:
try to use driver from link below
https://1drv.ms/f/s!Au9ppCUF0J7lgZpUFNW-cf8ot0EweA
now while making sure usb debug is enabled, try to see if in device manager in windows, you have the proper driver selected
I remember one time Windows did use a generic ADB driver that did not work with my G5 so this might be your case also
alternative way of testing is by trying to install a virtual machine and see if you can read it from there
most of the cases this is windows fault (you I know Microsoft douh)
Click to expand...
Click to collapse
Hi Gwolfu
Yup, I have that driver already, thank you for that. But I've now been able to unlock the bootloader. Guess a reboot was in order, as it's the first time I've turned on the laptop today.
Thanks so much for your reply though
Sigh!
When my watch connects to any PC via cradle, it's never detected. On Windows, I get a USB device malfunction. On Linux, it's not even detected. Via Bluetooth, it's unauthorised. So I can't even do basic file transfers to my watch. Anyone have a clue what I can do to get this working?
jrk190 said:
When my watch connects to any PC via cradle, it's never detected. On Windows, I get a USB device malfunction. On Linux, it's not even detected. Via Bluetooth, it's unauthorised. So I can't even do basic file transfers to my watch. Anyone have a clue what I can do to get this working?
Click to expand...
Click to collapse
I don't mean to insult, but do you have usb debugging enabled under the developer options and bluetooth debugging enable in the watch + app? If so, you might try an FDR on your watch (unpair with phone). I used a MacBook Pro when I unlocked the bootloader on my g watch thinking I was going to try Asteroid OS. I had just re-rooted my 6P using the Mac so I knew ADB/Fastboot was working on the computer. It wouldn't work initially and I knew the unlocking process was going to reset the watch either way. After the FDR everything started working again and I was able to unlock the bootloader. Don't know why but that helped me. Good luck.
Alexandgut said:
I don't mean to insult, but do you have usb debugging enabled under the developer options and bluetooth debugging enable in the watch + app? If so, you might try an FDR on your watch (unpair with phone). I used a MacBook Pro when I unlocked the bootloader on my g watch thinking I was going to try Asteroid OS. I had just re-rooted my 6P using the Mac so I knew ADB/Fastboot was working on the computer. It wouldn't work initially and I knew the unlocking process was going to reset the watch either way. After the FDR everything started working again and I was able to unlock the bootloader. Don't know why but that helped me. Good luck.
Click to expand...
Click to collapse
You're perfectly fine, no insult taken.
Debugging is enabled on the watch with Bluetooth as well, debugging is enabled on the phone and in the companion app. I get an authorization error and never get promoted for key on the watch, and when plugged in I get a USB descriptor error. I tried using another dock, another USB cable, and another port, and had no luck. I factory reset several times but I just redid it, so I'll give it another go and see if I can get it to work.
jrk190 said:
You're perfectly fine, no insult taken.
Debugging is enabled on the watch with Bluetooth as well, debugging is enabled on the phone and in the companion app. I get an authorization error and never get promoted for key on the watch, and when plugged in I get a USB descriptor error. I tried using another dock, another USB cable, and another port, and had no luck. I factory reset several times but I just redid it, so I'll give it another go and see if I can get it to work.
Click to expand...
Click to collapse
I had this issue for the longest time, try copying your adb_keys.pub from the ./android folder (I know it's C:/Users/yourusername/.android on Windows, and I believe it's ~./android on macOS/OSX, but I don't have a Mac to verify) on your computer to /data/misc/adb/adb_keys on the watch. You may need to either be rooted or have TWRP, I can't remember for sure because I was already rooted when adb had stopped working for me
zack4200 said:
I had this issue for the longest time, try copying your adb_keys.pub from the ./android folder (I know it's C:/Users/yourusername/.android on Windows, and I believe it's ~./android on macOS/OSX, but I don't have a Mac to verify) on your computer to /data/misc/adb/adb_keys on the watch. You may need to either be rooted or have TWRP, I can't remember for sure because I was already rooted when adb had stopped working for me
Click to expand...
Click to collapse
Well I have TWRP, but the watch isn't detected for mtp even connected to the PC...
jrk190 said:
Well I have TWRP, but the watch isn't detected for mtp even connected to the PC...
Click to expand...
Click to collapse
Have you tried to delete and update the drivers for the watch?
Hello All,
I broke screen on my vodafone smart prime 6 (vf-895n). Touch layer is broken and LCD too, there is big black blot covering 20% of display. New LCD is expensive and I planed to buy new smartphone soon, I wan't to use my old phone as LTE modem only in future. (like Huawei CarFi)
Current status:
- USB debugging disabled :crying:
- not rooted, stock recovery :crying:
- touch layer broken in middle, only upper half is working, I can enable/disable WiFi or BT, but I am not able to enter PIN, open menu, start apps, change settings, etc.
- linked to google account, I can install apps from google play
- I don't much care about data in phone, everything important is on sd card or synced on my google account.
Is there any way how to gain remote access to phone? like install some app from play store which starts automatically after phone boot up? or something with recovery mode?
Or only way is replace at least digitizer which is not so expensive?
Thanks in advance
You can try using OTG connected to a mouse. I don't have other solutions in mind
KMXSLR said:
You can try using OTG connected to a mouse. I don't have other solutions in mind
Click to expand...
Click to collapse
Unfortunatelly phone doesn't support OTG, even OTG cable + USB hub with external power + mouse is not working
Skopy123 said:
Unfortunatelly phone doesn't support OTG, even OTG cable + USB hub with external power + mouse is not working
Click to expand...
Click to collapse
Try running adb commands while your phone is in stock recovery, it's rarely working but it's a try.
Last solution could be calling Vodafone for help about that or go in a Vodafone shop
Hope it will help
KMXSLR said:
Try running adb commands while your phone is in stock recovery, it's rarely working but it's a try.
Last solution could be calling Vodafone for help about that or go in a Vodafone shop
Hope it will help
Click to expand...
Click to collapse
Thank you very much for help,
I tried to run stock recovery and select apply update from adb, then I can see phone in result of "adb devices" but opening shell, or reboot commands via adb is not allowed, it seems that in recovery mode only flashing new ROM is allowed.
From vodafone I didn't expect any reasonable help, and it was true, they only offer me repair phone for non-sense price (90$), even whole used phones in good condition are cheaper.
So I bought new digitezer from ebay for 10$ and I am waiting for it.
Ok, good luck!