G9700 Occasional Full Crash - Log Included - Samsung Galaxy S10e Questions & Answers

My phone randomly shuts down when locking the screen. Not sure why. Seems to only happen when im booted into Magisk mode. attached is the kernel log, i hope someone can help.
EDITL: i have attached the last 11 last_kmesg.log into a rar file. Please check them. Thank you

Related

Tablet freezes and reboots after a few minutes of usage

This problem has been going on for a long time now and started even before I unlocked the bootloader.The problem occurs after a few minutes of usage (even when it's idle). The GUI freezes for 5-30 seconds and initiates a reboot, repeating the process every few minutes. I've restored everything to stock using the latest official firmware from ASUS, I've tried using Cyanogenmod as well as several other ROMs, but the problem still persists. Is this a low-level hardware issue? Has anyone else experienced this kind of problem before?
I've also done everything from Wiping Dalvik's cache to formatting the SD card and reflashing a fresh set of recovery and system ROMs. Nothing seems to work
Thanks
-Foxhoundz
UPDATE1 - After searching around, it seems like most people began encountering the reboot after the JB update. If that's the case, is there any way to downgrade from JB? I cannot find any 4.0 stock firmware for the US SKU on ASUS's website. I'm currently on the latest (as of 9/22/2013) ASUS firmware with Cyanogenmod 10.2 (JB 4.3).
Any possible solutions to this? It's been a while since I've made this post but the problem still persists. If at the very least I knew what was causing it perhaps I could begin approaching the problem correctly let alone try to fix it.
NVflash
Foxhoundz said:
Any possible solutions to this? It's been a while since I've made this post but the problem still persists. If at the very least I knew what was causing it perhaps I could begin approaching the problem correctly let alone try to fix it.
Click to expand...
Click to collapse
Have you recovered your nvflash blobs??
You do have fastboot??
What is your PC's OS??
lj50036 said:
Have you recovered your nvflash blobs??
You do have fastboot??
What is your PC's OS??
Click to expand...
Click to collapse
1 - I didn't make NVFLASH blobs. I already unlocked and flashed other ROMs before learning about it
2 - Fastboot works. Actually, everything works and I currently have Cyanogenmod on it. The problem is it freezes and reboots after a few minutes of usage or when it's doing a processor intensive task. It freezes for a few seconds and triggers a reboot.
3 - Windows 7
fastboot/adb
Foxhoundz said:
1 - I didn't make NVFLASH blobs. I already unlocked and flashed other ROMs before learning about it
2 - Fastboot works. Actually, everything works and I currently have Cyanogenmod on it. The problem is it freezes and reboots after a few minutes of usage or when it's doing a processor intensive task. It freezes for a few seconds and triggers a reboot.
3 - Windows 7
Click to expand...
Click to collapse
Does adb work ??
If so I would like a logcat of your bootup and a logcat of the crash....
To do this...Move to the directory your adb.exe file is in.. than open a CMD window and turn you tablet off plug the tablet into your PC and type
Code:
adb logcat > logcat_boot.txt
Than boot your tablet you will not get a output it will just come back to CMD prompt.. There will be a logcat.txt file in that directory. post that file
Than once fully booted into rom. Do the same thing just change the name if the output file
Code:
adb logcat > logcat_system.txt
Let it run till it crashes and post that file also.... Let me know if there is anything I can help with the process....

Not booting Stuck in Hboot/Fastboot - Fixed

Hey Guys,
So I know lots of others have this problem, but I managed to fix my Mini and now it boots correctly.
Like everyone else my phone was stuck in Hboot/fastboot and would not boot the system correctly, as such I tried lots of things to get it to boot, Unlocking the bootloader, Fuu, Zip files etc.
Then it struck me what if the phone does not have enough power to boot ?? So i found this thread here at XDA
http://forum.xda-developers.com/showthread.php?t=1658084
I followed the instructions and what do you know, it only booted up my device, but I then noticed that the power level was showing as 97% - So not a power issue but it worked.
You will need to create the Bin file, run it in Adb/fastboot folder and it should kickstart you phone back into life.
Good luck to everyone else with this issue
sudd1976 said:
Hey Guys,
So I know lots of others have this problem, but I managed to fix my Mini and now it boots correctly.
Like everyone else my phone was stuck in Hboot/fastboot and would not boot the system correctly, as such I tried lots of things to get it to boot, Unlocking the bootloader, Fuu, Zip files etc.
Then it struck me what if the phone does not have enough power to boot ?? So i found this thread here at XDA
http://forum.xda-developers.com/showthread.php?t=1658084
I followed the instructions and what do you know, it only booted up my device, but I then noticed that the power level was showing as 97% - So not a power issue but it worked.
You will need to create the Bin file, run it in Adb/fastboot folder and it should kickstart you phone back into life.
Good luck to everyone else with this issue
Click to expand...
Click to collapse
Hi! I'm a complete noob and I don't know how to create the bin file, or what an Adb/fastboot folder is. Please send help! This is my phone right now
Edit:can you please tell me how to run the .bin file ? ok i managed to run it but i want to ask you how much time should i leave the phone looping ?
should i do anything or just looking at it rebooting XD
nasryus said:
Hi! I'm a complete noob and I don't know how to create the bin file, or what an Adb/fastboot folder is. Please send help! This is my phone right now
Click to expand...
Click to collapse
in exactly same situation, had not used phone for a while, powered up and stuck on this screen, it is not rooted and have recharged

Anyone who can check out my recovery.log for anything wrong

Can't boot up, can't make a logcat, so i thought this would be the next best thing. Is it possible for someone to tell me some info regarding my boot up problem from this file (Damaged partitions?). Power button was recently replaced, recovery happens to randomly restart (all logs are taken from recovery). Using 2.7 f2fs because its the only one that boots.

Help with rooting

I am the proud owner of the SM-G970F
bit of backstory: about 2 weeks ago I had my ideal setup, I was rooted with magisk (using John sun's guild) and I had twrp Installed. Everything was going well until my phone started to run so slow, I did a geekbench test and I was getting 4000 on the multi score (I should get 10000 for my phone,) I wiped cache and my data NOT my os. As I was booting my phone back up It took a while to restore like 2 hours just sat on the Samsung logo, I was getting worried but then it changes to starting android and that's where I went to sleep, the next morning I unplug my phone from the charger and it's still on starting android it's been about 9 hours on this screen. I boot into twrp and do another wipe of cache and my data, and still the same thing, so I boot it into download mode and flash the stock firmware again (BL, CP, AP and CSC). The flash was successful I am now in my phone on stock recovery now I try to root again and start it all again by downloading the firmware from sammobile and patching the AP file, I continue on with the routing steps carefully following all of them, once done and booted into the os I setup my phone without restoring my data. I look for magisk manager and it's not there... I press on the settings app and it says app not found my phone starts to freeze until none of the buttons are doing anything the screen wasn't responding. I had no choice but to go back to stock where I am now
I have tried to root again following John wu's steps very carefully about 5 times and every time the same happens, last time I tried it was getting slow again so I tried to reboot and as it was turning on this came up in red in the corner of the screen it said something like "can not flash custom binaries now" then turned off and it did the same about 5 times until I managed to get it into download mode to flash stock AGAIN
I think it may be something to do with the way magisk patches the firmware I believe it's that my phone had corrupted files or something in the boot sector so when magisk tries to patch the AP file something goes wrong... I have also noticed that when magisk patches the file it is about 500mb less than the original AP file not sure if that's normal cant remember
anyways thank you if you read all that and please give me some tips and share it with John wu or something to try and get some help!!!
have a nice day
Hi,
check this manual:
https://www.the***********.com/samsung-galaxy-s10-twrp-magisk-root-guide/
*** are custom droid(without space between)
Did you do all steps? Maybe you forgot something (like me).
Leg1ndd said:
I am the proud owner of the SM-G970F
bit of backstory: about 2 weeks ago I had my ideal setup, I was rooted with magisk (using John sun's guild) and I had twrp Installed. Everything was going well until my phone started to run so slow, I did a geekbench test and I was getting 4000 on the multi score (I should get 10000 for my phone,) I wiped cache and my data NOT my os. As I was booting my phone back up It took a while to restore like 2 hours just sat on the Samsung logo, I was getting worried but then it changes to starting android and that's where I went to sleep, the next morning I unplug my phone from the charger and it's still on starting android it's been about 9 hours on this screen. I boot into twrp and do another wipe of cache and my data, and still the same thing, so I boot it into download mode and flash the stock firmware again (BL, CP, AP and CSC). The flash was successful I am now in my phone on stock recovery now I try to root again and start it all again by downloading the firmware from sammobile and patching the AP file, I continue on with the routing steps carefully following all of them, once done and booted into the os I setup my phone without restoring my data. I look for magisk manager and it's not there... I press on the settings app and it says app not found my phone starts to freeze until none of the buttons are doing anything the screen wasn't responding. I had no choice but to go back to stock where I am now
I have tried to root again following John wu's steps very carefully about 5 times and every time the same happens, last time I tried it was getting slow again so I tried to reboot and as it was turning on this came up in red in the corner of the screen it said something like "can not flash custom binaries now" then turned off and it did the same about 5 times until I managed to get it into download mode to flash stock AGAIN
I think it may be something to do with the way magisk patches the firmware I believe it's that my phone had corrupted files or something in the boot sector so when magisk tries to patch the AP file something goes wrong... I have also noticed that when magisk patches the file it is about 500mb less than the original AP file not sure if that's normal cant remember
anyways thank you if you read all that and please give me some tips and share it with John wu or something to try and get some help!!!
have a nice day
Click to expand...
Click to collapse
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
ExtremeGrief said:
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
Click to expand...
Click to collapse
thank you I will give it a look now ))
ExtremeGrief said:
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
Click to expand...
Click to collapse
Hii my kg state is prenormal. Any fix for this i tried flashing stock and everything but nothing works

Semi-Bricked S7

Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
GrabAndSmash said:
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
Click to expand...
Click to collapse
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
cooltt said:
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
Click to expand...
Click to collapse
Thanks,
I've got the SamFirm download tool because I was irritated waiting for the download, I'll try downloading and flashing it.
Should I flash the lot, or just one specific thing?
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
GrabAndSmash said:
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
Click to expand...
Click to collapse
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Sorry yes, flash all files, you'll have a clean new phone.
First boot can take about 5-10 mins, and the updating, erasing screens are normal.
cooltt said:
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Click to expand...
Click to collapse
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
GrabAndSmash said:
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
Click to expand...
Click to collapse
Leave the default options already ticked in Odin. You don't need to change anything there.
cooltt said:
Leave the default options already ticked in Odin. You don't need to change anything there.
Click to expand...
Click to collapse
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Only other possible thing I can think of is the battery. There were alarms in the log file and the phone does reboot more when it gets hot. Given the phone is 4 years old now, I wonder if the battery is damaged and the phone is having a hissy fit
GrabAndSmash said:
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Click to expand...
Click to collapse
Yeah look like battery overheating making it reboot
cooltt said:
Yeah look like battery overheating making it reboot
Click to expand...
Click to collapse
I'll give it a try for now, I've got the correct files for flashing it at least this time thanks, I''ll try replacing the battery in the future, and if I find out it fixes the problems I'll update the post. Or if I figure out what's causing it

Categories

Resources