Develop Bugs

Error 132 when using RUU

Right now I'm facing problem to update to stock using RUU.
My version is 2.17.707.3 so I dowload from HTCRUU the file named RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed.exe, but after some operations (reboot to bootloader, etc) gives me an 132 error saying: "Signature error". Why is that?
Also I found other RUU file named RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed.exe, Can i use just this to update to JB?

Before you proceed, check the actual version no. Go to bootloader in fastboot mode, do command fastboot getvar version-main then you will know which RUU is correct for you.
Example, mine is 3.14.707.24, then RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Ra dio_5.1204.162.29_release_296434_signed.exe is the correct RUU for my device.
Code:
D:\HTC\fastboot>fastboot getvar version-main
version-main: 3.14.707.24
finished. total time: -0.000s
D:\HTC\fastboot>

I already do that. That's why I know how version to use.

Then follow this procedure to flash the RUU
1) Boot to bootloader in fastboot mode, relock your bootloader - fastboot oem lock
2) Still in fastboot mode, run the RUU follow the updater instruction until it finish.
Important points relock bootloader & run ruu in fastboot

I already do that too. The problem is that after 1 minute, it says ERROR 132, "Signature Problem"

ERROR 132, "Signature Problem" usually refer to unlocked bootloader. As you said you did relock the bootloader, I have no idea. Maybe someone else can assist you on this.

Quick question. After flash the stock recovery is mandatory to erase the cache using fastboot erase cache?
After relock the bootloader, can I flash the stock recovery?

Not mandatory but recommended.
You can't flash stock recovery or stock boot.img after you relock the bootloader.
If you need to flash those to you device, do it before you relock the bootloader.

ckpv5 said:
Not mandatory but recommended.
You can't flash stock recovery or stock boot.img after you relock the bootloader.
If you need to flash those to you device, do it before you relock the bootloader.
Click to expand...
Click to collapse
Im also stuck with this issue! Error 132!!! I cant flash my HOX+ back to stock and I need toO!!! hhheelp!!

i have htc one x 4.0.3
fastboot getvar version-main
device >
1.29.401.12
total time: 0.010s
The bootloader is relocked and the Hboot is 0.95
tried to upgrade to JB 4.1 with RUU_ENDEAVOR_U_JB_45_S_hTC_EUROPE_WWE_3.14.707.24_Ra dio_5.1204.162.29_release_296434_signed.exe but wont finish due to a 132 signature problem error...
What are the steps i have to do ?
best regards

leddra2k said:
Im also stuck with this issue! Error 132!!! I cant flash my HOX+ back to stock and I need toO!!! hhheelp!!
Click to expand...
Click to collapse
Ok, just to ask, this is HTC One X section, and in quote i can see that you have HTC One X +? Did you download RUU for HTC one X or HTC One X +?
Because guide for back to stock with RUU is just like previous members wrote... go into fastboot, relock bootloader, run RUU (with administrators rights in vista or win7)..
And for the others: http://forum.xda-developers.com/showthread.php?t=1859714
Stock OTA and RUU: http://androidfiles.org/ruu/?dir=Endeavor
IMPORTANT from the link:
Get the RUU file required for your device:
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
Code: fastboot getvar version-main
If for example this command returns the value 1.29.401.x then you need to use that file or you can use a higher numbered file from the same region eg 2.17.401.x. NOTE: You can't use a lower numbered file eg 1.26.401.x and you also can't use a file from a different region eg 2.17.707.x.:
PROCESS :
1. Boot your phone to fastboot mode by holding power+vol down button for 10 secs..(if your phone keeps restarting in normal phone mode, go to Setting>Power and untick Fast boot)
2. Plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
3. cd to the location of your fastboot files folder
4. Relock bootloader - type command:
Code: fastboot oem lock
The phone will then restart into fastboot again showing "RELOCKED"
6. On your pc run the RUU (vista and win7 run as administrator) that you downloaded earlier, follow the steps as prompted and patiently wait for it to finish.
REMEMBER your phone should be charged ABOVE 50% (Full battery is advice) AND if the RUU or restore is INTERRUPTED 4 any reason during restore your
phone will be PERMANENTLY BRICKED..

I have successfuly installed the rom 4.1 from insertcoin i have update the hboot and the right firmware. Thebproblem im facing is the phone keeps rebooting, the installation of the rom ended with no errors... i have full wiped the phone formated the cache... amy idea how to fix the auto reboot? Thanks

armandino said:
I have successfuly installed the rom 4.1 from insertcoin i have update the hboot and the right firmware. Thebproblem im facing is the phone keeps rebooting, the installation of the rom ended with no errors... i have full wiped the phone formated the cache... amy idea how to fix the auto reboot? Thanks
Click to expand...
Click to collapse
It's because you didn't flash the correct boot.img or you didn't full wipe your device.. start over and follow these steps:
1. flash boot.img from rom.zip and then fastboot erase cache
2. Go to recovery and flash this script : http://d-h.st/B2K
3. Flash rom.zip
4. Reboot
PS: From next time, please don't highjack other people's thread by asking questions not related to the topic! If you need further help, open a new topic!

Please help. I am getting
fastboot getvar version-main
version-main:
finished. total time: 0.230s

ladylane100 said:
Please help. I am getting
fastboot getvar version-main
version-main:
finished. total time: 0.230s
Click to expand...
Click to collapse
try with fastboot getvar all

F:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-baseband: 1.46.40.0721
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) product: a11_chl
(bootloader) platform: hTCBmsm8226
(bootloader) cidnum: SPCS_002
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6a60e19e
(bootloader) gencheckpt: 0

ladylane100 said:
F:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-baseband: 1.46.40.0721
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) product: a11_chl
(bootloader) platform: hTCBmsm8226
(bootloader) cidnum: SPCS_002
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6a60e19e
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Strange I think you are not with ONE X international we never have this this radio 1.46.40.0721 and for first time I see this CID SPCS_002

Boas pro htc m9 3.35.401.32 qual é o ruu de nougat correto pra instalar pode me ajudar ?

(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: removed by me
(bootloader) version-main: 3.36.709.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
!!!!!!!!!!!!!!!!!!I AM ALSO GETTING ERROR 132 WITH HTC M9 RUU DOWNLOADED FROM HTC OFFICIAL SITE...!!!!!!!!!!!!!!!!!!
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12.exe

[Q] Error 152 during ruu update

hi...i need help!i was flashing an ruu on my htc one X and in the middle of the update it says error 152 and the phone stuck on htc silver logo....i can't get into bootloader but fastboot commands works...can anyone help me???

booster70 said:
hi...i need help!i was flashing an ruu on my htc one X and in the middle of the update it says error 152 and the phone stuck on htc silver logo....i can't get into bootloader but fastboot commands works...can anyone help me???
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main

Thant said:
Give the result from command fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 4.19.708.2

booster70 said:
version-main: 4.19.708.2
Click to expand...
Click to collapse
No RUU for your base it is to newer you must restore nandroid backup if you want stock rom or install custom rom for this you receive Error 152.

Thant said:
No RUU for your base it is to newer you must restore nandroid backup if you want stock rom or install custom rom for this you receive Error 152.
Click to expand...
Click to collapse
Can you please give me a link which describe the way i can do it please??

booster70 said:
Can you please give me a link which describe the way i can do it please??
Click to expand...
Click to collapse
This is the PHILZ 5.15.9 download take the recovery.img from adchive and paste it in you fastboot folder. After this go in bootloader choice fastboot and connect the phone to computer run the command fastboot flash recovery recovery.img and then fastboot erase cache then go in recovery. For nandroid backup look in general section

i will try and tell u...thks

Thant said:
download take the recovery.img from adchive and paste it in you fastboot folder. After this go in bootloader choice fastboot and connect the phone to computer run the command fastboot flash recovery recovery.img and then fastboot erase cache then go in recovery. For nandroid backup look in general section
Click to expand...
Click to collapse
i tried to flash the recovery and it failed...its says
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.253s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.465s

booster70 said:
i tried to flash the recovery and it failed...its says
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.253s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.465s
Click to expand...
Click to collapse
are you unlocked your bootloader via HTCDEV.COM? If no and you have warranty send it for repair if no warrant unlock it and flash the recovery

Thant said:
are you unlocked your bootloader via HTCDEV.COM? If no and you have warranty send it for repair if no warrant unlock it and flash the recovery
Click to expand...
Click to collapse
No warranty....i will try to unlock it and feed back

booster70 said:
No warranty....i will try to unlock it and feed back
Click to expand...
Click to collapse
i tried to unlock bootloader but when i do fastboot oem get_identifier_token it shows nothing

booster70 said:
i tried to unlock bootloader but when i do fastboot oem get_identifier_token it shows nothing
Click to expand...
Click to collapse
copy the command exactly like in htcdev.com copy and paste in your cmd windows try you must unlock your bootloader
when you run the command you must to see numbers in your CMD window

Thant said:
copy the command exactly like in htcdev.com copy and paste in your cmd windows try you must unlock your bootloader
when you run the command you must to see numbers in your CMD window
Click to expand...
Click to collapse
i did exactly like you said but its the same nothing appears

booster70 said:
i did exactly like you said but its the same nothing appears
Click to expand...
Click to collapse
try different cable or different port or different windows
if you can't unlock the bootloader we can't do anything

Thant said:
try different cable or different port or different windows
if you can't unlock the bootloader we can't do anything
Click to expand...
Click to collapse
i tried with a toolkit and i have unlocked it....but i can't flash the recovery it always fails!then i have done
Code:
fastboot oem boot
and it boot in bootloader but the only option is ruu,no recovery no fastboot,none of the things that are there normally....i see my hboot version and it was 0.95 i want to ask if i tried and flash another hboot would it work???the ruu i was flashing and have that problem is RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
i downloaded another jb ruu and they all refused to flash..so what can i do??

booster70 said:
i tried with a toolkit and i have unlocked it....but i can't flash the recovery it always fails!then i have done
Code:
fastboot oem boot
and it boot in bootloader but the only option is ruu,no recovery no fastboot,none of the things that are there normally....i see my hboot version and it was 0.95 i want to ask if i tried and flash another hboot would it work???the ruu i was flashing and have that problem is RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
i downloaded another jb ruu and they all refused to flash..so what can i do??
Click to expand...
Click to collapse
please post result from command fastboot getvar all and delete your S/N and IMEI from the info!?!? You can't be with hboot 0.95 and main version 4.19.708.2 that is inposible and post a picture on your bootloader
and you must to be in fastboot to flash recovery volume down + power button and you are in bootloader take a picture and post it here after this give the info from the command and we will see what will do

Thant said:
please post result from command fastboot getvar all and delete your S/N and IMEI from the info!?!? You can't be with hboot 0.95 and main version 4.19.708.2 that is inposible and post a picture on your bootloader
and you must to be in fastboot to flash recovery volume down + power button and you are in bootloader take a picture and post it here after this give the info from the command and we will see what will do
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.
(bootloader) version-baseband: 1.1204.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.708.2
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(bootloader) devpower: 94
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.822s
and here is the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.casimages.com/img.php?i=140830083217934400.jpg

booster70 said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.
(bootloader) version-baseband: 1.1204.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.708.2
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(bootloader) devpower: 94
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.822s
and here is the image
http://www.casimages.com/img.php?i=140830083217934400.jpg
Click to expand...
Click to collapse
Are your bootloader say S-OFF???? And are you Endeavoru XE or PVT??? you can see this in your bootloader
If the answare on the 1 question is YES then download this RUU relock the bootloader and run the RUU as administrator
but if the answare on 2 question is XE then we must to do something before run RUU

Thant said:
Are your bootloader say S-OFF???? And are you Endeavoru XE or PVT??? you can see this in your bootloader
If the answare on the 1 question is YES then download this RUU relock the bootloader and run the RUU as administrator
but if the answare on 2 question is XE then we must to do something before run RUU
Click to expand...
Click to collapse
I solved the problem by doing
fastboot erase cache
fastboto oem rebootRUU
fastboot flash zip rom.zip
i used the rom.zip inside the ruu i was trying to flash and it passed now the phone turn on but there is another problem.the touhscreen is not responding

booster70 said:
I solved the problem by doing
fastboot erase cache
fastboto oem rebootRUU
fastboot flash zip rom.zip
i used the rom.zip inside the ruu i was trying to flash and it passed now the phone turn on but there is another problem.the touhscreen is not responding
Click to expand...
Click to collapse
I know answare on my question your hboot is too old must be newr. Please answare on my question
And now what version is your hboot the same 0.95

[Q] HTC one M8 (dual sim) stuck on bootloader! What can I do?

Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!

Flash it again via adb, the flashing command must be executed twice.

I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!

Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.

Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!

Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(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: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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.017s

Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(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: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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.017s
Click to expand...
Click to collapse
Delete the IMEI.

OP - Do you want it back to Sense?

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.

Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...

EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.

We should be able to sort things out, but I'll need to get to a proper PC and get links together

EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!

OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!

EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.

I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!

The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you

At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?

Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.

My M9 Bricked please Help

Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.

I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help

freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.

computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much

Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.

my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?

If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.

shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.

freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.

obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.

freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s

freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?

blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.

is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s

freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?

sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.

HTC M9 Got encrypted... Please i need help

Hello,
I got on my phone a very ni message, Your HTC is encrypted... You have 30 attemps to unlock your phone with a code or device data will be removed.
There was a button "Factory Reset" i have try this button and after a Hour nothing happend. I hold the power button and i can restart or Shutdown my Phone...
I think this is a Malware. I have try to Flash a new RUU but nothing help.. i have try it with "Fastboot oem rebootRUU" but what i only got was a boot loop. I have a custom Recovery on my phone (Team Win Recovery Project)
i have try to Format Data and Factory reset but i only got: Unable to mount Data..and more
I have try it to reboot over TWRP an he says "No OS installed , want to reboot?"
Did anybody know what i can do now?
Here are some Device Data:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226066******
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP102
all:
finished. total time: 0.027s
Click to expand...
Click to collapse
Thanks for Help

Flash the stock firmware via SD card method. You will lose all data. You can flash 3.35.161.x firmwares.. Do not lock bootloader or s-on.

shivadow said:
Flash the stock firmware via SD card method. You will lose all data. You can flash 3.35.161.x firmwares.. Do not lock bootloader or s-on.
Click to expand...
Click to collapse
I have try it before, but i get a Blackscreen and a white HTC logo is flashing. But i will try it again. Thanks for Help