Database Users

[Help] Weird freezes and shutdowns (flashed Stock)

So i have a galaxy s5, was running Cyanogenmod 12
my phone was freezing and rebooting then eventually it was stuck and would only boot into download mode
so i cut my losses and flashed stock 4.2 and 5.1.1 (files from samMobile matched model number) and the problems persist
cleared cache and factory reset multiple times and booting in safe mode doesn't fix anything
the phone freezes on samsung splash screen usually mid animation, sometimes i get to tmobile screen when it freezes.
sometimes it will boot without any problems and work normally for a few seconds then freeze and shut off into the same loop
i have searched and can't find any advice past (flash stock and your good :good: )
oh and knox counter 0X1 (2) so no warranty for this guy.

anyone?

[HELP] Note 4 Good Lock probleme [URGENT}

Hello, please i really need help
so tried good lock (Samsung systemUI), after that, the phone become unstable... I uninstalled it and the phone had a lot of fc of systemUI and other apps and random reboots, and sometimes it boot into recovery on its own sometimes into download mode, so i flashed another official firmware and did a factory reset , but no luck , then i flashed a ported Rom (Dr.ketan Rom) now my phone don't do a lot of fc and don't reboot into recovery and download mode on its own , but still having a lote of random reboots and a lot of freezes, any ideas guys? i looked everywhere but nothing

Same problem as you, but it's worst : I tried latest Good Lock 24.0.10 and after uninstalling it, I got a popup saying "SystemUI has stopped working", with black screen and can't do anything else than accessing menu with Lock Key (with reboot, shutdown buttons, etc.) :/
Tried to reflash ROM with ALEXNDR ROM for Note4 but same problem. Any solution ? I'm trying to restore Good Lock latest apk through flashable .zip to see if I can re-use my phone.

WEIRD/PECULIAR RESTART SCENARIO in my S5 GM 900F

Hi Guys,
I am facing a peculiar kind of problem in my phone (G900F) since yesterday.
What happens is that, if I tried
i) To restart my phone from the phone (reboot menu), the phone stuc in boot screen and then vibrate twice then after 5-10 sec the phone start rebooting all along once again with 2 vibration and this process keeps repeating until I pull out the battery.
ii) To access recovery (both hard- key combination or from reboot to recovery option in phone), the phone reboots and it stays in the initial screen for about 45 seconds and then the screen went black and freezes there until I pull out the battery.
iii) To access download mode ( both hard- key combination and reboot to download mode option in phone), there seem no problem.
The weirdest part is that, if I remove the battery for 5-10 min and re-insert the battery and do any of the above options; the phone reboots and i get the home screen loaded successfully with no problem . I can also get into my recovery after this 5 mins switch off just like the above. I also found the phone lags a bit in this home screen.
I almost did all the combination to get off this problem (stated below) but I keep getting this problem again and again.
I was in Sixperience v 3.1 with Pheonix Kernel v 10 and Philz CWM recovery and tried the below to try to fix the issue
1. Re-flashed Kernel from Recovery (Also, tried to re-flash kernel after uninstalling Xposed but no use)
2. Re-flashed Modem and Bootloader from ODIN once again (G900FXXU1CPF7_BL_G900FXXU1CPB8_MODEM_LTE.tar)
3. Reflashed ROM once again as a fresh install through Philz recovery.
4. Restore the cwm backup from recovery (which was backed up a week before.)
5. Flashed Samsung Stock MM ROM (G900FXXU1CPFH_G900FPHN1CPFD_PHN.tar.md5) as a fresh install.
After this stock ROM installation is done, the phone struck at SAMSUNG flashing logo and the blue LED keeps glowing for more than 30 mins)
Nothing works. ? Any idea on what is to be done to fix this issue? I am not sure, what i did but this problem keeps coming even after trying of all of the options since yesterday.
Please help to with your expertise.

Bricked?

So. My Gf's Galaxy S5 has been wierd since an update she doesn't remember (Latest is May 2017?)
It has rebooted randomly, so ofc i blamed they battery, as it is 99 times out of 100.
But when a new one just resulted in a bootloop, i had to google and to they usual things: Reflash with latest Stock-fw, Factory reset, try the 2nd newest, FR, and so on.
I'we tried 3 firmwares now. (2x "nee" and 1x "vds")
Still the same loop, sometimes it gets to the Samsung logo, and boots for a while and reboots to the galaxy5 logo and freeze there. Right now i got " sa" from the Samsung logo, frozen.
Sometimes it reboots to black and wont start....
It doesnt feel line a Brick, since dl and recovery works, but it wont start....
May an custom rom and/or recovery help?
I got tools to open it, but i rather not, since you need to remove the screen to acces the PCB...stupid Samsung...
Edit/Update:
Flashed Twrp.
Cannot install the custom rom i'm trying, it freezes randomly. >_<

SM-N910F Blackscreen after flash / Odin = Pass - looking for help

Hello community,
A good friend of mine asked me to support him with his "bricked" Note 4.
I tried now for a few hours (usually im experienced with stuff like that) without any success.
Downloadmode is accessable. Odin (3.09) says most of time 'pass'.
I flashed the following stock roms:
N910FXXU1DRI2_N910FOXA1DRI1_DBT_(Germany) [We are from germany] 1 File.
Odin tells me: pass, Phone reboots in recovery mode, installs a system update, processbar filled half, "earasing", reboot into recovery and display stuck on black after retry to install a system update.
I already tried to debrick - after reflash the PIT file, the Note4 stuck in the Note4 Splashscreen with a blue LED blinking but nothing more happens. [Debrick XDA Thread] (should it?)
I tried also the N910FXXU1ANK4_DBT_4Files Firmware but same behavior (black screen after system update - the phone must turned on since the power button doesnt react - I need to pull of the battery for reboot).
Any hint for me what Im doing wrong? This devices drives me crazy ...
Is the device hardware broken maybe? What do you guys think?
Thank you for reading
Best regards
/nepixl

Have you tried to install a custom recovery instead first?