Develop Bugs

[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] Widfier S: Can't obtain Identifier Token

MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry

GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
First things first, your problem is not unique..........just less often found
The reason you are not able to get an Identifier token is because of HTC Sync............. HTC Sync usually tends to block any ADB or Fastboot commands
So all you have to do is uninstall HTC Sync, don't worry about it as uninstalling it won't remove the drivers

Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?

GERJDOY said:
Thanks very much for replying csoulr666
I promptly uninstalled HTC Sync, leaving:
HTC BMP USB Driver (Ver: 1.0.5375 ) 0.35MB
HTC Driver Installer (4.5..001 ) 2.82MB
and have tried the "get token" process again.
It has not worked.
Do you think that I should also uninstall the HTC Driver Installer?
Click to expand...
Click to collapse
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah

Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port without the SIM and SD cards (they may be erased while unlocking). Choose the Charge only option in your phone.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.

GERJDOY said:
MY ISSUE seems unique!! Please, is anyone able to figure this out?
I have a HTC Wilfire S A510e that I've been trying to root for three months!
It's stats are:
***LOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.
HTC Sense Version: 2.1
SO...I created my a/c on HTCDEV.COM, tick all boxes etc. No need to update bootloader, as per instructions, so I "proceed to next step".
I created \Android ( in My Documents) on my Dell Latitude D630 (using Windows XP); downloaded the "Fastboot binary, Windows (unzip the file before executing)" file [Fastboot-Zip] to \Android & also the recommended Android SDK zip, Java Runtime Environment. I already have HTC Sync 3.3.63. All unzipped. I set up my HTC- fastboot off, usb debugging enabled, bootloader screen up> click on fastboot, usb into it, the phone registers "Fastboot USB" and then open the cmd prompt on my pc.
The problem I encounter is this:
On the cmd prompt instructions:
I open cmd prompt- My pc cmd line says c:\documents and settings\administrater>[blinking cursor]. I type- c: cd \Android at the blinking cursor. That's okay as my cmd line returns- c:\documents and settings\administrater>[blinking cursor] again.
I type- c: \Android> fastboot oem get_identifier_token at the blinking cursor [hit enter] and...
Nothing happens! Nothing at all- not even the "waiting for device" problem that seems to be common at this stage.
I'm meant to get:
INFO <Please cut following info>
INFO <<<< Identifier Token Start >>>>
INFO {**multi lines of numerical text**}
I get nothing!
What's going wrong?? I've done weeks and weeks of research using google search; read hundreds of threads on multiple sites; in frustration I've even asked a question on Yahoo Answers, Android Forums & emailed HTCdev, but had only one answer and it was to use another port and another cable, both of which I've done, neither worked.
I just don't get it. Any assistance would be fantastic.
Thanks, Gerry
Click to expand...
Click to collapse
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"

csoulr666 said:
It should work now IMHO, did you see if your device is being recognized using "fastboot devices"???
Plus setting the folder to apply commands("cd"), try using the complete path that comes in the address bar in My Computer/Windows Explorer..........It would be like C................documents and settings......blah blah blah
Click to expand...
Click to collapse
Thanks for your continued time and assistance csoulr666. It's taken me a while to reply because after having no sucess having followed your advice, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
And following your recommendation I retried using the full path when typing both commands and it still didn't work. I'm not sure what you meant by "........your device is being recognized using "fastboot devices"???"
However, as you've mentioned "fastboot", I think I've identified an issue with the fastboot binaries from HTCdev. Please see my new post below.

aWFSuser said:
I think you are doing wrong with the c: android step you should first "cd android" and then enter "fastboot oem get_identifier_token"
Click to expand...
Click to collapse
aWFSuser- thank you for the advice.Yes, I do use the c: cd \Android command first, everytime I try the cmd process, even if it's after somthing silly like removing the sd card from the phone, putting a new one in (to render the "as disk drive" option available in the "USB connection type") on the handset, changing the USB port I'm using to a different one etc.
But thanks.

ukyo_tachibana said:
Hi,
If you can not find a solution for your method of getting the token, you may try another method that worked fine for me.
1) Search for HTC Wildfire S All-In-One Toolkit V2.1 post.
2) Read carefully the whole post.
3) Uninstall everything related to HTC (HTC Sync, USB drivers, everything).
4) Do not use USB hubs or USB 3.0 ports. Enable USB Debugging at the phone settings and plug the phone directly to an USB 2.0 port.
5) Proceed with the tool steps (select the step and click on 'go')(in useful links there is a link to a step by step guide):
a) Install the drivers.
b) Register at HTCDev (this is already done).
c) Get the ID (beware, you will see and empty command prompt, close it, and a second command window will appear with the token)
d) Submit the token to HTCDev.
e) Get the Unlock_code.bin file from your e-mail account.
f) Unlock the boot loader.
6) Once you have finished, I recommend to install the clockworkmod recovery with the same tool. Download the right version GSM or CDMA from the Clockworkmod official site. Beware: make sure that you download the right version for your phone. I think yours is GSM, but I am not an expert, sorry. It may be fatal if the wrong version is installed (brick). Choose the option your own recovery in the tool.
7) Create a backup before doing anything else.
8) You are ready to get a permanent root or install a ROM.
I hope this helps you. Feel free to ask any question. Regards.
Click to expand...
Click to collapse
Thanks so much ukyo_tachibana.
I will try this method, if I have failed to identify the issue correctly.
After having the problem of being unable to obtain my identifier token for so long, (trying now for 3 months!), I've been looking for a way to unlock bootloader & root- that works for the Wildfire S WITHOUT having to use the "get_identifier" process.
THANK YOU for this method!

It's taken me a while because after having no sucess, I decided to delete EVERYTHING and IT ALL FRESH, monitoring all downloads as they happened and ensuring I followed all steps and instructions PRECISELY, in case I did something wrong the first time around 3 months ago!
So, once again:
I created a folder: double click Local Disk C: then \Document&Settings and \administrater >Make a new folder. Called it Android.
Downloaded from HTCdev's links- HTC Sync, Java Runtime Enviroment & Google Android SDK to \Android.
(1) SYNC. Uninstalled Sync, as per csoulr666's advice. Used Control Panel> Add or Remove programs. This left HTC Driver Installer & HTC BMP USB Driver & also setup_3.3.63 (in \Android).
(2) JAVA. Opened chromeinstall-7u51(Runtime) and installed. Checked it installed correctly via Verify Java Version on java.com.
(3) SDK. Unzipped the zipped folder adt-bundle-windows-x86-201... It created a new folder- "adt-bundle-windows-x86-201.." with 2 subfolders & 1 application in it; subfolders (1)"eclipse" & (2)"sdk" along with the application "SDK Manager". NOW, as per instruction following the SDK download, (just in case it was relevant to what I am doing, although I don't think so as Eclipse is a developer tool as I understand it), I opened the eclipse sub-folder & opened (ran) the Eclipse application which set itself up in \workforce. I exited Eclipse in case it interfered with anything else. I did not run, open or do anything else with the adt folder at this stage.
Set up my HTC as per instruction- fastboot off, debugging on & usb to disk drive, (I've also tried it on the charge only setting), downloaded fastboot-win binaries from HTCdev to \Android. Clicked unzip and it generated 1 new folder _MACOSX & an application- fastboot; both in \Android. NOW HTCdev says "open cmd prompt...etc". So I did and retried the process twice. Once typing c: cd \Android. Then the c: \Android> fastboot oem...etc. It didn't work. So I repeated the process using the full path in both the commands- c:\Documents and Settings\administrater\ cd \Android; then c:\Doc...Sett...\admin...\Android> fastboot....Once again nothing. IT DID NOT WORK.
HOWEVER: I did notice 2 things!
(1) Probably nothing but there was a new folder created in \administrater, right beside the Android folder. As I was working from \Android, I didn't notice when happened. I did not do it. It called itself .android; ( "a dot" and a lowrecase "a" for android). I can't recall at what stage of the process this came into being. It contains 1 folder- "avd", which is empty, & 3 files- "adbkey" file, "adbkey.pub" file & "ddms.cfg" file.
(2) Just, following the latest failure of the cmd process working, I thought maybe I was meant to do more than just unzip the fastboot-win, so I went to the fastboot application and tried to open it, It said:
"The application failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem"
So I deleted it, re-downloaded from HTCdev, unzipped. Opened prompt, reran the cmd "get_identifier" process and it still hasn't worked. Again I to run the fastboot.exe in \Android
It still says "...application failed...AdbWinApi was not found. Re-installing the application...".
Does this mean the file download itself on HTCdev,com is corrupt? Could THIS BE the source of my problem????
Thanks.

I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token

csoulr666 said:
I'm attaching a zip with the files I use for this stuff............Extract them in a folder, use the "cd" command to it and then try to obtain the token
Click to expand...
Click to collapse
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help

GERJDOY said:
***csoulr666
Yes!! Thank you for the files. HTC's MUST BE corrupt, as your's have worked a treat & also. they behave differently ( "fastboot" application) when <highlight/right click > is used!! No error message! THANK YOU for your files. ***
They worked & after three months and hundreds of hours research, I HAVE MY TOKEN!! You guys are BRILLIANT!
However, there is a new issue, perhaps you can help with this also...
I copied the token exactly as HTC stated on their website. I started at <<<Identifier Token Start>>> & ended with <<<IIdentifier Token End>>>.
There are 18 lines in total- 16 lines of alpha/numeric sandwiched between the above 2 of text.
Both of HTC's examples also have the same line-count (18 in total 16 + 2) & layout as mine.
But when submitted, the website rejects it and the following error is returned:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
I've spent most of last night on this. I've tried logging in and out of HTCdev, copied and pasted multiple attempts (busy web traffic perhaps). I have cleared browser cookies/cache & history in case it's something like that. Counted and recounted my token in comparison with their examples, in case I made a mistake somehow. What am I doing wrong??.
Also, today when I tried the cmd get_token process, I got a different token i.e. a completely different set of 16 lines of alpha/numeric text. Is the token different every time it's requested?
Thank you all for your expert help
Click to expand...
Click to collapse
see whether you have copied the code correctly as instructed at HTCdev

Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.

By the way, two comments:
1) Note that unlocking HBoot is a destructive process, you will loose everything in the phone memory (similar to a factory reset). Besides, the SIM card and the SD card may be also erased, so remove both before starting.
2) If you want to install a custom rom, you don't know which one to install yet and you want some help, I can suggest one that has been working like a charm for more than one year in my Wildfire S. It is based on the last stock rom, but with several tweaks to overcome the limitations of the terminal (amount of RAM, internal storage, etc.). Do not hesitate to ask.
Regards.

ukyo_tachibana said:
Hi,
The token seems to be different every time you retrieve it, I don't know why (maybe someone can enlighten us ).
Regarding the token copy/paste. At the command window: right click, select mark, draw the rectangle enclosing the <<<< Identifier Token Start >>>> and <<<<< Identifier Token End >>>>> (this also includes all the alphanumeric token), right click again to copy. Now, paste it in Notepad, PSPad or any other text editor, and make sure that there are no white spaces, tabs, or any other special character, such as this example:
Code:
<<<< Identifier Token Start >>>>
5C1161E707F362366365EA333A6B51D6
7B52743B74534195B1C0CD07E738AEA3
93A6BD42CFA2C05006C6282B590CEDC3
6593DE3AEF7786B79527C1027E871C3D
9DDD04692D8F653D9BD548D86CB0AC58
01CDF6096D229B7E418BD74E8AC2311C
77D92CE222450E4B233CEC2286DD9CA4
C0871C78B430F4474C74FCE113E95C2D
2134C5495D588B3A580710A226A6675C
3D9F01CB8A8EF628A4EC2BB867E47D3E
2476FE360221DC834197EAECCA4BB09A
243420AEB1CFC713A658FC0A156448A9
6859FF58473B71BDFFFF5FFF292B066B
9CA1B055827C43BFE0F30A656906801E
35FD964354DAA6F83A38FE7D7452B97A
171BDB3A9D280118C638240DEDA452DE
<<<<< Identifier Token End >>>>>
If you select previous lines, there are no unwanted characters, check it. Once you are sure that everything is okay, submit the token to HTC.
I hope this post helps you. Regards.
Click to expand...
Click to collapse
BRILLIANT!!
I followed your recommendation- copy to notepad- there were white spaces:
Note: the <right click/copy> function was not available in cmd prompt.
I had to "mark" and then ctrl & c to copy.
I had spaces at the end of each of the token's lines.
Thanks. Token successfully submitted- just over ten minutes ago. Awaiting an email back from HTCdev with an unlock key and link for Unlock completion!
I assumed I'd have it instantaneously...but I'll be patient; it's taken this long to get this far...what's a few hours? more.
I have not given ANY thought to ROMs etc.
This part of the process baffles me.
This all began three months ago when I got the Wildfire S- my first ANDROID phone- and I noticed there are loads of pre-installed apps on it, many of which I have absolutely no interest in: like Peep, News & Weather, Maps & tons more via: Applications>Running Services>All. TO MY UTTER AMAZMENT I could not delete any of them!
Call me old fashioned but I would like to decide what I put on my phone and have total control over them. On this phone certain apps would start up of their own volition i.e. when the handset was powered off, then on; gather information and data; all without me even using/ activating them e.g. Google services/ Facebook. I could stop them manually, but like I said they would reassert themselves on start-up.
I'm unclear yet exactly what I can safely get rid of without damaging my handset, I need to do research I know, as some processes may be vital to the phone's operation, but I have been consumed with this first basic step- Unlocking the BootLoader.
Ideally, I would love to start with an empty phone- just the basics: calls/messages/phone book/ calender/ alarm facilities with a browser.
A normal, basic phone.
Any extra apps I am then free to decide upon, install, set permissions (where possible) & remove as & if I choose.
Thanks.

Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.

ukyo_tachibana said:
Hi,
Did you get the unlock binary file? It should take no longer than a few minutes (or even less) to send it to your e-mail account. Did you successfully unlock the HBoot? Let us know . Regards.
Click to expand...
Click to collapse
Hi ukyo_tachibana,
Thank you for your ongoing interest. I appreciate it greatly.
I have been checking my email address all night last night, and also today, awaiting my email from HTCdev.
No! As yet (over 24 hours later), I have not yet received my response.
HTCdev's site confirmed that I successfully sent my token when I did. I remained logged in for a hour and a half afterwards, just so the site would notice/ remember me. Sounds daft, but I really want this episode to finish now after all this time. I really thought I had cracked this step!
The web page said to expect and email with my unlock code and a link to directions to help me complete the process.
Now, over 24 hours later, I still have not received any communication from them. I check my email address- the one I used to register with them and, in late December of last year, communicate as to why I the "get_identifier token" process was not working- ever hour or so for the file & link. So I'm sure the site has my correct email address.
I was actually wondering what to do now as I'm unsure as whether I should wait X amount of time, contact them via the "contact us" option on their web site or resend a token to them and risk confusing the process. Basically I'm just playing the waiting/ unsure-of-next-move game.
Thanks.

Hi,
Do not despair . The token should be send to you in question of seconds (but in order to be safe wait a few minutes, no more than 5 minutes). The email sender should be something like [email protected] and the subject should be The key to unlocking your HTC Device (at least, this is what I received).
I would:
1) Search for the email in any other folder than the Inbox, such as spam. Your email provider may have archived the message in a different folder.
If you are not able to find the message:
2) Try to find your email white list and add htc.com and htcdev.com to the list, in order to avoid that emails from HTC or HTC Dev go to the spam folder or are erased.
3) Check that you activated your account. Register at the website is not enough, you also must activate your account clicking on the link that HTC send to confirm your email address. I know that this question is a bit stupid, but it just to cover all the possibilities that I can think about.
4) Get and send again the token.
I hope this helps you. Regards.

I have my email now.
Before I proceed, as I'm a complete techno-novice, I was just looking into how to create a full back up of my stock ROM, in case I decided to pass on the phone later I can return it to it's current out-of-the box condition- with all it's apps etc. Also I need to be clear on the root process files. I don't have the original SD Card. I have two to hand though- a 2GB & 4 GB.
Step 1- Unlock BootLoader.
REALLY, REALLY NOT sure of the rest:
Step 2- download CWM Recovery from (http://www.clockworkmod.com/rommanager/) 5.0.2.8 for the Wiidfire S to my PC.
?Move to SD Card
?Hboot>Recovery>chooseCWM and there should be an option to "Back-Up/ Restore"
?Select this option and "Back-Up". Wait for stoc ROM to be copied onto SD Card. When it has this is the back-up phase complete
As I understand it this will give me a re-installation disk type set up for my current ROM.
Step 3
?Find and download a file to my PC called "Root Zip".
?Transfer it to my SD Card
?Hboot>Recovery>choose file and it roots the phone itself.
Step4
?Find and download a file called "SuperSU"
?Move to SD Card and install.
??This gives me an app called "SuperSU" which allows me now to modify my phone how I like it to be- prevent apps starting at boot/ remove any preinstalled ones that I don't want or do I need to install a custom ROM?
Thanks,

[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

[Q] Bought M8, many problems/questions

Hi guys,
I've rooted my phone before and installed custom roms so not a complete noob but not far off. Anyway, down to my problems.
I bought phone off a guy, cheap. M8 running stock 5.0.1. Didn't get to look over phone properly, all looked ok. Then I noticed the problems.
Camera working but wont take pictures, says insert an sd card before using camera.
Cannot take screenshot as says no storage available (phone and sd card empty almost)
Can sign into my Google account, use gmail, photos, music but not hangouts or playstore. They will not load.
Cannot download apk's or zip files through chrome browser, so cannot get a file manager
Baseband, imei and kernel look ok but Seial number is some weird mix of characters and pictures, like <]#~q?/
Recovery is installed and phone is S-off. Computer recognizes phone but cannot see adb devices. This means I cannot change modelid from this weird serial number.
Some details
CID: GOOGL001
HBoot: 3.19.0.0000
Radio: 1.21.213311491.A04G
What would you guys recommend? Backup and install a sense rom through recovery? I have a feeling that will not work because of the serial no/modelid issues.
Any help would be greatly appreciated, I am broke now with a semi useless phone!! Please!!
Cheers guys
EDIT: ISSUE SOLVED
Was able to install a working backup through twrp (obtained elsewhere) This backup contained my serial no, modelid and imei details.

I would try to return the phone for a refund, if you can. As it seems like the phone is all manners of messed up.
If you purchased with no method of return or refund . . . well I'd never buy a phone that way. But if that is the case, we'll try to get her working again.
---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------
beardo81 said:
What would you guys recommend? Backup and install a sense rom through recovery? I have a feeling that will not work because of the serial no/modelid issues.
Click to expand...
Click to collapse
It looks like the phone has been fully converted to GPE, or was GPE in the first place. So you can't flash a Sense ROM until you fix the partitions by RUU. So you are right that you can't do that unless you change the CID and MID.
To be clear, what color is the hboot screen?
---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------
beardo81 said:
Baseband, imei and kernel look ok but Seial number is some weird mix of characters and pictures, like <]#~q?/
Recovery is installed and phone is S-off. Computer recognizes phone but cannot see adb devices. This means I cannot change modelid from this weird serial number.
Click to expand...
Click to collapse
Serial number and model ID (MID) are 2 completely separate and different things. Which one is messed up, or are they both screwed up?
---------- Post added at 10:50 AM ---------- Previous post was at 10:27 AM ----------
beardo81 said:
Computer recognizes phone but cannot see adb devices.
Click to expand...
Click to collapse
You're trying adb with the OS booted, right (not in bootloader, which won't work)? And debugging is enabled in Settings?
Does fastboot work (needs to be in bootloader-fastboot mode)?

redpoint73 said:
I would try to return the phone for a refund, if you can. As it seems like the phone is all manners of messed up.
If you purchased with no method of return or refund . . . well I'd never buy a phone that way. But if that is the case, we'll try to get her working again.
Unfortunately not an option, private sale and seller has 'disappeared'
---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------
It looks like the phone has been fully converted to GPE, or was GPE in the first place. So you can't flash a Sense ROM until you fix the partitions by RUU. So you are right that you can't do that unless you change the CID and MID.
To be clear, what color is the hboot screen?
Hboot screen is black, looks normal, states I have S-OFF and CID-GOOGLE001
---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------
Serial number and model ID (MID) are 2 completely separate and different things. Which one is messed up, or are they both screwed up?
They both are messed up, when I check through fastboot I see different weird characters. Very odd. Like a mixture of chinese numerals, small emoji and characters, maybe 8 of them.
Just to be clear though, I have box and checked imei online, it is a real M8
---------- Post added at 10:50 AM ---------- Previous post was at 10:27 AM ----------
You're trying adb with the OS booted, right (not in bootloader, which won't work)? And debugging is enabled in Settings?
Does fastboot work (needs to be in bootloader-fastboot mode)?
Click to expand...
Click to collapse
Debugging is enabled and fastboot seems to be fine too. Computer sees phone now (I installed drivers and HTC SYNC) but just now showing in adb devices.
Even if I could install a working GPE version on it I would take that, but at moment cant use camera, hangouts or Play store. So just browsing, texts and calls!!
Cheers for help, I appreciate any given.

Managed to copy the serial number from Settings> About Phone > Status. It is:
<眇?]q 戴
Nothing comes up when I google this, its very very strange and I have no idea how to change it!

beardo81 said:
Managed to copy the serial number from Settings> About Phone > Status. It is:
<眇?]q 戴
Nothing comes up when I google this, its very very strange and I have no idea how to change it!
Click to expand...
Click to collapse
since its s off i would try returning it to sense

toysoldierq said:
since its s off i would try returning it to sense
Click to expand...
Click to collapse
I tried reinstalling a gpe ROM last night and using the 5.1 update file also, but neither worked. Think I will try returning to sense today.
Would the serial number problem be when something corrupted during gpe conversion maybe?

Here is my getvar. Check out modelid and serial number. Bizarre.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: <þ£Ã└⌂*╩L]q▬÷H┤
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: ☻r♠
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
PLEASE SOMEONE HELP!!!

Private message me or Google hangouts

Did you try to run an Official GPe RUU?It should return the phone to stock GPe and maybe fix your serial No to prior state.
P.S. you may want to hide your IMEI from your previous message.

nighthawk696969 said:
Did you try to run an Official GPe RUU?It should return the phone to stock GPe and maybe fix your serial No to prior state.
P.S. you may want to hide your IMEI from your previous message.
Click to expand...
Click to collapse
Ive tried this, will not run because of the modelid issue, error 41 I think.
Thanks, hidden imei, not thinking!!

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
Sent you pm buddy. If it didn't get through let me know, it's not coming up as sent

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
I've received your message and replied but it is not showing under my sent messages. Am I not allowed private message yet maybe?
Anyway, thanks for the message, so should I type 'fastboot oemwrite xxxxx'?
I'll give it a shot!!

toysoldierq, are you getting my pm's?
That didnt work btw

Thanks for help toysoldierq, appreciated.
Guys, this is still unsolved if anyone can help?
Cheers

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
It's nice of you that i see you helping people constantly via teamviewer or PM but nobody else can benefit from that. This is an open forum and can also be used to learn by reading, we can't read your PM 's unfortunately !

I'm sorry but sometimes it's hard to explain to a person what to do, from now on I will keep it here

toysoldierq said:
I'm sorry but sometimes it's hard to explain to a person what to do, from now on I will keep it here
Click to expand...
Click to collapse
I did it for years on the hox, it's most off the time all same. I made a basic layout with steps and commands. Little copy and paste here and it was done
Cheers

It looks like the underlying issue here is the modelid and serial number got corrupted while whoever had the phone before me was changing it to GPE. The phone is useable for browsing and texts and calls but that's it.
I can sign in with my Google account and use YouTube, gmail, drive, photos, music etc but not hangouts or play store. No file explorer and can't download or open apk or zip files on phone. Camera launches but won't take pictures as SD card is not recognised.
Can't seem to contact phone via adb on computer although I can by fastboot. But this means I can't try change modelid this way.
All in one tool doesn't work. The flasahable zip for changing modelid on XDA didn't work.
I didn't do a full wipe yet through recovery as seeing as every time I have tried to flash anything I am getting met with error 41, modelid.
Pulling my hair out here guys!!

beardo81 said:
It looks like the underlying issue here is the modelid and serial number got corrupted while whoever had the phone before me was changing it to GPE. The phone is useable for browsing and texts and calls but that's it.
I can sign in with my Google account and use YouTube, gmail, drive, photos, music etc but not hangouts or play store. No file explorer and can't download or open apk or zip files on phone. Camera launches but won't take pictures as SD card is not recognised.
Can't seem to contact phone via adb on computer although I can by fastboot. But this means I can't try change modelid this way.
All in one tool doesn't work. The flasahable zip for changing modelid on XDA didn't work.
I didn't do a full wipe yet through recovery as seeing as every time I have tried to flash anything I am getting met with error 41, modelid.
Pulling my hair out here guys!!
Click to expand...
Click to collapse
Infact i wonder if you tried to re write the model id if that woud help or you could try to go back to sense
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
everything you need is in these threads
http://forum.xda-developers.com/showthread.php?t=2708581
http://forum.xda-developers.com/showthread.php?t=2733523

toysoldierq said:
Infact i wonder if you tried to re write the model id if that woud help or you could try to go back to sense
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
everything you need is in these threads
http://forum.xda-developers.com/showthread.php?t=2708581
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
Hi soldier,
I've tried both of those and neither will work. I cant seem to communicate with my windows 8.1 pc through adb. When I try to change the serial number with fastboot another error comes up.
I wonder if I tried a windows 7 pc would that work? Means I'll have to turn my other laptop into an win7 laptop now too!!
Very frustrating as I cannot seemingly falsh anything, either through fastboot or recovery

RUU Flash ADB stuck during 'sending ZIP'

Hi Folks
Let me preface by saying I've flashed RUU before, and flashed many recoveries and ROMs over the years, not a total novice, but certainly no expert either. But I've never seen anything quite like this one, and not sure what to do at this point.
first, I downloaded the GPE non-rooted RUU and copied the zip into my ADB folder (Windows 10 PC)
then, I connected phone, shift+rclick open cmd window in ADB folder
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
adb devices - device recognized
adb reboot bootloader
fastboot oem readcid - it's GOOGL001, no problem
fastboot oem rebootRUU - no problem, HTC logo displayed on device
fastboot flash zip <drag and drop file into cmd window> - (note, I haven't actually done that before, I've always just typed it, and drag+drop showed whole file path - "C:\user\me\adb\ruu2.zip.zip" - but shouldnt make a difference, as far as I know, so I hit enter)
it ran through everything, checked zip, etc then failed. This is expected and normal, no problem.
so I hit up arrow, reloaded the command and hit enter...
and now my cmd window is stuck. It says "sending zip", displays file size, and the cursor is flashing...and nothing is happening. It's been an hr or more. Nothing is going to happen.
Now what?
If I pull the phone am I going to be bricked? I just alt-tabbed and googled for a solution, but didn't find anything. So I figured I better post here. This is not a good place to be stuck.
Thanks in advance.
(I have a screenshot of my cmd window but I don't have enough posts to link it.)
EDIT: Figured worst case = new phone. Pulled cord. CMD window reset itself, phone stayed in RUU mode. Would not power down or respond to any button combo. Reconnected cable, entered command again, and it went. Worked fine. No idea why that happened, but all is well.
Thanks anyway.
Mods, please close thread. Thanks.

Sir_Cusfreak said:
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
Click to expand...
Click to collapse
Highly recommend you disable the Windows option to hide file extensions, to avoid any future file name confusion.
Sir_Cusfreak said:
Mods, please close thread. Thanks.
Click to expand...
Click to collapse
Threads typically stay open, in case there are other members with a similar issue, subsequent comments, etc.
Mods usually only close threads, if you start a thread about something you shouldn't have!

Hi, just wanted to say that the same thing happened to me, i got stuck on sending zip .. and i did like the OP, disconnected the cable and reconnected again, the cmd reset just like the OP said and after i put the command again it worked for me too. Cheers.

i had to do the trick a few times before it worked. thanks