Develop Bugs

[Guide] Subsidy Unlock, SuperCID, and Radio S-OFF

Update 12-29-10: Due to problems reported with v03, we now link to v02.
Update 12-23-10: A new version of gfree, v02, has just been released by Guhl. Links have been updated to the new version, which allows you to set Sim Unlock, CID, and Radio S-ON/OFF independently. If you have previously run gfree, you will receive no additional benefit from running gfree v2, unless you want to change one of the settings.
Notice: gfree is known not to work for radio firmwares with higher versions then 26.03.02.xx -- the reason for this is that HTC patched the hole that allowed scotty2 to power cycle the emmc chip to drop its write protection. So if you installed a radio version with a higher version number, downgrade the radio firmware before using gfree.
Guhl also released gfree_verify, which allows you to verify your phone's settings (regardless of which gfree you used). See the wiki for more on that.
The wiki is usually up to date on the latest of everything, so be sure to check it frequently.
---------------
scotty2 delivers again!
His "gfree" program should do the following for your g2, dz, or dhd:
* Radio S-OFF -- the real deal. This means the g2 will permit permanent root.
* Subsidy Unlock -- AKA "Sim Unlock" AKA "Network Unlock" AKA "Use a foreign SIM Card"
* SuperCID - enables the flashing of any carrier's firmware for the phone.
If you don't know what this means or why you might want it, check the wiki.
INSTRUCTIONS:
NOTE: If you have NOT permarooted your phone previously with the HBOOT/wpthis method, doing so using the new "gfree" method should have the added effect of sim-unlocking the phone, setting superCID and turning Radio S-OFF. In fact, it's the new method for permarooting for G2/DZ and DHD. So if you haven't yet permarooted, look at those instructions.
Again, the instructions below are for people only who have already previously "permarooted" through the earlier hacked-HBOOT method. See the wiki if you are starting from scratch with a new G2/DZ/DHD and have not yet done anything "root-ish".
WARNING: Be aware that by following these instructions you are messing with your phone with potential for screwing things up. Do so at your own risk. The many authors of this guide assume no responsibility for any damage to your phone, health, general well-being, or anything else untoward with respect to these instructions or you following them.
gfree uses a dynamic in-memory patch of the kernel to remove the kernel's write protection of the radio partition.
So, for those of you who have permarooted the old HBOOT way and put on new kernels --The following kernel versions that are known NOT to work yet with gfree. If you have one of the following kernel versions on your phone install a different (stock, OTA or cyanogen) kernel before starting this procedure:
| pershoots 11/30 build
| pershoot's 2.6.32.26 – OC-UV-NEON_FP (1.516GHZ) – G2 - 12/3
| Cyanogen Kernel / release 6.1.1
| 2.6.32.26-cm-virtuous-v1.0 [email protected]#1
Other newer kernels may also not work with gfree. So if you experience problems with this procedure (either the phone reboots during the process or the procedure completes correctly but the verify still shows that the phone is locked) then you may think about downgrading the kernel to an original stock kernel or even better to this kernel.
Okay. So we're assuming you've permarooted already and usb debugging is on (Applications > Development, then enable USB debugging). You'll also need about 5MB free on your sdcard.
You might want to back up your phone with nandroid on the Clockwork recovery image first, just in case.
Note: If you hanker to do it the longer, manual, harder, and more dangerous way, or are just curious what gfree does, see the wiki history for the old instructions.
No? Then let's begin.
==== 1. Download gfree and verify sdcard is not mounted by your computer ====
You will need to download a program called gfree (v02) that will first copy partition 7 of the phone, then patch it, then reflash back to your phone. (verified to work with the g2 and desire z as well as the desire hd). (You will also need adb, which you can download as part of the Android SDK.)
Unzip gfree_02.zip to your computer.
Make sure your computer is not mounting your phone's sdcard.
==== 2. Run gfree on the phone ====
On your computer's terminal/command line, navigate to where the gfree file is, and then...
Code:
adb push gfree /data/local
adb shell
This copies gfree to your phone, then puts you in your phone's terminal. Then do this:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Wait a few moments for the sync to "take". Then reboot your phone. That's it!
gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer.
Now you can try using a new SIM card to verifiy that it worked. Also, if you had to flash a different kernel before running gfree, you may now reflash the kernel you originally had.
Thanks to the gang at #g2root, including IntuitiveNipple, scotty2, tmzt, rhcp, ciwrl, and guhl... among many others.
Wiki: How to enable Radio S-OFF, SuperCID, and SIM-unlock (with some informational background)
File: gfree_02.zip
File: gfree_verify_v01.zip
Feel free to use the "Thanks" button below. Also, Scotty2's paypal email is walker.scott AT gmail.com if you want to make a contribution.
Finally, Americans might consider making a donation to the Electronic Frontier Foundation who fight to defend your legal right to root or unlock your own phone when the carriers and phone manufacturers may lobby or otherwise try to stop you. The EFF can always use your tax-deductible support.

Hey thanks for posting this!
So I guess this is like perm-perm-root.
Giving it a shot now.
Sent from my HTC Vision using XDA App

thenefield said:
Hey thanks for posting this!
So I guess this is like perm-perm-root.
Giving it a shot now.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah it's sim-unlock too. Which is nice.

Nice thanks going to try it to.
Sent from my HTC Vision using Tapatalk

shouldnt one image work for every phone

Word up scotty2. You the man.
EDIT: And you too fattire for writing up what no one else wants to

thatruth132 said:
shouldnt one image work for every phone
Click to expand...
Click to collapse
No. If it did, then this would be a lot easier, huh?

I cant wait until some juicy stuff comes out of this.

Now, what does this mean
"make everything better."

This is freaking awesome.

andrewklau said:
Now, what does this mean
"make everything better."
Click to expand...
Click to collapse
You know.... everything.

...
I just bricked my phone LMAO!!!
I did the perm root that was easy... this jeez... followed the [Guide] How to recover your semi-brick (OMFG Thank you guys over there!) BUT I'm back... I literally almost **** my pants. Well... Gonna try this again maybe after finals LOL

Question though (going to try it later tonight LOL =P) the guide says I need a "custom cyanogenmod based kernel and provides the boot image that contains it.. I am using the nightlies do they contain that same function or no? also when I did flash that boot image and ran "insmod /sdcard/wpthis-cyanogen.ko" it said error function not implemented? Anyone not run into this issue? or have any ideas?

nycjv321 said:
Question though (going to try it later tonight LOL =P) the guide says I need a "custom cyanogenmod based kernel and provides the boot image that contains it.. I am using the nightlies do they contain that same function or no?
Click to expand...
Click to collapse
Nope.
nycjv321 said:
also when I did flash that boot image and ran "insmod /sdcard/wpthis-cyanogen.ko" it said error function not implemented? Anyone not run into this issue? or have any ideas?
Click to expand...
Click to collapse
"Error function not implemented" means it worked.

well this time it didn't brick... I think I got it time to verify it

Ok I ran it all again and worked but when I was verifying it I got all the supposed feedback except at "echo -e 'AT$QCPWRDN\r' > /dev/smd0" I got AT$QCPWRDN and then +CME Error: 0.... (No OK as said in the guide? ) and then it rebooted? what didn't work?

Got it to work!
SuperCID, Radio S-OFF, Subsidy Unlock is a reality!
Thanks to scotty2.
Thanks also to guhl (guhl99).
Read my post for more details: http://forum.xda-developers.com/showpost.php?p=9495073&postcount=363
Thread: http://forum.xda-developers.com/showthread.php?p=9495073#post9495073

This may be a stupid question but doesn't 0 also equate to no error? (In my older post) (Its just not stated in the guide, I don't want to overlook something which is why I asked ) You guys are AWESOME!!!

nycjv321 said:
This may be a stupid question but doesn't 0 also equate to no error? (In my older post) (Its just not stated in the guide, I don't want to overlook something which is why I asked ) You guys are AWESOME!!!
Click to expand...
Click to collapse
After entering the following into ADB Shell command prompt:
# echo -e 'AT$QCPWRDN\r' > /dev/smd0
The reply I got was a bunch of numbers (which filled the screen and wrapped to a new line) from what I can recall and then the phone rebooted. I didn't save the command window so I don't have the full details.
When the phone re-booted, I get signal from the local Thailand carrier AIS using a pre-paid SIM card.
The first time I went through the process I made a mistake setting the following using the Hex Editor:
"...set the 4 bytes at 0x807fc to 49 53 F4 7D"
The second time around I figured out what the "c" in "0x807fc" meant in terms of location on the Hex Editor. That was it.

:O i cant believe how awesome scotty2 is...

[Guide-How To Unroot and S-On after Revolutionary] Got ICS/Root Issues? This Helps!

Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!

^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.

ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.

RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.

This helps a lot thanks

Reg, could update the links for the Froyo and GB RUU's? Thanks!

I'll post new links sometime today, guys.

RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!

the RUU files can be found here:
http://goo-inside.me/vivow/ruu

Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable

nevermind!... lol

my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions

ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........

hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.

The links are bad. I need the two PG32IMG files... My phone is not fairing well =/

S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?

smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.

I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.

New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.

Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks

[Tutorial][Marvelc]How To Solve Common Marvelc Issues

Marvelc Problem Solving​We all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.

Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.

Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.

vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)

kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!

vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!

Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks

CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA

Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help

Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"

Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?

CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.

kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.

CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)

Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?

CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.

kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on

CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!

A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2

insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.

[Q] HTC Desire HD

I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail, & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
SMS/MMS messages,
Call Log,
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
MyBackup Root, SMS Backup & Restore, and Call Backup & Restore are all free applications that can assist with backing up your data.
Downgrade to an exploitable Firmware
AT&T Inspire 4G: Firmware Downgrade: Froyo, Gingerbread
HTC Desire HD: Firmware Downgrade: Froyo, Gingerbread
Rooting the HTC Ace
WARNING: ROOTING THE HTC ACE WILL VOID THE WARRANTY.
Before you begin, if VISIONary is installed on the HTC Ace, uninstall it before continuing.
You will need ADB on the computer to root the HTC Ace and to flash the necessary files for radio S-OFF. Follow the Android SDK guide, to get the ADB shell on the computer.
Download busybox, the ClockworkMod Recovery, the Engineering HBoot, gfree 0.7, psneuter, root_psn, Superuser package:
busybox: Download
md5: 25c5db694c987995909cc3166d4f01b0
ClockworkMod Recovery: Download
md5: 072a643b0aba983a4b9994db0e113c5e
Engineering HBoot: Download
md5: b2c8834905bfa2349f5223077493140a
gfree 0.9: Download
md5: 2dd45594b1ecb084401d428432f87010
psneuter: Download
md5: 89c2dec8d72d87b4c669f44dd31c8d17
root_psn: Download
md5: c8fe38ef55eb8951def9ff17b2eb99c1
Superuser package: Download
md5: 43d9a40b63e916635d5ad7ca32433fab
Unzip the zip files and copy the contents to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Ace to the computer via USB.
Make sure USB debugging is enabled on the HTC Ace by checking Settings » Applications » Development » USB debugging.
On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-5.0.2.3-ace.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./gfree -f -b hboot-eng.img -y recovery.img
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
The messages that you what to see are either/or
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
If you get a different error message you should run for help at then DO NOT REBOOT and join #G2Root on Freenode for further help.
If gfree worked correctly continue with:
./root_psn
sync
reboot
The HTC Ace is now rooted with S-OFF, the Engineering HBoot & the ClockworkMod Recovery. Continue to the next section.
Flashing CyanogenMod
If the {{{device}}} has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the {{{device}}} be returned to stock & start over with the full instructions provided above.
Method via Recovery
Download the [[Devices Overview#{{{device}}}|latest version]] of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Optional: Select backup and restore to create a backup of current installation on the {{{device}}}.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The {{{device}}} should now boot into CyanogenMod.
Method via ROM Manager
Launch RomManager.
Optional: Choose the first option in the app, Flash ClockworkMod Recovery to update to the latest version.
Select the Download ROM option from the main menu in the ROM Manager.
Select the CyanogenMod option, and then choose the latest version of CyanogenMod from the menu.
Optional: When you select the latest version of CyanogenMod, check the Google Apps option.
Once the ROM is finished downloading, it asks if you would like to Backup Existing ROM and Wipe Data and Cache.
If Superuser prompts for root permissions check to Remember and then Allow.
The {{{device}}} will now reboot into the recovery, wipe data and cache, and then install CyanogenMod. When it's finished installing it will reboot into CyanogenMod.
:crying:
I have try that was another fail lol...

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
GUIDE] Downgrade from 3.13 (Sense 3.0) roms
This guide is for phones shipped with froyo and updated to the 3.x firmware! For phones shipped with gingerbread (even the lower versions) please read attn1's posts in this thread!
With the Sense 3.0 upgrade HTC patched against fre3vo, so we can no longer temproot to use misc_version on that firmware. Lucky us, a new exploit was issued @rootzwiki. This exploit was tested at #g2root (freenode) and was able to temproot a 3.13.161.3 firmware version.
The usual disclaimer applies: Everything you do is your responsibility, no one can be held accountable for the state you put yourself and/or your phone into.
If you meet troubles search for help at IRC: freenode, #g2root
make sure your phone is in 'charge only' mode and the 'fast boot' feature is turned off.
What you need:
tacoroot
misc_version NOTE: you need THAT version of misc_version. Earlier versions would not work.
flashgc for a goldcard
1.32 PD98IMG.zip
put all files in your platform-tools directory (unzip misc_version and tacoroot.sh)
Code:
adb push tacoroot.sh /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
adb push flashgc /data/local/tmp/
adb push PD98IMG.zip /sdcard/
NOTE: the last command will take a long time
After all files are pushed you have to run tacoroot:
Code:
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
This command will reboot the phone to recovery. Once it is done, use vol up/power then choose 'reboot' to reboot the phone. After it boots (it will bootloop, that's expected):
Code:
adb shell
/data/local/tmp/tacoroot --root
this command will kick you out of adb shell, so we need to return there and see the # sign of root access, after which we can change the main version and create a goldcard:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
./flashgc
./tacoroot --undo
After these commands are done, the phone should get rebooted by tacoroot. After it boots, boot to bootloader to flash the 1.32 firmware:
Code:
adb reboot bootloader
Once in bootloader, use the vol buttons to go to 'bootloader' and the power button to execute. The rom will flash. Enjoy!
Credits:
the tacoroot team
skorgon for flashgc
Donate to RevSkills and EFF!
fail againnnnnn:crying:

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
use this
http://forum.xda-developers.com/showthread.php?t=1377119

For the last few days I have try new software
Z4root No chance another fail...

for debrand use latest RUU, WWE version.. no branded
for rooting use advanced ace hack kit

The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
failed..........

new Advanced Ace Hack Kit system
I just found a new chance and I'm trying it
with new Advanced Ace Hack Kit system, I found it at http://tau.shadowchild.nl/attn1/?p=74
was Posted on July 26, 2012
The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
AAHK will work on Inspires on AT&T’s latest ROM, 3.20.502.52 only after following the steps outlined here: http://tau.shadowchild.nl/attn1/?p=88 .
Warnings:
If your PC environment is not ready to run this kit, there is a good chance your device will not boot properly until you fix your PC or switch to another and re-run the hack kit from the partial boot. READ THIS ENTIRE POST and READ THE EFFEN MANUAL! There is no substitute for READING for COMPREHENSION
Do NOT use earlier versions Ace Hack Kit (12.x and lower) on Inspire or DHD devices shipped with Gingerbread.
Do NOT attempt to downgrade a Inspire or DHD shipped with Gingerbread with a Froyo RUU.
Do NOT attempt to install earlier ENG HBOOTs on these models. AAHK now has Hboots that safely support fastboot image flashing.
Doing this WILL severely degrade bootloader performance on Inspires and DHDs and causes issues trying to install RUUs. In other words, it WILL jam you up. (Note: Issue confirmed on later DHDs – ignore at your own risk).
Sense 3, including those with RELOCKED HTC BOOTLOADERS (NOTE: NOT UNLOCKED – MUST BE LOCKED OR RELOCKED) is auto-detected in hack step. Option is given to download a GB RUU and downgrade or abort. This WILL wipe data.
#include <std_disclaimer.h>
/*
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because you can’t tether. Please
do some research if you have any concerns about features included in this
TOOL before running it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
*/
(Disclaimer borrowed heavily from cyanogenmod)
Features:
COMPLETELY INTEGRATED/INVISIBLE GOLD CARD PROCESS
Custom AAHK Bootloaders support popular ENG S-OFF functions for both Sense 2 and Sense 3 partition layouts
Only ONE menu step – HACK ACE
No ROM downgrade required (only radio/kernel) for devices not running sense 3
The original ROM is retained (except when downgrade from Sense3-GB is required)
No wiping data for devices not running sense 3
Rom is fully functional (yes, inc wifi)
Fully rooted with insecure boot image (supports adb remount for rw system)
Busybox manager app installed
Radio S-Off, superCid & carrier sim unlock
Correct Radio is automagically restored for HSPA+ operation
Clockworkmod Recovery included
All known Inspire/DHD builds supported
Easy return to stock for SOME builds (See the Effen Manual – not all carrier RUUs are available)
Notes:
Please do NOT run the hack step if you are already S-OFF AND are running a custom ROM. It’s pointless, and while it won’t brick you, you can get jammed up a bit. This is for stock devices only.
You MUST read the ENTIRE EFFEN MANUAL in order to run the hack kit.
Do NOT try to run this from a VM – particularly VirtualBox. You WILL get jammed up and may wind up flashing an RUU to recover, losing data in the process.
After kernel downgrade – video is lost on boot – this is okay as adb is working and can be used to finish the process. If the process fails, it can be restarted once the PC environment is corrected. When the process completes successfully, everything is restored and fully working.
Youtube videos are neat demos, but they make poor guides. READ THE EFFEN MANUAL. “There is no substitute for reading for comprehension.” – GenePoole
Make sure you extract the hack kit to your pc maintaining the directory structure in the archive you downloaded. The docs will be in the root directory of the unarchived kit, as will the scripts. READ THE EFFEN MANUAL.
I can’t believe that so many people are asking where the effen manual is. THE EFFEN MANUAL IS IN THE EFFEN HACK KIT.
This kit should work fine on HTC Inspire and HTC Desire HD Software versions below 3.06.405.1 which require the radio/kernel downgrade before a root exploit is available.
Windows Prep:
IMPORTANT – disable all malware (Antivirus detection etc) detection before unarchiving the hack kit. Keep it off thoughout the hack kit processes. Many Windows malware detection programs report false positives, deleting or binding critical files required by the process.
IMPORTANT – Remove or disable all services and daemons you can, particulary anything Apple, blackberry, PDAnet, Microsoft Mobile, anything USB not required for this task, any resource hogs. Also disconnect all un-needed USB devices and USB HUBs.
Remove HTC Sync and drivers.
Only after completing the above steps, install the drivers contained in the Hack Kit (see the Effen Manual) BEFORE plugging in the phone.
Connect the phone to the computer via a USB port connected to the system board – not a front panel port or a hub or extention port.
Verify successful android device driver installation in device manager.
Issues during downgrade:
IMPORTANT: BEFORE SWITCHING FROM DISK DRIVE TO CHARGE ONLY MODE, ALWAYS EJECT THE SDCARD WITH PC SOFTWARE TO FLUSH WRITE BUFFERS AND AVOID CORRUPTING THE SDCARD.
model ID incorrect update fail – this is because your goldcard is not working.
READ THE EFFEN MANUAL. Reading is fundamental.
Download:
Note: AAHK filename uses ddmmyyyy naming convention.
aahk-11092012.zip
md5: 5727960aa167b305b8f3561ffbbb1360
viperbjk is with Revskills, and his contribution is key to finally allowing one step processing where a goldcard is required. The entire process is now one menu step. A second step will be required to clear your conscience –
DONATE to:
Revskills.
and/or
Electronic Frontier Foundation
Note: No money has been accepted for the AAHK or support of the AAHK by myself or anyone working with me on it.
If you have read this post and the effen-manual and get stuck during processing,
help is available in IRC at http://webchat.freenode.net/?channels= – aahkSupport
Yes, there are stupid questions.
Questions that will get you immediately kickbanned from the IRC channel with no further explanation:
Q: Do I need to flash a ROM after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: Do I need to flash a radio after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: The options menu has options to flash radios. Do I need to flash a radio?
A: Kickban. What part of “optional” is vague? This option is to make it easy for people who may have flashed another radio and want to flash back to these particular radios.
Q: Do I need to plug in the phone?
A: Kickban. If you know how to enable usb debugging without a USB connection, then I’ll change this policy. In the meantime, asking such a question just makes me think you have not read anything and/or have dedicated yourself to being an idiot.
Q: What’s the best ROM?
A: Kickban. The whole point of this is to give YOU control and allow YOU to decide. Yes, we prefer CM7 and I think it’s the only real Android choice available, but don’t ask us to think for you. If you don’t see that pretty much everything else is either ripped off or HTC Non-Sense, then you haven’t done your homework and that’s okay. Just don’t ask, because in the end, it’s YOUR choice.
Q: Facebook doesn’t work.
A: Kickban. This has nothing to do with anything but Facebook. Go ask Facebook, not us.
Q: I can’t find the pass key.
A: Kickban. Really? Then you did not really read the Effen Manual. If you really did, then you would not ask. Really.
Q: My phone won’t boot – how do I fix my HBOOT?
A: Kickban. We’ve been warning people not to flash Froyo Hboots (Including HTC ENG ones) on devices shipped with GB for going on a year now. If you do this and screw up, it’s not our fault and you’re on your own.
This IRC channel is for people who read, attempt and get stuck because of PC issues or an occasional bug introduced with a new feature. It’s not for people to troll those who dedicate their time for support without any compensation by asking a series of mindless, inane questions and observations for attention. We’re too busy for that – even if we have nothing to do. It’s beyond annoying and you will be kickbanned without warning. Read, search, think, try, then ask.
The people in #aahkSupport have been helping noobs without compensation for over a year now, with generally very good results and a generally good nature, despite being abused by some on almost a daily basis.
Thanks to:
Revskills for their fantastic gold card algorithym
GenePoole for the kickass android goldcard binary based on above
agrabren for fre3vo, the Gingerbread temproot used
scotty2 for finding the vold exploit and the author of psneuter
Guhl for misc_version and gfree
hyuh for misc_version revisions and Hboots with ENG features
jcase for taco root
shad0wf0x for his windows scripting contributions
ktilcu for DOC contributions
anthony1s for his review and unique perpective
neolobster for his generous file hosting
The > 150,000 downloaders of the hack kit, most of whom seem to get though it without issue.
and they have amazing feedback's, lets try it now....

sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol

PauloMHAlmeida said:
sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol
Click to expand...
Click to collapse
Well, don't forget that you also need to read the "effen manual!"

I have not forget to read it but is a fail....
thanks for telling me that but I found the solution for all S-ON HTC...
and for the Hboot lol
is a big journey I made on the last months, and I have put some staff all together and got it made lol
just wait for my next post how to duet....

look for my next post
There's no need to make the phone S-OFF (like some people say).

PauloMHAlmeida said:
look for my next post
There's no need to make the phone S-OFF (like some people say).
Click to expand...
Click to collapse
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.

I'm finish here Just look for my next publication Thanks

fr34kde said:
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.
Click to expand...
Click to collapse
There's no need to make the phone S-OFF (like some people say).
Disable fast/quick reboot (Settings » Power » Fastboot)
Download all
Fastboot commander.zip http://www.mediafire.com/download.php?xsu7c3m981o9gb8
Google.zip http://www.mediafire.com/download.php?cm9pdoh2g9mkgvb
Superuser-3.1.3-arm-signed http://www.mediafire.com/download.php?kzpbhq13jb085s8
Android ultimate toolbox pro http://www.mediafire.com/download.php?6m5w39zmb6ph8gq
Recovery.img http://www.mediafire.com/download.php?grl8wsjzxihhfwf
Update http://www.mediafire.com/download.php?dzkww8zaq7sxhae
Fastboot.bin http://www.mediafire.com/download.php?bhzth13p4kvow4v
Copy in to the root of your sd card after been formatted
Google.zip + Update.zip + Superuser-3.1.3-arm-signed.zip
On your pc create a new folder on C: and name it HTC for easy access and copy in to the folder
Recovery.img + fastboot binary
Install on your PC
Fastboot commander.zip + Android ultimate toolbox pro
Start rooting
Unlock bootloader: http://htcdev.com/bootloader/
Put the phone in Fastboot USB mode (Turn off, hold Volume Down + Power)
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin (file from email)
Install ClockWorkMod recovery the recovery.img from my link our use android ultimate box to flash recovery
fastboot flash recovery recovery.img
Make a backup
Start clockworkmod recovery (Fastboot mode, Recovery)
Select backup and restore
Select backup
Go to your mobile start it as Fastboot and go to recovery
You go in to Clockworkmod Recovery V5.0.2.7 from the Ace Hack Kit
On the top is the menu with + and – buttons just scrool in to advanced and press power
Select “Wipe Dalvik Cache”
Then select “Wipe Battery Stats”
Then select “And go back”
Then select “Wipe data/Factory reset”
Then select “Wipe cache Partition” (Now you have cleaned all the old staf from your mobile)
Now let’s start rebuild the HTC
Select "apply update from sdcard"
Then select "Yes - install update.zip" to confirm
Then select "install zip from sdcard"
Then select “google.zip”
Then select "Yes - install google.zip" to confirm
Then select "install zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back to your pc for the files you have download and unzip update and copy Boot.bin to the file you created C:\HTC
o Flash boot.img trough fastboot:
o fastboot flash boot boot.img
o Reboot
• Done
• You should have now a white screan from HTC for at least 5 minutes and after will sart the new room, just let it on for a couple minutes and you will see the sucess….
All my files are at http://www.mediafire.com/?al6dsdcd6c02f
Enjoy it, next I will say how to sort google play problem I found it easy lol…

PauloMHAlmeida said:
[....]
Unlock bootloader: http://htcdev.com/bootloader/
[....]
Click to expand...
Click to collapse
And thats the point.
You do what S-OFF does through HTC-Tool.
Now u unlocked the bootloader and your warranty is gone because your device is registered now.
Why should anyone go the complicated way if there is an easy way?

Firts have 2 types of waranty, 1st the manufactors warranty. That runs off 3 years after your purchase, 2nd the software warranty... And HTC have take off that point on the warranty, now you can unlock our relock the bootloader from your HTC with out lost of your warranty... By the way that's the reason HTC created HTC devoluppers web page...
And if you want to understand that just read all my post's. Changing our due hboot s-off make you lost warranty lol....
Sent from my HTC Desire HD A9191 using xda app-developers app

Unlocking Your Bootloader
HTC is committed to listening to users and delivering customer satisfaction. We have heard your voice and starting now, we will allow our bootloader to be unlocked for 2011 models going forward. We plan on releasing the updates that will allow you to unlock your bootloader in the coming months, please keep an eye on this website for more details on which devices will be adding this feature. We are extremely pleased to see the energy and enthusiasm from our fans and loyal customers, and we are excited to see what you are capable of. HTC eagerly anticipates your innovations.
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
Un lo c k Bo o tlo ad er
Unl oc k th e pos s ib ilit i es wit h to ta l cu s t omi zat io n
Unlock Bootloader
Frequently Asked Questions Preview Unlock Process
Supported Devices
Select “All other supported models” if you cannot find your phone in this list. Devices launched after 9/2011 will be shipped with the unlock capability. Please check back often for updates on the unlock status of additional devices.
------- Select Your Device ------
Beg i n Unl o ck Bo ot l o ad er
* Indicates HBOOT update required.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, certain models may not be unlockable due to operator restrictions. We continue to work with our partners on this, check back often for ongoing updates about unlockable devices.
Copyright © 2012 HTC Corporation. All rights reserved. Terms of Use Privacy Policy About HTCdev HTCDev Affiliates Follow Us Comments - Tell HTCdev what YOU want.

[GUIDE] [T-Mobile] Unlock Bootloader, Install Custom Recovery, Root, S-Off

This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
There was speculation that the phone's build date might be a reference for who's phone was compatible with firewater. This is not the case. There is no correlation between build date and compatibility. A further explanation is given under the S-Off instructions.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXXdevice
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXXfastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
>
And end with this line:
>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Hi Recipient
Attached in this mail is your unlock bootloader key file. To use this file to unlock your device, simply follow the remaining instructions on the website to complete the process and successfully unlock your bootloader.
Please remember that unlocking your bootloader may void all or parts of your warranty and your device may not function as intended by HTC. Unlocking the bootloader is for development purposes only.
* Click here to continue the bootloader unlocking process.
The bootloader unlock key file can only be applied to the device with which you generated the token.
Please do not reply to this email which is auto-sent by server.
If you need to contact us with questions please click here.
Sincerly,
HTC
Click to expand...
Click to collapse
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' ...
OKAY [ 0.151s]
writing 'unlocktoken'...
unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' ...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
There was speculation that the build date was an indicator of compatibility with firewater's S-Off method. As several people expected, there is no correlation. There are batches of components that HTC purchased from various manufacturers that vary in compatibility with the firewater exploit. At this point there is no known method to determine if your phone will be compatible with firewater. Unfortunately, it's just a shot in the dark. So, if you're comfortable, give it a shot and hopefully you're compatible.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones

FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app

jcase said:
FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info! Changed in OP.

Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.

Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app

fryingpan0613 said:
Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the bottom edge of the box on the same sticker as IMEI.
Sent from my HTC One M8
egcthree said:
Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.
Click to expand...
Click to collapse
Updated OP to show that firewater may not work without having to show the contents of the S-Off info. Thanks for the comment.

I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8

OctoberNexus said:
I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8
Click to expand...
Click to collapse
Nope. That means that firewater won't work for you and S-Off isn't yet achievable for your phone.
OP updated with your build date.
Sent from my HTC One M8

Hopefully there will be another way in the future until then running GPE ROM which is a lot better than nothing still not what I had in mind when purchasing this thing.
Sent from my HTC One M8

Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:

thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list

VolcanicSkunk said:
This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​ g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​ h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​ i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0KB>...
OKAY [ 0.151s]
writing 'unlocktoken'...
<bootloader> unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​ j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​ a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​ e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' <14,818KB>...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
The speculation is, there are different components used during the builds due to sourcing those components from different companies. It seems that some people believe that the phone build date may indicate the devices that have components that are compatible with the exploit. So we'll document this to try to see who achieved S-Off on which build dates.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​ Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
Build Dates S-Off Achieved On:
04/01/2014
04/04/2014
04/07/2014
04/12/2014​
Build Dates S-Off Not Achieved On:
04/03/2014 x2
04/08/2014
04/09/2014
04/10/2014
04/11/2014​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones
Click to expand...
Click to collapse
tks

tnez said:
thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list
Click to expand...
Click to collapse
Thanks for posting your results. OP updated with your build date.
abutran said:
tks
Click to expand...
Click to collapse
You're welcome. If you don't mind, please edit your post to remove the quote of the OP. It keeps the thread much shorter for people on mobile devices. Thanks.
Sent from my HTC One M8

uoY_redruM said:
Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:
Click to expand...
Click to collapse
Saw your post in the other thread and agreed with you! It was way too many pages to sift through.
Sent from my HTC One M8

Anyone good to go with a build date of 04/01/2014?

donciclon said:
Anyone good to go with a build date of 04/01/2014?
Click to expand...
Click to collapse
My build date is 04/01/2014 and I was able to achieve S-Off. If you try it, let us know the results. We haven't pinned down if the build date is the indicator. I'm hoping like hell it is though.
Sent from my HTC One M8

04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk

irrelephant said:
04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day.
Click to expand...
Click to collapse
That's what I was thinking too. Multiple runs happen on any given day.
I was hoping it would be as simple as the build date. Of course we're not that lucky though. Lol. Whelp.... Back to the drawing board.
Sent from my HTC One M8

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.
Click to expand...
Click to collapse
Well what information might be of assistance and I will gladly provide it. I'm pretty good with adb, and willing.
Sent from my HTC One_M8 using Tapatalk