Database Users

[Q] Phone Bricked/Dead - Not even download mode

Hi ,
Am running PAC 4.4 ; My AT&T s4 is rooted. Everything was running fine except for the occasional bugs and restarts cause of them. But today suddenly, it just went fro sleep mode to off.When i turn it back on; just vibrates and displays the bootlogo and shuts off again. I will have to remove the battery and put it back in for it to start again
Tried going into download mode but it just shuts off when i make a choice of pressing the volume up to confirm , sometime after going into download mode.
It wont start with the usb connected. Any help is appreciated.Thanks

N-910C crashing after turning off screen

Hey,
I've been looking around here quite a while now to find a solution, but I can't find one. So that's why i made this post.
My N-910C was running Sweet Rom 17.1 and Googy Max Kernel, everything worked fine. But after 3 weeks my phone starts to crash immediately after locking my phone, or after it automatically turns its screen off.
I've tried flashing the stock rom, that didn't work, after flashing it's crashing when it says 'installing system update' and after a few times it says 'No command'. After that I flashed Googy Max Kernel back on my phone and it boots, but when my screen turns off my phone will crash again.. My options in recovery are limited due to the fact it reboots after a while without any reason.
Is there anyone here that knows how to fix this? Or is it possible to do something to get it fixed with warranty?
Thanks for your help
Update: Tried to flash stock rom with the newest firmware(N910CXXS2CPB3_N910COXA2COJ5_N910CXXU1COJ5_HOME.tar) with Odin 3.10.7(with Phone bootloader update on), passed, when rebooting it said 'Installing system update', but before it was finished it said 'Erasing...' aaand a reboot again. But than it showed the Samsung logo animation and it crashed at showing the first 4 letters. After that I flashed Philz 6.58.9 to flash Googy Max 2.0, the phone now works, but is still crashing when the sreen turns off.

Flight mode messed up phone

I dont often use flight mode, but when I did recently, about an hour later I noticed the phone was dimly lit and on. It was on the Samsung logo, like it rebooted and stuck on boot. The blue LED was on and the 'kernel not seandroid enforcing' in the corner. Could not turn it off without removing battery. Even when I put battery back in, again stuck on boot.
Eventually managed to get into recovery and wiped dalvik and cache, but still same problem. This is on MM 6.01 stock debloated (either xXx 2.1 or _andr 3.3 devbase). Restored a full backup and managed to boot and seemed to work OK, but it again froze after 10-15 min.
Problem was only fixed when I restored an older LP backup (xXx 1.6). 2 days later works fine even in flight mode. Anyway, googling this issue, seems a few others experienced same, but on LP. Havent seen instances of it happening on MM, but not sure I want to go back to MM so soon.
Anyone else experienced similar issue? And what could have caused this to happen when in flight mode?

Same thing happened to me with the BTU modded MM 6.0.1 ROM G900FXXU1CPDF-BTU, but nothing to do with flight mode, I just noticed the phone dim and stuck trying to boot
I went back to G900FXXU1CPD7-BTU and it's been fine since

Strange thing when powering off

Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat

Gumak11 said:
Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat
Click to expand...
Click to collapse
Its a common issue.
Just wipe everything from bootloader, like system, data,cache, then flash recovery.img from .44 update and then reboot to recovery and sideload the .54/.540 update.
everything will be fixed.
Me and my friend faced the same issue about a year and a half ago,and this fixed the issue.

What does 'sideload' mean? Sorry I am new here :v

weird bootloop

I flashed a custom kernel recently on my phone that's compatible with Android 10 roms. After the reboot all seemed fine. I waited 30 minutes just like for any other custom kernel then I turned my screen on, the substratum theme I was using wasn't applied then my phone randomly reboot so I let it do so. After the reboot I turned it on immediately and it randomly reboot a few seconds later so I force reboot to recovery to reflash the kernel. It didn't work and now I'm stuck in bootloop so I prepared my phone for a clean flash and did so. After the clean flash Havoc booted up into setup wizard then about a minute into the setup my phone rebooted again(soft reboot) and it rebooted into the setup wizard with the progress from before already done. I gave it about an hour and it kept doing the same thing over and over again so I clean flashed a different rom this time thinking it would fix the issue but the same thing still happens, it's still happening till now and I can't think of any way to fix this
tl;dr
I flashed a custom kernel and I'm stuck with a weird kind of bootloop where it does boot but then restarts a minute later over and over
is there any way to fix this? And if so if I need to flash the fastboot rom can I do it without losing twrp and stuff so I can reinstall my cusrom?