Hello Forum,
I bought an HTC Desire Z from ebay a few months ago. I think it's a great phone, and I'm gutted that I seem to have killed it. It was working fine on purchase, so I can't return it. The problem is: About 6 weeks ago, it decided to do an OTA update (Not sure if it was of apps only, or the OS).
It got locked up half way through, and I had to pull the battery.
Following this, it no longer boots. It gets stuck on the HTC logo. I have tried to follow all the advice on various threads, but they all seem to assume scenarios that aren't possible in my case. (eg. I can't use ADB because USB debugging was never enabled, I can't create a goldcard, because I can't boot the phone up, and my SD card adaptor doesn't seem to work with ReadCID):
As far as I know, it is completely stock, though I can't see any carrier branding. It isn't rooted, and has S-ON. I don't know what version it is, but I think the details below will help this:
I can get to the Fastboot menu.
'Factory Reset' just causes it to lock up.
'Recovery' causes it to shut down, show an icon of arrows encircling a phone, then buzzes about 7 times, then locks up, powered off.
ADB doesn't recognise the phone.
RUU stops every time on 'Rebooting Bootloader' and doesn't move further.
Fastboot does recognise the phone but I can't seem to do anything through it.
The best result I've had was that I was able to extract the most up to date ROM.ZIP from the RUU, which I put on an SD card, as PC10IMG.zip. This did load up, and started updating, but got stuck on 'Updating' the Bootloader, until the battery was completely flat. (4-5 hours). This has happened three times.
The text on the bootloader screen is:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
Parsing ... [SD ZIP]
[1] BOOTLOADER - Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress
Do not power off the device!
Can anybody offer any advice on what I might still be able to do from this position?
Thanks in advance for any help, and apologies if I've missed any important information!
Ian.
ok, fasboot doesn´t help if you do not have eng hboot.
you could type fastboot oem boot and the phone will try ro boot into the rom and will probably also get stucked on htc screen.
did you try to push power & volume up if the icons comes up after enter recovery?
other thing you could try is to find a ruu that is similar to the version you had on your phone before and try the pc10img thing...
EDIT: or first enter bootloader and then start the ruu on your pc
Hi,
Thanks for your reply.
I tried the 'Power and Volume Up' when the icons came up doing recovery. The screen seemed to go slightly duller than normal, but it then just buzzed 7 times, turned off, and won't turn off again at the moment. Does it need to be left for a period of time after starting this procedure?
FYI - I tried two other ROM.ZIP files from two other RUU's before I got this one to even attempt to load, and both came up with 'Main version is newer than rom' (Or similar). The only one that seems to do anything is the very latest one from the Shipped ROMS website.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
All the other ROM's have Radio versions lower than that mentioned on the Bootloader screen, so I guess I won't be able to use any earlier ROM.
I'll try the fastboot oem when it starts responding again from the recovery procedure.
Fingers crossed !
I'm afraid that the 'recovery' method doesn't seem to have made any difference to previous attempts.
The 'fastboot oem boot' comes up with:
fastboot oem boot
.. FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Any other ideas?
Hmm. I think I'm out of ideas.
Does anyone have any other thoughts before I list it on eBay for parts?
Thanks,
Ian
The same thing happened to my phone during an OTA 2.3 update, thankfully for me I still had warranty so sent it off to the shop, when it came back I noticed the void tag has been broken, so I'm guessing the fix may of required replacing the internal memory or something along those lines.
Thanks Greg.
At least it's starting to confirm my fears.
The only other thing I just remembered, was that the SD card failed a couple of weeks before the problem happened, and I replaced it with a new one. Maybe this is tied in with the problem. Do any of the experts have a view on whether the OTA update could have failed because the SD card wasn't the original?
The RUU is able to see what the image version is on the device, so there is some connectivity, but it can't seem to reboot the bootloader.
As a result, I can confirm that the image on there currently is 2.42.405.2.
Similarly, the PC10IMG approach seems to get to the point of updating the bootloader, but then hangs.
Could any of the experts confirm whether this would happen if I didn't have a goldcard in, but need one? I can't seem to create one with any of the methods I've found online so far, and want to know whether this is the best line of attack to move things forward, or whether this will be likely to be a similar waste of time.
As far as I can tell, I can't install an ENG bootloader without being able to boot the phone to turn on ADB, I can't do anything with fastboot without the ENG bootloader, and I can't do anything with ADB whilst the phone won't boot up.
In short, I think I'm stuffed. Any other ideas?
Thanks,
Ian.
Update:
I contacted HTC, and apparently, it's still in warranty, even though I wasn't the original purchaser, so there may be a positive conclusion to this story. Will be back in 7-10 days to let you know what happened
Fingers crossed.
there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not giving you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)
Cant help
Sorry cant really help you much... i wouldnt want that to happen with me...
Thanks anyway for all responders
I just have to wait a few more days for HTC to pick it up and take it to the phone hospital. So long as the previous owner hadn't done anything to invalidate the warranty, I think I may be OK. I definitely haven't.
I'm starting to wonder if it's a bad pin in the USB socket that's preventing it from communicating with the PC properly. I found an error in the RUU log when trying to do a 'fastboot oem rebootRUU':
... FAILED (status read failed (Too many links))
Apparently, this is linked with bad USB cables or drivers, but I know the USB cable and drivers are OK, because I can communicate properly with my Wildfire S using the same set-up.
Anyway - Thanks again for the advice, and fingers crossed
Related
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
What probably went wrong is that you installed a 32B Radio (the ion's) on a 32A device.
Now if you can't get into fastboot, hboot or recovery then there isn't anything you can do, unfortunately
Try to get the device replaced if it's still under warranty.
pelaon said:
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
Click to expand...
Click to collapse
I'm pretty sure your phone is finished but you didn't happen to mention what you were doing in the first place? Were you just updating your ROM or flashing a new Radio?
Hum, i fear it has become a very expensive white brick indeed.
I confirm it was a 32A...and i tryed to flash an ion rom wich is 32B.. gasp !
My bad... sould have waited to have my head clear before doing this :/
i'll try to see if i can get the unit replaced/fixed by official means..but idoubt it
Anyone interrested by replacement parts ?
Oh, and what is the radio bootloader mode for (action+power => blue led)...?
Several qustions as i am deseperately trying to revive my Magic:
- Is there anyway to make the phone pick up a special boot on the sdcard Without accessing recovery/fastboot ? If so what file do i need on the sdcard (sappimg ?)
- What is the radio bootloader mode for ???
Try to connect your phone to your computer using USB. Start it in different ways, and see if fastboot or adb finds your phone. As you said you can start it in radio bootloader, try boot in that too, to see if fastboot or adb finds your phone.
If it does, post your radio and hboot, maybe I can help.
Did try all possible boot method, but the phone never registers on the usb with fastboot or adb. It just keeps showing me the operator splashpage.
The last thing i installed on the phone was the "signed-google-ion-ota-14721" (now i see this was for 32B...didn't pay attention enough that day). This overrode the radio with another one included in the zip.
The installation went quite smoothly but when the phone rebooted, it froze on that logo screen...
well i'm here in the same situation...
there must be something to do...
cmon where is the nerd within you, solve this and get a ****load of respect from me
First of all my software facts so we know what we're talking about:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Oct 11 2010, 12:44:14
im using the latest nandroid. can't find the information for that.
I've looked in a couple places for similar problems but i couldn't find something useful for my problem.
I was at a party last night and had my phone in my jeans pocket. I think its obvious that it was pretty hot and I sweat...
After the party I checked my phone and the style and wallpaper were changed. I also found that the power button didn't work anymore. Before everything had worked just perfectly.
Since I could still use my phone I tried to backup as much as possible. I also made a backup of the current rom.
Unfortunately I restored that rom, and I think that's what causes me problems now. Please don't ask me why I did it, I just wasn't thinking a whole lot.
After reboot the phone stuck in the white screen with green htc logo.
I tried to take out the battery a couple times and rebooted it, but it didn't work. The phone always starts automatically when I put the battery in. Sometimes the colors of the screen were messed up, meaning that it was all pink or some kinda "pixel curtain" was above the image.
I also started the phone in recovery (holding just vol down and inserting the battery) In recovery the phone checks the usual things but I can’t see the results of those checks. I’m pretty sure though, that they all say “No” (no clue if that’s good or not).After that I’m stuck in recovery. The vol buttons don’t work or at least I can’t move my selection and the power button, no surprise, doesn’t work either.
So that is pretty much my problem. I hope you can help me with that.
i ran the latest ruu and it succesfully got my phone back. the power button, however, still doesn't work. anybody an idea how i could fix that? or what could cause the problem?
Update:
when i connect the phone the my pc it shows: hboot usb plug.
i'm not familiar with hboot. could someone tell me what i can do to repair my phone, i guess i have to flash a new rom, using hboot?
moreover, after some time the phone changes into fastboot usb
now i can use the vol+/- buttons again but i cant select anything since the power button doesnt work. but that probably means that i can use fastboot to flash a rom right?
could somebody please explain how i can do that?
i'm also trying to use the test ruu and change the room.zip to the latest one. i founde a thread where that worked: http://forum.xda-developers.com/showthread.php?t=835595&page=3
i hope i can fix it because i doubt htc will replace my phone because of the void warranty...
Seems that this is a hardware issue.
You said you ran a RUU, right?
What does your bootloader show now? The first line is important. It should say something like ACE PVT SHIP S-ON
If this is the case, you should get it replaced by htc because they can't figure out anymore if you had a custom rom or not
Btw: which RUU did you install?
Sent from my Desire HD using Tapatalk
Forgive me for probably relatively simple questions, but my last involvement on here was the development of WM5 for the HTC Blue Angel! So quite some years ago...
I've found a wildfire in the local park a fortnight or so ago. I tried to make an attempt to find its owner, but the device is locked out (asking for email/password) and there is no SD card or SIM card in it (Guessing someone "obtained" it one way or another, couldn't get into it and threw it away). Anyway, long story short - Police aren't interested, Virgin say the phones likely already been disabled and there's nothing they can do with it - so thats left me with it.
Now when I power it up, it goes straight to a screen that has FASTBOOT highlighted in red. This menu key info shows:
S-ON
HBOOT-1.01.0002
RADIO-3.35.20.10
Dec 27 2010, 17:49:10
The power button and volume down buttons don't respond. Tried to do a hard reset, but the buttons don't respond on the other screen either.
Tried to flash with a WWE RUU. It would fail due to Customer ID error but the phone would subsequently boot to the locked screen again. Managed to create a Goldcard (using my Blue Angel none-the-less!) and now RUUs fail due to a bootloader error I think it is.
When running RUU, the version the device is running is: 2.39.775.1
The highest RUU i've found is: RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
It seems a shame to just throw the phone in the bin, but I'm now at a loss what to do.
I've guessed the phones on Virgin, as putting that sim card in when the phone is on the lock screen rather than the white one it shows a different message to any other sim card. I can't find a Virgin RUU though if that would help.
HBoot seems to be the newest one, it is not possible to use Unrevoked to unlock the bootloader, so you either wait till Unrevoked releases a new version with a new exploit, or you find someone with a XTC-clip to S-off your HBoot. (or you buy it yourself)
I thought as much.
Is there no way to be able to get the hard reset to work - just to get the device remotely usable?
First take out SIM and memorycard,
1.Switch off phone by removing battery and put battery back in
2.hold the volume down button and press the power on button briefly, with the volume down button held
3.you will now get a screen approx 10 seconds later and with a few options, go to hard reset/factory reset
4.follow options through, this will reset phone to factory settings.
Post if it works or not
h4oxer: I could get to that menu, but there was no response from the buttons. I couldn't change the menu option highlighted, nor did the power button execute what was already highlighted.
By placing a PC49IMG and a rom on the memory card and then booting to that menu, it enabled those options to be selected. I couldn't flash the rom, but I have now managed to perform a hard reset. Now it boots up ok, but when I go to power off, the next time I power on it's going back to the fastboot (highlighted red) screen. I'm running any RUU update to kick it out of fastboot back into the actual OS.
I've been using Android NAND for a while with no problems but the other day I struggled getting into bootloader. Eventually (for no obvious reason) it went in and I flashed the shipped rom. I tried bootloader again but no dice. Then I made the fatal error of flashing HSPL again only to get stuck on the O2 screen. I can't get any further.
I can't connect to the pc because it doesn't see anything and I can't get it onto bootloader to flash anything else. I've tried everything I can think of bar JTAG (which is out of my league) and I'm supposed to be sending it back to HTC tomorrow for a repair.
Question is, will HTC see HSPL installed without access to the bootloader and, if they do, will they tell me where to shove it?
..tried searching everywhere before starting a new thread...
jetsetwilly said:
I've been using Android NAND for a while with no problems but the other day I struggled getting into bootloader. Eventually (for no obvious reason) it went in and I flashed the shipped rom. I tried bootloader again but no dice. Then I made the fatal error of flashing HSPL again only to get stuck on the O2 screen. I can't get any further.
I can't connect to the pc because it doesn't see anything and I can't get it onto bootloader to flash anything else. I've tried everything I can think of bar JTAG (which is out of my league) and I'm supposed to be sending it back to HTC tomorrow for a repair.
Question is, will HTC see HSPL installed without access to the bootloader and, if they do, will they tell me where to shove it?
..tried searching everywhere before starting a new thread...
Click to expand...
Click to collapse
How did you flash shipped if you couldn't get into bootloader?
You're doing vol-down and power on right? If you get a splash you should be able to get into bootloader, because SOMETHING is telling your splash to show up.
Try putting the correct shipped on your SD and power up with vol down.
I think they will be able to tell that you modified it.
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
jetsetwilly said:
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
Click to expand...
Click to collapse
Well, I've seen lots of warnings about having your battery greater than 50% while flashing, which (obviously) means that if your device has run out of juice while flashing could lead to unrepairable (by end-user) issues .
Try orangekid's advice and report back.
jetsetwilly said:
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
Click to expand...
Click to collapse
when flashing from SD, SPL and radio are the first 2 things it flashes afaik, so power out right when you started flashing could be a serious issue.
Hopefully what I said above works though, if your SPL is completely fubar I have no idea what HTC will say, what I would tell them if you try to RMA is you had problems with random reboots and did a hard-reset, then when it started flashing it just turned off for no reason and now it's weird or something like that so they think it was a regular stock hard reset thing and not a "oh **** I have to restore to factory cuz I have HSPL on here" thing.
Ok, so I tried about 10 more times with no joy - at least it's consistently broken now.
Thanks guys, just hoping for an 11th hour rescue. I'll send it off tomorrow and report back the outcome with HTC. I appreciate your help. I knew the lack of charge and flashing via bootloader was going to trip me up one day.
Was HTC able to bring the phone back to its original state or were you able to do something to get the issue fixed? I have the same problem. All I did was to load prj Clean Desire v0.3.2 ROM (this ROM is the same as Cotulla's but with few fixes). This was the first time I ever attempted loading an Android ROM on to my HD2. All looked well initially. The phone was rebooted after ROM was installed. I did intial setup like facebook acct, email, wi-fi, gprs, etc. Then after few hours, the menu button (windows button in HD2) and back button quit working. Even the power button when pressed for few seconds wouldn't bring up the power off and other options. I thought a soft reset would fix it and then I pulled the battery off and restarted. All I now get is the first boot screen with "123456...go.go.go..." and then a white screen with HTC on it. Nothing more. It is stuck there. I tried getting in to bootloader, but I couldn't. Holding down the volume-down and then pressing the power button just restarts the phone as mentioned above and takes me to the HTC screen. Not sure how can I get to the bootloader. Desperately looking for help....
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