Develop Bugs

[Q] Flashing Stock RUU

Hi Everyone,
I have become slightly frustrated as I seem to be unable to flash the stock rom back onto my HTC One X. I have a CID of HTC__001 which seems to be perfect and I am with Orange Uk. I have downloaded the correct RUU for the specific radio I have (2.1204.135.20) and when I run the exe in windows. It starts to work and then says my USB is not connected.
Previously I have been rooted and have flashed the recovery image, which does mean I am connected via use and in fastboot mode. Not sure what is causing this issue. If anyone could provide any assistance that would be fantastic.
Thanks
Andy

Andy,
Ruus need stock recovery. Are you back on stock recovery? Also, phone must be booted up into rom and respond to adb commands such as
Adb devices
This should list your devices serial number as connected. If you see that, then try running the ruu.
Sent from my HTC One X using xda premium

1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required

Thanks
Thanks for both of your replies. I have since managed to install the sense jelly bean roms from Insert Coin and also Maximum, realised that I did not need to install the RUU, just need to flash the boot.img. All is now great. The RUU that you posted was the one i tried but failed :s Its ok now though as now I am unable to return to ICS roms

EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:

DropePT said:
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:
Click to expand...
Click to collapse
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.

shadwell_lad said:
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.
Click to expand...
Click to collapse
I only get into the black screen with HTC logo:silly: I have Microsoft Security Essentials, already flashed RUU without problems, this was the 1st time. Meanwhile, flashed now with football rom, Revolution without any problems. Just wonder if when OTA will be available, if i can install it

thanks so much guys, this helped me a lot!

Help needed!
Hi guys. I'm very new to this so forgive me if I seem a bit stupid at times. I've been reading a lot and trying to learn things about the phone but I've got myself a bit stuck.
I have a HOX with the following;
*** relocked ***
CID HTC__001
Hboot 1.12.0000
radio-2.1204.135.20
Everything was stock, I unlocked and rooted. All went well, everything worked fine. Didn't install any ROM's. Installed CWM. Then JB was released so I unrooted and relocked and flashed stock recovery.
The phone now has;
Android 4.0.4
HTC Sense 4.1
Software 2.17.401.2
API 4.23
HTC Extension 403_1_GA_20
Everything works. I can boot the phone and everything works as it should. The only issue I can see is that it won't boot into recovery. I get the green arrows, press power and up volume, some errors are reported on the screen - Cannot find /cache/recovery/command and Failed to open loopdevice, no such file or directory. The phone then restarts and boots the OS.
My question is, what should I do next to be able to receive the OTA JB update? I assume I'll need to do some combination of flashing the boot.img and recovery.img but I'm unsure what the process is, or even if my assumptions are correct? Help??
EDIT 1 : I found this. http://forum.xda-developers.com/showthread.php?t=1193540
I think it's what I need. I just need to read some more and find out what ROM I need to download. Can anyone advise if this is in fact what I need to do and what ROM I should be looking for?
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.

The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.

BenPope said:
The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.
Click to expand...
Click to collapse
Thanks for the reply BenPope. Yea, I saw the guide was for a different device, but the steps are virtually identical. I went ahead and ran the RUU. Everything flashed OK, no errors, no issues. Re-locked the bootloader. Still can't run recovery tho. Still getting the same errors. As I understand it I won't be able to get OTA updates installed if Recovery isn't working correctly. Have I got this right? Any ideas?

You're saying everything in the wrong order. Please be more clear.
To run the RUU, your hboot needs to be locked. If after the RUU you can't access recovery something went wrong and the RUU failed. What errors are you getting?

g12__ said:
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.
Click to expand...
Click to collapse
Take boot_signed.img and recovery_signed and Rom.zip from the RUU. Boot to fastboot, flash boot_signed.img and recovery.img . Boot to recovery and flash the rom.zip.
Sent from my HTC One X using xda premium

Your problem was due to flashing stock recovery AFTER relock.
Try this:
1. Unlock again.
2. Fastboot flash stock recovery.
3. Then, relock.
4. Boot your phone.
Try to update then.
Sent from my HTC One X using XDA Premium HD app

EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
is this RUU same for cid_032????????????????

yode said:
is this RUU same for cid_032????????????????
Click to expand...
Click to collapse
2.17.401.2 RUU is for :
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

I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!

****head said:
I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!
Click to expand...
Click to collapse
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X

TToivanen said:
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X
Click to expand...
Click to collapse
sigh ....
thanks for the info.
do you know how much they will ask for the repair?

****head said:
do you know how much they will ask for the repair?
Click to expand...
Click to collapse
No but there is a slight chance it could be covered by warranty since it is a hardware fault. Sorry for your loss man.
Sent from my HTC One X

[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.

[Q] Returning my HTC Wildfire S back to normal to warranty issues

I have a HTC Wildfire S, its a GSM device and I bought it from Vodafone a year ago, its still under warranty. It came with 2.3.3 pre-installed but I OTA updated it to 2.3.5. I unlocked the bootloader using the guide from htcdev, rooted it and installed Clockworkmod Recovery and backed up my current stock rom. I have installed Marvellous Sense 2.1 Cyanogenmod 7.1 on my Wildfire S and I ran into a problem with my phone, the POWER button needs a little bit of strength in order to actually work (I took the phone once to the beach and the button has been malfunctioning ever since) so I'm thinking of sending it to Vodafone to repair the button, my Wildfire S is SIM Unlocked (I went to those 'specialized stores' to unlock it, my guess is they used an unlock code for it) so I don't know if Vodafone will actually notice it, so I'm thinking of locking the bootloader again (not relock it) and then proceed to use the right RUU for my radio version, however I am dead afraid of bricking my phone, so can I get a little help with this? My theory is as it follows:
1- Leave the clockworkmod recovery installed and the custom rom as well
2- Lock the bootloader using a bootloader tool (I forgot the name of it)
3- Run the correct RUU for my radio version (7.57.39.10M)
4- Hopefully the RUU will delete the custom recovery and custom rom
5- Device would be back to normal with a completely stock ROM almost as untouched
Is this the correct proceeding? Also my stock Vodafone rom has a lot of portuguese Vodafone crapware installed which I don't think its in the original RUU for this phone (I might be wrong) I've been reading around XDA forum by forum and gathering everything I can get to safely restore my phone for warranty issues but I'm afraid I might f*ck it up, specially since it wasn't cheap and it was a brand new phone.
Thanks for the help guys :good:

Yepi69 said:
I have a HTC Wildfire S, its a GSM device and I bought it from Vodafone a year ago, its still under warranty. It came with 2.3.3 pre-installed but I OTA updated it to 2.3.5. I unlocked the bootloader using the guide from htcdev, rooted it and installed Clockworkmod Recovery and backed up my current stock rom. I have installed Marvellous Sense 2.1 on my Wildfire S and I ran into a problem with my phone, the POWER button needs a little bit of strength in order to actually work (I took the phone once to the beach and the button has been malfunctioning ever since) so I'm thinking of sending it to Vodafone to repair the button, my Wildfire S is SIM Unlocked (I went to those 'specialized stores' to unlock it, my guess is they used an unlock code for it) so I don't know if Vodafone will actually notice it, so I'm thinking of locking the bootloader again (not relock it) and then proceed to use the right RUU for my radio version, however I am dead afraid of bricking my phone, so can I get a little help with this? My theory is as it follows:
1- Leave the clockworkmod recovery installed and the custom rom as well
2- Lock the bootloader using a bootloader tool (I forgot the name of it)
3- Run the correct RUU for my radio version (7.57.39.10M)
4- Hopefully the RUU will delete the custom recovery and custom rom
5- Device would be back to normal with a completely stock ROM almost as untouched
Is this the correct proceeding? Also my stock Vodafone rom has a lot of portuguese Vodafone crapware installed which I don't think its in the original RUU for this phone (I might be wrong) I've been reading around XDA forum by forum and gathering everything I can get to safely restore my phone for warranty issues but I'm afraid I might f*ck it up, specially since it wasn't cheap and it was a brand new phone.
Thanks for the help guys :good:
Click to expand...
Click to collapse
BUMP sorry guys I hate bumping but I need to know this because I'm thinking of sending the phone soon.

Yepi69 said:
BUMP sorry guys I hate bumping but I need to know this because I'm thinking of sending the phone soon.
Click to expand...
Click to collapse
Hi your procedure is correct and will work allowing the ruu has the correct cid for your phone.
An alternative would be to flash a stock rooted rom, and tear open the rom.zip from the ruu you have and then re-add your vodaphone boot animation.
And if your really stuck you could post a link to the ruu and i could make a safe flash rom from recovery, and pass you over the stock recovery as well. Then the plan would be
Nandroid backup
Wipe everything
Flash rom
Boot to fastboot
Flash stock recovery
Reboot and check all is well
Bootloader to lock bootloader
Profit lol also, last thing. Htc records when people unlock their bootloaders and you may have voided your warranty in the process. Just a thought
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
Hi your procedure is correct and will work allowing the ruu has the correct cid for your phone.
An alternative would be to flash a stock rooted rom, and tear open the rom.zip from the ruu you have and then re-add your vodaphone boot animation.
And if your really stuck you could post a link to the ruu and i could make a safe flash rom from recovery, and pass you over the stock recovery as well. Then the plan would be
Nandroid backup
Wipe everything
Flash rom
Boot to fastboot
Flash stock recovery
Reboot and check all is well
Bootloader to lock bootloader
Profit lol also, last thing. Htc records when people unlock their bootloaders and you may have voided your warranty in the process. Just a thought
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm aware of that, but even so I don't believe that alone voids my warranty because on HTCDEV's website it says it *may* void it, all I care is to bypass Vodafone's smartass checking, so basically I have to extract the rom.zip the RUU temporary creates, flash it everything (boot.img, system.img, recovery.img) through fastboot, reboot and check the rom's status and then finally use the tool to lock (not relock) the bootloader, can't I just wipe everything, lock the bootloader and use the correct RUU?
Also thanks.

Yepi69 said:
I'm aware of that, but even so I don't believe that alone voids my warranty because on HTCDEV's website it says it *may* void it, all I care is to bypass Vodafone's smartass checking, so basically I have to extract the rom.zip the RUU temporary creates, flash it everything (boot.img, system.img, recovery.img) through fastboot, reboot and check the rom's status and then finally use the tool to lock (not relock) the bootloader, can't I just wipe everything, lock the bootloader and use the correct RUU?
Also thanks.
Click to expand...
Click to collapse
You could assuming that it has a higher software version than yours, higher hboot and the correct cid you can by all means run the ruu. If you extract the rom.zip you will see a file called android.info or androidinfo.txt open it in a text editor and lists several Cid's that it will work for.
If you issue the following command via fastboot mode it will output lots of useful information about your phone including your cid.
Fastboot getvar all
Assuming everything matches up then by all means make a nandroid then run the bootloader tool, Then the ruu. The ruu wont run on an unlocked bootloader, and when you get your device back all nice and repaired you can just restore your nandroid backup and your back to were you left off
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
You could assuming that it has a higher software version than yours, higher hboot and the correct cid you can by all means run the ruu. If you extract the rom.zip you will see a file called android.info or androidinfo.txt open it in a text editor and lists several Cid's that it will work for.
If you issue the following command via fastboot mode it will output lots of useful information about your phone including your cid.
Fastboot getvar all
Assuming everything matches up then by all means make a nandroid then run the bootloader tool, Then the ruu. The ruu wont run on an unlocked bootloader, and when you get your device back all nice and repaired you can just restore your nandroid backup and your back to were you left off
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Can I run a RUU with the same baseband and radio version?
Basically I'll just need to lock the bootloader first right?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0099
(bootloader) version-baseband: 7.57.39.10M
(bootloader) version-cpld: None
(bootloader) version-microp: 0451
(bootloader) version-main: 2.26.168.1
(bootloader) serialno: SH15RTR15911
(bootloader) imei: 358225045934016
(bootloader) product: marvel
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PG7610000
(bootloader) cidnum: VODAPD18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 510e562c
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

BUMP :highfive:
EDIT:
heavy_metal_man said:
Hi your procedure is correct and will work allowing the ruu has the correct cid for your phone.
An alternative would be to flash a stock rooted rom, and tear open the rom.zip from the ruu you have and then re-add your vodaphone boot animation.
Click to expand...
Click to collapse
I have a backup of my vodaphone stock rom when I first rooted and installed clockworkmod, however that rom is rooted (but unmodified, clean 100% stock rom updated from OTA when I got it) I only made a backup after rooting it.
Can I just restore that backup, re-flash recovery to remove the root (I tried the rom's own recovery but that didn't remove root, superuser was still there) and then use the HTC bootloader tool to lock the bootloader?

Yepi69 said:
BUMP :highfive:
EDIT:
I have a backup of my vodaphone stock rom when I first rooted and installed clockworkmod, however that rom is rooted (but unmodified, clean 100% stock rom updated from OTA when I got it) I only made a backup after rooting it.
Can I just restore that backup, re-flash recovery to remove the root (I tried the rom's own recovery but that didn't remove root, superuser was still there) and then use the HTC bootloader tool to lock the bootloader?
Click to expand...
Click to collapse
Yeah restore the back up and flash the stock recovery. Then install SuperSU from the play market. It will state that it has compatibility issues with all other superuser apps and remove them upon request. Then from supersu's app menu select full unroot and it will remove all traces of it then relock the hboot using the tool.
Sent from my HTC Desire S using Tapatalk

[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!

HTC One M8 Bricked? Looking for help desperately!

Hello,
I got an OTA update for my HTC one but i wasnt able to install it normally. so i went into TWRP recovery and FULLY-wiped my phone(system,data,cache,dalvik). When i proceeded to install the zip, i got an error saying:
file_getprop: failed to stat "/system/build.prop": No such file or directory.
E:Error executing updater binary in zip '...'
I got the same error when i tried flashing another ROM, dirty unicorns. I tried restarting my phone and installing again WITHOUT wiping anything and still nothing. When i connect the phone to my laptop, it shows the phone as a CD DRIVE. Can someone PLEASE help me?
TWRP:2.7.0.2
**TAMPERED**
**UNLOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
eMMC-boot 2048mb

OTA updates usually cannot be updated via Custom recoveries like CWM or TWRP. I suggest you do roll back to a stock rom using TWRP backups found in the forums, flash a recent version of TWRP and then try flashing custom roms.
Suggesting that you start with updating your current TWRP to 3.0.2

what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs

ahmed.ismael said:
what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Htc on(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And the name of the file is:
OTA_M8_UL_K44_SENSE60_MR_hTC_Asia_WWE_2.22.707.4-1.54.707.7_release_387917.zip

@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock

ahmed.ismael said:
@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock
Click to expand...
Click to collapse
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.

Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.

Younuszain said:
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.
Click to expand...
Click to collapse
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Younuszain said:
I got the same error when i tried flashing another ROM, dirty unicorns.
TWRP:2.7.0.2
Click to expand...
Click to collapse
Your hboot and TWRP versions are far too old to install or run any current ROMs.

redpoint73 said:
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Your hboot and TWRP versions are far too old to install or run any current ROMs.
Click to expand...
Click to collapse
So You're saying if i update my TWRP version, I should be able to install any other ROM?

Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.

redpoint73 said:
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.
Click to expand...
Click to collapse
What if i just want to install a custom ROM, dirty unicorns?

Younuszain said:
What if i just want to install a custom ROM, dirty unicorns?
Click to expand...
Click to collapse
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs

ahmed.ismael said:
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/

Younuszain said:
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/
Click to expand...
Click to collapse
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs

ahmed.ismael said:
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Ok So i follewed the instructions to flash the firmware and twas successful. Now my screen looks like thisThe bootloader had to be locked to flash the firmware):
**Software status: Modified**
**RELOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark! So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
Which was given on the TWRP website. I got an error saying:
FAILED <remote: signature verify fail>
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
I read somewhere that to flash TWRP I need to unlock the bootloader again and i have give the token on the HTCdev wesbite. But i tried registering there but i received no email from them.
What do i do now? :/

Younuszain said:
Ok So i follewed the instructions to flash the firmware and twas successful.
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark!
Click to expand...
Click to collapse
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
Younuszain said:
So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
I got an error saying:
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Younuszain said:
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
Click to expand...
Click to collapse
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.

redpoint73 said:
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.
Click to expand...
Click to collapse
Well, Thanks a lot for that info . As far as me not knowing, guess theres a first time for everything.
Could you direct me as to how to get the existing bin code to unlock the bootloader? Because i guess thats what I have to do next inorder to get my phone up and running again.

Younuszain said:
As far as me not knowing, guess theres a first time for everything.
Click to expand...
Click to collapse
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
Younuszain said:
Could you direct me as to how to get the existing bin code to unlock the bootloader?
Click to expand...
Click to collapse
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.

redpoint73 said:
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the guidance. Will definitely be more careful from next time.
The Dev website isn't sending the confirmation mail though.

Younuszain said:
The Dev website isn't sending the confirmation mail though.
Click to expand...
Click to collapse
The website can be buggy. I think when I unlocked the bootloader on this or a previous HTC device, I had to use 3 different emails, before I got the confirmation email.