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.
Related
I have a 512mb hd2 and today, when i reboot my phone, magldr shows fatal hit 1 and it wont boot into android or enter cwm.
Therefore, i did a task29 and flashed a stock winmo rom using usb cable. However it wont boot into winmo. It shows the htc logo and it stucks there. Sometimes it show htc logo with rgb at the bottom and it will stuck there. I never get into winmo.
Then i tried flashing the stock winmo rom using the sd card method. However, when the phone say that the process is finished, i plugged out the battery. i didnt know that i have to press the red button.
Now, the phone will only boot into the tri coloured screen and the screen shows this:
e??????u HX-BC
(upside down "e" followed by some unknown and indescribable characters followed by a "u")
SPL-142.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
I cannot do anything else. I can't flash anything at all. It will end up in an error.
When i try to flash stock winmo rom using sd card, it will say loading... , then it will say checking... then this red numbers: 0058002 will appear on top then it will go back to the tri coloured screen again.
When can i do?
corrupted modelID, (the e??????u HX-BC bit)
I think JTAG is the only way out, and i've not actually seen hard confirmation that JTAG will fix it. there certainly isn't any flashing solution that i've seen, and we've seen this problem a fair few times.
Unlucky. Got warranty?
yes, its still under warranty. Would the warranty be void?
munchyzoo said:
yes, its still under warranty. Would the warranty be void?
Click to expand...
Click to collapse
Hi,
Unless you can flash an original WM ROM,warranty will be void.
You need to revert back to orginal... HSPL is a hack and your warranty is void.
Go to HTC site>support>download>ROM upgrade and choose appropriate ROM upgrade for your phone
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.exe
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less
and reboot to bootloader (the one with 4 colors,hold volume down button)
follow the instructions from there
That way you will have your original software with SPL restored and ready to send it for repair
No need for PC drivers etc.
Don't panic, faced this situation before.. create a goldcard .. follow this thread
Really? Goldcard ignores modelid? You sure? Cos that would imply that you could use a hd2 Goldcard to flash any winmo rom to any winmo phone, which you can't. I'll be interested in anyone confirming absolutely that a phone with a corrupted modelid in bootloader can be flashed from Goldcard.
@op. Yes warranty is valid If your boooader shows a valid spl, ending 0000,because you tell them you woke up and it was on the charger, hot, and in bootloader, screen on, that top line looks wrong, you tried to flash the stock rom but it fails. So long as the spl is good is usually enough for warranty.
Yes with goldcard you can put any HD2 rom on any HD2 phone, debrand .. make it chinese or whatever.
And that's my slightly sarcastic point,,,,, if the modelid is corrupt the Goldcard won't recognise it as a hd2.
munchyzoo said:
Now, the phone will only boot into the tri coloured screen and the screen shows this:
e??????u HX-BC
(upside down "e" followed by some unknown and indescribable characters followed by a "u")
SPL-142.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
When can i do?
Click to expand...
Click to collapse
I saw on the bottom Mr Samsamuel is here, he point me a lot of help to revive my HD two days ago, now my hd2 is up and running. First you failed with MAGLDR, and you did to revive with stock rom. what stock rom did u use. More info will help many hd2 guru here
I believed before you flash anything (as I understood from own experience) flash HSPL, do task29, flash Radio. Just try and let us know. alert : do not do this on Virtual Machine
I have step by step edited copy tutorial to install cLK on hd2, it also can be use to revive brick hd2 (at some level of brick) PM me I will send by email
let us have coffee
the stock rom I use is hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
but the problem is I can't do anything with my phone at all. i can't flash hspl or any rom at all...
Buy anyways i have gotten my phone back from htc and now its working. i am now afraid of installing magldr as i fear the same problem (fatal hit 1) will happen again.
I am now considering the old sd card method of running android.... (i think this is safer)
Not sure if clk would have a similar error or something... i have not try it before.
I have googled the magldr fatal hit 1 error and quite a few people have this problem but i can't seem to find a real solution to it. I remember reading somewhere that someone say it is caused by many bad blocks on nand due to excessive flashing. (not sure what this means and how to deal with it)
Since got back ur live hd2. It will no fun anymore. No singgle software 100% safe or bug free. Clk is almost same with MAG both are boatloader. Your bootloader from htc also not bug free.
Running os from sd card is slow. Its same as ur pc booting from live cd/usbstick or external hdd. That for emergency only, rescuing fail software etc. Just do everything carefully read all instruction asking forum and google. You will safe and have a lot of fun
Sent from my HTC Incredible S using XDA App
I have a Tmobile 1024 Leo. A year ago I put Android and WM on it. It was a dual boot, beacuse they had not done NAND yet. Well I dropped it and broke the screen. So it sat for a year untill I decided to to fix the screen. Now when you turn it on it will not go past the sticking together screen. I can boot it in to the tri-color screen and nothing else. I tried flashing it back to WM and it gets anywhere from 64-99% done, depending on what ROM I use, and then errors out. I tried to do it from the memory card and it will not go into the flash menu. Is this thing bricked? Do I need to have some one with a Riff Box make a go at it? Or am I missing something? If some one has ideas that would be AWESOME!
what does your bootloader say?
check out my thread, you can try the sd card method / task 29
I tried flashing it back to WM and it gets anywhere from 64-99% done, depending on what ROM I use, and then errors out
Click to expand...
Click to collapse
maybe post error or a screenshot of it
maybe at the error are some hints.
then whats your bootloader version @tri color screen?
tried task29?
maybe installed a wrong HSPL/SPL version?
You should download the HD2 Nand Toolkit from Nand Development.
http://forum.xda-developers.com/showthread.php?t=1090783
Install it and do a Task29 Wipe. From there on you should check your Radio. Most of the time you need 2.15.50.14. Then install HARDSPL 2.08 and then you can flash whatever ROM you like. Check this : http://forum.xda-developers.com/showthread.php?t=893948
Hope I could help!
jsmccabe78 said:
what does your bootloader say?
Click to expand...
Click to collapse
Okay the Tri-Color screen shows :
PB81120 SS-B3
SPL-2.08.HSPL 8G Xe
0x05
CotullaHSPL 0x50
Then in the top righ hand corner of the screen it shows.
RUUNBH
putti71 said:
You should download the HD2 Nand Toolkit from Nand Development.
http://forum.xda-developers.com/showthread.php?t=1090783
Install it and do a Task29 Wipe. From there on you should check your Radio. Most of the time you need 2.15.50.14. Then install HARDSPL 2.08 and then you can flash whatever ROM you like. Check this : http://forum.xda-developers.com/showthread.php?t=893948
Hope I could help!
Click to expand...
Click to collapse
I downloaded the tool kit like you recommended, and then did the task29 wipe. Then I tried to install the radio that you recomened. It installs to 96% done and then freezes. Not sure what to do next.
UPDATE:
Got MagLdr to install. When I push power then the volume button to get it to open, it brings up the MagLdr screen and then there are no options to use. But when it was flashing, the computer said error communicating with device, but the screen on the phone shows that it was at 100%.
Nevermindd
Sent from my HTC HD2 using XDA Premium App
Any good ideas or am I just screwed?
This is gonna sound dumb.....but try it on a different computer.
Sent from my HTC HD2 using XDA Premium App
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.
Hi everyone! After checking the forum on possible quirks that can be encountered when installing MAGLDR I hope someone can help me with the following:
I am trying to install Android on the HD2 via full-NAND-flash (i.e. directly via USB without SD card). I read tons of webpages and I believe I understood the necessary steps. Check the SPL; Install Hspl; Install MAGLDR; etc.
I tried to install MAGLDR 1.13 and everything went nice and quick: 100% complete on the phone; 100% complete on the PC; click on finish; phone reboot .......... and now the HD2 does not go past the green-on-white HTC splash screen. No boot.
I can still acess the colour-striped bootloader, which reacts if I connect the USB cable. No more.
What have I done wrong? Can it be recovered?
Thanks in advance for any suggestion.
You need to do a bit more reading (it's fundamental). Flashing MAGLDR is only the first step in getting Android on NAND. Next, you'll need to flash CWM and if you're going to install Android, you are going to have to have an SD card.
It's clear you read enough to get as far as you have. I suggest doing a bit more.
Start here:
http://forum.xda-developers.com/showthread.php?t=905841
Thanks but I don't think I can do much more at this point. The phone seems to be stuck (see my initial post). Cheers,
Did you try holding the Red power button down while the phone was powering up? That should take you into the Magldr menu.
Also, since you say you can get into the bootloader, have you tried reflashing Magldr?
Yes, I did. However, in the flash window, where you should see you are going from ROM version X to ROM version Y, this information does not show. The flash process seems to go through normally but then the situation is the same one.
The bootloader I can access is the normal one, with the red-green-blue stripes: it shows:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
On the bottom it reads "serial" and if I connect the USB cable it changes to "USB".
Do a task 29.
Flash radio 2.15
reflash magldr
Hope this helps
yz.hd said:
Flash radio 2.15
Click to expand...
Click to collapse
I think this is the case sensitive for the OP explained symptoms.
Flash 2.15 or any Radio Rom that supports 576MB.
I have used Task29+radio 2.15.50.14, the doloop file repackaged by shadrac.....
So in principle the radio should be the correct one.
Shall I try with the separate flashes? Would you please let me have the links to download them?
(beginning to despair.....)
Thanks
Use HD2 Toolkit to re-flash MAGLDR 1.13... easiest and most comprehensive tools.. If u still stuck, re-install WM ROM (better custom ROM since u want to install AD NAND) this w keep ur HSPL. Once u are back to WM, repeat the whole cycle use the kit (pls confirm ur Radio 2.xx.50.xx (above 2.07.50.xx) and not the .51.
gd luck
Norton 360 doesn't like the HD2 tkit...
Any idea why Norton 360 discards the download telling me the HD2 Toolkit is a threat? That's odd...... the download link comes from this very site.
Anyone else with the same experience? Cheers!
i searched and searched all over xda but no thread could give any definite answer.
here's a summary of my problem:
I've been using android on my phone through NAND for quite a while, but the "tinkerish" part of me wanted to try windows phone 7 for a while. i "had" spl 2.08 and the correct radio, magloader also installed. but the problem was that i needed to perform task29 from hd2 toolkit but my phone wasn't being detected by pc...giving he "qualcomm driver" thingy....so i figured flashing a stock win 6.5 from sd card will make an easy alternative task 29 wipe then use active sync and reinstall hd2 driver....i tried the 3.14 wwe rom but it failed and now my phone is stuck at bootloader....can't DO ANYTHING!
it gives:
PB81100 HX-BC
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(touch) 0x30
please don't ask me to search and stuff...i'm kinda desperate now :/
Hey u have spl 3, and not hspl, the thing works with hspl 2.08 and not higher. Try installing hspl using hd2 tool kit.
Sent from my HTC HD2 using xda premium
Hi,
I have also faced similar situation.
I am to a newbie like you, see this thread it might be useful for you.
Best Regards,
Vikas
Try flash through RUU.exe
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
i cant go to bootloader,how to get back to windows 6.5?
the tricolor is bootloader ... hold vol down button + power. when you get the tricolor then flash whatever you heart desires (id personally start with hspl 2.08) then your options are limitless.
i cant go to bootloader becouse the volume key not work,what to do now?
ummmm :-S i would hate to be you friend!
hey, tricolor is NOT boot loader, that is the native recovery....
bootloaders are magldr and clk...and native wm bootloader also...
if your vol key is broken you have nothing to do....like dead I think...you need to enter into recovery for do anything! repair it if you want back your sweet phone
throcker said:
hey, tricolor is NOT boot loader, that is the native recovery....
bootloaders are magldr and clk...and native wm bootloader also...
if your vol key is broken you have nothing to do....like dead I think...you need to enter into recovery for do anything! repair it if you want back your sweet phone
Click to expand...
Click to collapse
The tricolor screen is the bootloader, and even if I'm wrong (I may well be) then everyone refers to it as the bootloader and you should also refer to it as the bootloader in order to make things clear and not cause confusion, it just makes things much better that way. Most people refer to cLK and MAGLDR as cLK and MAGLDR anyway, so there isn't much point in trying to change things.
Nigeldg said:
The tricolor screen is the bootloader, and even if I'm wrong (I may well be) then everyone refers to it as the bootloader and you should also refer to it as the bootloader in order to make things clear and not cause confusion, it just makes things much better that way. Most people refer to cLK and MAGLDR as cLK and MAGLDR anyway, so there isn't much point in trying to change things.
Click to expand...
Click to collapse
+1
Flashing back to window does not require volume key.
Are you with tmo or eu?
If you are tmo I do have a file that work if you want to revert back to window 6.5.
Try this for getting back to win6.5
I use it all the time when in trouble, and it always gets me out of trouble.