Related
Hi,
Is there any method to keep using stock Rom with root and do not wipe the data?
Thanks
Root nexus s rom 2.3.6
Ehi!
I'm also looking for that!!
I just got the nexus S whit the 2.3.6 rom and I want to root it, but I haven't find any answer online
someone can help us??
thanks!
http://forum.xda-developers.com/showthread.php?t=1007782 read this topic page1 and page 49 very important...
please click thanks button
- -
easiest way
just install from recovery this file
if i didn't upload wrong file...
does not work for me, signature verification failed...
here is the link for your question:
http://forum.xda-developers.com/showthread.php?t=935819
the link does not work for 2.3.6 as google fixed the issue on fasboot boot...
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Damned what a crap...
Has been two days looking around to find a solution, and seems not possible for the 2.3.6...
What a shame google to pretend having open source system and having no way to unlock your device without loosing your data as
- The data is wiped as you unlock the device.
- To fu**ing backup the data you need to have a fu**ing unlocked device.
WTF, I just got it in my ass..
If someone at last know a way....
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
plipness said:
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
Click to expand...
Click to collapse
As said before, does not work anymore for 2.3.6 as google has fixed this exploit...
I've looked all over, but cannot find anything on the problem I am having.
I go through the steps to load the current factory image onto my nexus s 4g through terminal on my mac, but for some reason it doesn't load everything. Here's what it says in terminal about the items that can't load:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
And here's what my folder looks like where I'm loading everything from:
I guess I can't post a picture from an outside source, so I'll just type in what my folder looks like:
boot.img
bootloader-crespo4g-d720spric1.img
flash-all.bat
flash-all.sh
flash-base.sh
image-sojus-jro03r
image-sojus-jro03r.zip
radio-crespo4g-d720sprilf2.img
there are files in the unzipped folder (image-sojus-jro03r) named:
android-info.txt
recovery.img
system.img
userdata.img
These seem to be some of the files that are missing, but even when i drag them over to the main folder, they still don't load. maybe something to do with the fact that they are .sig's?
I drag the flash-all.sh file into terminal and it loads and writes everything except for these .sig's, which I truthfully don't know what they are. Now I can't get into the correct recovery mode, it just shows some weird blue-lettered options that are different then the normal recovery options. That is why I think the fact that these .sig files are not loading is the problem.
I also booted up the new operating system and signed on, but for some reason none of my apps can download.
Sorry for my noobness, but I'm sure I'm missing one easy step that will fix my problems.
Does anyone know what I'm going through?
Any help is much appreciated.
Alright. I've searched the web and found a few different things. It seems that it's common for those .sig files to not load. Also, i loaded the factory image again and was able to download my apps.
I also now foolishly realize that to get a good version of recovery, I need to root my phone. I'm in terminal now, and for some reason adb is not showing my phone in adb devices. This wasn't a problem when I loaded the factory image, but now it's a problem when I'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1129759
step 5 is a problem, but hey, I can turn off the phone and go into fastboot mode myself. I guess step 7 is the next problem I'm dealing with. Here's what I get in terminal when I do step 7 manually (I put a *#* where my name is just so everyone knows):
MacBook:~ *#*$ /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img
-bash: /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img: Permission denied
Does anyone know what I'm dealing with this time around?
You probably need to enable adb in Settings --> Developer Options. If it's an issue with adb while in recovery, i'm pretty sure the stock recovery (which will be overwritten on every boot from a stock ROM) doesn't allow it. What you need to do is flash a new recovery in fastboot (not in recovery).
Commands (while in fastboot mode):
/path/to/fastboot devices <-- this will tell you if your phone is connected properly
/path/to/fastboot flash recovery /path/to/recovery.img <-- this will flash the new recovery
You'll need to type in the path to fastboot unless you have it in somewhere like /bin or a more convenient environmentally recognised location. The command you typed there is the same as trying to open the .img file as a script, you want to tell fastboot to flash the file to the phone and not open it with the computer.
Edit: Also, once you root, you probably want to delete /system/etc/install-recovery.sh. That file replaces any custom recovery with stock each time you boot.
Thanks Harbb.
That's what I ended up doing, using fastboot. it worked perfectly. I did try to find the /system/etc/install-recovery.sh file in root explorer, but could not find it. don't know where it is.
Everything is rooted and restored on my custom rom to where I was previously using titanium backup.
Here's the tutorial I was using: http://forum.xda-developers.com/showthread.php?t=1129759
with this video being a walkthrough of the previous tutorial: http://www.youtube.com/watch?v=sP9ZDWmbLVM
I was actually using the recovery img in the android folder that I downloaded from the tutorial, and not the one he told me to download, which was my problem in the end. Here's the link to the download page where I should have downloaded it from: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+4.0.0.2
Thanks again Harbb, much appreciated.
No worries buddy, glad you got it sorted.
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
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).
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?