Related
Hy guys and girls.
I am a bit confused here and would like to ask for some help, by the way I already spent a lot of time lookign for answers here but I get more and more confused.
Well I wanted to try some Roms and I saw the high suggestions to install the HDPL first to avoid bricking my expensive HD2, well I tried but the problem is here.
FYI my HD2 is a Telstra version. It came with a black GUI style I guess it was the world wide version, but I am not sure as I did not recorded any info (did not thought on that), then I installed the original Australian Rom (at that time I was not looking for fancy Rom just for the latest upgrade and did not even know about cooked roms). Then I came back to the worl wide version because the autralian one was too bloated, not as nice as the black GUI and it was slower.
Finally I tried the HSPL2 to start tring with ROMs but it gave me an error message telling me I had the wrong version or something like that (I supposed because it is the Telstra version).
Then I tried the HSPL (older) but it gave me an error message telling me I need version 1.42.00. Here it get confused for me: When I do VolDwn + Power I get the following information:
PB81110 HX-BC
SPL-1.42.HSPL XE
0X05
CotullaHSPL 0x40
Serial
1st - Well I read that 1.42.HSPL was supported by HSPL so why it is not being accepted?
2nd - Why my unit is stating CotullaHSPL if I never installed it before? Cotulla comes with it?
3rd - Whats is HSPL in a interaction perspective? It is just a software that sit there and work alone without any GUI or it is something that does have a GUI that I can choose options and things to do? I am still lost on that.
4th - Sorry for the noob questions, but I apreciate if there is someone with patience to help me out (thats what I do when I can help someone).
Thank you
Felipe
Try reading the post about the HSPL:
http://forum.xda-developers.com/showthread.php?t=611433
and this tutorial about flashing ROMs:
http://forum.xda-developers.com/showthread.php?t=609477
Concerning your questions (I'm no expert either, but here goes):
1. You already have HSPL, so no need to install it again
2. Cotulla is (one of) the developer(s) of the HSPL, sort of a copyright
3. HSPL is a peace of software that essentially allows you to install other (custom made) ROMs or ROMs with another language. It has no Userinterface, but loads the ROM on your device
4. Your welcome
Ok but how it happened to get in there if I could not install it?
Perhaps it came with Telstra?
felcas said:
Ok but how it happened to get in there if I could not install it?
Perhaps it came with Telstra?
Click to expand...
Click to collapse
No, it will deffinately not have shipped with HSPL installed.
Sounds to me like someone already hspl'd it and installed a new rom. (black gui?)
did you buy it second hand?
samsamuel said:
No, it will deffinately not have shipped with HSPL installed.
Sounds to me like someone already hspl'd it and installed a new rom. (black gui?)
did you buy it second hand?
Click to expand...
Click to collapse
Hell no I bought it on Expansys, however the box that it came on had a picture of a Telstra one, with blue theme, but when I turned it on it was the world wide black theme and not the Telstra blue one, I changed it latter.
I even tried to instal the HSPL two or three times but it always gave me error messages and never showed the progress bar.
This is too strange for me.
Now I am very afraid if I really have the HSPL installed or a bugged or corrupt HSPL on it because of my failed tentatives.
what you guys suggest me to do to be 100% sure I have HSPL on it before installing cooked ROMs?
Thank
Felipe
i also bought a telstra version t9193 too. The seller ask me for permission to install the Official Rom for me. They state that i will have connection problem if i choose to stay with telstra's rom. So let them install HSPL and Official Rom since i don't want to deal with the connection problem when i have the device. I believe your seller install the HSPL and Official rom for you because they know u will have the connection problem.
felcas said:
Hy guys and girls.
I am a bit confused here and would like to ask for some help, by the way I already spent a lot of time lookign for answers here but I get more and more confused.
Well I wanted to try some Roms and I saw the high suggestions to install the HDPL first to avoid bricking my expensive HD2, well I tried but the problem is here.
FYI my HD2 is a Telstra version. It came with a black GUI style I guess it was the world wide version, but I am not sure as I did not recorded any info (did not thought on that), then I installed the original Australian Rom (at that time I was not looking for fancy Rom just for the latest upgrade and did not even know about cooked roms). Then I came back to the worl wide version because the autralian one was too bloated, not as nice as the black GUI and it was slower.
Finally I tried the HSPL2 to start tring with ROMs but it gave me an error message telling me I had the wrong version or something like that (I supposed because it is the Telstra version).
Then I tried the HSPL (older) but it gave me an error message telling me I need version 1.42.00. Here it get confused for me: When I do VolDwn + Power I get the following information:
PB81110 HX-BC
SPL-1.42.HSPL XE
0X05
CotullaHSPL 0x40
Serial
1st - Well I read that 1.42.HSPL was supported by HSPL so why it is not being accepted?
2nd - Why my unit is stating CotullaHSPL if I never installed it before? Cotulla comes with it?
3rd - Whats is HSPL in a interaction perspective? It is just a software that sit there and work alone without any GUI or it is something that does have a GUI that I can choose options and things to do? I am still lost on that.
4th - Sorry for the noob questions, but I apreciate if there is someone with patience to help me out (thats what I do when I can help someone).
Thank you
Felipe
Click to expand...
Click to collapse
felcas said:
Hell no I bought it on Expansys, however the box that it came on had a picture of a Telstra one, with blue theme, but when I turned it on it was the world wide black theme and not the Telstra blue one, I changed it latter.
I even tried to instal the HSPL two or three times but it always gave me error messages and never showed the progress bar.
This is too strange for me.
Now I am very afraid if I really have the HSPL installed or a bugged or corrupt HSPL on it because of my failed tentatives.
what you guys suggest me to do to be 100% sure I have HSPL on it before installing cooked ROMs?
Thank
Felipe
Click to expand...
Click to collapse
Hello man, I'm brazilian to, so if you want send me a PM I will explain things better in portuguese
Think in SPL/HSPL/SSPL like a BIOS in a PC, it will help you to understand some things. The SPL/HSPL/SSPL are the first softwares that the phone loads.. Read more here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
If you phone shows HSPL on the bootloader and it boots, probably your HSPL is not damaged.
Stock phones does not comes with HSPL (that is secure unlocked), it comes with SPL. Probably the seller flashed HSPL on your phone.
So, it is simple to know if you have HSPL or not:
Reset your device - press volume down - Read the screen and if it has HSPL or anything similar, you has it!
Another way is more objective:
Download a custom ROM, then try to flash it via MicroSD method. If it flashes, you have HSPL, if not (security error), you don't have it
Does not metter what version of HSPL you have on your device, it will falsh any custom ROMS. **be carefull** ..................READ READ READ.......................
I sugest Sternas ROMS (ARTEMIS).. It has PT and is very stable.. Take a look here: http://forum.xda-developers.com/showthread.php?t=612580
I hope it helps!
Have a nice flashing
Digao100nocao,
I tried to upload Artemis with the MicroSD but nothing happens, not even an error message.
I changed the name and formated the MScard and copied it to the card but as soon as I get into the bootloader nothing else hapens. When I restart the old ROM is still in effect.
I can only upload it with the CustomRUU, but doing so does not overwrite the HSPL.
As more as I try more it is confusing and weird.
To make things even more scary this morning my earpiece stop working, now I can't hear anything thru it, I hope this is some software problem and I can get it to work.
What I want to do now is just uninstall the current HSPL as I do not trust on it anymore and reinstall a fresh new one. Problem is that I can't find an old version 1.42 to install it thru the MicroSD, only .exe files.
Hi,
I've got some major problems with my HD2. First of all, it was running well. Last Saturday, I wanted to update my NAND TyphooN_CM7_v2.5 to TyphooN_CM7_v2.8.1. I opened CWM and made a backup. Afterwards, I installed the 2.8.1 version and after the reboot, I restored the backup(I think that's my mistake).
After that, I checked the build-version - it was still 2.5..
A little confused, I went to buy a BD. I recognized in the car, that the wake up bug happened again and I resetted the phone. Then, it worked fine.
Back at home, I took my phone in order to reinstall the 2.8.1 version. Suddenly, the HD2 only showed a clear white screen. I didn't boot and MAGLDR didn't appear either. So I tried to reinstall MAGLDR - didn't work(sometimes it's the 270 error, then it's the 262..)
What I've done till today:
-Tried to reflash HSPL
-Hardreset
-Tried to flash a tmo original WM Rom via USB(262&270 error)
-Tried to flash a tmo original WM Rom via SD =>No Flash Screen appeared
I'm kinda stuck cause the damn phone won't flash...
The usb connection is functionnable(the HSPL installer recognizes the HSPL version on the phone)
Hope you can help me
Greets
Erbse
Did you use s USB Micro SD card reader to copy tbd leoimg.nbh file to your SD card, and are you sure your SD card is formated Fat 32? Also go to your device manager in the control panel of hour computer while your BD2 is connected via USB and in bootloader. Make sure it says HTC USB Sync.
Yep - I'm sure about everything you mentioned
What to do next? The previous owner assured that the phone's got t-mobile de branding..
I guess then it is necessary to use a t-mobile Rom..
I'm quite confident, that it's not completely bricked - I can still enter the bootloader and the hard-reset mode
Give me some ideas
Erbsenkönig said:
What to do next? The previous owner assured that the phone's got t-mobile de branding..
I guess then it is necessary to use a t-mobile Rom..
I'm quite confident, that it's not completely bricked - I can still enter the bootloader and the hard-reset mode
Give me some ideas
Click to expand...
Click to collapse
Yes if you want to go back to stock and start over this is a very good idea. If you have the T-Mobile Leo with 1024MB RAM then yes only flash the T-Mobile official ROM to your HD2 as the any other official ROM will either brick your HD2 or the ROM will not function properly. Most of the time they brick a T-Mobile HD2 though as they have radios with x.xx.51.xx with them or a radio like these 2.04.50.xx or 2.05.50.xx. Any of those radio versions will brick a T-Mobile HD2
Also this may or may not help but I suggest it as it might help you out. Go to windowsmobile.com/getstarted and download the latest version of ActiveSync or Windows Mobile Device Center depending on what Windows your computer uses. The lateast releases have updated USB drivers and sometimes this is the problem when people are having issues flashing via USB.
You also had said you have tried the stock ROM already so you probably do not have HSPL anymore unless you got HSPL to reflash. So you will either have to flash a stock ROM or flash HSPL again so you can flash a custom ROM.
T-Macgnolia said:
Yes if you want to go back to stock and start over this is a very good idea. If you have the T-Mobile Leo with 1024MB RAM then yes only flash the T-Mobile official ROM to your HD2 as the any other official ROM will either brick your HD2 or the ROM will not function properly. Most of the time they brick a T-Mobile HD2 though as they have radios with x.xx.51.xx with them or a radio like these 2.04.50.xx or 2.05.50.xx. Any of those radio versions will brick a T-Mobile HD2
Click to expand...
Click to collapse
As far as I know, it's the 512 MB Version - a friend of mine made me check it the first day I got it
T-Macgnolia said:
Also this may or may not help but I suggest it as it might help you out. Go to windowsmobile.com/getstarted and download the latest version of ActiveSync or Windows Mobile Device Center depending on what Windows your computer uses. The lateast releases have updated USB drivers and sometimes this is the problem when people are having issues flashing via USB.
Click to expand...
Click to collapse
Already done
T-Macgnolia said:
You also had said you have tried the stock ROM already so you probably do not have HSPL anymore unless you got HSPL to reflash. So you will either have to flash a stock ROM or flash HSPL again so you can flash a custom ROM.
Click to expand...
Click to collapse
The bootloader still says
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
Ok you still have HSPL 2.08 wich is good as this means you can flash a custom ROM if you want to. Bit be advised that seeing as you have the 512MB version if you use any 3.14 official ROM or 3.14 based custom ROM then you will have to have SPL 3.03.0000 or HSPL 3.03 or you will incounter memory problems, also you will need a Radio version with a 50 in it. bit yhis is only if you are going to use Windows Mobile, if you are going Android don't worry about this.
Now what all have you tried sense your first post, and have hou tried a task 29?
I tried
-several USB ports
-AV and firewall off
-tried to install the other HSPL version(HSPL3 installer)=>Installer says "successfully done"..but there's no change in the bootloader
What's next?Task 29?
Btw: My battery LED doesn't turn green I charged the HD2 the whole night and in the morning, the LED's still orange..Looks like the first MAGLDR. With the first version, the charging didn't work when the phone was off. I had to take the battery and reinsert it. It's like that at the moment...
You want to make sure you have atleast a 50% charge or more on your battery cause you do not want your battery to die whild you are flashing anything as it will almost assuredly lead to your HD2 being bricked.You are right about MAGLDR too and that your HD2 has to be on to charge. Task 29 will delete what ever is in your NAND memory of your HD2 and reformat the NAND memory also. It is always a good idea to run a task 29 when you are going to flash a new ROM of any kind. Be advised though Task 29 will remove MAGLDR from your HD2. Here is a link to Task 29 so you can learn more about it anx download it if hou want to give it a try.
http://forum.xda-developers.com/showthread.php?t=644781
Thx buddy
But how can I be sure about my battery? The HD2 doesn't show me the battery status and I can't recognize it because the LED doesn't change
Erbsenkönig said:
Thx buddy
But how can I be sure about my battery? The HD2 doesn't show me the battery status and I can't recognize it because the LED doesn't change
Click to expand...
Click to collapse
That is a very good point as you have to have a ROM of some kind on your HD2 to get what percentage oc charge your battery has. I also do not know of any software you can get for you computer that can give you this information, but that is not to say it does not exist. You can try googling it to see what you can find. But the best bet is for you to boot up into MAGLDR and pmug your HD2 up to your wall charger and lrt it charge for 45 minutes to an hour and gou will have enough charge then.
MAGLDR doesn't start - the phone's stuck in that screen
The phone's been charging for about 90 minutes - I'll now try task 29
Task29 doesn't work either..
ERROR 262
Somewhere, there's a problem with the connection..but I can't see where
EDIT: I reinstalled the WMDC drivers - still the same error..
EDIT2: Same error with the original windows update drivers
Finally, I managed to use the SD card..
But then, the flashing failed
What now?
EDIT: After a couple of minutes, I pushed the reset button..The bootloader's still there The bootloader says still the same things as mentioned earlier and the usb connection is still working
I know this might be a redundant question, but are you absolutely sure you have the correct stock ROM for your HD2? Also are you 100% positive you have a T-Mobile Leo with the 1024MB ram and not a EU model with 512MB ram?
No problem buddy
I used this german website:"[Upd.19.02] Downloadübersicht HTC HD2 ROMs ( orig. & Betreiber ), Radio und Hotfixes and I took the first T-mobile rom(as it was an advice of an user)=>Auslieferungsrom(means like the rom the phone had when you bought it)
And I'm sure about the 512MB version - it's definetely a EU version!
Erbsenkönig said:
No problem buddy
I used this german website:"[Upd.19.02] Downloadübersicht HTC HD2 ROMs ( orig. & Betreiber ), Radio und Hotfixes and I took the first T-mobile rom(as it was an advice of an user)=>Auslieferungsrom(means like the rom the phone had when you bought it)
And I'm sure about the 512MB version - it's definetely a EU version!
Click to expand...
Click to collapse
OK so your phone looks like the picture of the one I attached below. Does the Duesch Telecom(sorry if I did not spell that right but I know they are the mother company of my carrier T-Mobile USA) not have a website you can download a official ROM from? Sorry I am still translating the stuff on the site you linked lol
Yeah, it looks like that. First, I downloaded the 3rd t-mobile Rom(directly from their website). But then a user told me to take the first version..
So you down;loaded this ROM and flashed it correct.?
Auslieferungsrom/Deutsch 1.43.111.2 2.04.50.22
And you had wanted to flash this one but was told not to correct?
01.02.11 / Deutsch 3.14.111.1 2.15.50.14
Who is your carrier by the way?
Edit: Could you not use one of the ROMs from here
I extracted the "Auslieferungs-Rom" and copied the *.nbh on the SD Card. I renamed it and tried to flash it - got to error message from the picture above.
My carrier is t-mobile de
I'm not sure if I can use a Rom from the HTC website When I use my SN, the website says "Sorry, this software download is not suitable for your device"
PS: Is it possible, that the flashing failed because of the different Radio versions? As far as I know, the version 2.15.50.14 is installed on my HD2. The "Auslieferungs-Rom" is mentioned with an other version..
EDIT: On the german HTC website, my SN only works for T-Mobile Roms.
I never experienced any problems whatsoever with my previous HD2. It had the Vodafone ROM on it (latest). Unfortunately I lost it a few months ago but bought a used one shortly after.
This HD2 unfortunately died on me. I bought a used motherboard through eBay from a guy in England (I'm in the Netherlands myself) and replaced the broken motherboard with the one from eBay. This brought my HD2 back from the dead.
But I noticed it had a weird Arabic ROM version on it so I wanted to flash the latest official HTC ROM on it. This at first didn't work because the RUU kept complaining the ROM was not suitable for this HD2.
So I first flashed HSPL4 after which I was able to flash the official HTC ROM v3.14.404.2.
But my problem is I'm constantly encountering what seems memory related problems. Sometimes I want to start a program and I get a pop-up saying there's no sufficient memory available to start the program. Other times nothing happens at all when I try to start a program. Or for instance the display doesn't update properly. The only that helps is switching the phone off and restarting it again (soft-reset).
But I need to soft-reset my phone about 5-10 times a day.
I've tried reflashing the ROM a few times now, even did a Task29, but I still get the same errors.
Is this a ROM problem or a hardware problem? Or is there any way to troubleshoot what could be causing this?
what does the spl line say in bootloader? a 3.14 rom wont run right on any thing except 3.03.0000 or 3.03.hspl, it loses a few hundred meg of ram.
Ah, well that's the problem then.
Code:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
I'm pretty sure I used DFT HSPL4 to install the HSPL. Can I use that too to install SPL 3.03?
Zippy1970 said:
Ah, well that's the problem then.
I'm pretty sure I used DFT HSPL4 to install the HSPL. Can I use that too to install SPL 3.03?
Click to expand...
Click to collapse
To answer my own question, I just used HSPL4 to install SPL 3.03.HSPL.
The difference I immediately see is that my total program memory went up from 208.81MB to 336.77MB and (more importantly) free program memory went up from 46MB to 173MB.
common error, most people dont notice the dropdown selector in the hspl.exe program, or dont really get what the options mean. for all non 3.14 roms, they will all run on any spl.
Just to let you know that switching to SPL 3.03.HSPL seems to have solved all my problems. Well, the HD2 related ones that is.
Everything runs very smooth now (some programs that didn't run at all now run without problems) and I haven't had a memory related error since.
Thanks!
Hey, my sister got a HD2 off ebay, and asked me to flash it to android, so i got to the point of installing MAGLDR, and after it successfully flashes, it doesn't boot into it, it just hangs on the HTC boot logo. I used to have a HD2, but it came pre-flashed with android.
I have flashed it with HardSPL too, before you ask.
how long did you wait? sometimes it takes 10+minutes before it boots.
did you try an SD version? it also boots via Magldr.
What steps did you take?
Did you task29 before flashing magldr?
My advice get the hd2 nand toolkit and Task29 before Flashing magldr
http://forum.xda-developers.com/showthread.php?t=1090783
Symptom - Flashed magldr folowed by hanging at splashscreen and not entering magldr menu.
Cause - nearly always caused by forgetting that magldr WILL ONLY start when spl =2.08.hspl -AND- radio is tmous compatible (meaning 2.07.50 or higher, where the .50 is not. 51,,, 2.08.50 will work 2.08.51 wont)
Go flash radio 2.15.50 and whilst you are in bootloader check what the spl line says.
I think i forgot the radio flash, will try it tomorrow.
You have to be careful with the Radio flashing. It is a good way of bricking your phone. I have had the same radio on my HD2 since I got it and never needed to change it. I have ICS running on it now and I am still on the same radio. You may have used the wrong version of HSPL when you flashed that portion. I would make it stock and start from scratch...follow this guide to make it stock and start from the begining.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
You only need to worry about flashing an incompatible radio with TMOUS phones, and as far as I know you shouldn't ever need to change the radio of those for Android anyway, so everything should be fine.
Sent from my HTC HD2 using XDA
Nigeldg said:
You only need to worry about flashing an incompatible radio with TMOUS phones, and as far as I know you shouldn't ever need to change the radio of those for Android anyway, so everything should be fine.
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Actually, I don't think the OP mentioned the type of HD2. It could be either us or int.
Sent from my HTC View in LALA land.
Updated the radio, worked fine.
thanks for the help guys
stevedebi said:
Actually, I don't think the OP mentioned the type of HD2. It could be either us or int.
Sent from my HTC View in LALA land.
Click to expand...
Click to collapse
We can safely assume he's got an EU phone as not only is he from the UK but he's got a .51 radio (Android isn't booting), and I think that all of the TMOUS phones come stock with a .50 radio (or bricked )
Same Problem
I know...I know I'm about to get a beat-down for not reading the forums properly on xda but, there's soo much information that I don't know where to start! It will be much appreciated if someone can help:
I got a HTC HD2 on T-Mobile (UK) - I have the one that reads 448mb of RAM
It has the latest official ROM since it was downloaded from the HTC site (site link no longer available)
The radio version is 2.15.50.14
I have also installed HSPL (it reads SPL-3.03.HSPL)
Tried to install MAGLDR via the HD2 Android NAND Toolkit
Now my phone wont bootup....just stuck at the loading screen (the pink circle arrow)
What do I do? :-s
You need hspl 2.08 to do install magldr!
clk works with 3.03.
I
Sent from my NexusHD2 using xda premium
If you know you're going to get flamed for not reading properly, surely the logical thing to do would be to go back and start reading properly? As shanman said, MAGLDR requires HSPL2.08 which you would have realised if you read any one of the numerous guides available (e.g. the one in my sig).
Nigeldg said:
MAGLDR requires HSPL2.08 which you would have realised if you read any one of the numerous guides available (e.g. the one in my sig).
Click to expand...
Click to collapse
or even sentence 4 of post 1 in the magldr thread, , , nice bold lettering.
Update: Maybe stock rom is not flashing because i'm not getting the correct ROM for this phone?
Could someone PLEASE help me identify the correct stock ROM with the below serial number of the phone?
Hi Xda gods,
I shows me as a noob because i forgot my old account password!
Anyway, I have with me a friend's EU HD2. Details as follows:
HTC HD2 T8585
S/N: SH06KNW01615
The following are the problems with the phone:
1. I think he had someone try to upgrade the radio on the phone WITHOUT HSPL first because it used to show a 'software update failed, please try again' msg when turned on.
2. Installed HSPL 2.08 successfully and tried to install radio version 2.15.50.** and that didn't work either. got an error 264 i think which said 'this update utility cannot be used on your PDA'.
3. Read in many threads that a possible solution could be to flash back to a stock ROM that came with the phone via SD card method but after abt 3% i get an error saying 'radio v2 FAILED, LEOIMG.NBH FAILED, Update Failed'.
4.Used Mtty and followed the steps..set value to 14 0, task 29, task 8...and then flashed a custom rom through SD card...
5.The cutom rom flased fine but now phone is stuck on 'HTC quietly brilliant' and does nothing else.
Could one of you brilliant minds PLEASE help me solve this problem? i tried for more than 7 hours yesterday but didn't get anywhere...
thanks in advance!
Custom ROM did not have a Radio included so expect trying a Radio such as linked in my sig may be worth another go.
If problems persists could be memory issue or other hardware issue.
Thanks Mister B for the quick response..
I tried flashing a radio before flashing a custom Rom but got the same 'This update utility cannot be used on your PDA' error..tried radios: 2.15.50...2.12.something..even 2.08.50 but all with the same error...
You try radio after flashing ROM ?
What custom ROM are you using ?
Try to flash official ROM. It will update your radio.
Sent from my HTC HD2 using XDA App
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
samsamuel said:
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
Click to expand...
Click to collapse
Thanks for the feedback.
Actually, HSPL flashes fine..after the 'we hacked it' screen i go into bootloader again and the HSPL has installed.
With custom Roms, they flash fine but stay stuck at the boot screen and nothing else.
Tried every possible method even with Mtty but to no avail! No radio will flash!!
I'm currently on 2.08 but i will downgrade to 1.66 or 1.42 like you said and try again..
It was a branded htc but i installed HSPL..should i still try only stock roms or custom roms are fine?
Also, i saw in someone's post that their bricked HTC was brought back to life using the Goldcard method with dutty's Rom...maybe i can try this method.
Will let you guys know how it turns out.
Excuse me "hijacking" the thread with a question - I've been through this and another long thread about "stuck" radios and not seen a definitive answer (perhaps there isn't one).
In which part of the phone's firmware does the "carrier lock" reside, and what form does it take, is it in the bootloader, radio rom, or main firmware?
I've just purchased a second hand carrier locked HD2. I don't specifically want to unlock it as my sim matches it, but I have installed hspl, using hspl4, with a view to playing with ROMs, and wondered how far you can go without unlocking.
I'm quite used to flashing roms from previous unlocked HTCs I've owned, but I've never had a carrier locked phone before, hence the question.
You can flash away as normal, Carrier SIM lock makes no difference but for the cheap price of HD2 unlocking it may be wise to get a code & unlock it know rather than perhaps the future.
Thanks. I might well take your advice on unlocking bearing in mind the minimal cost.
Still puzzled, as a few of the queries I've seen seem to suggest the problems flashing different radios some folk were having were down to the phone being carrier locked. Or, maybe it was just a case of certain radios only working with certain firmwares (and maybe with certain spls) and nothing to do with carrier lock at all?
Sorry for my apparent ignorance on the subject!
Pete_S said:
Still puzzled, as a few of the queries I've seen seem to suggest the problems flashing different radios some folk were having were down to the phone being carrier locked. Or, maybe it was just a case of certain radios only working with certain firmwares (and maybe with certain spls) and nothing to do with carrier lock at all?
Click to expand...
Click to collapse
you have a regular hd2, therefore all radios will work on your phone, , but with some caveats.
If you intend to
a - use wp7 or nand android..
b - use a custom wm6.5 rom that unlocks the 576mb ram
then you MUST have a tmous radio - which translates to - you MUST use a radio with ..50.. in teh version.
i.e 2.07.51. will not work, 2.07.50 WILL work.
ALL radios will have either 50 or 51 in that third set of digits, if a radio doesn't, dont download it, go find another one. (some radio downloads may show the protocol version first, so it may say something like ''15.32.50.07U 2.07.51.22 2'' in which case its a 51 radio
Many people (myself included) find that some radios give slightly better reception and/or battery and/or less wake from sleep issues than others, however its not consistent, , what works well for one hd2 may not be the optimal for the next hd2 in the same location.
In general tho, most people seem to have settled on 2.11.50, 2.12.50 2.14.50 or 2.15.50.
(For simplicity, go flash 2.15.50 and you can forget about it till you've got everything else working)
Dont bother going lower than 2.10, theres nothing down there thats any better than those four.
As for the radio brick from flashing the wrong radio, thats tmous hd2 only, you can ignore that.
Carrier being locked will have no effect on anything you do, though you cannot unlock it under android, you need to be running winmo 6.5 to enter an unlock code and make it stick.
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Big note - - - Anything that refers to a tmous, or a tmobile hd2, or a tmobile radio, , does not apply to you, just because it may be t mo provided, or locked to tmo, or running a tmobile branded stock rom,. its still a regular hd2 you have (well, assuming you didnt get an import from the states? it would say t mobile under the earpiece, and have red and green end/send keys if its a tmous). Only t mobile usa bought a different version hd2 from HTC.
samsamuel said:
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Click to expand...
Click to collapse
Don't be! Sceptical, I mean... They're right!
I've managed to unlock by code a few TMoUS-version HD2s under Android(various versions, I don't remember...)!
Unlocking by wires is another story: it can be done under WM, only!
bib*oops said:
Don't be! Sceptical, I mean... They're right!
I've managed to unlock by code a few TMoUS-version HD2s under Android(various versions, I don't remember...)!
Unlocking by wires is another story: it can be done under WM, only!
Click to expand...
Click to collapse
Hmm interesting, noted.
samsamuel said:
(For simplicity, go flash 2.15.50 and you can forget about it till you've got everything else working)
Dont bother going lower than 2.10, theres nothing down there thats any better than those four.
As for the radio brick from flashing the wrong radio, thats tmous hd2 only, you can ignore that.
Carrier being locked will have no effect on anything you do, though you cannot unlock it under android, you need to be running winmo 6.5 to enter an unlock code and make it stick.
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Click to expand...
Click to collapse
Thanks so much for all the nuggets of info. I actually have radio 2.15.50 already, so it can't be bettered and is ready for android if I decide to go that route.
The info relating to Android and carrier lock (that it doesn't make any difference unless you want to unlock) is also very useful.
From what you've said it seems carrier locking has very little effect on anything other than, er, choice of sim
So, sorry to be persistent, where does the carrier lock info reside in the phone? In other words, when you unlock a phone, officially or otherwise, where are the bits of information which change? It's purely out of curiosity - I need to know these things
Sorry, no clue, I'd suspect some dedicated chip somewhere, since its not affected by anything we have access to. Just a wild guess tho.
Pete_S said:
Thanks so much for all the nuggets of info. I actually have radio 2.15.50 already, so it can't be bettered and is ready for android if I decide to go that route.
The info relating to Android and carrier lock (that it doesn't make any difference unless you want to unlock) is also very useful.
From what you've said it seems carrier locking has very little effect on anything other than, er, choice of sim
So, sorry to be persistent, where does the carrier lock info reside in the phone? In other words, when you unlock a phone, officially or otherwise, where are the bits of information which change? It's purely out of curiosity - I need to know these things
Click to expand...
Click to collapse
The SIM lock is part of the bootlaoder, more specifically the IPL. This is what only Win Mo ROMs can be used to SIM unlock a HD2 because only Win Mo ROMs can actually communicate with the IPL of the bootloader. Now let me go a little deeper, like Samsamuel said it is more than likely a seperate chip somewhere on the mainboard of the HD2 that actually stores the SIM lock but only the IPL can access and change the data on that chip.
Thanks to you both for the info. That would explain why being network locked has almost no effect on anything else like ROMs etc. The actual info might even be stored in flash in the chip which "drives" the sim.
I think the problem could be somewhat overcome if i knew which would be the correct stock rom for this phone! Its quite maddening!
My phone's serial starts with SH which i know is Shanghai, China but i haven't been able to find a 1.66 stock rom for this..
Thoughts?
samsamuel said:
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
Click to expand...
Click to collapse
Fone HTC support, they'll tell you in seconds.
Also, there are no branded 1.66 roms, ,, because branded 1.66 roms carry the verson number 1.72.