Database Info

Bricked device?

Hi!
Here is what happened to my One S (S4 version, about 6 months old). I unlocked the bootloader when i got the phone, installed cwm, afterwards twrp (2.3.1) and was running several sense and non-sense roms without any issues. Till last week:
I installed "BAKED Black Bean" in twrp and was using it for a few days without issues. One night i wanted to turn on the flashlight to search for something on the floor, and BAM: phone restarted and got stuck in a bootloop. I tried to enter recovery, but still bootlooping. Reflashing twrp or cwm did not work either. Still couldn't enter recovery. Then i managed to enter twrp again by erasing the cache in fastboot (fastboot erase cache) but now external storage was unmountable.
Here is what i tried to recover the phone:
* relocked bootloader
* ran RUU (RUU_Ville_U_Vodafone_AT_1.78.169.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258382_signed.exe)
* cleared storage in hboot (this fixed the unmountable external storage)
* factory reset in hboot
Now the phone booted fine, external storage was working. BUT since then the phone is behaving strange. After a few hours it responds very laggish when i press the power button (takes up to 5 seconds for the screen to turn on, touch screen is irresponsive for a couple of seconds) and occasionally it reboots when i press the power button and is stuck in bootloop again. I already ran the RUU again, but still the same issues.
I'd really appreciate any ideas regarding this.

Hi, if you can, I'd try to start a logcat, then attempt to recreate the issue while it is running. Then post the logcat, and we might be able to see what's causing the sluggishness and random reboots.
Sent from my HTC One S using Tapatalk 2

thanks, i will post a logcat as soon as possible.
another thing i found out: when the phone is plugged in (charger or computer) it switches on normally. just when unplugged it's making troubles.
oh, and just to mention: i did not install anything on the phone. just the ruu, no apps nothing. just did the initial setup. so any 3rd party apps causing the problem can be ruled out.

sounds like you did a lot correctly
Are you wiping system as part of your wipes
You could try reformatting sdcard also
Get a nandroid and sdcard bu if opportunity presents itself

more issues:
- when opening the camera app, it takes 7-10 seconds until the picture shows up
- screen rotation is not working. when i try to calibrate the g-sensors they are not reacting at all
i think i will try my luck with warranty repair. what are my chances with an unlocked bootlader?

kabufzk said:
more issues:
- when opening the camera app, it takes 7-10 seconds until the picture shows up
- screen rotation is not working. when i try to calibrate the g-sensors they are not reacting at all
i think i will try my luck with warranty repair. what are my chances with an unlocked bootlader?
Click to expand...
Click to collapse
Have you done a logcat yet? You can try warranty, yes.

[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.

Z5 stuck in bootloop (100% stock firmware)

Over the weekend, my Z5's battery died. When I booted it back up, it started running dexopt which I found unusual. Once it completed and switched to "starting apps" the phone rebooted and began running dexopt again. The next time, I ran logcat and saw that com.sonymobile.wifi/.internal.SomcWifiService was ANRing at the end of starting apps which caused the phone to reboot. Any ideas how I can fix this?
This is one of the first phones I've used that is 100% stock firmware and not rooted or unlocked. Any ideas what may have caused this or how I can get out of the boot loop?
I tried running adb shell svc wifi disable as a last resort but it didn't fix it.
EDIT: I've created a gist with the logcat during dexopt and leading up to the crash here: gist.github.com/gpeal/d580d12c8f8f01569128

Try to repair your phone with pc companion,or remove sd card if you have one and try without it.

Update: I was somehow able to get it to boot in to safe mode while trying to do the 3 finger salute to get it into recovery mode. After it booted into safe mode, I had it forget all wifi networks (hoping that it may have caused the wifi anr). I rebooted after that and it booted back up normally. I still have no idea what caused the ANR though.

goorioles747 said:
Update: I was somehow able to get it to boot in to safe mode while trying to do the 3 finger salute to get it into recovery mode. After it booted into safe mode, I had it forget all wifi networks (hoping that it may have caused the wifi anr). I rebooted after that and it booted back up normally. I still have no idea what caused the ANR though.
Click to expand...
Click to collapse
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated

TaZ4444 said:
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated
Click to expand...
Click to collapse
Turn the phone on and directly press volume down and keep it pressed till the phone boot will take you to safe mode.

TaZ4444 said:
How did you get the phone to boot into safe mode?
Mine is stuck showing "Optimising application 1 of 76" and I have to let the battery run out before I can charge it and try again. Sometimes it gets through all 76 and then says "Starting Android" and then just re-boots and it all starts again.
Plugging it into the PC doesn't seem to give any response either as the thing won't turn on so I can't run the PC repair option in PCC, any advice muchly appreciated
Click to expand...
Click to collapse
If you have adb setup, run logcat while the phone is optimizing. Let it continue running until the phone reboots. When it does, the adb connection will close and you'll be able to find the crash/ANR pretty close to the end of the log.

Thanks guys. I actually didn't need to do either of those things, I found a little reset switch next to the Sim card tray, pressed that and then it took twice as long as previous attempts to optimize the apps but then it booted up fine

Z5 SOV32 stucks in bootloop after phone restart
Hi, my phone Z5 SOV32 that 100% stockfirmware stucks in bootloop everytime i restart it ( it was normal before), then i have to repair it by using Xperia Companion many times. I created a logcat.txt file but i don't know how to analyze it, please help me.
This is the logcat link: mediafire.com/download/c5ap0zngixmo5ts/logcat.txt
Thanks.

Random bootloops and weird issues

Hi all!
My S7 is unrooted, completely stock, running latest 6.0.1 official update
Few days back I updated some apps from the play store and after that, my phone suddenly restarted on its own
This sudden restarting kept on increasing and currently the device boots up for a few seconds, and then freezes and restarts again
I know there's some faulty app that's causing the restarts, because once i managed to turn the UPSM on before the device restarted and it worked fine, with all the apps disabled
I have tried to get a logcat to look for the issue but I can't do that properly as I haven't taken any logcats before and i'm not familiar with the process
I have already tried to flash the stock firmware but that didn't help either
Is there any way or solution to get this fixed? Or can anyone here help me on how to get a logcat so that I can look for the error causing app?
There's a lot of stuff on my phone and I can't risk losing it by factory resetting it

I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.

munchy_cool said:
I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.
Click to expand...
Click to collapse
I've booted into safe mode as well, but that isn't helping either
The same keeps happening in same mode as well. The device boots up, and after some 30 seconds it freezes and restarts and gets stuck in a loop

Samsung Galaxy S7 Stuck on Samsung Galaxy Logo

Hello again Xda community I really need some advice here because I'm unfortunately having problems with my phone at first it was a problem with it randomly crashing. In order to address that problem I did the following things - I prevented all apps from running in the background, I set several apps to run on the low data usage setting, and I even cleared the SIM toolkit cache as well as the individual caches of apps that I regularly use but for some reason my phone was still crashing. After installing the latest update my phone was stuck in a boot loop, it's stopped doing that, but it's now stuck on the Samsung galaxy logo screen.

You may have to flash your phone with Odin to fix the issue if you're stuck on boot loop and can't get pass it.

beevme said:
You may have to flash your phone with Odin to fix the issue if you're stuck on boot loop and can't get pass it.
Click to expand...
Click to collapse
Well, I've managed to turn my phone on again by pressing the power button and the up button, but I'm still having the problem in regards to my phone constantly crashing. One thing that I forgot to mention in my original post is the fact I also removed a large number of files which I was no longer using. I backed these files up by transferring them to my external hard drive even after doing that my phone was still crashing from time to time.
I'm not 100% sure, but It might have something to do with all of the data being kept in my internal storage instead of my SD card which isn't recognised.