Develop Bugs

[Guide] Return stock without latest RUU

Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:

I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?

There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium

ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.

HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself

a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?

ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium

darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium

or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.

usefull for some case
bookmarked

BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2

unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time

darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium

I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?

lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file

hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.

lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks

lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium

hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9

lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.

Unable to root my phone, need help please

Hi guys,
Apologies for starting a new thread, but I've spent the last day trying to root my DHD without success. I've tried everything I could from searching through similar problems on the forums but I'm getting stuck and very frustrated and need some help please.
My phone:
Vodafone Australia branded
Android version 2.3.5
Sense 3.0
Software number 3.12.178.2
HBOOT-2.00.0027
My noob attempts so far:
1. First I did a factory reset
2. Then I tried to install Miui following this link - http://en.miui.com/a-57.html & this tutorial - http://www.youtube.com/watch?v=wNoMelTPvok, but it got stuck installing VISIONary.apk and wouldn't do a temp root.
3. I then found this forum & started reading up
4. I tried the EasyAceRootTool but get this error;
Obtaining Unlock Token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.057s
5. Upon further reading it seems I needed to update my hboot, so I got the correct RUU from HTCdev site, but I get the message - Error 191 when using RUU - Rom not supported.
This is where I'm stuck and all my attempts to update the hboot have failed, despite reading through similar problems on the forum. So is my only option to create a gold card with this link? - http://forum.xda-developers.com/showthread.php?t=970157 Do I use my phones sdcard or do I need a spare one?
Hopefully there's something obvious I'm doing wrong and would really appreciate any help thanks.
Rob

yokelhama said:
Hi guys,
Apologies for starting a new thread, but I've spent the last day trying to root my DHD without success. I've tried everything I could from searching through similar problems on the forums but I'm getting stuck and very frustrated and need some help please.
My phone:
Vodafone Australia branded
Android version 2.3.5
Sense 3.0
Software number 3.12.178.2
HBOOT-2.00.0027
My phone is 3 years old and I wanted to give it a new lease of life with a new ROM. First I did a factory reset, then tried the EasyAceRootTool but get this error;
Obtaining Unlock Token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.057s
Upon further reading it seems I need to update my hboot, so I got the correct RUU from HTCdev site, but I get the message - Error 191 when using RUU - Rom not supported. This is where I'm stuck and can't find any further solutions. Is my only option to create a gold card with this link? - http://forum.xda-developers.com/showthread.php?t=970157 Do I use my phones sdcard or do I need a spare one?
Hopefully there's something obvious I'm doing wrong and would really appreciate any help thanks.
Rob
Click to expand...
Click to collapse
No, you can use the easy ace root tool script that creates the goldcard image. Then use simple gold card tool to patch the SD card. Link is in my signature.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

glevitan said:
No, you can use the easy ace root tool script that creates the goldcard image. Then use simple gold card tool to patch the SD card. Link is in my signature.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Ok, so I run GC.cmd as admin first, then follow the steps?

So I've managed to create a succesful goldcard thanks, but now I need to "flash it in the PD98IMG.zip way". Not 100% sure the process for that, so about to have a read around.

I'm still confused about how to "flash it in the PD98IMG.zip way" as referenced here - http://forum.xda-developers.com/showthread.php?t=2169515 I don't understand what I'm menat to download, from where, or where to put or run it?
I managed to run EasyAceRoot.cmd as admin and got an unlock token. I put that into the token folder, but the command prompt window just displayed 'waiting for device' and nothing happened.
Now, I'm trying this step - http://www.htcdev.com/bootloader/unlock-instructions/page-4/ but it wants me to download a 440mb sdk file, was I supposed to have all this installed first, don't recall reading that anywhere.
So, at this stage I have a goldcard & unlock token, but my phone is still not rooted. Please any more help?

Bah, I'm ready to give up, gonna take a break for awhile. I'm getting a Error[170] Usb connection error now.

About to head to bed in Aus, I've spent all day going round in circles here, so hopefully someone will have some help in the morning for me.
Basically I'm stuck at these steps with no root still:
IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
1. Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
DONE
2. Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
I've tried various RUU's changing the ROM.zip to PD98IMG.zip on the sdcard, but they all fail in hboot. I tried the RUU that auto downloads with EasyAceRootTool, the stock Vodafone Australia ROM (http://forum.xda-developers.com/showthread.php?t=842722) & even one from shipped-roms, but they give this message "Main version is older! Update Fail!"
3. Re run the tool and you will be able to update the hboot and unlock it
I've tried this also but get the following message "Error[170] Usb connection error". I have pdanet, htcsync & android sdk tools all installed.
I even tried to downgrade to an earlier version using this guide but couldn't pass the final step.
Any help at all is greatly greatly appreciated, please what am I doing wrong?
Cheers
Rob

yokelhama said:
About to head to bed in Aus, I've spent all day going round in circles here, so hopefully someone will have some help in the morning for me.
Basically I'm stuck at these steps with no root still:
IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
1. Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
DONE
2. Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
I've tried various RUU's changing the ROM.zip to PD98IMG.zip on the sdcard, but they all fail in hboot. I tried the RUU that auto downloads with EasyAceRootTool, the stock Vodafone Australia ROM (http://forum.xda-developers.com/showthread.php?t=842722) & even one from shipped-roms, but they give this message "Main version is older! Update Fail!"
3. Re run the tool and you will be able to update the hboot and unlock it
I've tried this also but get the following message "Error[170] Usb connection error". I have pdanet, htcsync & android sdk tools all installed.
I even tried to downgrade to an earlier version using this guide but couldn't pass the final step.
Any help at all is greatly greatly appreciated, please what am I doing wrong?
Cheers
Rob
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
download the hbootupdate_kit zip and the rom.zip from there.Extract the hbootupdatekit in any folder you'd like, and place the rom.zip in C:
Run the HBOOT Update .bat and see what it tells you.I've used this to update to .0029 numerous times and it has worked.

Iydryne ftrong
Steam. said:
Try this.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
download the hbootupdate_kit zip and the rom.zip from there.Extract the hbootupdatekit in any folder you'd like, and place the rom.zip in C:
Run the HBOOT Update .bat and see what it tells you.I've used this to update to .0029 numerous times and it has worked.
Click to expand...
Click to collapse
Hi, thanks for your help.
This is what happens, I waited for 10mins but no change. The phone screen is black with the HTC logo displayed.

Success! I finally got it all sorted, but not really sure how lol.
In hboot this morning it says I'm updated, ran the easyacetool and everything finally worked perfectly.

[Q] ReApply Lollipop ROM on Unlocked S On M8

Hi,
I did a mistake by not S off my mobile prior to upgrade. However, I under stood from the response (http://forum.xda-developers.com/verizon-htc-one/help/sunshine-su-access-denied-t2845121/) that I'll have to wait till sunshine 3.0 come out.
Meanwhile, I've a long history of ROM/OS issues with this device. Now it got OTA update from 4.4.4 to Lollipop
Unfortunately, there seems to be missing files from my last system erasing
For example, the Exchange ActiveSync keep deciding on random basis not to sync, asking for the password (which is not changed) then it resolve the issue by itself. Another example is the camera, where I cannot enable video recording from inside the camera, I seem to be able to make from within messenger apps!!! :S
So, my question would be how can I reapply the Lollipop ROM again?
I've downloaded both, the exe file from HTC support site, and the zip file from RUU famos article on this forum.
The exe version says it will reboot to recovery but it never finish (stops on black screen with HTC gray logo)
The zip file installation through recovery failed, and through renaming it to 0P6BIMG.zip and put it on the SD root failed as well.
Any ideas?

Need to add, I've downloaded the file "RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe"
Now, when running this tool, it says the update will be:
From Image version: 4.16.401.10
To Image version: 4.16.1540.8
I'm not sure, but is this file for another model?

Read carefully here
http://forum.xda-developers.com/showthread.php?t=2701376
Read it well and it has all the answers to get back to stock backup and update again.
If you are s-on you can't flash any other ruu than the one that matches your phone.

help

friends would you help me my htc one m8 it stuck of a htc logo with 4 error signs and wont work .i attached pictures of the error and the bootloader

Was it you trying to update the firmware ? Reinstall firmware.zip again to fix that.
Or .. run the official RUU from here : http://www.htc.com/us/support/htc-one-m8-att/news/
(one thing to note : there is no need to relock bootloader to do anything when your device is S-Off)

how to do that my friend iam a nowbie in these thing also i dont want an at&t thing also for your notice i dont have a recovery in it , its simply empty

You just need to install that AT&T RUU to bring it back to life.
Once it is working normally, you can install other ROM on it.
What you need is a Windows PC with USB 2.0
Latest HTC USB drivers installed on PC. Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Download the RUU that I gave link earlier.
Connect to PC
Right click the RUU exe and select run as Administrator and follow the intructions

my friend do you have a youtube link showing how to do all this

No ... no idea as I never rely anything on youtube.
What I gave you, you don't need youtube.
Just download and install those three items.
1. ADB/Fastboot - when you install, it asks to install adb/fastboot, type Y
then it asks to make it system wide - type Y
then it ask to install drivers - type N
2. Install the HTC Sync Manager as it will install the drivers. Once completed, uninstall HTC Sync Manager but leave all other things
3. The RUU.exe, right click on it and in select run as administrator then follow the pop-up instructions accept - next - next - blablabla until it says completed.
Most important your PC must have USB 2.0

i did what you said but then i get this error
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
it says on the bootloader

I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.

ckpv5 said:
I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.
Click to expand...
Click to collapse
Yeah my friend i realized this and install the gpe ruu and its now working fine with 6 thanks alot hope you feel much better

Somebody to help me with this... (HTC One M9)

Hello everybody
I'm the owner of a HTC One M9 and I really love it! I'm kind of newbie on Android.
This is my case, I can't upgrade my firmware to 6.0.1 (or later) I'm still on Android 5.0.2 and I tried to install a cyanogenmod firm that kind of fit with my model... BUT! it start to have some many problems.. like the display starts to break the images and start to repetitive the image like an a glitch... when a phone call comes it turn off or restart it was like a dead phone... Then I install a MaximusHD 1.0.0 and it come back the same way it was but it returns to Android 5.0.2... I already unlock my phone and it's S-OFF via sunshine...
So, If you have some info that help me fix this (upgrade to Android 6.0.1 or later) or you have the same experience please leave your comment!
My data:
MODEL: htc_himawl
CID: LRA_001
MID: OPJA30000
Cheers!
Alvaro

Boot your phone into download mode, connect it to your computer and make sure ADB and FASTBOOT drivers are installed and working.
To ensure your device is connected, type "fastboot devices".
Your Bootloader needs to be unlocked, this is done with "fastboot oem unlock".
First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.

Kartoffelrudi said:
[...]First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
Click to expand...
Click to collapse
Please don't give such advise if you don't know what you're talking about. The OP owns a CDMA device and the dev firmware is GSM. GSM and CDMA aren't compatible and you can't convert the one into the other due to their different partition layouts. In the worst case this can lead to unrecoverable damages.
Edit: This post isn't meant to be an offense. I just want to prevent the OP from doing something he/she could regret afterwards.
Edit 2 @cedricpixler: You'll need a windows PC if you want to use the following instructions. Win 10 and 8 (or 8.1) might not work whereas win 7 is always fine. I'm using win 10 myself without any problems but others have been reporting that they needed to use a win 7 PC.
Charge your phone to at least 50 %.
Go to HTC's US website and download the latest RUU for your SKU. Your current firmware is stated in Download Mode in the line that starts with "OS". The SKU are the numbers behind the second dot of the firmware version.
If not already done you should download and install the HTC Sync manager. Uninstall it directly, afterwards. This way you update the needed drivers to the latest version. If you keep the manager you might face some connectivity issues during the upcoming steps. Next you need to boot your phone to Download Mode and to connect it via USB (if possible use a 2.0 cable and port instead of 3.0) with your PC.
Disconnect your PC from the internet. Disable your antivirus program and your firewall and execute the RUU as an admin. In some cases the flashing process might take some time so don't worry if it hasn't finished after 10 minutes.
When the RUU has finished you can re-activate your av program and your firewall. Afterwards you can re-connect your PC with the internet. Your phone should be up to date now.
Not every step is actually essential but if you follow these instructions the most frequently occurring problems should be prevented.
Sidenote: Every problem you faced with custom roms is based on the difference between your current firmware and the base of the mentioned roms.
If you want to use a sense-based custom rom after you updated your firmware you need to re-flash the stock boot.img of your firmware after you flashed the rom. For non-sense-based roms like CM you need to flash thicklizards mono kernel. If you don't do this your phone won't recognize your sim card.
Sent from my HTC One S using XDA Labs

Thank you @Flippy498, I will take this steps you write and I will write here the results.
Somebody from LlaTooFer Maximus was helping me and send me this
"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."
I tried the first step (installing the full firmware but this error comes up "C:\Program Files (x86)\platform-tools>fastboot flash zip 3.37.605.13_FULL_firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (41818 KB)...
OKAY [ 3.430s]
writing 'zip'...
(bootloader) HOSD CL#523158
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7: fail to flash via downloadzip)
finished. total time: 4.567s"
But they or he doesn't tell me whats going on.... or what to do next.. @Flippy498 do you know if this instructions could help to change my CID or MID..? and If my phone is CDMA can I re Write the CID or MID

cedricpixler said:
[...]"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."[...]
Click to expand...
Click to collapse
Interesting, being a 24/7 Viper user since the One S was my main device I didn't know that Llabtoofer doesn't support CDMA devices at all.
My bad. I missed the fact that you don't have the Verizon CID. (I only looked at your MID and wasn't even aware that this MID belongs to more than one CID.) If you want to change your CID then you need to do so manually via fastboot use "fastboot oem writecid VZW__001" while your phone is booted to Download Mode and connected to your PC via USB. Flashing that firmware pack before the RUU shouldn't be necessary (but it shouldn't hurt either). Besides I would download the latest 605 RUU (605 is the Verizon SKU) directly from HTC. Afterwards it's your choice whether you stay on stock or whether you want to install the latest Viper rom.
The MID of a CDMA device should never be changed. Even the sprint firmware (CDMA, too) isn't compatible with Verizon devices and vice versa. Changing the CID should be fine, though.
Sent from my HTC One S using XDA Labs

Update: Well I save my phone! the fact is that I just change the CID to VZW__001 and practically I followed the instructions I posted here and flash the last ViperOne firm and Kaboom! I have the latest firmware and it's so stable! If any one has the problem I had just ask me how I do.
Cheers!

@Flippy498 I see that Nugat comes for HTC M9, did you know if there is any official 7.0 stock from HTC? for CDMA phones like mine? Cheers!

Only the dev edition (GSM) got the update yet.
Last year Android M got released one day before Christmas for that sku and most of the rest of the world received it between mid January and the end of February 2016. Therefore I think that the unbranded skus might get the update around the end of this year (if we're lucky) or at the beginning of 2017. Branded skus like the CDMA ones always need a little more time than the unbranded ones due to all the bloat the carriers want HTC to add to the system.
I don't have a direct link at hand but there is an article on the xda portal which explains in general (not HTC-specific) why carrier-branded phones need to wait that much for their updates. If I remember correctly it got published sometime during the summer.
Sent from my HTC One M9 using XDA Labs