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.
Related
Ok maybe you guys can help. I'm having the strangest problem.
I'm running cyanogenmod nightly 151 and last night I was using the torch widget on bright for a little while and the battery died. Charged it back up and when I unplugged it in the morning it rebooted to white htc logo screen. Booted up normally and as soon as screen times out it reboots again. It did this a number of times so I Did a complete wipe and installed an older nightly, same issue. Full wipe and installed a stable rom, same thing. Then I noticed when I leave it on the charger I don't have the rebooting problem, only on battery power, so I replaced the battery. Same issue. Then I noticed that if I constantly use the phone it doesn't reboot. Only when the screen times out. Set the time out to 30 mins and left it idle. 30 mins later it rebooted. Turned off the "screen off animation" thinking that was the problem, no luck. Flashed back to stock official tmobile rom, same issue! Tmobile is sending me out a new phone and battery but just for curiosity sake and so it doesn't happen again, any ideas on what it could be? Definately gonna avoid that torch widget in the future! Thumbs up to tmobile customer service for their no haggle "overnight me a phone for 5 bux" customer service!
To sum it up, when phone is on charger no problems. When phone is running on battery, anytime the screen goes out, either by hitting power button or by it timing out, it instantly reboots to htc logo.
chrisconley1 said:
To sum it up, when phone is on charger no problems. When phone is running on battery, anytime the screen goes out, either by hitting power button or by it timing out, it instantly reboots to htc logo.
Click to expand...
Click to collapse
Flash a fresh version..or a stable one.
Sent from my HTC Desire Z using XDA Premium App
Yea I flashed 5 different ones, first I flashed back to the previous release that included a different kernel, then the stable rc1, then the stable before that, then I flashed the stock rom with root. There's nothing on my phone now except stock software and root. As soon as I hit the button to turn the screen off it reboots. The real question is what exactly happens when the screen goes off that the phone isn't liking? Its speedy and everythng works great for as long as the screen remains on. Its gotta be a hardware issue if I've tried so many different roms right? Or is there some core piece of software that nightly 151 changed that none of the other roms I'm flashing are changing?
Update: if I have music or navigation on and I turn the screen off the phone doesn't reboot until the song ends or route ends! Lol wth is up with this? It only reboots on idle? Maybe processor drops too low?
Update. Phone stopped rebooting every time the "screen goes off / all processes stopped" and now only does it very randomly, almost hardly ever. Its like its repairing itself lol. Htc cyborg! New phone should be here tomorrow. I was really hoping to figure this out though. Oh well
Last night I had dropped my phone from about a foot on a sitting-swing and it hit the ground. I have the black case from the sprint store on it. After that I attempted to turn it on and it just got stuck on Samsung loading screen with the genocide 2.0 logo below it, it then proceeded to be stuck there and eventually rebooted, this never seemed to end. When I attempted to plug it in to charge it the battery charging icon appeared but just has the loading symbol inside of it frozen, after many battery pulls and attempted clockwork-recovery boots failing I decided to go to bed. When I awake I went and tried to turn on my phone which immediately booted up into clockwork recover, fearing for my phones safety I backed everything up on it and then rebooted it. It seemed to work fine! It came on flawlessly and worked well. Throughout the day the battery seemed to drain extremely fast and then eventually died, having just gotten home I have found that the same thing is happening and it won't even charge.
Re flash the ROM then flash journaling on zip right after you flash the ROM then re boot & download you're apps fresh cuz you're data might be corrupted! Hit the thanks button if I've helped in any way! ;-)
Sent from my SPH-D700 using xda premium
I flashed back to stock rom to see if it would turn on, same thing happens, and I don't know if this is significant or not but when my phone boots up the buttons light up, then turn off, then back on again and stay on until the phone reboots itself or the battery is pulled.
EDIT: I have a strong feeling it's my physical battery that is causing the issues because it was working completely fine earlier yesterday.
Try booting in safe mode by holding power and the physical menu button until the phone gets to the lockscreen... Im curious to see if it helps because safe mode might help us get out of soft bricks? I wanna test this theory...
No it does not work, just get stuck at the Samsung loading screen. I don't honestly believe this is a software brick either because of the way it's acting, as I said in my above post I believe it's the physical battery and will probably be going to get it replaced soon
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
I run a M.O.A.R. stock 4.2 rom on my Sprint GS3 SPH-L710 (that is out of warranty). Yesterday, I was scrolling through facebook when my phone spontaneously rebooted. It didn't lag, or slow, or start to not respond. I was scrolling through my feed, and suddenly it was going through the boot screens. Except it wasn't just a reboot, it went into a boot loop.
I let it reboot maybe four or five times before pulling the battery. After a few minutes, I started it up again and it was fine. It operated normally for the next couple of hours until I felt it vibrate in my pocket, and when I pulled it out I found it had went into a boot loop again. Once again, I pulled the battery.
But this time, the phone wouldn't power up. I couldn't get it to power up, go into recovery mode, download, anything. Every button combination I tried produced no response. I tried using a different battery, didn't work. I tried charging my phone for a few hours (even though my phone was >75% when this happened) and even the battery indicator screen didn't show when I pressed the home button.
I searched for possible fixes, but I couldn't find any post or thread that was similar enough to the situation I'm in. I'm 99% sure it's not Sudden Death Syndrome, and that's about all I've found.
Anyway, I need help. What can I do (if anything) to make my phone work again?
sircharlieg said:
I run a M.O.A.R. stock 4.2 rom on my Sprint GS3 SPH-L710 (that is out of warranty). Yesterday, I was scrolling through facebook when my phone spontaneously rebooted. It didn't lag, or slow, or start to not respond. I was scrolling through my feed, and suddenly it was going through the boot screens. Except it wasn't just a reboot, it went into a boot loop.
I let it reboot maybe four or five times before pulling the battery. After a few minutes, I started it up again and it was fine. It operated normally for the next couple of hours until I felt it vibrate in my pocket, and when I pulled it out I found it had went into a boot loop again. Once again, I pulled the battery.
But this time, the phone wouldn't power up. I couldn't get it to power up, go into recovery mode, download, anything. Every button combination I tried produced no response. I tried using a different battery, didn't work. I tried charging my phone for a few hours (even though my phone was >75% when this happened) and even the battery indicator screen didn't show when I pressed the home button.
I searched for possible fixes, but I couldn't find any post or thread that was similar enough to the situation I'm in. I'm 99% sure it's not Sudden Death Syndrome, and that's about all I've found.
Anyway, I need help. What can I do (if anything) to make my phone work again?
Click to expand...
Click to collapse
Sounds like SDS, HERES a solution, or if your comfortable soldering, HERE
Follow this guide with the unbrick image pitched in the OP:
http://forum.xda-developers.com/showthread.php?t=2369125
joeyhdownsouth said:
Sounds like SDS, HERES a solution, or if your comfortable soldering, HERE
Click to expand...
Click to collapse
It was my understanding about SDS (and please, by all means correct me if I'm wrong) that a) it only affected phones with firmware below 4.1.2 (and that 4.1.2 and 4.2 had a patch to fix SDS) and b) and it only affected international models, i.e. i9300.
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.