Database Users

official at&t callerID update bricked my phone.. :(

after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!

......
noone?????

The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)

Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...

Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .

i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck

There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL

It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?

another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL

When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.

I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.

The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!

Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.

It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.

Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."

The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!

Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1

I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!

jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh

jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.

What am I doing wrong???????

Hi all,
This is my first post in this forum. Just got my HD2 yesterday & immediately set about installing a new ROM. I installed HSPL without any issues, but I'm having problems installing a new ROM. I've downloaded a couple in .exe format, synced up the phone to WMDC in Win 7, then when I start the exe file everythings fine until it starts to install, then the 4 colurs come on to the phone, and then the USB connection drops so WMDC isn't connected, then I get the error 266 (or 226). I used to have a touch diamond that did this, but I can't remember how you get the connection to remain whilst uploading the new ROM. I've had a look through the forum, but can't find the answer. Can anyone give me some ideas?? Does the phone need to have certain settings applied to it before flashing?? I'm not exactly a noob to flashing ROM's, but can't work this one out!! Thanks all.

just extract the exe, rename *.nbh to LEOIMG.nbh, put in ur microSD root, enter bootloader, press power button when u asked to do so. soft-reset when complete. feel free to pm me n i will guide u.

SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.

EddyOS said:
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
Click to expand...
Click to collapse
Hi, I'm using the same OS. I've tried running as admin but it still drops connection. The SPL is 1.42.HSPL. It just starts the update, then I see the phone disappear from the connected devices, then WMDC shuts down & a few seconds later the error message comes up??

you started flashing this fast only after one day of use

You don't need WMDC open - just close it once it says you're connected
The run the file and it should work.
As mentioned, why are you flashing it out the box? It's always best to get to know the device as it might just work as it is...perhaps try a stock ROM if you're not already using the newest one and go from there

EddyOS said:
SD card method is the quickest way to brick your phone...
Click to expand...
Click to collapse
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator

samsamuel said:
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
Click to expand...
Click to collapse
Didn't know that, glad I have HSPL on my phone now!! lol

lots don't and that's what makes sd flashing dodgy. in the case of 1.6 it can be downgraded with a 1.4 spl stock rom.its just a pain. but 2.0 spl can't. check out the horror stories in my sig.​

Yeah read about them, I nearly bricked my phone using the SD card method the first time I flashed but luckily the WMDC flash with my stock ROM got me back to normal!

I was trying to flash the stock 1.66 ROM, but it still disconnected. I have 1.43.206.4 WWE at the moment. The reason for flashing straight away, is usually the stock ROM updates are to improve / fix previous issues. This is why I wanted to start with a stock ROM & maybe move onto a cooked ROM at a later date. Does it make any difference when starting from an .exe file instead of RUU? Do you have to change something on the phone itself to allow it to stay connected?? cheers everyone for your comments.

run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash. ​

samsamuel said:
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash. ​
Click to expand...
Click to collapse
Just tried it again & still no joy. It starts, the phones switches off, thats when it loses connection, then the bootloader appears, then about 10 secounds later it says error 266 connection lost. Still stumped???

Sounds like the device isn't reconnecting with the PC once in the bootloader - try another one...

with the phone in boot loader unplug the usb and plug back into a different port. preferably a port directly on the motherboard (round the back) not through a usb hub or slot in the case.

Sussed it now. I'm a mac user using Win7 using VMware fusion. I think it was this that was causing it to not detect the phone once it had started flashing the ROM. I tried it on my work laptop running XP & voila, it flashed immediately. Thanks everyone for your comments - no doubt I'll be posting a few more questions soon!!!

ah good stuff.
todays lesson ? put all the system info in the first post!

clemo71 said:
Sussed it now. I'm a mac user using Win7 using VMware fusion.
Click to expand...
Click to collapse
Ahhh... yes, that's the kind of non-standard setup that would make sense mentioning right away indeed. Everything that touches hardware level is rarely friendly to emulation, virtual machines, resource sharing and so on...

1st lesson - use a PC!!! POW!! lol

Ok.....next question. I've tried to flash a rom using the customruu file, but all it does is open up the contents of that file. I'm using XP Pro. Any ideas why anyone???

Issue with my HD2

Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Edit: i can now connect my phone to the pc i'm trying to update to 2.13.531.1 but i got to 8% but the update froze there and the phone currently has no image version. I'm using windows 7 ultimate and ive tried to run as administrator and with xp service pack 3 compatibility.

thatg said:
Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Click to expand...
Click to collapse
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom

can someone also help me figure out how to get the ruu.nbh file off this rom and how big it should be so i can try to flash it from the sd card. thanks
http://forum.xda-developers.com/showthread.php?t=681030

zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone

thatg said:
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone
Click to expand...
Click to collapse
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom

zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
+1 or flash the phone then task 29 it.
Sent from my HTC Desire using XDA App

zelendel said:
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom
Click to expand...
Click to collapse
no i have not run hard spl so i can only install a stock rom a suppose. the exe gets stuck at 8%, i have no idea where the right nbh file is. i read somewhere when you run the exe it installs the nbh in a temp folder but im not sure i found the right one. ive also downloaded task29 and tried to run as admin but it doesnt do anything just goes to the htc install screen and stays at 0% Getting frustrating it was working fine actually before i tried to install the new tmobile software update. ive read that task29 gets rid of extra leftovers of other roms and might help the exe finish up on the phone and get past that 8% wall but it doesnt seem to be working for me

right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.

samsamuel said:
right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.
Click to expand...
Click to collapse
lol thank you for the words of encouragement, so i've extracted the .nbh file its 268mb, renamed it to leoimg.nbh tried the update from the sd card and it fails at the radio says, update terminated, update FAIL. any idea where to go from here?
Edit: i've run hspl3 on the phone is boot loader mode and have also run task29 from doloop but still get the same error with the tmobile file. 8% using the exe and FAIL trying to flash from the sd card

heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?

samsamuel said:
heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?
Click to expand...
Click to collapse
The first exe file, which got to 8 percent then went red and failed was
T-Mobile_HD2_MR_Software_2.13.531.1
After hspl3 and using task29 i tried flashing this exe which gets to 99% and fails
RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15.29.50.07U_2.06.50.04_TeleNav-5.5.42

that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl

samsamuel said:
that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl
Click to expand...
Click to collapse
i tried flashing using the .exe method in bootloader mode. next to spl it reads -2.08.hspl 8g XE
it now says
Upgrade ROM code error

ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.

samsamuel said:
ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.
Click to expand...
Click to collapse
Which do you suggest, i bought the phone so that i could ultimately install android on it. but it seems i'd be lucky to even have wm running on the thing
Edit. just tried kumars classic rom, renamed to leoimg tried running off the sd card, The update finishes successfully but after i hit the reset button on the back of the phone i just see the tmobile stick together logo and the phone doesnt boot. Do a lot of people struggle with the hd2s or do i just have a bad example here?

well unfortunately i think you may have a dud. its the radio that is preventing it from booting.
it could be the radio from that test rom, it could be something else (but still the radio)
options...
its still under warranty, speak to t mobile and/or htc, but don't mention flashing and be sure to remove hspl if you do send it back. (run hspl3, choose 2.08.0000, that's stock)
or
look on here for a user called xmoo, he knows a lot about this sort of problem, (im just good with regular flashing issues)

im having the same issue so if you believe its the radio will installing different radio maybe fix the problem?

i;ve tried installing a new radio from the sd card. it goes red and fails

It sounds like a hardware issue at this point. I'm willing to bet you fried something when you pulled the battery in the middle of the master reset.

Hope thats something htc will cover. Phones on its way over

Searched and did, Searched and did.

I tried after 2 weeks of investigation, to upgrade from 6.1 to 6.5. I downloaded hardspl and Ryans 6.5 Heavy for sprint. I read everything about doing the install. I made sure Windows Mobile Center was working and sync'd. I started the the hardspl and did everything it asked. I watched the Mogul go into I guess bootmode. The Red, Green, Blue and white, and then nothing. Somehow the phone became disconnected. According to Windows Mobile Center. I tried re-connecting and failed. I tried AFM's solution for flashing from SD card, with no change. Stuck. I copied RUU_signed.nbh on the SD card. That didn't do anything. I put the 6.1 program from HTC on the Card with the .nbh file and still no good. Beginning to think I didn't read enough. Anyone know how to get this phone back to normal again? Thanks for your time.

Hootyhoo said:
I tried after 2 weeks of investigation, to upgrade from 6.1 to 6.5. I downloaded hardspl and Ryans 6.5 Heavy for sprint. I read everything about doing the install. I made sure Windows Mobile Center was working and sync'd. I started the the hardspl and did everything it asked. I watched the Mogul go into I guess bootmode. The Red, Green, Blue and white, and then nothing. Somehow the phone became disconnected. According to Windows Mobile Center. I tried re-connecting and failed. I tried AFM's solution for flashing from SD card, with no change. Stuck. I copied RUU_signed.nbh on the SD card. That didn't do anything. I put the 6.1 program from HTC on the Card with the .nbh file and still no good. Beginning to think I didn't read enough. Anyone know how to get this phone back to normal again? Thanks for your time.
Click to expand...
Click to collapse
Just passing through here at xda, I can help you if you this evening, no time during day today. If you don't get it before then. You can reach me at ppckitchen.org in the chat section.
But until then you can post what your bootloader version says right now, in order to see what you got.
current bootloader version?
current radio version?
If your current bootloader is either the 2.40 or 2.47 then all you might need to do is flash a custom rom. Hard to tell if you don't give all the info needed to know where you are at exactly.
Also the nbh on the sd card has to be renamed to TITAIMG.nbh not left as the RUU_signed.nbh it was. SD card can be NO BIGGER than 2gig. and must have a format of FAT32.
Hit me up in ppck this evening if need be. Justpctech might be around as well.

Well thats where the problems are coming from. I'm using a 4g card and I forgot to rename the file. Yes the bootloader was 2.4. Screen says : upper right corner -RUUNBH .........Starting at left side towards top: TITA 100 MFG.....SPL-2.40.OLIPRO....CPLD-9
i believe the the problem was the SD card and the naming. Thanks so far. Heading to work at the moment but will try later. Thanks again.

Perfect, that one is best IMO.
I recommend this from where you are.
1. Flash the sprint stock rom from here Because it contains a gps radio, 3.42.02 which is fine. Now if you already KNOW you have that radio, skip this step and go right to step 3.
2. After flashing that rom when it comes to the part "tap here to align screen" : At that point instead of tapping here to align screen, do a soft reset. This will allow the customizations to NOT run.
3. Start flashing custom roms. If you don't like the one you flash, then just flash another, your bootloader and radio are good if you are on this step.
Just a note to anyone else, all you are doing is this:
1. Unlock with hardspl, 2.40 or 2.47
2. Upgrade radio to gps (this can be done by flashing that stock rom I supplied) or just putting the radio rom nbh on card and flashing.
3. Flash custom roms.

[Q] HyperdroidGBX v11 big problem

Hi Guys, i have just followed the Video for this step by step, all went well at first, right up till the check that the spl had updated, which it did ok,.
Removed the battery as in the video, replaced it, turned on and great went back into windows mobile fine.
Plugged in usb again, went into DFT_LEO_MAGLDR113_DAF folder, ran the update utility as in the video, program said it was updating, screen on hd2 changed from the rainbow screen to HTC with progress bar underneath, went on for yes about 10min with no progression showing on the bar, Then up pops an error 262 message.
I am stuck, i have downloaded a stock image from HTC tried to write it and get the message 262 again and do not know where to go from here so would like some help now if possible from you guys.
Thank you.
Jim

Did you flash HSPL 2.08 before ?
http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1894

Yes i did i followed the video completely, i tried to use 2.08 also when trying to get my phone back to stock but it would not work, in the end i flashed with
(i think) 3.03, this did allow me to go back and write the stock rom back on my HD2, so well pleased about that, but alas i am still stuck with WM and i am used to using an old G1 android phone, so really wanted android on my HD2.
Thanks

You can install it from your sd card. Just rename the .nbh file to leoimg.nbh and boot on the bootloader. That will be easier!
Sent from my HTC HD2 using XDA App

Hi guys, well have decided to go with "SuperRAM_FroYo_V1.5" on to the sd card and everything, yes everything is working very well.
Thanks for your input.