Manual Update using ota ( 5.01) - LG G Watch R

This only works coming from KNX01R!
Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
1. Root using tonu42's method here http://forum.xda-developers.com/g-watch-r/development/root-root-twrp-r-t2960511
2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).
3. Boot in the system and upload the update
adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip
4. adb shell
5. cp /sdcard/update.zip /cache/update.zip
6. echo 'boot-recovery ' > /cache/recovery/command
7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command
8. reboot recovery
9. Update installs
Thanks to tonu42 for root and intersectRaven for the stock boot.
Use at your own risk.

Does it remain rooted after the update ?

Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.

The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
nxt said:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?
I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
Click to expand...
Click to collapse

superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).
All is good now, thanks!
EDIT: Looks like SuperSU is still installed though (won't run)
Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock

Between step 4 and 5 you need to type su

You'll lose root and I am working on a fix.
Sent from my A0001 using XDA Free mobile app

Why all this manipulations? Why not use ADB Sideload?

superdave said:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
Click to expand...
Click to collapse
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).
AntonChernov said:
Why all this manipulations? Why not use ADB Sideload?
Click to expand...
Click to collapse
I'd like to know as well, which method is better/safer, this or ADB sideload?

Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.

Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit

Nice, good catch. I'll add that to the first post.
Camazza said:
Actually there's a faster and safer way that does not involve rooting.
1) Unlock Bootloader
2) Flash 5.0.1 Stock Recovery
3) Enter recovery and sideload update (it works in the new recovery)
4) Profit
Click to expand...
Click to collapse

superdave said:
Nice, good catch. I'll add that to the first post.
Click to expand...
Click to collapse
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb

kanzone said:
I did the same as following and it's work for me:
recoveryll.bin => 5.0.1 Recovery http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
5.0.1 Recovery work with adb
Click to expand...
Click to collapse
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?

b0gd4n said:
hey I am trying the same method:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
Click to expand...
Click to collapse
adb version
make sure the adb version is > 1.0.32

kanzone said:
adb version
make sure the adb version is > 1.0.32
Click to expand...
Click to collapse
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!
thanks!

So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?

i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?

Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
cottageboy said:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?
what the hell am i doing wrong?
I have also tried to fastboot a new recovery and I get the same thing?
Click to expand...
Click to collapse

hi,
when I am trying to flash the recovery I get this error:
fastboot flash rcovery recoveryll.img
target reported max download size of 268435456 bytes
sending 'rcovery' (6634 KB)...
OKAY [ 0.312s]
writing 'rcovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.403s
adb version
Android Debug Bridge version 1.0.32
any idea?
do I need to flash the new boot.img before?

Related

[Q] Stuck on Cyanogenmod Simple Recovery

Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Perez92 said:
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Click to expand...
Click to collapse
Follow this nkk71's Return to 100% Stock Guide!
majmoz said:
Follow this nkk71's Return to 100% Stock Guide!
Click to expand...
Click to collapse
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Perez92 said:
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Click to expand...
Click to collapse
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
majmoz said:
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
P.S. I am STUCK in Cyanogenmod Simple Recovery. I am not able to power down the device or get to any other screen.
Perez92 said:
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
Click to expand...
Click to collapse
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
So I was able to get my device past the first prompt. I now see the white bootloader screen and it does say "FASTBOOT USB". I downloaded the latest TWRP and placed it in the same folder as ADB and Fastboot. I did the second command to flash it, however I keep getting the error "error: cannot open 'TWRP.img'. Any idea as to what I could be doing wrong?
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
Got it to work. Used adb to get into fastboot. Then opened up the CM installer and let it redownload cyanogenmod onto my phone.
Thanks for the help!

[Q] Htc One stuck at Htc Logo

Hey,
I have a huge problem and do not know what to do. I write what is in the bootloader:
Locked
M7 UL PVT Ship s-on rh
Hboot 1.57
Factory reset do not work. I did not find anything in the internet. It seems the mobile is not rooted or had a custom rom right?
It is from T mobile and when the T mobile logo appears it is like the graphic card has a problem, then it stucks when the htc logo is there.
anyone an idea? If someone find the problem he/she can have a goodie :crying::crying::crying::crying::crying:
lutoluto said:
Hey,
I have a huge problem and do not know what to do. I write what is in the bootloader:
Locked
M7 UL PVT Ship s-on rh
Hboot 1.57
Factory reset do not work. I did not find anything in the internet. It seems the mobile is not rooted or had a custom rom right?
It is from T mobile and when the T mobile logo appears it is like the graphic card has a problem, then it stucks when the htc logo is there.
anyone an idea? If someone find the problem he/she can have a goodie :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
your phone looks like to be stock (unmodified) so you should first contact t-mob to repair/replace the phone under warranty. If a factory reset has not solved the issue you'll probably have, at least, to unlock the bootloader and that may void your warranty.
You might also want to try this command from bootloader:
Code:
fastboot erase cache
fastboot reboot
and see if the phone can boot normally, if not ---> claim warranty, if no warranty ---> unlock bootloader a flash a rom to see if the phone can boot with a fresh install, if not ---> probably an hardware defect.
alray said:
your phone looks like to be stock (unmodified) so you should first contact t-mob to repair/replace the phone under warranty. If a factory reset has not solved the issue you'll probably have, at least, to unlock the bootloader and that may void your warranty.
You might also want to try this command from bootloader:
Code:
fastboot erase cache
fastboot reboot
and see if the phone can boot normally, if not ---> claim warranty, if no warranty ---> unlock bootloader a flash a rom to see if the phone can boot with a fresh install, if not ---> probably an hardware defect.
Click to expand...
Click to collapse
no warranty. any good tut for the flash unlock thingg?
lutoluto said:
no warranty. any good tut for the flash unlock thingg?
Click to expand...
Click to collapse
first try to clear cache as it will not wipe any of your data from the phone
Code:
fastboot erase cache
fastboot reboot
then if it doesnt work you can try to unlock the bootloader (will wipe everything) and test if another rom can boot.
alray said:
first try to clear cache as it will not wipe any of your data from the phone
Code:
fastboot erase cache
fastboot reboot
then if it doesnt work you can try to unlock the bootloader (will wipe everything) and test if another rom can boot.
Click to expand...
Click to collapse
I did it. in the cmd it asks if I meant formating this partition, but said ok. but it is stucking on the logo again.
I think it is a hardware thing. but do you know what to do now to unlock it and get a rom on it?
lutoluto said:
I did it. in the cmd it asks if I meant formating this partition, but said ok. but it is stucking on the logo again.
I think it is a hardware thing. but do you know what to do now to unlock it and get a rom on it?
Click to expand...
Click to collapse
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3
alray said:
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3
Click to expand...
Click to collapse
I think you forgot to post them !?:crying:
lutoluto said:
I think you forgot to post them !?:crying:
Click to expand...
Click to collapse
yeah sorry http://forum.xda-developers.com/htc-one#root
:laugh:
alray said:
yeah sorry http://forum.xda-developers.com/htc-one#root
:laugh:
Click to expand...
Click to collapse
So I did this and it worked. BUT! I am in Clockwork recovery blabla where I need to select something from sd cardnright? but it is htc one m7 xD there is no sd card or if I cant get the back open. Something is written here in recovery sendingvia sideload!? any idea if there is a way get a file on my phone?
lutoluto said:
So I did this and it worked. BUT! I am in Clockwork recovery blabla where I need to select something from sd cardnright? but it is htc one m7 xD there is no sd card or if I cant get the back open. Something is written here in recovery sendingvia sideload!? any idea if there is a way get a file on my phone?
Click to expand...
Click to collapse
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.
alray said:
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.
Click to expand...
Click to collapse
Oh ****, I just did what was in the videos. So now I have to download the new cwm and flash it?! Ok wait a minute
lutoluto said:
Oh ****, I just did what was in the videos. So now I have to download the new cwm and flash it?! Ok wait a minute
Click to expand...
Click to collapse
not the new cwm recovery.... TWRP recovery 2.6.3.3.
alray said:
first, follow these 2 video tutorials to unlock the bootloader and flash twrp recovery 2.6.3.3
Click to expand...
Click to collapse
alray said:
You have flashed cwm recovery? like I said in post #6, you'll need to flash TWRP recovery 2.6.3.3. then you'll be able to adb push or adb sideload a rom to your phone.
Click to expand...
Click to collapse
you can flash TWRP recovery 2.6.3.3 the same way you did for cwm, same procedure:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
lutoluto said:
I think you forgot to post them !?:crying:
Click to expand...
Click to collapse
Hey, it is not opening the 2.6.3.3 I have. you have a link?
lutoluto said:
Hey, it is not opening the 2.6.3.3 I have. you have a link?
Click to expand...
Click to collapse
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
alray said:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Click to expand...
Click to collapse
okay and now?
lutoluto said:
okay and now?
Click to expand...
Click to collapse
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.
alray said:
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.
Click to expand...
Click to collapse
at format data he is unable to mount cache and when wipe he says not succesful. I will continue what you wrote and write then again
alray said:
boot in twrp recovery (bootloader ---> recovery)
when booted in twrp main menu, select "wipe" then wipe everything + format data
download this rom and save it in your adb/fastboot folder on your pc.
with your phone still booted in twrp enter this command:
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait between 5-10 min untill the file is copied to your phone (no progress bar, just wait until you get back the command prompt)
then in twrp select "install" from the main menu then browse the sdcard to find Android_Revolution_HD-One_71.1.zip and select it, swipe to confirm flash, wait until the rom is flashed and reboot phone and hopefully it will boot correctly.
Click to expand...
Click to collapse
When I type in what you said there is just a message saying error: more than one device and emulator.... T_T
lutoluto said:
When I type in what you said there is just a message saying error: more than one device and emulator.... T_T
Click to expand...
Click to collapse
so you have any other android device connected on your pc? if yes disconnect the other device or you can also direct the adb command to the specified device (your htc one)
find the serial number corresponding to your phone and use it with the following command
Code:
adb -s your_serial_number push Android_Revolution_HD-One_71.1.zip /sdcard/
to find your serial number do
Code:
adb devices
lets say your phone sn is HT386W890355
Code:
adb -s HT386W890355 push Android_Revolution_HD-One_71.1.zip /sdcard/
alray said:
so you have any other android device connected on your pc? if yes disconnect the other device or you can also direct the adb command to the specified device (your htc one)
find the serial number corresponding to your phone and use it with the following command
Code:
adb -s your_serial_number push Android_Revolution_HD-One_71.1.zip /sdcard/
to find your serial number do
Code:
adb devices
lets say your phone sn is HT386W890355
Code:
adb -s HT386W890355 push Android_Revolution_HD-One_71.1.zip /sdcard/
Click to expand...
Click to collapse
Okay now a lot of text is ran under the command. I think that is a good sign, I will wait

Manual OTA Update - NO ROOT

Here's how to sideload the update without ROOT.
EDIT: added a more precise description of every step
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
- Done!
If this was helpful to you, feel free to press the Thanks button :good:
Also, you might have to reinstall the ADB drivers since the device will be identified as Dory (LG G Watch) when sideload of 5.0.1 recovery is enabled. (LG's fault)
Camazza said:
Here's how to sideload the update without ROOT.
- Unlock bootloader
- Flash 5.0.1 Stock Recovery
- Enter recovery and ADB sideload the update
- Done!
Click to expand...
Click to collapse
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
EDIT:
nevermind, I did fastboot flash recovery... not adb boot recovery..
it's fine, uploading zip now.
b0gd4n said:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."
however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.
can someone please tell me what am I doing wrong?
EDIT:
nevermind, I did fastboot flash recovery... not adb boot recovery..
it's fine, uploading zip now.
Click to expand...
Click to collapse
Same
mchj said:
Same
Click to expand...
Click to collapse
Wait, what's the correct command for flashing recovery if it is not fastboot flash .img?
b0gd4n said:
ok, so I unlocked the bootloader, flashed the 5.0.1 recovery,
Click to expand...
Click to collapse
may I ask you for some help how did you download the 5.0.1 recovery? I am struggling with ezdownloader
Koopa777 said:
Wait, what's the correct command for flashing recovery if it is not fastboot flash .img?
Click to expand...
Click to collapse
I did fastboot flash recovery.img, and it looked like it was fine, but when I rebooted to recovery and started adb sideload, the pc did not recognise the device.
However, doing fastboot boot recovery.img, it booted straight to the recovery image and starting sideload was fine.
Can you list the correct steps (with commands) to do in order to flash it?
I'm not expert and I prefer to follow literally your steps.
Thx
Kickoff said:
may I ask you for some help how did you download the 5.0.1 recovery? I am struggling with ezdownloader
Click to expand...
Click to collapse
I guess...don't use that ezdownloader (untick the option).
I also uploaded the img here.
Kickoff said:
may I ask you for some help how did you download the 5.0.1 recovery? I am struggling with ezdownloader
Click to expand...
Click to collapse
Are you having problems downloading it through dev-host? Be careful as there are two download buttons on that page, one is legit and the other is adware and popups.
As b0gd4n said, there may be a tick box to uncheck.
b0gd4n said:
I did fastboot flash recovery.img, and it looked like it was fine, but when I rebooted to recovery and started adb sideload, the pc did not recognise the device.
However, doing fastboot boot recovery.img, it booted straight to the recovery image and starting sideload was fine.
Click to expand...
Click to collapse
But boot is kernel partition...How is that allowed? Can anyone else confirm that is what we are supposed to do? Can you boot into system fine afterwards?
MorgaNet said:
Can you list the correct steps (with commands) to do in order to flash it?
I'm not expert and I prefer to follow literally your steps.
Thx
Click to expand...
Click to collapse
@kanzone wrote:
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------
Koopa777 said:
But boot is kernel partition...How is that allowed? Can anyone else confirm that is what we are supposed to do? Can you boot into system fine afterwards?
Click to expand...
Click to collapse
I did exact that and I am now running 5.0.1 on my watch.
b0gd4n said:
@kanzone wrote:
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot boot recoveryll.bin
4. Select adb sideload then
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
5. Done
6. Reboot to fastboot
7. fastbook oem lock
---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------
I did exact that and I am now running 5.0.1 on my watch.
Click to expand...
Click to collapse
Perfect. Thank you!
To everyone having trouble with the process, I edited the first post.
Please be careful if you don't know your way around ADB and Fastboot. While it's technically a safe procedure, there is always room for total screwup!
Camazza said:
Here's how to sideload the update without ROOT.
EDIT: added a more precise description of every step
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
- Done!
If this was helpful to you, feel free to press the Thanks button :good:
Click to expand...
Click to collapse
the first time, I did just those steps and when I got to start adb sideload, my pc will not recognise that any device was plugged in, therefore, unable to do any abd commands.
I needed to do fastboot boot recovery.img instead, and this booted me straight to the image. Now, when I started the sideload feature, the pc recognised the watch straight away, and was able to sideload the update.
b0gd4n said:
the first time, I did just those steps and when I got to start adb sideload, my pc will not recognise that any device was plugged in, therefore, unable to do any abd commands.
I needed to do fastboot boot recovery.img instead, and this booted me straight to the image. Now, when I started the sideload feature, the pc recognised the watch straight away, and was able to sideload the update.
Click to expand...
Click to collapse
I guess it didn't flash properly the first time. Issuing the boot command makes a lot of sense nonetheless, as it boots straight to the new recovery without even flashing it. I'm happy you worked it out in the end.
Would you not need to flash the recovery first and then boot from it? Or does the update also update the recovery?
dunjamon said:
Would you not need to flash the recovery first and then boot from it? Or does the update also update the recovery?
Click to expand...
Click to collapse
The update patches it, but without updating prior you won't be able to sideload it in the first place. LG Really goofed up our watch.
tonu42 said:
The update patches it, but without updating prior you won't be able to sideload it in the first place. LG Really goofed up our watch.
Click to expand...
Click to collapse
Ah OK, Just waiting to finish work now and then gonna give it a go.
sideload problem
Thanks to all the contributors so far.
I installed the new recovery no problem. When I boot into recovery from bootloader menu and try to sideload the zip file, I get nothing other than, in Terminal, the adb command help listings, like I typed in the wrong command. Here is what I input
adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
I can type 'adb devices' and my device is listed, but for some reason I am having a problem with the sideload command. Any advice?

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.
2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.
danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

success!

11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!
What usb driver did you use? I'm stuck on fastboot <waiting for device>
ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
Did u allow usb debugging in developer options ?
greeneyez15o said:
Did u allow usb debugging in developer options ?
Click to expand...
Click to collapse
Yes and allow for OEM Unlock. It's a windows 10 driver issue. I couldn't figure it out.
Luckily I was able to run in on a Linux computer. Fastboot worked fine and was able to unlock the bootloader!
Sergeantslaughter said:
11/10/19 @ 3:05..successfully obtained root access for my 1st device!!
Bold N1
Rooted with Magisk
Flashed stock boot.img
Fastboot flash boot (boot.img)
Fastboot flash recovery (recovery.img)
I'm finally a big kid!!
Click to expand...
Click to collapse
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.
The easiest way I've found is to download magisk manager and the stock boot img for your device.open magisk manager and click install-download zip only.. then move the zip file and your stock boot img to the root of internal storage. Eg/storage/emulated/0/. Go back to magisk manager and click install/select and patch file. Navigate to where you stored your stock boot img and select it. Magisk will automatically flash and repck img file and will save it in your downloads folder as magisk_patched.img. enable and debugging in Dev options and reboot to bootloader. /Adb reboot bootloader. Once your phone is in fastboot mode type /fastboot devices to be sure your computer can recognize your phone. Should come back as a serial number followed by the word fastboot. Then type
Fastboot flash boot magisk_patched.img
You should get a success prompt. If successful then reboot using
Fastboot reboot
Once your phone loads back up check magisk manager to verify that everything is installed, should be two green checks. Then use a root checker to verify root.....and that's it!
Also, you have to make sure your bootloader is unlocked in order to do this....its very easy for the bold n1 just enable oem unlock in Dev options and the reboot to bootloader and type fastboot flashing unlock. Select yes on the prompt on your phone and then continue your process.
ycgr2002 said:
What usb driver did you use? I'm stuck on fastboot <waiting for device>
Click to expand...
Click to collapse
mtk droid tools all in one installer worked for me
davids_laughter said:
How exactly did you root it? What were the steps if you don't mind sharing. I've only rooted one phone and I followed a step by step tutorial on YouTube.
Click to expand...
Click to collapse
Did I mention that I did this on my Chromebook....no windows at all lol

Categories

Resources