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
Related
Ok so iv had my GN for four days now and its developed a problem with the power button.
Sometimes when i try to turn the screen on via the power button it wont respond, at first. It happend last night for the first time, i tried to unlock it and nothing happend, then after trying about 5_6 times it rebooted. Same thing happend this morning.
Has anyone else had this problem?
Does anyone think this could be software or hardware issue?
The phone is completely stock running 4.0.1 on tmoble uk.
Anyones help or opinion would be appreciated.
Try updating to 4.0.2 before you write it off as hardware problem.
Sent from my Galaxy Nexus using xda premium
Thought about that but it would mean rooting , my fear is that it becomes permenant , then my warrenty would be void , i did have it on face unlock when this was happening i have now changed to slide and as yet ive had no problem , i will post here if the problem is fixed for anyone who is interested
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
mwestendorf said:
I thought the stock build is 4.0.2?
Have you tried pinging for an update in the settings menu?
Sent from my LTE Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yeah several times, and its defo 4.0.1
chirea.mircea said:
Rooting is not permanent. You can remove it by delete the SuperUser apk and binary; that's what root is. Or if you're paranoid, flash a stock image.
Then lock the bootloader. Hooray, your device is stock.
Click to expand...
Click to collapse
Yeah i do understand that, my fear is while rooted that the problem becomes permanent (at least for me) then while off for repairs they see that its rooted and tell me to get lost!
Iv had a few problems with this phone like locking up while adding widgets to home screen, locking up half way though a phone call, browser hanging all the time and of course the power button all of which resulting in a battery pull.
Id come to expect this kind of behavior over the last year & 1/2 from my hd2 as it wasnt ment to run android in the first place, but this is a google flagship.
Maybe i just got a dud or maybe its the stock 4.0.1 has anyone on custom rom had any of the above problems?
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
RogerPodacter said:
i think the point is that you can unroot it and they cannot tell the difference that it was ever rooted in the first place. and get your warranty fix.
Click to expand...
Click to collapse
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
I haven't experienced anything like what you're describing on my Galaxy Nexus, even while I was running 4.0.1. Does the power button only become unresponsive when you're turning the phone on/off? Or does this happen while trying to lock/unlock the phone as well? If it only happens while you're using the face-unlock feature then it could be a software bug and flashing could fix it...
I would call either Samsung or your carrier about it before deciding to root/flash it myself. Perhaps your carrier will just switch it out for another one they have in stock.
I have experienced this problem as well with the power button. I have the GSM version and I haven't received the 4.0.2 update but I did receive the ITL41F update. After about three or four presses of the power button it becomes responsive again. I think you might be getting the resets if you press the power button repeatedly without waiting a few seconds I'm between presses to get it responsive again. I also do not think it is hardware related and may be some kind of software bug. I am waiting patiently for the updates.
Sent from my Galaxy Nexus using XDA App
Kinbote said:
Yes, but his point is if the power button becomes unresponsive while he is attempting to root/unroot the phone then he wont be able to complete the process.
Click to expand...
Click to collapse
yes thats exatly my point, although i really am leaning toward software as tk123456789 pointed out if i wait a few seconds it will come on though only after i got rid of the face unlock, using face unlock it was a lot worse. Im thinking if it were hadware it would either work or not,
BTW this problem is when i unlock the phone and not when turning it on, i dont think i made that clear.
my power button has stopped working....it only works sometimes but it usually acts like im holding it down....if i pull the battery and put it back in, it boots up by itself and i dont even press anything...idk what to do and im freaking out
I wonder if this is becoming a known problem with Samsung devices. Do me a favor and shake your phone a few times. Try it every now and then until it wakes your phone or the power menu pops up. Means the switch is busted and the contact is floating around. This is what was going on with my Captivate and I haven't found a fix, nor do I want to solder on a new power button.
I left it in rice overnight and now everything is working perfectly! Hopefully it stays that way! It may have gotten wet from my XO skin application! Never ever ever again with a wet apply! NEVER!
Edit: its still doing the same thing again...spoke too soon
sent from my Nexus Prime
I got my GSM Unlocked Galaxy Nexus from the Play Store two days ago and am experiencing the same issues with the power button. It worked fine for the first 24 hours.
I'm on the phone with Google right now to get a replacement phone which is nice because they're contacting Samsung on my behalf.
(I'm within the 14-day replacement policy for new devices)
Flash manually the official 4.0.4 IMM76I.. And relock your bootloader after that and try.. Thats it
Sent from my Galaxy Nexus using xda premium
similar Issue:
I bought a used, rooted Galaxy Nexus. Due to my own (drunken) stupidity not long after my purchase I caused a scratch on the glass covering the display. As I did not want to pay for a out-of-warrenty repair, I left the device as it was.
Some time after, my power button became unresponsive. As it took 3-5 presses to activate the screen I installed the app "PGM Galaxy Nexus" that allows to wake the device with a swipe gesture. Not to long after, the power button stopped responding all together. While researching a permanent solution, my battery died.
In order to be able to use my phone as soon as possible, I brought it to a local (and unfortunately, unauthorized) repair shop. The repair shop tested quicky for any further defects (by plugging the phone into a wall charger - I had done the same at home) and quoted me 50€ for the repair. Some time after, they emailed me that the replacement of the power button did not repair the device. They said however, that the "main power supply IC" is most likely at fault and that a replacement would cost about 120€. As I could not find this chip in the teardown pictures at ifixit, I am not sure if I should invest further trust in the repairshop. In addition and as writen above, charging the device was no problem at all. In fact, I charged the battery that was in my Galaxy Nexus to 100% before bringing it in.
This is where my questions start:
1.: Is a defect of the "main power supply IC" a known defect at all? If there are known defects of the "main power supply IC" are those defects linked to a faulty power button?
2.: Currently, my plan of action is to collect the device and contact Samsung to have it repaired by Samsung itself. Does this mean sending it in? Do they have authorized repair centers like Nokia used to have (NSC) where I could just bring it in?
3.: What might the cost of the repair be? Can it be noticed that the device was opened before? Is root a problem when sending it in for repair?
I would be greatly thankfull for any device and in case I forgot to provide any details, please feel free to ask.
Related Information:
Galaxy Nexus GSM unlocked, bought in Germany
Android 4.2, running no custom firmware but rooted
Purchased by the first owner on 24th March 2012
Running on E+ (simyo) and o2 networks
I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.
bobvanjr said:
I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.
Click to expand...
Click to collapse
I'll leave the real advice to the experts, but I can tell you that putting your Note sim card in your Nexus certainly did not brick the Nexus. If your Nexus is bricked and that is really all you did to it, then it was defective when it arrived -- you didn't do it.
Well, I'm glad it's not my fault but WTF? If it is jacked I hope I can return it to Google.
Odin phone?
*EDIT* See there's only tar for sprint. Try factory reset?
Sent from my Galaxy Nexus using Tapatalk 2
Def not bricked. Search stuck at boot loop and there around a million threads with instructions.
people on these forums really have a hard time understanding what bricked means
Yeah it's good that actually bricking these days is pretty rare outside of getting wet. I remember when people failed when hspling their HTC wizards and bricked to the point of requiring jtag.
Sent from my Desire HD using xda premium
you can do two things here:
1. return the phone and get it replaced.
(or)
2. just flash the stock factory image and see if that fixes it.
Sent from my Galaxy Nexus using xda app-developers app
I have a gnex with my notes Sim and never had an issue
Sent from my Galaxy Nexus using xda premium
Pardon me for calling it bricked. I mean I have a $350 phone that doesn't work. I'm no expert. If I was I probably wouldn't be asking here what to do. I tried the volume and power button and went into recovery mode as someone suggested. I get to the point with the Android with the exclamation. It won't allow me to go past that.
Anymore suggestions?
Btw, I did search for what to do and didn't find any way to fix it or the ideas didn't work, thus my question.
Even if I did get it working it would be interesting to know what happened.
Thanks
http://lmgtfy.com/?q=galaxy+nexus+boot+loop
http://forum.xda-developers.com/showthread.php?t=1626895
This tutorial by efrant is amazing and will get you sorted
bobvanjr said:
I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.
Click to expand...
Click to collapse
This may sound silly but how long was it boot looping for ? I would be incline to let it do whatever its doing...I would say give it a good a good 10-15 mins and see what happens. Just a suggestion.
This could help too http://forum.xda-developers.com/showthread.php?p=28486488
I ended up posting on AC also and some guys walked me through recovery. It wouldn't work. I called Google and they did the same thing. It didn't work. They called it DOA and got me in touch with Samsung. Samsung is sending me a new phone without even getting this one back first. Of course they will charge me if I didn't send it back, but still, darn good service. The guys at Google were also very nice (and American) and they were professional and easy to understand. Great guys.
Well, they may not have been American but they spoke English well. I only mention that as I have recently spent time dealing with Straight Talk customer-no service and it was so flipping hard to understand them ON TOP of their horrible service.
Anyways, seems like I got a bad unit. I'm sure there was a way to flash a stock image or something but because it was literally brand new I figured I'd just get a replacement.
Everyone has said the sim shouldn't matter. Is that 100 % true? Could I use my Note one day and decide to use the Nexus the next just by switching the sim? I think that's ideally what I'd like to do. I still have my Epic Touch on Sprint and 3 phones is gonna be a pain. I've been using Google Voice with the Note and that has been working out ok.
Anyways, thanks for all the help and I apologize for being such a noob.
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight
U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all
Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
That sucks. Good that they are replacing it. What was the last thing you were doing before it happened?
VoiD_Dweller said:
That sucks. Good that they are replacing it. What was the last thing you were doing before it happened?
Click to expand...
Click to collapse
Yeah I have PHP protection with them so I always have warrenty and insurance together. Its alot easier trying to get an exchange when your phone wont turn on because they dont make you do 1000 different things lol, was off the phone within 5 mins. Tried being slick and saying " Well you know if their arent any S2 in stock, you can always send me the s3 if you like ".. Didnt work =[ They had s2 lol
Anyway, nothing really. Was just typing, put the phone down, then the screen went off like it always does, then when I tried to turn it back on to unlock it, it happened.
This happened a few weeks ago but the vibrating lasted for a couple of mins ten ended up turning itself back on. Now its just not turning itself back on at all. Just stuck with the vibrate.
Am I losing everything on it now or will it automatically back up on my gmail account?
I knew I shouldnt have saved all those pix on the phone and not the sd card lol
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
Is this a thing with this phone? Got the same problem two days ago. Cant send to tmobile, any idea anybody?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
ITALIANNYC said:
Am I losing everything on it now or will it automatically back up on my gmail account?
I knew I shouldnt have saved all those pix on the phone and not the sd card lol
Click to expand...
Click to collapse
Sorry, unless you had some kind of auto upload set up ( I set mine up through Dropbox and Google + ), those pictures are likely lost.
Google doesn't automatically sync pics unless you have Picasa, I think?
Russian smashed across the interwebz from my T-Mobile Galaxy S2.
Sounds like the power button might be stuck.
I gotta say, I HATE UPS. I dont know why T-mobile uses them. You get overnight delivery and of course they ring the wrong bell and do not come back. I live on ground floor and they up and ring top bell. Fed EX of course would always come back. Thank fully the overnight delivery was basically be free, but that sucks. I also wish they would just leave the phone sometimes but they never do, even though it is not sig required. ( Drivers Discruction )
Gotta wait till Monday now.
sux brohim
had the same thing happen to me. this was back when i was dong the stock ICS update through (hang myself) Kies. Thankfully T-mobile sent me a new one at no charge and i didn't pay for the shipping either. either battery fried or something in the phone. seems to have been a fairly rare but known prob with the t989.
i always seem to to get the units that are within the .05% of defective units, no matter what company i buy from.
Here's to hoping you get better luck with the next unit! :raise a beer:
Quick question
I have used GB for my gs2 from the beginning and never upgraded to ICS.
I am worried that the replacement they send will have ICS in it. Simply put, will it be easy for me to put GB on the phone when I get it.
You can root and flash a gb Rom
Sent from my SGH-T999 using xda premium
You can go through odin and follow the tutorial on galaxys2root.com to unroot and ffash to stock GB. Link provided. The power button may have been stuck on yours but congratulations on getting it replaced. Just follow that tutorial and it will get you to stock 2.3.6 GB with no root or anything done, completely stock.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
Was messing around with the power button today pushing it 100 times and it finally turned on. Figures it would turn on when I'm getting a new one on Monday. Least I now backed up all my pix and contacts. Now point in keeping this one though, probably gunna happen again. Keeping the new one.
Wow another S2 down with a defective power button. I just had to send my out to get fixed for the same problem. This is become more common
So I received the phone today. Came stock with 4.0.4.
I plug it into my computer and kies gives me this
" Your device does not support software upgrading via Kies "
What the hell is that all about.
Oh and when I made my first call, I heard the people on the other end, but they did not hear me. I had to battery pull. It sucks because that was an issue with my phone on GB, figured it might have been fixed with ICS. Guess not. It really makes me sick that this happens. Sometimes I call someone and I hear nothing at all. Its happened with both GB and ICS. When the hell are they going to issue a fix for this crap.
First thing that I noticed and do not like is that when I use the keyboard, the phone vibrate heptic or w.e is not as strong as it was with GB. Also the voice on the other end sounds more muffled and more can like than GB. Not sure if thats the phone though
I keep reading that ICS stock verison UVLH1 ICS 4.0.4 is the Official tmobile and best ICS rom for stock
The phone they sent me is Baseband Version UVLI1.
I cant find anything on this version. What is it?
ITALIANNYC said:
I dont know what happened. Running stock everything
All of a sudden the phone shut off and now it vibrates every 2 seconds. Have tried everything to get it on.
When you put the battery back in, it shows the load up screen and then half way through, shuts itself off and just vibrates once every 2 seconds. Really annoying.
Called T-Mobile and having a replacement sent tomorrow.
Click to expand...
Click to collapse
Time for upgrade maybe you can convince them to send you S3
I had to just replace my S2 with a new one from t-mo because I had tons of problems with my original phone once it upgraded to ICS. "Hanging" goodbye (didn't want to shut off unless you took out the battery, even after the buzz - which tells me that I may possibly had a stuck on/off switch too), lost the phone's internal driver so that the phone can be plugged into my PC, internet and processes became S-L-O-W-E-R than molasses, and more.
I'm assuming that, since all the S2's now have ICS on them shipping out, Samsung may have added a little additional processor power or something in order for it to run efficiently on ICS. All I know is that it runs a little faster than my original S2 did. And no problems - SO FAR.
P.S. UPS really does suck - they tried to deliver twice to my house, didn't leave one of those sticky things that said they were there, and I finally wound up going to a UPS service facility where I had to wait over one hour to get my new phone.
sparkie6point0 said:
I had to just replace my S2 with a new one from t-mo because I had tons of problems with my original phone once it upgraded to ICS. "Hanging" goodbye (didn't want to shut off unless you took out the battery, even after the buzz - which tells me that I may possibly had a stuck on/off switch too), lost the phone's internal driver so that the phone can be plugged into my PC, internet and processes became S-L-O-W-E-R than molasses, and more.
I'm assuming that, since all the S2's now have ICS on them shipping out, Samsung may have added a little additional processor power or something in order for it to run efficiently on ICS. All I know is that it runs a little faster than my original S2 did. And no problems - SO FAR.
P.S. UPS really does suck - they tried to deliver twice to my house, didn't leave one of those sticky things that said they were there, and I finally wound up going to a UPS service facility where I had to wait over one hour to get my new phone.
Click to expand...
Click to collapse
I am not really happy with it. Seems slower to me. Not as smooth. Still sometimes the person on the other line cant hear me, and vice versa with the battery pull, but I had that with my old phone and GB also. If I am going to have it either way though, id rather just stay smoother with GB.
What did your new one come with? Mine is UVLI1. Kernel 3.0.8
So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !
jcrompton said:
So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !
Click to expand...
Click to collapse
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.
xmattisi said:
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.
Click to expand...
Click to collapse
Unfortunately mine won't even boot into recovery
jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
I am sorry to hear that.
jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
That definitely sucks! RMA...RMA...RMA! :good:
Badger50 said:
That definitely sucks! RMA...RMA...RMA! :good:
Click to expand...
Click to collapse
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Don't blame you a bit my friend. Problem is, what to buy that doesn't have it's problems as well? I wish you well in your search :good:
xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Why don't you take it back to bestbuy?
jd1639 said:
Why don't you take it back to bestbuy?
Click to expand...
Click to collapse
BestBuy only has a 14 day return policy. Even when they do run the return if its not covered under a protection plan which is for physical damages ( $200 deducible to get the replacement ). On top of that they also have a restocking fee lol. When you try the return under the manufacturer warranty it tells me to Call Google.
I haven't even fully remembered what I lost but this has confirmed one of my concerns about a device that doesn't have an SD card .... Basically either Pixel I've lost everything that doesn't get backed up to the cloud
So I gotta get better at backup routine or get a device with an SD card
I believe titanium might be the way to go. https://www.titaniumtrack.com/titanium-backup.html
Well for sure TiBu would be helpful for your apps and some of the app says if you were doing backups online
I'm mainly taking about the scores of files that were accumulated in out device that may not get backed up ..... Where on a device with an SD card, I use the card mainly to store things.
Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Sent from my [device_name] using XDA-Developers Legacy app
cmlusco said:
Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Click to expand...
Click to collapse
Absolute unbelievable!!!
Now I'm thankful but maybe even more frustrated
This worked!!!!!
After an hour on the phone with Google support (I obviously knew more than they did) ..... Worse yet with an RMA device in hand ...... My phone is back up and running!!
Now... Should I send the reburbed RMA back or the original phone back? Lol
Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Sent from my [device_name] using XDA-Developers Legacy app
cmlusco said:
Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Click to expand...
Click to collapse
The DINC! What a great device and learning tool that was! :good::good:
Thread cleaned. Keep it civil.
The lack of respect needs to stop. All users know there will be risks when doing anything to a phone post bootloader unlock.