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] need to go to stock htc one x for warrenty

Hi all,
I have the following problem. I have een htc one x with venom rom but sinds yesterday the touchscreen won't work anymore. I tried to reinstall and delete all but still it won't work. So I think I'll have to send it back to the factory. But now the following problem occur everytime i try to install the ruu I get an arror message Error [132] signature error.
my cid is E__11 i tried many different .....401.... but all have the same problem.
my carrier is vodafone
unlocked using the def page S-ON
Please help!
Kind regards

Get me the main version number with this fastboot command
Fastboot getvar version-main

That is 1.29.401.11

Cool !
Download this file :
http://bugsylawson.com/files/file/1...12-radio-2120413520-release-274900-signedexe/
* put the phone in the bootloader and relock the bootloader with this command
Fastboot oem lock
* keep the phone in the locked bootloader and run the 2.17.401 ruu.exe with admin rights. Right click the ruu.exe and select " run as administrator "
It will flash the phone back to stock. Stock software, kernel and recovery. If the screen works after this (maybe) you can even update via the phone update menu to 3.14 jellybean and also all the way up to 3.20 software.
* Note : make a backup of the things you want to keep. If still possible. This will wipe the phone (data,contacts)
Succes !

Thanks but now i got an new error
error[152] image update error
what should i do next?

packman89 said:
Thanks but now i got an new error
error[152] image update error
what should i do next?
Click to expand...
Click to collapse
okey I tried it few more times and now i have a full green bar when the error [152] message pops up.
but when i try to restart the phone its stuck at the white grey htc letters and black background I thank it is the download mode.
im getting worried that my one x is died...

Okey i tried the following of user tomascus
run the RUU again but this time don't click next, instead:
Go to C:/Users/(Yournamehere)/AppData/Local/Temp
- search for "rom.zip" file
Copy it to your fastboot folder
Remember to relock your device before running an RUU! To do this from the HTC screen, type: "fastboot reboot-bootloader" and then
type 'fastboot oem lock'. To go back to the HTC logo, type: 'fastboot oem rebootRUU'
Then, on the HTC screen, use fastboot to flash the rom.zip file: "fastboot flash zip rom.zip"
This might take awhile and might fail once, but be patient and try again if it fails
After installation it most likely won't appear to do anything and in that case, type: "fastboot reboot"
my cmd looks like this.
C:\Android\fastboot>fastboot flash zip rom.zip
sending 'zip' (577161 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) Your memory size = 29820MB, choose rawpt_32g.img
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) Start to update BCT ...
(bootloader) Looking for filename bct.img ...
(bootloader) BCT filename : bct.img
(bootloader) Prepare BCT ...
(bootloader) bct size = 6128
(bootloader) Replace bct in Iram done.
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]WP,hboot,50
(bootloader) signature checking...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) start image[system] unzipping & flushing...
(bootloader) Format partition APP done
(bootloader) [RUU]WP,system,5
(bootloader) [RUU]WP,system,11
(bootloader) [RUU]WP,system,18
(bootloader) [RUU]WP,system,25
(bootloader) [RUU]WP,system,32
(bootloader) [RUU]WP,system,39
(bootloader) [RUU]WP,system,46
(bootloader) [RUU]WP,system,53
(bootloader) [RUU]WP,system,60
(bootloader) [RUU]WP,system,67
(bootloader) [RUU]WP,system,74
(bootloader) [RUU]WP,system,81
(bootloader) [RUU]WP,system,87
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,100
(bootloader) start image[userdata] unzipping & flushing...
(bootloader) Format partition UDA done
(bootloader) [RUU]WP,userdata,18
(bootloader) [RUU]WP,userdata,79
(bootloader) [RUU]WP,userdata,100
(bootloader) start image[spl] unzipping & flushing...
(bootloader) Format partition SP1 done
(bootloader) [RUU]WP,spl,100
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) ERROR enable flash mode attn time out
(bootloader) unzip and update fail, error code : 6
(bootloader) start image[wlan] unzipping & flushing...
(bootloader) Format partition WLN done
(bootloader) [RUU]WP,wlan,100
(bootloader) start image[pg3] unzipping & flushing...
(bootloader) Format partition PG3 done
(bootloader) [RUU]WP,pg3,100
FAILED (remote: 51 partition update fail)
finished. total time: 282.763s
but still no luck

Try the 1.29.401 ruu wich you can download from here
http://forum.xda-developers.com/showthread.php?t=2189048

Mr Hofs said:
Try the 1.29.401 ruu wich you can download from here
http://forum.xda-developers.com/showthread.php?t=2189048
Click to expand...
Click to collapse
YEs that worked :laugh:
only my touchscreen still doesn't work tho:crying:. Is there a way to check if the stock software, kernel and recovery are back to stock? I want to now for sure before I'll send it back to the factory.
Also I noticed that in the bootloader it says relocked instead of locked is this going to be a problem for warrenty?
Thanks so much so far I'm verry happy :laugh:

Well no we cant make it "locked" the ruu takes care of everything. You are as stock as you can get now !
Shame your screen does not work. If its hardware related they should replace the screen/digitizer !
Good luck, i hope you will be served well

Mr Hofs said:
Well no we cant make it "locked" the ruu takes care of everything. You are as stock as you can get now !
Shame your screen does not work. If its hardware related they should replace the screen/digitizer !
Good luck, i hope you will be served well
Click to expand...
Click to collapse
Hello again,
New day new problem
the batterie depleted last night and when i was charging my phone and restarted it it didn't came past the blackscreen with the grey htc logo.
I thought it was fixed yesterday because i could start the phone whitout any problems.
I did still had the [152] image update error. But because the phone worked and everything seemed to be on stock again i didn't paid any attention to that any more.
should i fix this first or can i just send the phone back because i assume everything is on stock anyway.
and how do i fix this
I can't go into bootloader mode but fastboot comands do still work. Iff it type fastboot reboot-bootloader it just goes to the blackscreen with grey htc letters again.

Weird indeed, try this
Fastboot erase cache
Then try to reboot again to the bootloader. Otherwise its defo a htc warranty/repair issue

when trying to reinstall the rom with cmd fastboot i get an 44 hboot version check fail.
if i remember correctly hboot was 00.95.00.000 when i could get into the bootloader

Did you install an official ota maybe to 2.17.401 ? Check the hboot if possible, or perform this command again
Fastboot getvar version-main

Mr Hofs said:
Did you install an official ota maybe to 2.17.401 ? Check the hboot if possible, or perform this command again
Fastboot getvar version-main
Click to expand...
Click to collapse
getvar is still 1.29.4.11
I tried 1.29.4.12, 1.29.4.11, and the ruu you gave me.
if ota means updating true phone i can not do this because the touchscreen doesnt work..
can you check hboot truew fastboot ?
and can somebody please fix my 5 min waiting lim

Can you speculate what will happen iff i send my phone to htc in his current stage? Wil they fix it or are they going to charge me?
I definatly find it a little strange. I have this phone for 10 months now and when i got it i installed the venom rom instantly without having any issues or problems 10 months later the touchscreen dies and going back to stock is verry difficult somehow....

packman89 said:
Can you speculate what will happen iff i send my phone to htc in his current stage? Wil they fix it or are they going to charge me?
I definatly find it a little strange. I have this phone for 10 months now and when i got it i installed the venom rom instantly without having any issues or problems 10 months later the touchscreen dies and going back to stock is verry difficult somehow....
Click to expand...
Click to collapse
when you unlock your phone you lose your phones warranty.. so there is a high chance you will be charged for repairing.. and did u make a full nandroid backup before installing venom rom??

daninantro said:
when you unlock your phone you lose your phones warranty.. so there is a high chance you will be charged for repairing.. and did u make a full nandroid backup before installing venom rom??
Click to expand...
Click to collapse
My phone is S.ON and unlocked by def website. the phone is relocked now so I should not have any warrenty problems when stock. Yes i did a full nandroid backup and kept it save on my computer that crashed in december.

packman89 said:
My phone is S.ON and unlocked by def website. the phone is relocked now so I should not have any warrenty problems when stock. Yes i did a full nandroid backup and kept it save on my computer that crashed in december.
Click to expand...
Click to collapse
Oh that is sad! Your phone has a RELOCKED bootloader.. Htc people will see that relocked and then you will have to pay for your repairs! It doesn't matter that your phone is s-on, your phones warranty is gone.. Htc people see for LOCKED status in your bootloader for warranty. RELOCKED/UNLOCKED bootloader=warranty void

daninantro said:
Oh that is sad! Your phone has a RELOCKED bootloader.. Htc people will see that relocked and then you will have to pay for your repairs! It doesn't matter that your phone is s-on, your phones warranty is gone.. Htc people see for LOCKED status in your bootloader for warranty. RELOCKED/UNLOCKED bootloader=warranty void
Click to expand...
Click to collapse
F me... That's stupid because it's not my fauld the touchscreen broke down.. It just doesn't respond anymore and that has nothing to do with a rom change or whatever i used this rom for more then 10 months without any problems. The rom problems started when i wanted to go back to stock...
This is a hardware problem not a software problem or am i seeing this wrong?
Mr.. hoffs what do you have to say about this?

HOX is givng me a major headache! need help!

i have a HOX and it came to me in fastboot mode only! it has the latest OTA version on it and my customer says he tried to download some applications and due to battery voltage low the phone went dead and now it just goes to fastboot mode only! i
it had custom recovery and was bootloader unlocked earlier and it also had a CWM backup in it! but the phone never let me restore the backup always gave an error about mckop1 error! i think something with partitions!
so i relcoecked it and i tried to flash a lot of RUU but they give error when i try to flash thru RUU method! pls find below the whole log and the errors ive come across while trying to flash this phone!
"
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.3
(bootloader) serialno: SH24xxxxxx25
(bootloader) imei: 359188047xxxxx4
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3739mV
(bootloader) devpower: 27
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.855s
"
this are the errors i face when trying to update'
"
sending 'zip' (669375 KB)...
OKAY [ 78.800s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) time: 4014
(bootloader) rom parsing finish ...
(bootloader) Your memory size = 29820MB, choose rawpt_32g.img
(bootloader) Read zipped android_info fail!
FAILED (remote: 22 loading zip info fail)
finished. total time: 83.373s
E:\One_X_All-In-One_Kit_v2.5\One_X_All-In-One_Kit_v\data>"
"
can some expert guide me how to revivve this phone?
WBR
ReTech.

I will have a go at it ! You know fastboot commands ?
In steps
1: download this file and rename it to recovery.zip and copy it to the fastboot folder on the pc
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
2: Open a command window inside the fastboot folder on the pc and flash the recovery
Fastboot flash recovery recovery.img Fastboot erase cache
3: Then enter the recovery and connect the hox to the main charger. It will charge the battery......start with that !
You still have the backup on the sdcard ?
Inside recovery do this :
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache, data and system
Then go into the backup and restore menu and restore the backup !
Reboot the phone after that. If its not booting after ~7 min max you have to flash the boot.img from the nandroid backup

Mr Hofs said:
I will have a go at it ! You know fastboot commands ?
In steps
1: download this file and rename it to recovery.zip and copy it to the fastboot folder on the pc
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
2: Open a command window inside the fastboot folder on the pc and flash the recovery
Fastboot flash recovery recovery.img Fastboot erase cache
3: Then enter the recovery and connect the hox to the main charger. It will charge the battery......start with that !
You still have the backup on the sdcard ?
Inside recovery do this :
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache, data and system
Then go into the backup and restore menu and restore the backup !
Reboot the phone after that. If its not booting after ~7 min max you have to flash the boot.img from the nandroid backup
Click to expand...
Click to collapse
hi tks for replying! but i get this error when iam trying ti flash the recovery!
"
sending 'recovery' (8050 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.293s
E:\One_X_All-In-One_Kit_v2.5\One_X_All-In-One_Kit_v\data>"
now what to do?
WBR
ReyTech.

Unlock the bootloader !

Mr Hofs said:
Unlock the bootloader !
Click to expand...
Click to collapse
thanks! i did as u mentioned and then installed android revoluton HD rom thru "mount usb" and then the phone started fine! the touch doesnt seems to work but i guess it is hardware problem!
anyway thanks again for your help!
and this philz recovery is simply great!
WBR
ReyTech.

Does touch work in the recovery ? Link to the exact rom please. Would like to crosscheck.....

I will do it tommorow, the touch doesn't work coz of rom, and now I cant conndct to the phone to my system thru adb sideload or thru mount usb storage as they both get selected but the phone doesn't get detected, what could be tje the reason, pls inform!
Wbr
Reytech
Sent from my GT-N8000 using Tapatalk

[Q] Any way to unlock a bootloader again (currently showing "relocked")

So I am new to the posting aspect of xda but have been around checking out other peeps info for a while. Basically I've gotten into a weird situation, and have no idea now how to fix it. Sorry if there is already a thread for this issue, but I have been looking for 2 days, and decided I was in over my head.
I have a HTC One M7 Verizon (blue Best Buy model) which I got AFTER HTCDev had locked Verizon from unlocking bootloader via their website.
One a exploit was found to unlock the bootloader and gain root, I jumped and ran through the process using a CWM recovery and a Cyanogenmod as my ROM. Everything was peachy until a few days ago when an update, auto updated over night, and created a problem where my phone would reboot show the lock screen, but when I swiped up to unlock it, the green HTC came back up and eventually the thing would reboot.
So I started looking around to see what other ROM's were out there at the moment and flashed ViperOne, all was well, updated my radio, firmware, and such. However, every-time my phone would go into a regular boot after setting up the ViperOne ROM, it would freeze.
So desperate for a fix I hurriedly wiped the system, used CWM recovery to reinstall the stock rom.
Upon doing this I decided I should take advantage of the stock status of the phone and get the OTA's. This is where I became stupid!!!!!
Apparently doing such a thing re-locks your bootloader. Since I wiped the system SU was not longer installed and I lost root as well. Now I cannot issue ANY fastboot FLASH commands from my adb/fastboot CMD.
HELP, pretty, pretty please!!!
I really don't like sense at all, and think that Blinkfeed is the largest piece of #[email protected]*&^% I have ever seen.
Thanks in advance for even reading!
***Edit***
Forgot to mention what's currently running on my phone:
Build/OS: 4.3 JB CL278010 2.10.605.1
Kernal: 3.4.10-g40851b1
[email protected] #1
Baseband v. (Radio) : 1.12.41.1112_2
Basically stock jelly bean, used a stock RUU version flashed via fastboot flash command. Once phone rebooted with stock then applied the 2 previous OTAs I had missed coming from 1.10.605.10 (4.2)

Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?

cmlusco said:
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
Click to expand...
Click to collapse
Yes I am still s-off, thank goodness!
I just can't get any flash commands to work, even in oem rebootrRUU.
I can try going through the process your suggesting and see if it works, will update with results.

What errors do you get when trying fastboot cmds?

"What errors do you get when trying fastboot cmds?"
Once I am in bootloader and go into fasbootusb this is what I have tried:
fastboot oem rebootRUU (phone flashes and comes up with the silver HTC on the screen)
Send the command for recovery:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8786 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.199s
If I try to flash a zip:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip superuser.zip
target reported max download size of 1526722560 bytes
sending 'zip' (4538 KB)...
OKAY [ 0.697s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.972s
It will respond (obviously) when I give it:
fastboot reboot-bootloader
But am not able to enter any adb commands as there isn't a recovery installed!!
Here is the info from the phone:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxx
(bootloader) imei:xxxxxxx
(bootloader) meid:xxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
The fastboot system will let me do things like, change my CID from VZW_01 to a super CID11111111 and back again, no errors, but not sure how much help that is...
I worry about trying to flash a new RUU because I can't back anything up right now....also just to be sure I heard I shouldn't upgrade further to Kit-Kat as there isn't a unlocked bootloader exploit yet...correct? (Obviously if I was still unlocked, and not relocked it wouldn't be an issue)
Click to expand...
Click to collapse

Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.

cmlusco said:
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
Click to expand...
Click to collapse
YAY!!!! That worked
:good:
Thank you for all of your help!! I really appreciate it, I knew there was probably a way to get a custom recovery installed, I just had run out of plays in my own knowledge book!!
I will now be able to do a nandroid b/u and get rid of the stupid sense Blinkfeed, belch! lol

[Q] HTC One M8 won't boot.

Some one please help me.
I have the HTC One M8 which I updated to Android 5.0.1 through OTA updates about 2 weeks ago.
Yesterday, I successfully unlocked the bootloader and rooted my device. I also have the TWRP Recovery v.2.7.0.2 installed.
Everything was working fine until after the root when I noticed that the internal storage had some kind of write protection on it. Like even the default "DCIM , ANDROID, Downloads etc... folders weren't there". I discovered the write protection on the internal storage when I tried to download a file using Chrome on the phone and it replied with "No SD Card".
Funny thing is apps from the Play Store were installing perfectly fine.
So I booted back into TWRP recovery and did a factory reset thinking I must've messed up while rooting.
After the factory reset when I try boot up my phone the Setup Wizard constantly crashes so I can't do anything.
My HTC One M8 is the international variant Model: 0P6B100.
Someone please help

1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard

ckpv5 said:
1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard
Click to expand...
Click to collapse
I installed TWRP 2.7.0.2 using All in one tool v2.0 by Hasoon2000. The tool needs usb debugging to be turned on which I can't turn on because I can't get past the setup wizard because it keeps crashing.
Is there a way to install it manualy using fastboot?

I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned

ckpv5 said:
I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned
Click to expand...
Click to collapse
Okay I got my serial number. Now what do I do with it?

bolajiibrahim7 said:
Okay I got my serial number. Now what do I do with it?
Click to expand...
Click to collapse
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.

ckpv5 said:
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.
Click to expand...
Click to collapse
I did that. Then it started the "Android is upgrading - Optimizing apps splash.
After that I'm back to the Setup Wizard which keeps crashing.

Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)

ckpv5 said:
Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)
Click to expand...
Click to collapse
My software version is 5.0.1 Lollipop.
I don't have a stock backup. RUU is my only option.
Here's my fastboot getvar all
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\adb>

I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.

bolajiibrahim7 said:
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.
Click to expand...
Click to collapse
You don't need S-Off to run RUU, relocked bootloader before run RUU. Read thru that thread, there are many discussion.
Read this, this guy also doesn't have S-Off device : http://forum.xda-developers.com/htc-one-m8/help/one-m8-htc001-cid-firmware-wifi-problem-t3031656 and he managed that.
Or just restore backup that linked to you if you don't feel to relock bootloader.
You need to read all those thread. Without reading, this is going no where .. good luck

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
What does RUU mean? and how do I use it?
Also does applying RUU restore my phone to the way it was before root as in With Android 5.0.1 and Sense 6.0?

RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.

ckpv5 said:
RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.
Click to expand...
Click to collapse
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s

bolajiibrahim7 said:
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s
Click to expand...
Click to collapse
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot

Thank You.
ckpv5 said:
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot
Click to expand...
Click to collapse
Thank you so much for your help. My phone is now on Lollipop and rooted and working fine.

Kinda in the same problem...
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43TWM0xxxx
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
TWRP 2.7.0.1 - I know it's old and buggy but flashing a newer one, even though it flashes ok, it wont load.
The phone is Tampered - Unlocked with S-On
After unlocking and flashing TWRP, I flashed custom ROM MaximusHD, it worked but as I didnt that it needed newer firmware, wifi wasnt working, tried to restart the phone and it entered in a boot loop.
Then flashed: http://forum.xda-developers.com/showthread.php?t=2699186
But it wont boot...
Could you please help me?
Thanks in advance

macdo said:
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version-bootloader: 3.16.0.0000
product: m8_ul_ca
modelid: 0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)

Thanks for the fast answer, I'll it and report back!
---------- Post added at 02:20 PM ---------- Previous post was at 02:16 PM ----------
ckpv5 said:
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)
Click to expand...
Click to collapse
After fastboot oem lock, I got this:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.139s
And rebooted to bootloader now, it says:
Tampered
Relocked
Security Warning
Is it ok? (btw, im downloading ruu)
Thank you so much!