[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Huawei Watch

[Rapscallion16]

still working same as 2.6 nothing is wrong only wishing for the back to stock option would be cool and give it like a click twice or 3 times warnings about "you sure you wanna do it? there's no goin back!"

I'd love to do a back to stock option but because the toolkit supports over 170 devices I can really only include commands that work with every device. Also I don't wanna scare people with too many messages. If they didn't get it with the first one, maybe they shouldn't be unlocking in the first place.

 

[chachin]

3.1 working like a charm :3

 

[Faspaiso]

Can't get the program to recognize my device. In Developer options, I enabled ADB debugging, then I connected it to the charger via usb to my PC. My PC recognize the device and install the drivers, but it says offline in the tool and refreshing or any other button says the watch is not connected.

Anyone how what to do?

Thanks in advance

EDIT: Normal ADB can't recognize it either. Any reason why? I should have downloaded the drivers needed. The watch charges shortly when connected to pc and then stops charging, but is still connected as the pc tells a sound when I plug it in and out.

 

[chachin]

@Rapscallion16 for 3.2 maybe... could you make it so it installs 3.0.1-0 twrp please that would be neat. thanks for your work

 

[Faspaiso]

@Rapscallion16 Can you help me with unbricking my device?

I used this tool and now I can't boot into anything else than TWRP or bootloader. Normal boot starts TWRP. The watch was on, I clicked unlock bootloader and it loaded to fastboot menu and unlocked. After that I clicked FLASH TWRP and worked fine. Then when I tried to flash SuperSU it told me I needed to start android up and re-enable ADB debugging (cause it's disabled now, I can't see my device in ADB DEVICES, but can still see it using your tool and unlock and relock bootloader)

So is there any way I can flash standard image by using your program?

Thanks in advance!

 

[flax]

Is this tool compatible with latest android wear 1.4.0.2593646?

 

[flax]

So I try this SuperSU.ZIP root included in this tool with latest Android Wear 1.4, but it doesn't work. Installation in TWRP works, but after restart no root available.

 

[negamann303]

So I try this SuperSU.ZIP root included in this tool with latest Android Wear 1.4, but it doesn't work. Installation in TWRP works, but after restart no root available.

I achieved root by pushing and flashing the latest SuperSU(systemless): HERE

Then I pushed and flashed busybox, commands work : HERE

you can use root essentials to uninstall superuser.apk

 

[acultr]

I achieved root by pushing and flashing the latest SuperSU(systemless): HERE

Then I pushed and flashed busybox, commands work : HERE

you can use root essentials to uninstall superuser.apk

worked fine on android preview 2.0

Sent from my Nexus 5 using XDA Labs

 

[tayeb100]

Link To Main Thread

About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!

Download
WinDroid Toolkit

Changelog
Check out this document for current and past changelogs.

Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!

Contribute
Check out the source code on GitHub here.

Disclaimers
Confirmed working by @chachin!
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Hi
When i try to choose any phone it gives me an error that submitted to log fie which tel me to report it to xda

Hope to see xda community the biggest cellphone solutions community

This is the log::

System.Net.WebException: The remote name could not be resolved: 's3.amazonaws.com'

at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)

at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at WinDroid_Toolkit.MainWindow.<DownloadRecoveries>d__16.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at WinDroid_Toolkit.MainWindow.<deviceListBox_SelectionChanged>d__20.MoveNext()



05:15:51 م[INFO]:Microsoft Windows NT 6.2.9200.0 64Bit
05:15:51 م[INFO]:WinDroid Toolkit 3.0.0.0
05:15:51 م[INFO]:mscorlib 4.0.0.0
05:15:51 م[INFO]resentationFramework 4.0.0.0
05:15:51 م[INFO]:System.Xaml 4.0.0.0
05:15:51 م[INFO]:System 4.0.0.0
05:15:51 م[INFO]:MahApps.Metro 1.2.4.0
05:15:51 م[INFO]:AndroidLib 1.5.2.0
05:15:51 م[INFO]:WindowsBase 4.0.0.0
05:15:51 م[INFO]resentationCore 4.0.0.0
05:15:51 م[INFO]:AutoUpdater.NET 1.3.2.0
05:15:51 م[INFO]:System.IO.Compression.FileSystem 4.0.0.0
05:15:51 م[UPDATE]:AutoUpdater started.
05:16:27 م[DOWNLOAD]:Recovery download queued.
05:16:27 م[DOWNLOAD]:Recovery download started.
05:16:28 م[DOWNLOAD]:Recovery download error.
05:16:50 م[DOWNLOAD]:Recovery download queued.
05:16:51 م[DOWNLOAD]:Recovery download started.
05:16:51 م[DOWNLOAD]:Recovery download error.
05:17:41 م[ROOT]:SuperSU root command started.
05:18:05 م[ABOUT]:Toolkit button clicked.
05:18:11 م[ABOUT]:Toolkit button clicked.
05:18:55 م[ABOUT]:Source button clicked.
05:19:07 م[ABOUT]:Help button clicked.
05:19:11 م[ABOUT]:Requests button clicked.
05:19:16 م[ABOUT]evices button clicked.
05:19:46 م[DEVICE]:Refresh button clicked.
05:19:52 م[DEVICE]etecting Device...
05:19:52 م[DEVICE]:No Device Found.
05:20:12 م[DEVICE]:Refresh button clicked.
05:20:16 م[DEVICE]etecting Device...
05:20:16 م[DEVICE]:No Device Found.
05:20:22 م[DEVICE]:Refresh button clicked.
05:20:26 م[DEVICE]etecting Device...
05:20:26 م[DEVICE]:No Device Found.
05:20:38 م[REBOOT]:Reboot button clicked.
05:20:42 م[DEVICE]etecting Device...
05:20:42 م[DEVICE]:No Device Found.
05:20:43 م[REBOOT]:No device found.
05:21:54 م[REBOOT]:Reboot button clicked.
05:21:59 م[DEVICE]etecting Device...
05:21:59 م[DEVICE]:No Device Found.
05:22:00 م[REBOOT]:No device found.
05:22:13 م[DEVICE]:Refresh button clicked.
05:22:17 م[DEVICE]etecting Device...
05:22:18 م[DEVICE]:No Device Found.
05:22:57 م[DOWNLOAD]:Recovery download queued.
05:22:58 م[DOWNLOAD]:Recovery download started.
05:22:58 م[DOWNLOAD]:Recovery download error.

 

[pablo71]

I achieved root by pushing and flashing the latest SuperSU(systemless): HERE

Then I pushed and flashed busybox, commands work : HERE

you can use root essentials to uninstall superuser.apk

I tried to duplicate what you did on the stock flashed images provided by Google that came with the 2.0 preview. I pushed and flashed the zip of supersu beta 2.74 and busybox from links you provided, and I kept system read-only in twrp and installed both zips ... but root isn't achieved and supersu just crashes when I open it on watch and the app Advanced Settings just crashes when I open it to check root ... any ideas?

anyone experience these issues and overcame them?

 

[negamann303]

I tried to duplicate what you did on the stock flashed images provided by Google that came with the 2.0 preview. I pushed and flashed the zip of supersu beta 2.74 and busybox from links you provided, and I kept system read-only in twrp and installed both zips ... but root isn't achieved and supersu just crashes when I open it on watch and the app Advanced Settings just crashes when I open it to check root ... any ideas?

anyone experience these issues and overcame them?

The superuser app won't load, but root should still WORK. Try advanced Settings or root essentials from the play store to test. If you aren't rooted, it will tell you. If you don't want to install either of those, you can adb shell then su to check for #

Sent from my SM-G935P using Tapatalk

 

[acultr]

I tried to duplicate what you did on the stock flashed images provided by Google that came with the 2.0 preview. I pushed and flashed the zip of supersu beta 2.74 and busybox from links you provided, and I kept system read-only in twrp and installed both zips ... but root isn't achieved and supersu just crashes when I open it on watch and the app Advanced Settings just crashes when I open it to check root ... any ideas?

anyone experience these issues and overcame them?

have you deleted the superuser.apk?

Sent from my Nexus 5 using XDA Labs

 

[pablo71]

The superuser app won't load, but root should still WORK. Try advanced Settings or root essentials from the play store to test. If you aren't rooted, it will tell you. If you don't want to install either of those, you can adb shell then su to check for #

I will try this again and try some su commands to check for root. neither 'Advanced Settings' nor 'Root Essentials' would open; these apps would start to open then just die. I'll explore further

---------- Post added at 12:51 AM ---------- Previous post was at 12:47 AM ----------

have you deleted the superuser.apk?

I've already wiped and re-flashed the Google provided stock image.... but are you suggesting that deleting the SuperSU app on the watch will allow apps requiring root to run properly without being apprehended?

I pushed latest SuperSU with Windroid, but flashed it in twrp ... I will try this again flashing it with Windroid 3.1 - that might be where I went wrong

 

[konvalink]

I have the similar problem. I used the tool for root 1.4.0.2593646 and the watches has status rooted. But the SuperSU wont start. Neither the version form tool or beta 2.74. Watches are frozen and restart must be performed when SuperSU is started or other app wants to use it.

 

[acultr]

I will try this again and try some su commands to check for root. neither 'Advanced Settings' nor 'Root Essentials' would open; these apps would start to open then just die. I'll explore further

---------- Post added at 12:51 AM ---------- Previous post was at 12:47 AM ----------



I've already wiped and re-flashed the Google provided stock image.... but are you suggesting that deleting the SuperSU app on the watch will allow apps requiring root to run properly without being apprehended?

I pushed latest SuperSU with Windroid, but flashed it in twrp ... I will try this again flashing it with Windroid 3.1 - that might be where I went wrong

ok.
download the SuperSU and busybox zip.
unzip SuperSU and delete superuser.apk
connect watch to PC push the both zip to watch
adb push ....... zip /sdcard/
adb reboot bootloader
fastboot boot TWRP2.8.7.0-Sturgeon.img
install SuperSU.ZIP
install busybox zip
reboot

Sent from my Nexus 5 using XDA Labs

 

[pablo71]

ok.
download the SuperSU and busybox zip.
unzip SuperSU and delete superuser.apk
connect watch to PC push the both zip to watch
adb push ....... zip /sdcard/
adb reboot bootloader
fastboot boot TWRP2.8.7.0-Sturgeon.img
install SuperSU.ZIP
install busybox zip
reboot

this is a great how to, thank you.
removing the apk from the zip makes a lot of sense.

[UPDATE:] that did the trick. great how to. looks like stock kernel is locked to a single core with userspace as the governor. there is a performance and ondemand option to try as alternate governors. fun stuff to play with, thanks again.

 

[pmgnet]

Adiuator just spins its logo. I reinstalled the latest kernel, superSU, and I still have busybox (I think it's part of the latest kernel install zip). Is Adiuator for Wear a separate project? Is there a site/download for it? Maybe I can try installing it on its own.

 

[tonybahr]

I'm stuck at a red triangle when trying to boot into recovery. Anyone have any idea what i'm doing wrong. I've tried this from scratch 3 times at least. I'm stumped.

 

[tonybahr]

I don't get why this works for some but not me. I must be rebooting at the wrong time or something. If anyone could post some steps for me I'd appreciate it. I'm sure it's something small and stupid. I'm not even that big of a noob I've been rooting and adb since the freaking HTC Leo I think that's why this irritates me so much. I just want to flash the one rom available. Seriously help me if you have a second. Yes I know nobody owes me a thing and the work here is done as a hobby.

Sent from my SM-N920V using XDA-Developers mobile app