Recently picked up a refurb G watch. However it appears to be in some debugging mode with a hidden menu of debug type tests. So I went into the about device section of the watch and something didn't seem right.
Software version: KKWT
Build number: platina-userdebug KKWT OPENMASTER eng.yjyj.kim.20140818.1125 39 test-keys
This doesn't seem like what I though it should say normally.
So I tried factory resetting the watch and after I got it set up again, I went into the settings and nothing was different.
Any ideas on how I can revert this back to the correct version of android wear or something?
Here is a link to the dump https://www.dropbox.com/s/vyp4ejxnipkjlnm/wearable-bugreport-2015-06-05-08-30-25.txt?dl=0
I figured it out. Once the device is connected to the dock and shows USB debug on the screen, you need to go to the hidden menu and find the port settings. There are four different options. The first and third are the same type of connection. You should be able to choose the first or third. Pay attention to the Device Manager, you should see ADB Interface, G Watch and CDC Serial. If you see that, then install the LG United Mobile Driver. After that you should be able to use the tool from XDA http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. Once you use the tool and get to the bootloader screen you will get another driver prompt in device manager for ADB Bootloader. Once the driver is installed you can completely use the XDA LG G Watch tool and Bob's your uncle!
tha_bigga78 said:
I figured it out. Once the device is connected to the dock and shows USB debug on the screen, you need to go to the hidden menu and find the port settings. There are four different options. The first and third are the same type of connection. You should be able to choose the first or third. Pay attention to the Device Manager, you should see ADB Interface, G Watch and CDC Serial. If you see that, then install the LG United Mobile Driver. After that you should be able to use the tool from XDA http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. Once you use the tool and get to the bootloader screen you will get another driver prompt in device manager for ADB Bootloader. Once the driver is installed you can completely use the XDA LG G Watch tool and Bob's your uncle!
Click to expand...
Click to collapse
I too got one of these watches. Unfortunately, all of them have a pre-production software version (KKWT). Because this was pre-production software it was never meant to be updated and cannot be updated
tha_bigga78, I tried what you said but something isn't happening right. To be clear, I tried this on two different computers: one that already had Android SDK on it and I have successfully used for ADB connections with my phone before, and one that had never been used for any adb/android software before.
The first time I got what you said, the three things in Device Manager: ADB, G Watch, and CDC. I installed the LG United Mobile Driver. I then downloaded rootjunky's tool from the link you provided and was able to see the device and to unlock the bootloader. Brilliant. But then after the watch rebooted rj's tool would never see the watch again. It sees my phone just fine. I made sure the watch has USB debuging enabled. After beating my head for an hour I did a fresh install on the 2nd, virgin, PC and got the same thing - it doesn't see my watch but if I plug in my phone and run rootjunky's tool I can see my phone show up in the list of devices just fine. Of course, on both PCs I did at rj's tool said and reinstalled the ADB driver through menu option 1. It didn't make a difference in either.
So now I am stuck with a watch that can't be updated and now won't communicate properly with my PC. I am left with a stripped down, pre-production phone and no way (that I know of) to fix it. Any ideas on what to do next would be great appreciated. Thanks!
intron1 said:
I too got one of these watches. Unfortunately, all of them have a pre-production software version (KKWT). Because this was pre-production software it was never meant to be updated and cannot be updated
tha_bigga78, I tried what you said but something isn't happening right. To be clear, I tried this on two different computers: one that already had Android SDK on it and I have successfully used for ADB connections with my phone before, and one that had never been used for any adb/android software before.
The first time I got what you said, the three things in Device Manager: ADB, G Watch, and CDC. I installed the LG United Mobile Driver. I then downloaded rootjunky's tool from the link you provided and was able to see the device and to unlock the bootloader. Brilliant. But then after the watch rebooted rj's tool would never see the watch again. It sees my phone just fine. I made sure the watch has USB debuging enabled. After beating my head for an hour I did a fresh install on the 2nd, virgin, PC and got the same thing - it doesn't see my watch but if I plug in my phone and run rootjunky's tool I can see my phone show up in the list of devices just fine. Of course, on both PCs I did at rj's tool said and reinstalled the ADB driver through menu option 1. It didn't make a difference in either.
So now I am stuck with a watch that can't be updated and now won't communicate properly with my PC. I am left with a stripped down, pre-production phone and no way (that I know of) to fix it. Any ideas on what to do next would be great appreciated. Thanks!
So, I think that the problem isn't with my PC
Click to expand...
Click to collapse
I think I may have left a part out....
Once you get the bootloader unlocked and the watch rebooted, you have to get the watch to the bootloader again from a powered off state. Follow the instructions here: https://www.youtube.com/watch?v=ftSCH7qihRI
Put it back on the cradle and see if it is showing ADB Bootloader in device manager. Install the drivers and continue from there.
tha_bigga78 said:
I think I may have left a part out....
Once you get the bootloader unlocked and the watch rebooted, you have to get the watch to the bootloader again from a powered off state. Follow the instructions here: https://www.youtube.com/watch?v=ftSCH7qihRI
Put it back on the cradle and see if it is showing ADB Bootloader in device manager. Install the drivers and continue from there.
Click to expand...
Click to collapse
Thanks! I will give this a try when I get home tonight.
This worked. Thanks a bunch!
I bought the same watch and same problems. Mananged to unlock the bootloader in windows. Just couldn't complete the proccess so I switched to linux and chose "restore" from "[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool" menu and now its like a new watch. Maybe should have just started in linux but its fixed now anyway.
Related
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
dsore1218 said:
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
Click to expand...
Click to collapse
I can't get mine to work either. Closest thing I've gotten is using omap4boot-for_optimus-v1.21
its different from some of the others, in that its a blue background and it doesnt actually list the p769. However, after selecting option 5, and following onscreen instructions, I was able to get my front capacitive buttons to light up, but nothing else. I can't enter S/W upgrade mode, I can't get LG recovery tool to recognise my phone, I am absolutely **** out of luck. I dont know if using omap4boot-for_optimus-v1.21 will help or hurt you, but im just explaining my experiences.
Have you installed the omap driver for fastboot?
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
I don't have Windows 8.1 so I'm not sure how to address the driver issue. I reer as wel.commend you uninstall the driver, both of them. The one under Android Phone in the device manager and the one called TI Boards in the device manager.
1. Uninstall all OMAP drives (Two of them)
2. Disconnect from the internet (to preventing Windows update from selecting its own driver.
3. Follow steps to fastboot. When connecting your phone have device manager open and right click the device that is flashing on and off (you will see the device manager refreshing and stuffs. It will dissappear after about two seconds but if you get the right click in and the option to install the driver, do it, point to the fastboot driver.
4. Disconnect phone after driver install and pull the battery.
5. Fastboot again, using option 1.
6. Quickly install same driver on the new device in device manager. Be quick.
7. Disconnect, Pull battery
8. Fastboot again
9. Flash ICS U and X
10. Make sure your LG drivers are installed.
11. Reboot PC.
12. Now you should be able to get into SW UPGRADE MODE with the plugging in of the USB
Should not lock up at 15%, make sure you have drivers installed for this.
13. Should work and reboot to home screen automatically.
14. If you really must, fastboot again and install JB U and X
dsore1218 said:
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
Click to expand...
Click to collapse
I've heard fastboot (and several other programs) aren't working on Windows 8. You need windows 7
Sent from my LGMS769 using XDA Premium 4 mobile app
Hi all
Recently, my optimus L9 (the P760), has started to get popups saying ''the process com.android.phone has stopped."
This started when I turned on my phone and suddenly I got pop-ups of multiple apps and processes being stopped.
Then the phone was suddenly off, without having given any kind of warning that it was going to turn off..
Then I restarted it, it got stuck on the LG logo for a while (didn't count, was about 1-5 mins) and then it said 'Encrypting' (under which I can see something I presume is a loading bar, but it's not loading) And under Encrypting, it has a button which says 'Reset phone', which won't work. I've tried it several times, restarted the phone (which also took 1-5 mins) several times, and have looked for solved threads about this on xda, as well as other forums..
There have been several threads like this, but none seems to be solved. That is the reason why I open this new thread.
My pc won't recognize the lg when I try connecting it either.. Nothing seems to be able to fix this, but my warranty has passed due to it being older than 2 years..
I really hope you guys can help me, thanks a lot!
Patrick
The final production run of L9s featured an encrypted bootloader, phones manufactured in 2013, if bought until early '13 this cannot be the case.
Anyway this means the phone is bricked, if you did not activate Android' s encryption feature.
The LG recovery tool should ve able to fix it in download mode. There are driver problems under Windows 8&10, but download mode should work and is also the final option before sending it in or dumping it.
For download mode switch phone off, then press Vol- while plugging the phone in and wait until it switches on by itself. Activating download mode after an off-on-off sequence seems to help when even download mode doesn't work as supposed. Seems to do the same as taking out the battery in between tries.
This was the last issue I had before my p760 got trashed by this tool http://forum.xda-developers.com/showthread.php?t=2748384 I wish you luck though.
There's various driver issues in the various connection modes the phone can assume.
First there's more trouble with Windows newer than Seven. This affects Fastboot and generally the recognition under Windows. And with a custom rom the LG drivers may not recognize the phone, thus all LG tools will fail too.
Best support is gained with two sets of drivers installed: LG usb drivers and Google SDK usb drivers.
With Artas' CM11, the Google drivers provided support for non-LG tools and ADB commands. The LG drivers only recognized the phone in Download mode and were necessary for unbricking it, as all tools for flashing KDZ files are based on LG's own tool, which needs the LG drivers.
The driver installation is less difficult on Win10 compared to 8.1, run the setup to install both ones.
On Win8.1 you may have to manually assign the Google drivers after their installation in device manager, they' re either found in the Android Phone category or the ADB interfaces one, while the LG ones sit invisible(!) in the other category(phone not recognized, remember?), but the phone recognition will be triggered by attaching it in download mode, and a virtual COM port will be installed.
Hopefully this was confusing, weird and silly enough, but if you manage to get it right, unbricking the phone is still quite possible.
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!
My LG L9 Optimus P769BK (T-Mobile) is stuck on Boot Logo. Hard reset or any other reset procedure in this world does not recover the phone to a normal state.
History:
-I rooted the phone a few months ago in order to get rid of some of the bloatware
-Ever since adware/malware keeps coming which made my wife's life miserable
- I unrooted it but that didn't change anything, the malware now resides within system apps so the misery continues
-The USB drivers are installed and the connection shows three entries in Device Manager
-LGE Mobile USB Modem
-LGE Mobile USB Serial Port
-LGE Mobile Composite USB Device
These are shown only when the phone is in download mode (VolUp + USB Cable In)
The only software that communicates with the phone and recognizes the USB port connected (Com41) is the LG Flash Tool V1.8.1.
Unfortunately this software processes the first 80% successfully until the reset stage after which the phone get stuck at the bootup logo (non-responsive) and never finishes the started flashing process.
I just want to re-flash it with stock ROM for which I downloaded v20h_00.kdz and converted the other required DLL, FLS and BIN files.
I know this is an older model but it was seldom used and I don't want to trash it. Thanks for any response in advance.
PC Desktop: Windows 7, x32, Clean Installation just for this purpose
Update: OMAP driver added
I noticed that I was missing OMAP drivers that are specific for the TI chip this model uses and I did install them. Now the phone has a new entry in Device Manager as Portable Devices where two drives/partitions are listed (F:\ and G:\) These are visible while the phone is stuck on the boot LG logo. The LG Flashing tool still can't continue after the reset at 80% so there is no really any progress yet. Any clue anyone?
Problem solved
I finally solved my problem with LG-P769
I don't know why I couldn't succeed earlier but it turned out using a laptop is a bad idea. I tried Windows XP, Windows 7 and Windows 10. The final solution worked on my desktop with clean Windows 7. The solution was using the trick with Small HTTP server. I don't know why it didn't work earlier but it seems another thread gave me a little bit more details that I missed at the beginning (maybe the server settings)
Anyway, it seems that this phone model was long time forgotten since there was not a single reply to my original post except my two updates so it turned out I was just talking to my self loud, LOL.
Anyway, I would like to thank this forum for most advanced postings regarding the Android branch of cell phones. Regards to whoever found this interesting enough to read.
So I have been trying to root my Moto G Power 2021 all day. I have been following the guide to using Magisk the non-twrp way, and I keep hitting the same snag over and over again. So far, I have successfully unlocked the bootloader, downloaded and installed the latest Magisk apk (Magisk25.2.apk) form the github page, and downloaded and installed the official Rescue and Smart Assistance (LMSA) on my computer. The problem that I am having is that whenever I plug my phone into my computer while I have RSA open, it asks me to authorize the computer to use it, but nothing opens on my phone to give me that option.
Before I am asked, yes I have Developer tools unlocked, the OEM is unlocked already (As I said above), and I have made sure that USB Debugging was allowed.
Please, tell me where I'm going wrong with this if anywhere?
The only other information I can think to add is that my phone IS running Android 11, but I'm unsure if that matters as I have seen other guides that explain how to root on Android 11.
Thanks in advance for any information that can be given!
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.cust...can-i-download-the-usb-drivers-for-my-device?
sdembiske said:
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Click to expand...
Click to collapse
Yes I did. I also tried uninstalling and reinstalling it when you linked it in case I didn't have it installed correctly, and that still did not work.
The below image is what I keep getting when I attempt to connect to RSA with my phone, and nothing at all like that shows up on my phone to verify.
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Thanks! I'll give that a shot and update when I've got a chance. I don't believe it's the USB cable since it's the cable that came with the phone, so I'll try the antivirus/firewall software side of things first.
Small edit:
I forgot to actually answer your question before. No, I hadn't already authorized this computer, as this is actually a pretty new computer (Only a few months old at this point). The USB debugging shows up at the top of my phone yes, but RSA won't do anything unless I authorize it, which gives me conflicting impressions that the phone seems to think it's verified the computer, but the computer and program don't see the verification.
sdembiske said:
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Click to expand...
Click to collapse
Thank you! That worked! I was able to get it sorted out, AND following the root guide, I was able to get my phone rooted too! Thank you very much again!
@Cloud557 How did you unlock bootloader? I have cricket moto g power 2021 but I checked with Motorola and apparently this model cannot be unlocked? Thanks