Related
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
this is why you make nandroid backups
If you do happen to have a recent nandroid backup you might wanna restore to that, otherwise the only other other option I can suggest which may still not work but it's worth a try...
recovery > wipe cache > wipe dalvich cache > flash the same warm 2.2 zip you are running and do not flash the custom kernel just yet, see it that gets you to boot
colindelong said:
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
Click to expand...
Click to collapse
I would suggest wiping cache and dalvik cache and trying to boot up the phone again. I have ran into this a few times using the fastboot option, otherwise never had the problem.
Hello, everyone, this is my first post here, and after doing much research on my problem, I haven't had much insight into solving my problem permanently. tl;dr version is at the last paragraph.
First off, I installed AOKP on my phone for the first time a couple months ago and I had no problems for two months for reboots or anything like that, and I believe my phone was overclocked to 1520 mhz on the SmartReflex voltage settings. I did not undervolt whatsoever. In this phase, whenever I would turn it on, I would get to the boot animation, then the animation would hang, and the screen would rise to the highest brightness, flicker, and reboot, or shut down.
Then, in my troubleshooting, being the idiot I was, I accidentally unplugged it while I was flashing back to stock using ODIN. I got the "Android triangle computer" A.K.A. the "Soft Brick" signal. If I booted it normally, into my recovery, ODIN mode, whatever, I would get the same signal.
So, I left my phone alone for a couple weeks, accepting failure. Two weeks ago, I rebooted again into Odin mode, and I saw that Odin on my PC still recognized it, so I connected it and reflashed the stock ICS rom. I re-rooted and installed AOKP, all was fine for two/three days.
After that, the reboots started to happen again, and after a week of constant rebooting, and restoring latest backups,I set the CPU back to normal with no overclocking. I also undervolted but left "Set On Boot" unchecked for everything, This seemed to work fine for normal use, but I still had the phone on "InteractiveX" as the governor. So, when I would go to sleep, I would wake up and the phone would not be on. I would have to battery pull, reboot, etc. I thought this had something to do with one of the cores being turned off when the screen is, so I changed the governor to "Interactive" and the phone would charge now the same.
Now, the problem is, yesterday, I was fiddling with some benchmarks and I OC'd to 1520 for fun, and the phone screen froze, rose to the highest brightness, and shut down. I didn't have it "set to boot" so I thought everything should be fine, so I rebooted and the same thing happened at the boot animation which happened to me when I OC'd. I restored a Nandroid Backup I had before I set it to 1520, and still, no dice.
I reflashed my recovery then, because sometimes it would just freeze at the Google logo and not boot into recovery at all. Then, I restored my Nandroid again, and it booted into Android. After a few minutes, it crashed with the same "High Brightness, Screen Flicker". I restored again, and this time, I rushed into the "Performance Tab" and set my undervolt settings. The phone worked smoothly until I turned the screen off, and then I got the "Screen of Death". Basically, the screen stayed black, but the notification light was still on, and there was no response. So I pulled my battery and tried to reboot, but at the boot animation, the Nexus logo goes into "High Brightness, Screen Flicker". So, I took the battery out, and the phone is just sitting here now for fifteen or so minutes while I typed this out.
My question is, has anyone been having these same issues with their GNex. Because at this moment, I'm thinking I caused a hardware defect for running on 1520 for so long previously and I fried some inner components. Any help?
Edit: I put the battery back in and still the same thing. Going to charge overnight and let it sit, but if anyone has any help, please come forward.
Bump
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Sorry
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
First post here, didn't know much about rules. Thanks for the response. My Nexus did come back, just about 5 minutes ago. I'm going to stay on AOKP for a day and if I don't encounter any problems, I'll stay on it. If I do, I'll revert back to stock.
So yeah, **** this
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
It was working fine until I got 3 or 4 Sleeps of Death a day until today. It just stopped working, and I restored my backup multiple times, but it would just hang at boot or bootloop. So I'm like **** this, so I flashed the stock image for 4.2.2 through Fastboot, and it still didn't boot, even after complete data wipe through the stock recovery. So, I thought it must be 4.2.2 that is doing this, so I installed the 4.1.1 and still the same result.
I'm so done with this thing, it's a hardware issue, total crap of a phone. If it is actually meant to be tinkered with and to be a "developer's phone" this crap wouldn't happen.
So I've had my GS3 since launch, about 14 months. Up until Monday, everything was working fine and I had been through a dozen ROMS. Sometimes things would get buggy, I'd flash a new ROM and it would all be great again.
On Tuesday I noticed that when I'd go to use my phone it would not wake up and need a hard reset. As I went through my day I noticed it would randomly freeze to black while being used and require a hard reset to get going again. It probably went through 20 random resets throughout the day until I had a chance to flash a ROM in the evening, thinking everything would be fine.
Flashed the new ROM, noticed almost immediately the freezes were still going on, tried searching various forums for a fix and couldn't find anything that sounded like this problem. I did check through the Ultimate GS3 freezing thread and Ultimate GS3 Sudden Death threads, but neither seemed to have the same problem. Finally I decided to try the dummy file generator described in the freezing thread and after a while it gave a FC. I tried to run it again and it would not run properly, I cleared the data/cache for the program and was trying to try again when the phone froze for the last time.
It is now bricked, it will not hard reset, respond to battery pulls, respond when charging, boot to recovery, nothing. Can't be detected when plugged in to a computer and I will be taking it in today to see if it can be repaired out of warranty. I doubt anyone here can help with fixing the phone, I just thought I should post this so other people might find it if they suffer the same symptoms and can share similar experiences.
Hello,
So I bought a G3 the day before yesterday and yesterday was my first day with it, and for that first day my phone had shutdown twice on its own. The first time was when my phone was lying on the bed and doing nothing, it had around 50% battery and was not hot or anything.
The second time was this night i don't know when, i have put my G3 on the charger and went to sleep i woke up and it had shutdown.
I didn't made factory reset when i got i from the box which i will when i come home from work and hopefully this will fix it, but does anyone have a problem like that? If is something serious i will be disappointed to return the phone.
p.s. My previous phone was galaxy s2 and had this king of problem only with custom roms and kernels, but i have not put anything on the G3 yet, except activating the developers options and had switched it to ART and the first time the phone had shutdown i thought that the art was the issue and switched it back to dalvik, the second time though was on dalvik.
Dredd90 said:
Hello,
So I bought a G3 the day before yesterday and yesterday was my first day with it, and for that first day my phone had shutdown twice on its own. The first time was when my phone was lying on the bed and doing nothing, it had around 50% battery and was not hot or anything.
The second time was this night i don't know when, i have put my G3 on the charger and went to sleep i woke up and it had shutdown.
I didn't made factory reset when i got i from the box which i will when i come home from work and hopefully this will fix it, but does anyone have a problem like that? If is something serious i will be disappointed to return the phone.
p.s. My previous phone was galaxy s2 and had this king of problem only with custom roms and kernels, but i have not put anything on the G3 yet, except activating the developers options and had switched it to ART and the first time the phone had shutdown i thought that the art was the issue and switched it back to dalvik, the second time though was on dalvik.
Click to expand...
Click to collapse
I have the exact same problem. The past few days when I go to bed and wake up in the morning, the phone has shut itself off. I haven't rooted or installed any custom roms.
I would advise you both to take a factory reset, only install apps you need for a few days and see if the problem persists, if it doesn't install your apps back one by one as it may well be a particular app causing the reboots.
If you still get reboots after the reset and with no apps installed then you may have to take the phone back to swap it.
Lennyuk said:
I would advise you both to take a factory reset, only install apps you need for a few days and see if the problem persists, if it doesn't install your apps back one by one as it may well be a particular app causing the reboots.
If you still get reboots after the reset and with no apps installed then you may have to take the phone back to swap it.
Click to expand...
Click to collapse
Yes as I said in the first post the factory format and hard reset will be the first thing that will be done as soon I am at home. About the apps i have pretty much basic apps (facebook, messenger, soundcloud, etc) all from the market except smashhit of which i have the apk and installed from the internal memory.
Except those apps I have 2 mp3s and some wallpapers and nothing else, becouse when i got my phone it was late on the evening and i had no time to do anything else. So the phone is pretty much out off the box and I was verry frustrated when the secound shutdown happened, becouse i tought the first was from the ART runtime.
Anyway today I will have more time to spend on the phone and we will see what will happend.
p.s. The phone does not reboots, just shuts off.
Dredd90 said:
Yes as I said in the first post the factory format and hard reset will be the first thing that will be done as soon I am at home. About the apps i have pretty much basic apps (facebook, messenger, soundcloud, etc) all from the market except smashhit of which i have the apk and installed from the internal memory.
Except those apps I have 2 mp3s and some wallpapers and nothing else, becouse when i got my phone it was late on the evening and i had no time to do anything else. So the phone is pretty much out off the box and I was verry frustrated when the secound shutdown happened, becouse i tought the first was from the ART runtime.
Anyway today I will have more time to spend on the phone and we will see what will happend.
p.s. The phone does not reboots, just shuts off.
Click to expand...
Click to collapse
Is it definitely off or is the phone just stuck on a black screen? It is quite common on some devices when something is not quite right for the kernel to be unable to wake the phone up, the phone is still technically on but stuck in deep sleep.
does holding the power button for 2 seconds turn it on? or do you have to hold it for say 7-8 seconds?
Lennyuk said:
Is it definitely off or is the phone just stuck on a black screen? It is quite common on some devices when something is not quite right for the kernel to be unable to wake the phone up, the phone is still technically on but stuck in deep sleep.
does holding the power button for 2 seconds turn it on? or do you have to hold it for say 7-8 seconds?
Click to expand...
Click to collapse
It is definetly shut down around 2 seconds(the normal time to hold the power button to turn on) it turns on and work perfectly and does not show anything suspicious in its behavior, it's super fast, not laggy and etc, may be a little high on ram consumptions but with this havy skin i think it is normal or could not be normal idk, the ram consumptions go from about 1,2GB the lowest i have seen to up to 2,3 the highes i have seen.
Anyway about the shut off think yes defenetly 100% sure it is off, it happend again a while ago and i thoght the same thing may be it si deep asleep even i had chacked the weather 10 min ago and call myself from a friends phone and the operator said that the phone is off or i am somewhere without network covarage.
i got same problem. it turn off it selft and black screen even battery still 70%. rmust remove the battery to restart again, ealy bad. huft
mandrive said:
i got same problem. it turn off it selft and black screen even battery still 70%. rmust remove the battery to restart again, ealy bad. huft
Click to expand...
Click to collapse
If you have to remove the battery to get it to restart then its not actually shut off, its just stuck in deep sleep! which is usually caused by a bad app.
Yes if you have to remove the battery the problem is different, i just have to push the power button and it boots right away after it have shuted off by its self........
i didnt have this issue with my 855. but i did a factory reset after i got the phone just for the hell of it
So it's reset time i finally have some time to the some staff on the phone so hopefully everything will be fine. I will post if this fix or not the problem to inform the other people in this thread.
Dredd90 said:
So it's reset time i finally have some time to the some staff on the phone so hopefully everything will be fine. I will post if this fix or not the problem to inform the other people in this thread.
Click to expand...
Click to collapse
did you have any luck with the problem? I have the same issue, performed a factory reset and restored, hopefully it will fix too..
Hi all!
I have and have had the same problem and think I've pinpointed the problem to Google Search but can't 100% confirm it yet. I didn't do a factory reset when I got the phone and it shutdown during the night. I did a factory reset, made sure it got enough time to update everything properly. Problem was gone and worked fine. HOWEVER, the phone kept asking me which home screen I prefer at random times when I hit the home button. With random I mean like 4+ times per day. I searched the net and found a threat saying that a guy with a G2 solved the problem by removing Google Search updates. So I decided to do just that and get the factory version back and the questions disappeared but guess what, the phone shut down the following night.
Any takers or might this just be random? Note that it was working fine for three days with the updated Google Search and shutdown the first night after the downgrade.
So I did hard reset and so far so good the phone had not shutted down itself, and I updated everything which need to be updated (mentioning this for the guy with the upper post). So far so good I will keep you in touch if something goes bad...
Dredd90 said:
So I did hard reset and so far so good the phone had not shutted down itself, and I updated everything which need to be updated (mentioning this for the guy with the upper post). So far so good I will keep you in touch if something goes bad...
Click to expand...
Click to collapse
Let me know if you also encounter the problem with the home screen questions! :good:
Good luck!
mandrive said:
i got same problem. it turn off it selft and black screen even battery still 70%. rmust remove the battery to restart again, ealy bad. huft
Click to expand...
Click to collapse
Had you enabled ART instead of Dalvik ?
turt said:
Had you enabled ART instead of Dalvik ?
Click to expand...
Click to collapse
whether the use of ART
The problem will be resolved?
I suggest take it to your dealer and get it replaced asap. I've seen lots of returned phones(my job at XXXXXXX company ) with the same issue, and as long as the defect is reproducible the dealer will give you a new phone. If it's outa replacement period then they'll probably repair it.
aaaaaaaaaaaaaaaaaaaaand shut down again but this time it took quite a bit time longer to shut off by its self so i tought the problem was fixed, but it's not, so i am going to the store which i buy it from to replace the device.....
Does this also happen with the korean models?
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.