[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Verizon One (M8)

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Verizon One (M8) - Verizon HTC One (M8)

Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.

Reserved
Reserved.

Thank you. This looks like a very helpful GUI for those not familiar will using ADB in shell.

I'm all for one click guis, but I don't see how this can work on Verizon. We can only be unlocked with firewater and they specifically state this on their site.
" The firewater binaries you download may not be shared, rehosted, bat’d, integrated into a one-click, repackaged, hotlinked, or otherwise distributed or reused."
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
I'm all for one click guis, but I don't see how this can work on Verizon. We can only be unlocked with firewater and they specifically state this on their site.
" The firewater binaries you download may not be shared, rehosted, bat’d, integrated into a one-click, repackaged, hotlinked, or otherwise distributed or reused."
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, it definitely won't be able to be directly implemented into the toolkit, but I will probably link to a guide, or create my own, for using WeakSauce and Firewater, then direct users to come back to the toolkit to flash a recovery and root.
Sent from my HTC One X+ using XDA Premium 4 mobile app

WinDroid Universal Toolkit v1.2
WinDroid Universal Toolkit v1.2
Version 1.2 is now out! There's tons of new phones, features and fixes, so check it out and let me know what you think!

This is great. However for us Verizon users this is mainly to flash recoveries?

WinDroid Universal Android Toolkit v2.0 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.0 update is now out! It's a complete redesign, and fixes all of the downloading issues and errors that people have been facing.
Check it out here.

WinDroid Universal Android Toolkit v2.1 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.1 update is now out! It's a complete code rewrite, with new features and support for 17 new devices! As always, reply with any comments you have or issues you're facing, and Happy Holidays to all!

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.

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.

WindyCityRockr said:
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.
Click to expand...
Click to collapse
Hi, im on a verizon m8 on kitkat 4.4.2. Ive unlocked bootloader and got s-off via sunshine but this tool doesnt seem to installing twrp for me. It says the install was successful but, every time i try and boot into recovery it just gets stuck on the entering recovery screen. Any idea what to do?

sid3091 said:
Hi, im on a verizon m8 on kitkat 4.4.2. Ive unlocked bootloader and got s-off via sunshine but this tool doesnt seem to installing twrp for me. It says the install was successful but, every time i try and boot into recovery it just gets stuck on the entering recovery screen. Any idea what to do?
Click to expand...
Click to collapse
Is SU installed? The folks that brought you Sunshine have a temp SU that lets you install the full one from the store.
Edit: Looks like this Tool will flash SU for you. I've never used it so don't know.
Look at the second download here;
http://theroot.ninja/download.html
Looks like this tool will flash SU too. Look to right side.

schneid said:
Is SU installed? The folks that brought you Sunshine have a temp SU that lets you install the full one from the store.
Edit: Looks like this Tool will flash SU for you. I've never used it so don't know.
Look at the second download here;
http://theroot.ninja/download.html
Looks like this tool will flash SU too. Look to right side.
Click to expand...
Click to collapse
Thanks! Im now rooted. Any idea how to install a recovery? Ive tried a few ways( manually flash through adb, flashify, windroid) and all of them successfully install the recovery but it just keeps getting stuck at boot. I have to hard reset the phone to reboot it.

sid3091 said:
Thanks! Im now rooted. Any idea how to install a recovery? Ive tried a few ways( manually flash through adb, flashify, windroid) and all of them successfully install the recovery but it just keeps getting stuck at boot. I have to hard reset the phone to reboot it.
Click to expand...
Click to collapse
I use fastboot. Read here:
http://forum.xda-developers.com/showthread.php?t=2277112
I really like the Captain's recovery. Last one on the list here:
https://basketbuild.com/devs/Captain_Throwback/One%20%28M8%29/ALL/Recovery

Just an FYI, the Captain's latest recovery is 2.8.6.2 which is outdated. TWRP is up to 2.8.7.2, but for the M8, only 2.8.7.0. 2.8.6.2 might be good enough, but IIRC @Captain_Throwback himself has said that his 2.8.6.2 is outdated by the official release.

sid3091 said:
Thanks! Im now rooted. Any idea how to install a recovery? Ive tried a few ways( manually flash through adb, flashify, windroid) and all of them successfully install the recovery but it just keeps getting stuck at boot. I have to hard reset the phone to reboot it.
Click to expand...
Click to collapse
You can use Flashify from the play store if you don't wanna ADB. You can download the recovery img from within the app as well.
Sent from my iPad using Tapatalk

J_awn said:
You can use Flashify from the play store if you don't wanna ADB. You can download the recovery img from within the app as well.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I did. Same issue. Im on 4.4.2, if that helps.

dragontology said:
Just an FYI, the Captain's latest recovery is 2.8.6.2 which is outdated. TWRP is up to 2.8.7.2, but for the M8, only 2.8.7.0. 2.8.6.2 might be good enough, but IIRC @Captain_Throwback himself has said that his 2.8.6.2 is outdated by the official release.
Click to expand...
Click to collapse
I know that but so is the phone. I like his GUI and works fine.
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
sid3091 said:
I did. Same issue. Im on 4.4.2, if that helps.
Click to expand...
Click to collapse
I've never got Flashify to work either.

schneid said:
I know that but so is the phone. I like his GUI and works fine.
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
I've never got Flashify to work either.
Click to expand...
Click to collapse
Still no luck. Im at a complete loss here. Is there any other recovery besides twrp that may work on this device?

Related

[HOW-TO] Root Jelly Bean

For all those people who did not use OTA RootKeeper to keep root before upgrading to JB, there is a way to root the device.
You need to be unlocked for this to work.
1) Boot into fastboot method. Flash custom CWM JB recovery from http://forum.xda-developers.com/showpost.php?p=32251319&postcount=1
2) Flash CWM-SuperSU.zip from http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
This should give you root back. You can test using Root Checker.
Fresh Install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After Rooting:

Nice work man with the cwm jb. Got a system dump last night so working on a deodexed rom now
Sent from my SCH-I535 using xda premium

Seems without unlocking someone can downgrade from JB, root and then upgrade back to JB again. All data is lost, but the device warranty remains in tact .
[TIP] Downgrade from JB to 0.30 works!

PY
hiemanshu said:
For all those people who did not use OTA RootKeeper to keep root before upgrading to JB, there is a way to root the device.
You need to be unlocked for this to work.
1) Boot into fastboot method. Flash custom CWM JB recovery from http://forum.xda-developers.com/showpost.php?p=32251319&postcount=1
2) Flash CWM-SuperSU.zip from http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
This should give you root back. You can test using Root Checker.
Fresh Install:
After Rooting:
Click to expand...
Click to collapse
This worked!!! In less than 10 minutes I was rooted again and now have my fave CWM back on my tablet! You are the MAN!!

hiemanshu said:
For all those people who did not use OTA RootKeeper to keep root before upgrading to JB, there is a way to root the device.
You need to be unlocked for this to work.
1) Boot into fastboot method. Flash custom CWM JB recovery from http://forum.xda-developers.com/showpost.php?p=32251319&postcount=1
2) Flash CWM-SuperSU.zip from http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
This should give you root back. You can test using Root Checker.
Fresh Install:
After Rooting:
Click to expand...
Click to collapse
I'm getting a <waiting for device> response with fastboot. Yet the drivers are installed, the TF700 is in fastboot mode (and plugged in) tried several USB ports a Windows XP VM with the same drivers, nothing. Can't get past this. If I try to boot into recovery I also noticed I get a red triangle and a dead Android. Help? :/ The device still boots normally thankfully. But no root.
EDIT: Nevermind. Reinstalled Android SDK works fine!

Just saw that TWRP does not work with JB on the TF700. Oh well, I will do as planned and redo the cwm recovery tomorrow. Thanks for getting this fix out and making it available.
Sent from my SCH-I535 using Tapatalk 2

GRIM1337 said:
I'm getting a <waiting for device> response with fastboot. Yet the drivers are installed, the TF700 is in fastboot mode (and plugged in) tried several USB ports a Windows XP VM with the same drivers, nothing. Can't get past this. If I try to boot into recovery I also noticed I get a red triangle and a dead Android. Help? :/ The device still boots normally thankfully. But no root.
EDIT: Nevermind. Reinstalled Android SDK works fine!
Click to expand...
Click to collapse
Just for people out there, connecting the tablet directly, not through the docked keyboard, fixes problems too, in general. I was having that problem too, with fastboot.

hiemanshu said:
For all those people who did not use OTA RootKeeper to keep root before upgrading to JB, there is a way to root the device.
You need to be unlocked for this to work.
1) Boot into fastboot method. Flash custom CWM JB recovery from http://forum.xda-developers.com/showpost.php?p=32251319&postcount=1
2) Flash CWM-SuperSU.zip from http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
This should give you root back. You can test using Root Checker.
Fresh Install:
After Rooting:
Click to expand...
Click to collapse
Absolutely flawless!! Thank you! This was by far the easiest way to root, for me at least, since Debugfs' root program decided not to work for JB. Anyways, thank you very much.

Thx hiemanshu. It worked for me

Good on you man. Worked like a charm, thanks. Just a tip for very literal people such as myself, superuser gets flashed via CWM.
---------- Post added at 10:02 PM ---------- Previous post was at 09:54 PM ----------
Is CWM making usable backups on jellybean? I understand WTRP is not working yet.

Darnell_Chat_TN said:
Seems without unlocking someone can downgrade from JB, root and then upgrade back to JB again. All data is lost, but the device warranty remains in tact .
[TIP] Downgrade from JB to 0.30 works!
Click to expand...
Click to collapse
Another way to do this without unlocking your device is to use the "Factory Restore after a softbrick" option in this thread: [How-To] All-In-One Guide For Asus Infinity (TF700) [01/10/2012]
I did this using the Stock Recovery.

Mykew said:
Good on you man. Worked like a charm, thanks. Just a tip for very literal people such as myself, superuser gets flashed via CWM.
---------- Post added at 10:02 PM ---------- Previous post was at 09:54 PM ----------
Is CWM making usable backups on jellybean? I understand WTRP is not working yet.
Click to expand...
Click to collapse
Yes the latest one is.

Mykew said:
Good on you man. Worked like a charm, thanks. Just a tip for very literal people such as myself, superuser gets flashed via CWM.
---------- Post added at 10:02 PM ---------- Previous post was at 09:54 PM ----------
Is CWM making usable backups on jellybean? I understand WTRP is not working yet.
Click to expand...
Click to collapse
TWRP def does not work. I going back to the revised cwm and crossing my fingers that I can get a backup. The one posted yesterday did not support backups (and I am stupid for not seeing that in the OP)
Sent from my SCH-I535 using Tapatalk 2

Turiya_31 said:
Another way to do this without unlocking your device is to use the "Factory Restore after a softbrick" option in this thread: [How-To] All-In-One Guide For Asus Infinity (TF700) [01/10/2012]
I did this using the Stock Recovery.
Click to expand...
Click to collapse
Great call. That looks like the easiest method of all.

Do these methods work if the device was never rooted before the JB install ? Or do these methods get root back for a device that was already rooted ?
Trying to decide if I should root my TF700 or not before installing JB.

Linuxguy1 said:
Do these methods work if the device was never rooted before the JB install ? Or do these methods get root back for a device that was already rooted ?
Trying to decide if I should root my TF700 or not before installing JB.
Click to expand...
Click to collapse
It doesn't matter if your device rooted or never rooted. If you still on .26 or .30 just follow the directions to root your device.

Just updated to the JB OTA and this worked like a champ to recover root (I prepared for the OTA with Voodoo but restoring root didn't work using that method). Many thanks to the OP.

Thank you for this, it worked well on my TF700.

Turiya_31 said:
Another way to do this without unlocking your device is to use the "Factory Restore after a softbrick" option in this thread: [How-To] All-In-One Guide For Asus Infinity (TF700) [01/10/2012]
I did this using the Stock Recovery.
Click to expand...
Click to collapse
Will this way erase my data in the internal storage?

Piruelo said:
Will this way erase my data in the internal storage?
Click to expand...
Click to collapse
Yup. Save it elsewhere first.

[Q] E:Error executing updater binary in zip...

hello, hope you guys can help me out:
everytime i try to flash trickdroid, viperones or zenROMplus i get the same similar error in TWRP which looks like this:
Updating parition details...
Formatting Cache using mke2fs...
Done.
Formatting Data using mke2fs...
Wiping Internall SDcard
Updating parition details...
Installing '/sdcard/TrickDroid_9.0.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
=======================
|Welcome to TrickDroid!|
|by torxx |
=======================
Formatting paritions...
E:Error executing updater binary in zip '/sdcard/Trick
Error flashing zip '/sdcard/TrickDroid_9.0.0.zip'
Updating partition details...
i have no problems flashing CM10 or CM10.1 nightly.
whats wrong with that?
Ville (s4) (o2 branding)
unlocked
s-off
hboot 2.13.0000
radio 1.11.50.05.28
TWRP v2.5.0.0

Flashing the Sense ROMs like TrickDroid or zenROM+ doesn't work in TWRP versions above 2.3.3.0.
Don't ask me why, but it doesn't work. You can temporarily flash it in an older recovery
fastboot boot recoveryname.img

Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?

turnschuh said:
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
Click to expand...
Click to collapse
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2

Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?

HOSer_hut said:
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
Click to expand...
Click to collapse
It's quicker to wipe on the newer one, but other than that it's the same. (Save for a few UI elements)
Sent from my One S using Tapatalk 2

The major change is the addition of otg in versions above 2.4
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!

turnschuh said:
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
Click to expand...
Click to collapse
On the TWRP website, search for Ville and you'll find all the previous versions (not the goo.im app link)

oh lol yea found it thanks, think im blind sometimes..

Yes!! Back in action
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.

The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.

aaron79att said:
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
http://teamw.in/project/twrp2
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.

tivofool said:
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
Click to expand...
Click to collapse
Thanks for the reply, tivo. My mistake on the .zip. I meant .img. I made sure to download the correct version, but still have the same issue. I just get stuck on the white HTC development screen. So, I can get into bootloader and TWRP (2.6.0.0 only), but can't flash ROMs. I'm just stuck with no OS and can't seem to find a work-around. My bootloader says Tampered and Unlocked/S-On. I did, however, use an unlock guide for the One X by accident, instead of the X+. That is the only thing I can think that would cause my troubles...

charliearthur said:
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
Click to expand...
Click to collapse
sorry how to revert back? I have TWRP 2.5.0.0
Edit:Nevermind I found out, but that wasn't the case for me I'm trying to flash liquid jb v2.37 and after I downgraded twrp ,I've still got an error (error 7)...

How do i get 2.3.3 when the goo.im page only goes back to 2.5 for my device? Also is this solution still relevant for flashing an AOKP 4.4 kit kat nightly rom on the Sprint HTC One (m7wls/m7spr)

usaff22 said:
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated

Learnerspermit said:
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Click to expand...
Click to collapse
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.

usaff22 said:
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
Click to expand...
Click to collapse
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.

Learnerspermit said:
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Click to expand...
Click to collapse
On the TWRP site, look for the "Get TWRP for your device" button in the upper right hand corner. Then that should bring up the search function:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[SOLVED] Can't update further (3.4 kernel)

Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.

Chris95X8 said:
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Click to expand...
Click to collapse
Why not flash the boot.img from the New Build.zip as you are S-ON?

khan.orak said:
Why not flash the boot.img from the New Build.zip as you are S-ON?
Click to expand...
Click to collapse
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.

Chris95X8 said:
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Click to expand...
Click to collapse
Aahhh yess
Can you just run an RUU from your carrier? That's a one-stop solution: will upgrade your firmware and HBOOT and you should be good to go.
Sent from my HTC One S using Tapatalk 4 Beta

Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Okay. Sure.
First, You will have to tell me your CID. You can find that out by getting CID GETTER from play store. It should tell you your CID in RED color.
Also, you run the RUU, it will upgrade you plus get you on stock, afterwards, IF it is locked again, you can unlock it and flash CM latest nightlies again. So no biggie there.

Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I suppose that is Three (3) UK .
Okay, I found that there is no JellyBean RUU for your carrier. Same as they did with HTC One X.
But here's the deal, after relocking your bootloader, you can use This RUU which is an ICS RUU.
It will bring you to Stock ICS without changing your HBOOT and firmware. Afterwards, you should check for System Updates and receive JellyBean OTA. So that will take you to JellyBean + 2.15.0000 HBOOT + Newer Firmware.

OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4

Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Yeah, that's right.
Yes, udpdate through WiFi as it is a big update to JB OTA. works everywhere.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.

khan.orak said:
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?

Chris95X8 said:
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Click to expand...
Click to collapse
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff (unlocking, rooting etc), make nandroid backups of the new JB ROM. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.

khan.orak said:
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff, make nandroid backups. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
Click to expand...
Click to collapse
That's how I did it :laugh:

Chris95X8 said:
That's how I did it :laugh:
Click to expand...
Click to collapse
Great. shouldn't be a problem then.

khan.orak said:
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.

Chris95X8 said:
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Click to expand...
Click to collapse
what recovery do you have right now?

khan.orak said:
what recovery do you have right now?
Click to expand...
Click to collapse
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?

Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Click to expand...
Click to collapse
If you want to root your device, just flash a flashable SuperSU.zip from recovery. Instant root.
---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Click to expand...
Click to collapse
actually, I have been having issues with 2.6.0.0 flashing Carbon ROM. PACman worked fine. Can't say anything. Both worked okay with 2.3.3.0. You may give the latest a try.

Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Chris95X8 said:
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
Click to expand...
Click to collapse
Oh. Just yesterday, some folks reported unsuccessful and corrupt RUU downloads from androidruu site.
You may use this one Here

[TOOL] Lock/Unlock Bootloader + Remove Tampered | Aroma GUI

This tool will allow you remove the Tampered flag from your bootloader. It will also allow you to easily Lock and Unlock your Bootloader directly from recovery.
No root required since it is run in recovery, however you still must be S-OFF.
Before using this tool you need to be sure you are using the latest version of recovery as the M7 U/UL TWRP requires at least version 2.6.3.3 for this package to work. The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE.
The latest M7 U/UL CWM can be downloaded HERE.
***[UPDATE] - It seems that the latest TWRP 2.6.3.3 has been pulled due to some minor issues. If your TWRP version doesn't work please use CWM for now until a updated TWRP release is made.
This will work for Verizon and Sprint as well, however they have different versions of these recoveries, so please make sure you are using the correct recovery for your device.
Saying this again in case you missed it: YOU MUST BE S-OFF!
To use the tool simply copy the zip file to your phone and then boot to your custom recovery and choose install. Then browse to where you copied the file and select it. The aroma installer will begin. Follow the steps outlined in the pictures below and choose the options you want to run.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can just keep this file on your phone and Lock and Unlock at anytime without a PC and without losing data.
***Credits***
S-trace for originally discovering the location of the lock status flag. See this thread.
scotty1223 for his ADB shell commands. Threads HERE and HERE. Scotty was also very helpful to me in understanding some of the default values.
Just to be clear I did not just copy and paste scotty1223's commands into a aroma installer. The echo command can be problematic in aroma, so I developed original code for all four commands. The end result is the same in that the data in the partitions is changed as needed.
***Download***
Guru Bootloader Reset Tool
md5: fdb8264a8f4741bae22939cd7734f7c2
Enjoy!
If this helped you out please consider a small donation or just a thanks would be great.

Demo and Troubleshooting
Demo Video:
***Troubleshooting***
If the installer stays on this screen fore more than a few seconds, then it means you need to delete/format cache. This can be done within both recoveries. You may need to reboot recovery after clearing cache and begin the installer again. This seems to happen more on CWM than TWRP.
If the installer runs but your bootloader doesn't change, it is proably one of these things:
You are not S-Off
You do not have the latest version of recovery (I recommend TWRP)

+ 1

+1

Worked on int. m7 with hboot version 1.55.
Now have removed my tampered flag :victory:
thx
pOpY

Oh yeah..thanks..a handy tool..
Sent from my HTC One using XDA Premium 4 mobile app

Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?

Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk

nkk71 said:
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Click to expand...
Click to collapse
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.

Evil-Dragon said:
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It will work on any firmware. Hboot is not touched. This only modifies partitions mmcblk0p3 and mmcblk0p7.

crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Noted. Thanks
Sent from my HTC One using Tapatalk

Awesome!
I was looking for this... it worked great! Thanks man!

crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI

Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?

DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
. Warranty purposes. Or for example in my case if I decided to upgrade my phone with jump, I can make everything look like never even happened. It's quite useful.
Sent from my HTC One using XDA Premium 4 mobile app

nkk71 said:
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Click to expand...
Click to collapse
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks

DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
Also sometimes a locked bootloader is needed for promotions like the 25 GB of Google Drive space.
There can be a variety of reasons one might need to toggle it.

Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app

crushalot said:
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
Click to expand...
Click to collapse
I'm still on CWM 6.....2 (the old one, but with updated ts drivers) gonna test ur tool on friday.
Will let u know.
Btw, thanks for all your guru site, I refer to it a lot; PayPal doesn't work in my country so can't contribute. But thanks !!
Love ur work.
Sent from my HTC One using Tapatalk

joho5 said:
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, my tool doesn't wipe data during a lock or unlock.
It directly modifies the partitions that conatin the bootloader status, without touching /data or /system

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | One (M9)

Reserved
Reserved.

This works with the new bootloader setup for the M9?

Captain_Throwback said:
This works with the new bootloader setup for the M9?
Click to expand...
Click to collapse
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.

The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.

How
niekie73 said:
The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.
Click to expand...
Click to collapse
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...

kaw900r said:
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...
Click to expand...
Click to collapse
I used this one
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?

DroidShift79 said:
Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?
Click to expand...
Click to collapse
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.

WindyCityRockr said:
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.
Click to expand...
Click to collapse
doesn't work. won't flash twrp. and my phone is unlocked.

stargaterules said:
doesn't work. won't flash twrp. and my phone is unlocked.
Click to expand...
Click to collapse
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.

NaitsirkC said:
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.
Click to expand...
Click to collapse
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.

stargaterules said:
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.
Click to expand...
Click to collapse
Actually I misspoke. In bootloader mode it says that, but in download mode, the one with the black background instead of the white background, it works like a charm! That's a relief.

What works like a charm? It's not letting me install recovery because s is on. How did you get past that?

stargaterules said:
What works like a charm? It's not letting me install recovery because s is on. How did you get past that?
Click to expand...
Click to collapse
It's supposed to be in download mode, it works just fine then. Manually choose download mode not bootloader and it works

WindyCityRockr said:
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.
Click to expand...
Click to collapse
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.

Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
awesome. it works. maybe add the info about device needing to be in download mode so people don't get confused. the program reboots the device into bootloader.

Will the program be updated?

Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!

emptyPD said:
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!
Click to expand...
Click to collapse
2b Make a stock backup
For 3 you need to make sure you install the latest Beta SuperSU, which I don't think is linked in this app.

Database Info

welcome