Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Kal5el said:
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Click to expand...
Click to collapse
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Reason I say this is because the only three reasons I can think of are 1) app you have installed doesn't play nicely with stock Kitkat 2) something borked your EFS partition 3) your GPU is screwed.
thattypicalnerd said:
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Click to expand...
Click to collapse
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
"One of the good ones"? You clearly don't have "one of the good ones".
I think this doesn't have anything to do with anything you might have done wrong, I think the phone needs to be RMA...can you relock it?
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
HIGHLY doubt its a software issue at this point. Considering your phone is completely stock, the crashes are unrelated to the phone app, that takes out app interference/EFS issues. Also, considering it happens on first boot, 99.99% sure it's hardware. Relock and send it back to Google. If you really want to, try CWM and see if that does anything, but I doubt it. In my experience, CWM causes more trouble than TWRP. Computers are complex little devices, it could be a bad CPU that has a small sector of the transistors not working or something like that. Bad RAM even?
So you guys think it's a hardware issue? It's possible, I guess. But it started after TWRP messed up on wiping Dalvik, so I figured it was a partition problem. I can relock it, I'll just have to reset the tamper flag. Was really hoping this was a fixable software problem.
I think you don't have the latest TWRP, which causes some issues on cache partition, and takes ages to wipe
2.6.3.4 is the latest
I'm running 2.6.3.4 TWRP. Thanks for the suggestion though.
Okay, just posting the solution in case this happens to anyone else. Wiping in stock recovery, CWM, or TWRP didn't work. Fastboot erase, fastboot format, and fastboot oem lock/unlock didn't work. Factory images didn't work, with multiple downloads and md5 checking. What ended up somehow fixing it after trying everything I could think of was pretty simple.
In the Android OS, in settings, under backup and reset, I clicked reset. That's it. So far, graphical glitches gone. It's been almost 2 days, far longer than it's gone without a bootloop since it started these shenanigans.
No idea why recovery and fastboot and all that business didn't work. Just posting the solution for those who come after.
Funny thing is the reset in android settings uses recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know, I can't figure it out. It rebooted into recovery exactly like I had done before, and I watched the robot's polygon spin exactly like I had done 20 times. I can't explain why it worked.
Same thing that happened to me. What I finally got done to resolve it was:
1) Completely wiped the device and I mean all partitions so there is no OS and no internal files
2) Get the refresh zip file from Google to flash the device back to stock 4.4 while in the bootloader
3) Boot up, skip the setup, place CM11 files on the phone, then turn it off, reboot to bootloader
4) Flash CWM with fastboot
5) Boot to recovery
6) Do a factory reset
7) Wipe cache
8) Install CM11 & gapps
9) Wipe cache again
10) Reboot
So far for me no more issues. I did the same steps as you when mine started acting up. Now cache wipes super fast as expected no more reboots.
Sent from my Nexus 5 using xda app-developers app
I was wrong. The reset fixed it for 2 days or so, then it started showing the same problems. Graphical glitches and rebooting. I'm RMAing it. This thread can be ignored from now on. Further discussion of this particular problem can go in ssconceptz's thread linked below.
http://forum.xda-developers.com/showthread.php?t=2547863
That sucks. Mine works great now. I'll remove the first method.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:41 PM ---------- Previous post was at 11:41 PM ----------
Maybe you could try the method I show before RMA?
Sent from my Nexus 5 using xda app-developers app
So today my droid started messing up, home and recents button didnt work. Google play store and whatnot couldnt access data, the signal status bar at the top was just grey.
So i factory reset it. During the reset it just sat there on the little screen with the spinning hexball thing for like an hour so i shut the phone off. Now every time the phone boots it just tries to wipe it again unless i go into the boot menu and hit normal boot.
Running stock rom and whatnot, but im rooted.
I know that theres a flag somewhere that it reads on boot saying to wipe it, but dang if i know what to change.
Thanks in advance
Well i unrooted my phone and tried to let it redo the factory reset again, and it still just wont do anything.
jombo2323 said:
home and recents button didnt work
Click to expand...
Click to collapse
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
coolloser said:
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
Click to expand...
Click to collapse
I dont have a custom recovery or an unlocked bootloader.
I managed to get the problem sorted out through some unrooting and some non stock system file deletion. Installed safestrap and got blurry hd running on it now.
Thanks.
I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.
The inability to make write changes sounds like a bad NAND issue, you could try flashing with a .pit file but the phones internal memory could be physically damaged.
Andromendous said:
I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.
Click to expand...
Click to collapse
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.
Metabolic12 said:
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.
Click to expand...
Click to collapse
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!
Andromendous said:
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!
Click to expand...
Click to collapse
Whenever you flash back to stock or update a stock firmware through official means, it automatically boots into recovery and erases the system you have in place, very similar to TWRP. If you try to flash a stock firmware without erasing everything you will always run into some kind of incompatible memory error. The screen you're thinking of is just the stock recovery checking your system and OTA's for an official upgrade. Glad I could help man.
My stock Nexus 5 hardlocked today while attempting to connect to a wifi network. Upon restart, the boot-up animation took longer than usual, then displayed the 'Optimizing Apps' screen (which is not typical). It completed optimization on 5 apps, claimed to be starting Android, and then reset back to the boot-up animation, continuing the same cycle.
Unsuccessfully tried to boot into safe mode, although I can access Recovery Mode. Wiping system cache did not help. Installed ADB/Fastboot and sideloaded the original OTA without any improvement.
At this point, I'm hoping for either another path to get the device to boot or a way to extract some critical data (SMS, docs, etc.) off the device before doing a factory reset.
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
audit13 said:
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
Click to expand...
Click to collapse
Sadly no, fully stock phone.
Gave up and pulled the trigger on factory reset. We'll see if it helps.
On the plus side, this incident has motivated me to unlock and root my phone, hopefully expanding my options for the next time this happens.
Yup, an unlocked bootloader is definitely a plus in these situations.
I always unlock the bootloader unless it voids the warranty on the phone. Once the warranty is over, I unlock it if possible.
Factory reset seemed to work. Now unlocked and rooted!