Hello there,
Here's the 5.1.1 "update.zip" directly from /cache on my watch. I hope someone can do something with this
DropBox
OneDrive
MD5: d34b8c63ad43ccc3a797029d6dce7394
Greetings,
EpicLPer
Thanks!
The update.zip can be applied from recovery on the watch, the updated UI is a much-needed improvement.
OTA 5.1.1 manual update without root!
OTA 5.1.1 manual update
How I did it without root(!) and all stock (stock ROM 5.0.2 / stock bootloader / stock recovery)
1. download the update file (update.zip) from post #1 or here http://android.clients.google.com/packages/ota/lge_clockwork_gwatch_release_key/baaff49c592f87404c2df18f06aae64e5433359b.signed-platina-LDZ22D-from-LWX49K.baaff49c.zip to your pc
2. connect the LG g to adb
3. on PC enter: adb reboot recovery
(wait until you see the android on the watch)
4. on the watch tap the android
5. on the watch swipe up/down to select update via adb sideload
6. on the watch swipe left to right to activate update via adb sideload
7. on PC enter: adb sideload update.zip (or your downloaded filename.zip)
8. update process starts - wait until reboot and updating OS and optimizing wear apps.
READY!!!
bitstra said:
OTA 5.1.1 manual update
How I did it without root(!) and all stock (stock ROM 5.0.2 / stock bootloader / stock recovery)
1. download the update file (update.zip) from post #1 to your pc
2. connect the LG g to adb
3. on PC enter: adb shell
4. in shell enter: reboot recovery
(wait until you see the android on the watch)
5. on the watch tap the android
5. on the watch swipe up/down to select update via adb sideload
6. on the watch swipe left to right to activate update via adb sideload
7. on PC enter: adb sideload update.zip
8. update process starts - wait until reboot and updating OS and optimizing wear apps.
READY!!!
Click to expand...
Click to collapse
Merge 3 and 4 to: on PC enter: adb reboot recovery
bitstra said:
OTA 5.1.1 manual update
How I did it without root(!) and all stock (stock ROM 5.0.2 / stock bootloader / stock recovery)
1. download the update file (update.zip) from post #1 or here http://android.clients.google.com/packages/ota/lge_clockwork_gwatch_release_key/baaff49c592f87404c2df18f06aae64e5433359b.signed-platina-LDZ22D-from-LWX49K.baaff49c.zip to your pc
2. connect the LG g to adb
3. on PC enter: adb reboot recovery
(wait until you see the android on the watch)
4. on the watch tap the android
5. on the watch swipe up/down to select update via adb sideload
6. on the watch swipe left to right to activate update via adb sideload
7. on PC enter: adb sideload update.zip (or your downloaded filename.zip)
8. update process starts - wait until reboot and updating OS and optimizing wear apps.
READY!!!
Click to expand...
Click to collapse
thanks so much
still cant get it working cause my watch cant be found once i go into recovery
not sure what to do now
mayurh said:
thanks so much
still cant get it working cause my watch cant be found once i go into recovery
not sure what to do now
Click to expand...
Click to collapse
Did you used point 5 + 6 ? after reboot to recovery?
bitstra said:
Did you used point 5 + 6 ? after reboot to recovery?
Click to expand...
Click to collapse
Yep but sideload wont work and when i check it doesnt find my watch once the watch is in recovery/sideload mode
mayurh said:
Yep but sideload wont work and when i check it doesnt find my watch once the watch is in recovery/sideload mode
Click to expand...
Click to collapse
Hmm, I made it on a MAC, maybe on a PC (Windows) driver problems hook in???
Edit: try disconnect/reconnect USB while in recovery/ADB sideload...
thx for Update zip, also updated via recovery ADB Sideload THX alot
bitstra said:
Hmm, I made it on a MAC, maybe on a PC (Windows) driver problems hook in???
Edit: try disconnect/reconnect USB while in recovery/ADB sideload...
Click to expand...
Click to collapse
yep i think its a driver issue
tried disconnecting and re connecting.no change..pc makes a noise to show something connected but nothing else happens
mayurh said:
yep i think its a driver issue
tried disconnecting and re connecting.no change..pc makes a noise to show something connected but nothing else happens
Click to expand...
Click to collapse
Have you checked inside the Device Manager to see if the driver is really there. To me it sounds like its not so i would check that again and if its there try uninstalling it and reinstalling it that might help but it really sounds like you are having a driver problem
mayurh said:
yep i think its a driver issue
tried disconnecting and re connecting.no change..pc makes a noise to show something connected but nothing else happens
Click to expand...
Click to collapse
If you can hear the usb-connect-sound that means ADB lives in recovery!
Have a look into Windows device manager, it there is a (!) marked USB device.
Uninstall it yes and reconnect recovery watch once...
bitstra said:
If you can hear the usb-connect-sound that means ADB lives in recovery!
Have a look into Windows device manager, it there is a (!) marked USB device.
Uninstall it yes and reconnect recovery watch once...
Click to expand...
Click to collapse
yay finally got it right
checked in device manager and updated the drivers in normal mode, bootloader and adb sideload..
for some reason it showed samsung adb interface.but i just tried it
and it worked
5.1.1 thanks guys
Anybody tried it on TWRP RECOVERY,?
installation aborted - status 7 :\
Yeah, I keep getting installation aborted. Stock recovery and rom.
I had the same issue. Unlocking the bootloader and using Clockwork Mod driver when in ADB Recovery mode worked for me.
Can you post tose drivers?
Perfect install...THANKS!
Wahooooo......5.1.1 with the instructions works great!
Thanks!
I'm still getting status 7 error Installation aborted
Related
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
DakshMiglani said:
So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
Click to expand...
Click to collapse
very good how to! couldn't go wrong.! before step 4 I also check if device is connected via code: adb devices.
if device is not showing up you already know somethin's wrong.
Thank you for the guide. I pushed twrp into my phone without any error and I'm on the OTA 5.8.015S but it doesn't work. I rebooted into recovery and it still gave me the stock recovery screen.
Finally got it to work! After pushing twrp you have to type fastboot boot twrp.img and you will get a screen that looks like it's broken. Leave it alone for about 1 minute or two then the screen will turn off. Then press the power button once only to wake the screen up. From there twrp is working! Thank you to steve mars and jim262 for this tips!
Cannot mount /cust in TWRP
After trying to flash I noticed that after the wipes The failure of /cust cannot be mounted appears.
Can't get adb/fastboot to work on Windows 10
windhoarse00 said:
Can't get adb/fastboot to work on Windows 10
Click to expand...
Click to collapse
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Sörnäinen said:
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Click to expand...
Click to collapse
Were you asking for help or just wanted to help windhoarse00?
Amowagou said:
Were you asking for help or just wanted to help windhoarse00?
Click to expand...
Click to collapse
I don't have the phone yet - a mix of both, as I will be in a similar situation soon.
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Amowagou said:
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Click to expand...
Click to collapse
That's welcome news, cheers.
For me rooting a phone and putting a custom ROM of my choice is essential - not to speak of Titanium Backup to transfer all my stuff to the new phone.
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
nflau said:
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
Click to expand...
Click to collapse
Yep. I ended up with the exactly same issue.
Not working at all, no matter what I do.
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Sörnäinen said:
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Click to expand...
Click to collapse
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
nflau said:
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
Click to expand...
Click to collapse
Gearbest.
I'm already considering to just keep the EUI, but I do not trust their PlayStore installation...
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Sörnäinen said:
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Click to expand...
Click to collapse
Where to download the driver? Thanks!
nflau said:
Where to download the driver? Thanks!
Click to expand...
Click to collapse
No need to download. Just choose the list of drivers on the PC and take the one that's made for fastboot.
this is not real for dummies
this is what you forgot
1) after enable debug mode with tapping 7 times build you must actually enabyle usb debug in settings
2) to install the driver in win10 which dont work automatic unrar the adbsetup and then start in driver dir DPInst_x64.exe
3) after I did manage to adb reboot bootloader I got after reboot into the bootloader but then I am stuck
what is recovery image? and fastboot devices shows nothing
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
vespa70 said:
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
Click to expand...
Click to collapse
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
RAZERZDAHACKER said:
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
Click to expand...
Click to collapse
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
vespa70 said:
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
Click to expand...
Click to collapse
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
RAZERZDAHACKER said:
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
Click to expand...
Click to collapse
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
vespa70 said:
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
Click to expand...
Click to collapse
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
RAZERZDAHACKER said:
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
Click to expand...
Click to collapse
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
vespa70 said:
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
Click to expand...
Click to collapse
If you have an sdcard you can put the files on there and flash via sdcard.
RAZERZDAHACKER said:
If you have an sdcard you can put the files on there and flash via sdcard.
Click to expand...
Click to collapse
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
vespa70 said:
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
Click to expand...
Click to collapse
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
RAZERZDAHACKER said:
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
Click to expand...
Click to collapse
I am a little confused about this. This is what I have on the sdcard:
cm-11-20160603-UNOFFICIAL-kylepro.zip, TWRP.S7580.tar.md5, HDPI_gapps-kk-20160526-signed.zip.
I have done TWRP.. with Odin, is that what you mean "boot into it"??
"Hit install", where?? Wipe: Shall I "wipe cache partition"??
There is "wipe data/factory reset", but then everything is gone.
Please, can you show me point by point what to do, so I don't brick it all.
You know what, I stumbled across this video and it is basically a full tutorial! Lycka till med ditt flashande!
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
Ha, jag visste det från alla utropstecken , hoppas att allt funkar bra och om du får några bugg eller så rapportera det här.
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Activate "ADB Debugging"
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Thanks, your guide worked perfectly, there are no replies so it seems doubtful but it's very clear and perfect.
Updated my watch to Android wear 2.0, as it got flashed from stock recovery means it should be stock OS from Asus
You are the man!!! For some reason it kept getting stuck after adding my Google account, so I did a full data and cache wipe afterwards, and now it's working smooth. I haven't had a chance to really play with it yet to get a good feel for it, though.
EpicLPer said:
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Click to expand...
Click to collapse
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
matze19999 said:
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
Click to expand...
Click to collapse
A full ROM will require someone to dump it from their watch.
Lrs121 said:
A full ROM will require someone to dump it from their watch.
Click to expand...
Click to collapse
Yeah, I know ^^
awesome finally. just flashed the 6.0.1 again its syncing now. had the watch lying around 3 weeks since i got tired of charging 2 times a day with webwear.
can go straight to recovery and sideload the update or should i wait out the 6.0.1 syncing with my phone ?
I just wanted to add that for #8 I have a Windows 10 PC and Minimal ADB installed and you can just drag the file to the CMD window instead of typing all of that.
My watch has definitely recognized that I'm a developer, but I don't the message to "accept the connection on the watch" anywhere.
I am typing the adb reboot recovery command in the outer shell of CMD, but get the message "error : device '(null)' not found.
Windows 10 machine. A little help, please?
EDIT: Got it!
I forced the Zenwatch into Recovery Mode manually and accepted to install update manually.
Hi
I'm trying to updae but cmd says:
error: protocol fault (no status)
and in watch:
You need adb 1.0.32 or newer to sideload to this device.
installation aborted
???
After enabling the developer-settings, you need to enter those settings and activate ADB-Debugging. After that your watch will be recognized and you get the "Accept connection" message on the watch.
Hello,
I flashed my Zen2 this morning and do not notice any lag like others are stating...actually runs pretty good. One thing I do notice however is that my phone shows an active connected bluetooth device (like when connected to a car stereo or speaker). This is different than my Moto2 watch when connected to the same phone. Also on the older Wear 1.5 software did not show as actively connected as a bluetooth device. Does this mean the Zen2 will be using more juice or that we can use it as a portable speaker to play music? Just seems odd as I have always had multiple watches connected to the same phone. I just grab whichever suits my needs for that day. Why would this change by updating from Wear 1.5 to Wear 2.0? I suspect we will notice more drain on both the phone and the watch...time will tell. As far as those concerned with updating just do it as Wear 2.0 works fine once you get used to the change.
Cheers
Thanks this procedure worked for me. I di have to power off and power back on when first boot hung on animation
Update is perfect
wait was good
Procedure worked great, easy and fast. I am receiving email notifications on the watch but no text messages. Any ideas?
i waited out the 6.0.1 syncing to my phone before sideloading aw2.0
what i did:
reboot to recovery
sideload update
factory reset watch
clear watch cache (i know its alrdy done by factory reset but still)
reboot
still got stuck at booting the 1st time. boot animation forever.
hard rebooted the watch and aw2.0 came up fine.
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot format system
fastboot format userdata
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
matze19999 said:
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
Click to expand...
Click to collapse
THX!
TheDantee said:
THX!
Click to expand...
Click to collapse
You're welcome bro
So I followed the steps, zero issues. Everything went like you said it would. When it rebooted I was still on 1.5....i rebooted again and same thing. Did a full factory reset and still won't take the update even though it seems to have been loaded. Tried clearing cache as well. Any ideas?
Sent from my S8