Related
Had my HD2 since November, screen quit responding to touch. Hard reset multiple times, finally gave up and sent it in for service. Got an e-mail from the service center with the following:
Diagnosis:
Mianboard hacked/illegal software.
If you cover the price for mainboard replacement they will take care of the touch panel issue in warranty for you.
Suggested Repair:
Replace Mainboard.
Total Repair Price:
$317.43
I argued with the service center manager for about 15 minutes, explaining to him that I had never flashed a hacked ROM. He's supposed to be provide me with proof that the mainboard was hacked tomorrow.
It wasn't until I got off the phone that I realized that I had loaded HSPL and when I looked at the NOOB guidelines again, found out that it didn't get overwritten when I flashed from 1.43 to 1.66. That must be what they are talking about.
Not sure how this is going to play out, I never loaded any cooked ROM's. Is there a way for the service center to see that's the case? Will they simply say that the HSPL software constitutes the mainboard being hacked, end of story?
What do you think?
Sorry for the cross post, thought this may be a better forum for this issue.
Will they simply say that the HSPL software constitutes the mainboard being hacked, end of story?
Click to expand...
Click to collapse
Yup most likely.
Refuse repair, and tell them to send you the phone back unrepaired.
Overwrite HSPL with stock SPL as explained in the HSPL thread
Send the phone in again.
Solved
If they want to play fools (they of course know HSPL can't be the source of the problem), you can too.
yep its the hspl that is the bad part. they wouldn't have said anything about a cooked rom most likely, its the hspl that is the dodgy part.
Thanks Kilrah, I thought of that but it I also thought it would be too obvious to the service center. Might be worth a try if they balk at the repair though.
Yep of course there's a risk they take a note of it, linking it with the phone's S/N, and that they see it the 2nd time. But you'll most likely fall on someone else, plus if they do moan again you can always ask them to show evidence, which they won't be able to do this time... and even if they still insist you'll have just lost shipping. If they don't, you save the amount of the repair
kilrah said:
Yep of course there's a risk they take a note of it, linking it with the phone's S/N, and that they see it the 2nd time. But you'll most likely fall on someone else, plus if they do moan again you can always ask them to show evidence, which they won't be able to do this time... and even if they still insist you'll have just lost shipping. If they don't, you save the amount of the repair
Click to expand...
Click to collapse
Just got to thinking, when I flash using the sd card technique to remove the HSPL, will it go through the entire process without any prompting or need for screen input? If they send the phone back without fixing the screen, I won't be able to initiate any prompts on the screen.
mhmobile said:
Just got to thinking, when I flash using the sd card technique to remove the HSPL, will it go through the entire process without any prompting or need for screen input? If they send the phone back without fixing the screen, I won't be able to initiate any prompts on the screen.
Click to expand...
Click to collapse
if i recall correctly it goes through without any prompts so you should be ok.
Audio Oblivion said:
if i recall correctly it goes through without any prompts so you should be ok.
Click to expand...
Click to collapse
Great, Thanks!
Hi
Ok so my phone was working fine on a custom ROM when suddenly yesterday an exclamation appeared next to the phone signal and stopped from receiving/making calls and texts. I thought it had just crashed but after soft and hard resets and changing to a few others sims I just can't get my phone signal back.
Really strange as everything was working fine. I now have trouble flashing custom ROMs and am struggling to run a stock ROM because I'm on a mac.
It's driving me crazy as my phone is now useless.
Any ideas guys?
thanks
Quick update
I've managed to get the Leo Lite ROM running and everything is good except that damn exclamation mark next to the phone to phone, which means I can't get the phone working.
Anyone know know why this is???
Have you tried the sim in a different phone?
could just be a simple issue
And I know it a simple thing............but have you got flight mode on?
johnerz said:
Have you tried the sim in a different phone?
could just be a simple issue
And I know it a simple thing............but have you got flight mode on?
Click to expand...
Click to collapse
Thanks for the reply John.
Yeah currently having to use the sim in an ancient motorola and it works fine, tested with calls and texts. Also tried turning on and off flight mode but still that bloody exclamation mark stays.
That sounds like its been blocked. Theres a network there it just isn't letting it connect. Did you buy it second hand? or off ebay?
samsamuel said:
That sounds like its been blocked. Theres a network there it just isn't letting it connect. Did you buy it second hand? or off ebay?
Click to expand...
Click to collapse
Hey Sam
Do you know what, I did buy it second hand, from a reputable store in town.
However this raises more questions than answers;
1. Why would it be blocked after several weeks of normal use.
2. Doesn't some sort of message need to be displayed stating the handset has been blocked.
Does anyone know if this is what happens when a HTC HD2 is blocked? i.e. the exclamation being shown all the time.
I presume a handset is blocked for security measures like theft. I will take it back to the shop tomorrow, they will have all the details of the person who sold it to them.
However is there no way this can happen from flashing custom ROMs? Even though that doesn't really make sense cause I had a ROM that was working fine and this happened when I was out and about.
It could be a bad rom, but it certainly wouldn't be in every rom.
I think id try going back to the stock rom, radio and spl (i.e an sd card flash, do you now if it has a provider locked rom?) and see if it is still there. If it still won't work, then it's definately either hardware or network.
The reason it could have taken weeks is, , seller trades in phone for cash, waits a little while, thinks 'i know'..., reports the phone lost/stolen to claim on insurance, insurance won't pay out without the imei being blocked.
samsamuel said:
It could be a bad rom, but it certainly wouldn't be in every rom.
I think id try going back to the stock rom, radio and spl (i.e an sd card flash, do you now if it has a provider locked rom?) and see if it is still there. If it still won't work, then it's definately either hardware or network.
The reason it could have taken weeks is, , seller trades in phone for cash, waits a little while, thinks 'i know'..., reports the phone lost/stolen to claim on insurance, insurance won't pay out without the imei being blocked.
Click to expand...
Click to collapse
Well I've tried flashing at least 6 custom ROMs, all show the exclamation mark.
The phone was sold to me as being unlocked to all networks, however I never tried with anything other than a o2 sim.
Now going back to the original ROM has its own problems. First off i'm quite new at this so sorry for sounding silly. How on earth do i go about finding out what the original stock rom, radio and spl is?
When I have these I can't easily go back as I don't have a pc, using a mac. I would have to use the sd card way but I can't find an official signed .nbh file.
I have a brand new T-Mo US HD2 with similar issue (out of the box). It's like the radio will not initialize. Did hard resets, tried to force it finding a carrier, etc, and it just will not turn on the radio.
I did find out that there is a likely issue with my SIM slot. If I attempt to remove my SIM card (which works fine in other phones) it is almost unremoveable and feels jammed in. However, once removed, I get connectivity via wifi and touch response is great.
If I insert a SIM card, it takes a LOT of pressure to reinsert it (yes, inserting it in the correct orientation), and the phone cannot connect turn on the phone's radio. Also, I get random phone.exe and credential.exe error message (plus the phone becomes very slow.
Don't know if you have any of these other symptoms, but the lack of connectivity sounds similar.
Supposed to get a replacement HD2 today, and we'll see.
I had the same problem too. I got unlocked code from tmoile and everything working fine for a month. It was working great after upgrade the latest rom 3.14 from tmobile download site (i got the message from them to upgrade), until i went out off country last month then the phone could not turn the phone's radio on. It kept at airplane mode. I been try to flash back and forth all the tmobile .50 stock rom and still having the problem.
Does any one know the issue to fix it? TIA
Looks like a hardware fault. You need to open case and check bottom two brass hinges are in working order and correctly hinged to make contact with antenna which is on the rear case at the bottom.
Follow the guide of opening s HD2 on YouTube there is a factory guide to dismantling the HD2.
xlr8me said:
Looks like a hardware fault. You need to open case and check bottom two brass hinges are in working order and correctly hinged to make contact with antenna which is on the rear case at the bottom.
Follow the guide of opening s HD2 on YouTube there is a factory guide to dismantling the HD2.
Click to expand...
Click to collapse
Thanks for reply xlr8me. I just check the two brass hinges at the right side of usb connector. It looks fine to me. The other thing i didn't mention on the above post I was flash the dft_leo_nand android after tried all the stock rom from tmobile and the android said "no sim card", i also checked and cleaned the sim slot. Do you think any thing else to cause that problem?
One more thing without the sim or sd card the about phone show up all info of phone: imei, serial..... But with sim card in it just blank when i read the about phone hardware info. Thanks again
Did you try simcard from another carrier?
cecobald said:
Did you try simcard from another carrier?
Click to expand...
Click to collapse
Yes I did tried the sim from the carrier of the asia country i was traveling to last month, that why i call tmobile to get the unlock code before i go. When i was there and inserted their carrier's sim and it won't work, even when i get back to U.S. I been tried either tmobile or at&t sim too. The phone radio won't turn on. The rest is working ok except those above error messages "A problem has occurred with device.exe" and "Credential.exe".
Do you think i can reflash with WWE rom .50 radio instead of tmobile's official rom?
Thanks
htcphonelover,
You will have to reset the phone back to default rom from htc website. You may also need to reformat sd card but the radio should still work regardless of whether the sd card is in or out.
My only concluding thoughts are that if the above fails to work then try a different sim card and still no good then probably something with the motherboard on HD2.
Good luck and update us with any new info..
My Desire HD with both, froyo and gingerbread has the same problem, all with oficial roms: When I turn the screen off the phone just turns on back again. I sent to the SAT about 4 times now and the only thing they do is "Software update", is it a hardware problem? Can I change it for a new one? How can I do so? Im so desperate about all this problems because I am not able to use it because battery runs out in half a day. Please! SOS! Thank you every1.
BraskOviedo said:
My Desire HD with both, froyo and gingerbread has the same problem, all with oficial roms: When I turn the screen off the phone just turns on back again. I sent to the SAT about 4 times now and the only thing they do is "Software update", is it a hardware problem? Can I change it for a new one? How can I do so? Im so desperate about all this problems because I am not able to use it because battery runs out in half a day. Please! SOS! Thank you every1.
Click to expand...
Click to collapse
This happens, without failure, every single time you turn off the screen? If that's the case, i can't see how the technicians at the service center haven't been able to reproduce the problem after a full wipe/update..
I'd say this has to be a hardware fault unless the service people haven't done anything at all. If this keeps happening regardless of factory resets/software updates, I can't see how this is a soft problem.
I'd ask you to try a few different roms and such, but I assume you are unrooted and uninterested in all that? If so, there's not really much you'll be able to fix for yourself. I would try to send this in as a hardware issue and try to get it repaired/replaced, makeing sure to explain that this "software update" **** they're doing isn't working.
Tried everything
I write here cos ive tried everything. Tried all roms and now back on vodafone oficial rom. Problems on all. I sent it with faulty hardware on the repair sheet and wrote:
GPS module.
Light sensor module.
Screen ok?
Radio OK?
And many more things, they just "Software updated"
BraskOviedo said:
I write here cos ive tried everything. Tried all roms and now back on vodafone oficial rom. Problems on all. I sent it with faulty hardware on the repair sheet and wrote:
GPS module.
Light sensor module.
Screen ok?
Radio OK?
And many more things, they just "Software updated"
Click to expand...
Click to collapse
That sucks. I've worked at shops that sell mobiles, and I've seen this many times: The technicians get an error report and end up just doing a "software update" (eg nothing) and ship it back.
I think the problem for the main part is that they recieve so many inane error reports (poor battery or something stupid like that) from customers who have no business handling any piece of electronics that they just have to go the easy way and not really do anything.
In this case I'd say it's a gross oversight on their part if this problem happens every time you turn off the screen. If there's any way for you to underline the fact that you are fairly competent with these things and feel that it is a hardware fault, and that their goddamn "software updates" don't work, you should do that.
sry I don`t have a solution about your problem but the thread title describes also my problem.
how can I turn the screen ON from the other buttons also? (not only from power)
Hi again guys. I dont know if i ralle can use the term bricked or not, but i guess so. After a funny day with a couple reboot and new "radio" image my Legend want start anymore. The screen is just black, even if i hold down vol down/up and power. So the big question.... Is this phone bricked? If so, can i fix it?
EDIT: The LED does not even respond when charger is plugged in.
Sorry for the lack of English.
if it is bricked - try this.
I dont even get to fastboot The phone is completely dead/black
Are you S-OFF? I've never known a S-ON Legend be completely bricked like that!
No i'm still S-ON because of the d*** HBOOT 1.01
Only thing i've done so far is root+CM7. And yesterday when i played around with ROM Manager i had to remove the battery upon a crash.
Apparently same problem as here : http://forum.xda-developers.com/showthread.php?t=1096083
This is really weird...
I dont even get to fastboot The phone is completely dead/black
Click to expand...
Click to collapse
I think you are in trouble...
RomManager is maybe the source of your problems, what did you do with ?
Did you have errors during the radio installation process ? and which radio were you flashing ?
Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.
SGT John Doe said:
Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.
Click to expand...
Click to collapse
me too it sucks
Is it still under warranty? (Obviously not as you're rooted, but would it be if you weren't rooted?) If so, try sending it to HTC they might just replace it if they can't see for themselves that you're rooted!
If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back
bonesy said:
If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back
Click to expand...
Click to collapse
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?
madcat340 said:
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?
Click to expand...
Click to collapse
They will send it back unfixed and say the warranty is void. Even if they know its rooted they might still fix it for you, it depends.
It's my fault that the phone is broken and i'm willing to take that blame A clean conscience makes me sleep better at night
I dont know how it is in the rest of the world, but in my country there is a high fee if they notice that the owner has done something with the firmware etc. Thanks anyway for all the respons and help, and remember guys, stay away from Rom manager
You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone
bonesy said:
You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone
Click to expand...
Click to collapse
well i'm going to say something like that. Generally because my phone was buggered before then (signal problems and locking into airplane mode) though i'm rooted i still wouldn;t think i'd get away with it
does it matter if the root is S-ON i'm just thinking off my chances
PM sent, I can fix hard bricked Legends with JTAG.
My girlfriend got angry with me and had my phone in her hands. Result: Flying S4 crashes with wall and turns off.
When i turned it on, i noticed it won't connect to the network, and that it has some kind of "micro-freezes" (every 5 seconds, it will freeze for 0.3 seconds).
I brought it to my telephone company service center (as the phone hasn't any fall sign, nor is it damaged). When they first take it, in front of me, they type *#06*, and notice the IMEI says "null". Then they tell me that this is a sign that i tried to root or modify the phone, so the warranty won't cover any fix. They still keep the phone to analyze it.
Some hours after that, i receive an email saying that the phone is ready to pickup. When i go, they repeat that as the IMEI is null they cannot do anything. They also factory-reseted the phone as they always do when analyzing them. (i'm sure they didn't open the phone to check if something was broken, as they take more time when doing this)
So i have two questions:
Has the "micro-freezes" problem have anything to do with the IMEI being null? or is it a problem with broken motherboard? (also the phone will heat a lot when charging, more than normal)
Is there any way to recover the IMEI?
Thanks a lot for your help.
I personally don't think the micro-freeze is related to the IMEI. You should monitor the CPU activity. There can be a component failure, which makes the phone freezing due to drivers and component failure. Just saying....
demlasjr said:
I personally don't think the micro-freeze is related to the IMEI. You should monitor the CPU activity. There can be a component failure, which makes the phone freezing due to drivers and component failure. Just saying....
Click to expand...
Click to collapse
I also doubt it could be related to that. What application should i use to monitor the CPU activity?
Thanks for replying.
soylomass said:
I also doubt it could be related to that. What application should i use to monitor the CPU activity?
Thanks for replying.
Click to expand...
Click to collapse
Try with System Monitor Lite: https://play.google.com/store/apps/details?id=com.cgollner.systemmonitor.lite&hl=en
You can also install Android System Info: https://play.google.com/store/apps/details?id=com.electricsheep.asi&hl=en
With ASI you can check the log, or you can also connect the phone to the pc and monitor through ADB. But with that app you need nothing. Check the logs, there are lines related with the freeze.
Back in March when my S3 was freezing due to sudden death, I had lines in the log related with the freeze, I shown it to the Samsung tech and they replaced my phone's motherboard. Check the line and post here the log, we may help you detect the issue.