Develop Bugs

[Resolved] Boot Loop Issue -- please help if you can!

I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
EDIT: Now resolved after following thoroughly the directions listed here:
http://forum.xda-developers.com/showthread.php?t=721055
Thanks for helping me out!

aikeru said:
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
Click to expand...
Click to collapse
i had a similar issue, and so did a few people. i wrote out a post some time ago, i don't know if you read it...
http://forum.xda-developers.com/showpost.php?p=7204861&postcount=4
try that out. let me know how it goes.
EDIT: it also sounds like you don't have nand unlocked.

Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.

aikeru said:
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
Click to expand...
Click to collapse
having a boot recovery program doesn't necessarily mean you have nand unlocked. the ability to flash custom roms does though. good luck! i know it's frustrating, but keep at it.

silly question but are you wiping correctly ?
I had to ask...

elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
i almost spilled my drink LOL

elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back

aikeru said:
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
Click to expand...
Click to collapse
lol good luck buddy. it's a relatively easy walkthrough if you follow it closely. post up any questions you have.

EVO stuck on bootloader no recovery tried several PC36IMG none help :((

Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?

Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App

you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.

At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.

Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App

HTC EVO stuck in BAD boot loop.. need HELP

I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.

Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.

Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App

That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.

And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?

What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.

I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.

HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.

Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx

teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!

tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.

Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7

HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702

No, MIUI is not based on CM. It's a completely different ROM

Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702

It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!

I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....

I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.

Rooting Success!

As I am a junior member, I do not have the permission to post in the android development section. But i believe that my past experiences can be helpful to those who are attempting to root and are having trouble along the way.
My mom and I both have the DInc2 (long story haha), and about six months ago I rooted mine. I first used the HTV Dev Unlock, but that didn't really do anything, because I realized I had the newest update. So I relocked it, and then used the tacoroot method to root my phone and then Revolutionary. Everything seemed to work fine as long as you changed the radio name to PG32IMG.zip instead of the long one they give you. Seven hours in the hot office paid off, and my phone is currently running CM7.2 with aeroevan's 15 kernel (who needs pictures?)
Today, however, I went straight to the tacoroot method on my mom's phone, and about maybe the tenth step, where you have to type
adb shell /data/local/tacoroot.sh --root
adb wait-for-device
it just got stuck. and after maybe 20 minutes of petting my cat, nothing happened. so i pulled the plug and attempted to start over again. now i don't know if thats what went wrong, but the second time i didn't type the second line and everything worked smoothly.
after i finished tacoroot and revolutionary, i reboot the phone and it got stuck in bootloop. now i heard many stories about bricking and it scared me, because my mom would kill me if i had destroyed her phone. i tried many things. i flashed the radio under the PG32IMG.zip name, but that didn't change anything. i even flashed CM7.2 and it just got stuck on the blue android man instead of the droid eye. as a last resort, i went into recovery and did a factory reset, and voila, everything just fell into place!
now i know maybe all this is out there somewhere, but i hope my experiences can still help others!

Dang I wish I could help. I'm sure someone will know how to fix it though. When I rooted mine everything worked flawlessly.

Did you factory reset before flashing cm7.2? You didn't mention that, so maybe that's what ended you up in a bootloop.
Sent from my SCH-I535 using xda app-developers app

Stuck in a very, murky, muddy, Desire HD puddle......

Right. Here we go.
Yesterday, I used HTC devtool and easy ace tool to be rooted and unlocked bootloader. Im still S-On. Ace Pvt Hboot.
Had all sorts of problems. Firstly, with PacMan, which looked and worked fantastic, except no GPS lock, AT ALL, (important to me) soi tried Jellytime and CFX, but all three had issues, and GPS worked on none. I believe this is because the radio is the original one, but dont have the knowledge, skill, or importantly courage to flash an updated radio.
So, tried to flash and EXT4 recovery, with the tool from Google Play. Will not work. Saves to a folder on SD but still boots in CWM recovery So I cant use EXT roms properly. I tried to go back to PacMan, but I cant even do that. I wipe and format, and reflash the boot image, but every time it wont load correctly - something ddoesnt work, and I get errors. Latest was Android Keyboard is not working, so I cant do anything!
Attempted to put ViperDHD rom on to go back to something like stock (GPS worked great on stock!!) and worked ok, with some funny issues on initial boot but settled down. But, STILL no GPS.
Decided stuff it, go back to stock . Downloaded stock RUU and attempted to install, but, of course, it wont work.
So, in short, I have a fantastic Desire HD, that wont flash EXT4, wont go back to stock on RUU, and I cannot find a ROM that will work with GPS. On some, wireless doesnt work either.......
So, if someone could help me to either make my GPS work on ICS or Jellybean, or, help me go back to where I was, (GPS working!!) before I started all this, I'd be eternally grateful. I dont have money to spend on a new phone, so I'll even put some money in your development coffers as a thankyou for helping me out. I just need me smartphone to be smart again, not the useless pile of Sh*te it is right now
My previous post about lack of GPS proved fruitless, no replies. BUt I am hoping that one of you Desire HD gurus will rise to the challenge that I face right now and help. I cant but you a beer, I cant do much at all, but of you help me fix my problem I will, I promise, be eternally grateful. I'll even send your missus flowers by Interflora if that helps!!!:silly: Seriously, I really need someone who knows there stuff to give me a hand out of a hole.
My thanks in advance.
Phil

Hey there. Seems like you've gotten yourself into quite a little mess there.
First of all, I'd recommend you flash BlackICE. Its a Gingerbread based ROM but I know for 250% fact that it is rock solid and the GPS works.
After that, I believe you're going to have to manually flash the recovery using fast boot (hit up the link for the Ace Think Tank in my signature for guides and any additional help you might need)
Finally, another bulletproof ROM I recommend is IceColdSandwich. I personally know that this ROM is 100% stable and that the GPS works.
If you need any additional assistance, feel free to post in the Ace Think Tank. And as always, be sure to drop a thanks if I helped or anyone else helps!
Edit: ViperDHD isn't based on stock my friend. Its based on the One V stock ROM as far as I know, so its been ported from that. An amazing stock based ROM is Android Revolution HD, which I've tested personally and found to be bloody amazing!
Also, the RUU won't flash as you'll have to relock your boot loader. Use fast boot to to that if you still want to return to stock
Edit 2: also. Please refrain from creating multiple threads. I know its tempting but the desire HD is slipping into the legacy stage, where I treat and development is slowing down. If you must get an answer quick, either 'bump' your thread (simply post the word 'bump' and it'll push it to the top of the list, so it'll show as unread. Be aware that you can only do this once every 24 hours) or post in the Ace Think Tank.
Thanks
- Sent from Guy's Super Duper S3

GuyInTheCorner said:
Hey there. Seems like you've gotten yourself into quite a little mess there.
First of all, I'd recommend you flash BlackICE. Its a Gingerbread based ROM but I know for 250% fact that it is rock solid and the GPS works.
After that, I believe you're going to have to manually flash the recovery using fast boot (hit up the link for the Ace Think Tank in my signature for guides and any additional help you might need)
Finally, another bulletproof ROM I recommend is IceColdSandwich. I personally know that this ROM is 100% stable and that the GPS works.
If you need any additional assistance, feel free to post in the Ace Think Tank. And as always, be sure to drop a thanks if I helped or anyone else helps!
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
Thanks for coming back to me mate, it is greatly appreciated.
Ok, deep breath, and after my above and considering your reply, I ihave flashed an EXT4 recovery from Fastboot, but, this will not load. Goes to HTC screen and stops. Im sure I can put it right with EasyAce which I will try now.
I will try then to put Black ice on as you advised and post back.
really appreciate your advice!

addictR3 said:
Thanks for coming back to me mate, it is greatly appreciated.
Ok, deep breath, and after my above and considering your reply, I ihave flashed an EXT4 recovery from Fastboot, but, this will not load. Goes to HTC screen and stops. Im sure I can put it right with EasyAce which I will try now.
I will try then to put Black ice on as you advised and post back.
really appreciate your advice!
Click to expand...
Click to collapse
Seems I cant boot into a recovery at all now. Tried to reflash with EasyAce tool but getting errors. I dont have a working recovery, so cant flash a rom

Ok, somehow, via the red wine and stress induced fog, I managed to get EXT recovery working. Im now tryig to get a rom working. Tried PacMan again, bit straight off I get AOKP keyboard not working error and I didnt have to go through the Google setup - why cant I get a clean boot - this confuses me?? I wipe Cache, Dalvik. Factory reset - same problem. I have even tried formatting system from Advanced - same????
At least I can flash RIMs now!!
Thanks again for your help

You are still s-on yes?
Have you flashed boot.IMG?
If you are s-on you must flash the boot.IMG (contained inside the ROM's zip file) using a PC and "fastboot flash boot boot.img" every time you change to a new, different ROM.
Sent from my GT-I9505 using xda app-developers app

I have indeed mate, one thing I learned early on.
I have managed to get JellyTime on ok, but, again, no gps and also the potentiometer for the compass etc appears to not work!! Arrrrrgh!!!!
I think the issue must be the radio. Can I flash a new radio if im S-On and bootloader unlocked? Im ok with fastboot stuff if I need that to push a radio, but, I read that flashing a radio is inherently more "dangerous" than flashing the recovery etc.
I hoped the EXT4 recovery would make a difference, but seems not to have at all. FWIW, I also did the GPS antenna mod yesterday, and it hasnt helped either. My gps appears to work, but its very poor. I left it outside for 10 mins last night looking up at clear sky and it didnt show one satellite.
Think it might be time to sell the phone

You need to be S-Off to flash a radio.

I still cant get my head around why I cant get PacMan back on ok? It worked a treat first time, except for gps. Now, it will not install properly at all. It boots ok, but straight away I get keyboard has stopped working, and it doesnt go through the account setup etc.
But the potentiometer works!!!!!

Where I am at now.
Put CWM recovery back on, and tried Cyanogen 7.1. Would not boot. Several attempts at wipe and reflash did not cure this. So I am now running Android Revolution HD7.3. I thought as it was close to a stock ROM it may work, but, still no joy.
I put other halfs Desire HD next to mine and started the GPS on them both. Hers locked in less than a minute. Half an hour later, I had seen one brief flicker of two satellites on mine, Still no fix.
So, I dont know what to do really. I ish I could put the phone back to how it was, but doesnt look like that is going to be an option. Tried the RUU, but it doesnt work
I still cannot understand why none of these roms will work with the GPS when it was perfect before on stock 2.3.5??

What's wrong with the RUU? I would try flashing a fresh recovery image from fastboot, then wiping everything under the sun and flashing ARHD again.