Database Info

Update to ICS

Hello,
point me in right direction please,
I had TF101 rooted and CWM installed,
First of all, I made backup and installed stock recovery from 8239USrecovery.zip file.
Next, I unfroozed DMClient and temperary unroot with OTARootKeeper
Unfortunately I removed some bloatware and can't update to ICS because of yellow triangle error,
found I have to update to 8.6.5.21 first (which is my current version)
I put WW_epad-user-8.6.5.21.zip file on sdcard, but i can't update to 8.6.5.21
"The update package is not compatible with your current software..."
now is fourth hour I'm googling and can't find 8.6.5.21 firmware to my TF101 (B60)

You can download the latest firmware from here http://support.asus.com/download.as...ansformer+TF101&os=&hashedid=gHh4q7I8dvWJzhdV
I think 9.2.1.27 is the latest ICS version.

What next?
gee one said:
You can download the latest firmware from here
I think 9.2.1.27 is the latest ICS version.
Click to expand...
Click to collapse
I accidentally bricked my ASUS TY101. Had down-graded it to root it, and upgraded it after. That worked, but when I tried installing another ROM (ASOP#5, I think) something went sideways, and I'm stuck on the boot screen.
ADB works, but I can't start the shell on the TF101, and I can't push a file as I don't know ADB syntax well enough, and everything read-only.
I have downloaded the latest ICS ROM (9.2.1.27) from ASUS, unzipped it once, and placed the extracted ZIPfile on the external micro-SDcard. However, CWM will not let me navigate to the micro-SDcard to select the ZIPfile to flash it.
Is there some way to skip past CWM to get to the ASUS loader - it is exists - so that I can use it to get to the ZIPfile on the micro-SDcard?
If not, is there something I'm missing with CWM?
Some syntax with ADB to get the push to work? What's the destination?
TIA;
Patrick

PMcHargue said:
I accidentally bricked my ASUS TY101. Had down-graded it to root it, and upgraded it after. That worked, but when I tried installing another ROM (ASOP#5, I think) something went sideways, and I'm stuck on the boot screen.
ADB works, but I can't start the shell on the TF101, and I can't push a file as I don't know ADB syntax well enough, and everything read-only.
I have downloaded the latest ICS ROM (9.2.1.27) from ASUS, unzipped it once, and placed the extracted ZIPfile on the external micro-SDcard. However, CWM will not let me navigate to the micro-SDcard to select the ZIPfile to flash it.
Is there some way to skip past CWM to get to the ASUS loader - it is exists - so that I can use it to get to the ZIPfile on the micro-SDcard?
If not, is there something I'm missing with CWM?
Some syntax with ADB to get the push to work? What's the destination?
TIA;
Patrick
Click to expand...
Click to collapse
To fix the read-only error, use adb remount.
Then you can adb push.
Sent from my Galaxy Nexus using Tapatalk 2

PMcHargue said:
I accidentally bricked my ASUS TY101. Had down-graded it to root it, and upgraded it after. That worked, but when I tried installing another ROM (ASOP#5, I think) something went sideways, and I'm stuck on the boot screen.
ADB works, but I can't start the shell on the TF101, and I can't push a file as I don't know ADB syntax well enough, and everything read-only.
I have downloaded the latest ICS ROM (9.2.1.27) from ASUS, unzipped it once, and placed the extracted ZIPfile on the external micro-SDcard. However, CWM will not let me navigate to the micro-SDcard to select the ZIPfile to flash it.
Is there some way to skip past CWM to get to the ASUS loader - it is exists - so that I can use it to get to the ZIPfile on the micro-SDcard?
If not, is there something I'm missing with CWM?
Some syntax with ADB to get the push to work? What's the destination?
TIA;
Patrick
Click to expand...
Click to collapse
OK. I managed to master the ADB command prompt well enough to "ADB Push c:\update.zip /sdcard/" Hey-zuss, there is a lot out there to read. After that, a few 2 tries with CWM got me to actually flashing '/sdcard/update.zip'
Steps I took:
Install the android SDK
Get the latest version of the ASUS ROM
Unzip the outer container.
Rename the zip carried inside to to "update.zip", and place it on 'C:\'
Start a command prompt in the directory with 'ADB.EXE' in it. (part of platform-tools for the android SDK)
In the command prompt, enter the statement, "ADB Push c:\update.zip /sdcard/update.zip'
Use ClockWorkMod to flash a new ROM, and chose the 'update.zip' from the root directory.
Chew nails.
(mine failed, so as a true windows user, I tried it again)
Chew nails.
Success.
The android SDK is easy to fin/install
The ASUS ROM is available from asus (find downloads/firmware for your system)
Now to time backup the ROM I have with CWM so I never have to do this again!

My Rooted N5, & Android 4.4.2

Hey guys, I have a rooted N5 with CF Auto Root. I have been trying to do a update to 4.4.2. however, every time I download it and go to install, I get a error upon reboot, The update doesn't install. I'm still rather new with rooting phones. I was hoping someone could give me some insight on how to install this? I had a friend tell me its possible to manually install the update if I could locate the files?
Thanks!

Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely

viking37 said:
Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely
Click to expand...
Click to collapse
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD

ItsStormy said:
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD
Click to expand...
Click to collapse
Install the android-sdk platform- tools, look here for how to https://www.google.nl/url?sa=t&rct=...OWoMssTikMpokJ6TtwEND5A&bvm=bv.61190604,d.bGQ.
Then put the rom/OTA you want in the platform-tools folder, reboot in recovery and select adb sideload and then in cmd type `adb sideload namerom.zip` to flash the zip.

Ooops, got it sorted, thanks guys!

ItsStormy said:
Hi again, so I've gone over the tutorials. However when I attempt to go through the steps within http://forum.xda-developers.com/showthread.php?t=2523217 - I keep getting the error 'adb' is not recognized as an internal or external command, operable program or batch file. What am I doing wrong?
Thanks!
Click to expand...
Click to collapse
You have not created a path, look here http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/ item 5, 6 and 7.

Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.

ItsStormy said:
Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.
Click to expand...
Click to collapse
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.

gee2012 said:
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.
Click to expand...
Click to collapse
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.

ItsStormy said:
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.
Click to expand...
Click to collapse
If you have stock recovery there should stand 3e recovery on top, if so reboot into bootloader and do what i wrote in the prior post. Or sideload the OTA with adb in stock recovery.

Thanks for the help gee2012
I leave you in good hands :good:

I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Dumb question, but is adb.exe in the android-adb folder?

jd1639 said:
Dumb question, but is adb.exe in the android-adb folder?
Click to expand...
Click to collapse
Now that you mention it, apparently not. I did however find this. And it is either in that location. I went into AVD Manager, but I don't see anywhere where I can install ''Android SDK Platform-tools"
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Best is to install the sdk straight to the C drive, so C:\android-sdk and not in a folder. The path vaiables to add would be \android-sdk\platform-tools.

[Q] Accidentally wiped the system and now my Nexus 5 says No OS installed!

I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:

Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk

First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app

Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.

raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk

All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache

raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/

thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk

raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.

1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk

rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?

Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy

thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.

rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option

Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.

thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk

rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were

thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect

Someone else posted twrp default path as /sdcard/downloads - try that.

Rotted, Team win, er how to update to 5.1?

pretty much says it all, its been a long long time since ive flashed anything ( and the last time i did something it didnt exactly go to plan )
Ive got a Nexus 5 (32GB) its rooted with team win recovery and i would like to update it to the latest version, preferably without losing any data
ive tried searching but there doesn't appear to be a simple guide on how to do this
any help would be greatly appreciated thanks.

There's a whole thread on ota's in the general forum. Start there. You have a number of different options. It would also help to know what android version you're on now.
Sent from my Nexus 5 using XDA Free mobile app

Your Nexus 5 is rotted?

Its not rotted yet, however my typing skills probably have.
Android version 5.0.1
just tried downloading the OTTA update and renaming it as update.zip
then adb sideload with adb sideload update.zip
then error : closed
and thats that.
the guides says this:
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Click to expand...
Click to collapse
OK, so on to section B as advised
Section B says
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Click to expand...
Click to collapse
Im on 5.0.1 so thats that out of the window

Download the latest Factory image.
Download the Android SDK.
Boot into bootloader (Vol- & Power). Connect the phone to your Computer. Check for exclamation marks in device manager.
If there are some install the drivers. If there are none extract the contents of the SDK. Copy the contents of the extracted factory image into the same folder (into platform-tools).
Open up the command prompt, by typing "cmd" into the search in the start menu. Once you are in cmd you can change the current folder with "cd" (cd .. gets you out of the current folder and into the above one, path wise / cd foldername enters a folder). "dir" lists the contents of the current folder.
Navigate to your SDK, into the platform tools folder.
Open the flash_all.bat (DO NOT DOUBLE CLICK, do a right click select edit). Type these commands one after the other (just the stuff starting with fastboot). So you flash the new bootloader, reboot, flash radio etc.
The latest fastboot has a "-w" in it. Leave that "-w" out, otherwise you will wipe your device.
Congrats, you flashed a factory image.
If you only want to flash parts of the "image-hammerhead.zip", extract it. It will have several .img files. You can flash these with "fastboot flash "image Type (system/recovery/data)" "filename.img" (without "" of course).

LG Urbane 2nd Edition Verizon W200V , Android Wear 2.0 Side load OTA Guide

Hey All,
This is my first ever post on XDA ,So forgive me if I have not done a good job. I will try my best to provide sufficient details on how to upgrade LG urbane 2nd Edition Verizon model watch to Android wear 2.0 from Android wear 1.5
Known Issues : **********Android Pay is not working as reported by few users ***********
YOU FLASH THESE FILES AT THE RISK OF BRICKING YOUR DEVICE. I AM SIMPLY PROVIDING THEM AND BEAR NO RESPONSIBILITY FOR ANY SUBSEQUENT DAMAGE FROM FLASHING THESE FILES. ALL DATA ON THE PHONE WILL BE ERASED.
Prerequisites:
[*]LG Urbane 2nd Edition Verizon Model (W200V) for all other model you should have received a OTA by now , Please check OTA software updates on you watch.
[*]ADB tools ( Minimal is also sufficient) google for files and install in your computer , in my case I did it in "C:\adb".
[*]twrp-3.1.1.0 (twrp-3.1.1.0.img) recovery Image Copy of the file :- https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k
[*]Android Wear 2.0 OTA udpate Copy of the file :- [*]Modified file link http://www.filehosting.org/file/details/699795/lg2.zip or original file https://android.googleapis.com/pack.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
[*]notepad++ (to edit updater-script), You can use Notepad as well.
1)perform factory reset on your watch just to be on safer side.
**update** Few users have reported that they have faced error while flashing due to buggy USB cable and they could successfully overcome the error by holding the cable to the watch and making sure the cable is fully in contact with the watch while flashing .**Update**
2)now we need to modify the OTA update file to work with Verizon model W200V ( skip this step if you have downloaded modified zip file and jump to 3rd step)
unzip the 'af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip" downloaded earlier and Browse the folder Edit file (updater-script) the file can be fount in the below path in my case."C:\ADB\af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8\META-INF\com\google\android\updater-script". Use Notepad ++ and open the file and Remove 2 first rows,The file should start from "ui_print...", I used Note++ to edit the file and saved, as mentioned earlier you can use notepad as well.
Now Zip All files And name LG2.zip(Note : don't put all the files into a single folder and then zip, The zip should contain "META-INF" and other files) and place it in "C:\ADB\LG2.zip" for easier navigation in Cmd. (this file can be downloaded using above link Modified file")
3)next Connect your LG Urbane 2nd Edition watch to Computer and Enable ADB Debugging On watch (Settings-About-Tap about 8 times on "Build Number" and now go back to Setting and scroll down you should see new options "Developer Options" , Tap on "Developer Options" - and "ADB Debugging" select "Enable always from this computer" or something like that !!)
4)Now Check if your device has a connection to your computer using ADB tools
now on your computer under "Run" , type Cmd, this will bring windows command prompt.
Open Cmd in Windows and browse to ADB tools folder in my case I have placed ADB tools and all required files under "C:\abd"
Type "adb devices"
your device should show up under "List of devices attached"
Once device is found by computer we have to push the TWRP recover image to phone , To make life easy , I have downloaded all the above mentioned files to "C:\adb" folder
"adb push twrp-3.1.1.0 /sdcard/"
later boot into bootloader
"adb reboot bootloader"
Unlock bootloader
"fastboot oem unlock"
5)Now flash TWRP recovery (because we will be changing/modifying the original the OTA update file, stock recovery will fail to verify signature)
"fastboot flash recovery twrp-3.1.1.0.img"
boot to recovery to perform OTA side load
"fastboot reboot recovery"
Now you should see TWRP recovery welcome page,Allow read and write partition permission in TWRP.
6)now on your phone you should be in TWRP Main screen , press Install and you will find option to adb Sideload select that option and you will be presented with a option to wipe Dalvik and Wipe Cache , Select that and now go back to your cmd and type below code.
"adb sideload lg2.zip"
Now sit back and relax , The system will starts loading Android Wear2.0 to your verizon LG urbane 2nd edition watch (W200V) and once the process is finished , reboot to system.
1st boot will take some time , Have patience !! after all you have done ever thing right till now. (approx 5-10 mins, sometimes 15 mins)
Now your watch has Android wear 2.0 , enjoy.
Initially it might feel the OS is slow but allow the OS to settle down after that its snappy and the battery backup is also good in my opinion.
If you want to restore Stock recovery image just in case if you don't like TWRP, then
download the below targz file and extrat recovery.img file , LG Urbane 2 stock recovery image.
Link ,
enable ADB options under settings similar what we performed earlier.
1) Boot into bootloader
"adb reboot bootloader"
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE(extract the file and copy recovery.img file to your folder , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files and you will see recovery.img file .
Place a copy of recovery.img in "C:\adb\recovery.img"
"fastboot flash recovery recovery.img"
You can also Lock Bootloader to avoid the Notification at each boot.
"fastboot oem lock"
To get back to original android watch wear 1.5
if you don't like Android wear 2.0 use the below link and follow instruction to revert back to Android wear 1.5.
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files.
Extract the *.tgz(targz) into your folder ("C:\adb")
Perform a "fastboot oem unlock", then run "flash-all.bat". Afterwards, you can "fastboot oem lock". This should restore you back to 1.5, where you need to take 1 OTA (from June 2016 Patch to December 2016 Patch).
Thanks All,

Missed something
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!

Has anyone other than the original poster tried this guide and been successful?

Thxfctr said:
Tried a thousand times. Not working
Click to expand...
Click to collapse
Are you getting any specific error ?

djdubd said:
Has anyone other than the original poster tried this guide and been successful?
Click to expand...
Click to collapse
It does work I had problems but I think holding the USB to the watch helps. I tried it a lot but it was worth it. Suck it verizon!

Thxfctr said:
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Click to expand...
Click to collapse
I am Glad finally it worked for you!!

suresh.chikkanna said:
I am Glad finally it worked for you!!
Click to expand...
Click to collapse
Ty! I think my USB connector is just a bit jinky.

I'm going to give this a try soon, everything working like lte, messages+, and phone?

Almost got it working
Followed all the directions and all seemed to work ok without errors. However, on startup now the watch is stuck on the startup splash screen (the animated google logo, has stayed there for hours). Can still access fastboot but unable to connect via ADB since the OS is not starting fully.
I also tried to restore back to 1.5 but since i can only access fastboot, my only option is to sideload but wont work with the TGZ link above.
Anyone have any ideas? or the zip file I could use to sideload the stock Wear1.5?
Thanks

Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.

Locked /data won't allow sideload.
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.

Gphoton31 said:
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Click to expand...
Click to collapse
I had similar issue initially , had to restore back to 1.5 and then clean all the data and then sideload 2.0 back. Try that and let us know if that worked.

You are the man! That worked
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.

suresh.chikkanna said:
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Click to expand...
Click to collapse
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]

Solved flash-all not working
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
---------- Post added at 06:37 PM ---------- Previous post was at 06:05 PM ----------
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.

Gphoton31 said:
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
Click to expand...
Click to collapse
I am really happy for you.

OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
Flash the original recovery.img extracted from the .tgz file and try again it should work.
For ADB access in TWRP use sideload using ADB option .

So will android pay work now with this

B
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?

I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?