Related
I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?
So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.
I hope that you have the warranty from the carrier!
gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.
!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....
ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk
android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.
volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.
Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.
Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux
republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
If you can't get the phone to turn on you're out of luck.
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/
Call Google and get it replaced. They are very good about that stuff.
kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!
Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?
That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!
So I had purchased my HTC One M9 through their website (it guides you where to pay and see the price). I opted out of the warranty because I have never had an issue with any of their phones and I still try to convince people to buy them. Nonetheless, while I was in the middle of a phone call my phone had suddenly just up and died, which i thought to be weird since I waited to leave the house until it hit 80%. I have tried everything I could think of since I have done quite of my own tinkering on previous models. No computer it is plugged into recognizes its' existence. I have been able to hold down the buttons and get it into recovery but everything there fails. I contacted HTC and they told me to try and manually install the update rom but without finding a computer that sees it, there was no such luck. Their only other option they gave me was to send it in and pay $250 to have it looked at. When I bought it brand new it was damn near $800! I'm just wondering if anyone has had this problem or if it is in fact a hardware rather than software issue. I have never tried to unlock it or anything since it came unlocked from the factory. Story of my life...haha
Can you get into your boot loader? That might help your computer recognize the phone.
Last night my phone went dead. When I plugged it in. I saw the Goggle words on the screen, like when the phone is booting up from being off power. this stayed on for several seconds, then it flashed off and nothing all night. The led light was flashing on and off for a bit, but nothing. I couldn't turn it on then.
Then this morning, I was able to hold the power button and then the Google showed up for a few seconds, then nothing. I have tried holding down the power button for 10 sec to no avail, holding the power and vol down, nothing. Is there any other way to reset this or is the battery or something else on it dead and it needs to be returned to Google. Any and all help is welcomed.
Right now I have it plugged into the google cord and plug, not seeing the led light.
Good news: You're not the only one this is happening to.
Bad News: Not really a good solution yet.
Android Authority is covering it. There's some discussion in their comments.
I tried going into recovery and factory reset/wipe cache and that did nothing. Apparently some people have had luck flashing an older release, but I wasn't able to get anywhere close to that. I ended up calling calling the Google Hardware Warranty Center and they're sending me a replacement.
If bootloader is unlocked, I will be able flash factory image to fix this?
I haven't rooted the phone. It is just the basic android. I'm on with Google support right now. They are going through all the things that I have already done.
I can't get to the bootloader. The phone is off / dead right now. Once it turned off last night, I haven't been able to get it to power up again.
Google wanted me to put it on their cord and charge for an hour to see if anything changed. Hoping it works. I have to travel this weekend, and he was saying it could take up to 7 business days to get a new phone.
No power after 2 1/2 hours on the google cord. Guess to get a replacement.
hope you have a backup phone to use.
I have an iphone 5 I use for Ipod. Would it be too much work to use this until I get the other one, or will it probably not have the right sim card?
I'm in the same boat too. Google sent me out a warranty replacement. Mine just crashed when making a call and it would no longer power on after that. The only thing it would show when plugged in to my computer was Qualcomm downloader for USB.
When I updated to Nougat, I now get the screen that says Firmware Update with a message telling me to keep it plugged in. It's been at 0% for a few hours. Rebooting the phone results in the same thing. Phone's not rooted or anything. Guess I have a brick now.
90s
Sent from my Nexus 7 using XDA-Developers mobile app
There are lots of reports that nexus5x die after the nougat update
I got it to boot up last night, and I was able to get it to recovery mode, then tried to reboot, but nothing else. I'm contacting Google again to get the warranty started.
Just ordered a replacement, bummer that it is a refurb, not new, but sometimes the refub units are tested more than new. Is there any way that I can ensure that the data on the phone won't wind up in the wrong hands after it is fixed by Google and sent out, or is it just a roll of the dice?
They said they were sending me a refurb but its was a brand new one. It came in a retail box. Wondering if they ran out of refurbs with all the people having issues.
So I have the refurb unit at home. It is asking to update to nougat. Are the software updates safe enough to put on the phone. Mine is just stock not rooted.
Can't wait. I've been limping by on the iPhone 5.
Sent from my iPhone using Tapatalk
Mine died, LG told me to send it to them for repair, but only have me a FedEx ground, would have liked more like Air delivery for faster processing