Database Info

HTC stuck on splash screen

Im really hoping someone can help me please...
ever since viper 1.6.x sometimes my phone will shut down, or if my phone battery runs completely dead of battery, and then when i try and turn the phone on again it will go into a boot loop where is gets stuck on the senasation splash screen...
can someone tell me why this is happening and how i can turn my phone back on after this happens...?
info
i am on vipers had this problem since 1.5.x - 1.6.x with multiple kernels, but the last kernel i was on when this happen was faux 10b9
this most often happens when the battery run completely dead, but has occasionally happened on a random reboot swell
things i have tried...
pulled battery...
clearing dalvik and cache - this will get me past the splash screen once, to the android is upgrading page (as i have cleared dalvik and cache) only to reboot at the end and finally get stuck on the htc sensation splash screen again
formated system
installed the rom again with the restore option (the last of the 3 options stating to use it if you have a corrupt operating system)
reflash the kernel
install same rom without wiping
the only thing i know i can do and that ail work is going back and restore an old backup via 4EXT but i no longer have any back ups (dont ask why i did this! i thought it was working now!)
is my only option a full format?
why is this happening?
anyone know a way around it?
does this mean i can never go back to ViperS as i will always have this problem or is the problem from somewhere else??
thanks so much in advance...

i suggest to format all partitions except sdcard
flash viperS rom
see then if your issue exists
otherwise try different rom
also if you are S-ON enable smartflash from 4ext before flashing the rom

[Solved] try this if you're stuck at the boot loading screen

While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:

Freezing/bootloop even after stock RUU

Hello,
I'm running out of ideas to solve my problem with my Sensation, maybe you can help. I was on my beloved ViperS5 ROM and it crashed while browsing due to memory overload or something. After several boot attempts and removing the battery I managed at least to get into bootloader/recovery (ended up with a black screen or freeze 8/10 times). Reinstalled the ROM and it kept crashing at the configuration screen, resulting in a boot loop. So I tried a few other ROM's, exactly the same results.
My last hope was going back to stock using RUU, same problem at the configuration screen, but I managed to boot after few reboots. The phone still crashes after few minutes, when I try to start any app, resulting in a boot loop/black screen/HTC logo freeze. (tried to remove the SD card, it didn't help)
Any ideas how to fix this?

did you leave the device switched off for a long time?
if not do it and then try to switch it on
probably it is still overheated when you are trying to boot it
leave it for 10-15 minutes
best wishes

Maybe it's really damaged from overheat, cause it even crashed in recovery once, so I guess I'm ****ed. I will try to leave it switched off for a few hours, but I doubt it will help. Thanks so far.

Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.

frgntz said:
Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.
Click to expand...
Click to collapse
If memory serves correctly you should be able to get a logcat from the phone while its in recovery. it might shed come light on what is producing the failures, but its definitely sounding like a hardware failure. Were you overclocked?

How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .

How is your sensation going on?
frgntz said:
How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .
Click to expand...
Click to collapse
hello, may i know how is your sensation device condition? recently my device having the same issue as yours and out of idea to solve it. before i send device to repair i hope can get some other solution which i miss. thanks in advance if able to provide further infomation.

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM
My Nexus 5 is having a problem that is just confusing the hell out of me.
To summarize the issue...
1. Phone will get stuck on "Google" splash screen (written in white) on bootup.
-at this point, I can reach bootloader and recovery
-clear cache/format cache does not alleviate problem
-factory reset does not alleviate problem
-fastboot flash-all does not normally alleviate problem
-only flashing a ROM via TWRP works
2. ROM flashed via TWRP, things work like normal for ~4-24 hours. At some point, there will be a random reboot. Usually, this is while under stress (playing a game, updating apps). It will reboot normally and continue to work like normal for some time. But it's a ticking time bomb. There will be another random reboot at some point, often while idle - definitely not workload-related. This second one will get me stuck on the Google splash screen again, with the only way of fixing being re-flashing the ROM via TWRP.
These symptoms are basically the same regardless of the ROM - I've tried factory images, a stock-ish ROM with Gapps removed from XDA, and CyanogenMod. It seems like it could be a hardware problem, but I don't have a clue what it would be since it is so consistently fixable, albeit temporarily. Does anyone have any troubleshooting suggestions or a clue as to what part of the phone is likely failing?

Post logs.

Elluel said:
Post logs.
Click to expand...
Click to collapse
Okay, so this afternoon I went to check on it after spending some time on the charger. The LED was lit, so I thought things would be fine. It just wouldn't wake up. It wasn't responding to various button presses, but the LED turned off after I held the power button. It took a lot more attempts than normal to get to fastboot, but eventually got there. I used fastboot boot to get to TWRP and retrieved last_kmsg, kernel_log, and logcat. Logcast was empty. Here are pastebins for the other outputs.
last_kmsg: http://pastebin.com/z2KG2aHW
kernel_log_output: http://pastebin.com/v7TZZKeb
Thanks for the help!

I'm going to bump this one time, since there are now logs posted which I think might provide some clear insights to those who know how to interpret them.

Corrupt boot animation? (More information included)

Hello all, so after reading a post on how to change your boot animation on the Samsung Galaxy S6 (G920-F But applies to other variants)
I gave it a try, and I decided to use the method where you transfer three files to system\media. So I did, and upon restarting the phone, it wouldn't restart, but instead black out for a few seconds then go back to the lock screen. After this, I panicked (Thinking that I broke it) and reverted the old files to where they were (From a backup I made previous to changing it) and it still does not work. Is there something I can do without reinstalling the ROM (Which in question is the stock ROM) or a method without posing my data? If not, they'd be the last resort. I do have root access (Rooted with CF-AUTOROOT)
Side note: The exact same thing happens when you try shut it down as well, and the only way to shut it down is to use an app that executed a script to shut it down, or booting to the recovery and shutting it down from there. I'm using TWRP recovery. version 3.0.2-0-zerolte (That is the name of the TAR I used to flash)
I was thinking about this for a while and I have this question; Is there a way to log everything the phone does before running into errors, causing it to go back to the lock screen after restarting/shutting down?
If there is any other way to restore it or troubleshoot it, please tell me. I'm reinstalling the ROM as a last resort if anything else lets me down
Other than the boot animation errors I've been having, the phone has been working just fine. Just it boots up way faster then it is meant to do when powering on (No one's complaining about that)