HTC Y cable bricked or not, (how to tell) - Trophy General

Hi,
(Sorry if I posted wrong section or reposted) Now I know I am not the only one to have bricked a trophy during a zune update. My Trophy died on the Mango update, has been bricked for over 6 months. So I recently invested in Y cable as it was able to boot into USB host mode, and a RIFF Box when it did not boot at all.
So to cut a long story short after about 100 resurrections, 10k RUU's. Hopefully this will save some time for some folks as I have wasted countless hours
If your Trophy switches on and buzzes 7 times then hangs at logo, this is what I am fairly certain to be radio failure. Without radio installed OS will not boot and you cannot even enter recovery mode (power button + hold camera). If you flash with correct RUU using Y cable and recieve radio - fail, you more than likely have a defective/damaged eMMC same applies with Flash/Write error 226 on RUU I think, if it keeps throwing the error at the same percent. My radio failed the first time I tried flashing, then worked the second time???, Personally I prefer Y cable over ruu.exe, anywho all ran smoothly only to be killed completely by a Zune update. Countless resurrections with RIFF Box and a fluke radio OK message, strange. Had strange errors within Jtag manager itself when trying to read eMMC, did not see them mentioned on RIFF support .
Finally got a radio update installed (the same one I tried countless times installing before), the second the handset said radio OK I frantically disconnected the Y cable as radio was now installed and didnt feel like taking the risk of it re verifying it after it said OK. Next step was install RSPL then HSPL.. The best bet now is to either cook your own ROM with OsBuilder removing the radio partition, Or insatll a custom ROM containing only the OS. Use a Y cable and make sure it only updates OS If it all completes and states update sucess. Your device should start up
WARNING the above procedure is risky and could potentially completeley brick your device, do not blame me if this happens. Writting to ROM is always a risky proceedure if your phone is under warranty send it for repair, this is a worse case scenario way of getting your device back to life. Also its best to remove HSPL before sending off.
Hope this helps somebody, RIFF Box on standby is essential rather than reccomended

Related

Uh oh, HD2 might be bricked/broken?

Hi all,
Hoping someone can help!
OK, first of all I'll admit quite openly that my knowledge of flashing and so on isn't what you'd call strong so any accusations of being a n00b are warranted and accepted.
I got my HD2 in Jan and I'd flashed a few handsets before without issue so flashed the HD2 pretty much straight away and played with some ROM's and so on and settled on one (from memory Dutty ROM) and everything was fine, the phone was stable and everything was good.
Then 2 weeks the handset started acting oddly. I hadn't changed anything (as far as I'm aware) but the phone starting freezing, restarting and so on. I'd have to take the battery out to restart it (and sometimes leaving the battery out for a while before it'd boot up.) When it froze the area around the bottom of the battery would also warm up. I'd also notice that if I tried doing something on the handset it would restart - almost as if I was putting to much "strain" on the handset and it went *bang*.
I decided to hard reset the phone and it went back to original form. Now, I'll again admit this is probably down to my lack of knowledge, I assumed this put the handset back to a factory state but this is probably not the case (it certainly looked like it but some signs suggested it hadn't).
This seemed to improve things a little but the problems just came back. As I'd flashed it and put on the HSPL I thought the warranty was now invalid so thought I'd try and "fix" it myself.
Big mistake.
Or was it?
I think the phone has an issue with power or something like that as it freezes as I've said. And it did this while I was trying to flash a ROM. Panic then set in.
Basically my handset is now in a state where it'll boot into the bootloader (power and Vol down) three colour splash screen and it'll do the white HTC "normal" boot up screen but nothing else.
I can connect to the handset via RUU and I can run:
Task 29
however this doesn't run and finish gracefully most of the time. It'll stick on 99% or 100% or sometimes it'll moan about not being able to do this on this handset.
Any ROM I now try to flash on it using the exe's or RUU (I've not tried them all, granted!) starts and stick at a certain percentage. The Artemis ROM sticks at 12%, Official 1.43 WWE ROM sticks at 0% and Leon ROM sticks at 9%. Eventually they'll time out with an error. Unfortunately I left the handset at work so cannot state which error(s) I get when trying to flash a ROM.
So, after boring the hell out of you, is the handset terminally ill in your opinion? I really do think that there could be a faulty power button/general power issue with the handset (just a feeling I've got) but from my brief reading I'm not 100% sure.
Is there anything I could do? At the moment it's completely unusable so any suggestions on getting it into a working state? Ideally I'd like to get it into a state where I could return it to O2 UK and not have them flag the fact it's been flashed.
Any help gratefully received!
can you get into bootloader? if so, check the spl.
if it is 1.42.0000 or 1.66.0000 then the warranty is fine.
if the spl ends .hspl then connect to usb and run hspl 2.
choose whatever was your stock spl (one that ends 0000, 1.42.0000 most likely)
reboot to boot loader, and confirm the spl ends 0000 and you will be fine.
have same problem!
my hd2 freezed on startup screan, boot screan, sometime donot start - only black screan, after rom flash 99percent or 100percet once freezed when i return stock rom and spl,sometime dont want to boot with 1.42hspl, next time with 1.66, but my experinece is :
1.
-with 2.08hspl allways start
-uninstal your hd2 driver on your computer! restart your computer install after that, with windows update,
-same with bootloader mode, uninsta, driver on your computer,restart your comp, and install it
-turn off your antivirus protector when install any rom, and your run as administrator in windows 7,vista.
2. use other pc if this dont help
3. the problam can be with battery pins under cover.
some people write there with pins problem, they have screaved pins and hd2 dont want boot or start or have same problems
its my secondary problem
if u want u can use clasical gum ereaser and lightly clean pins and battery conectors...
its help for better contact
donot take the pins with wet hands!!
its can make litle corosi..
i belive its help to you
sorry for my english
lol its come to me on twitter
http://wmpoweruser.com/?p=16952
samsamuel said:
can you get into bootloader? if so, check the spl.
if it is 1.42.0000 or 1.66.0000 then the warranty is fine.
if the spl ends .hspl then connect to usb and run hspl 2.
choose whatever was your stock spl (one that ends 0000, 1.42.0000 most likely)
reboot to boot loader, and confirm the spl ends 0000 and you will be fine.
Click to expand...
Click to collapse
Samsamuel, you're an utter *star*.
Now back to 1.42.0000. I can blag O2 now if needs be in regards to the handset (tried upgrading to 1.72, USB cable came out, phones shagged, give me a new one, etc) without them getting funny about it if needs be.
Will try upgrading to 1.72 stock O2 ROM and see what happens.
Thanks again Samsamuel, I owe you a pint!
I have the exact same problem.
The screen freezes for a while, and then the device reboots.
Usually it's stuck on the white (with green "HTC") screen after that, the red text doesn't show up.
If I remove the battery and leave the device alone for a while (cool down?) it boots past the white screen (although it's highly likely that it crashes again when I enter my pin).
At first this was only happening when I was watching some video's with coreplayer, but now it's just happening all the time, even when it's in my pocket.
I just finished flashing a stock rom, but it's even worse now
9 out of 10 times it doesn't even make it to the pin screen, and I have spend about 2 minutes total actually in windows mobile.
Brood, it sounds like your issue is hardware related, I would contact htc too look into getting it repaired.
Just an update from OP.
Thanks for the link ilijan, very interesting.
I spoke to O2 business tech support yesterday and deliberately asked whether anyone else was complaining of this issue. They said no but I'm unsure whether I believe them and whether this was just the corporate line.
After setting my SPL back to 1.42.0000 I tried flashing to 1.72 stock and this did work. Every other ROM I tried wouldn't work. Even with the official ROM it's still freezing/restarting.
Getting a refurb today.
Thanks to all that responded/helped. Appreciated.

[Q] Help!

Hey guys,
Sorry to be a burden but I'm having a few issues with my hd2, and being a noob I didn't really know where to turn except this forum.
Basically my dad bought the hd2 from the UAE early this year and it all worked fine on stock settings for about 6 months. In the last few months, however, the phone started to lock up, and it got to the point where it wouldn't even boot properly.
In an effort to fix the problem I went with a hard factory restore, however, this seems to have caused more problems as now the phone is stuck in the bootloader.
I've been searching for hours, and have come to the conclusion that I need to update the flash? and then possibly install a new rom on the phone?
My major issue in doing this though, is that I can't seem to connect to activesync while the phone is in the bootloader.
Please help me sort this out.
First of all lets make sure that your trying perform the hard reset correctly.......
You need to hold down both volume buttons whilst the phone is turned off..... Then tap the power button and keep the buttons held down.......
Release them when you see the confirmation screen.........
Powering on while holding only the vol down button will take you to bootloader....
If you need to reflash the device then have a read of this thread here....
If its a "Tmous" HD2 (green and red call/hangup buttons) then you need to read this one
When connecting to the pc in bootloader you should see the word "serial" at the bottom of the screen change to "USB".......
Might be worth checking the text on you bootloader screen for any irregular looking characters, there have a few cases of people with corrupt bootloaders, usually these will display odd looking characters at the top. This is quite rare though.
If you want to flash another stock rom then you wont need to worry about HSPL just download the appropriate ROM and follow the instructions on screen.
Start off at the HTC site and input your serial number to see which ROM is suitable for your device.....
If none of that helps then hold out for some advice here from someone with better knowledge of these things.....
Ok well I've just tried to do the hard reset in the way you've described and had no response from the phone. I had to remove the battery from the back to actually power down the thing as nothing else seemed to work. I can't actually seem to start it up again now =S
Thanks for all the info, I'll keep trying to get it started. I'm downloading the stock rom from the htc site. Hopefully I will find a way to install that.
Also, when the bootloader was up, there weren't any odd characters that I could see. It all seemed pretty standard. It had the current rom driver which was 1.42 or something and a few other lines of info.
Thanks for the post.
edit: perhaps the battery is dead?
No problem.
Is it charging when plugged in and turned off?
If so let it charge while turned off for a while and then try to boot........
If you cant get to bootloader and establish a USB connection then you could try flashing the ROM from the SD card.
rename the rom to "LEOIMG.nbh" place it on the root of a freshly formatted (fat32) sd card and turn on the phone holding vol down..
conantroutman said:
No problem.
Is it charging when plugged in and turned off?
If so let it charge while turned off for a while and then try to boot........
If you cant get to bootloader and establish a USB connection then you could try flashing the ROM from the SD card.
rename the rom to "LEOIMG.nbh" place it on the root of a freshly formatted (fat32) sd card and turn on the phone holding vol down..
Click to expand...
Click to collapse
To be honest I have no idea if it is charging whilst turned off =S All I get is the bootloader when it decided to turn on and that gives no indication of power level so I really have no idea. It makes updating a rom pretty scary haha.
So I just attempted to install the default rom from teh htc site, but failed due to the lack of activesync. It was strange though because the updater managed to change the screen on the phone and get to 1%. It then crashed and I had to go through this recovery process.
I will have to try this SD card process I guess. Could you perhaps link me to a more in depth guide to how to do this?
Thanks a lot for your help I really appreciate it.
you should get a red light up near the earpiece to indicate that its charging........
try this video for flashing from sd card......
I am not getting a red light flashing? But it doesn't seem to be running out of charge. I'm still having lots of trouble
It would seem that I need to install this hspl before I do anything, however, I can't install that if I can only access the bootloader screen. Does this mean my phone is bricked?
I want to be able to set up a rom straight from SD, however, I have no idea where to start. That video just seems to send me in a big loop.
Perhaps you could link me to a simple rom that I can attempt to load via sd card?
edit:
I seem to have somehow fluked an install of HSPL 8G XE.
I have no idea how this happened or whether it is good or bad.. but at least something has happened.
Hmmm
installing hspl is covered here
as long as the word "serial" is changing to "USB" on the bootloader screen when you connect to the computer you should be ok.......
You dont need HSPL to flash via sd card but I think that video was directed more towards people installing cooked ROMS from XDA.
Installing a stock rom will automatically overwrite HSPL so unless your planning to flash a custom ROM then installing HSPL is pointless........
You might be better off installing a cooked rom. (Artemis, Dutty's)
They tend to run better than stock, if you get one running then it will be easier to get back to a stock rom (if you want to) than the situation your in now.....
This is from the flashing guide;
Flashing Via MicroSD Card
NOTE (PLEASE READ): If you flash a Stock Rom via microSD Card then it will overwrite your HardSPL with a stock SPL included in the nbh file. This does not apply to custom roms as they do not include an SPL. BE CAREFUL!!
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the LEO Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to LEOIMG.nbh
4. Copy the LEOIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Reset the device while pressing the volume down button to enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Reckon you could link me to one of those roms? I think we're getting pretty close now.
Your help has been great I can't thank you enough.
Your welcome
You can find Dutty's ROM here
or the Artemis ROM here
Have a quick read and see which one you think you'll prefer, to be honest I think they're both pretty similar to stock but with a lot of the crap taken out....
Just follow the steps in the first link I posted and you should be good to go.
Ok new problems.. Can you believe it.
I seem to have tried everything.
Basically I can install of a sd card, but when it gets to the end of the install and I restart instead of booting into a OS it boots to the tri colour screen, and starts the install process again.
Also, I have attempted to install via usb and have had varying success.
As I have already said, I am able to install hspl, however, when I try to flash I get to varying percentages below 30% before the whole thing freezes.
I now have an error that says Upgrade Rom code error Please Try Again.
Sorry i dont mean to hijack ! but will any of you be kind enough to help me here..
http://forum.xda-developers.com/showthread.php?t=879980
thanks !
Ok so I followed the steps and still to no avail.
I am able to boot using the sd card method, however, the same problem occurs with each rom version. Basically as soon as I reset the device it pretty much switches itself off, then I can't turn it back on, once I finally do turn it on, it restarts the process like it never happened.
The other issue is again the active sync problem.
With most of the the usb connections I am able to connect and get a little way through the install (most I've got is 15%) then it just freezes up and I get the 262 error
Your best bet is to try flashing with a freshly formatted (FAT32) 4gb, class 2 card.
I know, sounds pretty specific right?
You wouldn't think it would matter?
I have tried flashing with 16 gb class 2, failed at the radio step
Tried with a 8 gb class 6, failed at the radio
4 gb, class 2, flashed successfully.
Seems our HD2's are picky about what cards they'll take a ROM from for some reason.
Alright I'll try that, my next issue is which is the stock rom for the phone =S
It was bought in the UAE and I'm currently in Australia.
edit: Also I read somewhere that the constant bootloader screen can be caused by a bent battery pin?
Edit2: I have attempted to do that, however, now the bootloader will accept the card, then just sit on loading...
I'm pretty sure this thing is bricked.
tombm said:
Alright I'll try that, my next issue is which is the stock rom for the phone =S
It was bought in the UAE and I'm currently in Australia.
edit: Also I read somewhere that the constant bootloader screen can be caused by a bent battery pin?
Click to expand...
Click to collapse
I've heard of bent battery pins being a pretty common problem, causing usually just the phone not to charge properly. I've personally never heard of it causing constant bootloader, but it's definitely worth checking.
It's weird that it's such a common problem, my usb/charging port is broken, so I have to use an external charger. I change my battery on average twice every 24 hrs, and I've never bent a pin
Ok, new info, apparently because the device is for the middle east it does not support stock 3.14 roms. What does this mean for me? Am I bricked.
http://forum.xda-developers.com/showpost.php?p=9614007&postcount=30954
Click to expand...
Click to collapse
That's the post I found the info in. All of that info matches up to mine except my original image was 3.142 I think =S
Firstly, your phone is not bricked - a bricked phone is responsive as a brick.
Can we start from the begining?
What does the Bootloader Moder screen say (with and without the USB cable connected)?
What ROM (and if custom ROM, what RADIO) have you flashed and are trying to flash?
fred_up said:
Firstly, your phone is not bricked - a bricked phone is responsive as a brick.
Can we start from the begining?
What does the Bootloader Moder screen say (with and without the USB cable connected)?
What ROM (and if custom ROM, what RADIO) have you flashed and are trying to flash?
Click to expand...
Click to collapse
Alright from the beginning.
Basically about a month into using the phone in Australia it became very unresponsive to the point where it would not boot at all. We left the phone for a couple of months, however, after seeing a friend rom android I decided maybe it was time to attempt to fix this phone.
Some more info:
When I attempt to do any sort of ROM update there is nothing in the 'current image' part so for example it will say update to Dutty 3.6 but it's updating from nothing, does this mean there's no firmware there?
In the bootloader I have:
PB81100 HX-BC
SPL-2.08.0000 8G XE
MICROP(LED) 0X05
MICROP(TOUCH) 0X40
Without USB cable in I get Serial in the white part down the bottom, with the USB cable in + plugged into computer I get USB.
Just to further clarify. In regards to the ROM I have installed. I simply don't have anything installed. There is a bootloader, no image, no bootup. It boots up to the tri colour, that's it.
For a moment we will forget about going to 3.14 ROM: I don't know if that phone is entitled to an official upgrade to 3.14, if it is locked to a particular network, if it is branded, etc. If it is not entitled to a 3.14 ROM upgrade then you will have to go through GoldCarding, so we will leave it for now.
Make sure that the battery has had a good couple of hours charge in the charger or double that if connected to the computer.
Remove SIM Card and SD Card.
Switch on to Bootloader Mode, then connect to USB.
Download and run HSPL2 - ignore the instruction about connecting to ActiveSync etc, just proceed.
Download and install the HTC 1.66 WWE ROM - again, ignore the instructions, just proceed.
The reason for HSPL is because your phone may be operator locked (not SIM locked) and you aren't entitled to run the 1.66 WWE ROM.

Flash RADIO fail at 96% -HELP!

ANybody can help me . i have a HD2 When tried to FLASH to any RADIO from 2.07 to 2.15 all failed at 96%. I have made a TASK29 also it fails at 96%. NOW cant install anything on it !
At first 2.15 flashed and after i made task29 it stop to install. Then i used 2.07 it flash, but again i used TASK29 and now when i retry to reinstall any RADIO, it fails at 96%.
Am using tasks29 because my HD2 is stuck in LOGO HTC. So am trying many ROM file for it to WORK but in VAIN !! I still can enter BOOTLOADER. Manage to install MAGLDR and WIN7 but never the phone was OK!
I was wondering if its a HARDWARE problem?
It usually takes a long time at 96%. Try leaving it for a while and see if it will complete. Mine took some time at 95%
Crust2 said:
It usually takes a long time at 96%. Try leaving it for a while and see if it will complete. Mine took some time at 95%
Click to expand...
Click to collapse
Yep, mine hangs at 96% too. Maybe try this Task29 with Radio (check it's the right radio though)...
http://forum.xda-developers.com/showthread.php?t=1018427
If you can get into BL dont worry you'll be able to flash. Just try everything again and give loader a moment.
Ok. I waited almost 30Mins ! is that ENOUGH?
But i Found that If i flash with this ROM (that has RADIO in it) - " Duttys_Leo_Sense_2.5_5.2.21907.5.0.93_1.80_ML_V4_Ship_EN " flash succESSfully but still i have the PROblEM of STUCK on HTC logo !
Again failed at 96%
Hello,
has anyone managed to resolve this problem?
I am having the same issue - radio and rom flash fails at 96%, I have tried even older radios and different roms with radio. Tried with HSPL 3.03 and 2.08.
When flashing from USB it always stops at 96% at hangs for 15mins then says fail.
If flashing from SD card then it just hangs indefinetely.
only the Duttys_Leo_Sense finishes flashes but the phone wont boot
Download this, flash it and and start from scratch. something went wrong along the way..but start from scratch and go again.
If you have trouble once you download. restart the phone holding the the power and volume down buttons. and you will get into bootloader..then connect phone and wait until it says usb and flash.
http://dl.htc.com/ruudownload/t-mobileUS/DeviceDownloads.aspx?pid=leo2
toreone said:
Download this, flash it and and start from scratch. something went wrong along the way..but start from scratch and go again.
If you have trouble once you download. restart the phone holding the the power and volume down buttons. and you will get into bootloader..then connect phone and wait until it says usb and flash.
http://dl.htc.com/ruudownload/t-mobileUS/DeviceDownloads.aspx?pid=leo2
Click to expand...
Click to collapse
Thanks - and a quick question - is this download for US or EU version?
I have a EU version.
nitko666 said:
Thanks - and a quick question - is this download for US or EU version?
I have a EU version.
Click to expand...
Click to collapse
I have not looked to see if it is for the US or EU HD2. But seeing as you have a EU HD2 you have nothing to fear really as the EU can be flashed with any radio version with no bad effects. But the US HD2 can not be flashed with any radio version with a 51 in it or it will be hard bricked. The 51 radio versions were the first radio versions for the EU HD2.
also, try chillign teh phone for twenty mins in teh freezer, then quickly reinsert the sd and try to flash. It may help you get past the last few %
Unfortunately it didnt end well
HTC HD ROM update from USB stalled at 8% for more than 30mins.
Then I tried updating it from SD card when it failed instantly reverting to factory SPL.
And then I tried to use HSPL4 to put: SPL-208 instead of HSPL208. Phone said cracked it and after that it died.
Its completely bricked now, cannot turn it on - no key lights, no lcd
odd, these devices are very difficult to brick since if you mess up, just go into bootloader mode and reflash.
slybunda said:
odd, these devices are very difficult to brick since if you mess up, just go into bootloader mode and reflash.
Click to expand...
Click to collapse
ahhh if only it was that simple. Check out the title of this thread, what you're suggesting is exactly what is failing. Look around, teh forum is stuffed full of this type of error. Sometimes it is solvable, sometimes not.
Hello, sorry for saying this but there is no solution to fix that. I had the same problem on friends HD2. It died with no reason, just rebooted. All you wrote is the same there, if you use newer radio stuck on 96%, older stuck in 97%. HSPL working ok, leoimg.nbh stuck on 8% and you getting ROM Update fail all times. That is hardware issuse and Radio ROM chip is damaged. We did not found any solution to fix that and even tryed xtc clip and all methods of instalation...
can u try flash HSPL first then the radio and then MGLDR...my problem is solve..
Hi.
I bought Hd2 yesterday, and I have a biiiig problem with it. It started perfectly - but after 5 min it shut down. It shows message about low battery, so I connected it into charger, orange led turned on. I tried to switch telephone on, but it freezes on white screen with HTC written. I tried soft-resets and hard-resets, even tried to install official rom - but installer is always freezing at 8%. I can get into BootLoader and phone is recognized by the PC after connecting USB cable. But this is all - i can't switch phone on, I can't install ROM...
What is wrong? Is it gonna work, or maybe it is totally bricked?
Radio flash stuck @ 96%
This seems to be the kiss of death for an HD2. I also have the same symptoms: stuck at 96% when trying to flash a radio. I have a US HD2 and I've flashed about 10 of these phones with no issues. This is the first one I've ever seen with this issue though. It was a friends phone that he wanted me to assemble. He gave it to me in pieces. When I assembled it, it wouldn't boot. So I flashed the stock ROM, but the flash won't complete. Fails at 8% or 11%. Tried flashing HSPL and it seems to work. But when trying to flash the radio it fails at 96% (it just hangs).
I was wondering if it has bad sectors on the partition or someting and if a J-tag service could fix this. Theoretically, it's supposed to be fixable if you can get into the bootloader. Oh well, into the junk box this HD2 motherboard goes until someone posts a fix.
I got the same problem can't not flash anything, and alway stucked at 96%.
Only thing I did to get it complete flashing radio, rom was put the phone in zip lock, and put in freezer for 10mins, took it out and plug in battery and flashing, at anytime, if the phone vibrating it will not accepting any data in, and it will stop at 96% and then i have to put in freezer again. Took me awhile to get everything boot up and got in windows 7 and play with it. But... the phone still rebooting it self, sometimes it will reboot after 5 mins or an hr when I am surfing webs or setting up the phone... Right now I am trying to get a different sim card to test out.
Seem more like hardware problem.
My problem is solved - I've got new motherboard....
NAND Toolkit
Have you guys tried to use NAND Toolkit?! it works fine for me, and never had issues flashing my HD2...

Serious problems with (semi?) bricked HD2

Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)
I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"
Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?
test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?
Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.
Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse
Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium

[Q] Recover Fail - No boot White screen

Hello, and sorry for the post asking for assistance!
been driving me nuts for 2 days now, it seems i'm having a major case of melting HD2
it started with the phone freezing often, reboot solved it.
then, it went to having to unplug battery for a few, and, reboot fixed it.
now i'm at a constant white screen (no htc logo)
was running in Android but tryign to just get anything working for now.
i made the sd card leoimg.nbh with a custom rom to recover it, but i can't get it to finish
in red : Radio_V2 Fail
in blue : all the rest
tried to flash radio update, failed
tried to update the HSPL version (2.8one now) but no go, it shows "success" but in bootloader shows the same old version.
what can be the cause of this, exept memory nand being screwed?
greug said:
what can be the cause of this, exept memory nand being screwed?
Click to expand...
Click to collapse
CPU and its BGA balls!
Not alot to be done i think...
Keeps coming up on white screen.
Tries to flash HSPL (newer version) finishes but it still shows the same version when powering +volume MIN.
Tried to flash a Radio, comes up with an error Radio V2 error
Tried to push a ROM on there, gives a "image file is corrupted"
Tried what i found here on the different forum threads but....seems my HD2 gave up on me...or at least it's beyond my repair skills.
Thanks for those before me who gave suggestions on what to try, it's a damn sad day i loved that phone..
wts : one slightly bricked phone
Try to do a Task29. Use the HD2 Toolkit for that.
You have to JTAG it in order to recover it. RADIO_V2 means it's radio, and it's officially bricked. There's nothing you can do other than JTAG to recover it
Well, in a way i'm glad i have the answer now about the V2 being the radio ...
Thanks for the input guys, not sure i'm going to bother with the JTAG story, already ordered a replacement for my HD2 as it is, can't spend too much time without my phone.
Anyone knows if people are interested for the "bricked" HD2's? or how to reach people?

Categories

Resources