Database Users

[q] hd2 bricked (?)

Hello, I itried to install a rom not suitable fot T-mous and I can't recover the phone since Then. It's possible to help me out? I became really sad without my hd2.
I tried to install several different roms (official and others), everything seems fine but when it reboots goes to the white screen and reboots...when i enter bootloader shows:
PB81120 ss-b3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
Still charges through usb and the led is working but when i disconnect it from the pc..Turns off instantly
PLLLLSSSS Help me out through this issue

a plus point of it, ITS NOT BRICKED
DONT DO **** TILL PEOPLE SAY WHAT 2DO..
otherwise you will brick it...(trust me selfexperience, bricked my)
when its bricked, you cant do ****, the phone doesnt turn on, NOTHING happends.
just w8 till some nice people who have some experience want to help you (and me stuck with spl-3.03.0000)
So dont do anything yet!!

Firstly try switching on the phone without the SD Card installed.
If that doesn't solve your problem then:
Go to HTC's website and download a TMOUS ROM (preferably the 2.10 ROM) - you need to use your phone's serial number to get to download the ROM. If you get an invalid message, then you are trying to download a ROM not suitable fro your phone.
Press and hold the Volume Down button then tap the Power button. You are now in Bootloader Mode. Connect to the PC and the 'Serial' at the bottom of the screen will change to 'USB'.
Run the ROM. Just tick the box about ActiveSync.
If in future you are going to run a custom ROM, then check that it is suitable for a TMOUS. Only flash RADIOs with a .50 in it and above 2.07.50.

None of the suggestions...worked...Tried to boot without tha sd inserted...Noresult...And I have installed the two official versions of the T-mobile again with no result )):
Any other suggestions///????
Thanks ):

Sounds like quite a predicament. Have you tried any of the NAND android roms? Maybe a different os might get the phone to act differently.
I'm not going to say that this will work, but if it doesn't you should be able to hard reset back to a windows mobile os you have used previously by doing what you have done up until now with flashing them back on afterwards, putting you back to your current situation.

do a task 29. and try reflashing. (google "mtty for hd2" to perform task 29 )

[Q][Help] Android rom inssue crash on kernel (HSPL Installed?)

Hi guys. Im trying to install android on my HD2 as you may have guessed. First I have tried getting HSPL installed. It is from Virgin Mobile. It is not locked to a network as I run an 02 simcard in it.
To confirm this is already working my bootloader reads:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
It is has tri-colour and a white at bottom which reads "serial" that is then blank.
If this is correct all is good so far.
I then try and install android from my SD card (have tried multiple versions, all resulting in the same issue)
It boots up and starts running. Every version freezes on Loading Kernel.. or it runs and starts to blur out.
What am I missing in this process?
I have given as much information as I can think of. I look forward to your replies. Sadly I cant get online to tomorrow but look forward to a positive response xD

MaxSan said:
Hi guys. Im trying to install android on my HD2 as you may have guessed. First I have tried getting HSPL installed. It is from Virgin Mobile. It is not locked to a network as I run an 02 simcard in it.
To confirm this is already working my bootloader reads:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
It is has tri-colour and a white at bottom which reads "serial" that is then blank.
If this is correct all is good so far.
I then try and install android from my SD card (have tried multiple versions, all resulting in the same issue)
It boots up and starts running. Every version freezes on Loading Kernel.. or it runs and starts to blur out.
What am I missing in this process?
I have given as much information as I can think of. I look forward to your replies. Sadly I cant get online to tomorrow but look forward to a positive response xD
Click to expand...
Click to collapse
Hi,
I think you missed a couple of steps in the process.
please read this thread:
http://forum.xda-developers.com/showthread.php?t=893948
Check also my sig...guide number 2

Ok I think the difficulty may be something entirely different.
Ive tried installing all kinds of bits and pieces inc the new radio and magldr but they all seem to have the same issue.
When installing the phone reboots but once it loads to the bootloader it no longer detects it on the computer i get a three low beeps (like when a cable is unplugged)
Could this be an issue with my laptop specificly?

Fixed one thing.. turns out my laptop was missing the qualcomm drivers and not updating automatically so was just dropping the phone from the computer..
...ive installed magldr and new radios.. trying to boot android of SD card but it seems to be freezing on the black on green HTC logo display... im sure this issue has came up somewhere else so if someone can point me to a fix while i struggle on and see what I can find on my own back

first load should take longer than usual. just give it around 15 minutes.

HD boot screen issue hardware problem?

Hello and good morning
I have a issue with my HD2
i get to the boot screen right now it says this
PB81100 HX-B3
SPL-3.03 HPSL XE
0x05
Cotulla HPSL 0x50
i have even try to go back to SPL 2.08 also.
i do a boot screen to try to restore stock rom but it won't work.
i have installed MAGLDR111 on it and 113
When it turns on it goes in a Dexter loading please wait and sits there forever. i even left it there for half an hour once and nothing
When i go to SPL2.08 to boot stock rom it goes into effect it starts the process but it gets stuck at 3%
7% and the maximum i can get is 8%
Try it on two computers and is the same.
Even some custom roms.
LDR
If i hold the power button for the MAGLDR it goes into a black screen with the letter on top but no menu to scroll down to anything.
Can someone tell me if this a hardware issue and i should give up?
i got this phone like this from Ebay with booting up to the boot screen only.
i thought i was going to be able to flash it myself cause i done it before on other hd2
but this one is really giving me a hard time
I just try it again and I get 302 error
I hope someone can help me out. ifnot i will have to give up on it.

Hm you need to try to flash an original Windows 6.5 rom to restore your SPL and RADIO. Also check what kind of SD card do you have. Sometimes it fails with some.

i don't have a SD card in it im trying to flash it from boot mode usb
And i have try installing the original rom from tmobile.
but it keeps getting only to 8% and it gets stuck.
im at the point that now i think there is something wrong with the hardware.

crazerico said:
i don't have a SD card in it im trying to flash it from boot mode usb
And i have try installing the original rom from tmobile.
but it keeps getting only to 8% and it gets stuck.
im at the point that now i think there is something wrong with the hardware.
Click to expand...
Click to collapse
And change hspl from bootloader can?
Try to touch versions hspl and to stitch original ROM.
p.s. It would be certainly easier, if was available sd, but alas... Absence sd complicates a problem.

HELP: Phone wont start!

I need help. I wanted to install android on htc hd2, i previously had WM 6.5. I formated sd card and put Android rom folder on it...run clrcad.exe and haret.exe. It came to black screen with some text, last line was something about jumping to kernel. It was there like 15 min, i pulled the battery...now it wont start...what to do?

When i plug in the usb it boots up to htc screen and then again shuts and boots to htc screen and keeps going like that.

Bent battery pin.

i now have another problem, i installed magldr 1.13 and now its stuck on htc logo screen...only can pull out battery and go to bootloader...i had radio 2.xx.50.xx...all the text on bootloader is:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
what to do??

Go to tricolor screen. Install stock winmo ROM and make sure the phone boots up fine, etc. Then you can start messing with it again. Note - if you install a stock rom, your hard spl will be replaced.

Did you check the bent battery pin idea? And also, may want to try the thing stated above, but use a custom ROM.
Oh, and may seem obvious but you are holding the power button down when trying to boot MAGLDR right?

Is my bootloader corrupted or not

Please help
my HD2 has had been running NAND flashed andriod fine for the last 2 years. It has MAGLDR 1.13 on it.
Now on boot up it hangs up it hangs up after 123456 gogogo.
1.I tried to reflash using AD recovery and again it hangs up after 123456 gogogo (won't enter recovery)
2.I have tried flashing other rom (DFT_LEO_NAND_Andriod) via USB flasher, it flashes but again hangs up on booting up at 123456 gogogo.
3.I decided to flash a stock winmo 6.5 rom and on booting up the phone in bootloader
I flashed winmo 6.5 via USB and it flashed ok BUT on boot up the touch screen would not work.
Tried flashing the stock ROM bootloader SD card (renaming RRU_SIGNED.NBH to LEOIMG.NBH)
Again it flashed but the touch screen would not work.
On closed look at signs of any thing diffrent I noticed that the 3rd line of the Bootloader
was missing in the writing at the top.
PB1100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
xxxxxx(missing line which should say COtullaHSPL 0x30)
I can reinstall MADLDR 1.13 ok after installing SPL-2.08 HSPL.(HSPL4.exe) but an stuck on 123456 gogogo.
Is my problem to do with missing line in the Bootloader and if so is it recoverable.

have a try to task 29?maybe it will work~

rb2056159 said:
have a try to task 29?maybe it will work~
Click to expand...
Click to collapse
I've done task 29 with radio 2.15.50.14

Case solved!
happyhkv said:
Please help
my HD2 has had been running NAND flashed andriod fine for the last 2 years. It has MAGLDR 1.13 on it.
Now on boot up it hangs up it hangs up after 123456 gogogo.
1.I tried to reflash using AD recovery and again it hangs up after 123456 gogogo (won't enter recovery)
2.I have tried flashing other rom (DFT_LEO_NAND_Andriod) via USB flasher, it flashes but again hangs up on booting up at 123456 gogogo.
3.I decided to flash a stock winmo 6.5 rom and on booting up the phone in bootloader
I flashed winmo 6.5 via USB and it flashed ok BUT on boot up the touch screen would not work.
Tried flashing the stock ROM bootloader SD card (renaming RRU_SIGNED.NBH to LEOIMG.NBH)
Again it flashed but the touch screen would not work.
On closed look at signs of any thing diffrent I noticed that the 3rd line of the Bootloader
was missing in the writing at the top.
PB1100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
xxxxxx(missing line which should say COtullaHSPL 0x30)
I can reinstall MADLDR 1.13 ok after installing SPL-2.08 HSPL.(HSPL4.exe) but an stuck on 123456 gogogo.
Is my problem to do with missing line in the Bootloader and if so is it recoverable.
Click to expand...
Click to collapse
You got yourself an explanation: TOUCHSCREEN (faulty as you said)!
I've encountered a few cases of HD2 not passing over GoGoGo, just because of a faulty touchscreen!
Don't ask me why (I only may assume that Android on booting is checking/testing somehow touchscreen and this fails check/test), because my knowledge doesn't allow me to answer you, but I can assure you touchscreen failure is your explanation!

PB1100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
xxxxxx(missing line which should say COtullaHSPL 0x30)
So the missing line in the bootloader screen has nothing to do with it at all.
If the android does do a check then not sure if the AD recovery does the same.

Maybe you should try to "start over all again". flash stock rom, remove hspl, install hspl(the in windows mobile way) and hope its repaired. Could try that, if you wanna be sure if it isn't a software issue.

On a standard spl bootscreen the two lines below spl are
MicroP led and
MicroP touch, (no doubt hspl alters the txt to say cotulla) so the fact that the lines are gone would make me assume the hardware isn't responding to query. It could simply be an unseated screen/touch connection ribbon.
Agree with above post, your first step hasta be flashing back to stock.

Small observation
samsamuel said:
...
Agree with above post, your first step hasta be flashing back to stock.
Click to expand...
Click to collapse
He already did that, but same result:non-working touchscreen.
---------- Post added at 11:51 PM ---------- Previous post was at 11:49 PM ----------
That's what I mean:
happyhkv said:
3.I decided to flash a stock winmo 6.5 rom and on booting up the phone in bootloader
I flashed winmo 6.5 via USB and it flashed ok BUT on boot up the touch screen would not work.
Tried flashing the stock ROM bootloader SD card (renaming RRU_SIGNED.NBH to LEOIMG.NBH)
Again it flashed but the touch screen would not work.
Click to expand...
Click to collapse

I have been keeping a eye on this thread from the first day it was started. I see no definitive answer has been reached yet. And I am afraid I probably do not have the definitive answer either as that would require hands on time with the device.
What I can tell you is that if you have a missing line in the bootloader then that would be my best guess as to what is causing your issues. Unless as Sam said it is just a loose connection between the digitizer and the mainboard. If you have a TMOUS HD2 this is a worth checking out as the TMOUS HD2 has a connector on the digitizer ribbon where the EU HD2 digitizer ribbon is sodered to the mainboard. Back to the bootloader, the bootloader is what initializes all the hardware of the device on boot up. So if your bootloader has become corrupted somehow, then it may not be initializing the digitizer correctly or at all. I suggest you learn how to run what is equivalent to a logcat in Android. I have never done any real work with Windows Mobile bit I think it is something called RAPI Debug, I may be wrong. Here is a link to a page that may help you get started. If you can get a log on your computer of what is going on during boot up you may be able to get the definitive answer you are looking for.

T-Macgnolia wrote ..."If you have a TMOUS HD2 this is a worth checking out as the TMOUS HD2 has a connector on the digitizer ribbon where the EU HD2 digitizer ribbon is sodered to the mainboard. Back to the bootloader, the bootloader is what initializes all the hardware of the device on boot up. So if your bootloader has become corrupted somehow, then it may not be initializing the digitizer correctly or at all. I suggest you learn how to run what is equivalent to a logcat in Android. I have never done any real work with Windows Mobile bit I think it is something called RAPI Debug, I may be wrong. Here is a link to a page that may help you get started. If you can get a log on your computer of what is going on during boot up you may be able to get the definitive answer you are looking for."
Thanks for that, It is EU HD2 handset so from your insight in to the differnces between the US and EU handsets the ribbon is soldered on the M.board.
It might as well be the digitiser in the end. A bit more info, prior to complete failure I noticed on the previous 2 days that on boot up the Magldr would hanged up at 123456 gogogo and on removeing and refitting the battery booted in to Android Ok.
Again I don't know much about the windows boot loader, but the fact in allows flashing of ROMs with the faulty boot loader, I don't know if the Magldr NAND boot and the AD recovery has a check that IF the digitiser in not working then don't boot up.Know ing that it does do this check would confirm that the digitiser is dead.
I'll look in to RAPI debug see where that leads.

xxxxxx(missing line which should say COtullaHSPL 0x30)
Click to expand...
Click to collapse
In OSPL there is "MicroP Touch" string.
If this string is missing that can means that touch screen chip is not detected in software.
As well it can stuck after GOGOGO in touch screen driver init.
Should be hardware issue I think
Current MAGLDR versions doesn't use touchscreen at all. Future - may.

Cotulla said:
In OSPL there is "MicroP Touch" string.
If this string is missing that can means that touch screen chip is not detected in software.
As well it can stuck after GOGOGO in touch screen driver init.
Should be hardware issue I think
Current MAGLDR versions doesn't use touchscreen at all. Future - may.
Click to expand...
Click to collapse
There is the definitive answer you are looking for.
All hail Cotulla!!!

Cotulla said:
In OSPL there is "MicroP Touch" string.
If this string is missing that can means that touch screen chip is not detected in software.
As well it can stuck after GOGOGO in touch screen driver init.
Should be hardware issue I think
Click to expand...
Click to collapse
I've told you...

Many thanks for all your help for this, I shall endever to get the screen digitizer changed.