Develop Bugs

[TUT]How to relock your bootloader,downgrade and root or s-0ff

Hi guys, this is very simple tut on how to lock your bootloader,downgrade,s-off and root
Full wipe before Doing this. (Recommended)
Relocking BOOTLOADER Steps(skip this if your bootloader is locked)
--------------------------
1.First download the fastboot folder (Click here!)
2.Then EXTRACT it to where you can locate it (e.g C/Desktop)
3.Now put your cursor to your EXTRACTED Fastboot Folder And Press SHIFT+Right click on the Fastboot folder and click 'Run as Command Prompt'
4.Minimize the Command prompt
5.Now on your HTC DESIRE Turn it off and load into bootloader (press Power+ volume down and hold untill a white screen pops up)
6.Then use your volume up and down to controle it (Volume up goes up, Volume down goes down (duh) and pressing power button enters directory)
7.press Volume down to fastboot on your htc and click the power button
8.Go back to your computer and open your minimized command prompt
9.Type in this code
fastboot oem lock
10.If you did this sucesfully a fail word will come up and your phone will shut down. Reload your htc bootloader and you will see relocked on your pink header.(Note: this product cant be 'locked':crying
11. Voila! Enjoy your downgrade and rooting!
Downgrade steps [1.03](Skip this if your hboot is 1.02)
-----------------
1. Download tools package (click here!)
NOTE: THIS FILE DOES NOT CONTAIN VIRUS NOR TROJAN BUT YOUR ANTIVIRUS DETECTS IT AS VIRUS SO TURN YOUR ANTIVIRUS OFF
2. Download the HTC Desire ROM (RUU)
3. For branded phones you need to create GoldCard (How to)
4. Extract theses tools where you can actually remember.
5. Run RUU and wait till the ROM update utility screen appears.
6. Go to Temp directory where your ruu is downloaded (C:\Users\Your User Name\AppData\Local\Temp for Win7 and vista,C:\Documents and Settings\Your User Name\Local Settings\Temp for WINXP Users) and search for rom.zip
7. Copy the rom.zip and paste it to sdcard and rename it to PB99IMG.zip
8. Connect your phone to computer via USB as charge only and enable USB debugging and Unknown Sources.
9. Run DOWNGRADER on tools folder that you downloaded and extracted it.
10. Follow the onscreen instructions (This may take upto 1 to 2 min)
11. Your phone will be reset, wait for detect and check the Update Package.
12. After checking update package, press vol-up to begin update process, IN FIRST TIME AFTER PRESSING VOL-UP YOUR PHONE WILL RESET AND DO NOTHING, YOU SHOULD DO AGAIN FOR STEPS 11,12
s-off Steps:
1.Click this
2.fill up your information
3.save your beta key somewhere
4.Download revolutionary
5.follow step and on some occasions they will ask for beta key
6.your phone will s-off
Rooting
-----------------------
1. download unrevoked (click here)
and let the programme do the rest
How to flash your own costume recovery!!
--------_------------
Press shift+right click on the extracted fast boot and click open as command prompt something like that and minimize that and download your costume recovery. Then put it inside fast boot and rename it as recovery. Then plug in your HTC and go to boot loader and go to fast boot. Now¶π° go back to your command prompt and typein this code
fastboot flash recovery.img
If u did this successfully then it will say successfully flash costume recovery
Notes
The process will flash a clockwork mod recovery partition:good:
This process will wipe all the data from your phone:good:
The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot):fingers-crossed:
Your sdcard should be fat32 formatted:good:
This Pure entertainment will relock the bootloader:laugh:
When life gives you lemonade
HiT THANKS IF THIS HELPED YOU. AND POST A REPLY FOR IMPROVEMENTS
Improvement credit
Nloooo

Respect for the effort but there are a few misunderstandings:
1. Locking of bootloader??? Why for God's sake??? A ton of people lost their hair trying to unlock it!!!!
2. Downgrading? What kind? You have to explain the reason (1.03 bootloader or what)
3. Quoting "2. Download the HTC Desire ROM (RUU)". Don't mix rom with RUU (Rom Update Utility), they are not the same.
Plus: which RUU to download, you have to explain, what version (Android related), which region based (for branded devices)...
Ok you mentioned goldcard-explain why (for branded devices)...
My recommendation: suggest 2.3 RUU, it's usable with all phone types (amoled or slcd) and all regions (no goldcard needed applicable for all brends).
Also you have to mention that all RUUs can be used from PC while phone is connected via USB.
4. S-off process: revolutionary-yes but for 0.93. and 1.02 hboots, for older versions of hboots alpharev reflash utility needed
5. Rooting: Unrevoked-yes but when you don't use Revolutionary (gaining s-off using Alpharev reflash utility).
Revolutionary itself gives option to flash recovery (Clockwork Mod) which you use to flash Superuser app to gain root access (explained on documentation page for
Revolutionary, all you need is to read http://unrevoked.com/rootwiki/doku.php/public/revolutionary)
6. Quoting "The process will flash your recovery partition back to stock" - no, Revolutionary will flash ClockworkMod recovery.
7. Quoting "The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot)" - not necessarily the hboot will be 1.02, it depends on which RUU you choose to flash.
Plus:
Downgrade package contains virus, warn potential user - what is it, a virus that will ruin their PC or just an exploit used to gain access to restricted phone partitions.
I hope I helped...

wow... i agree with nlooooo, good effort but u just confused the s*** outa me lol.
Sent from my HTC Desire

ok thank you nloo
Thank you for your reply and I appreciate for your time writing this! I will,perhaps, change my thread

just go by what nlooooo says, i mean just add a bit more detail to what ur saying. this is a TUT and people might use this and the last thing u want is people blaming u if anything goes wrong because u forgot to mention something
Sent from my HTC Desire

thanks!
good work!

Stop spamming and start hitting the thanks button!
Sent from my HTC Desire using xda premium

Umg

my problem is that I can't boot in the OS, it is always stuck at HTC logo I did relock and I can't flash RUU, get "signarure error"

ferencz1 said:
my problem is that I can't boot in the OS, it is always stuck at HTC logo I did relock and I can't flash RUU, get "signarure error"
Click to expand...
Click to collapse
Try the 2.3 RUU. Check my sig.

my phone was sent for repair, got new motherboard and after one hour of using it he just froze. I removed my battery and put it back, after that it stuck on HTC logo screen. So I went to flash RUU but I couldn't install it I got singarure error, so I made bootloader unlock and after that I don't know what to do next.
Nothing in bootloader it says: "checking PB99IMG.zip - no images found"
so I really don't know how to make downgrade because I can't get into the OS I can't flash RUU's and PB99IMG's, some PB99IMG's are read but after that it just stops, I don't get the screen with recovery...OK, boot....OK, etc (I don't get parsing message). He just get's in the bootloader again :/

hi sorry for a stupid quistion but i had to ask
can i use this to relock bootloader on my htc desire hd?

slimboy01 said:
can i use this to relock bootloader on my htc desire hd?
Click to expand...
Click to collapse
The command is the same, so just make sure u got fastboot set up then use the command
fastboot oem lock

done
i relocked my bootloader using this tool

RUU needed
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13KTJ32915
(bootloader) imei: 35506*******
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
i didn't find any correct ruu
please help :/

mkumar55533 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13KTJ32915
(bootloader) imei: 35506*******
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
i didn't find any correct ruu
please help :/
Click to expand...
Click to collapse
This is the htc desire (bravo) section, click the link below and use the correct guide for ur device (desire "s") and u can find the correct ruu at shipped roms.
http://forum.xda-developers.com/showthread.php?t=1318919

I did relock and how to back to unlock ?
nlooooo said:
Respect for the effort but there are a few misunderstandings:
1. Locking of bootloader??? Why for God's sake??? A ton of people lost their hair trying to unlock it!!!!
2. Downgrading? What kind? You have to explain the reason (1.03 bootloader or what)
3. Quoting "2. Download the HTC Desire ROM (RUU)". Don't mix rom with RUU (Rom Update Utility), they are not the same.
Plus: which RUU to download, you have to explain, what version (Android related), which region based (for branded devices)...
Ok you mentioned goldcard-explain why (for branded devices)...
My recommendation: suggest 2.3 RUU, it's usable with all phone types (amoled or slcd) and all regions (no goldcard needed applicable for all brends).
Also you have to mention that all RUUs can be used from PC while phone is connected via USB.
4. S-off process: revolutionary-yes but for 0.93. and 1.02 hboots, for older versions of hboots alpharev reflash utility needed
5. Rooting: Unrevoked-yes but when you don't use Revolutionary (gaining s-off using Alpharev reflash utility).
Revolutionary itself gives option to flash recovery (Clockwork Mod) which you use to flash Superuser app to gain root access (explained on documentation page for
Revolutionary, all you need is to read http://unrevoked.com/rootwiki/doku.php/public/revolutionary)
6. Quoting "The process will flash your recovery partition back to stock" - no, Revolutionary will flash ClockworkMod recovery.
7. Quoting "The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot)" - not necessarily the hboot will be 1.02, it depends on which RUU you choose to flash.
Plus:
Downgrade package contains virus, warn potential user - what is it, a virus that will ruin their PC or just an exploit used to gain access to restricted phone partitions.
I hope I helped...
Click to expand...
Click to collapse
I done relock but after bootloader I cant downgrad ! I need help unlock bootloader back . I type fastboot oem unlock but dont work !!!

Ah, the old times.
miniandroidp : can you give us some photos?

:S Phone cannot boot :/

My friend has just unlocked his bootloader using HTC Dev, this has left it S-ON, so he installed cwm, made a nandroid, then began flashing rom's, he flashed the boot.img separate via fastboot due to the s-on, yet aosp rom's just get stuck on the boot animation, and any sense rom, (including the backup) just boot straight to recovery :/ He's asked me for help but I'm at a loss to explain this :S
we have tried reflashing an RUU but it just complained about it being the wrong version even though there is no other version it could be
Any ideas?
Thanks in advance

Relock the bootloader, then root using the ace advanced kit. You will may find a link to it in xda or if you search for glevitan. The hack kit was removed from xda.
Sent from a dream.

l.m.prowse said:
My friend has just unlocked his bootloader using HTC Dev, this has left it S-ON, so he installed cwm, made a nandroid, then began flashing rom's, he flashed the boot.img separate via fastboot due to the s-on, yet aosp rom's just get stuck on the boot animation, and any sense rom, (including the backup) just boot straight to recovery :/ He's asked me for help but I'm at a loss to explain this :S
we have tried reflashing an RUU but it just complained about it being the wrong version even though there is no other version it could be
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
you have to flash the boot.img in fastboot commands if you have unlocked the bootloader with HTCDEV. Do that, and the you will have a working phone.
HTCDEV is useless, I would suggest that u relock the bootloader and then use the Hack Kit....:good:

Teichopsia said:
Relock the bootloader, then root using the ace advanced kit. You will may find a link to it in xda or if you search for glevitan. The hack kit was removed from xda.
Sent from a dream.
Click to expand...
Click to collapse
glevitan said:
you have to flash the boot.img in fastboot commands if you have unlocked the bootloader with HTCDEV. Do that, and the you will have a working phone.
HTCDEV is useless, I would suggest that u relock the bootloader and then use the Hack Kit....:good:
Click to expand...
Click to collapse
We cannot get the phone to boot into a rom, therefore the hack kit is useless, it requires the phone to boot, and we've relocked and everything, it just refuses to boot any roms (yes we have been flashing the boot.img's via fastboot

l.m.prowse said:
We cannot get the phone to boot into a rom, therefore the hack kit is useless, it requires the phone to boot, and we've relocked and everything, it just refuses to boot any roms (yes we have been flashing the boot.img's via fastboot
Click to expand...
Click to collapse
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.

Teichopsia said:
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.
Click to expand...
Click to collapse
His advice was to use the hack kit, which we cannot do without a booting OS, which we currently do not have, which is the reason I posted here.

Teichopsia said:
Shhhh, saying the hack kit is useless will get you in a lot of trouble. Be patient, listen to glevitan.
@everyone, pardon him on my behalf - he doesn't know. Try to help him despite that comment.
Sent from a dream.
Click to expand...
Click to collapse
From what I've gathered, he's in a bootloop, unlocked with HTCDEV and has tried to flash the backed up boot.img via fastboot.
In this specific situation how is the hack kit any use to him if he can't get past the splash screen?
Perhaps double check the locations and files you're pushing/flashing and "fastboot erase cache" before and after.
I'm sure you've probably tried this already but it's the only other things I can think of causing the loop.

sprogurt said:
From what I've gathered, he's in a bootloop, unlocked with HTCDEV and has tried to flash the backed up boot.img via fastboot.
In this specific situation how is the hack kit any use to him if he can't get past the splash screen?
Perhaps double check the locations and files you're pushing/flashing and "fastboot erase cache" before and after.
I'm sure you've probably tried this already but it's the only other things I can think of causing the loop.
Click to expand...
Click to collapse
Yeah we've tried all of that :/ I can't think of any reason its doing it. It's the same as I do on my HOX, never had a single problem with it :/

l.m.prowse said:
Yeah we've tried all of that :/ I can't think of any reason its doing it. It's the same as I do on my HOX, never had a single problem with it :/
Click to expand...
Click to collapse
Ok, in order to flash a RUU you will have to relock your bootloader. The main version error is due to the unlocked bootloader.
If you still have CWM, before relocking the bootloader u can try to flash a custom rom and then flash the boot.img in fastboot (but doing a wipe first) If that is not working, then you gotta flash a RUU but wil only work if you relock the bootloader....:good:

glevitan said:
Ok, in order to flash a RUU you will have to relock your bootloader. The main version error is due to the unlocked bootloader.
If you still have CWM, before relocking the bootloader u can try to flash a custom rom and then flash the boot.img in fastboot (but doing a wipe first) If that is not working, then you gotta flash a RUU but wil only work if you relock the bootloader....:good:
Click to expand...
Click to collapse
We relocked the bootloader, and the RUU still said it was the wrong version, the image on the device is 1.13 whereas the ruu is 1.12.405.1, there is no 1.13 ruu :/

l.m.prowse said:
We relocked the bootloader, and the RUU still said it was the wrong version, the image on the device is 1.13 whereas the ruu is 1.12.405.1, there is no 1.13 ruu :/
Click to expand...
Click to collapse
ok, do the following, what CID number does the phone have?
boot in hboot, choose fastboot and then plug the phone (you should see fastboot usb in red). Now open a CMD as admin in the PC and type fastboot getvar all. Get the INFOcidnum...and paste it here...

glevitan said:
ok, do the following, what CID number does the phone have?
boot in hboot, choose fastboot and then plug the phone (you should see fastboot usb in red). Now open a CMD as admin in the PC and type fastboot getvar all. Get the INFOcidnum...and paste it here...
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.0.0
(bootloader) serialno: SH0CFRX04874
(bootloader) imei: 352668046527618
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3882mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
That's everything it displayed

same problem
I have the same problem. I use bootloader from htc.dev, forgot to backup and i am stuck on fastboot mode. I have cwm but i succesfully instal miui rom, but i cant to use phone, because HTC logo dont move i follow you suggestions. I hope u can help me too.
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.31.405.6
INFOserialno: SH11ZRX02646
INFOimei: 356299049533530
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4194mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.005s

Please help! THREE STRANGE SINDROMS !!! White screen after flashing tried everything

Hello all.
I have dev unlocked the device, flashed clockworkmod recovery v2.5.1.2 (MODACO r2)
Flashed custom rom , during flashing it says all is ok , but when i reset i get just the white screen.
I have tried 2 other roms, same things happen.
++++++++++++++++++++strange thing no 1 - device now says its s-on
++++++++++++++++++++strange thing no 2 - clockworkmod recovery says these things almost every time i get there
E: cant mount cache:recovery/command
E: cant mount CACHE:recovery/log
e:cant open CACHE:recovery/log
++++++++++++++++++++strange thing no 3. I have tried to dev unlock it again, it responds on commands as get identifier token, it shows the codes,but when i enter fastboot flash unlocktoken Unlock_code.bin nothing happens.
here is my recovery info :
*** Unlocked ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_m
eMMC-boot
dec 22 2011
+++++++++++++++++++++here is fastboot info+++++++++++++++++++++++++++++++
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.0.0
(bootloader) serialno: SH11ZRX02794
(bootloader) imei: 356299049535014
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4108mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++RUU UPDATE+++++++++++++++++++++
I have downloaded RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M
it detects the phone, says that my image version is 3.13.0.0. and that it will be updated to
3.13.405.1, starts updating and stops some time after with error 155
I have also downloaded correct p98img.zip for my radio, it flashes ok from recovery when i put it on sdcard.
Does anyone know why did the device lock itself ? why I can not unlock it again ?
Some say that these error messages in clockwork mod are because of faulty emmc chip.
Is there some hope for this phone ? Can I restore it to stock rom, just as it was....
Please help

same problem here

Relock the bootloader and use AAHK to root, S-OFF & SuperCID (SIM Unlock)
Sent from another dimension...
thanks don't hurt ya know?

But my bootloader is already relocked ? it says s ON

S-on means else. You can detect whether your bootloader is unlocked or relocked on the top of your boot menu. But I guess AAHK won't solve your problem, because if you have the same problem as me, your phone doesn't boot up, so you can't use AAHK.

Gabouka said:
S-on means else. You can detect whether your bootloader is unlocked or relocked on the top of your boot menu. But I guess AAHK won't solve your problem, because if you have the same problem as me, your phone doesn't boot up, so you can't use AAHK.
Click to expand...
Click to collapse
His device does boot, just not into a ROM
Sent from another dimension...
thanks don't hurt ya know?

GuyInTheCorner said:
Relock the bootloader and use AAHK to root, S-OFF & SuperCID (SIM Unlock)
Sent from another dimension...
thanks don't hurt ya know?
Click to expand...
Click to collapse
You are getting better bub
Problem with htc dev method, you need to flash the boot img instead of the way we explain the flashing process in the threads.
What guy said is right. Relock the bootloader. Im not sure if you have to flash a ruu and then use the hack kit to get s-off or just use the hack kit.
Search the forum. This issue has been covered plenty of times.
Sent from a dream.

Ah, now I get it, my bootloader is unlocked because thats what it says on top of the recovery screen :
*** Unlocked ***
ACE PVT SHIP S-ON RL
So i have to find out how to relock the bootloader.
Where to find boot img ? I have downloaded the p98img.zip but it only has the radio.img
If anyone has some directions please help... Meanwhile ill search the forums

Open the ROM zip file, in there is boot.img; use that
Sent from another dimension...
thanks don't hurt ya know?

I have tried flashing the ruu for my region , but it doesnt work

Either use the WWE RUU or stick with the boot.img method
Sent from another dimension...
thanks don't hurt ya know?

GuyInTheCorner said:
Either use the WWE RUU or stick with the boot.img method
Sent from another dimension...
thanks don't hurt ya know?
Click to expand...
Click to collapse
I did use the wwe ruu , I mentioned that on my first post.
I used one for my radio :
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.6 0.29_26.14.04.28_M
It says that my image version is 3.13.0.0. and that it will be updated to
3.13.405.1, starts updating and stops some time after with error 155.

Guys, stop. Give me two minutes.
Sent from a dream.

I'm gonna take a break, gf's calling cya
Sent from another dimension...
thanks don't hurt ya know?

retrorobot said:
I did use the wwe ruu , I mentioned that on my first post.
I used one for my radio :
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.6 0.29_26.14.04.28_M
It says that my image version is 3.13.0.0. and that it will be updated to
3.13.405.1, starts updating and stops some time after with error 155.
Click to expand...
Click to collapse
Take a break, don't start trying things without being sure what you are doing.
Ok, so you relocked the bootloader.
Im not sure what the next step is, if you have to flash a ruu or not. Do a search, check what the next step is. Come back and report.
I can't remember if you have to flash a ruu or not or if there was anything else involved before running the hack kit. Im going to try and find something after I've had some coffee. In the meantime search and report back.
Sent from a dream.

I will allso search the forums.
I have not relocked the bootloader, I am currently on my job and I can not do anything till I come home...

Up to this moment, I have figured out that I have to pull out the rom.zip from ruu , and rename it to p98... and put it in the phone.
but how to lock the bootloader ....im still reading about it...

'To relock, just boot to hboot and choose fastboot.
Plug the phone and You should see fastboot USB in red.
Open a CMD as admin or terminal as root in the PC
Type: fastboot oem lock'
great here is info how to do it via adb command, after that I will get the rom.zip from temp folder of the ruu which i used and try with that....

Yup, sounds like you are heading in the right direction.
Sent from a dream.

I will try that tomorrow.
Only thing I can not figure out is, when I tried to update it via ruu from windows, it gave me error 155, why would this method via recovery work ?
I hope it will ) but i'm a bit worried about it ...

bricked htc

Hi
by the time i have heard so much about bricked phones and thought that could not have happend to me. finally it happend to me.
i am a proud owner of bricked HTC desire HD - white screen after RUU file instalation.
S-ON, locked.
i can unlock it becuse htcdev doesent support any more my version of hboot.it is 2.00.027. it needs to be updated to version 2.00.029.
i found a dosen programs and guids to solve my issue BUT nowhere could i find how my computer supose to see my DHD.
USB debbuging is off and i cant reach it due to white screen.
when i plug data cabel in, computer recognizes it as android 1.0., no G particion and HTC sync doesent work. Hboot mode doesent seems to make any hepl
everybody who have faced this kind of problem please post
Thanks in advance

You've tried re-installing the official RUU through fastboot?

that something i havent done so far. how that suppose to be done?
make a small guide.
i accept all suggestions

Actually this might help:
http://forum.xda-developers.com/showthread.php?t=1049414

If you ment by re-installing RUU file - put RUU file the same or higher version of whats on the phone on the sd card rename it PD98IMG.zip enter the hboot (not the fastboot) - hboot will ask me if i want to update - the answer is yes but with fastboot i have no clue.

orangekid said:
Actually this might help:
http://forum.xda-developers.com/showthread.php?t=1049414
Click to expand...
Click to collapse
thats something that i have done first.
last ten days ive been doing nothing but trying to unbrick my DHD
thanks for effort.
t

You're s-off? Flash a recovery then a ROM
Sent from my Desire HD using Tapatalk 4 Beta

humzaahmed155 said:
You're s-off? Flash a recovery then a ROM
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
iam
s-on
HBOOT 2.00.0027
MICROP - 0438
RADIO 26.14.04.28_M
eMMc - boot
pure stock
locked, unrooted
hboot needs to be updated on version 2.00.0029 because htcdev doesent support any more this version of HBOOT. ican do that with the HBOOT updaters but my computer dont see my phone. the usb debugging is off.
what to do that my computer sees my phone? i tried hboot, fastboot, regular mode etc...

s-on
this post would solve my problem completely but as i mentioned computer cant see my phone. it sees it as android 1.0., no G particion and htc sync doesent work
http://forum.xda-developers.com/showthread.php?t=2286438
i hope this link would help you full to understand whats bugging me for a while.

charles66 said:
iam
HBOOT 2.00.0027
MICROP - 0438
RADIO 26.14.04.28_M
eMMc - boot
pure stock
locked, unrooted
hboot needs to be updated on version 2.00.0029 because htcdev doesent support any more this version of HBOOT. ican do that with the HBOOT updaters but my computer dont see my phone. the usb debugging is off.
what to do that my computer sees my phone? i tried hboot, fastboot, regular mode etc...
Click to expand...
Click to collapse
Ok so the SD update thru hboot doesn't work,
Have you run the RUU from your computer during fastboot?

orangekid said:
Ok so the SD update thru hboot doesn't work,
Have you run the RUU from your computer during fastboot?
Click to expand...
Click to collapse
you mean run the ruu file on computer and connect phone via cabel in fastboot usb - yes
application on comp. stuck on bootloader rebooting with the .......................... keep on going and going with no end

charles66 said:
you mean run the ruu file on computer and connect phone via cabel in fastboot usb - yes
application on comp. stuck on bootloader rebooting with the .......................... keep on going and going with no end
Click to expand...
Click to collapse
you're 100% sure you have the correct drivers?
Try it again with another USB cable too maybe.

am 100% sure my driver are ok.
i tried two more others cabels.
i thought of all that but useless.
i ran out of ideas

Running "fastboot devices" on your computer while your phone is plugged in and in fastboot mode, what does it show?

Hmm, launch the RUU exe file, then go to its app data in windows, and pull the ROM.zip file, rename it to PD98IMG.zip, stick it on your sdcard and go into hboot
Sent from my Desire HD using Tapatalk 4 Beta

bananagranola said:
Running "fastboot devices" on your computer while your phone is plugged in and in fastboot mode, what does it show?
Click to expand...
Click to collapse
nothing. device manager shows android 1.0.
htc sync says no conected devices
G particion doesent pop up - cant reach the datas on sd card
cant reach device from computer
all drivers updated and installed for sure
white screen - obviously usb debugging off
if i could see the device i solved all my problems. the rest wouldnt bug me at all - i mean on unlooking, flashing recovery and rom

humzaahmed155 said:
Hmm, launch the RUU exe file, then go to its app data in windows, and pull the ROM.zip file, rename it to PD98IMG.zip, stick it on your sdcard and go into hboot
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
already tried, doesent work.
hboot needs to be updated

charles66 said:
already tried, doesent work.
hboot needs to be updated
Click to expand...
Click to collapse
What that PD98IMG does IS update your hboot (and everything else) to what's in the RUU. And are you sure your phone is in fastboot (not hboot) when you run "fastboot devices?"

charles66 said:
s-on
this post would solve my problem completely but as i mentioned computer cant see my phone. it sees it as android 1.0., no G particion and htc sync doesent work
http://forum.xda-developers.com/showthread.php?t=2286438
i hope this link would help you full to understand whats bugging me for a while.
Click to expand...
Click to collapse
You need to flash a RUU from fastboot as you were told. The ruu needs to be for your device (match CID and Main Version) other wise it will fail. Depending on what Main Version you are you might be able to update the hboot and then unlock the bootloader. Boot the device in hboot, press power and plug it to the PC (you should see fastboot usb in red) then open a cmd in the PC and run this command:
Code:
fastboot getvar all
Paste the outcome in here deleting the IMEI

glevitan said:
You need to flash a RUU from fastboot as you were told. The ruu needs to be for your device (match CID and Main Version) other wise it will fail. Depending on what Main Version you are you might be able to update the hboot and then unlock the bootloader. Boot the device in hboot, press power and plug it to the PC (you should see fastboot usb in red) then open a cmd in the PC and run this command:
Code:
fastboot getvar all
Paste the outcome in here deleting the IMEI
Click to expand...
Click to collapse
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.1
(bootloader) serialno: SH198RX00810
(bootloader) imei: 3xxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.000s
C:\android>
here is what i got. now i have to find the RUU file that match cid and main version.
thanks mate. i ll try.
i keep you informing

try to root htc m8 i ahve red text on screen

when i tery root and s-off let the info and picture to explan more " sory for my english"
this all info
:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: 3.19.0.0000
bootloader) version-baseband: 1.29.214500021.12G
bootloader) version-cpld: None
bootloader) version-microp: None
bootloader) version-main:
bootloader) version-misc: PVT SHIP S-ON
bootloader) serialno: SH469WM04000
bootloader) imei: 357871051160565
bootloader) imei2: Not Support
bootloader) meid: 00000000000000
bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
bootloader) modelid: 0P6B10000
bootloader) cidnum: HTC__J15
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: 76df2b54
bootloader) hbootpreupdate: 11
bootloader) gencheckpt: 0
ll: Done!
inished. total time: 0.137s
​and the phone now like this
​on phon screnn
software status modified
m8-ul-pvt ship- s-on
hboot-3.19.0.000
radio-1.29.214500021.126
opendsp-v51.2.2.00593-m8974-f001015
os- ---------------------------nothing here
emmc-boot 2048mb
dec 17 2015,14.15.48.27717

So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.

redpoint73 said:
So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.
Click to expand...
Click to collapse
thanks for replay
i am not sure what exactly happend i receved th phone like as say befor
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off
2- twrp is installed
3- i use androiad one toolkit and relock again s-on
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed

The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
amira77 said:
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off how exactly did you try to s-off?
2- twrp is installed Did you also try to root at this point? Did you get stuck (no OS)?
3- i use androiad one toolkit and relock again s-on Why did you relock the bootloader?
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed You phone will only run one RUU that matches your CID/MID, you can't just run any one you want.
Click to expand...
Click to collapse
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.

redpoint73 said:
The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.
Click to expand...
Click to collapse
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100

amira77 said:
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100
Click to expand...
Click to collapse
The 1st RUU you listed won't work. It's for the AT&T version M8.
The 2nd one should work, but I don't know what you mean when you say it did not accept the phone. What exactly happened, and what was the error message? It needs to be flashed in fastboot-RUU mode, and with HTC fastboot drivers. What commands did you use to flash it? Cut and paste the command prompt inputs and outputs.
Also, I asked a number of questions in my last post in red font which you either ignored or missed. Please answer them, as it would help me understand what you did, and why.