[Q] My Nexus 7 just exploded. What do I do? - Nexus 7 Q&A, Help & Troubleshooting

Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert

Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app

I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app

The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?

Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195

BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert

Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.

BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert

Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.

It's 4 days old. Send it back as defective.

turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.

I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium

Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.

did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.

I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.

I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.

Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app

Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok

Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...

djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.

Related

My damn phone doesn't want to turn off while charging.

I just finished uninstalling everything on this phone thinking it was an app doing this. Tonight is the first I've noticed this.
Here's the scenario. Phone is on and plugged into charger in car. I have root and recovery. No problems with those installs. I try to shut off the phone and it goes like it did, then a few seconds after the charge light comes on when the phone is off, it boots into recovery by itself. I pulled the battery and no change. I turn the phone off while unplugged and it stays off. Keeping the phone off, I plug it into the charger and recovery boots up. This is the strangest friggin thing I've ever seen!
I'm going to ruu it when I get home shortly. I will see if it does it then. If okay then I will root it and see if it does it. If not then I will install recovery and see if it does it. I don't think it was doing this with root only but I will see when I get home.
If it turns out to be recovery, I can live without it for a while until a newer version comes out. I prefer rooted stock anyways. Anyone seen this? I doubt it.
Sent from my PG06100 using XDA App
Others were talking about having this issue, so it could very well be a preliminary issue with root on the shift
Sent from a truly Epic phone and a transparent XDA app
This is a known issue with CW recovery. I am thinking about learning how to make a recovery for us, as this really bothers me.
cloverdale said:
This is a known issue with CW recovery. I am thinking about learning how to make a recovery for us, as this really bothers me.
Click to expand...
Click to collapse
Please do! Mine boots into recovery anytime I plug the charger in while the phone's off.
^ Shift Faced
I ruu'd and rooted and will stay this way until things get ironed out.
jesusice said:
Please do! Mine boots into recovery anytime I plug the charger in while the phone's off.
^ Shift Faced
Click to expand...
Click to collapse
I am working on it, but since I know no java, it will take some time.
Finally got mine rooted today, ran into some weird issues, but haven't experienced this issue. I did run into some issues with it plugged in an booting the phone. It wouldn't boot when power was pressed. Charge light would also stay on after it was unplugged. Battery pull resolved my issue. Not the same I know but kinda quirky

Nexus 7 abnormal Shut down and screen flickr

Hi Geeks,
I think, I am having a weird problem with my Nexus7. Its been third time in a row that device gets shut down completely and abruptly at 10% remaining battery without any warnings ( The last warning that pops up is at 15% and then nothing.
When I turn it on while plugging in charger, it powers up and shows charging at 10% but as soon as I open any app, screen goes crazy like an old CRT television screen when no signal reception. Extreme flickr that can't even see anything. Also, no touch is responded I guess or don't know what happened on touch action. Then it shuts down again :[email protected]
If I left it charging for some time. It starts working fine till it goes down to 10% again.
Has anyone experienced the same or any suggestions to check before I contact support also, if device is rooted, do we get any support at all or not?
Device is rooted and boot loader unlocked.
So, before returning to Google I would need to restore the factory image on it. Can anyone please share the procedure to do that?
Thanks in advance for the help and looking forward to hear from you soonest.
Use the nexus toolkit, get stock recovery if you're on cwm or twrp. Then go to settings, security, factory restore (something like that).
Sent from my LG-P999 using xda app-developers app
I jst opened mine today and it did the same thing. Mine is not rooted so it is not the cause. At 10% bad CRT reception. I tried resetting the unit several time and noticed too that when the change is higher than 10% it goes back to work. I don't want the hassle of sending it back. If it happens, who should I call and how to send it back
perceptorz said:
Hi Geeks,
I think, I am having a weird problem with my Nexus7. Its been third time in a row that device gets shut down completely and abruptly at 10% remaining battery without any warnings ( The last warning that pops up is at 15% and then nothing.
When I turn it on while plugging in charger, it powers up and shows charging at 10% but as soon as I open any app, screen goes crazy like an old CRT television screen when no signal reception. Extreme flickr that can't even see anything. Also, no touch is responded I guess or don't know what happened on touch action. Then it shuts down again :[email protected]
If I left it charging for some time. It starts working fine till it goes down to 10% again.
Has anyone experienced the same or any suggestions to check before I contact support also, if device is rooted, do we get any support at all or not?
Device is rooted and boot loader unlocked.
So, before returning to Google I would need to restore the factory image on it. Can anyone please share the procedure to do that?
Thanks in advance for the help and looking forward to hear from you soonest.
Click to expand...
Click to collapse
Try wug's toolkit and for oem locking procedure, you can follow this youtube link http://www.youtube.com/watch?v=_uMdtjUh6Co&feature=relmfu :fingers-crossed:
redmonke255 said:
Use the nexus toolkit, get stock recovery if you're on cwm or twrp. Then go to settings, security, factory restore (something like that).
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. Used Nexus Toolkit and it was breeze
fpaquin said:
I jst opened mine today and it did the same thing. Mine is not rooted so it is not the cause. At 10% bad CRT reception. I tried resetting the unit several time and noticed too that when the change is higher than 10% it goes back to work. I don't want the hassle of sending it back. If it happens, who should I call and how to send it back
Click to expand...
Click to collapse
Unfortunately my friend, I have no good news for you too I had chat with the Google Play support and they asked me to do factory reset claiming 90% of the time the issue is resolved. I performed as they said and waited for battery to drain to 10% and as soon as it hit 10%, the device shut down itself and then bad CRT. I gave them a call and they simply asked to return it. They sent me couple of emails, one for replacement order and other for logistics like UPS shipping label.
They sent me a new unit in 3-4 days and I am yet to return the old one, making sure nothing is wrong with the new one too. Its working fine so I will ship the old one back.
I am afraid, you will have to send it back too The number to reach them is: +1-855-83-63987

[Q] Nexus 4 randomly turning off, intermittently not being able to restart

Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.

[Q] Nexus 4 shuts down right after boot every time!

Hi,
I don´t know what to do. I got my phone 2 days ago. All fine. Rooted right away and used only adfree and titanium backup to restore apps.
Today out of the blue my phone shuts down. When I reboot it shuts down again right after Android booted up. Every time!
Can´t use it at all!
Tried reflashin factory und relocking but still it shuts of right after start of Android. I can get to bootloader and wipe in recovery all day. That works but as soon as android boots up it shuts down again once you reach the lockscreen.
Guess my phone has a failure but I wanted to ask here first before returning it.
And honestly I did not do something kernel or rom or OC.
Can't tell you on the N4, but my vivid, anytime it started to do what you're describing, I had to re-flash the boot.img and reinstall the ROM to stop the boot loops.
Sent from my Nexus 4 using xda premium
I already did a factory reste via image flash. Still no good. Once you reach the lockscreen it shuts down "powering off"
temperature issue?, there must be some hardware fault that's forcing it to shutdown after all services are loaded or a issue with battery stats.I would restore it and rma, or somehow drain the battery then recharge it
republicano said:
temperature issue?, there must be some hardware fault that's forcing it to shutdown after all services are loaded or a issue with battery stats.I would restore it and rma, or somehow drain the battery then recharge it
Click to expand...
Click to collapse
Mine is doing the exact same thing. I have returned it to bone stock but no change. Will try to drain the battery but it might take days with just the recovery /bootloader screen on!
OP: were you able to fix yours?
instigator008 said:
Mine is doing the exact same thing. I have returned it to bone stock but no change. Will try to drain the battery but it might take days with just the recovery /bootloader screen on!
OP: were you able to fix yours?
Click to expand...
Click to collapse
Hi,
I did the same.....drained battery but afterwards it would not charge again all i got was a red LED and no hint to fix it helped me. Phone is completely dead.
I already ordered a replacement unit and am still waiting for it
Same deal with mine. It worked fine for 6 weeks, it was completely stock the entire time. I have sent it away for RMA.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Also, when I told the CSR what it was doing they had absolutely no hesitation to process the RMA, they didn't even suggest a factory reset, I'm assuming this must be a known issue.
Same issue/ diff reason
I have the same issue with starting up the phone and automatic shut down.
I dropped mine in the water, however. Nothing seems to be wrong with it other than this auto shut down.. I was thinking that the battery was possibly fried. I ordered a new one to see if that would fix it.
Mine is also rooted too, however. This was the issue of the above original post. If there is a solution for either of my issues, I would greatly appreciate it.
thanks!
Pmarsh91 said:
I have the same issue with starting up the phone and automatic shut down.
I dropped mine in the water, however. Nothing seems to be wrong with it other than this auto shut down.. I was thinking that the battery was possibly fried. I ordered a new one to see if that would fix it.
Mine is also rooted too, however. This was the issue of the above original post. If there is a solution for either of my issues, I would greatly appreciate it.
thanks!
Click to expand...
Click to collapse
Hey dude this the new battery work? exactly the same issue here.
Nexus 4 shutdown after boot
Hey guys
I tried replacing the battery and the issue still persists and also tried a few different roms including stock but it does the same thing.
My N4 is not under warranty any more. Has anyone got this issue fixed...??

Running CM10.1 and my N7 will not keep a charge!

So I my Nexus 7 died the other day, but as I was buys I just put it on the charger and called it good. Then today I pulled it off the charger before going to work, and forgot it at home. Most of the time the damn Nexus will still be at 100% or 99% if its not touched all day.
So I have seen other people have this problem and there is the same way to fix it posted about a 10000 times all over the web, but its not working. I am hopping someone here has a better way, but dont want to try anything until I get some input on how to fix it.
If needed I can wipe it, I am able to boot in to the recovery and made a backup..
What happens when I power on the tablet?
It turns on, as soon as android is done it powers off.
Thanks for any help.
--------------
So I was able to get it going, after doing a backup I restored that back up and let it site for a little bit.. Now its charging like it should.
So the next question, other than not letting your N7 die, is there a way to stop this from happening again?
I'm not sure if there is any way to prevent this, but, you should be more specific about your problems with it not holding a charge next time, as, it sounded like you where talking about the battery percentage issues that CM10.1 in general is having. Also, please state your ROM next time, that could be critical to solving the problem.
Sent from my Nexus 7 using xda premium

Categories

Resources