[Q] HTC HD2 Blackout - HD2 General

Hi, to everyone! Please, forgive for my bad English (I'm Russian)
So, I have an HTC HD2. There are Windows Mobile 6.5.3 Professional RUS. One day, I needed an MS Console for little network tweaking. All tweaks works fine. Than send my device to the Soft Reset (via shortcut by SPB Pocket Plus. I used this shortcut thousand times) And my device freeze at the first boot screen (with sign "Stick Together", and versions of radio, os, etc) I understand, that this "console" killed my os. So I decided to flash my HD2 with new WM 6.5 ROM. Boot my device to the Service Mode (HSPL), And start to flashing process. Everything works perfect, but afterwards my device show message that this rom is not suitable for my device.... Rom was from US HTC HD2. I started doubt about origin of my device, and looked under th battery: It's Chinese! This was too much...
Ok, it's bad, but not "the end of the World". I desided to download and install this ROM: RUU_Leo_HTC_RUS_1.48.411.1_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship. It's installed ok, without any problems, but after restart, device simply DO NOT TURN ON! It's shakes about 0.1sec, and that's all.... :crying:
As I read at at some forums, it means, that I destroyed IPL - initial loader, which loads SPL or HSPL.
So, is there ANY WAY to recover IPL or whatever it can be, without "programmer unit JTAG"??
P.S. Device are visible in "Device Manager" on my PC via USB as "Qualcomm CDMA Technologies MSM", with these Device IDs:
USB\VID_05C6&PID_9002&REV_0000
USB\VID_05C6&PID_9002
Which definitely not in Windows Mobile Device Center driver pack.
Also, "driveridentifier.com" says, that this is "Qualcomm Diagnostics Interface 3197".
I'm Running Windows 7 Ultimate x64

Well, the 'stick together' screen is from a tmous rom, (t mobile US), and if it IS a tmous phone, then the radio RUU_Leo_HTC_RUS_1.48.411.1_Radio_Signed_15.28.50.0 7U_2.05.51.05_2_Ship
has just killed it.
Any non tmous rom will destroy a tmous phone. Only JTAG will rescue it.
BUT
you say it is a chinese copy? How sure are you? They normally say 'made in taiwan' under the battery.

First, thanks for answer!
The first Rom, which I flushed, was with "TMOUS" postfix.
An after it successfully installs, my device says me that this rom not compatible.
But, the HSPL was alive...
About origin of my device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, as I understand, original US devices should have an SPL loader, but I already has an Cotulla HSPL 2.08:
And what's wrong with my last Rom? It has IPL inside? or SPL?

All stock roms contain an spl (notsure what an ipl is,alwaysalways assumed it was another word for spl.
Notsure what to suggest next,sorry.

As I understand there are 3 steps in HD2 Boot sequence:
1) IPL - invisble 'app', wich searches for SPL
2) SPL (HSPL) itself, which in normal mode loads OS and Radio drivers, in service mode searches for ROM's NBH files inside SD card and listens USB for similar data.
3) Loading OS's files.
As read at some forum, IPL - is a part of SPL. It doing only one thing: Initializing internal 'flash' memory, and gives control to SPL itself.

I have 4 TMOUS HD2s that have made in China on the build label
*Same as your images exept no big "Made In China" sticker, just the smaller print & just smaller print on battery but expect changes pending on manufacture batch.
& this is nothing to worry about as HTC has an assembly plant in China. Also have an HTC Desire that was made in China too

So, this means, that I have an US HTC HD2 Leo TMOUS, assembled in China?

scadl said:
So, this means, that I have an US HTC HD2 Leo TMOUS, assembled in China?
Click to expand...
Click to collapse
Yes, I have not seen one that has not been ...
assume this has the green answer & red end key colour to help identify it as a TMOUS.
Would assume as mentioned above that the .51 radio has killed it good & jtagging maybe only fix if it didn't have any other hardware fault causing original issue.

Mister B what you can say about recovery of my device? Do you also suggest to search for someone, who know, how to work with JTAG?
Also, dear specialists, what can you say about true US Smartphone Audiovox XV6600?.
It serves me for about 7 years without any problems!

Mister B said:
assume this has the green answer & red end key colour to help identify it as a TMOUS.
Click to expand...
Click to collapse
Yes, it has exactly that looking buttons
Mister B said:
Would assume as mentioned above that the .51 radio has killed it good & jtagging maybe only fix if it didn't have any other hardware fault causing original issue.
Click to expand...
Click to collapse
No, the original issue was because I installed strange app... It hasn't direct access to drivers. I think it just broke my Windows Mobile registry...
Or you think other TMOUS ROMs (which didn't start), could make another issues? But before the last ROM (it full name I wrote in first topic), device perfectly loads into HSPL!
Dear specialist, if I'll find someone, who can recover my SPL, Can I install any of Android NAND ROMs from this section, or there are also limitations, which breaking could lead to the similar device death?
Mister B, the look of my device in the attachments. What can you say about origin and quality of it?

If you can find someone at sensible cost to jtag it maybe worth effort repairing. You need get idea on cost then make decision on price, ease of repair (local, shipping abroad etc) & how keen you are to get it working again.
From Photos it look 100% original HD2 to my eyes via internet viewing.
Expect a couple other members can give you details & maybe a link to people who can jtag.
If thinking of Android it maybe a good time to move on, personally I think the custom WM6.5 roms such as from NRG are far better serious smartphone power & customization than Android at many levels.

Ahhh I didnt know about the china link to tmouses, , i've seen four euro hd2's and they are all made in taiwan.
scadl said:
Or you think other TMOUS ROMs (which didn't start), could make another issues? But before the last ROM (it full name I wrote in first topic), device perfectly loads into HSPL!
Click to expand...
Click to collapse
Why the tmous rom didn't work is odd but not at all unknown, just an unlucky bad flash, whatever, it happens, but that isn't what killed it, it was probably recoverable at that point, (unless it was an hardware fault of course). Its the last rom, the non tmous one, almost certainly.
When you flashed the non tmous rom, two or three things happened,
1 - if its an sd card flash, the spl(or hspl, whatever) is replaced by the one in teh rom, , if its usb flash, this doesn't happen if hspl is there.
2 - the radio gets flashed. This happens in both sd and usb flashes. From this point onwards, the phone was doomed. It still continued the flash right to the end, but as soon as it reboots, the new radio takes effect, and kills it.
3 - the rom itself gets flashed.

[26.01.2013]
I used USB flashing process.
It's seemed, I have the second case...
You think even jtagging can't recover device with wrong radio flashed?:crying:
[27.01.2013]
I gave my beloved HD2 to Service Center for JTagging. Tech Specialist says, that it cost me approximately $50.
[30.01.2013]
Thanks all, for help! Service Center JTagged my HD2 Radio, and my device finally ALIVE.
I already flashed Paranoid Android 2+, and very glad, because from NAND ROM Android 4.1 works with lightning speed...

Related

Wizard is dead ... need help

Hi
i have G4 wizard 2.16 IPL/SPL and i updated it by IPL_SPL_3.08 update Rom utility. I flashed fine after that i turned it off using power button. my Bad !!!
after that i never start.. no more power i tried to connect to charger and usb connection but LCD still showing no sign. i checked my wizard battery to one of my friend Wizard and its working fine..
so confused dont know what actually happened to it.... please help
You update your IPL/SPL, THAT is what the problem is. You cant update a G4's IPL/SPL to anything other then HardSPL, OR with an official carrier ROM and expect it too work. I may be wrong, but it sounds like your phones bootloader is now bad, and we currently have no way of fixing this....sorry!
my5terious said:
Hi
i have G4 wizard 2.16 IPL/SPL and i updated it by IPL_SPL_3.08 update Rom utility. I flashed fine after that i turned it off using power button. my Bad !!!
after that i never start.. no more power i tried to connect to charger and usb connection but LCD still showing no sign. i checked my wizard battery to one of my friend Wizard and its working fine..
so confused dont know what actually happened to it.... please help
Click to expand...
Click to collapse
Are you sure its G4 ? coz G4 doesn't have IPL/SPL 2.16.It must be 2.16.0001.
Well,if its 2.16.0001 then its a G4 and flashing G3 IPL/SPL 3.08 will certainly Brick it.But if it has IPL/SPL 2.16 only,then its a G3 and there are chances to recover it back.
The only way to fix a G4 in the condition you're describing is to go and flash the Memory chip directly inside the device like they do on the assembly line. This just isn't possible from the standard miniUSB port, as you've overwritten the bootloader, which contains the instructions which move the data from the USB serial buffer onto the flash chip.
As you probably don't have the technology, software, or know-how to correctly identify the memory chip inside your Wizard, rig up a cable, and download the correct binary data, I'd recommend one of two options:
1) The safer option: admit your mistake and try to send the device back to your 'OEM'- whoever branded your Wizard. They should have the technology to repair it- but don't expect it to come cheap.
2) The cheaper option: Find a cheap Wizard with a broken LCD and either transfer your LCD to the new wizard (probably easier), or transfer the motherboard from the new Wizard to your bricked on.
And next time, read through the guides posted here before attempting any flashing operation- they cover the basics, and will prevent you from putting your device into this state again.
zabardast_1 said:
Are you sure its G4 ? coz G4 doesn't have IPL/SPL 2.16.It must be 2.16.0001.
Well,if its 2.16.0001 then its a G4 and flashing G3 IPL/SPL 3.08 will certainly Brick it.But if it has IPL/SPL 2.16 only,then its a G3 and there are chances to recover it back.
Click to expand...
Click to collapse
Well, i did exactly the same- i had a 2.16 and 2.16oip, which i flashed to a 3.08, after which it booted ok, showing a 3.08 and a 2.16oip. On the next re-start everything went dead, no power up. So do you have any hope for me (G3)?
Thanks
If your device is truly a G3, just flashing to IPL/SPL 3.08 shouldn't cause any problems whatsoever.
When you say no power up, what symptoms are you experiencing? Does the device charge? Can it turn on to the tri-color bootloader screen? The more specific you are, the more we can help you.
ktemkin said:
If your device is truly a G3, just flashing to IPL/SPL 3.08 shouldn't cause any problems whatsoever.
When you say no power up, what symptoms are you experiencing? Does the device charge? Can it turn on to the tri-color bootloader screen? The more specific you are, the more we can help you.
Click to expand...
Click to collapse
I cannot get any display at all. I tried the power button several times, (i don't want to ruin the power button too!) as that is pretty flimsy on this device. On charging- i do not see any charging light either, but i do have a fully charged battery (so its not a case of the battery having no charge charge that the charging circuit would not work)
Appreciate your help.
Have you read at all....
Wait wait wait...
Ill expend all my icons in mad.
The man dont knows what about his device is... you cant!!!!!! you cant!!!!! upgrade that way!!!!! only Stock roms for G4!!!!!
So... I Dont have a G4 and i never had one or wish it... so... I never see a IPL SPL G4 with aku3!!! I saw only... IPL 2.16.0001 and SPL2.16.Olip or something made by hardSPL tool.
Please go to this site and please vote for dont get new users without all his info RIGHT!!!! posted in his signature or before everything on login info display and see this info.
http://forum.xda-developers.com/showthread.php?p=2691418#post2691418
We can get Info by default...? i dont know im just trying to get some answers and posibilities.
So sorry for MAD faces I apologized to all... and for my english too jejeje.
dsmadala said:
On charging- i do not see any charging light either, but i do have a fully charged battery (so its not a case of the battery having no charge charge that the charging circuit would not work)
Appreciate your help.
Click to expand...
Click to collapse
I don't know what you mean by the latter, but your problem sounds more like a hardware problem than a software.
Can you confirm that your battery is fully charged with a voltmeter? (It should be slightly above its rated voltage.) Were you trying to charge with the wall charger or the USB cable?
You dont be advised!!!?
Your wizard is......
BRICKED!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IF YOU DONT HAVE SIGNAL AND FULLY BATT IS BRICKED...
Read this...
I can enter in bootloader... and the IPL and SPL are the same G3 or G4
Your wizard is not bricked..
I can NOT enter in bootloader... when plug on wall charger red LED or no led..
Your wizard is bricked.
So Sorry men... a silence minute everybody please.
ktemkin said:
I don't know what you mean by the latter, but your problem sounds more like a hardware problem than a software.
Can you confirm that your battery is fully charged with a voltmeter? (It should be slightly above its rated voltage.) Were you trying to charge with the wall charger or the USB cable?
Click to expand...
Click to collapse
You may be right, it looks more like a hardware issue. Tried both the wall charger and the USB onthe phone to check the LED light. The battery, however is fully charged- have a couple of them and an external battery charger. Thanks for your thots, unlike a few who go ranting about dumbness.
dsmadala said:
You may be right, it looks more like a hardware issue. Tried both the wall charger and the USB onthe phone to check the LED light. The battery, however is fully charged- have a couple of them and an external battery charger. Thanks for your thots, unlike a few who go ranting about dumbness.
Click to expand...
Click to collapse
Its not a hardware problem and if you think what all say here is all ranting about dumbness,then just let me remind you,it was your own dumbness & fault,that you got your device 'BRICKED'.
A Bricked device,doesn't charge,nor gets into Bootloaders and neither Power up.
Now,how it got bricked,let me tell you straight,it was a G4 device and HardSPL was applied and flashed with patched IPL/SPL.You flashed a G3 Bootloaders (IPL/SPL 3.08) to a HardSPL patched IPL/SPL (2.16 and 2.16oip),what were you expecting cud have happened,its known and warned many times to read and follow the instructions carefully,you didn't pay any attention or mis understood all,now its bricked.
This is exactly what all the above members have been telling you,now if you take that as 'dumbness',well I'm astonished.
ktemkin
Perhaps,you didn't read the post carefully or have no idea about what he did or what has happened.Even you have a fully charged battery,still it cannot Boot up a Bricked phone. The DOC CHIP Flash Memory is corrupted due to wrong IPL/SPL flash.either the DOC Chip Flash Memory is to be replaced or the whole Motherboard.That means buying a new device,lol.
It was due to ignorance and wrong Software fault.
Leave it....
dont make sense about it man!
Till we have members without his info correctly we cant do nothing... just try to advise them or tell what was the prob or try to help... misunderstand is a non handle thing we cant avoid....
Already posted to adms and Mods to make, in register info the first time, this kind of info... but it seems that our devices WIZARDS are the most bricked because this IPL and SPL diferences in DOC CHIP version...
Maybe is info that not everybody got and not to be forced to answer anyways... could help. see REQUESTS to Mods and admins in about XDA-developers forum.
thanks.
Thanks for setting me straight. If you can indulge my ignorance one more time, would flashing a 3.08 brick the device immediately? or would it brick it on the first boot after a flash? I ask because i did see it boot with a 3.08, work for a while and then fail on a reboot (which i started manually).
Thanks
Nonono
dsmadala said:
Thanks for setting me straight. If you can indulge my ignorance one more time, would flashing a 3.08 brick the device immediately? or would it brick it on the first boot after a flash? I ask because i did see it boot with a 3.08, work for a while and then fail on a reboot (which i started manually).
Thanks
Click to expand...
Click to collapse
The first problem here is the mixed g3 and g4 ROMS 3.08 is g3.
It dont has issues about that cause is a stock rom i have it and no issues about that... its highly recomended to upgrade just to 2.xx original stock not 3.xx because the aku version ok?
so im apologize for all I said Men... but the experince is the best thing you can get. i have 3.08 just a few months but i did not do the upgrade with this... even tough i ask a lot about upgrade my ipl spl to zabardast and he told me Stupid newbie too but now i know more thing, and yes! I stiil am an stupid but a little less than since he answer all my question... if you dont believe me read all the forum about upgrade jeje
Thanks Zabardast.
zabardast_1 said:
ktemkin
Perhaps,you didn't read the post carefully or have no idea about what he did or what has happened.
Click to expand...
Click to collapse
I wasn't referring to the original poster. I was replying to dsmadala, whose device is a G3- which shouldn't be adversely affected by a G3 IPL/SPL upgrade.
Did someone has a flexible for wizard...................mine was broke

O2 herald problem 3 color screen

Hello
ROM device to install 3 color keranda left. Now I want to install 2% remain open and 3 are colored. Can not HARDSPL.
How can I solve?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ibobaba said:
Hello
ROM device to install 3 color keranda left. Now I want to install 2% remain open and 3 are colored. Can not HARDSPL.
How can I solve?
Click to expand...
Click to collapse
This is the wrong thread to post in if you have problems as this is the ROM Development thread, and it'll probably be moved and/or locked once Ivan sees it. But I'll go ahead and answer your question.
The three colored screen is the bootloader. If you press the reset button, you should be able to boot your copy of Windows Mobile. If you are trying to HardSPL you'll need to first be in Windows mobile, and next follow one of the many HardSPL guides on this thread. If you have trouble finding it, a quick forum search will bring it up. I hope this answers your question, good luck.
I've searched the forum. But the device was not able to HARDSPL in any way. Not install the ROM. RESET solution did not.
At first you have to install an original htc rom, after this you have to install hard spl, and then you can flash a rom. If the device stops flashing at 2%, it is a rom with less than 52 MB, this must be flashed by storage card (Read the description). It happens to me also before a time.
If the rom has more than 52 MB, it will work in the normal process after installing hard spl.
I could not find the original O2 ROM. Can not SPL. 100% gives an error. The storage card when I want to look at "certifica invalid" error.
Restart your pc and your smartphone. Press and hold camera button and the upper button on the right side of the terra, press short in the soft-reset hole with your stylus, but hold the buttons until the three coloured screen appears (the bootloader). Now connect your phone with the pc.
At first flash this ROM. I used it yesterday with an o2 XDA-Terra, and it runs. If your storage card makes problems like before, formate it in the pc in FAT.
After this step you can follow the description here. Don´t forget to soft reset your device after installing the three cabs. Flash the Hard SPL rom also using the bootloader mode. There will be less errors in this mode. Don´t worry, that you don´t see the progressbar. When you flash Hard SPL, the screen is blank (white). After a while it´s finished, your device will reboot and shows on the 1st screen: Now your Hard SPL. Until this time you can flash every herald rom bigger than 52 MB by bootloader mode or in the normal way.
same problem
my phone is hard spled. thing went fine after hard spl, i was able to flash 2 roms, the last one was juststablev2. after one day my phone started to freeze, random crashes, finishing with a "white screen" and then resets. and after a couple of crashes the phone coulnt even load windows anymore, after the splash screen it continiued to reset. and now, the phone dosnt gets on anymore, it only goes to bootloader (not when you turn on the phone, the cant be turned on, only pressing cam button and resetting turns the phone on and you can only be in bootlader. ) i tried everything, readed almost everything in xdadevelopers, tried to flash with shipped roms, tried to flash with custom roms, tried to flash from pc, to flash from sd card (and yes i know everything to do becouse i did my earlier flashed with sd card, all went without any problem). it just looks the phone is dead, but can enter into bootloader. do anyone have any idea ? ill be realy very thankfull if someone can think something about my problem.
ps : my SPL is 4.70.yang
On your pics I can´t see 4.70 yang. When I look there, it seems, as it has lost Hard SPL. Because there is written 4.10.0000. If the 1st screen shows Now Your Hard SPL and the yang-sign, it´s only a boot screen, left by the installation of Hard SPL before. The actual spl you see in the bootloader mode.
If these pics are not actual, I don´t know, what´s to do. But if they are right, you have to flash again an original rom and then Hard SPL again. Put your storage card out of the device or formate it in FAT/ FAT 32, before you begin to flash. Maybe, it´s the reason of your problem.
Neo XL said:
Restart your pc and your smartphone. Press and hold camera button and the upper button on the right side of the terra, press short in the soft-reset hole with your stylus, but hold the buttons until the three coloured screen appears (the bootloader). Now connect your phone with the pc.
At first flash this ROM. I used it yesterday with an o2 XDA-Terra, and it runs. If your storage card makes problems like before, formate it in the pc in FAT.
After this step you can follow the description here. Don´t forget to soft reset your device after installing the three cabs. Flash the Hard SPL rom also using the bootloader mode. There will be less errors in this mode. Don´t worry, that you don´t see the progressbar. When you flash Hard SPL, the screen is blank (white). After a while it´s finished, your device will reboot and shows on the 1st screen: Now your Hard SPL. Until this time you can flash every herald rom bigger than 52 MB by bootloader mode or in the normal way.
Click to expand...
Click to collapse
4:10 SPL as in the picture. Can not HardSpl. 100% gives an error. I'm trying to install gives 1% error HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship. Still could not solve. With the original O2 rom if you can add terra?
Do you have a solution with MTTY?

Please help...my HD2 stuck in " Stick together " screen

please help me...i up a lot of "rom ship" but my HD2 still stuck at " stick together screen" although all process of uploading rom is ok. I've used Task 29 but cant help me...
i dont know why...please help me
thank you all.
here is my bootloader and my sitiuation:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cant really see what you're boot-loader says picture to small, what have you done to get to this?
Demon_man said:
cant really see what you're boot-loader says picture to small, what have you done to get to this?
Click to expand...
Click to collapse
U can see big picture in here :
Code:
http://lh6.ggpht.com/_nKBDPu7hzaw/TCYtMkhVVEI/AAAAAAAAA_w/UUa7iKqnI-4/s128/IMG_0018.JPG
http://lh3.ggpht.com/_nKBDPu7hzaw/TCYtMwhZ9tI/AAAAAAAAA_0/qOC5MIT3pkw/s128/IMG_0019.JPG
i do nothing...
first my brother have this...and used it nomally....( when i check the recieved call time and outgoing call time about 10 hours....) but after my brother did somthing with my hd2 ( he didnt remember what he did..)
when i recieved hd2...it sometime can boot into OS...but sometime automatic reset and stuck at logo "HTC" screen...after that i up rom ship...but nothing better....now it stuck at "stick together" screen.. ( .
hlpdt10 said:
U can see big picture in here :
after that i up rom ship... .
Click to expand...
Click to collapse
what does that mean?? do you mean you tried to update the shipped ROM?? if so then please write this because it makes more sense for people to understand
and the pictures are still small on them links, just to let you no
have you tried a hard reset ?
Demon_man said:
what does that mean?? do you mean you tried to update the shipped ROM?? if so then please write this because it makes more sense for people to understand
and the pictures are still small on them links, just to let you no
have you tried a hard reset ?
Click to expand...
Click to collapse
Yes...i try update a lot of shipped rom( asia WWE shipped rom, tmous........ and try to hard reset alot of time) but nothing better..
Sorry..i 've updated a big screen about my bootloader
I see you have hspl have you tried to flash a custom ROM
Demon_man said:
I see you have hspl have you tried to flash a custom ROM
Click to expand...
Click to collapse
yes i tryied PQ 's rom....but nothing better...
Now...it can boot into the OS again but i'm afraid that it can happen again( sometime OK sometime NG )
i captured my information for u :
Now it auto restart after some minutes and stuck again...(
this is very strange, ill be honest im not the best person to speak to really, you couple ask in the rom section, or advance edit your first post and ask for it to be moved to the rom section, you might get a little more help mate, sorry i cant help though hope you find a solution
sounds like the wrong hspl was used. go to mskips tutorial on flashing a custom rom for the leo. is yours the 1024 leo hd2 or the 512 leo hd2.
sherlockpwnz said:
sounds like the wrong hspl was used. go to mskips tutorial on flashing a custom rom for the leo. is yours the 1024 leo hd2 or the 512 leo hd2.
Click to expand...
Click to collapse
512 LEO HD2 is mine....
hlpdt10 said:
Now it auto restart after some minutes and stuck again...(
Click to expand...
Click to collapse
run task29 to clear your rom space from all the flashing, reflash your chosen rom using usb, and check your battery connections, some possibility of a bent pin maybe.
samsamuel said:
run task29 to clear your rom space from all the flashing, reflash your chosen rom using usb, and check your battery connections, some possibility of a bent pin maybe.
Click to expand...
Click to collapse
i tried Task 29 before , and i replace my battery with good one from my friend ( he 's using his LEO nomal) but nothing better...
samsamuel said check the pins mate, the battery can be fine if the contacts re at all bent on the phone it wont boot double check ??
here my picture about my pin and battery:
hhmm looks all ok to me, I'm sorry this doesn't help you in anyway at all but there seems to be a few people this is happening to of late.
now my LEO cant turn on..poor me...
hey man,
i just had the same problem and i was freaking out for a bit. i was stuck on the screen forever.... but i knew i was in a okay situation because i was still able to go into bootloader mode. anyways, i tried to format my sd card from my tools>>format sd card>> after that i restarted and my phone would hang on the tmobile splash screen.
i then tried to flash miri rom and it was still hang. i reflashed the last known working rom which was energy rom and it booted up perfectly.
im curious how your phone wont turn on? sorry to hear that man.
same problem with my hd2
i bought this phone on ebay and have the same exact problem it is stuck on "stick together" screen some times its boot and work normaly but after 3-5 minutes it reset again back to "stick together screen" this is frustaiting please help
I find this happening to me afew times a day actually, it gets rather annoying but I find taking the battery out for about a min or two and then trying again helps usually. It's a pain when you have to pull the battery 5+ times just to get your phone to start back up.

GPS problem

Hi guys and gals, i recently purchased a htc magic
i have been having trouble getting gps to work.
i did a bit of reading and found out how to do a
factory test. So once it starts i checked my gps and the message i got was
(gps failed -8) has anyone come across this error ? is it fixable
or does it mean its stuffed ?
any help would be much appreciated thanks
apprentice01 said:
Hi guys and gals, i recently purchased a htc magic
i have been having trouble getting gps to work.
i did a bit of reading and found out how to do a
factory test. So once it starts i checked my gps and the message i got was
(gps failed -8) has anyone come across this error ? is it fixable
or does it mean its stuffed ?
any help would be much appreciated thanks
Click to expand...
Click to collapse
Sounds to me that you either have
Hardware malfunction
Problem with your rom.
Is your phone rooted with a custom rom installed?
the phone is rooted im trying to put custom rom on but
i cant get the flash recovery to load up on startup.
currently i have android 2.1 installed
apprentice01 said:
the phone is rooted im trying to put custom rom on but
i cant get the flash recovery to load up on startup.
currently i have android 2.1 installed
Click to expand...
Click to collapse
Could be the rom, could be the hardware, could be the radio.
thanks for your help guys is there anyway to check which one it might be ??
apprentice01 said:
thanks for your help guys is there anyway to check which one it might be ??
Click to expand...
Click to collapse
Process of elimination.
Flash the stock rom and double check your required spl/radio combination.
If it still doesn't work then it's hardware.
If it does then it's either the rom or the radio.
Good luck.
I have run system info says got no radio
here's a print out
# Build #
ID=ERE27
Product=e1000_klx1
Device=e1000_klx1
Board=unknown
CPU ABI=armeabi
CPU ABI 2=N/A (API Level 8)
Manufacturer=unknown
Brand=yusu
Model=e1000_klx1
Type=user
Tags=test-keys
Finger Print=yusu/e1000_klx1/e1000_klx1/unknown:2.1/ERE27/eng.root.20101014.171514:user/test-keys
Time=1287048036000
User=root
Host=talcon-ubuntu
Hardware=N/A (API Level 8)
Radio=N/A (API Level 8)
Bootloader=N/A (API Level 8)
Incremental Version=eng.root.20101014.171514
Release Version=2.1
SDK Version=7
apprentice01 said:
I have run system info says got no radio
here's a print out
# Build #
ID=ERE27
Product=e1000_klx1
Device=e1000_klx1
Board=unknown
CPU ABI=armeabi
CPU ABI 2=N/A (API Level 8)
Manufacturer=unknown
Brand=yusu
Model=e1000_klx1
Type=user
Tags=test-keys
Finger Print=yusu/e1000_klx1/e1000_klx1/unknown:2.1/ERE27/eng.root.20101014.171514:user/test-keys
Time=1287048036000
User=root
Host=talcon-ubuntu
Hardware=N/A (API Level 8)
Radio=N/A (API Level 8)
Bootloader=N/A (API Level 8)
Incremental Version=eng.root.20101014.171514
Release Version=2.1
SDK Version=7
Click to expand...
Click to collapse
That would be the problem. I'm sure of it. Then again... if you had no radio then I fail to see how your phone is even booting. You're probably using a rom that is incompatable with the radio that you have installed. What rom are you using?
Reboot to bootloader (power and volume down) and tell us everything that you see on the screen.
You might want to take the sdcard out first so you don't accidently flash anything.
thanks for the reply, when I restart and press volume down and power button I get message and its says factory mode and there is a few options mainly testing hardware also clear flash and that's it, when I posted the results I can see under heading of bootloader said N/A, I have tried many times to load different ROM but just can't I used ROM manager and followed other ways shown on these forums but for some reason this phone is stubborn and can't modify it
apprentice01 said:
thanks for the reply, when I restart and press volume down and power button I get message and its says factory mode and there is a few options mainly testing hardware also clear flash and that's it, when I posted the results I can see under heading of bootloader said N/A, I have tried many times to load different ROM but just can't I used ROM manager and followed other ways shown on these forums but for some reason this phone is stubborn and can't modify it
Click to expand...
Click to collapse
So there wasn't any text on that screen?
Was it a white screen or colorful?
We need the SPL version, radio version, S-ON or S-OFF etc.
thanks for response, I can't see spl version, when it loads factory mode, its got black background with yellow text and blue highlight under heading of version it has uboot ver 1.1.6. the headings are full test item test, version clear flash which is nand type flash and. reboot nothing else
apprentice01 said:
thanks for response, I can't see spl version, when it loads factory mode, its got black background with yellow text and blue highlight under heading of version it has uboot ver 1.1.6. the headings are full test item test, version clear flash which is nand type flash and. reboot nothing else
Click to expand...
Click to collapse
Yeah... I really have no clue what your talking about.
Your sure you have a MyTouch device... right?
Mind taking a picture if you can?
You should have something that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Give me everything above where it says Fastboot USB in red.
If you don't have this screen while holding down the back + power or volume down + power then I would think that you have a different device.
thanks for your help mine looks slightly different has a little black hole on the left but. I think it might not be the same when I bought it the guy said its htc magic but I think it may not be I don't have the same screen come up as you have shown
apprentice01 said:
thanks for your help mine looks slightly different has a little black hole on the left but. I think it might not be the same when I bought it the guy said its htc magic but I think it may not be I don't have the same screen come up as you have shown
Click to expand...
Click to collapse
Looks like you have one of those chinese fakes.

HD2 bricked?

Hi at all.
I'm a member from Germany so please excuse my bad english.
I think ,y device is bricked. Installed Android on my NAND since it was out (I think it was Feb. 1st) but now nothing works anymore. The device hung up several times since monday, so i decided to update the rom (Typhoon Cyanogenmod 7). After the update it was the same experience: the device hung up every boot at the lockscreen of android. I tried to flash clk again, flashed MAGLDR, i also flashed a WinMo 6.5 Rom but nothing works. The device gets stuck at the first boot screen.
I dont know what to do now. I love my HD2 so i pray to the lord, someone got the conclusion to my problem.
Greetings from Germany
metalgitarrist said:
Hi at all.
I'm a member from Germany so please excuse my bad english.
I think ,y device is bricked. Installed Android on my NAND since it was out (I think it was Feb. 1st) but now nothing works anymore. The device hung up several times since monday, so i decided to update the rom (Typhoon Cyanogenmod 7). After the update it was the same experience: the device hung up every boot at the lockscreen of android. I tried to flash clk again, flashed MAGLDR, i also flashed a WinMo 6.5 Rom but nothing works. The device gets stuck at the first boot screen.
I dont know what to do now. I love my HD2 so i pray to the lord, someone got the conclusion to my problem.
Greetings from Germany
Click to expand...
Click to collapse
I would start from scratch.
1) Flash task29
2) Flash MAGLDR 1.13
3) Flash Android again
it should be fine.
It also sounds like your HD2 may have a hardware issue, maybe cpu overheating.
If you still get this flash stock from SD (go to HTC and find your stock ROM), if it STILL does it send it in for warranty.
orangekid said:
I would start from scratch.
1) Flash task29
2) Flash MAGLDR 1.13
3) Flash Android again
it should be fine.
It also sounds like your HD2 may have a hardware issue, maybe cpu overheating.
If you still get this flash stock from SD (go to HTC and find your stock ROM), if it STILL does it send it in for warranty.
Click to expand...
Click to collapse
Done exactly this several times. I cant send it in, cause i bought it on ebay without warranty *cry* Thought i should update the radio rom, but the updater got stuck at 96% and send "INVALID COMMAND, the update is not for your phone" Now i get Upgrade ROM code error at HSPL screen
metalgitarrist said:
Done exactly this several times. I cant send it in, cause i bought it on ebay without warranty *cry* Thought i should update the radio rom, but the updater got stuck at 96% and send "INVALID COMMAND, the update is not for your phone" Now i get Upgrade ROM code error at HSPL screen
Click to expand...
Click to collapse
that means you need to flash official stock for your area, get it from your IMEI number on the HTC site.
Also, HTC does warranties by IMEI and when the device was originally purchased, so even though you bought it from ebay they will probably still cover it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried to update via the newest htc official rom...failed at 8%
It says the updater doesnt work for this phone...
EDIT: after 6 times of trying to flash the stock rom, it finally ran through to 100%.
The phone reboots and...*tada* stuck at first boot screen
Huh, you're having the exact same problem as my brother-in-law. He bought a cheap HD2 phone hoping I could fix it for him, but the same problem occurred. I tried my best on the damn thing for nearly 12 hours, but it was all for naught -- the closest I could get to installing a ROM on it was 99% before it freezes.
I haven't tried MAGLDR yet, but flashing a radio had the same problem.
As a last resort, I was going to try the technique mentioned in this topic (perhaps you can try it too): http://forum.xda-developers.com/showthread.php?t=668347&highlight=Bricked
P.S. Don't worry about your English. Your English is still better than my German.
I tried the unbrick tutorial, but it fails at the mtty-program, cause it dowsnt show up USB (using windows 7). Using the Task29 program doesnt work either. So back to start with the device stuck at the first boot screen
metalgitarrist said:
I tried the unbrick tutorial, but it fails at the mtty-program, cause it dowsnt show up USB (using windows 7). Using the Task29 program doesnt work either. So back to start with the device stuck at the first boot screen
Click to expand...
Click to collapse
It sounds to me you may have internal hardware failure. I know it sounds crazy but some members with your exact problem havechad success with this method. Put you HD2 into a plastic sealable bag and place it in the freezer for 10 to 15 minutes then immediately flash the ROM from SD card when you take out. If it works I will tell you my thoery on why it works.
Cant flash from SD card, the bootloader doesnt show any flash-options when i boot into hspl
metalgitarrist said:
Cant flash from SD card, the bootloader doesnt show any flash-options when i boot into hspl
Click to expand...
Click to collapse
Well either you don't have the LEOIMG.nbh file on the root of your SD card or you need to reformat your SD card using Fat 32, make sure to malefactors back up copycof you SD card on your computer before you reformat it though. Also if the HD2 still has a ROM on it it might just boot up aftercgivimg it a good cool down in the freezer. The reason I say this is because sometimes if the processor has become somewhat disconnected from the main board form overheating or other reasons. The cold makes the internal parts contract just enough to get it to bootip all the way. Now after of warms back up it may shut itself off and reboot back to the same screen it is stuck at now. Which in this case you will need to get te main board replaced to permanently fix the phone.
reformatted the sdcard from fat32 to fat32: doesnt work
ok, i tried the hint with the 15mins-freeze and it works!
i flashed clk, android and after 10-15mins, it back to start: the device hangs andgets stuck at the bootloader...
Try magldr... To rule out software related issues
Sent from my HD2 using XDA Windows Phone 7 App
metalgitarrist said:
reformatted the sdcard from fat32 to fat32: doesnt work
ok, i tried the hint with the 15mins-freeze and it works!
i flashed clk, android and after 10-15mins, it back to start: the device hangs andgets stuck at the bootloader...
Click to expand...
Click to collapse
Well I am glad to hear the freezer trick worked but sad to hear your problem sbowed back jp again. Like I said in my last post if it come back that means for sure you have a hardware issue. probably need another main board.
Sorry man.
So you are able to flash but it always returns to the SPL? I've seen this twice now and it was physical NAND failure in both cases.
i am able to flash but the hd2 freezes after a while and at the reboot it gets stuck at the bootloader (android logo)...with the freezer trick again, the phone boots normally (no need to reflash) but the device freezes everytime after 15-20 mins
metalgitarrist said:
i am able to flash but the hd2 freezes after a while and at the reboot it gets stuck at the bootloader (android logo)...with the freezer trick again, the phone boots normally (no need to reflash) but the device freezes everytime after 15-20 mins
Click to expand...
Click to collapse
You have either a thermal breakdown of fhe processores connection or bad physical space in the NAND chip.

Categories

Resources