Related
HELP,
yesterday, I was using my nexus 7 for normal use, wasn't playing game, just browsing with chrome. the battery was 8 percent when I last saw it. I then proceed to charge it, but the thing suddenly just shut down itself. I thought I misread the battery percentage, so I charge it anyway. about an hour later, i checked on my nexus 7, turn it on, got to the boot screen, got to the home screen, use it for about 15 minutes, and suddenly, the screen black out, it was flickering like crazy, and making some white noise ish sound. I panicked so I hold down the power button and turn it off. I turn it on again, and after about 30 seconds, the same thing happened again. I was using motley's kernel with 520 GPU, and I thought, maybe my nexus 7 cant handle the GPU OC. So I went to recovery, tried playing with recovery for about a minute or so, but the screen didn't flicker at all on the recovery. So I flashed the 484 GPU version of motley's kernel. When I reboot to system, the same thing happened again. So I thought, maybe if I restore to my old backup, it would not be like this any more. so I wipe the data, dalvik, and cache, and I restore my old backup. But the same thing happened again, only this time, after I turn it off, it make a high pitched sound.
I waited for about 6 hours, and now when I turn my nexus 7 on again, it works normally.
So, what has happened to my nexus 7?
bump
I'd say it is the overclock. Graphic cards do some weird stuff when overclocked. You can burn up your GPU doing that and cause it to forever freak out. I always shied away from GPU overclocks.
Sent from my Nexus 7 using xda premium
would that cause any permanent damage?
keni.mardira said:
would that cause any permanent damage?
Click to expand...
Click to collapse
It should be ok if you reflash back to stock rom to make all the hardware back to reset mode. A warning always given when we try to flash rom with oc created.
i also experienced this one, also received a battery warning and then suddenly screen went blank. then same weird thing happened as the one above. I'm on paranoid android rom and i'm quite sure it's not overclocked or something. Was only able to get back to normal by holding the power button for around 15-20 seconds...
Happens to me
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Same thing happened to me yesterday...
I got the "low battery" warning and after some time the screen started flickering in many colors and there was a weird static noise.
I pushed the on/off button, but it wouldn't turn on again. After a few minutes of charging, I could turn it on again.
This isn't normal behaviour, is it? Shouldn't the N7 perform a regular shut-down when the battery has no juice left?
I'm on the rooted stock rom btw.
androidswagz said:
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Click to expand...
Click to collapse
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Aditya88 said:
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Click to expand...
Click to collapse
I faced the same problem. I dont know when the battery might have drained out, but on starting the tab on low battery, it suddenly started showing black screen with little grains and suddenly stopped with a noise. I charged, started the tab again while charging, and the battery reading stuck at 21% even after charging for 20 mins. Within 5 mins, it happened again. Now after 35 mins of charging, I start it again, it boots normal, and now its reading the battery percentage in an incremental value (started with 22%) and now its again stuck at 23%
Is this a HW related issue? Or do you think it is more of SW related issue? If it is more towards the HW side, we better have it replaced. Mine is C70 model.
bump
just happened to me... it may have run out of juice... didn't turn on when I tried, so I guess it did... then I put it on the charger, tried booting it, went away for a sec and when I came back I also got this black screen with some flicker and a static noise...
will now try to charge it over night before trying again...
Nexus 7/Google problems
I received my Nexus 7 on Aug 21 after hearing the rave reviews. It didn't come with app for a camera, so I downloaded one.
The camera didn't work. I re-booted it & it worked this time. Downloaded Skype - whole reason for getting the tablet - to stay in touch with family that is far away. Tried to Skype - camera wouldn't work. Rebooted - worked this time again (getting tired of having to reboot for something I want to use to work). On Sept 2, sent message to Google inquiring about camera & app I downloaded. Only response - "thank you for contacting...blah, blah, blah - check out Q&A." All along, the tablet would shut itself down & reboot randomly (battery fully charged sometimes). On Sept 13, I shut it down & charged it. After a full charge, I tried to power it back on. Tried again several times that night & then the next morning. Called Google (who I bought it from). Told them I didn't want a piece of junk that wouldn't work. He told me it was past my remorse period. (The only remorse I have is buying their piece of crap instead of a reputable one.) I finally did get it to come back on, but camera hasn’t work since even after a complete factory reset. Any way – in order to get this one fixed, I have to “buy” a new one, then send back the old one & be reimbursed. Is this a legitimate business practice?
hi,
since today i have the same issue. did nothing special, just swichting from g currents to chrome. stock rom, no modifications, not rooted, everything original
n7 suddenly had a black screen(battery was at 28%). nothing worked, no powerswitch(10-30 secs). when connected to original power supply and cable, it boots up.. google logo .. glowing X.. lockscreen. then, approx. 30 sec later it turns off again(screen black). usb cable still connected. after some time it comes up again.. and repeats the procedure. after some cycles it stops, and when i reconnect the usb calbe it starts over again. sometimes, before it turns black, it shows a flickering screen and sometimes fizzling sound.
any suggestions?
I had this same issue right after the 4.2 ota update, after leaving it on charge overnight it seems fine now after a couple of discharge / charge cycles
Its like after the update it was over estimating the battery level
Sent from my Nexus 7 using xda premium
Same thing!
I have a completely stock Nexus 7, and the EXACT same problems are happening to me too! The first couple of times it happened my tablet would reboot normaly. But now, my tablet won't boot up at all. Any suggestions on what I should do? Also, remember, I have no mods installed.
Happening to me too.My N7 shut itself down because of low battery a couple hours ago and I haven't been able to get it to boot since. When I plug it into the charger it shows a flickering screen like a tv with no signal but with less white flickers. I've tried multiple chargers and cables but I could only get it to boot up a couple times and both times it did not show that it was charging even though it was plugged in and the battery was at 0% so as soon as it boots up it shuts itself down again because of low battery.
So now I've got it on the charger, screen all a'flicker, waiting for it to get a charge but I've got a feeling its not even charging because, like I said, the few times it has booted it showed the battery at 0% and not charging.
I guess I'll try to leave it alone for a while and see if it will start up after being plugged in for a bit.
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
devhen said:
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
Click to expand...
Click to collapse
Yup... I've let mine sit there turned off and charging over night... helped!
Just had a problem with the Nexus 7 not charging when battery was likely fully depleted. Putting a charge cable in was automatically booting the Nexus 7 up and wouldn't charge shutting down right after. Loops going on and off. What I did was plug a charge cable in and hold power+both volumes and now I believe I am charging at the bootloader screen. It stays on so I will leave it like this and if it doesn't resolve the issue I will try recovery once it is charged.
I've just started having the same issue. Has happened twice when battery gets to 8%, suddenly jumps to 0, shuts down, then after a few seconds restarts itself. Gets to home screen for a few seconds, battery showing 8, then jumps to zero, switches off and has flickering blocks on screen with static noise. This keeps repeating, only way I have found to solve it is to load into bootloader, then select power off. Device charges normally then and once charged works fine. I am unlocked and rooted but running stock 4.2.1, think I'll just have to return it for a warranty claim.
Based on what you experienced, the lesson here is your device can't handle the GPU over clock of more than 446mhz or it will do some crazy stuff.
Sent from my Nexus 7 using xda app-developers app
Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
edbr said:
Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
Click to expand...
Click to collapse
Probabily the rain damaged a part of your hardware. Did you solve?
If the battery is dead, the phone won't work.
The battery needs to have at least a bit of charge in order for the device to work, even if it is plugged in.
If the battery can't hold the charge, and the device uses more power than it gets, it turns off. I speak from experience.
These devices don't seem to work without a battery. Power goes to the battery, and the phone takes the power from there. Power doesn't go straight to the phone.
Anyway, I don't think a bit of light rain hurts the devices, especially if it was in your pocket. I walked through rain with my device in the pocket many times and no problem.
It looks to me that the hardware is failing. I don't believe that a faulty battery can cause a bootloop. I also don't believe that the power button causes a bootloop.
What I suggest would be:
1) Try going back to stock ROM.
2) Maybe try to get an S4 with a broken screen and switch the motherboards.
Hello,
I received the YotaPhone 2 (YD206) today.
The box was sealed.
When I tried to turn on the phone, it didn't start. I thought it was empty so I put in on charger for 2 hrs.
After that I tried again , but still nothing happened -- i was holding power button multiple times, as long as 5 minutes at the time, but there was simply no response -- no vibration, no sound, screen remains black (not turned on), anything at all.
I tried different chargers as well (Xiaomi and Samsung one) -- they weren't working with this phone either.
When I connect phone to a PC, I just hear sound that something is connected (I saw installing drivers notice first time I connected it), but nothing happens at all. I don't see the phone in my computer or anywhere else.
Is there way I can fix this somehow? What else can I try?
Thanks!
You can try unlocking the bands like described here.
Not sure it will help but you can at least try.
http://4pda.ru/forum/index.php?s=&showtopic=550302&view=findpost&p=55303436
fly20 said:
Hello,
I received the YotaPhone 2 (YD206) from coolicool.com today.
The box was sealed.
When I tried to turn on the phone, it didn't start. I thought it was empty so I put in on charger for 2 hrs.
After that I tried again , but still nothing happened -- i was holding power button multiple times, as long as 5 minutes at the time, but there was simply no response -- no vibration, no sound, screen remains black (not turned on), anything at all.
I tried different chargers as well (Xiaomi and Samsung one) -- they weren't working with this phone either.
When I connect phone to a PC, I just hear sound that something is connected (I saw installing drivers notice first time I connected it), but nothing happens at all. I don't see the phone in my computer or anywhere else.
Is there way I can fix this somehow? What else can I try?
Thanks!
Click to expand...
Click to collapse
Sounds like the phone is defect. The only thing I can think of is that it somehow freezed up and you will need to let the battery drain so all power is off the phone and then try to recharge it. Draining the phone completly without screen use can take up to 7 days.
I finally managed to turn it on,by keeping it on charger for whole day and night and after a couple of attempts it was on.
I thought battery voltage was pretty low which prevented it from turning on.
I used a phone for a day, completely discharged it and then recharged it to 100% again. I thought everything is gonna be good now.
Then I wanted to upgrade to Lollipop, I decided to use YotaFlasher to flash EU KitKat first, and that worked fine. After that, I used OTA update to download Lolipop.
Download finished, and I was offered to "restart device and apply update", but as soon as I confirmed, the device went off and I can't turn it on anymore. What the heck is happening with this yotaphone? (battery was at 97%)
I can't turn it on, restart, put in download or recovery mode, get it to charge or get the screen on. Also PC don't recognize it *AT ALL* -- not even sound that something is connected. It looks completely dead (again).
Any ideas what I can do to fix my new problem?
So someone called me about 3 hours ago, and my phone just outright died. Couldn't turn it on - no signs of life, even though I had received a call just fine this morning, 2-3 hours before the random crash. Now I couldn't turn it on, and my first guess was that the battery was the culprit, though it was on charge through out the whole night.
So I pugged it into my powerbank, the phone turned on, but kept kinda bootlooping - where the "relock your bootloader pls" message would come up for half a second, followed by the phone restarting again to continue the cycle. This was without the battery charging animation - straight into booting.
After 20 or so tries to turn on it actually did, and I was able to discharge it past the point at which it crashed - most likely excluding the battery as the issue for now.
What could this be? Could it be a chip that's on its way out (as in about to brick my phone)? Anyone have any ideas as to why this is happening? Or maybe an app to check system stability / hardware test?
Edit: thanks to firefox, for saving the progress of this write up as my phone did the exact same thing after I locked it. My pebble watch vibrated to indicate that the connection is lost and I wasnt able to turn the screen on.
Had to plug the my 6P into my power bank again for it to turn on. Though it didn't do the glitchy bootloop this time.
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Ninety-9 SE-L said:
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Click to expand...
Click to collapse
Try to clean it out with the end of a safety pin
Sent from my LG-H918 using Tapatalk
I have a v20, and have the same issue, please help
Hello to all who view this,
I own an unlocked V-20 LG-H918 Its an unlocked T-Mobile variant that I use on Metro PCS, I have never had any issues, the phone works near perfectly.
I have a couple batteries which I switch out periodically, I just decided to switch to my backup battery to ensure that it was still okay, and charged... the phone refused to start, once I placed the new battery into it, instead it went to the "firmware updating screen waiting for a connection"
I was able to get the phone to start by pulling the battery and then plugging it into the wall PRIOR to starting it, and it started fine. however there is a reason I still use this outdated phone. I ENJOY IT. I would hate to end up replacing it, so i would like to know if there is a fix for this issue yet.
*for the record* I have not been able to ROOT this phone, I gave up about 10 months ago, and have had no issues, though as said I was unable to gain root acccess