Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
Short story, there's no "ethernet" option when I connect my G3 to my PC, and I can't get ADB to work (just says device offline).
Long story:
Had the G3 rooted with TWRP recovery, stock ROM. Made the horrible mistake of allowing the OTA update to run (I wasn't quite awake yet when the message came through).
This of course got me into the recovery bootloop which I fixed with the Flash2FixStuckRecovery zip.
However, at some point TWRP disappeared and I can only get to the stock recovery now. So....in an attempt to get TWRP installed, I'm trying to get ADB to recognize the phone and I can't get it working. The only two options I have on the phone when connecting via USB is MTP and PTP.
I've tried changing to PTP before hooking up the USB cable, then connecting, switching, killing adp, restarting adb, switching, etc etc. No good. All I get is "device offline".
The phone still has root, but I've got to get a recovery on here somehow. I'm having some other issues with root explorer not being able to read anything on the SDcard so I want to wipe everything and flash a new ROM.
Anyone have any ideas on what I can do to get this thing working?
Maybe (no guaranty):
Extract the twrp 2.8.2.0 .img and put it on your phone, as discussed in this post: http://forum.xda-developers.com/showthread.php?p=57338272
Install Terminal Emulator.
Launch TE
Input the series of commands in the twrp OP starting with SU (you did say you have root -- hopefully SU). On the last command, just input "reboot recovery", leave out the "adb".
(Alternately, at the end just exit out, do a restart, and install 4-way Boot from Play Store. I use that app often to go from my regular system to Recovery, or to power-off rapidly -- pretty handy.)
With any luck, you should now have twrp 2.8.2.0 installed. At that point you can flash a 10b boot, system, and modem set of .img (use autoprime`s flash2Boot, flash2Modem, flash2System, and the .img files that bweN diorD links to in a post in the General area: http://forum.xda-developers.com/showthread.php?p=57360121 ).
You should then be at a 10b rooted phone, with twrp 2.8.2. Your choice what to do next, but I'd recommend using a file manager to rename the /system/app LGDMSClient files, so you won't get future OTA.
As I said, no guaranty, but the steps make sense to me. I've used TE interchangeably with ADB multiple times to install stuff.
Good luck!
Thanks for that.
Manually doing it in terminal emulator likely would have worked, but that link got me the idea to use flashify which I ended up doing and it did work.
Now just working on the rest of the repair.
Thanks again
Cool, I thought about flashify, skipped it only because I saw mixed reports on it being used with installing twrp.
I've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!