My N7 was flawless until some days ago.
Usually to turn on, I had to press the power button for 4s and it would turn on, never ever failed. Also on the boot sequence (the X of nexus), it took relatively low time, even when I had all of my currents apps installed (nothing changed).
For the last days, it's happening that sometimes the device doesn't wake up after pressing the button. I've checked and I have to press it for 20-25s in order to see the "Google" logo and have it start booting.
Also, the nexus "X" boot animation also randomly takes like 4x longer, and it seems to not have any relation with the 20s pressing issue, since it happened me both with the 4s and 20s pressing power-on times.
But both of those issues came together.
Anyone else with the same issue? Would a factory reset solve the problem?
Thank you in advance.
RusherDude said:
My N7 was flawless until some days ago.
Usually to turn on, I had to press the power button for 4s and it would turn on, never ever failed. Also on the boot sequence (the X of nexus), it took relatively low time, even when I had all of my currents apps installed (nothing changed).
For the last days, it's happening that sometimes the device doesn't wake up after pressing the button. I've checked and I have to press it for 20-25s in order to see the "Google" logo and have it start booting.
Also, the nexus "X" boot animation also randomly takes like 4x longer, and it seems to not have any relation with the 20s pressing issue, since it happened me both with the 4s and 20s pressing power-on times.
But both of those issues came together.
Anyone else with the same issue? Would a factory reset solve the problem?
Thank you in advance.
Click to expand...
Click to collapse
How much memory is free on your N7? I've seen posts from people who have had similar issues when they came close to filling up the memory on their N7.
Sent from my Paranoid Nexus 7
RockNrolling said:
How much memory is free on your N7? I've seen posts from people who have had similar issues when they came close to filling up the memory on their N7.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
16 GB model, more than 6GB left.
It has been like that for the last 2 weeks.
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.
I have had a nexus 4 for a while, and I rooted it about 2-3 months ago, but today for absolutely no reason, it won't turn on (please note it was fully charged when I left it). I have tried to leave it plugged in for a while, and after I tried turning it on nothing happened. When I connected it to my computer it showed up as QHSUB_DLOAD. I don't have any custom rom or kernel, all I have is an unlocked bootloade on my rooted nexus 4. I tried holding the power button for over 30 seconds (it was suggested on another post here at XDA) and it still wouldn't do anything. Please help me, I have no idea what happened or how to fix this.
PROBLEM FIXED!
jonapunk sent me a message with a simple procedure to solve this:
"Try volume up and power for 20 sec. Then press power button one more time"
I have put his message up for everyone to see in case they encounter the same issue.
Android 9000 said:
I have had a nexus 4 for a while, and I rooted it about 2-3 months ago, but today for absolutely no reason, it won't turn on (please note it was fully charged when I left it). I have tried to leave it plugged in for a while, and after I tried turning it on nothing happened. When I connected it to my computer it showed up as QHSUB_DLOAD. I don't have any custom rom or kernel, all I have is an unlocked bootloade on my rooted nexus 4. I tried holding the power button for over 30 seconds (it was suggested on another post here at XDA) and it still wouldn't do anything. Please help me, I have no idea what happened or how to fix this.
Click to expand...
Click to collapse
There are several threads already dealing with this.
Got a new replacement Nexus 4 from google today and turned on phone and the colours were all fuzzy. After turning screen off, it doesnt turn on. Doesnt go into bootloader mode. Tried all the button combinations also.
I have had this phone for months. Installed TWRP 2.6.3.4 and CM11 Official. Recently the phone has SOD, and when i hard reboot (hold power button), the screen stays black. I have to reboot multiple times, and sometime plug in the power to get it to come back. Also, after it finally comes back, the video will glitch for awhile and the be fine until the next SOD. Anyone heard of something like this? Thinking I should go back to completely stock and see if it continues.
so last night my phone randomly froze and rebooted into the command page with the little android guy saying no command. So I had to reboot system and all is well. anyone have this happen to them?
That sounds like you booted into recovery mode. Not sure if this can be done with a button combo or not. If you were able to boot fine, it should be nothing to worry about.
I believe once you see "no command" you can hold power button and tap VOL UP then release both buttons and you will see some options, one of them being reboot, which will go back into normal Android.
Yeah it was recovery mode and it did it all by itself which was weird but no its fine and I got the security update seems even smoother if that was possible
This just happened to my phone at the beginning of a phone call! I didn't know what to do, so I just held the power button down a for a few long presses and fortunately it rebooted. Seems OK now, but leaves me a little worried!
Sent from my Nexus 6P using Tapatalk