(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
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
Hello. Today I tried to return to stock via flashing the factory image, but unfortunately I got stuck at the booting screen. It's doing nothing, I let it boot for a long time, still nothing. I wiped the cache partition, still nothing. I flashed the images (radio, recovey, boot, etc ,etc) several times and nothing seems to be working. What should I do?
This could be caused by a corrupt download. Try downloading it again. If you have got a slow or unstable internet connection ask a friend or somebody else to download it for you
experience7 said:
This could be caused by a corrupt download. Try downloading it again. If you have got a slow or unstable internet connection ask a friend or somebody else to download it for you
Click to expand...
Click to collapse
I'm downloading the files right now, hopefully it will work.
UPDATE: It worked, thank you!
Nice to hear
You're welcome to press the thanks button as well Not just in this case but always when a comment is valuable and helps you