I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
JaLex77 said:
I was getting Status 7 as well.
I flashed TWRP, did a full wipe of system, Data, Cache.
(Do not install Supersu) Reboot to Bootloader.
Fastboot Flash system, recovery, boot from LG G Watch Restore Tools.
Reboot to Recovery.
ADB Sideload option.
Adb sideload update.zip from PC.
Sucess!
Optional:
reboot bootloader
Fastboot flash TWRP
reboot
Click to expand...
Click to collapse
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Restore to stock with unlocked bootloader u cant update of its rooted.
Register ADB Driver
Lodorenos said:
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Click to expand...
Click to collapse
There shouldn't be a yellow Triangle when the driver installs. You have to assign the proper driver.
Update Driver>Browse My computer for Driver Software>Let me Pick from a list of Drivers on my computer>Android Composite ADB Interface>Next Complete
I had received this error because I had my phone rooted when I attempted to install the OTA via the /cache method.
What I sugest to you, to get this installed properly is to download the newest version of LG G Watch Tools and restore your watch to 5.0.2 and root it, push the update to /cache and make the /cache/recovery/command file but instead of rebooting normally like you would to trigger the update, instead run adb reboot-bootloader and restore your watch again to 5.0.2. The restore leaves /cache alone so this will work. Once 5.0.2 has been restored, use the fastboot options to boot into Recovery Mode, the update will start and install properly.
I do suggest doing a factory reset after running the update, as I was experiencing some performance issues after having done this until I had done a quick reset. Now it's running fantastically.
To solve any ADB problems, you should install the ClockworkMod ADB drivers, then open Device Manager, find G Watch in there and then right click, hit Update Driver, Let me find one, choose to choose a driver manually and then tell it that it is an ADB Interface, choose any of the ADB drivers that appear and then hit next. ADB should work for you after that.
ADB however does not seem to work inside recovery for 5.0.2 as I was unable to sideload mine due to it not showing in device manager at all while in recovery mode.
Related
I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
The scenario is that:
I purchased for the past year, ChainFire3d and found out to be effective. And right now I got a new phone and got it rooted. BUT, I forgot its running on 4.2.2 and ChainFire3d doesn't work on it. So, I am stuck on boot screen
I tried the following:
ADB commands to uninstall ChainFire3d, but in 4.2.2 roms, adb doesn't work in stock recovery for it has already have an alternative "update by adb support" which will let you go to adb sideload. And adb sideload mode doesn't support any other adb commands except sideload.
So, I tried to download a stock rom from a site, and tried to install it by "update by sdcard" and it says "Installation aborted" maybe because the stock recovery doesn't support the updater-script.
So, I tried fastboot, but fastboot cannot detect any device because stock recovery doesn't support adb.
And alas, I am out of options here.
Please help, somebody.
BTW, my phone is Lenovo A369i
OK... I managed to fix it.. after like... 10 hours .. whew
if you're wondering how I did it... here's how
...................
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I was running the latest Gohma when the update notification appeared on my watch. I have tried the following:
-Simply swiping left to install OTA update
-Using the tools including in Gohma's zip to restore to stock, then running update
-Both locking and unlocking the booloader and running update
-Using LG G Watch Tool (v9.7) to restore to stock and then update
-Once again, locking boatloader to try updating and unlocking to try it again
I don't know what else to try. A forum search hasn't revealed anyone else with this problem.
drdoombot said:
I was running the latest Gohma when the update notification appeared on my watch. I have tried the following:
-Simply swiping left to install OTA update
-Using the tools including in Gohma's zip to restore to stock, then running update
-Both locking and unlocking the booloader and running update
-Using LG G Watch Tool (v9.7) to restore to stock and then update
-Once again, locking boatloader to try updating and unlocking to try it again
I don't know what else to try. A forum search hasn't revealed anyone else with this problem.
Click to expand...
Click to collapse
You aren't actually restoring to stock then if you're using the Tools to restore as you should be updated to 5.0.2 when you do the restore (at least that's how it worked for me coming off Gohma), I did have to do some edits to my copy of the Restore Tools as for some reason my ADB wouldn't see the online device (even after authorized and installed) so I edited to remove adb wait-for-device and rebooted the watch into Fastboot where it restored fine.
ShadowEO said:
You aren't actually restoring to stock then if you're using the Tools to restore as you should be updated to 5.0.2 when you do the restore (at least that's how it worked for me coming off Gohma), I did have to do some edits to my copy of the Restore Tools as for some reason my ADB wouldn't see the online device (even after authorized and installed) so I edited to remove adb wait-for-device and rebooted the watch into Fastboot where it restored fine.
Click to expand...
Click to collapse
How did you do that?
I'm stuck too :<
yot2703 said:
How did you do that?
I'm stuck too :<
Click to expand...
Click to collapse
I'll check when I get home to my computer with the Restore tools sitting on it. It was part of the script that dealt with flashing. The other thing you could do is reboot into the bootloader and then manually flash in command prompt the correct files for the version you'd like to restore. I think 42Qsystem.img is 4.4w's system image and so on
I do notice that every so often, my computer will refuse to recognize the ADB interface as one. You can check in your device manager to see if this is the case for you, open Device Manager and check for "G Watch" or something similar while you have Debugging on. It will show under "Unknown Devices" right click the "G Watch" selection and hit Update Driver (you may need to install the ClockworkMod Universal ADB drivers first) and then hit Manually select a driver, it will ask you the driver type, hit ADB Interface and select any of the ADB drivers that show. Once it's installed, try again.
To skip using the tools, You'd do that by doing adb reboot-bootloader, or by swiping from the top-left to bottom-right on the screen during the LG Boot Logo, then in command prompt you'd change your directory to your Restore Tools
so cd C:\Path\To\Restore Tools\
fastboot flash <partition> <image>
So it would be something like:
fastboot flash system 42Qsystem.img to flash the system partition
fastboot flash recovery 42Qrecovery.img
fastboot flash boot 42Qboot.img
Please note that this is advanced and you will need to flash all of the image files for the version you select. The version is the 42Q in the example above.
However once I get home and look for the specific part I changed, I'll attempt to post it here.
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img