Database Info

[Q] Solution for random reboot/boot loops?

I've been searching the interwebs and XDA for days regarding the random reboots that the Nexus S is cursed with and I was wondering if there are any confirmed solutions? (Phone randomly reboots, and gets stuck at a bootloop with a very dark screen until battery pull).
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
Mine has been doing it at the most random times, which is a major inconvenience for me if I rely on the alarm clock to wake me up in the morning.
I've run factory wiped, flashed stock, Cyanogen, and NSCollab and they all have had the problem. Can anyone provide me with some help?
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.

I just got an AT&T version for my wife during the "free upgrade" promotion. I have not rooted or installed any roms and this phone is having some issues. Reboots at completely random times, goes into boot loops, and even locks on a black screen with the buttons lit. I have been searching for about 2 hours without any real answers. I have been through Aria, Captivate and now NS. Flashing roms and dealing with android quirks is usually not an issue, but I want to retain my ability to return this phone if it is faulty.
What I have tried:
1. Uninstalled questionable user apps
2. Switched SIM cards (used my SIM)
3. Factory Reset
Model: GT-I9020A
Ver: 2.3.4
Base: I9020AUCKE1
Build: GTJ61
Some help/suggestions from some experienced Nexus S owners would be appreciated. Thinking tomorrow will be a return to Best Buy.

andythefan said:
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
Click to expand...
Click to collapse
I ended up doing an exchange at BB today and the problem is gone. I would definitely attribute your problem to a hardware issue. The new NS that I have is running smoothly and has not had one freeze or reboot yet. Get yours traded in before it is too late.
I would like to add that it seems there is a lot less support/community advice in the NS section than some of the other sections I visit. Strange...

I get the same thing, and frequently woke up (late) to bootlooping...
This is far from a fix or diagnosis.. but this is how I manage:
1. Buy a cheap alarm clock
2. when the phone is bootlooping, I plug in the usb (to computer), open dos prompt and type adb reboot or adb reboot recovery (then fix permissions). If you have the android sdk installed on your computer, of course.
I have a case.. and it's a pita pulling the battery out.
However, before i go to sleep, I've been turning off auto-sync (gmail, contacts, etc, all of them), and it hasn't bootlooped overnight since.
Something to try.. but good luck My signature has my phone version and setup.

Thanks for replying everyone. I went ahead and arranged to have it replaced. In my area only one Best Buy had Nexus S's in stock and they were sold out online. There was an armed robbery in the area near the Best Buy, but I went anyways!
I've got the last Nexus they had and just nandroid restored. Everything seems fine so far!

Not even a week into having a replacement Nexus S the reboots have started happening again. It's happened twice today. This leads me to think, is this a software issue?

Try a different kernel.
Wipe cache & dalvik.
Fix permissions.

Rooted, Running Revolver, Screen Problem

So, I've rooted my TF and been running the latest Revolver ROM for about a week. Everything ran awesome with very few flaws. I also recently RMA'd my dock for the sleep issue and just got it back yesterday.
I hooked up the dock to my TF and it ran great all last night and this morning. Everything charged just fine. I packed it up to take to work, took it out at work and...nothing.
My TF would not wake from sleep. I thought maybe I had suddenly encountered the sleep of death issue that I had heard about but never experienced, so I held in the power button and restarted.
The TF restarted just fine. Booted past the first screen and the custom animation screen. But as soon as it was supposed to boot into the homescreen, it goes blank. The TF is on as I can hear email notifications and stuff, but there is nothing on the screen. I tried booting and re-booting with the same result.
So I wiped cache. Same result.
After getting an MD5 Checksum error from the one backup I had of my system through CWM, I wiped data/factory reset. I actually got past the boot animation and started setting up my TF again. However, the screen was set to auto-bright (I like it at fairly bright) so I started to adjust it. As soon as I touched the brightness controls, the screen went black. TF still on, just no screen.
I booted back into recovery again, wiped data/factory reset again and again it booted up just fine and took me to setup. Went to adjust brightness in the actual settings menu and as soon as my finger touched the brightness bar, the entire screen went black.
WTF? Has anyone else gotten similar experience with your TF, either rooted with a new ROM or not? Not a whole lot I can do with a tablet with no screen.
Here are the things it is not based on my observations:
1. It is not a dead screen. On boot up, the screen works. Animation plays well. I can access the CWM recovery menu.
2. It's not a dead touch screen. I can factory reset and go into the setup using the touchscreen.
Here are the things I suspect it COULD be:
1. Something up with the Revolver ROM. I had refrained from applying the 2.1.1 update as the update immediately after that just reverts it back to the version before the 2.1.1. update. However, I did apply the update after the second time of factory resetting.
2. Something up with my dock/dock software? I didn't have any of this issue before I received my dock back.
Please, can anyone help me out here? Sorry for the long post, but wanted to include as many details as possible.

Does the issue occur not docked? Can you use the dock brightness buttons to bring back the screen?

It happens both docked and undocked . Dock brightness buttons do nothing.
I left the tablet alone for about twenty minutes and when I came back the screen was on. Brightness was at max. But again as soon as I touched the brightness controls no screen.
Sent from my DROIDX using XDA App

Actually (after wiping and restarting yet again) I found that even the dock brightness buttons cause the screen ti go blank.
Sent from my DROIDX using XDA App

Okay so after searching high and low for others with this issue i found two unresolved threads. It seems to be a software problem that will not allow the backlight to go beyond 50% brightness when not plugged into the charger. I'm at work now so I can't test this for sure until I go home later this evening. If this is the case, then it could be a problem with my root and ROM installation. I will try the following things in order.
1. Restore from backup done right after I gained root access. This is basically my system with the original software. After gaining root, I did delete some things through Titanium Backup that I felt were bloatware. This might have had something to do with it so restoring the original backup should return these things to their normal state. The only problem with this is that when I tried to restore from recovery, the MD5 checksum gave me an error. I have found a thread that allows you to override using ADB and will try once I get home.
2. Unroot completely and flash back to stock. It worked when I was unrooted and stock, so theoretically it should work again.
3. If the above two methods don't work, I'll just RMA it back to ASUS. I already called in and got an RMA number for the issue. At least by doing the above two things I can ready the tablet to be within warrany specs in case it's just a dud and needs to be replaced.
Will update with results.

Results
1. When plugged into the charger (with or without the dock) I can up my tablet to full brightness just as the other couple of threads I read stated. Even with brightness up at full and running on battery (blank screen) there is still HDMI out. Wish I had realized this BEFORE I did a complete data wipe.
2. Had to use terminal emulator and the following link to recover the CWM backup with the checksum error: http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/70519-md5-sum-mismatch.html
It worked awesomely to bring my precious tablet back to stock with all applications I ran previously. Still no change in the brightness issue though
Now on to try to unroot and see what I get...

sounds like you're taking the right steps.

I hope so Malandro2011.
Looks like I will have to RMA after all. I unrooted, went back to stock recovery and a completely new install of the most current firmware. No dice. The issue is still there.
My tablet's all packed up and ready to ship off to the god awful Texas facility for repair/replacement. Since they sent my dock back with a bend in the metal near the adapter port, I made sure to take pictures of the entire tablet before replacement as well as leaving a note to them under the RMA slip about the condition of the tablet when I shipped.
My biggest question is what triggered this to happen. Was it rooting and installing a new ROM? So many people have done this without incident it is hard to believe this was the problem. Was it whatever changes they made to my dock? I was running smoothly for a week before charging it in the dock overnight.

many people have rooted and your the first I've heard with this particular issue so i doubt these roms caused it...but could be wrong.
Seems power related since adjusting the brightness sends more power to the screen or less then the screen fails.
I reckon its just faulty...
I wonder if they'll replace it with the newer models that cant be rooted yet..

Yeah, I agree it seems power related. My unsubstantiated theory is that when they adjusted the I/O board in the dock, perhaps it changed some of the power settings and caused some sort of overload/short in my tablet when I used the dock.
Such a shame to send it back. It was one of the earliest models and beyond this was one with the fewest problems. No light bleed, no stuck pixels, no sleep of death, good QC on the hardware. Here's hoping that what I receive back will be just as good (and hopefully not one of the unrootable new models).

Update for anyone following this thread. Received my repaired TF two days ago. Total away time was around 2weeks. It looks like hey had to replace the entire screen. Looks nice with even less lightbleed than before but the screen has a faint yellow tint that I have heard is common with later model TFs. Not sure if I should send back again as I really don't want it gone for any longer time...

[Q] Infinity Self Brick?

I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock

rock1324 said:
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
Click to expand...
Click to collapse
Update:
I can now rarely get it to vibrate for even a second holding the power for a long long time. Screen does not come on at all. Looks completely dead.

By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?

Thats OK said:
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Click to expand...
Click to collapse
I was hoping it wouldn't lead to something like this. I got my tablet from Amazon around the first week of september. I have treated it very well.
I'm not quite sure how it could have burned out, my brightness is usualy <50% and I have used the super IPS+ more less time than I can count
on one hand. If this is the case, Is it possible that a technical problem like this would still be repaired on warranty seeing as it has nothing to do
with the bootloader?
Also I'm not sure how this explain the constant vibrating that does not turn off untill the battery runs out. The way I see it is you could be right, the tablet is trying to tell me it's not going to work, or there is really some kind of software glitch.
Have you ever had LCD problems with a tablet? any idea how much this could cost?

rock1324 said:
Have you ever had LCD problems with a tablet? any idea how much this could cost?
Click to expand...
Click to collapse
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?

Thats OK said:
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Click to expand...
Click to collapse
Thanks for the advice, I have heard some terrifying stories of Asus customer support (never had a problem with them myself) and of devices just being completely lost in their care.
To answer your question, no the back lights are not visible at all. The only way I know the Infinity is somewhat alive is by the led coming on while charging and the somewhat random vibrating patterns that happen when trying to boot up.

Nexus 5 Screen Freeze

Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.

Something similar ....
I had a similar experience on the 15th .... took my N5 off the Qi charger and the screen froze when i tried to unlock it.
I hit the power button and was able to unlock and get a few touches in before it froze again.
I was finally able (after much screen off/on cycles) to get down to the developer options and turn on show touches & show cpu usage.
... background processes looked fairly normal when the screen was frozen(touches showed as frozen) ...
I was rooted, stock rom except for xda user Jishnu Sur's N5 camera mod and running a couple tried & true root apps(Stickmount & QuickBoot). Thought some software issue might be jamming up the digitizer i/o causing it to freeze.
Reverted entirely to stock (the Team Win recovery was also experiencing screen freeze - buttons worked fine) including removing TRWP and re-locking the boot loader!!
The screen freezing problem persists ... my conclusion is that it's a hardware issue. :crying:
It's possible you are seeing the same thing, but I haven't seen anything in the forums to indicate it's a widespread problem.
Returning it for a replacement phone ... :fingers-crossed:

Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.

biggiephat said:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Click to expand...
Click to collapse
Freezes tend to happen on custom kernels specially if you under-volt it too much. have you done that?

Screen Freeze
canaillou2k5 said:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
Click to expand...
Click to collapse
Last week I had the same problem with my new NEXUS 5. IT’S TOTALLY A HARDWARE ISSUE.
LG products are however not so bad in the JAPAN market but still we are expecting a lot from LG technology.

LG services suck.
I am facing the same problem with my Nexus 5. Unrooted, bought 7 months back from India itself, was working fine till around two weeks back,when the lags, screen freeze, blacking out n all appeared. Got it repaired twice at the LG centre. They changed the front display touchpad as well as the charging connector strip. The problem still persists.

[Q] Touchscreen Issues

I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.

This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.

I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet

I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.

I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:

I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet

Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.

There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.

2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.

So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk