Develop Bugs

How To Update Your HBOOT On CustomROM

ARE YOU ON A CUSTOM ROM TRYING TO UPDATE YOUR HBOOT FOR THE JELLYBEAN ROMS ? WELL HERE ARE THE STEPS
PS : I'M ONLY POSTING THIS BECAUSE SOME PEOPLE ARE SAYING YOU SHOULD BE ON AN ORIGINAL RUU TO UPDATE HBOOT
REQUIREMENTS :
1. The new HBOOT zip provided by Baadnewz or Football
2. PC/Mac/Linux with fastboot files
3. The Jelly Bean ROM file copied to your phone
4. Courage and patience. :highfive:
LET'S START :
1. First lock your One X with the command : fastboot oem lock
. You might get errors on the fastboot command line but that's nothing
2. The phone should reboot to HBOOT with a "RELOCKED" status and "SECURITY WARNINGS" under it. You might not get "SECURITY WARNINGS" but that's nothing.
3. Go into RUU MODE (Yes I said RUU mode on CustomROM) by typing in fastboot mode in the bootloader : fastboot oem rebootRUU and wait about 15 seconds
4. Flash the new HBOOT .zip file with : fastboot flash zip (the name of the zip file).zip
Example : fastboot flash zip firmware.zip
(If you get an error the first time. Flash again it will work)
5. When the process is done exit RUU mode by typing : "fastboot reboot-bootloader" and then re-unlock the bootloader of your device. If you forgot how to just follow the OneXRoot.com steps again.
6. Flash custom recovery again. (pretty much ClockWorkMOD)
7. Flash boot.img of the Jelly Bean ROM.
8. Go into recovery and flash that Jelly Bean ROM
9. Have fun with Jelly Bean
UPDATE : DUE TO A REQUEST, HERE ARE THE CIDs WORKING WITH THE HBOOT UPDATE :
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15

hi
assuming u have done the same and u have flashed the new JB provided by our developer
thanks again for the same:good::laugh:

It works with branded phones?
Because my CID is ORANG202.

Thank you very much!
I have been trying for the whole day until I read this post!
I was missing step #3

Does it work with CID: O2___102 ???
Sent from my HTC ONE X using xda premium

Hey, I'm at step 5 now, trying to re-unlock, but I can't do the following step:
fastboot flash unlocktoken Unlock_code.bin
I keep getting ''sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s''
What's going wrong?
edit: nevermind lol, bootloader was just stuck for some reason, a reboot fixed it

branded phones JB does not work..wait for the official OTA by the network providers

J-city just a bit of advice I think you need to add the cid's off which it will work on as people will get confused. I been branded no i cant upgrade but as goku said all branded phones will have to wait for out provider to push the ota
Sent from my HTC One X using Tapatalk 2

Followed ur guide and I was updated in no time at all!!
For your first post on xda.... Very helpful!!!
Sent from my HTC One X using xda premium

galaxys2Tav said:
J-city just a bit of advice I think you need to add the cid's off which it will work on as people will get confused. I been branded no i cant upgrade but as goku said all branded phones will have to wait for out provider to push the ota
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Updated the thread : list of CIDs now available.

great, worked like a charm

There seems to be mixed reports so can anyone please confirm that you can still flash a 2.17 sense Rom after updating the hboot? Thanks
Sent from my HTC One X using xda premium

stuart0001 said:
There seems to be mixed reports so can anyone please confirm that you can still flash a 2.17 sense Rom after updating the hboot? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Actually I just restored my venom rom, and gues what all seems to work so far... data/wifi/texting and calling works

stuart0001 said:
There seems to be mixed reports so can anyone please confirm that you can still flash a 2.17 sense Rom after updating the hboot? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You can't till now but I am 100 % there is a workaround

Many people saying I did the same as the Devs did in their tutorials. Actually there are a lot of people stuck in their Bootloaders after re-locking on custom ROMs so there wasn't a way in the Devs tutorial to go straight to RUUmode from bootloader. And that's why I put this thread.

stuart0001 said:
There seems to be mixed reports so can anyone please confirm that you can still flash a 2.17 sense Rom after updating the hboot? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
gffmac said:
Actually I just restored my venom rom, and gues what all seems to work so far... data/wifi/texting and calling works
Click to expand...
Click to collapse
J-CiTy said:
You can't till now but I am 100 % there is a workaround
Click to expand...
Click to collapse
QED :laugh:
Can anyone post if they have actually tried to install a 2.17 IC sense ROM and failed

stuart0001 said:
QED :laugh:
Can anyone post if they have actually tried to install a 2.17 IC sense ROM and failed
Click to expand...
Click to collapse
I have not tried it myself but apparently gffmac says it's working. So he must be right. And why do you need to get back to ICS ? Most of the famous custom roms devs are updating their roms to JellyBean

this is the only way that work for me
I try all dev ways but non is working my cidnum: HTC__001
thank you now I will flash JELLY ROM

salman saso said:
this is the only way that work for me
I try all dev ways but non is working my cidnum: HTC__001
thank you now I will flash JELLY ROM
Click to expand...
Click to collapse
Glad I helped. That was my intention in the first place. The devs tutorial first made my phone boot directly to the bootloader when I re-locked it. I did some researches and said why not share it with you people to help you. That's what xda is for after all

Thank you so much man!
So this method bypasses the need for having the ruu!
Cool!
ViperX Goodness

[Q} Hboot .43 upgrade

I'm going round in circles, trying to work out what I'm doing wrong.
I have hboot 0.43, and a fastboot getvar-main gives me 1.26.707.4
I presently am rooted etc and want to upgrade to JB. I have a nandroid backup of my stock rom. Hboot 0.43 means I cannot upgrade to JB hboot directly.
I restored the backup, flash the boot image from the backup, erase the cache and then flashed the stock recovery (1.29). Reboot. so far so good.
When the phone reboots it tells me there is a system update to 1.28.707.10 (31.82MB). I tell it to download and it says it will.
The problem is the speed. It's been going about 20 minutes so far and it has downloaded 0.15MB!! That's it.
I would try another method, but I can't find an RUU for my phone.
Any help appreciated.

Do fastboot oem readcid
Let us know what cid you have
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
Do fastboot oem readcid
Let us know what cid you have
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry, forgot to add that.
I have HTC_044

liquidguru said:
Sorry, forgot to add that.
I have HTC_044
Click to expand...
Click to collapse
give me a couple of minutes, il just double check which is the correct one and drop it into my FTP server.
il PM you with connection details
OK i have sorted the file you need, details have been sent in a PM.
that is the Jellybean RUU for your CID.
make sure you have a well charged battery
relock your bootloader then run that on your PC and it will bump you all the way up to stock Jellybean

bagofcrap24 said:
give me a couple of minutes, il just double check which is the correct one and drop it into my FTP server.
il PM you with connection details
OK i have sorted the file you need, details have been sent in a PM.
that is the Jellybean RUU for your CID.
make sure you have a well charged battery
relock your bootloader then run that on your PC and it will bump you all the way up to stock Jellybean
Click to expand...
Click to collapse
Fantastic, thanks...it will take me a little while to download, but I'll let you know the results
sent from somewhere

liquidguru said:
Fantastic, thanks...it will take me a little while to download, but I'll let you know the results
sent from somewhere
Click to expand...
Click to collapse
No problem
wow thats some seriously slow internet, are you only on a 1MB line

bagofcrap24 said:
No problem
wow thats some seriously slow internet, are you only on a 1MB line
Click to expand...
Click to collapse
I live in the middle of nowhere in the middle of Indonesia. An exceptionally beautiful place and I'm pretty lucky to have any internet , so can't complain about the speed to much...at least it works.
sent from somewhere

Ok, no luck.
Relocked bootloader, no probs.
When I run the RUU it start ok, but when it gets to updating the signature I get:
ERROR [132]: SIGNATURE ERROR
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
So, what to do next?

Did u update your bootloader? U have same cid as me... Your bootloader should show 1.36...then you can flash JB ruu...
Sent from my HTC One X using xda app-developers app

liquidguru said:
Ok, no luck.
Relocked bootloader, no probs.
When I run the RUU it start ok, but when it gets to updating the signature I get:
ERROR [132]: SIGNATURE ERROR
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
So, what to do next?
Click to expand...
Click to collapse
could be a bad download, did notice a few disconnects as you was downloading it from me.
found another link here
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_296434_signed.exe
100% that its the correct RUU for your device
Code:
modelid: PJ4610000
cidnum: HTC__044
mainver: 3.14.707.24
btype:1
aareport:1
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
delcache: 1
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
audahadi said:
Did u update your bootloader? U have same cid as me... Your bootloader should show 1.36...then you can flash JB ruu...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
running the RUU on HBOOT 0.43 should automatically update the HBOOT to 1.36, but by the sounds of it. He isnt getting that far
usually the signature fail is either because
1. Wrong RUU
2. Bootloader Still Unlocked
3. Corrupt Download

I don't think there is anything wrong with the download. I use a download manager, so it can handle disconnects.
Hboot still says 0.43
I think the problem may be that I need to update to an intermediate hboot first. So I need an RUU for Hboot 1.26 or something. Then from there I can update my hboot
I'm going to try the 1.28.707.10 RUU

liquidguru said:
I don't think there is anything wrong with the download. I use a download manager, so it can handle disconnects.
Hboot still says 0.43
I think the problem may be that I need to update to an intermediate hboot first. So I need an RUU for Hboot 1.26 or something. Then from there I can update my hboot
I'm going to try the 1.28.707.10 RUU
Click to expand...
Click to collapse
im not too sure on that one.
the RUU updates your HBOOT for you
but if you want to try it there is a thread here
http://forum.xda-developers.com/showthread.php?t=1957376
which contains 1.36 HBOOT's which you can flash
lock bootloader
download the one for your phone from thread above (see your CID HTC__044 - x.xx.707.x - Asia WWE (World Wide English))
rename to firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
then you can try the RUU again

bagofcrap24 said:
could be a bad download, did notice a few disconnects as you was downloading it from me.
found another link here
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_296434_signed.exe
100% that its the correct RUU for your device
Code:
modelid: PJ4610000
cidnum: HTC__044
mainver: 3.14.707.24
btype:1
aareport:1
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
delcache: 1
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
running the RUU on HBOOT 0.43 should automatically update the HBOOT to 1.36, but by the sounds of it. He isnt getting that far
usually the signature fail is either because
1. Wrong RUU
2. Bootloader Still Unlocked
3. Corrupt Download
Click to expand...
Click to collapse
Thanks..didn't notice that as before I only update bootloader then straight to custom rom..but worth a try
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
im not too sure on that one.
the RUU updates your HBOOT for you
but if you want to try it there is a thread here
http://forum.xda-developers.com/showthread.php?t=1957376
which contains 1.36 HBOOT's which you can flash
Click to expand...
Click to collapse
That did it i think! Success!! MIUI now booting.
Many thanks for all your help.

going from Hboot 0.43 to 1.36 directly
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:

usmanyo said:
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:
Click to expand...
Click to collapse
1. no
2. not sure but go with the worst case scenario and back it up before !

Mr Hofs said:
1. no
2. not sure but go with the worst case scenario and back it up before !
Click to expand...
Click to collapse
at 1. you said "no", as in it cant be done directly?

No it cant be done directly .... You got that right, the step to a JB hboot s to high !
In your case (from such a low hboot) it need to be done in steps
And about the direct firmware flash im not certain if it works directly but i would not risk it. There is for sure a RUU that fits your hboot. So I would go for safe and install a ruu to get back to stock and then officially ota all the way up to JB !

usmanyo said:
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:
Click to expand...
Click to collapse
Just flash the correct hboot from the post that bagofcrap24 linked to : http://forum.xda-developers.com/show....php?t=1957376
It doesn't erase your data and is a lot easier than trying to find the correct RUU and flashing that.

liquidguru said:
Just flash the correct hboot from the post that bagofcrap24 linked to : http://forum.xda-developers.com/show....php?t=1957376
It doesn't erase your data and is a lot easier than trying to find the correct RUU and flashing that.
Click to expand...
Click to collapse
Your opinion depends completely how familiar the person is with fastboot and commands :thumbup:
And btw, for such a low hboot there is definitely a RUU available

[Q] One X - can´t update to JB. All ICS works.

Hello,
Here´s the problem.
I have here a HTC One X, engineer model. (fully factory unlocked)
The problem is that he has 2.17.401.2 and works OK. But can´t upgrade to any version above.
As he came:
Bootloader Unlocked
Model : ENDEAVORU XC Ship S-Off RH
CID : HTC__001
Hboot - 1.12.0000
CPLD - None
MICROP - None
Radio -
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : disabled
Modem PATH : Off
Tried to update by RUU to 3.14.401.31 (I believe it´s the latest official), but an error came along about image error.
So I manually, updated the HBoot to 1.39.0000, and the RUU update now get´s complete, but the phone restart few seconds after power on. And recovery get´s the same restart cycle.
So, I update to RUU 2.17.401.2 and everything works again.
Changed the CID to 1111111 (supercid)
Flashed again the 3.14 and now he is at this point:
Code:
C:\Fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.39.0000
INFOversion-baseband: 5.1204.162.29
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.14.401.31
INFOserialno: HT21LWxxxxx
INFOimei: 35918xxxxxxxx
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3873mV
INFOdevpower: 60
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
Code:
C:\Fastboot>fastboot getvar version-main
version-main: 2.17.401.2
But at any time, I can downgrade to 2.17 or 1.29 and make it work.
BTW, I also tried other methods... when on 2.17, tried to update by CWM with zip file. Relocked the bootloader, unlocked it again... Tried to restore a nandroid backup from a 3.14.** working unit... but all ended in a restart loop. So always came back to 2.17 and get it working.
I think the problem in this unit remains here:
Code:
INFOmodelid: PJ461****
Should be PJ46100... or PJ4610000
If I try to write it on fastboot
Code:
fastboot oem writemid PJ46100
Command error !!!
Not sure if write model ID is supported on this unit.
Any way of writting the model id? or solve the main issue of not updating to 3.14?
Thank you

The model id was fine, what is the name of the files are you trying to flash and what command you used ?

Vcek said:
The model id was fine, what is the name of the files are you trying to flash and what command you used ?
Click to expand...
Click to collapse
Tried a bunch... RUU 3.14.401.27 / 3.14.401.31, tried install zip by cwm (ROM_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31.zip), tried a nandroid backup form a 3.14.401.31 working unit...
Also tried ota update (OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985n1wwcwzs385c0bvz.zip) by adb... but no sucess.
fastboot oem rebootRUU
fastboot flash zip (ota_file).zip
Came an error saying it android-info.txt file was not found
I´m running out of options...
Thanks

I´m kind in a dead end...
Phone works on all ICS, but if update hboot, and install JB, reboot loop... always, no matter what I do.

Drug_Store said:
I´m kind in a dead end...
Phone works on all ICS, but if update hboot, and install JB, reboot loop... always, no matter what I do.
Click to expand...
Click to collapse
Try twrp to install the rom, or cwm 5.8.4.0
Sent from my HTC One X using xda app-developers app

Vcek said:
Try twrp to install the rom, or cwm 5.8.4.0
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Tried CMW to install zip... flashed, but same result... reboot loop.
Tried to restore a twrp backup from 3.14.401.31, but always end up like this.

why dont you just go back to stock and update through OTA?

robchongke said:
why dont you just go back to stock and update through OTA?
Click to expand...
Click to collapse
If I go back to 2.17, there´s no OTA notify of newer update.
Only if I go to 1.29, then I receive 2.17 OTA notify, install it... but after that no more ota notify.

I am not sure for engineer version, but did you try to do steps like for "normal" One x when you do RUU flash! Need to lock bootloader and in win based systems with administrator control run RUU as administrator, and with phone in fastoboot mode.. I know that's you phone have unlock bootloader and S-Off but try..
And for use of nandroid backup that you mention did you try after flashing backup flash boot.img also..
link to firmware for your CID : http://forum.xda-developers.com/showthread.php?t=1957376, and link for CID match software:http://forum.xda-developers.com/showthread.php?t=2189048

Mis-read, delete please.

hpnxfox said:
I am not sure for engineer version, but did you try to do steps like for "normal" One x when you do RUU flash! Need to lock bootloader and in win based systems with administrator control run RUU as administrator, and with phone in fastoboot mode.. I know that's you phone have unlock bootloader and S-Off but try..
And for use of nandroid backup that you mention did you try after flashing backup flash boot.img also..
link to firmware for your CID : http://forum.xda-developers.com/showthread.php?t=1957376, and link for CID match software:http://forum.xda-developers.com/showthread.php?t=2189048
Click to expand...
Click to collapse
Already tried to flash RUU as Admin, and bootloader locked. But ended up the same... reboot loop.
Can´t recall for sure about flashing boot.img after nandroid backup, but will retry.
Thank you

Same Problem
Drug_Store said:
Already tried to flash RUU as Admin, and bootloader locked. But ended up the same... reboot loop.
Can´t recall for sure about flashing boot.img after nandroid backup, but will retry.
Thank you
Click to expand...
Click to collapse
Hi Drug_Store,
I have same problem. not able to upgrade to JB.
hboot 1.12. Super CID. S-Off. Ver: 2.17.401.2.
Tried all possible things. still no use., boot loop.
Are you able to flash any JB rom apart from RD-MIUI?
http://forum.xda-developers.com/showthread.php?t=1817633

Super CID, not able to upgrade to JB
mods, any inputs on the above?

Having the same issue
I'm having the same issue.
My phone is currently at RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900
but if I try to update it with RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
OTA will download the file fine and wipe the phone, then in the recovery menu (stock) it will reboot after 10 seconds of "installing".
All other RUU's or manual flashes fail and end up in a boot loop.

try to set another CID which is for exmaple from WWE so that it will download for sure the update...maybe it's due to supercid

Didnt work
One-X-master said:
try to set another CID which is for exmaple from WWE so that it will download for sure the update...maybe it's due to supercid
Click to expand...
Click to collapse
Changed cid to HTC__001 & checked with bootloader locked & unlocked. no update available.

vnayrox said:
Changed cid to HTC__001 & checked with bootloader locked & unlocked. no update available.
Click to expand...
Click to collapse
Try factory reset the phone with cid at HTC_001 and try update again

wigankev said:
Try factory reset the phone with cid at HTC_001 and try update again
Click to expand...
Click to collapse
Yup try that should work ...I just deleted cache and data in all Google things and HTC update thing restarted phone and searched again for and found one...and factory reset should work really, too...
Gesendet von meinem HTC One X mit Tapatalk 2

One-X-master said:
Yup try that should work ...I just deleted cache and data in all Google things and HTC update thing restarted phone and searched again for and found one...and factory reset should work really, too...
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Did factory reset via recovery with cid HTC__001, found no updates

vnayrox said:
Did factory reset via recovery with cid HTC__001, found no updates
Click to expand...
Click to collapse
As long as your on the right Hboot you should be ok flashing ARHD or any other Jelly Bean custom rom of your choice.

Help to find original RUU for HTC One X

Hello all.
A friend of mine has recently asked me for advice about how to RMA his phone due to some serious hardware fault (WiFi network not functioning and lower screen buttons not responding from time to time). It is a second-hand phone, and he has boot unlocked and cyanogenmod installed in it.
I have read that, among the conditions to get a successful RMA from HTC, it is needed to send the phone with the boot locked and an original RUU installed on it.
I have get both the CID and RUU needed through the fastboot command prompt and I would need to find the RUU to match these parameters:
RUU: 3.18.401.1
CID: HTC_203
I can only find either the RUU 3.18.401.1 but for different CIDs, or an older RUU (3.14) matching the area code (401) and CID (HTC_203). I have also read that one cannot flash an older RUU on the phone. Will it brick it?
I have to choose to flash one of this RUUs:
3.18.401.1 CID HTC__032
3.18.401.1 CID HTC__001
3.18.401.1 CID HTC__E11
3.18.401.1 CID HTC__405
Neither of them matches the CID on the phone.
3.14.401.31 CID HTC__203
Or this. This is the newest RUU matching the CID, but is it older than the one originally flashed on the phone.
Could I get any help?
Thanks so much in advance!
PD: Sorry for my English.

You can't run a RUU because there's no ruu for 3.18.401.1 base... You will need to restore this backup:
http://d-h.st/hFn
This is for HTC__E11 but it will work if the base is the same!
PS: Take a backup of the current rom or have a rom.zip in your phone so that if anything goes wrong, you can flash that!

vin4yak said:
You can't run a RUU because there's no ruu for 3.18.401.1 base... You will need to restore this backup:
This is for HTC__E11 but it will work if the base is the same!
PS: Take a backup of the current rom or have a rom.zip in your phone so that if anything goes wrong, you can flash that!
Click to expand...
Click to collapse
Thanks so much for the help! Much appreciated!
I will do it as soon as possible

jfromeo said:
Thanks so much for the help! Much appreciated!
I will do it as soon as possible
Click to expand...
Click to collapse
So, I have extracted the recovery.img and flashed it with:
"fastboot flash recovery recovery.img"
Then relocked the bootloader with:
"fastboot oem lock"
But when I was going to flash the RUU following the tutorial, I have realised that it is not in exe mode, it is a rar and I cannot "right click -> run as administrator" as the tutorial says.
Is there any way I can flash the original RUU to the phone in fastboot mode? Or an alternative RUU X.XX.401.X in exe format?

jfromeo said:
So, I have extracted the recovery.img and flashed it with:
"fastboot flash recovery recovery.img"
Then relocked the bootloader with:
"fastboot oem lock"
But when I was going to flash the RUU following the tutorial, I have realised that it is not in exe mode, it is a rar and I cannot "right click -> run as administrator" as the tutorial says.
Is there any way I can flash the original RUU to the phone in fastboot mode? Or an alternative RUU X.XX.401.X in exe format?
Click to expand...
Click to collapse
That's not a RUU, it's a nandroid backup!
You need to unlock your bootloader, flash this recovery : https://www.dropbox.com/s/p35p0tqf41jbj8b/recovery.img
Then transfer the all the 'files' to /clockworkmod/backup/04-06-2013/. Copy the boot.img to fastboot folder.
flash the boot.img and then go to recovery and wipe everything and then restore the backup!

jfromeo said:
So, I have extracted the recovery.img and flashed it with:
"fastboot flash recovery recovery.img"
Then relocked the bootloader with:
"fastboot oem lock"
But when I was going to flash the RUU following the tutorial, I have realised that it is not in exe mode, it is a rar and I cannot "right click -> run as administrator" as the tutorial says.
Is there any way I can flash the original RUU to the phone in fastboot mode? Or an alternative RUU X.XX.401.X in exe format?
Click to expand...
Click to collapse
if you are referring to the one vin4yak gave to you, it is a nandroid backup from another HOX not the RUU. you need to flash it via recovery.

Oh sorry, thanks for the clarification!
I will try it again as soon as I arrive home.

Spook HECDur
I have followed the above steps, but now in the bootloader, it appears a message above:
*** RELOCKED ***
And if I try to do anything, it appears a:
*** SECUTIRY WARNING ***
What could I do? I would need to send it as stock to HTC RMA, and I do not know if they could see that RELOCKED text, it could be suspicious...
I flashed the recovery.img, boot.img and restore the backup (now the phone is at stock ROM, but it is in German :S). What annoys me the most is that RELOCKED message at bootloader.
Thanks again!

jfromeo said:
I have followed the above steps, but now in the bootloader, it appears a message above:
*** RELOCKED ***
And if I try to do anything, it appears a:
*** SECUTIRY WARNING ***
What could I do? I would need to send it as stock to HTC RMA, and I do not know if they could see that RELOCKED text, it could be suspicious...
I flashed the recovery.img, boot.img and restore the backup (now the phone is at stock ROM, but it is in German :S). What annoys me the most is that RELOCKED message at bootloader.
Thanks again!
Click to expand...
Click to collapse
Did you flash the stock recovery before relocking the bootloader?
and what does your bootloader say? endeavoru or evita??
You can not change the ****relocked**** part...

vin4yak said:
Did you flash the stock recovery before relocking the bootloader?
and what does your bootloader say? endeavoru or evita??
You can not change the ****relocked**** part...
Click to expand...
Click to collapse
Oh, maybe not. I flashed the recovery.img from the dropbox link (it seems to be a modded cwm 6.X recovery), but I did not flash any other after restoring the backup.
It says Endeavoru.
May I need to unlock it again using the HTCDev method?

jfromeo said:
Oh, maybe not. I flashed the recovery.img from the dropbox link (it seems to be a modded cwm 6.X recovery), but I did not flash any other after restoring the backup.
It says Endeavoru.
May I need to unlock it again using the HTCDev method?
Click to expand...
Click to collapse
No need to do the whole process again... You must have the unlock code bin file right?
Use this to unlock your bootloader : fastboot flash unlocktoken unlock_code.bin
If you don't have your unlock code file, you will need to again get it from htcdevi...
Download this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img put it in your fastboot folder and then flash the recovery...
Again relock your bootloader... the security warning must go now? Try these steps and report back

vin4yak said:
No need to do the whole process again... You must have the unlock code bin file right?
Use this to unlock your bootloader : fastboot flash unlocktoken unlock_code.bin
If you don't have your unlock code file, you will need to again get it from htcdevi...
Download this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img put it in your fastboot folder and then flash the recovery...
Again relock your bootloader... the security warning must go now? Try these steps and report back
Click to expand...
Click to collapse
Thanks so much again.
I have followed the steps and the security warning is gone!
Unlock bootloader, flash stock recovery, lock bootloader.
But it says again ***RELOCKED***, is it normal? Could the HTC RMA deny it for this reason?
I have already changed the stock ROM to the native language.
So, the phone is right now, with recovery_stock flashed, stock ROM installed, native language, all set to default (factory reset), but bootloader "relocked", which is the only thing that would differ from a not modified one. Could it be a problem?
Thanks so much again!

jfromeo said:
Thanks so much again.
I have followed the steps and the security warning is gone!
Unlock bootloader, flash stock recovery, lock bootloader.
But it says again ***RELOCKED***, is it normal? Could the HTC RMA deny it for this reason?
I have already changed the stock ROM to the native language.
So, the phone is right now, with recovery_stock flashed, stock ROM installed, native language, all set to default (factory reset), but bootloader "relocked", which is the only thing that would differ from a not modified one. Could it be a problem?
Thanks so much again!
Click to expand...
Click to collapse
Yes, chances are always there of warranty being void with a relocked bootloader!
You have complete stock rom+recovery+bootloader locked... So you have done your best! Send it to HTC and lets hope for the best!
Do keep us posted!

Thanks again.
Could this thread work for getting a LOCKED state instead of a RELOCKED one?
http://forum.xda-developers.com/showthread.php?t=2168578
I will try the warranty claim anyway.
I hope that, given it is a hardware fault (Wifi not working from the second month) , a relocked bootloader has nothing to do.

jfromeo said:
Thanks again.
Could this thread work for getting a LOCKED state instead of a RELOCKED one?
http://forum.xda-developers.com/showthread.php?t=2168578
I will try the warranty claim anyway.
I hope that, given it is a hardware fault (Wifi not working from the second month) , a relocked bootloader has nothing to do.
Click to expand...
Click to collapse
That is for s-off phones only... There's isn't a way to edit Bootloader for S-on phones!
-Sent from my IceCold One X!

Thanks again.
I will try to RMA and let you know

jfromeo said:
Thanks again.
I will try to RMA and let you know
Click to expand...
Click to collapse
Ohkk! All the best! :good:
-Sent from my IceCold One X!

Help Needed please
version: 0.5a
version-bootloader: 1.36.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.14.720.24
serialno: HT245W121191
imei: 35918XXX1XXX301
product: endeavoru
platform: HBOOT-T30S
modelid: PJ461XX00
cidnum: HTC__038
battery-status: low
battery-voltage: 2854mV
devpower: 0
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Can Any one suggest me which Ruu should i boot for this device i have tried falsshing
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.26.720.2_Ra dio_1.1204.90.13_release_251419_signed ---> its showing 140 Boot vershion error please help me ASAP my phone is not booting into os as well please let me know thanks in advance

There is no ruu, go to the general section here and look for the stock backup collection thead. Read it.....completely......twice ..... and follow the guideline !
http://forum.xda-developers.com/showthread.php?t=1975140

[Q] Help Flashing Stock ROM onto Developer M8

Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!

rbalutiu said:
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
Click to expand...
Click to collapse
use this
http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe

clsA said:
use this
Click to expand...
Click to collapse
Just flash the exe onto the phone using the fastboot command? or is there something more to it?

rbalutiu said:
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
Click to expand...
Click to collapse
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb

clsA said:
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
Click to expand...
Click to collapse
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?

rbalutiu said:
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
Click to expand...
Click to collapse
Flash this first
https://www.androidfilehost.com/?fid=95784891001612796
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...

clsA said:
Flash this first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
Click to expand...
Click to collapse
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?

rbalutiu said:
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
Click to expand...
Click to collapse
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?

The ruu and Firmware works fine with s-on
post the command window output ..your doing something wrong

rbalutiu said:
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
Click to expand...
Click to collapse
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)

nkk71 said:
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
Click to expand...
Click to collapse
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again

clsA said:
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
Click to expand...
Click to collapse
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7

nkk71 said:
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
Click to expand...
Click to collapse
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!

rbalutiu said:
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
Click to expand...
Click to collapse
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B1****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: BS_US002
cidnum: GOOGL001
mainver: 3.11.1700.5
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php

clsA said:
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
Click to expand...
Click to collapse
Thanks so much! Got 5.0.1 running on the phone, thanks for all the help!