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???
Related
Help!
First time attempt at using HPSL and may have bricked my HD2 :-(
I have a Voda supplied HD2 so can't install the stock ROMs directly...I thought I would be able to do so via HPSL, but it seems not. I was trying to install 1.66 (UK WWE) following the HPSL for dummies guide, and did the following:
- installed HPSL onto HD2, confirmed by going into bootloader
- put nbh file (extracted from stock .exe) onto SD card, named LEOIMG.nbh
- entered bootloader and chose flash option via power button
- flash started (minimal progress)
- within 2mins error showed
- now going into bootloader shows
00028002
Not allow
then..
SPL-1.42.0000 :-(
Upgrade ROM code error Please try again
If I start normally I get a warning triangle.
How can I get my HD2 back from the dead, ideally with 1.66 rather than the crummy Voda 1.43? (can anyone point me at a stock ROM for the voda 1.43, perhaps that would at least unbrick it?)
Help!!!!
*EDIT* Currently downloading the Voda 1.43 image, hoping I can at least get that back and running...if that works will still be keen to find out how to apply stock 1.66 via HPSL (bearing in mind that the CID lock(?) means I can't apply 1.66 on my voda device thru normal means)
CraigBruce said:
(can anyone point me at a stock ROM for the voda 1.43, perhaps that would at least unbrick it?)Help!!!!
Click to expand...
Click to collapse
The 3rd sticky down in the HD2 ROM Development thread is titled, "[REF]Leo Official ROMs" - Click that.
Then click, "Shared folder for shipped Leo ROMs".
The first "box" will have the title "Leo 1.43" under it. Click the hand carrying the folder icon.
You'll be greeted with 3 ROM's, select RUU_Leo_Vodafone_UK_1.43.405.1_Radio_Signed_15.26. 50.07U_2.04.50.22_2_Ship.exe and download it.
Hope that helps.
Good luck with getting your phone back up and running.
Your device is not bricked. I think you have not installed HSPL properly.
Try installing HSPL again. As it seems your HSPL is not installed properly. Follow the following instructions very carefully :
Connect your phone to USB
I think when you boot in by default your device goes into bootloader if not press volume down + power butoon on the same time, your phone will enter tri color bootloader mode.
At the bottom of your screen it shoul show "USB"
Now download the HSPL.zip file(I have attached it here)
Now run HSPL.exe and follow the onscreen insteuctions.(Mostly you have nothing to do it will start installing automatically)
After a while on the screen of your phone a text will appear saying "We hacked it". If this text is displayed then everything went ok. Now confirm by clicking yes on the computer screen and it will finish the process.
All done.
Your phone will restart.
If you want to check that your fone has HSPL then press volume down+power key at the same time. The phone will enter into bootloader and should show "cotullaHSPL".
Now you can install any ROM and it will run properly.
Thanks - had just found that and started downloading as you posted this..fingers crossed! If this works will still be keen on ways to apply 1.66 (stock) to my voda CID locked device.
ankush1492 said:
Your device is not bricked. I think you have not installed HSPL properly.
<snip>
After a while on the screen of your phone a text will appear saying "We hacked it". If this text is displayed then everything went ok. Now confirm by clicking yes on the computer screen and it will finish the process.
All done.
Your phone will restart.
If you want to check that your fone has HSPL then press volume down+power key at the same time. The phone will enter into bootloader and should show "cotullaHSPL".
Click to expand...
Click to collapse
This is exactly what happened 1st time I installed HSPL...however trying it again did get the phone back and apparenty healthy again....thanks!
So - 2nd attempt to flash the 1.66 ROM, same as before. Confirmed HSPL installed via tri-colour bootloader screen, selected (via power button) option to flash from SD. Progress bar gets to (max) 10%, Warning triangle briefly shows then phone goes back to tricolour bootloader (but with std. SPL version) and nothing more happens.
Should I be waiting longer ? i.e. is the phone potentially still flashing when on the tricolour, std. SPL, screen ? Not flashed an HD2 before so not 100% sure I'm doing this right..will double check videos on this site, sure I'm just being stupid/impatient/not read enough....may try downloading the ROM again incase corrupted.
Anyway, HSPL installed for 3rd time and phone appears fine back running with 1.43.
People please read the HSPL thread properly, once you have installed the HSPL you CANNOT install from SD card you HAVE TO USE THE PC to install any rom images that are not original HTC.
CraigBruce said:
This is exactly what happened 1st time I installed HSPL...however trying it again did get the phone back and apparenty healthy again....thanks!
So - 2nd attempt to flash the 1.66 ROM, same as before. Confirmed HSPL installed via tri-colour bootloader screen, selected (via power button) option to flash from SD. Progress bar gets to (max) 10%, Warning triangle briefly shows then phone goes back to tricolour bootloader (but with std. SPL version) and nothing more happens.
Should I be waiting longer ? i.e. is the phone potentially still flashing when on the tricolour, std. SPL, screen ? Not flashed an HD2 before so not 100% sure I'm doing this right..will double check videos on this site, sure I'm just being stupid/impatient/not read enough....may try downloading the ROM again incase corrupted.
Anyway, HSPL installed for 3rd time and phone appears fine back running with 1.43.
Click to expand...
Click to collapse
Yeah, the 1.66 ROM you've downloaded may be corrupted. And next time, try installing the ROM with USB connection and the ROM's .exe file. You SPL is reverting back to stock, so it's possible that the culprit is flashing with SD.
OK, problem solved...
Rather than installing the stock ROM via HSPL bootloader I installed HSPL and then ran the RUU exe for the stock ROM. Phone now upgraded
dragon_soft said:
People please read the HSPL thread properly, once you have installed the HSPL you CANNOT install from SD card you HAVE TO USE THE PC to install any rom images that are not original HTC.
Click to expand...
Click to collapse
Thats not true, you can flash custom roms with hspl from an sd card
see my video *here*
dragon_soft said:
People please read the HSPL thread properly, once you have installed the HSPL you CANNOT install from SD card you HAVE TO USE THE PC to install any rom images that are not original HTC.
Click to expand...
Click to collapse
[★] said:
Thats not true, you can flash custom roms with hspl from an sd card
see my video *here*
Click to expand...
Click to collapse
I believe Dragon Soft was possibly referring to not using a stock ROM from SD? If I remember correctly flashing a Stock ROM from SD with HSPL on will remove HSPL.
So in other words, if you have HSPL and want to have a stock ROM, it is best install it from the PC when connected via ActiveSync as this won't affect the HSPL.
Custom ROM absolutely no probs with flashing from SD, the HSPL will stay intact, good work on the video ★
CraigBruce said:
OK, problem solved...
Rather than installing the stock ROM via HSPL bootloader I installed HSPL and then ran the RUU exe for the stock ROM. Phone now upgraded
Click to expand...
Click to collapse
Ok. I think you were trying to install official ROM. When you install an official rom your bootloader will revert back to SPL...
dragon_soft said:
People please read the HSPL thread properly, once you have installed the HSPL you CANNOT install from SD card you HAVE TO USE THE PC to install any rom images that are not original HTC.
Click to expand...
Click to collapse
thats not true. After HSPL you can intall directly from sd card..I have done it almost 100 times.
Ibb1982 said:
I believe Dragon Soft was possibly referring to not using a stock ROM from SD? If I remember correctly flashing a Stock ROM from SD with HSPL on will remove HSPL.
So in other words, if you have HSPL and want to have a stock ROM, it is best install it from the PC when connected via ActiveSync as this won't affect the HSPL.
Custom ROM absolutely no probs with flashing from SD, the HSPL will stay intact, good work on the video ★
Click to expand...
Click to collapse
Well if he does mean that then fair enough, I just thought that he meant custom when he said "that are not official" but whatever, sorry for the mis understanding
Ibb1982 said:
So in other words, if you have HSPL and want to have a stock ROM, it is best install it from the PC when connected via ActiveSync as this won't affect the HSPL.
Click to expand...
Click to collapse
I got my Leo two days ago, went home, put HSPL on it in the first place, wanted to upgrade the stock ROM, and ended up same as CraigBruce. Really frustrating, thought I'd bricked it. So I re-flashed HSPL and this time a custom ROM and it was back up again.
Now I know that I should have flashed the stock ROM via ActiveSync and not SD card which would have left the HSPL intact. I will definitely remember that for the future
just remember that some people WANT to remove HSPL when installing a stock ROM - e.g. when returning device.
tbh it should have worked with stock ROM and sdcard as leoimg.nbh - it is the way listed in HSPL thread to uninstall after all!!! we dont always want to use customRUU!!!
As from the noob flashing thread
NOTE: The only way to remove the HSPL is to flash an original SPL from microSD card
* You can also use this method to flash back your Stock Rom and Stock SPL that you originally had on your phone*
VIDEO TUTORIAL: [★] has made a YouTube video to walk people through flashing a Stock SPL via activesync. Find it *HERE*
- Download a shipped Rom from *HERE*
- Rename the extension to .zip
- open it with winzip and extract the RUU_signed.nbh file to a folder
- Rename it to LEOIMG.nbh and copy it to the root of a microSD card thats been formatted to FAT32
- Insert your storage card into your phone
- Enter Bootloader and follow onscreen instructions to flash
Click to expand...
Click to collapse
Guys, I had reached the exact same issue with the NOT ALLOW problem. And people, we do read some times (the newbies) and nowhere but here you say that AFTER HSPL YOU MUST NOT UGPRADE FROM MEMORY CARD!!!! And NO it is not included inhere: http://forum.xda-developers.com/showthread.php?t=609477
Cheers,
and thanks to all the smart people inhere!
D
thug_life_inc said:
Guys, I had reached the exact same issue with the NOT ALLOW problem. And people, we do read some times (the newbies) and nowhere but here you say that AFTER HSPL YOU MUST NOT UGPRADE FROM MEMORY CARD!!!! And NO it is not included inhere: http://forum.xda-developers.com/showthread.php?t=609477
Cheers,
and thanks to all the smart people inhere!
D
Click to expand...
Click to collapse
With hspl installed you CAN flash CUSTOM roms using sd card, it is only flashing OFFICIAL roms through sd card that removes hspl.
sorry to crash this thread but...
i have flashed HSPL on to my HD2 and am now wanting to install HTC's new 1.66 rom.
i have a VF hd2 so i am a little worried i will hit the same issues as the OP did.
can some one hold my hand through flashing the ROM as im a complete noob to this.. i have read the FAQs and im a bit like with all the acronyms etc
adam_r said:
sorry to crash this thread but...
i have flashed HSPL on to my HD2 and am now wanting to install HTC's new 1.66 rom.
i have a VF hd2 so i am a little worried i will hit the same issues as the OP did.
can some one hold my hand through flashing the ROM as im a complete noob to this.. i have read the FAQs and im a bit like with all the acronyms etc
Click to expand...
Click to collapse
Use the custom ruu to flash it. Do not put the nbh on the sd. I quote from the "[HSPL]How to flash everything" thread:
4) Uninstallation
Only way to remove the HSPL is to flash an original SPL from SD card.
- Take any "RUU_signed.nbh" from a ship ROM and copy it to SD card.
- Rename it to "leoimg.nbh"
- Reset the device while pressing the volume down button.
Click to expand...
Click to collapse
Why people cant read? refering to the person who started this thread.
No Problem Flashhing to 1.66 on a Voda HD2 with HSPL
I have a voda HD2 and being a total Newbie to the HTC / WM .. I followed the Dummie guide.. (thanx to all, for that.. fantastic..) installed HSPL..and then installed the latest 1.66 from the HTC site using a boggus serial number.. As actual would not let me download it. No problemo..
Feeling a bit more adventureous.. any suggestions for the best 'cooked Rom' ??
From my understanding, you can flash away Stock ROMS using activesync. No need for HSPL.
Ok my last 3 days I've been simply trying to install some custom ROMs and did all the reading and research step by step, but my AT&T HTC Pure just wont update the HSPL no matter what.
Steps I've taken so far:
1. Formatted SD Card
2. Obtained and put goldcard.img on SD Card
3. Fully connected phone via Windows Mobile Device Center
4. Antivirus turned off
5. Tried Topaz-HardSPL_V5_00R5_183HSPL in in auto-mode, fails telling me " Fatal Error" and underneath "Please make sure the device is properly synced; Please retry after syncing device (via Activesync or Windows Mobile Device Center)" which I have...
6. Tried installing ENABLERAPINEW.cab with results "unsuccessful" (but again my phone does sync just fine, I still took this step)
7. Tried Manual Flash, my phone never goes into bootloader, and right after "verifying phone information" shows screen saying "ERROR [224]: DEVICE NOT RESPONDING"
8. Tried entering bootloader mode and during auto-mode to flash, tells me same exact thing as without bootloader
9. Tried Manual Flash in bootloader, it gets to flashing screen with a progress bar at 0% on both PC and phone forever, I waited 20 mins and it didn't change.
It seems as if there is something preventing RUU to be writing anything on my phone, so that's why it throws connection error, but I am not sure. And I am seriously loosing all hope in this and dont know what to do, so HELP please!
Update
I also forgot to mention that I tried to Hard_SPL from another computer that is Windows XP, used Activesync, which didn't work either...
The only thing i can tell you is to read this thread (what you have already done i think)
http://forum.xda-developers.com/showthread.php?t=520312
SerGTR said:
Ok my last 3 days I've been simply trying to install some custom ROMs and did all the reading and research step by step, but my AT&T HTC Pure just wont update the HSPL no matter what.
Steps I've taken so far:
1. Formatted SD Card
2. Obtained and put goldcard.img on SD Card
3. Fully connected phone via Windows Mobile Device Center
4. Antivirus turned off
5. Tried Topaz-HardSPL_V5_00R5_183HSPL in in auto-mode, fails telling me " Fatal Error" and underneath "Please make sure the device is properly synced; Please retry after syncing device (via Activesync or Windows Mobile Device Center)" which I have...
6. Tried installing ENABLERAPINEW.cab with results "unsuccessful" (but again my phone does sync just fine, I still took this step)
7. Tried Manual Flash, my phone never goes into bootloader, and right after "verifying phone information" shows screen saying "ERROR [224]: DEVICE NOT RESPONDING"
8. Tried entering bootloader mode and during auto-mode to flash, tells me same exact thing as without bootloader
9. Tried Manual Flash in bootloader, it gets to flashing screen with a progress bar at 0% on both PC and phone forever, I waited 20 mins and it didn't change.
It seems as if there is something preventing RUU to be writing anything on my phone, so that's why it throws connection error, but I am not sure. And I am seriously loosing all hope in this and dont know what to do, so HELP please!
Click to expand...
Click to collapse
you cant flash hardspl on the sd card, it must be done over activsync. u dont put it on your card, you run it from your computer. make a new folder{on your computer} and name it whatever , then unrar the file into the folder, then you should be able to flash the hardspl.make sure the ruu and the nbh file are in the folder.
leemoss84 said:
you cant flash hardspl on the sd card, it must be done over activsync. u dont put it on your card, you run it from your computer. make a new folder{on your computer} and name it whatever , then unrar the file into the folder, then you should be able to flash the hardspl.make sure the ruu and the nbh file are in the folder.
Click to expand...
Click to collapse
I do run Custom RUU from desktop local drive and not from SD Card and results mentioned above are the ones I get. Again tried with phone on, it just tells me ERROR [224] and never goes into bootloader or anything. Tried entering the the phone to bootloader manually and connecting it to usb and run RUU, it goes a little further where it finally gets to screen of flashing progress but freezes at 0% and thats it.
Could missteps in obtaining Goldcard be the reason for such behavior?
leemoss84 said:
you cant flash hardspl on the sd card, it must be done over activsync. u dont put it on your card, you run it from your computer. make a new folder{on your computer} and name it whatever , then unrar the file into the folder, then you should be able to flash the hardspl.make sure the ruu and the nbh file are in the folder.
Click to expand...
Click to collapse
Yes, you can flash ANY .nbh from your SD card by renaming it TOPAIMG.nbh.
SerGTR said:
I do run Custom RUU from desktop local drive and not from SD Card and results mentioned above are the ones I get. Again tried with phone on, it just tells me ERROR [224] and never goes into bootloader or anything. Tried entering the the phone to bootloader manually and connecting it to usb and run RUU, it goes a little further where it finally gets to screen of flashing progress but freezes at 0% and thats it.
Could missteps in obtaining Goldcard be the reason for such behavior?
Click to expand...
Click to collapse
Sorry for my ignorance but what is goldcard?
What is the current SPL?
I agree leemoss. You need Hardspl from your system. First synch your phone to system through Active sync. Execute the HardSpl.183, select auto flash.
Second thing i noted is on SDcard you have to rename the ROM file and store it as TOPAIMG.nbh and place in the root folder.
I read about people having problems, and the ones that weren't spent the 20 bucks on the Sim unlocker. I'd never flashed a phone before, so I went that route. It's worth it IMO.
rbrsddn said:
I read about people having problems, and the ones that weren't spent the 20 bucks on the Sim unlocker. I'd never flashed a phone before, so I went that route. It's worth it IMO.
Click to expand...
Click to collapse
See I do take ever single step that is in the guide here:
http://forum.xda-developers.com/showthread.php?t=530335
But it just doesnt work, but again I flashed HSPL and custom ROMs before on my Xperia X1a (unlocked) without any problems. I attached a pic of my bootloader, and when I try to run some custom ROM which I name TOPAIMG.nbh it enter screen "loading..." and freezes so have to rest my phone by taking battery out so it loads back just fine.
Again this phone I am using is HTC Pure by AT&T and thats what confuses me, maybe I really do have to SIM unlock my phone before I can HSPL and flash custom .nbh ROMs?
gold card
Bruce Inman said:
Sorry for my ignorance but what is goldcard?
What is the current SPL?
Click to expand...
Click to collapse
My stock SPL is in pic attached, and Goldcard.img suppose to be something I had to put on my SD Card so that I have SuperCID so I can flash HSPL and any custom ROMs, you can read more about it here: http://forum.xda-developers.com/showthread.php?t=530335
SerGTR said:
See I do take ever single step that is in the guide here:
http://forum.xda-developers.com/showthread.php?t=530335
But it just doesnt work, but again I flashed HSPL and custom ROMs before on my Xperia X1a (unlocked) without any problems. I attached a pic of my bootloader, and when I try to run some custom ROM which I name TOPAIMG.nbh it enter screen "loading..." and freezes so have to rest my phone by taking battery out so it loads back just fine.
Again this phone I am using is HTC Pure by AT&T and thats what confuses me, maybe I really do have to SIM unlock my phone before I can HSPL and flash custom .nbh ROMs?
Click to expand...
Click to collapse
You only need to CID unlock to flash ROMs, if you buy the SIM unlocker you get both CID and Security unlocked but it still may not work.
I see you have 1.8.33 which is good because there is not a working HSPL for 2.54
You say you tried running custom ROMs as TOPAIMG.nbh, but did you try it with the HSPL nhb? It would be the same process as doing a ROM from SD card.
I would also get rid of goldcard as that is only to recover a bricked device.
Get all goldcard stuff off your card and PC, reformatt your card to Fat32 the place the renamed TOPAIMG.nbh and proceed to bootloader.
One last pointer, another method to flash is to download Topaz Custom RUU Wrapper and put the exe file in the same folder as the .nbh on your desktop and run the .exe after your sync'd. **Make sure all firewalls and antivirus are off.**
Good Luck.
Bruce Inman said:
You only need to CID unlock to flash ROMs, if you buy the SIM unlocker you get both CID and Security unlocked but it still may not work.
I see you have 1.8.33 which is good because there is not a working HSPL for 2.54
You say you tried running custom ROMs as TOPAIMG.nbh, but did you try it with the HSPL nhb? It would be the same process as doing a ROM from SD card.
I would also get rid of goldcard as that is only to recover a bricked device.
Get all goldcard stuff off your card and PC, reformatt your card to Fat32 the place the renamed TOPAIMG.nbh and proceed to bootloader.
One last pointer, another method to flash is to download Topaz Custom RUU Wrapper and put the exe file in the same folder as the .nbh on your desktop and run the .exe after your sync'd. **Make sure all firewalls and antivirus are off.**
Good Luck.
Click to expand...
Click to collapse
Tried still same results... freezes at flashing with 0% at progress bar. I attached view screens that concern me that RUU cant read my stock ROM Image version, is this normal? The only other thing I am gonna try to do is maybe reinstall the entire Windows Mobile Device Center, besides that I am clueless.
Have you install the enablerapinew.cab first?
If so, I'm outta tricks. Others have been having issues as well in the HSPL thread. You may have to wait for an update.
I don't think its anything on your PC unless firewall or AV aren't turned off.
Remove SD-Card and Sim-Card before HardSPL from PC. I had 2 TouchDuals before TD2, one was no prob to flash, second needed SD-Card to be removed! Once HardSPL succeeded you may leave SD-Card in TD2.
WORKING!!!
YES!!! I finally got it to SPL, what it was that my phone could not accept any .cab installations due to security issue with "unknown publisher" signature, that's why my phone didn't allow me to install enablerapinew.cab but then I just hard reset my phone installed enablerapinew.cab and everything worked, YEY! Thank you Bruce Inman, and everyone else who spend time to try to guide me through my issues, tnx!
i didnt unlock mine. all i did was flash it.theres gotta be sumthn ur doin wrong.
Problem solved!
leemoss84 said:
i didnt unlock mine. all i did was flash it.theres gotta be sumthn ur doin wrong.
Click to expand...
Click to collapse
I figured it out man, tnx.
SerGTR said:
I figured it out man, tnx.
Click to expand...
Click to collapse
good deal man. what was the prob?
leemoss84 said:
good deal man. what was the prob?
Click to expand...
Click to collapse
What it was that my phone could not accept any .cab installations due to security issue with "unknown publisher" signature, that's why my phone didn't allow me to install enablerapinew.cab but then I just hard reset my phone installed enablerapinew.cab and everything worked.
I know apparently this isnt the best way to flash your HD2, but im stuck without any access to windows. (mac user)
i cant seem to find step by step instructions on how to do this properly....
is there a link somewhere i can get to so i can figure this out? isnt it as simple as copying the custom.nbh file to the root of my memory card, and entering the bootloader screen?
Sorry for all the noob questions.
take ruu_signed.nbh, copy it to sdcard formatted fat32 (2gb cards seen to work best) rename it leoimg.nbh, boot to bootloader and it should detect the image and ask if you want to flash.
it still requires hspl, unless you have a goldcard(easier to borrow a pc for two minutes to apply hspl than make a goldcard)
the phones already been flashed with hspl.
i just want to change the rom!
Thanks for the tips im going to go for it right now
newnoise1024 said:
the phones already been flashed with hspl.
i just want to change the rom!
Thanks for the tips im going to go for it right now
Click to expand...
Click to collapse
Hi
One advice you have to remember is DO NOT flash any official rom with this method. If you do it will replace the hspl and you will be stuck.
Good luck
sabes143 said:
Hi
One advice you have to remember is DO NOT flash any official rom with this method. If you do it will replace the hspl and you will be stuck.
Good luck
Click to expand...
Click to collapse
True, flashing a stock rom via sd card will overwrite hspl with the new stock spl, but you will not necessarily be stuck. That used to be the case before hspl2, as the original hspl only worked with spl 1.42.0000. HSPL2 now works with 1.42.0000, 1.66.0000 or 2.08.0000 spl's.
or just throw your mac away and buy a PC
What many forget is that you actually need an SD card and not SDHC, as those will not work.
understand u already flash hspl,
microSD / microSDHC will work as long it is formatted with FAT32 fs.
just copy the *.nbh to SD root & rename it to LEOIMG.nbh.
enter bootloader, follow on-screen.
if bootloader cant find any rom image, run scandisk & try again.
gd luck.
I just flashed this rom.
It seemed to be fine. It installed and looked a-ok.
I had a look around and every thing looked as it should.
I added "26.4 column Start menu.cab" and now the phone won't reboot at all.
It gets to the HTC white screen, and then hangs.
Any ideas?
Is it a conflict between the 4 columns app and the ROM?
url_paul said:
I just flashed this rom.
It seemed to be fine. It installed and looked a-ok.
I had a look around and every thing looked as it should.
I added "26.4 column Start menu.cab" and now the phone won't reboot at all.
It gets to the HTC white screen, and then hangs.
Any ideas?
Is it a conflict between the 4 columns app and the ROM?
Click to expand...
Click to collapse
when you say "just flashed this rom", what rom?
also, did you read ALL the first few posts in the chefs thread? chances are it requires a specific radio version
either that or you didn't do a hard reset after you flashed.
apologies, I replied in here when I thought I was in the HTC Energy thread.
The device rebooted after the flash.
Does that not count as a hard reset?
samsamuel said:
Is it T Mobile usa? if so, then you have flashed an incompatible rom.
tmous (T Mo US) phones will opnly take roms based on 2.10, the rom you have installed is 1.66 (D 1. 66. Kumar)
Kumar has a rom in the Tmo US section based on 2.10, you should use that, not the one in teh normal hd2 section.
With power off, press and hold "volume down", tap the power key and continue to hold vol down until you get the three coloured screen, connect to usb, wait for word 'serial' to become 'usb' and flash a compatible rom.
Click to expand...
Click to collapse
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Try installing the recommended Radio
url_paul said:
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Click to expand...
Click to collapse
I ran into the same problem and all I had to do was to get the phone into Bootloader and then flash the radio recommended by ROM Cook.
also the same problem
I have also this problem, but I think it's in the rom, when I installed the rom, everything seems ok, but after a reset, the screenthat I get is the white HTC screen.
After a hard reset it is ok, but after a reset it is the same problem.
Then I thought, i take an older rom, but when I've installed the rom he is automatic installing the cab file's at the end of the installation, and he's going to automatic reset the HD2. After the reset I have the same problem as with the new rom.
So the biggest problem is that I can't install another rom or radio because the rom don't start for 100%, and when I do a hard reset, after the reset at the end of the installation I get the white HTC screen.
What can I do, can I fix this problem?
groot321 said:
I have also this problem, but I think it's in the rom, when I installed the rom, everything seems ok, but after a reset, the screenthat I get is the white HTC screen.
After a hard reset it is ok, but after a reset it is the same problem.
Then I thought, i take an older rom, but when I've installed the rom he is automatic installing the cab file's at the end of the installation, and he's going to automatic reset the HD2. After the reset I have the same problem as with the new rom.
So the biggest problem is that I can't install another rom or radio because the rom don't start for 100%, and when I do a hard reset, after the reset at the end of the installation I get the white HTC screen.
What can I do, can I fix this problem?
Click to expand...
Click to collapse
RTFM. These constant posts about white screen hangs are really getting frustrating. Does nobody follow the forum rules of searching any longer? There's nothing wrong with the rom, the user on the other hand I'm not so sure of.
YOUR RADIO VERSION IS WRONG
url_paul said:
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Click to expand...
Click to collapse
If you bothered to read even just the last 5 pages of the Energy thread you would have seen probably 20 mentions of the problem. Energy rom won't work with a x.xx.51.xx radio.
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
I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?
Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.
flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.
Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.
Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.
hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.
Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.
gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.
samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.
@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!
gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.