Related
Before I get started, I've flashed 4 different roms onto my phone before along with flashing the radio and installing Magldr, so I can't quite figure out what I'm doing wrong this time around
On my phone right now - MAGLDR 1.13
Radio is SPL-2.08.HSPL 8G XE CotullaHSPL
I've also got ClockworkMod v1.3 installed
No ROM? My phone isn't booting into anything right now
Alright, I've set my phone into the bootloader, got an active connection and ran the CustomRUU.exe for both radio version 2.15 and 2.14.50 and for some reason, when completed it doesn't seem to have updated my radio. The program finishes and completes with no errors, but when I go to check in the tricolor bootloader, it's still version 2.08?
My ultimate goal is to get this ROM installed http://forum.xda-developers.com/showthread.php?t=917590 CleanDROID v2.51 - Froyo+CM
Now it says to update my radio to at least 2.12 but I don't know why it's not updating? And because of this, I cannot seem to flash the rom. When flashing the ROM, i am approached with this error:
Happen error
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (712)
Error Description: CONFIG: file not exist
Info: .\RSPL\RSPL.cpp (346)
I have no idea what's going on or what I should do. I don't exactly see what I'm doing wrong or what steps are missing. I've never had so much of a hassle with rom and radio flashing before, it's aggravating me and I must figure it out lol!
Thanks in advance for all the help
efeguwewe said:
On my phone right now - MAGLDR 1.13
Radio is SPL-2.08.HSPL 8G XE CotullaHSPL
I've also got ClockworkMod v1.3 installed
No ROM? My phone isn't booting into anything right now
Click to expand...
Click to collapse
Firstly despite being on d right path, u've got ur info slightly wrong.
"SPL-2.08.HSPL 8G XE CotullaHSPL" is ur installed HSPL & NOT ur radio version...Assuming u were still running WInMo, u would have noticed d change in radios u flashed at the bottom of the TMobile boot-up screen...Rest assured there r no major problems here cuz it appears u've already installed d radio...
***You've Performed HSPL and installed MAGLDR 1.13....so Good.
***You also performed a CWM install but the ROM thread u posted is not a CWM build....Meaning it's a DFT build and does't need CWM installed.
Nw here's what u'll do.
>>Since a 2.12.50.xx radio is recommended by the rom dev...Flash it normally (thru bootloader mode) if u haven't already....hweva check out my signature for the radio i'm using and where 2 get it.
>>Reboot ur device into MAGLDR by pressing down the power button when starting up.
>>Scroll down & select USB flasher
>>Connect phone to PC with USB cable (allow it to install drivers if necessary)
>>Then flash the ROM with the supplied DFT flasher (DAF.exe present in the downloaded folder).
>>Sit back n relax.
*** Its that simple.***
P.S. Flashing a dft build will remove ur cwm installation...its a known fact dat both cannot co-exist.
I installed CWm because I was planning on flashing this ROM: http://forum.xda-developers.com/showthread.php?t=933951
But I gave up because I kept on getting the following error as well:
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (712)
Error Description: CONFIG: file not exist
Info: .\RSPL\RSPL.cpp (346)
Click to expand...
Click to collapse
Same numbers and text
How can I check what radio I've flashed? Also, I don't think i have WinMo installed anymore as my phone just boots straight to MAGLDR after failing to load a android nand (but how can it when none is installed lol).
Since I've gone through the CustomRUU.exe for both 2.14 and 2.15, do I already have the radio flashed? Nothing went wrong and the process was completed
I've already done everything you posted before my original post, I just on getting those .RSPL errors.
>>Since a 2.12.50.xx radio is recommended by the rom dev...Flash it normally (thru bootloader mode) if u haven't already....hweva check out my signature for the radio i'm using and where 2 get it.
>>Reboot ur device into MAGLDR by pressing down the power button when starting up.
>>Scroll down & select USB flasher
>>Connect phone to PC with USB cable (allow it to install drivers if necessary)
>>Then flash the ROM with the supplied DFT flasher (DAF.exe present in the downloaded folder).
>>Sit back n relax.
*** Its that simple.***
Click to expand...
Click to collapse
Tried it your exact way and I still get the .RSPL error
anybody have any idea what I should do?
efeguwewe said:
anybody have any idea what I should do?
Click to expand...
Click to collapse
Hmmm...Try this then.
Perform a Task29.
Flash a 2.15.50.14 radio.
Install MAGLDR 1.13.
Install CWM...(If needed & Paying attention to which particular clockwork partitioning system will work for you desired build).
Re-download the android build..(cuz i think some files might ave messed up while downloading).
Find an alternative means (e.g. thru sd card readers / thru CWM's mount storage system) to transfer the zipped build to ur memory card...Avoid using MAGLDR's inbuilt usb mass storage utility as its been reported 2 have a few issues during transfers.
If u also have a TMobile HD2, u might be interested in d build i'm currently running..It supports CWM n flashing it and or updates ave never given me issues.
Hi guys.
I have been going thru the threads and cant seem to find a solution to my problem.
I am currently dualbooting between wp7 and an android build - maglrdr 1.1.
I am having sound and signal and robotic sound on the android rom so I want to flash a new radio viz.2.15.50....
I go into bootloader vol down - power etc. do the normal but then it hangs on the the second last screen ...............0% etc.
It doesnt do past this.
Please help
nizaamh said:
Hi guys.
I have been going thru the threads and cant seem to find a solution to my problem.
I am currently dualbooting between wp7 and an android build - maglrdr 1.1.
I am having sound and signal and robotic sound on the android rom so I want to flash a new radio viz.2.15.50....
I go into bootloader vol down - power etc. do the normal but then it hangs on the the second last screen ...............0% etc.
It doesnt do past this.
Please help
Click to expand...
Click to collapse
Do you still have 2.08.hspl installed? Go back to bootloader and check it.
Hey XDA
Hope someone out there have got some good advice. We have some HD2s where i work and i have been sent one that is acting kinda weird.
I simply can not get it to flash a rom (_HTC HD2_RUU_Leo_S_HTC_DAN_3.14.403.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship) - we only use normal HTC roms. When i try to flash it nothing happens, it boots into the bootloader and just sits there at 0% until i disconnect the cable, if i dont it will sit there untill it runs out of battery. Tried a few times now and same result.
i have also just tried a restore, to see if its the internal flash rom that is broken and the restore also fails. My own HD2 restores in like a few seconds but this one just sits there again, like when i try to flash a rom to it.
So is it totally dead or is there something i should try?
Have you tried to use task29 (via computer) , then flash (via nbh) the htc rom?
hmm just tried task29 and it did nothing, it booted the phone to the bootloader but no progress screen did show up. Tried it again and the phone just shut off again after showing the bootloader for a few seconds.
beginning to think this phone is toast.
Gonna try a HSPL update later and just flash a non HTC rom to see if that works.
dkwolf said:
hmm just tried task29 and it did nothing, it booted the phone to the bootloader but no progress screen did show up. Tried it again and the phone just shut off again after showing the bootloader for a few seconds.
beginning to think this phone is toast.
Gonna try a HSPL update later and just flash a non HTC rom to see if that works.
Click to expand...
Click to collapse
HSPL 2.08 & reflash original HTC ROM via PC USB.
Do you get any error codes from the flash utility ?
could be CID related but you should see error code.
Yes, trying it with HSPL seems like a good idea to me, too.
Because then you can also try other ROMs.
will try this stuff on monday - i just cba to do more work today
thx for the advice
Build a gold-card and flash from the SD slot. If that doesn't work, put it in a zip lock bag and then into the freezer for 10 minutes. After 10 minutes, boot the phone and try flashing again immediately in it's chilled state. If it get's ANY further, you have a bad overheating NAND and need a new main board.
got HSPL2.08 flashed and a Dutty 3.14 rom but phone refuses to reboot sometimes and boot just shows the white HTC background and does not show the radio/os versions in the bottom. So i am just gonna toss this one out, since its can not be serviced (supplier has gone bust).
But still havn't gotten any error codes from the phone or flash programs, other then "USB connection failed". So i think its nand is kinda broken now.
dkwolf said:
got HSPL2.08 flashed and a Dutty 3.14[/COLOR] rom but phone refuses to reboot sometimes and boot just shows the white HTC background and does not show the radio/os versions((edit - the RGD screen)) in the bottom.
Click to expand...
Click to collapse
first, you can't run 3.14 roms on anything except spl 3.03.0000 or 3.03.hspl
Second it isn't booting because it almost certainly needs an updated radio, 2.15.50 for instance. You probably still have a 2.xx.51 from the original stock, and so wont show rgd screen till you change radio, won't run smoothly till you correct the spl with hspl4
But still havn't gotten any error codes from the phone or flash programs, other then "USB connection failed". So i think its nand is kinda broken now.
Click to expand...
Click to collapse
Put phone into bootloader manually, don't use front mounted USB ports, be sure and update win mo dev center to latest ver ..... all the usual USB connection error advice. Trying another PC with a different windows variant often helps if its available.
samsamuel said:
first, you can't run 3.14 roms on anything except spl 3.03.0000 or 3.03.hspl
Second it isn't booting because it almost certainly needs an updated radio, 2.15.50 for instance. You probably still have a 2.xx.51 from the original stock, and so wont show rgd screen till you change radio, won't run smoothly till you correct the spl with hspl4
Click to expand...
Click to collapse
hmm you sure? The dutty download page says -
Things to Know how about my ROMs:
* Radio 2.15 Recommended
* HSPL 2.08 Recommended
* HSPL 3.03 doesn't support 576 RAM enabled
But i'll try to flash a 3.03HSPL and find out what happens. I did flash 2.15.50.14 radio before i flashed the Dutty rom. But gonna give it one last try.
samsamuel said:
Put phone into bootloader manually, don't use front mounted USB ports, be sure and update win mo dev center to latest ver ..... all the usual USB connection error advice. Trying another PC with a different windows variant often helps if its available.
Click to expand...
Click to collapse
Have tried two pc's now, both running Win7 32bit - its all we have now.
Ahhh gitcha, then the dutty rom mustnt be 100% 3.14 rom (I didn't check) it must use a 2.x base to enable 576ram.
In which case, if stock roms don't flash but custom did, it could be stuck radio syndrome, which you can test for with (correct, get it using your serial from HTC.com) stock rom flash from sd card (4gb or smaller, fat32). Look out for "rsa radio fail" or similar on screen.
Edit, oh you said you flashed a radio, and that went ok?
samsamuel said:
Ahhh gitcha, then the dutty rom mustnt be 100% 3.14 rom (I didn't check) it must use a 2.x base to enable 576ram.
In which case, if stock roms don't flash but custom did, it could be stuck radio syndrome, which you can test for with (correct, get it using your serial from HTC.com) stock rom flash from sd card (4gb or smaller, fat32). Look out for "rsa radio fail" or similar on screen.
Edit, oh you said you flashed a radio, and that went ok?
Click to expand...
Click to collapse
yeah HSPL2.08, HSPL3.03 and Radio is flashing just fine. The roms i have tried also flashes perfect its just will not boot afterwards. I can usually do a hardreset on it and it will boot one time. If you then shut it off and try to turn it on again it fails with the white HTC screen again.
I am toally clueless on what is wrong with it, so gonna try to figure out if we have some kind of warrenty left on it and get it switched over to another one.
First, sorry if I post the kind of question that has been already asked 1000 times, I'll understand if my post is deleted.
here is the story: I still have an HD2, but got a Sensation almost one year ago.
Now my HD2 is still WinMo 6.5 with Android from the SD card.
Yesterday, one of my pupils (yes, I'm a teacher, and my pupils know I'm into smartphones....!) gave me his HD2 because his father kinda bricked it.
I haven't been using my HD2 or reading XDA HD2 section or a long time (I'm too busy flashing my Sensation, so reading Sensation threads ), but I thought I could give it a try to unbrick it, I'm not a noob after all (selfish guy!!!!!!!!!)
I think this HD2 was somehow bricked while trying to install Android into NAND, or installing MAGDLR, as far as my pupil can tell from his dad
So this Sensation can't boot and has this, written in the 3 colours screen
PB81100 HX-BC
SPL-2.08.00 8G XE
MicroP(LED) 0x05
icroP(TOUCH) 0x40
Upgrade ROM code error
Please try again
Click to expand...
Click to collapse
Here is the state I had this HD2, unable to boot, just able to get into bootloader with the message above.
I tried to flash latest Dutty ROM (because I was using Dutty creme of the creme at my HD2 time!)
=> through USB, flash freezes sometimes at 2%, sometimes 75%
=> through SD card: it flashes, says it's successful, but the device doesn't boot, back to three colors screen, or white screen with error message if trying to boot normally
I tried task29: full of errors, not better after flashing a ROM
I tried flashing a shipped "official" ROM => same as custom ROM, says success, flashed through SD card, but never boots to something else than 3 colors screen..
I tried factory reset, said successful, but still no boot!!
I tried flashing a Radio ROM=> flash successful, but still no boot
I tried flashing HSPL again, 2.08 and previous versions: it flashes OK, can see the changes in three colours screen, but no success flashing a ROM after
I noticed that sometimes, this HD2 vibrates 7 times quickly in a row, which my own HD2 had never done, and I suppose it's a very bad signal
I'm not a noob at all, but really can't follow every thread, and tried the search function with no real luck.
Is this HD2 definitly bricked? Is there something I can do?
Sorry again to seem so noob, I would have flammed someone posting like me, when I was following HD2 development everyday, before having my Sensation (and a Moto Defy for my wife)
see the line ''SPL-2.08.00 8G XE'' (you actually mean 2.08.0000) well teh .0000 tells you its NOT hspl, its a stock spl, so nothing will flash.
run hspl 2,3 or 4 and choose ''2.08.hspl''. Flashing, task29, magldr, all that will now flash.
THANKS!
how stupide I am (or too long away from WinMo)
I had tried hspl2 that was unable to do the job, hspl4 did it
So now I have spl 2.08.hspl
...but face other problem:
task29 fails: it launches OK but my HD2 disconnects from USB as soon as task29 starts its process
if I try to flash a custom ROM (the dutty one my own HD2 is still using), via usb, same, usb disconnects (it wasn't before I flashes hspl 2.08)
If I try flashing as a LEOIMG with microSD, it feezes at about 2/3 of the process
trying to flash a shipped ROM leads to errors, back to three colors screen with "Upgrade ROM code error Please try again"
...not to mention each time it replaces the hspl by stock spl
Any idea?
i900frenchaddict said:
THANKS!
how stupide I am (or too long away from WinMo)
I had tried hspl2 that was unable to do the job, hspl4 did it
So now I have spl 2.08.hspl
...but face other problem:
task29 fails: it launches OK but my HD2 disconnects from USB as soon as task29 starts its process
Click to expand...
Click to collapse
don't run flashes from running winmo, enter bootloader manually, when serial --> usb, run your flash/task29 or whatever. (Gorget about task29, it isnt necessary)
alternatively, if you do run it from running winmo, then once the phone has restarted and the usb has timed out, simply run teh flash program again, and dont touch teh phone, since it will now be in bootloader, and my above note takes over.
if I try to flash a custom ROM (the dutty one my own HD2 is still using), via usb, same, usb disconnects (it wasn't before I flashes hspl 2.08)
If I try flashing as a LEOIMG with microSD, it freezes at about 2/3 of the process
Click to expand...
Click to collapse
not a good sign, but ignore that for now.
trying to flash a shipped ROM leads to errors, back to three colours screen with "Upgrade ROM code error Please try again"
...not to mention each time it replaces the hspl by stock spl
Any idea?
Click to expand...
Click to collapse
because that's the way to remove hspl, , flash a stock rom from sd. Step 1 of sd flashing is the spl gets flashed, removing hspl, the phone then restarts and tries to flash the stock rom, but now that hspl has gone it fails, since you aren't using the correct stock rom for that particular phone.
Try this, get the stock 3.14 rom ( filename will be RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship )
EDIT - you dont have a tmous, right? if you do, dont do this!)
phone into bootloader
use hspl4 to set 3.03.hspl
phone into bootloader
flash the 3.14 rom over usb.
report back.
Man, I'm on the good way!
3.03.hspl seems to be the key, when 20.8hspl wasn't
While the stock 3.14 ROM finished to download, I could run a Task29 till the end, no more USB disconnecting.
Crossing fingers!
I'll edit this post once I've tried to flash the stock 3.14 ROM
Huge thanks to you !!!!
2.x spl is not a stock spl for regular hd2's, only tmous, so whilst it does work, it does introduce the odd problem. for example you cant sd flash stock roms with 1.x versions when you are currently on 2.x.
SO, with a regular hd2, any time you wanna return to stock or are having flashing troubles of some kind, it is always worth using hspl.exe (2,3 or 4 , doesnt matter) to remove the 2.x spl/hspl.
For me, I always go back to 1.66.0000 using hspl2 before i even try to flash a stock rom. Since i choose a 0000 ending, it will be updated as required by the stock rom.
Fingers crossed it helped.
samsamuel said:
Try this, get the stock 3.14 rom ( filename will be RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship )
EDIT - you dont have a tmous, right? if you do, dont do this!)
phone into bootloader
use hspl4 to set 3.03.hspl
phone into bootloader
flash the 3.14 rom over usb.
report back.
Click to expand...
Click to collapse
This worked for me...Thank you so much.
Ok. I have a HTC HD2 t-mobile. Someone gave it to me to see if I can fix it. So I have NO clue how it got to the point it is at now. All I know is that you power on and its a white screen. No HTC logo. Just white.
Enter boot loader: Red/Green/Blue/Black/White.... Its says:
PB81120 SS-B3
SPL-2.10.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
SERIAL
Thats it. It doesnt connect to the computer.
What can I do? I tried:
CLEAN INSTALL
It’s a pretty long process, however, it takes a shorter time than the Installation of NAND Android. It takes me about 15minutes. It should take you about half an hour but no more than half an hour.
HSPL3, -2.08.HSPL.
[Head to my guide on How to install HSPL3, if you haven't install HSPL3 yet.]
Radio Version that supports 576 RAM(Radio2.15.50.14).
[Head to my guide on How to install radio , if you haven't install a suitable radio version yet.]
Wipe phone memory completely.
Install DFT MAGLDR.
Install ClockworkMod Recovery.
Create EXT3 Partition with ClockworkMod Recovery. (This step will wipe everything on our SD Card.)
Transfer ROM(zip file) to SD Card with ClockworkMod Recovery.
Install ROM from SD Card with ClockworkMod Recovery.
Details will be provided for each of the 6 steps.
But the phone and computer cant communicate. I have tried a hard reset. So thats where I am at now.
temp removed.
Ok. So I tried to flash the stock ROM from the SD card. It didnt complete. It says that it failed. It says at the top
00018003
LEOIMG.nbh - FAIL
Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
Error Description: wait marker fails
Info: .\RSPL\BootLoader.cpp (225)
When I try to install HSPL3 I get this error
CRITICAL ERROR
FLOW: 00000006
Error code: 00000014
Description Unknown
I can not get HSLP on my phone. I have tried versions 2,3 and 4... Is the phone done???
So I know I am a pain. But I have searched and read just about everything I can. I have tried to flash the stock ROM, I get an error of Radio Fail. I can not flash any other ROMS because I can not install HSLP.... I can connect via USB. But Windows Mobile Device center does not acknowledge the phone. I have ran the Task29... well tried... it says image is corrupted. I have even stuck the dang thing in the freezer like I have seen in random posts. Nothing but a really cold phone.
When I try and install HSPL3 I get an option to choose 2.08.HSPL or 2.08.0000 I have tried both. I get the critical error... Error code 16 description unknown.
I have tried following every set of directions I can locate in xda... Nothing has worked at all.
McSpammer5 said:
temp removed.
Click to expand...
Click to collapse
???What does that mean???
Have you tried reflashing window mobile???
Sent from my LG-P999 using xda premium
Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android
yesiamanoob said:
Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android
Click to expand...
Click to collapse
Great...
Sent from my LG-P999 using xda premium
Hi to the experts!
I have a very similar problem, maybe "almost" identical...
My HD2 (Australian Telstra, stock in almost every way), and it has been reliable for 2 years from new.
Then last Saturday night it started "failing to load HTC Sense", but all the WinMo 6.5 stuff was still fine. This lasted for 2 days and I thought it was stable like this so I would have time to look for a new phone, but last night I turned it off and on again, and all I have is the white screen. Mine has the green htc on it, but the only way to make it go away is to take out the battery.
I tried the volume down / power ON and I get the RGB+W screen, and when I plugged it in via USB to my new laptop it loaded drivers and initiated Windows mobile device center - but it won't recognise that there is a device there.
Now my very strong desire is to somehow boot it to allow recovery of my contacts directory - I have just started a new job and have probably 40 or so new people in there since my last backup.
What are my options? Is there anyway to boot from SD card without erasing the whole of system memory??
Failing that, how do I flash back to stock?
thanks (in hope)
..Neil
Stock WM
Try installing stock WM 6.5. There are many links available for the same, google it.
Do this without the memory card.
Enter Bootloader by pressing volume down and power on button together.
Then run the WM ROM file on your computer. You must see the progress bar on your phone. Let it settle down.
Hope that helps..!!
Hi everyone!
I am very sorry for such a n00b-post, but I really cannot find a solution.
The problem:
I recently got a HD2 of a friends who did not use it anymore, because Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I tried resetting the phone using the red button near the battery, but it did not solve the problem. I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
Is this phone useless? What can I try to revive it?
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
andrejazzz said:
The problem:
Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
Click to expand...
Click to collapse
Since you're unable to connect to PC, then you can't re-flash HSPL.
HSPL needed to force flash any shipped WM6.5 ROMs to HD2.
Then the only way is to flash original WM6.5 ROM for your device from uSD.
If you're not sure what CID, just download any HD2 shipped ROMs and try to flash from uSD.
Just be careful not to flash EU's ROM on T-Mobile device!
Extract the ".exe" file, then rename the ".nbh" file into "leo.nbh", copy that to root of uSD.
Power up your device while pressing vol down button.
Don't worry if the ROM refuse to flash, it's just a wrong CID.
But to make sure, connect your device to another clean PC (without android drivers inside, just WMDC), preferably a PC sets for syncing WP7/WP8 devices.
And make sure your device turns on by itself when charger is connected (auto turn on from off state).
That's just to make sure that usb connector is not damaged.
HD2 vibrate 1x at power on, it's normal.
Vibrate 5x after magldr shows up, I suspect something wrong with magldr or the ROM itself (corrupted or something).
Another possibility is some NAND bad blocks.
But if it's vibrate 5x at power on, then you have a bad luck.
The point is, flash the original ROM first.
If it's success, then flash HSPL.
After that, the rest is up to you..
Firstly, I want to thank you very much for your quick and extensive answer!
But I have only one tiny question: are these the ROMS which I can find at http: //www . 4shared . com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html#dir=MGRa1Cen ? And you mean I should just pick one and try?
You can also find HD2 shipped ROMs here.
Anything that has "TMO" are T-mobile ROMs, otherwise it's EU.
Again, don't flash EU's ROM on TMO devices!
The first 3 digit are the ROM version (1.66, 1.48. etc.), 3.14 is the latest WM6.5 ROM.
The next 3 digit are CID code (207, 404, 707, etc.).
Like I've said, if you don't know which CID for your HD2, then just download all ROMs from different CID then flash it one-by-one using uSD.
Thanks!
So far I have tried the 404 and 162 (edit: and 161, 911), but so far without luck. I'll keep you posted!
Tiny question: is it normal that I cannot shutdown in Recovery Mode?
Perhaps some useful info shown in Recovery:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
Correct me if I'm wrong, but it looks like an EU HD2, TMO HD2 are rarely using hynix nand, made around late 2009 or early 2010.
Just try to flash ROM with CID for your friend's country first.
If failed, then try another CID.
There should be one or two info about CID number vs. country somewhere around.
Good luck!
Sent from my Windead Phone 7 using xda app-developers app
At this moment I have tried all the NLD roms with no result. Also I have tried roms from several european countries, but none of them works:/ Might it help if I give the serial number?
And what might be worth saying: my phone turns on when connected to AC power / wall-charger; when connected to charger the "serial" disappears...
Thanks for all your help!!!
Have you try connect to other PC?
When flasing ROM from uSD and failed, what error message you got?
If it's "CID mismatch" or something like that, than it's definitely a wrong CID.
If it's "ROM update error bla bla bla", it's most likely corrupted flash image or the uSD itself (use a small sized uSD, 1gb would be fine).
Even if you flash the correct CID, without removing HSPL first, it would still throw an error message "ROM update error bla bla bla" during flashing Radio.
Then it will restart and retry to flash again on it's own.
By the way, I don't know if there are ways to flash HSPL from uSD.
Or guide on how to make a "gold card".
I sugest you search it.
Worth to try if you couldn't find the correct CID for your device.
CID from serial number?
Yes, back in 2010/11 HTC site provides s/n checking for download the correct ROM.
But now it's gone.
Sent from my Windead Phone 7 using xda app-developers app
Thank you very, very much for helping such a newbie ^^
At this moment, I am able to get into the update-menu: I changed the filename to LEOIMG.nbh. The only problem is that all the Dutch images give the same error: 00018003 : Radio (V2) - FAIL.
What could I do to solve this error? Use the freezer-trick or wouldn't it make any sense?
edit: it does boot when I connect to another W7 pc with WMDC (replies " Not connected" ), only it automatically starts the update-procedure (which fails).
There are no such thing as newbie, that's why we need to learn.
Error 00018003 during Radio flash?
I have no idea what error is that.
But first, are you sure that your friend bought the phone on local shop?
I mean, not imported, or when he/she travel overseas, or has the mainboard swapped at HTC service center.
It happens to me when my second HD2 suddenly has no signal, about 2 years ago.
Brought it to local service center and they swapped the mainboard without telling me.
And the swapped mainboard has CID from 404 (europe), the original was 707 (indonesia).
Okay, back to error something.
WMDC won't recognize the phone unless it's a working WM6.5 device, or a working WP7 device with WP7 SDK + Zune installed on your PC.
Just put the phone into bootloader screen (3 color screen), then connect it to a clean PC.
Does the "Serial" changed to "USB"..?
If it does, reflash HSPL 2.08 using HSPL4 package.
Then flash Radio ROM only, 2.15.50.14 is a good one.
Again, an EU HD2 can use either EU's Radio ROM or T-Mobile's Radio ROM.
But a T-Mobile HD2 can only use a T-Mobile's ROM..!
If the "Serial" doesn't change to "USB" but on your PC makes sound like something is plugged in, open device manager and look for an unknown device (no drivers loaded).
Expand it, what does it says?
To be honest: I am not 100% sure that it is an European (Dutch) phone. What I saw when I opened the phone's back was that the warranty-seals on the screws were molested. I don't think he got the motherboard replaced: way to expensive in relation to a new phone...
The bootloader screen gives now the following text:
RUUNBH
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0X05
CotullaHSPL 0x40
Upgrade ROM error
Please try again
When I connected it to a clean pc, the phone booted and gave another upgrade-error, only this time on a black screen (I got the uSD out the phone).
After booting the phone and connecting to a pc the "serial" does not change to "usb"...
When I tried to install WMDC I get the error "Installationpackage not supported by processor". Seems like bullcrap, but there it ends. No yellow exclamation marks in Device Manager...
I have yet not tried to flash a T-Mobile ROM to the phone. I have tried all the NLD ROM's: 1.66.404 ; 1.48.404 ; 1.66.404 ; 3.14.404 ; 1.66.404 ; 1.43.404
I have yet not tried the other ROMs I downloaded, but I will tomorrow. To start 161 does not work.
Also: I cannot shutdown when in bootloader or MAGDLr, is that correct?
What colour are your call & end key buttons !
if white you have standard EU type model. T-Mobile EU models are same as any EU model & can flash any ROM/Radio
If green & red you have a T-Mobile USA model (TMOUS) & need correct ROM (found in HD2 Wiki)
T-Mobile USA model needs care as if flash wrong radio version you can brick it.
Flashing via SD card should be last choice as first stage of a SD card flash is install of the SPL to standard SPL from the nbh which means you have no CID bypass as HSPL gone.
ideally you need a Windows 7 32bit machine with a known working WMDC setup & try flashing a suitable rom once decided on EU or TMOUS device.
As you have HSPL on your HD2 already it will bypass CID if flash via PC so you can flash any CID code rom.
Try connecting device to PC (with known good WMDC) and use reset button on HD2 to boot to bootloader & see if get any luck in running ROM installer from PC.
If lucky the USB flash issue is PC & drivers rather than hardware on HD2.
I would suspect you have nand issues on HD2 or perhaps worse, if nand sometimes you can get it back if persistent & get something to flash completely.
Thanks MisterB for adds up.
So am I, suspected a nand issue.
The reason I want him to revert back to original SPL & Radio is to make sure that it's a nand related problems, not radio hardware problems.
If he managed to find the correct CID for his phone, he could easily reverts back in case somethings wrong in the future after playing with custom ROMs.
This also happens to my friend's phone a couple months ago.
But in her case, the bad blocks are definitely located where magldr resides, and many more on data partition.
She can flash shipped ROMs completely, but it refuses to boot.
Can't flash a WP7 ROM because magldr freezes when it's loading, can't even bring the menu screen.
She can run a native sd android build for a couple weeks, but then it acting strange again.
Then finally she just gave up and bought another phone.
@andrejazzz:
You can't shutdown on bootloader (3 color) screen.
Remove the battery is the only way to shutdown, or press the reset button to restart.
But you can shutdown/restart or anything else on magldr menu screen.
Press & hold power key right when magldr loads up (before it's start to "go go go").
In addition, you can download WMDC x86 version here, and x64 version here..
He may indeed need try SD flash but I would exhaust all options of USB cable flash via PC first as retaining HSPL will be useful to start with as any generic HTC ROM could be used for the USB cable flash.
If that is not possible then flashing via SD is only viable option & indeed many times only way get over bad boot/nand issues but with all the CID versions for HTC regions & operator branded regions you have a hard job knowing the right one, you could even try the right ROM & as it does not flash overlook it for further testing.
I see he has tried SD flashing but still has HSPL so either SD card is not best suited for nbh flashing or nand/hardware that bad even first stage of flash is not possible.
If I was testing this device & trying recovery I would probably try freezer test to cool device prior flashing & make good effort on USB flash before going on to SD card.
Most well used Android HD2s these days have nand or bga issues to some degree as android works the hardware so much harder than WM6.5.
You really need be sure PC & driver are known good for flashing & if going to SD flashing that SD card is suitable or you will waste a lot of time & effort.
Loads of links & tips for all the software & some threads are in the HD2 Wiki
I apologize for replying so late, but I have had no time: I had a few tests at school
@Mister B: I have a black HD2 with white icons, so I have a european model.
I have installed installed the X86 on a clean 32-bit system, but it does not recognize the phone. I have reinstalled the WMDC on my W7 64-bit system, but still it does not recognize the hd2. I have no other Windows Phones, so I am not able to verify the WMDC-installations.
When I connect to a pc, the phone boots and shows: "Software update failed! Please try again"
@Shadow_Nexus: Correct, that is exactly what happens. I do not completely understand what you mean with "Press & hold power key right when magldr loads up (before it's start to "go go go")", could you please explain?
@Mister B: How could I check if the SD-card might be the problem? It is a 16GB Class 4 Kingston SD. I have tried all the NLD-roms and other versions (random countries, not TMOUS). I have tried the freezer trick with a NLD-rom on a mSD, but it did not work.
Thanks for all your help!
Best using a 2gb or 4gb (8gb max) card for nbh flashing & do a proper fat32 format with something like hp format tool before using it.
link below may help:
http://forum.xda-developers.com/showthread.php?t=681317
Again, thank you very much for your reply. But: do you have any clue what ROM's I should try? I am asking this, because I have already tried all the NLD ROM's I found on the site @Shadow_Nexus gave in post #4, but every one of them returns the same error. Should I switch to another country and try, for example, all German ROM's?
I got my hands on another HD2 and when I connect that one to my pc it show up, named "HTC Sync". The bricked one still does not respond:/ Should I retry all the non-TMO roms I can find?
Edit: My brother "helped" me out and sold the phone...