Related
Does anyone have access to an *unrooted* Wind phone with the original software installed? I have an idea how to assemble the original sbf for it: a fastboot recovery.
Basically, my idea is:
1) enable adb
2) use adb to reboot into fastboot
3) fastboot boot a custom recovery that will dump the relevant code groups to sdcard
4) use the pieces from the sdcard to assemble the original sbf
So, to try this I need someone that's somewhat technically comfortable (i.e. able to use adb and fastboot). I can walk someone through it on linux. I haven't made the recovery yet, it's sort of still a brainstorming mode. If anyone bites we can work the details out.
Basically, I'll implement it first for my phone and then post instructions. The phone will be left untouched by doing this (except for files written to the /sdcard).
I will look for it tomorrow why do you want it.
Ok
Sent from my Milestone XT720 using xda premium
We've never had the wind sbf.
it'll be hard to find Windmobile has discontinued the phone
of the existing users, not many are aware of XDA, and i've been spreading word of it on Winds forum
More than happy to help you
Mioze7Ae Your one of my hero that make that xt720 livable. I have 7 of those xt720 at work. I root them all and install custom roms exept one that I keep original to make a nandroid or SBF. If you help me, I have a chance for sucsess. I love all the linux distribution that are base on Debian, I dump Ubuntu becose I can not stand unity. now I am running mint on most of my computers. I am not a programmer but I am a hardware expert. I look forward to work with you.
sorry for my english I am french Canadian.
Stéphan
Great! Give me a few days to get some instructions/needed files put together.
Any luck with that? I have access to unrooted Wind XT720 if you still want it.
Ok, here goes:
Step 1: prepare sdcard (root of sdcard is /sdcard)
Download OpenRecovery-XT720-01.zip (http://android.fjfalcon.com/Files/Tools/OpenRecovery-XT720-01.zip)
Extract onto root of sdcard (creates /sdcard/OpenRecovery directory and OpenRecovery.zip)
Download attached dump-partitions-02.zip and put in /sdcard/OpenRecovery/updates
Create empty folder on root of sdcard called dump (/sdcard/dump)
Step 2: fastboot and dump (you need a computer that has both adb and fastboot working)
On PC: Download attached openrecovery-fastboot.img
On Phone: Enable ADB debugging
Plug phone into PC via usb
On PC: Run "adb reboot bootloader" on the PC
Phone will boot to "Fastboot bootloader"
On PC: Run "fastboot boot openrecovery-fastboot.img" (may require sudo)
Phone will boot into OpenRecoveryXT720
On Phone: select "Apply update" > "dump-partitions-02.zip"
Wait for dump to complete
Reboot phone
This will fill the /sdcard/dump folder with these files:
boot.img boot.md5
bpsw.img bpsw.md5
cdrom.img cdrom.md5
cdt.img cdt.md5
cust.img cust.md5
devtree.img devtree.md5
lbl.img lbl.md5
logo.img logo.md5
recovery.img recovery.md5
system.img system.md5
zip up the /sdcard/dump directory and send it to me and I will attempt to assemble an sbf. I don't think any of these partitions contain personal/sensitive data, but I can't be 100% certain so PM is completely fine or you can gmail them to me ([email protected]). Actually, it's possible that kpanic.img might have private/sensitive data (I think it's where crashed kernels get dumped so it could contain anything that was in memory at the time of a crash) and I doubt I need that partition anyway. So don't send that one if you're concerned about that.
Edit: just a moment -- removing kpanic from dump script
Edit: attached dump-partitions-02.zip which doesn't dump kpanic
Not sure if you're still needing this or if you got this, but a google search for this will give you what you need:
XT720_WIND__STR_U2_05.1F.2__USASHLSTAB14P2XAPCNWND03B.0R_1FF.sbf
I would link you but I'm new so I can't post a link
Use the droid developers link
403d said:
Not sure if you're still needing this or if you got this, but a google search for this will give you what you need:
XT720_WIND__STR_U2_05.1F.2__USASHLSTAB14P2XAPCNWND03B.0R_1FF.sbf
I would link you but I'm new so I can't post a link
Use the droid developers link
Click to expand...
Click to collapse
Another link, http://www.pda-planet.com/forum/forum386/thread233.html.
Instead of having instructions all over the place inside various threads I felt a clear guide should be available as it's own thread. Now since Google implemented this great feature (all hail google) where normal OTA's no longer work on Nexus devices with Android 5.0 that isn't 100% stock i.e. rooted with or without custom recovery a lot of people don't know how to update their devices.
IMO opinion the easiest way without losing any data is to use Fastboot and this is an attempt of a how-to-guide. This is made on a windows PC, probably works with other OS's too.
What you need:
1. You need ADB.exe and fastboot.exe inside an easy accessed folder i.e. put in c:\ADB.
The easiest way to get these are with this tool: http://forum.xda-developers.com/showthread.php?t=2317790
You can also get this by installing the whole Android SDK but that is just a waste of bandwidth and time.
2. You also need to download the latest factory image for Nexus 5. Do this here: https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
3. You might need adb drivers but you'll have to find instructions for this by yourself.
The procedure:
1. Extract necessary files. The factory image you'll download is named hammerhead-lrx22c-factory-0f9eda1b.tgz
This is an archive which can be opened with an extractor of your choice e.g. 7-zip
Inside this archive is another file with no file type extension. Extract this file and rename it to whatyouwant.zip since it's a regular zip file. Then extract all files within this file (very meta with zips inside zips inside zips etc).
The files you need for updating with fastboot are:
system.img
boot.img
radio-hammerhead-m8974a-2.0.50.2.22.img (rename this to radio.img for more convenience)
put all these files in the ADB folder (it will make things easier).
2. plug your phone to your PC. You need to have USB debugging activated in developer mode.
3. open a command prompt and orient yourself to the adb folder (c:\ADB)
4. type adb reboot bootloader and wait until your phone is in bootloader mode.
5. type fastboot flash system system.img and wait until it's finished.
6. type fastboot flash radio radio.img
7. type fastboot flash boot boot.img
8. reboot your device (type fastboot reboot).
Hopefully this will work and you will update without loosing any data. Then you can proceed with rooting, flashing custom recovery etc. This is easiest done with WUG nexus root toolkit (http://forum.xda-developers.com/showthread.php?t=2389107)
I couldn't find any other guide's but if there's already one please remove this.
Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.
Thanks for the guide @mertzi. I've just used to upgrade my Nexus 5 to 5.0.1 without any loss of data. I appreciate the help!
rootSU said:
Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.
Click to expand...
Click to collapse
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?
optoisolator said:
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?
Click to expand...
Click to collapse
No. The 4th section is the file path and location.
So this keeps user data? Just updated the system to 5.0.1?
Maintains root and all?
Sent from my Nexus 5 using XDA Free mobile app
Keeps user data but you will have to re-root.
Thank you, thank you, thank you.
I've spent last couple days trying to make heads or tails out of other "tutorials". Some of them linked the OTA update and gave instructions for full image, others gave instructions but lacked the links to the image. I am surprised that none of my searches took me here until today.
Thanks a lot for this guide I was ale to update to 5.0.1 thanks to this guide.
Can I use this method to update from 4.4.4 to 5.0.0 ?
... Not aire if you can jump from 4.4.4 to 5.0 this way...
I actually jumped flashing radio and baseband and THEN flashing CM12.1
I'm writing this so that you all will not have to go through what I just experienced when trying to flash the android 5.0.1 OTA manual update. Here are some of the errors I've gotten out of and I will give you some tips to get fix these. I always seem to encounter issues that no one else has when flashing, so here we go.
Tip 1
1.)If you are trying to flash 5.0.1 (tip applies to any version) from the google website here: https://developers.google.com/android/nexus/images ....Make sure your computer can handle ".tgz" files. This took me a day and a half to figure out. If you try to download one of the files off this website without the proper software to do so you will simply get a ".tgz" file that you cannot extract the necessary files from.
*The solution is to download winrar from http://www.win-rar.com/predownload.html?&L=0 this website. Once you do and run it the ".tgz" file will become a folder (icon should look like stacked books) and you can proceed to actually follow the instructions on the page where you downloaded the file from. I learned this the hard way.
Tip 2
If you dont really understand how to us the "ADB" tools or "SDK" and everything related sounds like a foreign language to you then watch this video: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/. It will explain how to copy files to your device while in bootloop. Pay special attention to the part about making sure your drivers are set up correctly. Drivers always get me when I installs. This knowledge will transfer over to downloading any rom or factory image in the future.
Links for Moving files to your device while in recovery:
Here are the appropriate drivers for copying files while in recovery to the nexus 5:
http://downloadandroidrom.com/file/drivers/Android/usb_driver.zip
Here is the fastboot link: http://downloadandroidrom.com/file/tools/fastboot.zip
Tip 3
The way I installed android 5.0.1 was:
1.)I downloaded the file from the google developer website that i pasted at the top
2.)I moved that file to a folder named "root" that i created on my desktop
*In this folder i have chainfire auto root http://autoroot.chainfire.eu/ in case i need to re-root my phone, I have the adb and fastboot.zip folders in my root folder as well.
3.)I moved the folder inside the FASTBOOT folder and extracted the file that i got from the developer website here. Once this is down there is another
3.)I extract the files here. After you extract there should be another folder called "image-hammerhead-lrx22c.zip." I copied those files to the fastboot folder as well so that they are outside of the zip file. I did not remove the zip file once I copied the insides to the outside. Right or wrong this is what I did.
4.)I used the Command prompt to navigate to this directory. Watch the how to copy files video to see how to navigate using the "cd" command
*basically i typed "cd desktop" which means change directory to the desktop. Then i did "cd root"....then "cd fastboot" ...YOUR PATH MAY BE DIFFERENT.
5.)Once i was here i could follow more of the instructions on the developer website. I could run that "flash-all.bat" command to begin flashing the 5.0.1. In order to run this command you literally type "flash-all.bat."
6.)After it finished it said,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
helpful links: http://forum.xda-developers.com/showthread.php?t=1992063
This was okay, what you dont want is falures. While 5.0.1 is being installed, if you notice it say failure in the place where everything else is saying "OKAY" you have a problem. One guy on that xda link said:
"Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img"
You can type this into cmd and do each one by one and it may work.
7.)YOU MUST MAKE SURE TO EXTRACT THAT SECOND FOLDER inside the developer file! If you don't you will get failures because the program is looking for them. That's why manually installing them may work as well.
8.)IF YOU SEE THE ANDROID WITH NO LOADING BAR UNDERNEATH this does not mean that you are bricked. I thought it did and kept flashing 5.0.1 over and over and over again. Then i just waited a bit and my phone rebooted and i saw the glorious dots rotating on my screen. I lived happily ever after.
9.)Once you are finished installing 5.0.1 you will loose root. Run that chainfire auto root program.You have to boot in to the bootloader screen...NOT RECOVERY...just the screen where you see the android and you can select "start" "recovery" etc. and open up that chainfire program and hit a key to start it. There are instructions on the actual program if you need help. If you are on the bootloader screen that i am talking about and you start the program it will "auto root" that is, automatically root your phone and thats that.
10.)Download root checker off the play store to see if you are actually rooted and have a blessed day. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Let me know if you need further explanation. I'm no pro but I've failed in soooo many ways i probably could help ya out! Jesus loves you all!
Hello good people of xda,
I recently like less then 2 weeks bought my first tablet, the NVidia shield k1 and I loved it. great gaming experience, support for my 64gb card, smooth work, good battery life but... since I updated to 6.0 all of that is gone.
My sd card can no longer by used to move apps too, formatting it to internal storage cause the tablet to "corrupt" my card.
Battery is dyeing like there is no tomorrow, tablet feel much less responsive, the list can go on and on.
Hence I'm looking for help and advice. I want to go back to 5.1 lollipop OS:
- is there anyway to make a rollback officially?
- what tools I would need (would I need to root my device or not??
- will rolling back void my warranty ?
I would appreciate the help on this matter, as since the update my tablet became a 200 dollars tray to carry drink around, and that is not cool at all (shame on you nvdia!!)
many thanks
Get your firmware version here :
https://developer.nvidia.com/shield-open-source
Then fallow this thread :
http://forum.xda-developers.com/showthread.php?t=2399737
Unlock bootloader
And instal your firmware by those commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Done!
I just rollback on K1 from 6.0 update to 5.1.1
Riddo said:
Hello good people of xda,
I recently like less then 2 weeks bought my first tablet, the NVidia shield k1 and I loved it. great gaming experience, support for my 64gb card, smooth work, good battery life but... since I updated to 6.0 all of that is gone.
My sd card can no longer by used to move apps too, formatting it to internal storage cause the tablet to "corrupt" my card.
Battery is dyeing like there is no tomorrow, tablet feel much less responsive, the list can go on and on.
Hence I'm looking for help and advice. I want to go back to 5.1 lollipop OS:
- is there anyway to make a rollback officially?
- what tools I would need (would I need to root my device or not??
- will rolling back void my warranty ?
I would appreciate the help on this matter, as since the update my tablet became a 200 dollars tray to carry drink around, and that is not cool at all (shame on you nvdia!!)
many thanks
Click to expand...
Click to collapse
You should try a factory reset first. Whatever method you use to go back to 5.1, you have to do a clean install, so, why no try a factory reset first?
Doing a factory restore doesn't reset the android version is just resets it back to fresh with android 6.0
What firmaware are you using. For k1 there is only extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364
It`s correct?
perun said:
What firmaware are you using. For k1 there is only extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364
It`s correct?
Click to expand...
Click to collapse
extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.sh
and what about next ??
I did a factory reset after the upgrade and it's been really smooth for me
Sent from my LG-H901 using Tapatalk
You need cygwin to unpack this fule using command bash ./name.sh
There's no userdata.img in the file and there's a blob file
OmenHTX said:
You need cygwin to unpack this fule using command bash ./name.sh
Click to expand...
Click to collapse
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
abati said:
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
Click to expand...
Click to collapse
Very simple way to roll back from 6.0
1) Get the software here :
https://developer.nvidia.com/shield-open-source
2) Unzip it and you will get a file_name.sh
2)Unlock your device using this guide :
http://forum.xda-developers.com/show....php?t=2399737
Unlock bootloader
3) Install cygwin to unpack the firmware you downloaded from 1)
use thiscommand bash ./File_name.sh
4) Add ADB and Fastboot path to your windows system path
5) where you unpacked the file_name.sh there should be a flash-all.bat
run it wait for it to finish and you should have a shield k1 back to factory with 5.1.1 installed
If you face any problem on the steps above you can always have a look at this tutorial for rooting your device because they differ very little from install a custom ROM.
http://nvidiashieldzone.com/index.p...tablet-root/root-shield-tablet-v2-1-lollipop/
I found with any ROM, if I factory reset than got to recovery, than default wipe, than load new ROM but start fresh with Google apps 1 at a time. Sometimes reboot after each app especially if it is a new rom or updated rom in this case being marshmallow. This has usually solved issues for me.
eraizel said:
Very simple way to roll back from 6.0
1) Get the software here :
https://developer.nvidia.com/shield-open-source
2) Unzip it and you will get a file_name.sh
2)Unlock your device using this guide :
http://forum.xda-developers.com/show....php?t=2399737
Unlock bootloader
3) Install cygwin to unpack the firmware you downloaded from 1)
use thiscommand bash ./File_name.sh
4) Add ADB and Fastboot path to your windows system path
5) where you unpacked the file_name.sh there should be a flash-all.bat
run it wait for it to finish and you should have a shield k1 back to factory with 5.1.1 installed
If you face any problem on the steps above you can always have a look at this tutorial for rooting your device because they differ very little from install a custom ROM.
http://nvidiashieldzone.com/index.p...tablet-root/root-shield-tablet-v2-1-lollipop/
Click to expand...
Click to collapse
thnx bro, I just watched someone unpacking the sh file on youtube via Linux, So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
---------- Post added at 11:35 PM ---------- Previous post was at 10:37 PM ----------
abati said:
thnx bro, I just watched someone unpacking the sh file on youtube via Linux, So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
Click to expand...
Click to collapse
nvm ma8 !
I managed to succesfully flash the official stock 5.1.1 as you just guided me, Your amazing big thanks !!!
abati said:
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
Click to expand...
Click to collapse
right click on flash-all.bat and click on "edit" you can find those lines with fastboot then started on order. After that reboot it. It will take 15' or longer to go to instructions screen.
Sent from my SHIELD Tablet K1 using Tapatalk
Cygwin
where did you actually learn to unpack the sh file. I have cygwin installed but i have not a clue on how to use it to unpack that file. I am trying to get back to Lollipop.
abati said:
thnx bro, I just watched someone , So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
---------- Post added at 11:35 PM ---------- Previous post was at 10:37 PM ----------
nvm ma8 !
I managed to succesfully flash the official stock 5.1.1 as you just guided me, Your amazing big thanks !!!
Click to expand...
Click to collapse
fairley said:
where did you actually learn to unpack the sh file. I have cygwin installed but i have not a clue on how to use it to unpack that file. I am trying to get back to Lollipop.
Click to expand...
Click to collapse
Try this tutorial, it helped me aswell: Sorry I cannot paste links so just google "how to geek how to use linux commands in windows with cygwin"
Guys, I followed every step in the forementioned guides and how-tos but I get always stuck with the NVIDIA/Android bootscreen (the logo). I downloaded and extracted the Linux folder and executed the flash-all.bat
Did this process several times now. Often after the flash if I go to recovery it is saying "cannot mount cache". Read something it has to do with the KitKat -> Lollipop upgrade and a cache.img is needed?
I just don't get why everybody else just don't have this problem though I did exactly the same steps... btw, this is an European / German device... but I don't think this is the problem?
Thanks
thanks for the links, but it still does not tell you how to unpack the file. Are their any other links you can give me?
Groohmsch said:
Try this tutorial, it helped me aswell: Sorry I cannot paste links so just google "how to geek how to use linux commands in windows with cygwin"
Guys, I followed every step in the forementioned guides and how-tos but I get always stuck with the NVIDIA/Android bootscreen (the logo). I downloaded and extracted the Linux folder and executed the flash-all.bat
Did this process several times now. Often after the flash if I go to recovery it is saying "cannot mount cache". Read something it has to do with the KitKat -> Lollipop upgrade and a cache.img is needed?
I just don't get why everybody else just don't have this problem though I did exactly the same steps... btw, this is an European / German device... but I don't think this is the problem?
Click to expand...
Click to collapse
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?