[RECOVERY][lenok] TWRP 3.1.1-0 touch recovery [2017-05-19]

[CAYCE_VII]

I don't see how to flash .img files with this recovery on the watch itself. Any ideas why?

 

[miffymiffy]

Has anyone got this working with 511?

 

[hutchinsane_]

Has anyone got this working with 511?

yeah, it works without a problem.

 

[Lessaj]

yeah, it works without a problem.

Mine seems to be unable to mount anything, though it flashes without a problem.

EDIT: Interesting. Basically reflashed 5.1.1 and TWRP 2.8.6.0 was okay after that. Installed Wear-SuperSU-v2.40 no problem. Seems to be working.

 

[miffymiffy]

Mine seems to be unable to mount anything, though it flashes without a problem.

EDIT: Interesting. Basically reflashed 5.1.1 and TWRP 2.8.6.0 was okay after that. Installed Wear-SuperSU-v2.40 no problem. Seems to be working.

Same thing with me. After first attempt, lost all partitions. Reflashed everything and then all was ok.

 

[silentwitness1]

i cant seem to flash this keep getting the below error any ideas?

C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (9880 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.010s

after changing from a usb2 to usb 3 port get the below error


C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (9880 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s

edit

never mind got it working

 

[nicogri]

Hi guys,

Hi flashed TWRP with no problems at all...

When I entered recovery and did backup it worked well and then I chosed to reboot and it tell me it can install open su before reboot I said yes.

Back in android wear it tells me to tap to finish super su install but fail every time and ask next reboot...

 

[lukemo]

Sorry I got this error after flashing 2.8.6.1 and try to reflash 5.1..1 system boot and recovery:

target reported max download size of 268435456 bytes
sending 'recovey' (15030 KB)...
OKAY [ 0.581s]
writing 'recovey'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.687s

please help, it alway reboots to twrp, no way to boot normally

Thanks in advance

EDIT: sorry found the mistake in writing command

 

[silentwitness1]

hey guys i flashed this and now i have a popup for the stock wifi firmware update any idea how i can either make that popup go away or completely unroot and take the update?

 

[Unb0rn]

Hey, op, it looks like build of 3.0.0-0 for lenok failed, but first post is updated. Maybe someone else had built it? And thank you for your great work on TWRP)

Upd. Now it looks like recovery image is here, it works great with 5.1.1, but it won't work with 6.0.1(MEC) build. Recovery would reflash to stock every boot, it's unable to mount /system from within TWRP(and to install SuperSU for example) Hope it's possible to fix it!)

 

[miffymiffy]

Im getting System write issues on MM with 3.0.0. Can anyone else confirm?

Seems urbane has same issues.

http://forum.xda-developers.com/showpost.php?p=65383401&postcount=15

 

[rbox]

This is an official thread. Just want to make it clear this is an unofficial image:

http://www.mediafire.com/download/rhfr5ps2c8ssxx5/twrp-3.0.0-0-lenok+squashfs.img

 

[miffymiffy]

You sir are a gentleman. It works

 

[bartito]

Im getting System write issues on MM with 3.0.0. Can anyone else confirm?

Seems urbane has same issues.

I can confirm that issues with aquafs system images are also on prev TWRP versions

 

[flo071]

Im getting System write issues on MM with 3.0.0. Can anyone else confirm?

Seems urbane has same issues.

i have that problem too

system cannot be mounted: Failed to mount '/system' (No such device)

anyone know how to fix it?

 

[bombadier]

i have that problem too

system cannot be mounted: Failed to mount '/system' (No such device)

anyone know how to fix it?

Look at the solution, post number 32, one below the problem you quoted, could also try twrp 3.0.2.0

 

[flo071]

Look at the solution, post number 32, one below the problem you quoted, could also try twrp 3.0.2.0

TWRP 3.0.2.0 doesnt help

...but twrp+squashfs solved the problem :good:

 

[JoLe1203]

I flashed both TWRP 3.0.2 and "twrp-3.0.0-0-lenok+squashfs" but every I reboot in recovery (adb reboot recovery) I only see the standard Android recovery
It takes some minutes and the Watch reboots in system by itself without any further issues.

I used fastboot to flash twrp and directly restarted in recovery at Watch before rebooting. It then reboots in TWRP recovery but when I restart to system now I am not able to get to TWRP again.

Can anyone help?

EDIT: only working with "UNOFFICIAL-TWRP-Lenok-2.8.3.0.img"

 

[Bricking1]

Hey, op, it looks like build of 3.0.0-0 for lenok failed, but first post is updated. Maybe someone else had built it? And thank you for your great work on TWRP)

Upd. Now it looks like recovery image is here, it works great with 5.1.1, but it won't work with 6.0.1(MEC) build. Recovery would reflash to stock every boot, it's unable to mount /system from within TWRP(and to install SuperSU for example) Hope it's possible to fix it!)

Unb0rn,

Was this problem ever fixed or did anyone come up with a work-around??

 

[Darthsternie]

Unb0rn,

Was this problem ever fixed or did anyone come up with a work-around??

As for the official 3.0.2 version with MM the stock recovery gets reflashed after leaving TWRP and it still has issues with squasfs