Related
Hi,
While on holiday I put my Desire HD on charge over night (was working fine at that point), but when trying to turn it on the next morning it just vibrated 7 times and that was it - the phone would do nothing. The phone doesn't respond to the hard reset process described on the HTC website and no lights come on at any point (not even when connected to the charger).
The only time the phone does anything, is when you eject the battery and re-insert it. At the point where the battery touches the contacts inside the phone, it vibrates 7 times again and nothing more. The phone has not been modified in any way and uses the original OS from HTC. All the phone does is vibrate 7 times when inserting the battery. Otherwise it's completely dead.
This would, I presume, normally be a simple warranty case (8 month old phone). However, in my desperation to reset/fix the phone, I tried pressing what I thought was a reset button underneath the SIM & memory card cover (with the tip of a pen). Instead of the 'click' that I expected though, it pierced what turned out to be a small black sticker - an action which HTC says has invalidated the warranty on my phone. They have now created a return reference for me, but I'm likely to be hit with a big bill for repair if/when I send the phone in.
I understand that confusing a sticker for a button is a stupid thing to do, but I can't change what I did and I genuinely thought that I was pressing a button on the back of the phone.
Is there any possible solution without having to send the phone in to HTC?
Thank you,
Craig.
craigspc said:
Hi,
While on holiday I put my Desire HD on charge over night (was working fine at that point), but when trying to turn it on the next morning it just vibrated 7 times and that was it - the phone would do nothing. The phone doesn't respond to the hard reset process described on the HTC website and no lights come on at any point (not even when connected to the charger).
The only time the phone does anything, is when you eject the battery and re-insert it. At the point where the battery touches the contacts inside the phone, it vibrates 7 times again and nothing more. The phone has not been modified in any way and uses the original OS from HTC. All the phone does is vibrate 7 times when inserting the battery. Otherwise it's completely dead.
This would, I presume, normally be a simple warranty case (8 month old phone). However, in my desperation to reset/fix the phone, I tried pressing what I thought was a reset button underneath the SIM & memory card cover (with the tip of a pen). Instead of the 'click' that I expected though, it pierced what turned out to be a small black sticker - an action which HTC says has invalidated the warranty on my phone. They have now created a return reference for me, but I'm likely to be hit with a big bill for repair if/when I send the phone in.
I understand that confusing a sticker for a button is a stupid thing to do, but I can't change what I did and I genuinely thought that I was pressing a button on the back of the phone.
Is there any possible solution without having to send the phone in to HTC?
Thank you,
Craig.
Click to expand...
Click to collapse
Can you post a pic of the black sticker you accidently clicked.. Also any other "void stick" there is
I'd like to know if it is obvious that you tried to open the phone up or not..
To me, if you cannot get into Recovery nor Bootloader, your pretty much screwed, try pulling battery out, insert it back in, hold the Volume down button, and while holding press Power button?
Found this aswell:
http://forum.xda-developers.com/showthread.php?t=879726
Others with your problem, but it seems Service is the only way..
Shidapu said:
Can you post a pic of the black sticker you accidently clicked.. Also any other "void stick" there is
I'd like to know if it is obvious that you tried to open the phone up or not..
Click to expand...
Click to collapse
I'll have access to a Digital SLR tonight and will post a photo tonight. Looking at the phone though, it is clearly visible that it has not been touched with anything other than the tip of a pen. There is another small sticker that I found in the battery compartment - this is completely in tact.
I don't think anyone looking at the phone would doubt that the one sticker was pierced with the tip of a pen, but unfortunately that doesn't seem to make any difference. The guy I spoke to from HTC was friendly and polite, but he insisted that it wouldn't make any difference - I broke the rules and that's it.
I suppose the only reason that I'm disappointed is that I've now had four HTC smartphones and I've never requested warranty support before. Oh well... :-(
Thanks for the links you provided. Lots of useful info, but unfortunately I can't find any solution - the phone is clearly dead.
Thanks,
Craig.
Shidapu said:
Can you post a pic of the black sticker you accidently clicked.. Also any other "void stick" there is
Here's the pic. I didn't bother taking a photo of the other sticker as it hasn't been touched or damaged at all. Would you say it's worth sending the phone and enclosing a note explaining what I did?
Click to expand...
Click to collapse
Sending it I believe is the only way the phone will get fixed. DO include a note explaining what you did but I dont know how useful it will be. You never know though. As the other one is still intact they may believe you and do it for free.
Repaired
I just wanted to say thanks for the replies. I sent my phone in and the repair was carried out under warranty.
Regards,
Craig.
Can you tell what was broken and repaired in your phone?I have the same problem since yesterday...
Without screenshot is more difficult solve :-(
gopiter said:
Can you tell what was broken and repaired in your phone?I have the same problem since yesterday...
Click to expand...
Click to collapse
Apparently it was a motherboard failure. The board was replaced and now it's working fine again.
Same......
craigspc said:
Apparently it was a motherboard failure. The board was replaced and now it's working fine again.
Click to expand...
Click to collapse
Exactly the same is happening to me... 8 months old too..
About to send it off for warrenty, but can you tell me if you lost all your information and number, apps on the handset, as I cant remember the last time I did a sync..
thanks..
I just got answer from HTC service that motherboard of my DHD is broken and they wont replace it because of unautorised firmware flashed...
gopiter said:
I just got answer from HTC service that motherboard of my DHD is broken and they wont replace it because of unautorised firmware flashed...
Click to expand...
Click to collapse
Lol...thats bad, This might be the first case which I have seen returned because of unauthorized firmware..., Don't leave it like that and read the full document which come with the phone. There will be some wording which might not be clear but should be enough to fight back...
Yep...I think I'm the first person who returned phone back from warranty because of no HTC firmware flashed...As soon as I get my DHD and documents back I'll report what they said.
online4yourmin said:
Exactly the same is happening to me... 8 months old too..
About to send it off for warrenty, but can you tell me if you lost all your information and number, apps on the handset, as I cant remember the last time I did a sync..
thanks..
Click to expand...
Click to collapse
Yes, if you send the phone in for repair, you will lose everything stored on the device that you haven't backed up. I think this will be the case even if they don't replace the motherboard. Any apps that you previously bought through Android Market can be restored though - you don't have to buy them again.
Craig.
gopiter said:
I just got answer from HTC service that motherboard of my DHD is broken and they wont replace it because of unautorised firmware flashed...
Click to expand...
Click to collapse
Hmm.. That's bad news... Trying to read between the lines a bit - Are they saying that they won't replace the motherboard because you have flashed the phone, or because they suspect that flashing the phone played a direct role in the failure?
If the motherboard has died surely they'd replace it? Then again, if the motherboard had died completely - how would they know that the phone had been flashed in the first place?
When exactly did the problem start for you?
Craig.
craigspc said:
Hmm.. That's bad news... Trying to read between the lines a bit - Are they saying that they won't replace the motherboard because you have flashed the phone, or because they suspect that flashing the phone played a direct role in the failure?
If the motherboard has died surely they'd replace it? Then again, if the motherboard had died completely - how would they know that the phone had been flashed in the first place?
When exactly did the problem start for you?
Craig.
Click to expand...
Click to collapse
A returned my phone to the seller so I don't have direct contact with HTC service but the seller got information from service that: motherboard is dead because of flashing unauthorized firmware/unauthorized firmware damaged motherboard...I'm waiting to get my phone back from service with documentation and then I'll fight back...
My phone works perfectly normal and when I tried to reebot it simply wont boot...it's strange and I wonder how firmware it self could damage motherboard?
Ok, DHD came back from HTC service with all documentation and statement that they will not repair it etc...and it normally boot into OS...But it couldn't boot into bootloader - just vibrates 3 times.So I booted it again into OS and flashed again the hboot and after that phone successfully boot into bootloader .So now my DHD is fully functional I just wonder why HTC claimed that motherboard is broken and wanted me to pay for replacement...?
Very strange - 8 month fault
I too have a DHD - this one is stock standard - got it back from employee today as he said it was not charging (worked right up till then). i plugged it in and got a flashing orange amber light. left if for a while noting would work. finally worked out if i inserted teh battery while plugged in it woud give me a solid charging light and vibrate 7 times.
Seems strange that they are all faulting at 8 months. Mine was an import, so it might have to go back to singapore or malaysia or where ever it cam from.
Checked battery it is at 3.8V so ok.
gopiter said:
Ok, DHD came back from HTC service with all documentation and statement that they will not repair it etc...and it normally boot into OS...But it couldn't boot into bootloader - just vibrates 3 times.So I booted it again into OS and flashed again the hboot and after that phone successfully boot into bootloader .So now my DHD is fully functional I just wonder why HTC claimed that motherboard is broken and wanted me to pay for replacement...?
Click to expand...
Click to collapse
My warranties over and i've got the same problem!
I just wanted to know if your phone wasn't working at all before you gave it in for service? And when it came back, it was working again?
And be not ready to repair it, they weren't ready to repair it for a fee either?
Omairss said:
My warranties over and i've got the same problem!
I just wanted to know if your phone wasn't working at all before you gave it in for service? And when it came back, it was working again?
And be not ready to repair it, they weren't ready to repair it for a fee either?
Click to expand...
Click to collapse
My phone wasn't working at all it didn't boot even display splash screen...just vibrates.I heared phone services have devices called "BOX" which can unbrick your dead phone.I think they did it with my phone and when it boots they saw my own boot screen instead of stock HTC...so it was clear to them they can void my warranty and offer motherboard replacement for fee (high fee ).I didn't agree for that and phone returned to me unbricked.I just had to reflash hboot again.
I couldn't turn on wifi anymore, the switch stayed greyed out and 1 out of ten times i could switch it on it kept giving the message "turning on wifi". The phone got really hot on the backside next to the camera lens so i send it for repair (Dynafix - Netherlands) now my gnex is repaired and they did a "boardswap" (?) this means that they replaced the whole motherboard? Is this a good thing? An second question, could the wifi module be defect because of flashing roms?
Thanks very much
appie72 said:
I couldn't turn on wifi anymore, the switch stayed greyed out and 1 out of ten times i could switch it on it kept giving the message "turning on wifi". The phone got really hot on the backside next to the camera lens so i send it for repair (Dynafix - Netherlands) now my gnex is repaired and they did a "boardswap" (?) this means that they replaced the whole motherboard? Is this a good thing? An second question, could the wifi module be defect because of flashing roms?
Thanks very much
Click to expand...
Click to collapse
Yes they likely replaced the whole motherboard.
No, roms should not harm your wifi module.
Overclocking and excess heat might be able to though.
Flashing ROMs normally doesn't do anything to the motherboard, itself, but if flashing the wrong radios, or installing the wrong drivers could cause such a problem...
But as long as the phone is working, all is good, don't you think?
If you ask me, I do it this way:
(This is an example only). Phone broke, phone bootloops, with stock ROM, flashing a new ROM won't help, I phone my carrier, I get a replacement, if I don't like the device anymore, I phone again, say the device I got is also defect, I get a new phone of my choice, for free...
I have had to do this twice (hTC 7 pro and Samsung Galaxy S II, yet the GS II was really defect, so was the 7 pro), now I've got a GNexus, it won't boot, doesn't show up, at all, neither as OMAP, or anything. I could probably JTAG it, but as I regret buying the phone, because I miss the button, and I don't want to risk the same think happening, I phoned up my carrier, I'm getting a GS 3 on Friday...
(I will still help with GNex problems, though)
Thanks for your answers, very clear! By reading this i think i broke it myself because for a while i had an older radio with a ics 4.0.4 rom but i can't recall the exact time wifi died on me. Well.... my gnex is fixed for free (warrenty) a little more reading before flashing Thanks again for the answers!
familyguy59 said:
Flashing ROMs normally doesn't do anything to the motherboard, itself, but if flashing the wrong radios, or installing the wrong drivers could cause such a problem...
But as long as the phone is working, all is good, don't you think?
If you ask me, I do it this way:
(This is an example only). Phone broke, phone bootloops, with stock ROM, flashing a new ROM won't help, I phone my carrier, I get a replacement, if I don't like the device anymore, I phone again, say the device I got is also defect, I get a new phone of my choice, for free...
I have had to do this twice (hTC 7 pro and Samsung Galaxy S II, yet the GS II was really defect, so was the 7 pro), now I've got a GNexus, it won't boot, doesn't show up, at all, neither as OMAP, or anything. I could probably JTAG it, but as I regret buying the phone, because I miss the button, and I don't want to risk the same think happening, I phoned up my carrier, I'm getting a GS 3 on Friday...
(I will still help with GNex problems, though)
Click to expand...
Click to collapse
What? installing the wrong drivers on your computer has nothing to do with the motherboard on your phone. My HTC drivers don't affect my nexus, why would they? Flashing a radio won't hurt the motherboard either. It may disable the wifi but it won't physically break the motherboard.
My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
*Update* Went to a cell repair shop, turns out its actually the power button that needs replacing and this is why the phone continually turns off and on and never reaches passed the logo screen. Apparently it's common for the power button to stop working or get all messed up on the gs3, if you have not rooted your phone or played around with the software the power button may be the cause of it not passing the logo screen and your phone might actually not be bricked
me too
KeeKeeB said:
My phone was charging while I was taking an nap and when I woke up my phone was off I also noticed it was hot so I turned it on and it wouldn't boot passed logo screen. I then went to bell and they would not replace it because there is a small crack at the top right of the screen which voids software warranty. One of the bell store employees attempted to put the phone in recovery mode but the process was stopped multiple times due to the fact that the phone only powers on for a few seconds. I don't have the money to buy another gs3, is there anyways to fix this. Doing some research on the phone and i believe it is hard bricked or something of that matter
Click to expand...
Click to collapse
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.
keviinricoy said:
i have the same problem, my phone is from bell too but warranty is over its been like a month like this xS.
Click to expand...
Click to collapse
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed
Have you tried another battery. ...thats what I would try. Also make sure all your ports are clean and debris free.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KeeKeeB said:
Im sorry mate, Bell is awful just a bunch of scumbags. If i can't find any help from here im going to go visit a cell repair shop to get some help. You should try to find some as well, google search cellphone repair shops in your area! I have very little knowledge of software on androids but apparently my phone needs to be flashed
Click to expand...
Click to collapse
Yes i tried my friends battery, this sadly did not work.
recovery
Have you tried to boot into the phones stock recovery and clear it ? Or how about odin a stock rom ? Just trying to brainstorm, but I seriously do not think your phone is toast. I would try seaching these ideas and see if you have any luck....otherwise search for how to recover a bricked phone for your carrier...the same method might work to get you up and running again???
same thing happening to me...i can boot into recovery/download mode but only for 2-3 seconds and then the phone reboots itself...all started after I dropped it from my sofa earlier today. any suggestions anybody?
turns out it was the power button that was malfunctioning for me..got it repaired and now its working fine..
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
is it possible that the LCD went bad?? when you plug it into charge does it react (lcd or vibrate?) I would also suggest trying out a known battery. could be that if it is the original battery that it is so dead that I got "spikey" and finaly just died.
hope it is that simple
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
If she wasn't trying to flash anything, doesn't sound like a brick which, to my understanding, results from software failures. The procedure posted in the thread applies when you are trying to recover from a brick caused by firmware failure from attempting to flash the wrong bootloader so I'd be doubtful if it would help you here. This could be a specific hardware failure which is not unheard of with equipment like this. Also sounds like it gave warning of the gradual failure. When you plug it into a charging outlet, does it show any sign of life - a light or vibration? If it's an LCD failure, it probably wouldn't affect charging or recognition by your PC. If there is no sign of life at all even with different batteries, you may want to try a professional repair service as I presume exercising the warranty is not an option in view of the firmware history.
Hi,
Thanks for the replies.
I did try different batteries. The phone does not vibrate or react at all even when plugged in which does not suggest an LCD failure.
I guess you are right,it must be a hardware failure. I'm quite suprised,I thought these phones were well buit and resistant.Oh well.
She's getting a Nexus 5 now.
Thanks for the help !
My G4 has randomly restarted on me a few times before (only once at a time), but I thought nothing of it. However, this time, it has gotten stuck in a boot loop. My phone was fairly hot from watching videos at a high brightness, and that is when I noticed it restarted for the first time. My G4 is NOT rooted, and I even went into recovery mode and wiped the cache and it is still stuck in the loop. Is there anything I can do besides try a factory data reset? I really do not want to lose all of my data because I did not even get a chance to do a backup as this happened unexpectedly.
Hey did you ever get this problem solved, same thing happened to me today not rooted was watching a video phone froze and now im stuck in bootloop
This just started happening to me on Friday. I have a warranty replacement on the way (and I managed to get the guys at my Verizon Wireless store to give me a loaner Samsung Galaxy S4 so I wasn't completely without a phone all weekend).
It looks like this may be a fairly widespread problem and related to HW version 1.0 of the phones:
https://www.reddit.com/r/lgg4/comments/3k5ofv/verizon_bootloop/
https://www.reddit.com/r/lgg4/comments/3oos3e/lg_g4_stuck_in_boot_loop_pulled_battery_tried_all/
I'm hoping my warranty replacement is a 1.1 version phone, but that's probably wishful thinking on my part.
chairthrower said:
This just started happening to me on Friday. I have a warranty replacement on the way (and I managed to get the guys at my Verizon Wireless store to give me a loaner Samsung Galaxy S4 so I wasn't completely without a phone all weekend).
It looks like this may be a fairly widespread problem and related to HW version 1.0 of the phones:
https://www.reddit.com/r/lgg4/comments/3k5ofv/verizon_bootloop/
https://www.reddit.com/r/lgg4/comments/3oos3e/lg_g4_stuck_in_boot_loop_pulled_battery_tried_all/
I'm hoping my warranty replacement is a 1.1 version phone, but that's probably wishful thinking on my part.
Click to expand...
Click to collapse
i read about the problem with the motherboard going bad i thought it had more to do with the serial number or the manufacture date mine was 505, anyway i recieved my replacement from lg and new serial is 512 but HW version is still 1.0
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.