Related
Hi folks,
I have a T-Mobile branded HD2 that gets stuck on bootscreen. Since this one is owned by the company I work for I should not flash custom ROMs or whatever. I got it from a colleague with this error.
What I did is downloading the latest official ROM from HTC with T-Mobile branding, extracted the .nbh file and stored it as LEOIMG.nbh on its SD card. I flashed the ROM, removed battery, put it back in and immediately did a hard reset. Still no luck it keeps stuck in the boot screen showing the ugly circle. No animation, no nothing.
Any ideas?
Regards,
Chris
What is the full name of the official ROM you got .and did I understand you correst you got it from the T-Mobile website? Also what does it say when you put it in BOOt loader?
Filename:
_HTC HD2_RUU_Leo_TMO_DE_1.72.111.4_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship.exe
Download from:
http://www.htc.com/de/supportdownloadlist.aspx?p_id=297&act=sd&cat=2
I am not sure what you mean with bootloader? VolDwn+Power?
PB1100 HX-BC
SPL-1.66.000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x50
Let me know in case you need more details.
It gets even more weird...
I put the phone on charge (switched off). It suddenly switched itself on and then booted into windows. It came to the point where it asks for the PIN. I entered it and as soon as it accepted the code it rebooted again and is stuck on the same screen as ever.
Sorry I was changing my ROM, That is why it took a minute, Are you sure you have a T-Mobile HD2? Cause it says in the name of the ROM you posted that it has a 2.07.51.22 and that radio is deadly to a T-Mobile HD2.
Does it have a green send button and a red end button?
Also did you enter the serial number of your HD2 in the HTC site to verify that this ROM is for your HD2?
What you said about it rebooting when you plugged the charger in is weird.
I bought this HTC (and several others) all from T-Mobile, since we got some company agreement. When I first got it disfunctional it booted up with this circular bootscreen in T-Mobile colors. I personaly own a Desire HD, so I know about the uncustomized bootscreen.
This is T-Mobile for Germany, not UK or US. For the US version the radio won´t work since bands are different. I have heard about that...
This device does not have colored buttons.
Yes, I have entered the serial number on this site and it has been validated. Then I downloaded and unpacked it just the way it is described in this forum.
I also tried to download the original, latest, unbranded HTC ROM, but it did not validate my SN.
I have reformatted the original 2GB SD card with FAT32 and tried the same. After it says UPDATE SUCCESS it does nothing. Is this correct?
I took off the battery and after a couple of seconds back in, doing a hard reset. It then still got stuck on the bootscreen.
Ok do this download the Task 29 by ShaDrak from post #1 of the Task 29 thread here on XDA and run a Task 29 on the HD2 then download HSPL 4 (link in my sig) and flash HSPL 3.03. then try to flash your ROM again. If it flashes successfully then use the HSPL utility to reset y our correct SPL. I will have to go see if I can find the correct SPL for you if you don't know whioch one it is.
Thanks for your help, but I think I´ll rather return it for a new one then. This HD2 is for testing our mobile website, so one developer will need to wait a little longer for a replacement. This smartphone is 3 weeks old (half a week of use due to vacation), so I do not want to brick it and stick with it. Last time I did HSPL was with my old diamond, feels like a decade ago.
I am limited with downloads at my company due to firewall restrictions and I am not allowed to install programs. I am glad that I got USB allowed, though I am part of the admin crew
I´d even take it home, but I do not have windows running on any of my computers.
Ferrosti said:
I am not sure what you mean with bootloader? VolDwn+Power?
Click to expand...
Click to collapse
This is what I mean by bootloader, once you see the multicolor bootloader screen connect it to your computer via USB and wait for the Serial to change to USB and Right click the RUU for the ROM and run as administrator.
I understand you not wanting to brick it and your issue with downloads, that does suck. But the task 29 just does a wipe of the ROM partition of the NAND memory and reformats that partition. Task 29 is a very small download also, very very small, the same with HSPL 4. I suggested HSPL for as it will disable the CID check on the flash and allow you to flash a ROm that is not for that particular HD2. And all you have to do to revert back is run the HSPL again but pick the SPL not the HSPL you want, it ask you what version of HSPL or SPL you want to flash. Also you have a International HD2 and they are not as prone to bricking as the TMOUS because they can be flashed with any radio version for the HD2.
It comes to my mind that I have a damn old windows installation on my computer. Maybe I´ll give it a try at home over the weekend.
The phone does not even switch from serial to USB mode as you described. Could it be because there is no active sync installed? I tried it with my personal Desire HD and I got access to its SD card.
How do I find out which SPL to flash to have it back to its original state? Is it the 1.66.000 that was shown in bootloader? Where do I get it?
Go into the Bootloader and it should say the SPL version
Mines for example is
SPL-2.08.HSPL 8G XE
CotullaHSPL
If yours should say SPL-(version number) without the HSPL/Cotulla since it shouldnt have HSPL
If Windows has the drivers for the HD2 installed (Active Sync/Center installed) it will say USB as long as the plugs and the wire are good if it stays stuck on Serial that just means either the HD2 isn't detecting windows or Windows isn't detecting it
Ferrosti said:
It comes to my mind that I have a damn old windows installation on my computer. Maybe I´ll give it a try at home over the weekend.
The phone does not even switch from serial to USB mode as you described. Could it be because there is no active sync installed? I tried it with my personal Desire HD and I got access to its SD card.
How do I find out which SPL to flash to have it back to its original state? Is it the 1.66.000 that was shown in bootloader? Where do I get it?
Click to expand...
Click to collapse
Yes I think the SPL 1.66 is the SPL for the 1.72.111.4 ROM you are trying to flash. The phone is technically suppose to install the drivers when you connect it to a computer in bootloader, but I have had to download and install the ActiveSync and the Windows Mobile Device Center too to get a computer to recognize my HD2 in bootloader (two separate computers) so yes installing the latest ActiveSync on your computer can help as it has device USB drivers with it.
Dont install ANYTHING.
If the phone is only 3 weeks old, send the damned thing back for a replacement.
Had the same problem with a european t-Mobile HD2. Sometimes (rarely) let me boot into windows, but mostly didnt.
Sent it back to HTC and they fixed and returned it within a week. Actually they said on their site that they were fixing it, but I ended up with a new phone......
So... either return it to your supplier for replacement, or send it off to HTC
Andy
I don´t know how, but I got it running on the day we have been discussing.
If I only knew how it worked I´d let you know.
After all this I put it on the charger and retried a last time before I would have taken it home (read above). I flashed the new T-Mobile branded ROM and it just worked.
Thanks for your help!
I just got HD2 Tmous from ebay for parts to fix another that I sliced and cut the LCD flex cable. The phone is in great condition and after I put in the battery from my old phone it booted up and stuck on stick together screen. I booted up to the bootloader tri-color screen and it displayed the following:
PB8112 HX-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x05
After I used the USB cable to connect to my PC running Windows 7, the Serial at the bottom changed to USB. I downloaded Windows Mobile Device Center 6.1 and installed and run it. The WMDC said USB not connected. I found the thread "Stuck on Stick Together Screen" with similar problem and was solved by re-stocking the ROM from Tmous. I downloaded it but renaming from exe to zip did not work in order to extract the LEOIMG.nbh. I found another thread "[TUT] Flash your ROM / Radio via microSD" and downloaded it. I copied the ROM to my FAT32 1GB SD card, inserted it in the phoned, booted it into the bootloader, and flashed it. It is now stuck at 10% for more than an hour.
LEOIMG.nbh
RADIO_V2 -
RCUST -
BOOTLOADER -
SPLASH1 -
OS
CONFIGDATA. -
Update in Progress...
(progress bar stuck at about 10%)
I forgot to verify that the ROM is for HD2 Tmous and don't know what it is - the thread did not mention it.
What should I do now?
Thanks in advance.
The part, where you stuck at 10% is the part, where it flashes the Radio Image. I stuck at it, when i choose the wrong ROM. Do you know, which ROM was the original one for your phone? Look it up on the internet and try it with it.
I saw, you wanted to extract the .NBH file. Try it with the Software "WinRAR". When you installed it, go to your RUU-Extractor file, right-click it and choose the point "Open in Winrar..." or sth like that.
I hope, that was a little help
Thanks,
I got it from ebay so i don't know its history. After more than 3 hours stuck at 10% and found out from other thread the ROM from Tmous was not a normal zip file that can be viewed directly from Windows Explorer, I used WinRar to extract the NBH file and pulled the battery out and put back in. The phone was rebooted and got the triangle failure symbol; I pulled the battery out and put back in and booted into the bootloader - it displayed these additional info: RUUNBH at top right and Upgrade ROM code error Please try again at the center. Also, the serial did not change to USB anymore.
(omitted some steps) I flashed the leoimg.nbh file downloaded from Tmous and the same problem happened.
Since ActiveSync does not connect to the phone and the bootloader does not function properly, any utility required ActiveSync and flashing with properly function bootloader will not work. I think there is no way for me to flash the Radio ROM, right? Is there any utility or mode that will tell me which version of Radio currently in the phone?
I am thinking of trying to flash the same HSPL and MAGLDR and see what happens after reading some more threads.
(omitted some steps) I flashed the leoimg.nbh
Click to expand...
Click to collapse
so it doesnt say 'fail' next to anything on the blue writing/grey background screen when you flash from sd card? like next to RADIO_V2 -? because it sounds like a pretty standard stuck radio (or stuck spl, tell me, did teh spl line change from your first post? (("(omitted some steps)" dont ommit anything, full detail is the only way to get accurate answers.))
Mostly this never gets fixed without a jtag, but sometimes trying all teh various roms for that particular phone (you sure its a tmous? if it is, DO NOT flash anything you didn't get from the tmous/htc website,,, if it doesnt work and you get frustrated after 100 attempts, and its late at night, dont think "oh ill just try a non tmous one, just to see" cos it will die.)
Things to read up on and try are the freezer trick, chill the phone for a while, then quickly try an sd flash (forget about usb flashing, if you are gonna fix it, its most likely sd that will do it),, trying various tmous stock roms (if you go in the tmous stock roms thread, DO NOT flash the first one in the list, , its not a real tmous rom and will brick you,, teh second and third would also be best avoided, with the manufacturing spl's, because going back to normal stock is tricky, , not impossible, but a pain none the less),, also have a play with hspl3 or 4, see if you can change the spl, because sometimes its the spl thats stuck, and not the radio (however sticking at 10% and not seeing anything next to RADIO_V2 - makes it almost certainly the radio,)
Nothing - no additional info besides the progress bar stuck at 10% described in 1st post and the SPL line did not change. I think the phone now has the exact info except there is nothing where serial was displayed before (yellow text info on red background) as my first post.
Omitted some steps: these are just steps to copy the ROM downloaded from Tmous website to the sd card for flashing (T-Mobile_HD2_MR_software_3.14.531.1.exe).
Yes, it's a Tmous. The void sticker is still there and the touch screen has the T-Mobile logo.
I knew that I had to flash Tmous ROM because HD2 Tmous has 1GB of ROM instead of the normal 512MB.
Unfortunately, most of shipped ROM links are broken. I wanted to try the 2.10.x.
Thank you for your help.
Hi All
Could do with some help here - I've got some info through searches etc, but most bricked HD2's seem to be through OS installations etc. The issue I've got is probably not that much different, but I'd appreciate any advice.
My totally stock HD2 has bricked itself. I got it as an insurance replacement for an O2 HD2 about 14 months ago, and from memory it isn't tied to O2.
I was browsing the interweb when the screen went 'sideways' - no problems I thought, just soft boot it....
Did that, screen rebooted as white with some black squares......
Current symptoms:-
On power on or soft reboot (red button/battery out) it restarts to a white screen.
Hard reboot has worked, but it still restarts to a white screen.
If I plug in the USB mains charger it gives a red light, but battery doesn't get warm, which I previously remember it doing on mains charge.
No connection to Win Mobile Dev Centre
I can start into the bootloader screen, details are:
PB81100 HX-BC
SPL 3.03.000 XE
MicroP (LED) 0x05
MicroP(Touch) 0x50
Bootloader can differentiate between USB & serial connection in the white section, when connected to PC.
I've tried a ROM update via HTC website RUU (albeit without the WMDC connection), both O2 3.14.206.1 & WWE 3.14.405.2 give a 270 error code - corrupted ROM.
My next idea is to try the SD flash method on the original 2GB SD card with leoimg.nbh from O2 RUU or WWE, extracted via WinRar, I'm a bit concerned about the battery power though - no way of checking current charge. I'd probably try it leaving the mains USB in.
As I said, any thoughts or guidance would be appreciated
Cheers
6X7
yes sd flash should be your next stop, and the phone should charge (albeit at normal speed, not fast charge like when winmo is running.) when left on the bootloader screen.
Thanks Sam
Tried the SD flash, O2 ROM says not allowed, WWE 3.14.405.2 comes up as:-
00018003
LEOIMG.nbh - FAIL
Radio V2 Fail
RCUST -
BOOTLOADER -
SPLASH1 -
OS -
CONFIGDATA -
Update Terminal
UPDATE FAIL
Next thing to try is probably HSPL installation followed by a custom ROM, OTOH I think this phone is dead - starting to feel like a hardware problem.
6X7
stuck radio.
pretty common error.
basically, the bootloader/spl/radio area gets corrupted, and you get one some or all of teh following symptoms
1 - stock roms fail to flash with the error Radio V2 Fail
2 - custom roms flash and work
3 - custom roms flash but dont boot
4 - flashing hspl 'seems' to work, but nothing changes
5 - nothing flashes at all
solutions
there isn't one. sometimes the user solves it by trying again and again to flash, sometimes trying the earlier correct stock roms for that particular phone
(so, for example an o2 uk phone, try the 1.43, 1.72 and 3.14 o2 roms ((note that for unbranded phones, teh version sequence is 1.43 1.66 and 3.14)))
, sometimes with the addition of using the freezer trick, and eventually it flashes, however (and its a big 'however') more often than not nothing fixes it, except JTAG, andf even then there have been a few failures with JTAG, in such cases one presumes its hardware corruption that can't be fixed even by JTAG.
This is all just theory, there are TONS of threads about it, and very very few have a happy ending.
next step
get the correct stock roms for your carrier/region and try flashing them from sd card using the freezer trick. If its gonna work, thats the most likely way to succeed.
First of all, sorry if this thread already exists, but for the past 2 days I've been searching the web for my problem, but no luck. So I'm asking for your help.
My device had android 2.3 few months ago. One day it got stuck at loading screen, and I thought the SD card was corrupted because the ROM was installed there, and I tried to plug it to the PC, the windows sound would play that a device is connected, but I didn't see the sd card listed in My Computer
. So I bought a new sd card 2 days ago, plugged it to the phone, and it still wouldn't recognize the sd card. So I tried a few solutions, like copying RUU_signed.nbh with a card reader, and renaming it to LEOIMG.nbh. That only gave me an error 'No Allow' 00028002.
HX-BC
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Right now I have copied Ruu_signed.nbh from RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
and renaming it to LEOIMG.nbh, and the phone is stuck on Loading...
I see the bootloader screen is missing the device model number (PB81100) so would suspect the nand chip has gone bad.
Do a search & perhaps try task 21 & installing a hspl via cottulla hspl4 (HD2wiki has links)
Also use rest pin rather than pull battery as sometimes can clear an issue but in cases like this expect picking up a donor device for a mainboard will be needed.
Mister B said:
I see the bootloader screen is missing the device model number (PB81100) so would suspect the nand chip has gone bad.
Do a search & perhaps try task 21 & installing a hspl via cottulla hspl4 (HD2wiki has links)
Also use rest pin rather than pull battery as sometimes can clear an issue but in cases like this expect picking up a donor device for a mainboard will be needed.
Click to expand...
Click to collapse
I think i've seen the PB81100 few times when I was trying different ROMs. Could you please link me an appropriate ROM for my case that I can install by putting it on the SD Card ? I cannot connect my phone to the pc, so im using a card reader to put things on the sd.
Just look in HD2 Wiki as have links to loads of ROMs & without seeing your device or knowing any of its history it very hard to know what is the correct regional cid rom for flashing.
I always do via USB & get a HSPL on first thus bypassing CID lock & making flashing less prone to problems over stock SPL. you will just have to guess most likely correct regional & brand ROM from what you know of the device & any branding logo it may have.
If lucky & persist a bit you may get something to flash :-/
Mister B said:
Just look in HD2 Wiki as have links to loads of ROMs & without seeing your device or knowing any of its history it very hard to know what is the correct regional cid rom for flashing.
I always do via USB & get a HSPL on first thus bypassing CID lock & making flashing less prone to problems over stock SPL. you will just have to guess most likely correct regional & brand ROM from what you know of the device & any branding logo it may have.
If lucky & persist a bit you may get something to flash :-/
Click to expand...
Click to collapse
Thanks for your reply, I just checked my folders to see if I have anything that I used before, and this is what I got.
DFT_LEO_MAGLDR113_DAF
NexusHD2-JellyBean-CM10_V1.4a
Recovery_v1.3_150M
And I currently have HD2ToolKit4.2.0.1 which is not of any use at the moment...
Edit: NVM, everything is working now.
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...