Manual Update using ota ( 5.01)

Search This thread

superdave

Senior Member
Feb 19, 2005
259
148
It should be
fastboot flash recovery recoveryll.img

Also make sure recoveryll.img is in the same directory that your running fastboot from.



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?
 

shadow_empire1

Senior Member
Oct 23, 2007
842
49
Vienna
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?



lol :)
recovery not rcovery
 

cottageboy

Senior Member
Dec 24, 2009
121
13
Toronto
I was up and running with 4.4 and was trying to upgrade to 5.0. I was unlocked rooted and twrp installed.
I tried installing over the air and everytime I tried flashing a boot.img or the 5.0 recovery fastboot keep saying that the file was not a boot img.
so then I went back to fastboot oem locked and then unlocked and it wiped y watch...
the only thing I have now is fastboot and twrp....Help?

never mind got it worked out...the file i was linked to was not the correct size, piece of cake once I had the right files.
 
Last edited:

Moe5508

Senior Member
Jun 18, 2007
3,045
320
www.manicorp.com
I was up and running with 4.4 and was trying to upgrade to 5.0. I was unlocked rooted and twrp installed.
I tried installing over the air and everytime I tried flashing a boot.img or the 5.0 recovery fastboot keep saying that the file was not a boot img.
so then I went back to fastboot oem locked and then unlocked and it wiped y watch...
the only thing I have now is fastboot and twrp....Help?

never mind got it worked out...the file i was linked to was not the correct size, piece of cake once I had the right files.

Just flash the 4.4 boot image file using fastboot and you should be back in stock 4.4 firmware again...freaked me out yesterday as well..

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

Now trying ADB via Bluetooth...am at stage where am copying the ota file to sdcard...holding thumbs...

https://developer.android.com/training/wearables/apps/bt-debugging.html
 

gusano38

Member
Nov 21, 2013
40
42
Grenoble
Ok, it seems we have to remove the supersu.apk from /system/app in order to get a working su back:

shell into the watch during boot and run su. This should work... you have to be fast.
Once root:

mount -o rw,remount /system
rm -rf /system/app/SuperSU
rm /data/dalvik-cache/profiles/eu.chainfire.supersu

reboot (or ctrl-d and adb reboot)

su should work even after complete boot.
 
Last edited:

lbrito

Member
Jun 20, 2010
22
6
I tried this during boot and got this:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied
255|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied

I'm on the latest Wear with TWRP installed, but SU crashes when i try to launch. Am I just not doing it fast enough?

Ok, it seems we have to remove the supersu.apk from /system/app in order to get a working su back:

shell into the watch during boot and run su. This should work... you have to be fast.
Once root:

mount -o rw,remount /system
rm -rf /system/app/SuperSU
rm /data/dalvik-cache/profiles/eu.chainfire.supersu

reboot (or ctrl-d and adb reboot)

su should work even after complete boot.
 

gusano38

Member
Nov 21, 2013
40
42
Grenoble
I tried this during boot and got this:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied
255|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied

I'm on the latest Wear with TWRP installed, but SU crashes when i try to launch. Am I just not doing it fast enough?
You have to adb shell at the very beginning of the booting process, start trying as soon as you see the LG logo. A correct su command should change your shell line to something like:
[email protected]:/
 

tonu42

Senior Member
Nov 14, 2010
1,145
439
You have to adb shell at the very beginning of the booting process, start trying as soon as you see the LG logo. A correct su command should change your shell line to something like:
[email protected]:/

I tried this during boot and got this:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied
255|[email protected]:/ $ mount -o rw,remount /system
mount -o rw,remount /system
mount: Permission denied

I'm on the latest Wear with TWRP installed, but SU crashes when i try to launch. Am I just not doing it fast enough?

I don't think you have rooted your device. Gotta flash the latest SuperSU via twrp.
 

lbrito

Member
Jun 20, 2010
22
6
That appears to be the case... no root.
I can't launch a root shell, even at boot. I flashed the SuperSU (v1.94) zip via TWRP. I used the UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img for TWRP. SuperSU still crashes when I try to launch it from the watch, also.
What actually achieves root? The .img file with TWRP? or the installation of SuperSu? Doesn't root usually require an exploit? I was rooted before on 4.4W.2, and I would definitely get the [email protected] prompt at shell. But, in retrospect, I don't understand how that was achieved, as we follow the exact same instructions. It's back to wondering what was done to achieve root? And, did I not do something for this 5.0.1 version that I should have?
Thanks for any help figuring this out!

I don't think you have rooted your device. Gotta flash the latest SuperSU via twrp.
 

tonu42

Senior Member
Nov 14, 2010
1,145
439
That appears to be the case... no root.
I can't launch a root shell, even at boot. I flashed the SuperSU (v1.94) zip via TWRP. I used the UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img for TWRP. SuperSU still crashes when I try to launch it from the watch, also.
What actually achieves root? The .img file with TWRP? or the installation of SuperSu? Doesn't root usually require an exploit? I was rooted before on 4.4W.2, and I would definitely get the [email protected] prompt at shell. But, in retrospect, I don't understand how that was achieved, as we follow the exact same instructions. It's back to wondering what was done to achieve root? And, did I not do something for this 5.0.1 version that I should have?
Thanks for any help figuring this out!

At boot quickly adb shell
su
*root prompt should work*
than
mount -o rw,remount /system /system
cd /System/app/SuperSU
rm SuperSU.apk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Nice, good catch. I'll add that to the first post.

    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
    1
    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.

    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.
    1
    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.
    1
    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
    1
    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?

    adb version

    make sure the adb version is > 1.0.32