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] Stuck in fastboot and no connections in ADB

Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi

ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.

riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?

Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app

elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?

PLS can anyone help me ? :crying:

themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?

FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.

FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..

HTC One M9 bricked..

Hey..
I bricked my HTC One M9... I was using a custom rom for three months and I wanted to flash a new rom. But it didnt work. Then i used the "Format Data" function in TWRP. Now it shows 0MB internal storage all the time. Then I tried to flash a Nandroid Backup of mine. After I restored it says "succesfull". When I try to reboot it is stuck in the HTC Boot screen (This build is for development purposes only...bla...bla..). So I tried to use the 0PJAIMG.zip. But when I try to get into the download mode it doesnt work. It just restarts the HTC download mode screen. So I tried to get into the download mode trough the bootloader. It went succesfull. But when it tries to flash the 0PJAIMG.zip it tries to reboot into the download mode again.. But then its stuck into this kind of stupid "boot loop" (SD-Card=FAT32). Also flashing with Fastboot doesnt work. If I try to flash a new recovery it just doesnt change anything. It's still same TWRP 3.0.0.2.. I have no ideas anymore... It's unlocked and s-on.. Thats why I couldn't flash the custom rom.. All of these roms I tried to flash after this accident were signed by HTC and should work fine with my phone (3.35.161.12 OS version, Stock-Rom version: 3.35.161.12).
Here is some info from "Fastboot getvar all":
c:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226069******
(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.012s

When you get into download mode do you see the prompt at the bottom of the screen that says whether the file (opjaxxx.zip)is there or not?. Name the file the same as what it is looking for.. If it just dies then you have a bigger problem..
Beamed in by telepathy.

I have a redmi note 4 and I'm not able to flash anything.my internal storage shows0mb
I have a redmi note 4 and I'm not able to flash anything.my internal storage shows 0mb. please help.

Troubles with going back to stock with S-OFF and unlocked Bootloader?

Well first of all heres the information:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 4.18.111.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
What happened?
I tried to flash twrp recovery and supersu, which actually broke my phones ability to recognize the Sim card (IMEI not showing up).
Well i tried to flash several roms (downgrade, upgrade and even the same version-main), yet i always encountered the FAIL12 ZIP error..
My phone is currently factory reset, twrp installed and well im unable to flash anything with it right now.
Does someone have some solutions? I tried the 3.35 ruu from the FAQ thread, tried some 2.x.x ruus, 4.28 ruus and latest one i got was this: 0PJAIMG_HIMA_UHL_N70_SENSE80_MR_TMO_DE_4.18.111.2_R_Radio_01.01_U114401011_117.00.61117G_2_F_release_498250_signed_2_4.zip
EDIT: I did change the CID TO 102 (standard german) from TMOBO 101
Help me out, please
Thanks in advance

As you've changed the cid you can only flash a firmware compatible with the new cid, the same version as what you already have. So the firmware you are trying to flash is the right version, wrong cid/sku. Currently your on tmobile fw with a cid that doesn't belong.
When you bugger a phone by flashing it unknowing what you are doing the best option is to flash to stock and start again.
When you have the firmware you need just copy it to the external sd card and rename it to 0PJAIMG.ZIP (0=zero, not o!), boot into download mode and you should have "press vol up to flash" in yellow at the bottom of the screen. Press vol up...

Problem resetting phone.

Hi, I need a little help getting my phone to work - I have the same issue as on this thread: https://forum.xda-developers.com/htc-10/help/black-screen-oreo-update-t3757142
However I can't seem to connect via adb and I'm guessing this is because I don't have developer options enabled?
Here is the fastboot getvar all results:
C:\Users\Home>C:\Users\Home\Desktop\platform-tools\fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA65TBN01081
(bootloader) current-slot:
(bootloader) imei: 3575xxxxxxxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: 11111111
There is a little difference between mine and his issue though, I couldn't check for update as it said something about possible corruption at which point I did a factory reset and immediately the screen when dead after doing so. I contacted htc for help after and wasn't anything they could do as the phone is out of warranty.
The only idea I have would be to use a keyboard to enable usb debugging and I can then try rooting and flashing via adb once that is done?
This video is kinda what I want to do although the steps would be different: https://www.youtube.com/watch?v=741MqF5uQDw
If somebody could provide me the steps needed I would really appreciate it, or give me advice on an alternative option to flash my device I would be incredibly grateful.
Thanks in advance.

Download the 2.41.401 ruu.zip, rename it to 2PS6IMG.zip and copy it to the root of the SDCARD. Boot to download mode and confirm to flash it.
After that the device is back to stock and you can update to Oreo if you wish.
ADB only works in TWRP recovery, in a running OS. Bootloader and download mode only work with fastboot commands.

Thanks, that helped but still black screen, perhaps the screen just died and the reset was a coincidence.
Mr Hofs said:
Download the 2.41.401 ruu.zip, rename it to 2PS6IMG.zip and copy it to the root of the SDCARD. Boot to download mode and confirm to flash it.
After that the device is back to stock and you can update to Oreo if you wish.
ADB only works in TWRP recovery, in a running OS. Bootloader and download mode only work with fastboot commands.
Click to expand...
Click to collapse