Related
My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en
Are you using a custom recovery/ROM? That icon you posted isn't the stock image
Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?
just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet
Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!
Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.
I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...
I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?
I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.
Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.
Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !
No, but this problem is not ROM related.
discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.
I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.
welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.
Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.
Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks
I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary
Hi everyone,
I'm experiencing really wierd behaviour with my HTC Desire S. I'll try to tell the story as it happened, so you may have the best grasp on what's happening to me. Here's the thing: yesterday, I charged my HTC on the wall plug as almost every night (y'all know how it is with smartphones, always needing to be charged ). When I unplugged it on the morining, the green LED stayed on. Not cool. I can't really remember if it was turned on and stuck or already turned off at that time, but I had to reboot the phone. Okay, that can happen, phones have to reboot sometimes.
And then, it did not boot. Instead, it was stuck on the bootscreen. I looked around on the internets, but people seemed to have boot loops or devices stuck after the "quietly briliant" part. Actually, mine was stuck before that part. It didn't even play the funny sound and show the fancy animation: it was stuck on the blank screen with only the HTC logo.
I tried many things, like praying pagan gods and removing the battery, let it cool for a while, boot and wait to see what happens for more than 30 minutes, boot it while plugged on the wall plug... I think I was about to get to the "I'll have to make a factory reset, then" line when I tried to see what dmesg would tell me if I plugged the phone on my computer. Note to self: always try to plug to computer. It did boot completely. The victory dance was almost completed when I was invited to enter my PIN code. My touchscreen did not respond. Damn.
So I had to reboot. Again had to remove the battery (I don't like that, but what choice do I have?). Now it always boots completely (that's a good start), but my touch screen seems completely unresponsive. I can't access anything, can't enter my PIN code or unlock the phone when there's no SIM.
That's where this forum comes in: I've not given up. You see, my phone has USB debugging activated (yeah I know, the thread's title spoiled all the story). I'm pretty sure this means adb can help me in some way to troubleshoot my device. adb shell gives a nice UNIX-like shell, yay, that is relevant to my interests.
My phone has never been rooted. I've looked into it (that's why USB debuging was activated), but I wasn't 100% confident it would work, so I gave up before ending up bricking my phone (duh, too late, haha). It's running the last Gingerbread version distributed by HTC in Belgium (2.3.5, I think, without any certainty), with the last Sense version related (could it be 3.0.3?).
tl;dr: Unrooted phone with unresponsive touch screen, debugging mode enabled, trying to find what's wrong.
So here's what I'd like to know: is there any way to try to force start my touch screen with the help of adb? Where's the related log, the one that should display the error(s) that occur(s)? Should Bill Murray play in the next Batman? If root is needed, do I have a way to use a temproot exploit in order to fix my phone once and for all?
Any attempt to help will be greatly appreciated. This is my first post here, I hope it's clear enough, and not too nooby for you guys. Also, that I didn't break any rule (I watched/lauged at that video about noobs to xda). Btw, I'm quite confortable with UNIX shells, so don't avoid cli-related answers if that may happen to be helpful. Also, I'm not at home right now, but I'll follow this thread with a lot of interest anyways. I'm back on a regular connection next sunday.
Have a nice day! And sorry for the long post (but believe me, I'm even more sorry to admit I can't investigate further on my own, now that is frustrating).
Okay, I'm back.
It makes no sense. I let my phone on for a few days, then suddenly, probably out of boredom removed the battery, put it back and rebooted. I distractingly tried to unlock it… and it worked.
I have absolutely no single clue on what happened. And I'm still quite concerned, because this means it can happen again without any warning.
I'm gonna give a shot at HTC's support in order to ask them what I can do to locate the problem if there are traces. I'd really, really like to read all the logs (and logcat didn't show anything interesting).
If anyone has a suggestion, feel free to shoot it. I'll try to keep this thread updated in case someone has the same problem.
Duh, just got an anwser from HTC's support. Totally useless, they told me to try to reboot in Safe Mode in order to see if the problem happens again. Well, even in normal mode it has not failed for two days. GJ, guys.
I'm really willing to meddle in my system in order to see what could have gone wrong. I'd especially like to see if there is any way to see whether there are HW faults or not, since I'm suspecting a temporary TS chip failure, which can happen again at any moment. I'll be reading some documentation about Android's system and its logs.
Yeah, I know I'm talking a lot alone, but if someone ever has the same problem, he might be able to see what I've gone through, so I'm documenting as much as possible. =)
adb bugreport
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello all
I come today with a question that i hope someone will have an answer for.
Week ago my Nexus 5 turned of and would not turn on, at all. Only times it showed signs of life was when it was charging. Then it would show the google logo for half a second and then turn of, then do the same thing forever. There was no way to enter the recovery or any other part of the phone.
This is how it looks: https://www.youtube.com/watch?v=7wNZfC1LSBA
After reading lots of stuff on the net and contacting Google and LG(with no help from either) i figured it was game over for the phone but i decided to send the phone for repair to a bigger city in my country some 400km away.
Here is where it gets interesting. Today my father delivered the phone and they fixed it literally in 3minutes. When my father asked what they had done, they said to him (or atleast thats how he understood it) that they have done a hardware reset. Apparently the phone got "blocked" somehow and they simply reseted the hardware.
My question is, what the hell is a hardware reset and how do i perform it myself???
I have tried EVERYTHING i could find on the internet to try and fix the phone before sending it, im not the greatest expert but id like to think i know my way around android more then the average user. I have to say again, the phone showed no signs of life, it was impossible to enter recovery so i have no idea how they could have done it.
I would really like to learn how to do this, so i am prepared if it happens in the future.
Thank you for your time
Factory reset?
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
valentinitag said:
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
Click to expand...
Click to collapse
If you have warranty take it to LG.
It will be an expensive way to find out what is fauilty, the motherboard or the screen.