Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
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.
Hey guys,
So before I had my HTC One, I stuck around for about 2 years with my HTC Thunderbolt and that was one of the influencing factors in my choosing an HTC device. However, there is a big difference that in some way, my Thunderbolt has the upper hand on.
On my Thunderbolt, recoveries and backups only took about 5 minutes tops whereas on my HTC One, both functions take about an hour. Is this normal? It took that long when I originally made my first stock backup before root and even now while running the latest versions of both CWR and TWRP.
Is this hour duration normal? How long does it take for you guys?
none
Mine takes about 2-3 minutes usually. It would take someone with more knowledge than I to tell you why it's taking so long, but what your experiencing I wouldn't think is normal.
Sorry I can't help more
Yea, mine only takes 2-3 minutes as well...maybe 5 tops.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Depending on what I'm doing, I flashed back to my pre from back up and that took 5min. But if I need to flash one of my backups of either eclipse ge or vanir. Forget it it takes me an hour or an hour an a half ugh.
Depends on how many apps you have installed, call history size, text messages, everything that will write data will increase the size of your backups thus taking longer. From my personal experience using orange backup and Cwm is the fastest, takes about 10–15 minutes and I usually have a lot of apps installed.
Sent from the One and Only
For anyone who experiences long restores and backups in the future, here's what I did to bring back times back to "normal":
Factory reset via your current ROM.
Wipe data and cache in recovery.
Format SD Card in recovery.
Reflash ROM.
I probably should have done this as soon as I started experiencing these issues but it's all fixed now! Thanks everyone for letting me know that more than 15 minutes was off.
edit:
doublepost
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
You answered your own question. You need to try a factory reset. Problems happen when you upgrade to new software without wiping.
dschachm said:
You answered your own question. You need to try a factory reset. Problems happen when you upgrade to new software without wiping.
Click to expand...
Click to collapse
Dschachm is correct. Then if you root and install TWRP you can back it up with all of your apps and data. So if there is ever a problem again, just restore and done.
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
I've gotten the sprint yellow screen and nothing else.phone doesn't turn on? When I try turn it on after removing batteryou I get the android figure and phone turns off? How can I reboot or start the phone..?and can I save my contacts?
Ok, first time poster, so I hope I can explain this all the right way.
So I bought an ATT branded note4 outright, refurbished and unlocked so I could use it here in Australia.
It was working fine for about 8mths and until last month started to drop all signal and reboot, but when it would reboot it would still show no signal
and reboot again after about 2 minutes.
This process would take at times an hour or two to come right and return to normal with full signal. (This would happen daily)
While it was in this rebooting loop it would seem hotter in the top half of the screen, thinking it was a battery issue I bought another battery
and also tried my partners battery but was having the same issues regardless.
Thinking it might have been the firmware, I updated to the ATT 5.1.1 ROM, but now that 2minute window that I had before is now taken up by "Optimizing app # of 23"
and it gets to between app# 12/18 and then freezes and reboots into this crappy bootloop.
I have tried safe mode/recovery mode/removed sd card/factory reset/clear cahe.. EVERY combination you could think of,
but one thing I have noticed is that when in recovery mode it doesn't turn off after a couple of minutes, I can leave it on that menu for 20 minutes and it wont have an issue.
I've been told it could be anything from the motherboard packing it in, to a "virus"(?), to a corrupted EFS file.
Does anybody here have any clue or could point me in the right direction.
Thanks in advance
Anyone???
Boots1 said:
Anyone???
Click to expand...
Click to collapse
Try removing the sim and flashing with odin