Related
So was following directions to upgrade to nuerom, and i accidently installed the old bootloader 1.2 (olipro), and so i then upgraded the ROM afterwards to the nuerom.
Well now my phone turns on and goes to the HTC screen but just sits there and does nothing.
Hard and soft reset don't change anything...what can i do?!
run the re-locker and then the 2.4 bootloader
you can find them both here
http://forum.ppcgeeks.com/showthread.php?t=9093
coffey_joshua said:
run the re-locker and then the 2.4 bootloader
you can find them both here
http://forum.ppcgeeks.com/showthread.php?t=9093
Click to expand...
Click to collapse
But it wont even connect via activesync, it just sits at the first screen you see whenever you boot your phone up...
TripFlex said:
But it wont even connect via activesync, it just sits at the first screen you see whenever you boot your phone up...
Click to expand...
Click to collapse
put it in bootloader mode first...hold down "Power Button" + "Camera Button" & press the "Reset Button" with stylus, and then try it...plus u dont have to be connected w/ activesync
no active sync
If you cant connect to active sync, open active sync on home pc go to conections and uncheck usb connection that helped me last night
rbadh91 said:
put it in bootloader mode first...hold down "Power Button" + "Camera Button" & press the "Reset Button" with stylus, and then try it...plus u dont have to be connected w/ activesync
Click to expand...
Click to collapse
if you follow his way it works but also
*please be cautious i'm new but i know my stuff*
your going to have to format the micoSD card to FAT32 with a MicroSD card reader or some type of MicroSD to SD converter(http://en.wikipedia.org/wiki/MicroSD)
(goto my computer/ right click the drive it was assigned to and click format... then under "file system" click on FAT32 then click format)
Download the rom update from HTC
Open the exe in WinRAR (rarlabs.com)
Find RUU_signed.nbh (it will be the biggest file)
extract it onto your desktop and rename it to TITAIMG.nbh
Move the file over to the formatted card and then insert it into phone.
Hold down "Power Button" + "Camera Button" & press the "Reset Button" with stylus
and done your phone should reconfigure back to how it would be "Virgin"
AtOMiiX
-CiiO kUrWa
same issue
I followed the format sd card directions, put in phone went to bootloader screen . BUT IT HAS BEEN DOWNLOADING FOR LIKE 15 MIN,
I guess my real question is did it freeze or should i let it keep going
Trying to flash from sd card Still in loading mode help
It is in loading mode for a half in hour is that normal
i have never used the sd card...bit i believe its gotta write about 50+mb of stuff to ur fone...it takes about 10 mins over usb2.0 (it doesnt really go to that speed) so i guess it can take that long
please post how long it took if it goes successful for others to know...thanks
I'm having the same problem here.
I ran the relocker, but it still says SPL-1.20.Olipro... I don't know why it didn't relock... what should I do, the SD option didn't seem to work either...
H'Roth-Gar said:
I'm having the same problem here.
I ran the relocker, but it still says SPL-1.20.Olipro... I don't know why it didn't relock... what should I do, the SD option didn't seem to work either...
Click to expand...
Click to collapse
i got it fixed...basically what you have to do is go into the bootloader like everyone said and then i reflashed it with the original rom...after that i learned that you have to run the radio in order to boot
it take 5-10 min its really fast... try it again or grab a different ROM
SD card Flashing wont work.
I Really Am stuck. Flashing did not seem to work left it in the downloading for over an hour, then gave up. (I was trying to update to DCD Titan 2.1.0, From Sprint 2.17.651.0, Radio Version 1.47.01 ORIGINALY gave me problem Stuck in htc black screen)
I wont connect activesync, or usb peroid, so I formatted SDcard to FAT32, put the Sprint 2.17.651.0.nbh file into the card renamed it TITAIMG.nbh, and tried to flash. (Loading screen for over an hour, then gave up)
Some else said somthing about flashin 3.16 because of radio issues.
(from going 2.17, to DCD 2.1.0) but I cant find 3.16.nbh. if anyone could Link me to it that would be cool.
ANTHING THAT COULD HELP ME UNBRICK MY MOGUL,PLEASE SEND
JonnyBoy313 said:
I Really Am stuck. Flashing did not seem to work left it in the downloading for over an hour, then gave up. (I was trying to update to DCD Titan 2.1.0, From Sprint 2.17.651.0, Radio Version 1.47.01 ORIGINALY gave me problem Stuck in htc black screen)
I wont connect activesync, or usb peroid, so I formatted SDcard to FAT32, put the Sprint 2.17.651.0.nbh file into the card renamed it TITAIMG.nbh, and tried to flash. (Loading screen for over an hour, then gave up)
Some else said somthing about flashin 3.16 because of radio issues.
(from going 2.17, to DCD 2.1.0) but I cant find 3.16.nbh. if anyone could Link me to it that would be cool.
ANTHING THAT COULD HELP ME UNBRICK MY MOGUL,PLEASE SEND
Click to expand...
Click to collapse
When you go into bootloader mode (power/camera/reset), what bootloader version is displayed on the screen? When you upgraded to the DCD ROM, did you also flash the new radio?
Can I add my dilemma to this thread? My Mogul also won't boot up. It gets to the yellow Sprint logo screen and then just shuts right back off.
I also, hard reset and that doesn't help. I can get to the bootloader screen but trying the Relocker means it wants my phone connected via Activesync (it calls for that in the DOS window that pops up), Activesync doesn't recognize the connection since the phone is in BL mode. Nothing I've tried so far has worked and some people on howardforums have tried to help and said I needed to install the radio only first and then go from there but I have had some trouble finding the original Radio as a download by itself.
Any takers on how I might be able to get this bad boy up and running again?
PS. I've also tried to install the original ROM found on the official HTC website and that didn't work either.
I appreicate if anyone can help both of us (the guy who posted the thread, too) out.
try extracting the relocker and then flash it.
Thanks guys this thread really helped me
s10onn2o said:
try extracting the relocker and then flash it.
Click to expand...
Click to collapse
If this is directed towards me, I extracted the relocker but I don't know what you mean by "flash it"
I thought flashing the ROM meant reinstalling a previous version or something. I've already tried running the relocker but like I said it requires an activesync connection but that doesn't work since I can only access R/G/B mode.
All the files inside the relocker are gibberish to me. Don't know what any of those things do separately.
TripFlex said:
i got it fixed...basically what you have to do is go into the bootloader like everyone said and then i reflashed it with the original rom...after that i learned that you have to run the radio in order to boot
Click to expand...
Click to collapse
Thanks, after pulling out my hair for a couple of hours, I finally was able to get it to work. The stock rom wouldn't flash at first for me, but I was able to get it to work on the third try... everything seems fine now...
willxcore said:
Can I add my dilemma to this thread? My Mogul also won't boot up. It gets to the yellow Sprint logo screen and then just shuts right back off.
I also, hard reset and that doesn't help. I can get to the bootloader screen but trying the Relocker means it wants my phone connected via Activesync (it calls for that in the DOS window that pops up), Activesync doesn't recognize the connection since the phone is in BL mode. Nothing I've tried so far has worked and some people on howardforums have tried to help and said I needed to install the radio only first and then go from there but I have had some trouble finding the original Radio as a download by itself.
Any takers on how I might be able to get this bad boy up and running again?
PS. I've also tried to install the original ROM found on the official HTC website and that didn't work either.
I appreicate if anyone can help both of us (the guy who posted the thread, too) out.
Click to expand...
Click to collapse
If you are in bootloader, try flashing the "unofficial leaked" ROM. NOT one of the custom ROMs based on it, but the complete leaked package; it includes compatible bootloader, radio, and ROM, and should get you back up and running. You should then be able to run the old relocker and the old official radio and ROM package if that is what you are trying to do.
http://forum.xda-developers.com/showthread.php?t=362403
Alright, so I obviously jumped into this a little too fast.
Right now I'm stuck at the bootloader. I tried to flash another rom, it got to about 12%, and then failed. Since then I cannot reboot into wm. I have tried tons of other roms, to no avail. I don't know why but they only get to about 1%, then the phone shuts down and the load fails.
I have tried the stock rom, and custom roms. I'm not really sure where the problem lies.
It also doesn't find my device in Sync Center. So, nearly ever tutorial says "Make a connection" as one of the first steps. I cannot do this...
Anyone have any idea's on what I can do?
Tyler
Do you have a microsd card under 2gig? If so, put the rom on the card and flash it that way instead of through USB. You have to name the file TITAIMG.nbh. Much easier way to flash. It is all in the Wiki.
http://wiki.xda-developers.com/index.php?pagename=TitanProblems
I tried that method, but actually, I didn't notice that it has to be under 2gb. Mine is 4gb. So I have to one that small? What is the reason behind that?
Tyler
I think it is because the driver needed to handle the high capacity cards (anything over 2 gig) doesn't work in the bootloader mode. I'm sure if you search around, you'll find the exact answer.
Well I just ran up to walmart and grabbed a 2GB card.
Loaded up what is supposed to be the stock rom, and no luck. It goes the gray screen, says loading for half a second, then quickly flashes "No Image File" I think, its so fast I can barely read it.
I named the file correctly. I have no idea what is going on. Now I just need to have my phone work correctly.
I was trying to get GPS to work.
Right now I have boot loader 2.07, do I need to alter that to load a stock rom? I wouldn't think so. And if I do, how do I load it, if my PC won't connect to the phone.
I'm stupid, lol..
Tyler
Ok, finally! Haha, I loaded the stock ROM on there. I didn't have the new SD card formatted correctly, had the wrong unit size. Jeez. Anywho, now on to try again..
Tyler
hellonfire said:
Alright, so I obviously jumped into this a little too fast.
Right now I'm stuck at the bootloader. I tried to flash another rom, it got to about 12%, and then failed. Since then I cannot reboot into wm. I have tried tons of other roms, to no avail. I don't know why but they only get to about 1%, then the phone shuts down and the load fails.
I have tried the stock rom, and custom roms. I'm not really sure where the problem lies.
It also doesn't find my device in Sync Center. So, nearly ever tutorial says "Make a connection" as one of the first steps. I cannot do this...
Anyone have any idea's on what I can do?
Tyler
Click to expand...
Click to collapse
If I am not mistaken, it must be under 2 Gigs because it has to be formatted in Fat32. If I am not mistaken, Fat32 only supports up to 2Gigs. Has anyone tried to partitiion the card as a 2 Gig partition in Fat32 with 1024 Allocation size.
I used to have that error when it reached 12%, actually twice with two different causes. This first one only applies if you are running Windows through an emulator or virtual machine. (could be Fusion, Parallels, etc.. on a mac or Linux)
1. Actually with a Treo 700WX ... The cause was an old version of Parallels, apparently it would "share" the USB port with the MAC OSX, each time it was "OSX's turn" it would timeout the firmware update. This was fixed by going into the configuration and setting USB for "GUEST ONLY." The problem I had was that I had selected "ASK ME EACH TIME." (while updating the firmware, your USB is temporarily disconnected and lost, without the firmware parallels would not detect it)
Another solution to this error, is to update parallels to the newest version. (the newer versions handle EVERYTHING much better.)
2. The other firmware update Issue I had, also with a 700WX, was a bad USB cable. (yes they can and do inadvertently go bad without apparent cause
hellonfire said:
Ok, finally! Haha, I loaded the stock ROM on there. I didn't have the new SD card formatted correctly, had the wrong unit size. Jeez. Anywho, now on to try again..
Tyler
Click to expand...
Click to collapse
I see so many people here with that same problem, and that is the problem I had with the SD for a while. Did you resolve the 12% issue?
I haven't tried to flash anything via the USB cable again, so I'm not sure.
But I do have another issue.. I cannot run the ##778 command. When I do, and hit talk, I get no edit button. Am I screwed?
Tyler
Just updating to keep myself records now.. Haha.
Anyways, flashed again to stock Verizon everything, the 6.1 WM stuff. Everything now works, called in a got the correct Home SID, MIN1, MIN2 numbers. But now I still have no internet.
When I type in the username and pass they provide, its like my phone does not save it. If I type it in, finish, ok. Then immediatly check the settings again, they are blank.
Anyone?
Tyler
Install DCD's Verizon (or whichever carrier you use) carrier cab. Data won't work without it.
I had already done that. But I called in, again, and they reset my internet, and now everything works.. but alas, no friggin GPS, which was the whole point of this ordeal. I downloaded the GPSToggler, and no help. I'm going to try to revert back to an older version first, and try all this again. I think during my troubles, I got a 6.1 Verizon release, which would cause it not to work. correct?
If not, I found another thread detailing how to do it within the 6.1 rom, any idea on this? Not sure if I trust it..
Tyler
Ok. Now using wm 6.5 It rocks, but still no GPS..
Tyler
Yes if you flashed a Verizon 6.1 rom then your gps will be locked. You need to downgrade then flash custom again.
Yeah, I figured that out. But I was going to do the aGPS fix, but... none of the links in the Wiki work anymore.
Tyler
what links do you need?
drewcam888 said:
what links do you need?
Click to expand...
Click to collapse
I finally got them to work. Thanks for the offer though. I'm about to try the aGPS setup. Wish me luck. Haha.
Oh, and so far, I've been through about everr DCD rom, settled on 3.2.6 Everything else had bugs it seemed like.
And all the WM6.5 Roms are way to slow and buggy. Does anyone have any other recommendations for a clean, functional rom? I could use a little more stuff then DCD provides, but I know I could cook my own...
Tyler
Bah, this is BS. I am now convinced there is no way to get GPS working.
I have just done the aGPS setup, everything went fine, but still no GPS locks.
Yes I have Location on. Yes, I have all the External GPS settings correct. I'm using Google maps, maybe I'll try another program.
What gives?
Tyler
I appologize in advance if there is a lot of information about this but I have searched and searched and haven't found anything as of yet. I have the Verizon Touch Pro with the newest V2 stock ROM from several months back. Now I am interested and going back to a custom ROM. I have tried the latest HardSPL (I think it was 0.35) and when I run it I get "Loading..." on the TP and eventually "ERROR [260] : CONNECTION". If I pull the battery and put it back in it boots up to the way it was so clearly nothing is getting programmed. I have tried it on 3 computers and get the same thing. I had programmed it many times in the past successfully but that was before I upgraded to the V2 stock ROM. I'm wondering, is it that upgrade that is causing the problem? I have not tried via SD card yet but I plan to at some point today.
Thanks,
Tbone
Ok, I put the Verion HardSPL on my SDCard root and renamed it RAPHIMG.nbh. I forced the phone to the tri-color screen by holding power and volume down and then pressing soft reset. It flashed the tri-color and then went immediately to "Loading..." and has been there for 10 minutes. I do remember that when I did this previously it would ask if I wanted it to load the ROM and that is not happening. Any ideas?
Thanks,
Tbone
Ha, I got it. I put the ROM on the SDCard and then copied over VZW_TP_SSPL-Manual.exe and ran that on the TP. It initially showed "Loading..." and then quickly changed to "Checking..." followed by the option to load the rom on the SD card. Not sure if this is the only way to do it once you have installed the V2 ROM but it seemed to work at least with HardSPL. Interestingly, I then put the custom ROM on the SDCard and re-ran the SSPL and this time it went to "Loading..." and stayed there. So I reset and forced the boot in to the Tri-Color screen and this time it got past the "Loading..." screen without a problem. I'm definitely a bit puzzled over this but I'm now up and running with a custom ROM again.
Hopefully this might be helpful to others.
Tbone
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.