Database Users

[Q]How to S-OFF your HTC Legend?

Hello,where can i found a good and easy tuto to make the legend s-off???
I cant find a clear step by step
Thanks a lot !!!!

Hi.. Step by step is given in the process..
Just go to www.alpharev.nl download the iso and boot it.. Then you are instructed..
Othervise search the development section.. There are 2-3 threads regarding this issue..

How safe is this? I am concerned about modified HBoot and partitions, as surely this is the stage that can brick your phone.
There were a lot of horror stories when it came out, have things settled down?
EDIT: I would say it's not very safe at all. My first impressions are that the script is fraught with danger. First try failed to copy files and aborted (perhaps I said yes to install Clockwork Recovery when I already had it?), 2nd and 3rd tried it simply didn't go into fastboot despite pressing the power button loads of times. Each time a nervous battery pull.
Given up, before I end up with a bricked phone.

If a make a nandroid and something with s-off go bad,can i restore the backup and everything is ok?

dangal said:
If a make a nandroid and something with s-off go bad,can i restore the backup and everything is ok?
Click to expand...
Click to collapse
No, if HBoot flashing fails, the phone is bricked.

Ok,was easy,make a iso boot cd,3 steps and everything is ok i have s-off in the legend

@CrazyPeter: I think it's more scary than dangerous. The timing in step 1 and 2 is way off, but step 3 is straight forward(this is the dangerous part). You just have to make sure the phone is connected.
Edit: I had to count to about 4.5 seconds after the -------> before pressing power. When it tells you to press power it's to late.
Sent from my Legend using XDA App

You certainly need to know what you are doing.
It's VERY possible you get lucky and get past stage2 but fail on stage 3 timing, if this is the case, then you have a partly updated boot and you need to boot recovery and nandroid backup (in the Advanced restore) the Boot partition and then try everything from the beginning again.
It took me 5 times round this route. It wouldn't be so bad if the script detected that you were restarting after the first timing critical bit and carried on from there.

As I remember there are no timing on step 3, only 1 and 2. Once you get past step 2 it's pretty easy. It can still go wrong though, if you loose connection when the bootloader is flashing during the 3rd step.
Sent from my Legend using XDA App

Now i have S-off,to enter in recovery mode what is the bets method?

Hello!
I've read lot of different topics here, but still cannot find exact answer for my questions.
I have a HTC Legend Device with S-ON.
It's CID is HTC__038, and HBOOT version is 1.01.0000
Do I have any chance to S-OFF my device? Does success of S-OFF'ing depends on how fast you press buttons during procedure? Can I still use custom ROM's without s-offing my phone?
Thanks a lot!

vpupkin said:
HBOOT version is 1.01.0000
Do I have any chance to S-OFF my device? Does success of S-OFF'ing depends on how fast you press buttons during procedure? Can I still use custom ROM's without s-offing my phone?
Click to expand...
Click to collapse
You cannot S-OFF your Legend if the HBOOT version is above 1.00.
The chances of an S-OFF success do not solely depend on "how fast you press buttons".
You can still use custom ROMs without S-OFF.

S-OFF
Can i use AlphaRev 1.8 HBOOT reflash utility with temp root to get S-OFF, i have an unbranded legend, open network phone (not sim locked) and HBoot 0.43.0001, Radio- 7.05.35.26L, I'd like to try CyanogenMod. I have been trying to root my phone using paul modaco's tutorials with no luck. Please help

To install AlphaRev your Legend must be rooted first.

stock hboot (0.85.0005) ignores S-OFF?

Hi all,
today i discovered something strange and i like to get your opinion on that:
I am not able to do s-off things in fastboot even if i have s-off!
Situation:
Phone: Desire Z
HBOOT: stock 0.85.0005
FW: 1.34..
Rooted: did root, supercid and s-off via gfree and verified via gfree_verify - even hboot showes up S-OFF
ROM: GingerVillain 1.5
Recovery: ClockworkMod 3.0.0.5
Problem:
First of all, i myself have no problem, but i started experimenting after a friend semi-bricked his desire z with same setup.
I did a nandroid backup and when i boot into hboot and do a 'fastboot flash recovery recovery.img' (with my nandroid recovery.img) i always get a remote: not allowed.
Now from my point of view this should only happen if I have a S-ON and should be impossible with S-OFF ?! Even using 'fastboot oem rebootRUU' does not change anything.
The thing that concerns me about that is: If something destroys both system and recovery, your pretty much screwed + bricked because hboot is not allowed to write to something other then cache and all of this basic stuff doesn't work:
- flash recovery with CW
- flash a complete zip
- flash an other hboot
- RUU
When I rooted my phone i have read everywhere that eng-hboots are not necessary any longer. But it appears that they are the only thing that helps and you have to install them as long as you have a working ROM.
Any thoughts on that issue / can you reproduce this / are fastboot actions logged anywhere?

You need a ENG. HBoot to use fastboot commands, doesn't matter if your s-off.

yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005? i did some experimentation with a goldcard, but at least remote commands didn't change in behaviour..
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here

DragonTEC said:
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005?
Click to expand...
Click to collapse
maybe thru a modified PC10IMG.zip
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
Click to expand...
Click to collapse
My thoughts exactly, its kind of a safety if you can't boot into android.

i'm not sure if a PC10IMG.zip will help at all.. my friend tried flashing both 1.34 and 1.72 RUU ROMs as PC10IMG and this didn't change anything.. in fact, the 1.72 even didn' install the new .00008 hbott, so i thing there is some heavy write protection in the hboot making it more or less useless..
what i can imagine that works is aa gokldcard with sppimg.zip, but i haven't yet found one for the desire z..
i have the feeling that this is a huge problem because with a short research i have found at least 3 threads of people having bricked their phone exactly this way and are now stuck.. some of the experts here might pay attention to this problem and in my opinion you should also consider removing the 'a eng-hboot is not needed, don't use it' advice from the rooting section of the wiki..

So what exactly is your problem.
You destroyed recovery and system?
If yes, and you used gfree to get Super-CID just install an PC10IMG that has a version higher or equal to the main version in you misc partition. And then do the whole downgrading, rooting, flashing recovery again.
If you are not Super-CID you might need a goldcard in addition if the CID of the phone is not supported by the PC10IMG that you whant to install.
have fun Guhl
It is almost impossible to brick this phone. The only possible way might be a failed copy of the eng-hboot and this is why the warning is and stays in the wiki.
Sent from my HTC Vision using XDA App

I thought so, too, but when flashing a newer original RUU using the PC10IMG.zip, the flash process runs okay, but after the restart nothing (still hangs in HTC screen, no new hboot) changes so apparently no changes are made..
So from my point of view the phone is more or less bricked.. i guess maybe some custome PC10IMG with an eng-hboot might change this, but i only found one for the G2 and wasn't able to find one for the DZ.. Thats why I thing that removing the 'UNNECESSARY' advice is justified (of course i don't want the warning advice that this can brick the phone to be removed)..

[Q] Have tried everything, can't fully root

I've seen about 20 posts on how to root my Mytouch 4G, but I still can't do it! When I try and run SU, I get errors. However, I've managed to S=OFF, which I can't even imagine how. Here's what my boot screen is showing:
Glacier PVT ENG S-OFF
HBoot-0.85.2007 (PD1510000)
Microp-0429
Radio-26.03.02.26_M
eMMC-boot
OCT 11 2010, xx:xx:xx​
There seems to be a few different set of instructions, but none seem to be working. I've tried the VISIONary way, as well as the other methods.

if you are s=off with the .85 engineering screen all you need to do is download VISIONary.apk
Temp root
perma root.
done.

Thanks N, but I can't seem to get that to work. I have Visionary r14. Also, when I reboot, at the loader screen, I started seeing some "pxxxx.zip" files getting errors, such as "wrong image". Not sure what I need to do...

Chicago T said:
Thanks N, but I can't seem to get that to work. I have Visionary r14. Also, when I reboot, at the loader screen, I started seeing some "pxxxx.zip" files getting errors, such as "wrong image". Not sure what I need to do...
Click to expand...
Click to collapse
I have the same screen as you with the eng bootloader.
When I do volume down + pwr I also get the boot screen and goes through a pd15img wrong image yada yada.... I thought that was normal????
However I have s off and su works for me in terminal.
Sent from my HTC Glacier using XDA App

The root methods follow this pattern:
1. Temproot with VISIONary
2. Run a script to get S-OFF (I recommend gfree for this)
3. Permroot with VISIONary
You have the Engineering bootloader (HBoot-0.85.2007), so I assume you used the root.sh script. Did you attempt permroot with VISIONary afterwards? That should be all you have to do (make sure to uncheck temproot on boot when you do).
Ignore that stuff about PD15IMG, that's normal. The bootloader is looking for a file on your sd card named PD15IMG.zip and isn't finding it. That zip file (which you can find on these forums) is used to revert back to stock.

If you have s-off all you have to do is temproot again, flash clockwork recovery, and flash away. My phone did same thing, once you get a recovery you're good to go.

what neidlinger said. plus,
"You have the Engineering bootloader (HBoot-0.85.2007), so I assume you used the root.sh script."
the main gree thread also has a bootloader part which is what i used - he could have done that too, which is diff than root.sh. i think we dont really know how he got to where he is.
chicago- what i learned when i rooted is that gfree or your method just turns s=off. that's not rooting, it's just removing radio security so that you can then root- you still like neidlinger said have to then run visionary+ to do it again.
you run it once to let gfree or root.sh work, then you run it again to actually gain root. the only thing is that i would download visionary+ 11, as many instances have shown that 14 doesnt do the job on some phones. 11 is older, but seem to work more often. uninstall 14 and install 11.
just run it, make sure "set to rw" is checked, nothing else checked. make sure usb debugging is checked on your phone. than reboot again after running visionary, you should be ok. my 1st time i ran it, it hung. then i removed the battery, and in terminal i couldnt get su. i ran visionary+ 11 again, with the settings described, then rebooted, and boom, i was su.

Also make sure you don't have a PDIMG15.zip or whatever it's called on the root of your sdcard or that'll keep effing up with bootloader. And make sure "temproot on boot" isn't checked cause that kept screwing up my roots too. Following jdkoren's instructions should get the job done for you. Good luck!

yeah i forgot to also say the i get that looking for pdming whatnot when i boot into hboot, but i thought that was normal - looks like it always checks for a zip file it needs to restore stock, and when it doesnt find it on the SD root, it assumes you dont want to, or need to restore your phone, which is good.... one day when you need to restore, you could put that file on your sd card, reboot, and boom, it'll pick it up.
so, it's normal it seems.

S-ON and S-OFF

Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old

Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed

XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.

What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.

How is the progress on fixing your phone?

jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary

I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off

How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.

PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader

If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.

PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha

Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.

PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help

PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it

Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.

BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.

PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off

Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.

PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio

Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash

Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash
ok. here goes.
On rebooting my phone last night it doesnt come back on. It vibrates 3 times and the LED flashes orange.
The only way it comes back on is if i take out the battery for a while and then power it on again.
here is a chronology of what happens.
reboot or power down
devices powers off but doesnt restart. vibrates 3 times and the LED flashes orange.
pull out the battery and SDCARD and wait a minute.
After this I can now boot into CM7
Reboot or power off to restart. same thing happens again
this happens everytime i power down the device
things i have noticed
on plugging it into my PC it recognises my device as a qualcomm_cdma_technologies msm desire and tries to install drivers for it.
this is the first time i have seen this. My device is GSM based and i am on tmobile UK.
Device can never power back on immediately from power off. just vibrates 3 times, LED flashes. Only comes back when i pull battery and SD and wait a few seconds before powering it back on
What i have tried but they all dont solve it
flashing a new cwm recovery. i am able to flash a new one from rom manager but doesnt solve the problem. currently on Rom manager 4.2.0.2 and CWM 3.0.2.6
formatting my SDCARD through ROM Manager.
doing a full wipe and reflashing stable CM7.
all of these completed successfully with no errors
What i can do successfully
i can boot into bootloader and recovery from commandprompt or using the power+volume down combination. doesnt always power on because of the no boot (start) problem .
i can do "adb devices" and successfully see my device as HT0****** in the list of devices
On the terminal app, on typing "su" it gains root permission successfully.
i can succesfully access my SDCARD using astro and also using mount usb storage in recovery.
device information
HTC DEsire hd.
CM7.0.3 stable, previously on nightly CM_ace_full 83
ROM manager version 4.2.0.2
CWM 3.0.2.6
Radio 26.09.04.11_M2
hdboot-0.85.2007 (PD9810000)
ACE PVT ENG S-OFF
USBdebugging always on
please let me know if any further information is needed and how to get it.
I really need some help. I have trawled the forums and i am starting to believe that i have a partially bricked device or a usb brick. I havent seen any real solutions or any post with a problem like mine so i want to be sure that that is the issue before trying the fixes there. Is there any thread for fixing a Desire HD USB brick, because all the ones i have seen do not have a definite fix.

Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.

andyharney said:
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
Click to expand...
Click to collapse
Thanks andy.
In flashing the HTC RUU. is that the process of removing root?. because i was thinking of removing root and then sending it back. but thought there might be a software fix for it i could try first.

Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.

andyharney said:
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
Click to expand...
Click to collapse
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.

santet said:
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
Click to expand...
Click to collapse
I recently had to send mt phone back to HTC. What I did was flash the RUU, temproot and revert to stock CID (don't know why I didn't do this first) then flash the RUU again just to make absolutely sure that all was well.

Yeah I would use the tool to change Radio S-OFF to ON and restore the CID before you run the RUU. You will save yourself a lot of time and effort.

ok. on first try i already have a problem. i downloaded the easy radio tool.
connected my device with usb debugging on. run the application as administrator. clicked on Stock CID (my device is unbranded desire hd) started up, notified as pushing file to sd. reurned with unknown error, probably connection.
i tried the same with Radio S-On. same response.
i am doing this before flashing the new RUU i downloaded which is version RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed.zip.
what have i done wrong?

Don't panic your ok,
It just means you will have to run the RUU first then run Visionary+(r14) to get temp root then run the Radio S-OFF tool.

I have gone through all the steps with no glitches. How do i verify that my device no more has radio S-On and is fully returned to stock enough so as not to voide warranty. I have the stock ROM installed.
I also want to try updating using the recent OTA update and use the device a while to see if the problem returns before returning it to HTC.

If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.

andyharney said:
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
Click to expand...
Click to collapse
Funny enough no more problem of being unable to reboot.
I have installed titanium.
i want to update to the latest OTA 2.3 update for the desirehd. do you know if the visioinary root and the the easy radio tool for s-off work after that update which i believe is the latest one.
I will use the device in its stock condition for two mpore days and if i do not have any more issues then im going to install a custon rom once again.
Thanks loads for all the help.

If you upgrade to 2.3 (2.36.405.x) then Visionary+ no longer works, you have to use GingerBreak instead. You can still downgrade to an earlier firmware.

I tried rooting again using visionary. got the same problem after applying permroot and then using the easy radio tool for S-OFF. After applying permroot it booted fine. But after applying S-OFF and SUperCID it goes back to same error and doesnt boot again. It seems then that it has something to do with the rooting process.
I will post a new thread asking if anyone has been unable to complete the S-OFF and SUPERCID process .

Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.

andyharney said:
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
Click to expand...
Click to collapse
I did exactly as you said using temproot so as to be able to turn apply S-OFF and the stock CID.
but after i did that and it worked i just tried rooting once again permanently and had the same issue. I have updated to the OTA update and i will use that for a while as when reading the gingerbreak threads people do not seem to trust that it works fine.

I just re-read my last post, sorry if I came across as a d*ck, that was not the intent.
I would remain stock for a few days to see if that has an affect. If rooting is the cause of your issue, I doubt HTC will repair it because it has booting problems once rooted.