Develop Bugs

[Q] Unable to load ROM

Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.

MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.

Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.

agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.

Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!

First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?

Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!

Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.

THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.

Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.

S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.

Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.

S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...

Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.

If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.

Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!

No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

no easy access or UI after deleting internal storage (newbie)

Hi,
Here's my story: I have a factory unlocked M9 bought in Belgium. After reading in XDA, I unlocked the loader, and install TWRP (2.8.5.0). I then made a backup and installed ARHD 5.2.
Everything worked fine, until I decided to sell my device (I live in Argentina, and although I bought the international version, it does not cover 4G band 4). So in order to sell it I wanted to wipe everything back to factory settings. I went ahead and restore my backup. Again everything worked flawlessly, but then I saw some folders in the internal storage that were not supposed to be there (such as maildroid folder, among others). So I went back to TWRP, wipe, advanced, "delete internal SD". oops, wrong choice...
I rebooted and then notices appeared "Unfortunately UI has stopped..../ unfortunately easyaccess has stoped...", losing all functionalities (no touch buttons, I had to restart every time I wanted to change menus).
I restored again the backup...no luck. I then installed again AR 5.2...no luck.
I wanted to RUU (I am not sure I know what it is, but I do know how to follow step by step guides...well at least sometimes...). my phone is S-ON. I tried installing sunshine to S-OFF, but I got the message "No SD card", so it wouldn't let me install it. in fact when I use the HTC file explorer it looks as if there is nothing in the internal storage.
I don't think I can fastboot (USB not recognized). I read that phones needed to be S-OFF ( http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545 ), so I don't know what else to do.
I really tried all related posts but I can't find the answer....
Any help is really appreciated (of course I couldn't sell the phone). Thanks.

A RUU is a Rom Update Utility. It's a little program made by HTC to reinstall a stock firmware and/or rom on a phone that is S-ON. Depending on the build number and the CID of your phone the needed RUU is an *.exe or a *.zip.
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware if you are on stock rom.
Otherwise you need to boot into download mode where you can find the build number (written in the line with "OS" at the beginning) and the CID of your phone. Since you never mentioned any branding and you bought the phone in Belgium I'm assuming that the CID is something like HTC__*** and that you can use a European RUU.
Next you need to download the corresponding RUU for your build number (just use Ctrl+F for easier searching) and your CID. Since the CID isn't explicitly mentioned in the RUU names you may have to search for the meaning of your phones CID (for example in a list like this one).
If the needed RUU is a *.zip then you have to rename the file to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32 and put the sd card into your phone. If you now enter download mode your phone should guide you through the rest of the procedure.
If the needed RUU is an *.exe then you just have to connect you phone to your pc and start the file (on windows).

Flippy498 said:
Are you still able to enter Settings>About>Software Information>More? (Not completely sure whether these are the correct english terms. On my phone it's Einstellungen>Info>Software-Informationen>Mehr.) There you can find the build number of the installed firmware.
Click to expand...
Click to collapse
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Flippy498 said:
Then you need to downlad the corresponding RUU (just use Ctrl+F and enter the build number for easier searching), rename it to 0PJAIMG.zip (that's a zero not an O), copy it on an external sd card that is not bigger than 32gb and formatted to fat32. If you put this sd card into your phone and enter download mode your phone should guide you through the rest of the procedure.
Click to expand...
Click to collapse
Ok there are two 1.32.401.15 version for Europe,that only differs in the release: Which should I use
1. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
2. 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R2_Radio_01.01_U11440261_56.02.50306G_2_F_release_427846_signed.zip
Flippy498 said:
Edit2: I forgot another important thing. (Sorry, I'm in a little hurry right now.) Your CID needs to correspond to the RUU you want to run. Since you never mentioned any branding I'm assuming that it is something like HTC__*** so that you can use a European RUU. You can find out by booting into download mode. (I'm not completely sure whether it's written there if you are S-ON. If not you can either try using an app like CID Getter or the fastboot command "fastboot getvar all".) If your CID differs from HTC__*** I would suggest you to post it here together with the build number so that it's easier for me or someone else to guide you to the correct RUU.
Click to expand...
Click to collapse
I cannot install anything as the internal storage is not recognized by the OS. However I was able to fastboot:
OS-1.32.401.15
HTC__031
Kernel: lk
Thank you for your help!

gsember said:
I had access, the build number is 1.32.401.17 CL506785 release keys. However from download mode I got Mainversion: 1.32.401.15. So I guess I have to use the latter right? I do not need to be S-OFF, because I can't make it....
Click to expand...
Click to collapse
I think that the original stock was 1.32.401.15 as ARHD 5.2 that I flashed comes with the 1.32.401.17

Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.

Flippy498 said:
Yes, that's right. Since there has not been an aboot update until now you can also try to install the 1.32.401.8 RUU and then update via the stock OTA function. I've done this with my phone before I got S-OFF so I know that it works. This way you can be sure that the correct version of the 401.15 firmware gets installed.
Click to expand...
Click to collapse
Ok, I already installed the first release of 1.32.408.15. it worked flawlessly. Should I relock (or lock) the phone to receive OTA?
Use a 32 GB card tip saved my day! ( I had a 128 GB which the phone didn't read)
Thank you all.

I am now trying the second release as the first one did not recognize 5G wifi networks.
Is it possible to receive OTA once you have an unlocked bootloader? XX.15 is the latest version? because ARHD has XX.17?
thanks again

Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.

Flippy498 said:
Actually I don't know whether it's necessary to relock the bootloader if you want to install an OTA but I would guess it is. The 401.15 version is the latest European one. 401.17 is only receivable on HTC__J** but llabtoofer stated on his twitter account that the next European update is waiting around the corner.
You mentioned earlier that you cannot connect your phone with your PC and that fastboot isn't working. Did you try to connect your phone to another PC/Laptop (maybe your parents/siblings/friends can help you out if you don't own another one)? As far as I know there is no way to relock bootloader without a PC.
Click to expand...
Click to collapse
Thanks. Everything is working smoothly. Actually fastboot is working. I won't continue to play.....
Appreciate your answers

HTC One M9 - 3.35.401.12 RUU installer how to guide!

I wanted to make a small guide how to return your HTC one m9 to stock with RUU exe installer. The steps are pretty simple so please follow them. Please note that this is only for WWE international models. Same procedure can be done for other regions, however, the files are different. Doing this, you will also get a latest Marshmallow and 3.35.401.12 update! This will save you of hassle to copy and flash your phone several times over to get it done, this procedure does all that. You will not even need to open a command prompt.
Before you do this procedure backup yours files somewhere safe. This will wipe everything you have on the phone to stock settings. This will also unroot your device and remove custom recovery if you had any.
Follow this guide step by step. Do not open / run anything if I haven't said so.
1. For sake of being organized make a new folder on your desktop called "RUU" and make sure your phone has more than 30% battery otherwise RUU procedure wont work.
2. Download HTC sync manager from here and install it (this can help if RUU installer starts derping with USB connections etc : http://www.htc.com/us/support/software/htc-sync-manager.aspx
3. Download the RUU exe from here and put it in the RUU folder you created on the desktop: https://www.androidfilehost.com/?fid=23991606952597788
4. Download the rom.zip file from here and put it in the RUU folder on your desktop. File name needs to be rom.zip
5. Navigate to TEMP folder by typing %temp% in the search bar. If you can't find the temp folder this way then simply navigate to: C:\Users\PCname\AppData\Local\Temp
6. Select all folders you see there and delete them. If you get a file in use or skip message then please do so.
7. Go back to the RUU folder we created earlier and run the RUU exe file from step 3 as an admin. Give it a little time to load and once you are here don't press on next.
8. Copy rom.zip file from RUU folder and navigate to %temp% folder. Paste rom.zip file here: http://prntscr.com/a5gwae
9. Once copying is finished go back to the RUU exe window from step 7 and start clicking next until it prompts you to update. Click on update to 3.35.401.12.
10. During this procedure the phone will go on and off for a few times and after several minutes it will give the message that procedure has been finished successfully.
- Please note that all files are official. Hope this little guide helped you.

TnQ so much man. I was searching for this RUU for a while but couldn't find it. I'm gonna test it tomorrow. BTW i have an unlocked bootloader and s-on, do i need to relock bootloader before installing RUU?

No, you don't have to.

Or just rename the rom.zip to 0PJAIMG.zip copy to the sd card root, after that power off the phone hold vol- and power select download mode and follow the instructions on the screen.
BTW thx for the rom

why is this not stickied?

Please I need marshmallow RUU for hima_uhl my camera and flashlight stopped working only flashing RUU will fix it

Quick question guys, running marshmallow 6, 3.39.531.7, I want to roll back to Android 5.0.2, 1.32.531.33. Is this possible via this method? Phone is not rooted and s-on? T-Mobile is the carrier
Sent from my HTC One M9 using Tapatalk

cloves said:
Quick question guys, running marshmallow 6, 3.39.531.7, I want to roll back to Android 5.0.2, 1.32.531.33. Is this possible visa this method? Phone is not rooted and s-on? T-Mobile is the carrier
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Downgrades are not possible as long as you are S-ON. You need S-OFF to do this.
Send by the swarm intelligence of my coffee machine ?.

Ok so I could flash the same firmware via this method so long as the ruu matches? Unless of course I could s-off then s-on before sending the phone back in.
Sent from my HTC One M9 using Tapatalk

Question: Once I RUU to Marshmallow from this, am I able to install CM13? I assume so. ( My phone is Htc One m9 (att/cingular) (502)) or will this not work, seeing you have the International (401))

ROM DL problem
After downloading "ROM" it says that is corrupted...!!! What now?
thanks
BR

HTC One M9, Help to get back to stock to install 3.5
Good Morning I have tried all this step by step, i cannot not get this to work does everything except put on my phone, phone is connected to pc via usb and through HTC sync Manager and reconised and have done exactly every step, can someone please help, i have Viper installed 3.5 as i am only on os-2.9.841.5 as i have accidently deleted backed up firmware, Can someone Please help, Regards Freddy

i got S-ON and **LOCKED** i tried to run the RUU(not the one on this thread but in htc/download the UNLOCKED/DEVELOPER HTC One M9) but it gives me error 131(which is wrong region) So is there a RUU international? and is there a possible way to S-OFF free?

error 158 image error.
i tired updating my m9 to 6.0 with ruu.exe but i get this image error message.now am stock at just the startup screen.pls i need help.the phone has no carrier

THANK YOU VERY MUCH FOR THIS GUIDE!!!
I had problems with my M9, now everything is ok! http://forum.xda-developers.com/one-m9/help/m9-freezes-t3456653

I'm on 3.35.401.12 100% will work? Anything I need to do first?

Thank you so much for this!

my M9 CID is HTC__002. Is it true if I flashed the RUU, my phone will be flashed into demo mode?
thanks

Eayip1 said:
my M9 CID is HTC__002. Is it true if I flashed the RUU, my phone will be flashed into demo mode?
thanks
Click to expand...
Click to collapse
Please don't post more or less the same question in several threads. It's considered as rude behaviour on xda.
An xda search for "demo" would have been enough for finding this thread. If you read the whole thread you'll learn everything about the problems that arise with the latest firmware and the Demo-CID HTC__002.

Flippy498 said:
Please don't post more or less the same question in several threads. It's considered as rude behaviour on xda.
An xda search for "demo" would have been enough for finding this thread. If you read the whole thread you'll learn everything about the problems that arise with the latest firmware and the Demo-CID HTC__002.
Click to expand...
Click to collapse
Oh, i didnt know that. Im so sorry man..
Thanks

Bricked my HTC 10, What to do next?

Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks

Have you tried doing a factory reset using the stock recovery?

See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.

tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?

@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs

Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset

5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.

tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?

Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse

bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs

5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?

If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?

tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.

Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.

bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.