yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] torch2424:
Thank you so much for this and your hard work! Do you happen to know if root through this method will still break our camera? :)
[E 2015 Android Development] Rapscallion16:
Probably, since the toolkit just puts together most of the unlock/root tutorials on the forum into one program.
[E 2015 Android Development] torch2424:
Alright thank you! But you're tool is still greatly appreciated, I'll probably be using it soon! Since you've made it so easy to do. Thank you again!
[E 2015 Android Development] bobbyphoenix:
Can this be used as individual steps? Like if one just wants root, so they would just do step 3?
[E 2015 Android Development] Shreps:
Hi,

I just tried your tool,

Unlock procedure was ok

But flash TWRP seems to have failed, because when trying step3, it rebooted on a Droid with red exclamation mark.

I forced power off by holding power, then reboot in bootloader and flashed manually TWRP using IMG from the official XDA thread : and it was ok

Maybe something (link ?) wrong in your tool ?

No file available in Logs directory.

Cheers,
[E 2015 Android Development] Rapscallion16:
Thanks for letting me know. I tested the TWRP flashing with my HTC and Nexus devices, but it may be different for Motorola devices.
[E 2015 Android Development] MameTozhio:
you might have to include mfastboot though I'm not sure as I don't have my Moto E unlocked.
[E 2015 Android Development] brotherswing:
Just a heads up, this doesn't work on the XT1528 variant, due to it not being eligible for unlocking.
[E 2015 Android Development] EB20XY:
using this toolkit and choosing Moto E (2015) brings an error and thats it.

This log created:

System.Net.WebException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden. ---> System.Net.Sockets.SocketException: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 127.0.0.1:62313

bei System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)

bei System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

--- Ende der internen AusnahmestapelÃ¼berwachung ---

bei Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

bei Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)

bei WinDroid_Universal_Android_Toolkit.MainWindow.<phoneListBox_SelectionChanged>d__46.MoveNext()

18:15:12[INFO]:Microsoft Windows NT 6.2.9200.0 64Bit

18:15:12[INFO]:WinDroid Universal Android Toolkit 2.4.0.0

18:15:12[INFO]:PresentationFramework 4.0.0.0

18:15:12[INFO]:MahApps.Metro 1.1.2.0

18:15:12[INFO]:System.Xaml 4.0.0.0

18:15:12[INFO]:mscorlib 4.0.0.0

18:15:12[INFO]:System 4.0.0.0

18:15:12[INFO]:AndroidLib 1.5.2.0

18:15:12[INFO]:PresentationCore 4.0.0.0

18:15:12[INFO]:System.Runtime 2.6.10.0

18:15:12[INFO]:System.Threading.Tasks 2.6.10.0

18:15:12[INFO]:Microsoft.Threading.Tasks 1.0.12.0

18:15:12[INFO]:mscorlib 2.0.5.0

18:15:12[INFO]:Microsoft.Threading.Tasks.Extensions.Desktop 1.0.168.0

18:15:12[INFO]:mscorlib 2.0.0.0

18:15:12[INFO]:WindowsBase 4.0.0.0

18:15:12[INFO]:AutoUpdater.NET 1.3.1.0

18:15:12[INFO]:Ionic.Zip 1.9.3.0

18:15:12[UPDATE]:AutoUpdater started.

18:15:16[DEVICE]:Detecting Device...

18:15:17[DEVICE]:Connected: Online.

18:15:31[DOWNLOAD]:Recovery download queued.

18:15:31[DOWNLOAD]:Recovery download started.

18:15:33[DOWNLOAD]:Recovery download error.
[E 2015 Android Development] Morak75:
I tried to use this tool on XT1524, I choose Moto E 2015 (no Moto E LTE 2nd gen) and it didn't find the phone despite that it is recognised manually with adb
[E 2015 Android Development] rnsxl666:
This toolkit worked like a champ to unlock my bootloader on my Moto E 2nd gen XT1526. Can't thank you enough,donation coming you're way.
[E 2015 Android Development] aaronrw:
[MENTION=4485224]WindyCityRockr[/MENTION] would this flash twrp to my LG g4 with unlocked boot loader? Sorry for off topic
[E 2015 Android Development] harshwardhan ghundare:
Will it work for moto e xt1506 indian version?
[E 2015 Android Development] Rapscallion16:
WinDroid Universal Android Toolkit v2.5 Now Out!

I'm happy to announce that the WinDroid Universal Android Toolkit v2.5 update is now out! As always, let me know what you think and report any bugs you encounter! :highfive:

You can download it here.
[E 2015 Android Development] Madricks:
Windroid crashes on my System with Windows 10 Pro. I am sad :-/
[E 2015 Android Development] TrueYears:
is it me or do these applications NEVER work?

I tried using this stupid tool http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150 to unlock bootload, didnt work at all, so I had to do it the manual way, then I am trying to use this to root, and it wont detect my device
[E 2015 Android Development] Rapscallion16:
WinDroid Toolkit v3.0 Is Now Out!

WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!

You can out more specific changes in the changelog here.

You can download the new update here.

All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
[E 2015 Android Development] skramz:
never mind, just flashed TWRP 3.0.0 manually :)
[E 2015 Android Development] Anonymous:
Can we install twrp recovery

with this tool
[E 2015 Android Development] 801legend:
THANK YOU!!!!!!!! after a thousand attempts and 4mo. (dont judge me) of confusion im

finally rooted
[E 2015 Android Development] bertoxo:
Same error here: no recovery for LTE model.

But iv'e putted this new updated TWRP on te 'Recoveries' folder, rename it to 'Recovery2.img', and do the job perfect. ;)

Link to recovery:

http://xdaforums.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649
[E 2015 Android Development] Creepi:
Thanks for this! Worked flawlessly (with the exception of user error.)
[Android Apps and Games] ssrij:
​

What is WearPIN?

WearPIN is an Android Wear app that adds extra protection to your Android device or tablet by changing its PIN every time you want to unlock your device. It also allows you to instantly lock your device if you've left your phone unlocked, which is very handy in case you give your phone to your friend who starts messing around with things or you accidentally forgot to lock your phone in a hurry and don't want any one else to touch or use it. (This will only work if your phone is in range of your Wear device)

How it works:

First, activate the app on your phone!

How to unlock:

Open the WearPIN app on your Android Wear device

Enter the PIN shown on the screen on your Android device

That's it!

How to lock:

Open the WearPIN app on your Android device

Tap "Lock my device"

That's it

What if my watch is disconnected or away from my phone?

WearPIN includes an emergency unlock feature. In case your watch is disconnected or away from your phone, you can unlock your device using a recovery PIN. The default recovery PIN is 123456 but you are given an option to change it when you set-up WearPIN for the first time.

Screenshots:

Download

Play Store: https://play.google.com/store/apps/details?id=com.ssrij.quicklock

Note: If you're unable to download it from the play store then you can download the APK directly from http://www.suyashsrijan.com/apps/wear_pin.apk

What's coming in next version (high to low priority):

Ability to send PIN instantly on device screen on DONE

Pebble Support

Ability to show the PIN as an ongoing notification on watch

Support for multiple devices

If you face any bugs or issues or have any ideas that can make this app better then please post below :)
[Android Apps and Games] ssrij:
Changelog:

Version 1.0.1, March 29 2015

Send PIN to your Wear device: You can now receive the PIN on your Wear device when you turn on your device! Faster than opening the app on your Wear device and then seeing the PIN. To enable, turn on "Send PIN to Wear" in Settings

Made the "Lock my device" text a little bigger to make it easier to tap

Some bugs here and there

Version 1.0, March 28 2015

Initial version
[Xoom Android Development] Rapscallion16:
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

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.
[Xoom Android Development] Rapscallion16:
Reserved

Reserved.
[Xoom Android Development] derrick1976:
why is this a recognized trojan
[Xoom Android Development] Rapscallion16:
It definitely shouldn't be recognized as a trojan. Did it say anything specific about the issue? The source code is here if you're still wary.
[Xoom Android Development] derrick1976:
ok,first it unlocked my mz604,but it didnt flash the recovery right.
[Xoom Android Development] Rapscallion16:
WinDroid Universal Android Toolkit v2.5 Now Out!

I'm happy to announce that the WinDroid Universal Android Toolkit v2.5 update is now out! As always, let me know what you think and report any bugs you encounter! :highfive:

You can download it here.
[Xoom Android Development] Rapscallion16:
WinDroid Toolkit v3.0 Is Now Out!

WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!

You can out more specific changes in the changelog here.

You can download the new update here.

All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
[Android Q&A, Help & Troubleshooting] Samable:
So I was trying to root my phone last night and watched some guides but none of them matched my Samsung Galaxy S4 4.4.2 SGH-1337m Sasktel so then I finally found an article: I cant post the link but the title was Samsung Galaxy S4 Android 4.4.2 KitKat Update: How To Root SGH-I337M Variant On Latest OS And Install Custom ROMs [TUTORIAL] Please look at it.

And so I used odin 3.09 exe and AP'd cf-autoroot and in the middle of the download it said failed rather than pass. After that I just pressed exit and pulled the plug, now my phone is saying Firm Upgrade encountered an issue...please selyatta yatta yatta.

Help is appreciated!
[Android Q&A, Help & Troubleshooting] sumitberi:
Hey dont take tension your phone is still alive it happened to me alao while rooting.It has simple solution just connect your phone to pc and open download mode in your phone then start odin and select that cf autoroot file and start rooting and after some minute your phone will be rooted and it will be working properly.

If it helps then please click thanks button:thumbup::)
[HTC ChaCha] navidali:
Hi everyone

Im new user of chacha....

I dont know how to root and which rom is more stable than the others

Help me please....
[HTC ChaCha] sayco.only:
you can use https://www.htcdev.com/ it will guide you to root your device

i prefere to stay with the stock rom it's the most stable rom for your device until you want to try another rom

but first remember to do a full backup your device before try any rom
[Blu Vivo Air] DvDwx.:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war
* or the current economic crisis caused by you following these directions.
* So don't be an *** ****
*/

DO NOT TAKE AN OTA WHILE ROOTED!!! YOU WILL HAVE A BRICK IN YOUR HANDS!!!

Hi, For while i try Root my Vivo Air and don't get much success with it... so i try a new ADB Driver* and that works :highfive:

Using vRoot you can easy root your phone BUT the problem is the Chinese SuperSU... so i get on Google a Script who Replace the Chinese SU to XDA's [MENTION=631273]Chainfire[/MENTION] SuperSU :highfive:

So follow the Steps ;D

1 - Download vRoot , ADB installer (Just to have sure about the drivers) , Google ADB Driver Modificated to Vivo Air (Driver without Signature =/ ) and WolfDroid Script

2 - Install vRoot and ADB Installer on computer ;D

3 - Turn ON the USB Debugging ... (if you put the cable but don't appear the option to turn it on, go on settings -> about Device and click over "Build Number" 5 times to get developer Mode, than you go back and enter on Developer Options and turn on USB Debugging)

4 - than put the cable and wait the computer says about missing driver... than unzip the "Blu Vivo Air.rar"(Google Generic ADB Driver modificated to BLU Vivo Air) and go on device manager and follow the photo steps on FAQ above

5 - now turn off the Antivirus Firewall to ADB Daemon Server can Work without any restrictions

6 - execute vRoot and follow the steps on screen (Any doubts search on Youtube how to follow that) and at final step on rooting the phone will restart and maybe the computer recognized a MT65xx Driver installation but that isn't need to root... than he will show Rooted status on vRoot program

7- after all that you allow file copy to get acess to internal storage from phone to put the Folder MRW from WolfDroid Script.zip on phone and follow this steps from this official video from WolfDroid (Just to remember, is need to install a Terminal emulator app from google market to do this step)

8 - after replace the chinese SU to SuperSU you go to google market and update the SuperSU to lasted update and execute SuperSU to update the binaries and reboot

9 - Finish the process ;D
[Blu Vivo Air] DvDwx.:
- FAQ:

1 - Question: Modificated Blu Vivo Air ADB Driver installation

Answer: you can try follow this steps from original Driver developer on Brazilian Forum (Just to remember.. the driver download already have all customizations about he describe on photos... LINK) or just follow this photos/steps on above

Go to Device Manager and right Click to select Update driver selected

[IMG="Go to Device Manager and right Click to select Update driver selected"]http://imageshack.com/a/img540/6440/X2ji0x.png[/IMG]

Click on Browse My Computer for driver software

[IMG="Click on Browse My Computer for driver software"]http://imageshack.com/a/img540/493/3uIUfb.png[/IMG]

Click Let me pick...

[IMG="Click Let me pick..."]http://imageshack.com/a/img537/7931/57gy3Q.png[/IMG]

Click Show ALL...

[IMG="Click Show ALL"]http://imageshack.com/a/img673/1994/pxvSTd.png[/IMG]

Have Disk...

[IMG="Have Disk..."]http://imageshack.com/a/img910/505/tn2VOQ.png[/IMG]

Search...

[IMG="Search..."]http://imageshack.com/a/img673/7232/n5rE7O.png[/IMG]

Go to located Unzip Folder and select Android_WinUSB.inf ... than click Open(or two click on .inf) and than OK

[IMG="Go to located Unzip Folder and select Android_WinUSB.inf"]http://imageshack.com/a/img537/2363/en4ifK.png[/IMG]

Select the Android Composite ADB Interface and click NEXT and Accept if he ask if you want install this driver anyway

Now you Installed your ADB Driver working :highfive:

Have any question, Commit above... i will try answer you and maybe i can put here on FAQ to everyone :highfive:
[Blu Vivo Air] freeslain:
Google ADB Driver Modificated to Vivo Air download link is broken. Can you fix it please.
[Blu Vivo Air] freeslain:
broken link

there is a broken link in your post. can you please fix it. I'm trying to flash my vivo air.

thanks
[Blu Vivo Air] spirodave:
I am having issues getting a custom recovery installed on this phone . I tried an app that allowed to choosed twrp or cwm and it installs succesfully but when i reboot recovery it still bots to stock. Being there is no option in dev options to unlock oem bootloader I belive this is causing the issue. Any ideas or links . Thanks in advanced
[Blu Vivo Air] jadesse:
Links are invalid. Can some please post new links?
[Blu Vivo Air] Raju Don:
Yes
[Blu Vivo Air] schlunk:
does anybody have the "ADB Driver Modificated to Vivo Air"?

link is dead. thanks!
[Nexus Player Android Development] Rapscallion16:
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

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.
[Nexus Player Android Development] Rapscallion16:
Reserved

Reserved.
[Nexus Player Android Development] midnightzak:
Does twrp install on the np?
[Nexus Player Android Development] Rapscallion16:
No, since TWRP has not been released for the NP yet. The toolkit only unlocks bootloader and roots.
[Nexus Player Android Development] Rapscallion16:
WinDroid Universal Android Toolkit v2.3 Now Out!

I'm happy to announce that the WinDroid Universal Android Toolkit v2.3 update is now out! It includes a bunch of new features, fixes and supported devices, so check it out and let me know what you think! :fingers-crossed:

You can download it here.
[Nexus Player Android Development] ganggreen777:
Is this tool still working?

Last post was March 29th
[Nexus Player Android Development] talk2nate:
Will you be updating this soon since there now is a TWRP available for the NP? Looks like a super simple tool to use :)
[Nexus Player Android Development] ganggreen777:
I would definitely like to know bc I am not rooted yet. ...and thus seems like it is what I need
[Nexus Player Android Development] Rapscallion16:
I will definitely be adding TWRP flashing for the NP in the next update of the toolkit. :o
[Nexus Player Android Development] slonn:
2.3 and 2.4 do not seem to be working. They keep suggesting that the Nexus Player is an htc device when attempting to unlock the bootloader
[Nexus Player Android Development] ganggreen777:
Any development here?
[Nexus Player Android Development] djerick3:
Can't even get mine to read

I get into recovery mode but then what? What steps from their because the device still doesn't get recognized.

Thanks,

Eric
[Nexus Player Android Development] Rapscallion16:
WinDroid Universal Android Toolkit v2.5 Now Out!

I'm happy to announce that the WinDroid Universal Android Toolkit v2.5 update is now out! As always, let me know what you think and report any bugs you encounter! :highfive:

You can download it here.
[Nexus Player Android Development] dyslecix:
Do you have to have your NP connected directly to the pc for this? or can I ADB through the network?
[Nexus Player Android Development] r1nstang:
just picked up a NP player today. installed the drivers and such as prompted when i started the toolkit. But just says "unauthor" at the bottom. says nothing is connected. Does the NP need to be plugged into a TV at the same time? I dont have a laptop so i have to plug it into my PC on 1 side of the room in order to use the toolkit.
[Nexus Player Android Development] djerick3:
I use the same toolkit and yes it has to be connected to a TV as you have to put the np in recovery mode. I modify them so you can get every channel available.
[Nexus Player Android Development] dincdoes.me:
I just bought two of these awesome players had all sorts of issues with this toolkit even working and the other main toolkit nothing would unlock my bootloader..

Downloaded WUGfresh NEXUS toolkit and that didnt work either so i ran manual mode from wugfresh then did the unlock code myself low and behold it worked lol
[Nexus Player Android Development] danigraham:
we have had a nexus player for almost a year now and are currently working on a friend's to unlock the BL and root to put Kodi on for them. now... my question..

has anyone successfully unlocked the bootloader AFTER taking the 6.0 OTA? we thought "hey to make it easier on ourselves and them we will just leave lean back instead of going with lollirock, take the update and put kodi on for them" we were a little over zealous because now our desktop (linux)terminal won't recognize the device and we have tried mannnny cables we know to work.

any advice or anything helps.. you know how it is to get the gears turning ? hoping that we didn't update and now there's no way to do it. I have a feeling ..
[Nexus Player Android Development] djerick3:
You can unlock it via adb/fastboot, type the following in the command shell. Fastboot oem unlock. You may have to type it twice but beware as it will erase everything on the nexus player.
[Nexus Player Android Development] danigraham:
like I said.. it wouldn't see the nexus player and we tried tons of cables.

but we got it.

by using this tool (just had to install windows)! thanks a bunch.
[Nexus Player Android Development] retire01022004:
Waiting delivery of NP. Getting ready for unlock and root. Receive error message downloading drivers within v2.5 on XP. Log follows....any advise?

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)

at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)

at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

--- End of inner exception stack trace ---

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

at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)

at WinDroid_Universal_Android_Toolkit.MainWindow.<Window_Loaded>d__19.MoveNext()

4:21:11 PM[INFO]:Microsoft Windows NT 5.1.2600 Service Pack 3 32bit

4:21:11 PM[INFO]:WinDroid Universal Android Toolkit 2.5.0.0

4:21:11 PM[INFO]:mscorlib 4.0.0.0

4:21:11 PM[INFO]:PresentationFramework 4.0.0.0

4:21:11 PM[INFO]:System.Xaml 4.0.0.0

4:21:11 PM[INFO]:System 4.0.0.0

4:21:11 PM[INFO]:MahApps.Metro 1.1.2.0

4:21:11 PM[INFO]:AndroidLib 1.5.2.0

4:21:11 PM[INFO]:WindowsBase 4.0.0.0

4:21:11 PM[INFO]:PresentationCore 4.0.0.0

4:21:11 PM[INFO]:System.Runtime 2.6.10.0

4:21:11 PM[INFO]:System.Threading.Tasks 2.6.10.0

4:21:11 PM[INFO]:Microsoft.Threading.Tasks 1.0.12.0

4:21:11 PM[INFO]:Ionic.Zip 1.9.6.0

4:21:11 PM[INFO]:Microsoft.Threading.Tasks.Extensions.Desktop 1.0.168.0

4:21:11 PM[INFO]:AutoUpdater.NET 1.3.1.0

4:21:12 PM[UPDATE]:AutoUpdater started.

4:21:22 PM[DOWNLOAD]:Download of Drivers started.

While indicates driver download started, no results after about hour.

Thanks