[Root] Root and TWRP for R

[2k4ever]

thanks again for your great work, tonu!

Try flashing the stock recovery.img instead.

just to be sure: you are referring to the stock image posted by intersectRaven, right?

 

[tonu42]

thanks again for your great work, tonu!


just to be sure: you are referring to the stock image posted by intersectRaven, right?

Yea that one.

 

[bRkiX]

hi!
i do all of this steps, but when i sent commadn adb reboot recovery, i dont get twrp, but dead android icon with exclamation....when i press it i get android system recovery, but no twrp...
what am i missing?

 

[tonu42]

hi!
i do all of this steps, but when i sent commadn adb reboot recovery, i dont get twrp, but dead android icon with exclamation....when i press it i get android system recovery, but no twrp...
what am i missing?

Be sure you did all the steps. It seems you did not issue the

 "fastboot flash recovery TWRPNAMEHERE.img"

command.

 

[intersectRaven]

hi!
i do all of this steps, but when i sent commadn adb reboot recovery, i dont get twrp, but dead android icon with exclamation....when i press it i get android system recovery, but no twrp...
what am i missing?

If you're using stock kernel, it might be that the recovery is being restored since you seem to be trying to boot to recovery FROM system. Either you need a non-stock kernel OR rename (NOT DELETE) the install-recovery.sh script in the /etc directory. You could boot TWRP with no fear of restore if you do it directly AFTER flashing the recovery.
e.g.
fastboot flash recovery TWRP.img
*navigate to boot to recovery option in bootloader*
TWRP boots!

 

[bRkiX]

yup that worked.....ahhh the geniuses of xda
i sucessfuly entered twrp, and instaled superuser....all in my quest to make vibrator stronger

thank you


edit:
and it also sticked this time....i issued adb reboot recovery from booted system, just to check, and it entered twrp with no issue....

 

[ricky326123]

EDIT

delete me

 

[Narsil]

Hi guys,

I'm going to look stupid, I know, but I can't go further than step 2 ...

3. Plug the watch into the computer

How am I supposed to plug the watch to the computer ?
Please don't laugh too loud :crying:

Diego

 

[tonu42]

Hi guys,

I'm going to look stupid, I know, but I can't go further than step 2 ...



How am I supposed to plug the watch to the computer ?
Please don't laugh too loud :crying:

Diego

It's quite alright. Using the charge dock they gave you that you put your watch on it. Than instead of plugging it into the charger plug it into the computer.

 

[lbrito]

Slight variation for me

It looks like I had an even different experience. For me, I could not get TWRP to flash using step 7 and 8.

I had to issue the command "fastboot boot recovery.img" (or, if you haven't renamed the file, "fastboot boot UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img") for step 11, then flash the supersu.zip when TWRP loaded by pressing the INSTALL button, and selecting the file I pushed over and swiping to flash.

Thanks for the added instructions, hope this helps anyone else that had my experience where this kept taking them to the stock recovery with the android and the hazard icon coming out of its chest.

I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything

So the correct procedure is like this

1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip

Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"

I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...

 

[tonu42]

PLEASE BE CAREFUL FLASHING LOLLIPOP UPDATE! It flashes a new bootloader, TZ, kernel, and system.

 

[Koopa777]

PLEASE BE CAREFUL FLASHING LOLLIPOP UPDATE! It flashes a new bootloader, TZ, kernel, and system.

So what exactly are the risks? Is adb sideload not safe?

 

[tonu42]

So what exactly are the risks? Is adb sideload not safe?

Flashing this with TWRP won't work because of the bad TWRP port I did. I have fixed one issue but ran into another. I am at the moment pushing a fix that I think will work to my watch as I type this so I will respond later. I can only work on this for another 57 minutes because I have a REALLY important exam tomorrow. I am really hoping my fix works because pushing a 113mb file to a watch is taking FOREVER.

 

[Koopa777]

Flashing this with TWRP won't work because of the bad TWRP port I did. I have fixed one issue but ran into another. I am at the moment pushing a fix that I think will work to my watch as I type this so I will respond later. I can only work on this for another 57 minutes because I have a REALLY important exam tomorrow.

I hear ya man, I have an exam tomorrow as well. But flashing this via stock recovery should work just fine? I'm interested in what you will fix though, I've never heard of being able to sideload on a custom recovery. On the Nexuses (Nexii?) it was always recommended to use stock recovery.

 

[tonu42]

So right now I have a paper weight...... things aren't looking good for me....

I am really mad right now.....

 

[nxt]

EDIT USED DIFFERENT USB PORT AND IT WORKED

After unlocking, rebooting, resetting up, going back to bootloader to flash twrp recovery, I get a FAILED error.

D:\Android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (9484 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 10.310s

Tried doing a fastboot boot recoveryname.img also and that fails.
Any Ideas?

 

[nxt]

Anyone know how to remove root?
I rooted to manual install 5.0.1 firmware, after that successfully updated, everything looks stock except SuperSU is still there (it won't run either). I want to remove it and go to stock.

 

[superdave]

1. Remount system rw
2. Remove the supersu app folder from system/app
3. Remove the su binary
4. Remount system r

 

[Walhalla]

Is root under 5.0.1 still working for you guys? I can not get a root shell and SuperSU app is crashing on the watch. I already tried to reflash the SuperSU.zip in the TWRP Recovery.

 

[tonu42]

Adb reboot device
Listen for your computer to detect the device
Adb shell
su Gotta do it real quick

this root is temporary you gotta do the following
mount -o rw,remount /system /system
cd /System/app/SuperSU
rm SuperSU.apk