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,
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,
In my attempt to root the device which I was successful in doing somehow things went south when i tried to flash TWRP on my device. I performed the .img to tar.md5 conversion with the CWM Tool on another thread then i flashed the file to my device, afterwards the devices were rebooted and now I am unable to touch the screen with my fingers and only my S-Pen works, which tells me hardware wise the screen is ok but something software wise is causing this issue. Can someone please help me in troubleshooting this issue. I seen another user have this same exact issue but it ended with him sending it to the service center. I have performed a full dat/factory reset.... I have performed a full reflashing of the stock rom i have re-rooted. I am all out of options.
See video i made regarding this issue.
https://www.youtube.com/watch?v=orLEnWhlATo
Thanks in advance!
Can anyone help with this
Capacitive touch and spen use 2 totally different chips inside the tablet. The spen uses a Wacom digitizer, while touch interaction is processed using standard methods.
In fact, each one has their own ribbon cable from the screen to different points on the motherboard.
I have no idea how rooting broke your touch ability, but the spen working is not an indication that the touch interaction is not damaged in some way.
I can tell you that on mine (especially when using papyrus) it has a tendency to lose touch until I shut the screen off and turn it back on. Maybe something screwy is going on with the touch driver. Flash back to stock and see if it's still broken
Did the reset work?
I ask because we just got a used tablet off ebay and it is doing the same thing to me. My wife emailed Samsung who said blah-blah-blah so we are stuck with it. I know enough to brick a phone really fast, but I have been running custom Roms a long time and have replaced screens so I may check the cables on my day off.
But it was doing it before I rooted it, recovery, and Hyper-drive Rom.
though the knox had been tripped before I got it, so I don't know what has been done to it before this. So please let me know what you think even if you try it and it does or doesn't work and I will gladly do the same for you.
Thanks--Rick
Hi All,
I had recently replaced screen and digitizer (which i bought through amazon with whole body) of my Google Nexus 5 Phone.
After i put everything back together, charged and turned on the phone i could see its turning on, i could see google sign comes up on main screen followed by 4 dots circling on screen and that's it after that it shuts off.
I have reopened the phone couple times already and reconnected everything back to make sure i have not left any connections in first place.
I have tried to go in recovery mode to do a hard reset but no luck there it says "no command"
I took the phone to a wireless repair place they said they couldn't do the hard reset because the data files are missing and the reason it happened is because i touched the processor board while replacing.
but they did confirmed its a software corruption issue, once a hard reset is performed through computer it should be all set.
i know i could loose all memory but thats okay.
any help here is much appreciated.
Thanks.
Hi there,
Here is where you must read about fixing this issue:
How to Fix a Google Nexus 5 | Screen Replacement Repair Guide
For other questions please ask directly here:
[HELP THREAD] Nexus 5 | Ask any question
Good luck
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
EriBerry said:
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
Click to expand...
Click to collapse
You may get more help by getting the thread moved to Galaxy S6 Edge Q&A, Help & Troubleshooting.
To do so, simply click the "report button" and select "thread/post moving".
Now, on with the issue. What you're having seems to be a bootloop.
One thing you could try is booting into recovery and wiping the cache.
I'm not exactly sure how booting to recovery works on the S6, but it generally is: turn the phone off, then hold the power button + volume up button until the phone vibrates. If that doesn't work, try adding the home button to that combo, or just Google how to boot into recovery.
Anyway, if that doesn't work, then I'm afraid there won't be any other solution than reinstalling the firmware yourself or sending it to warranty (where they will probably reinstall the firmware).
Your photos shouldn't be affected in the process, as they are saved on the internal memory and, unless somebody wipes it, you shouldn't lose your files.
But you will definitely lose your apps and app data in the process.
Flashing the firmware yourself should not void the warranty.
The process can be done with Odin (a software also used by Samsung). I'm not sure how familiar you are with flashing, but you may want to do some reading or watch video guides on the subject of using Odin. Since the S6 is pretty much a new device, I'm sure you will find lots of video tutorials for the S6 specifically.
And, as I said, your internal storage stuff should be safe too.