Related
Hey guys,
I don't usually ask questions rather than searching for threads/similar problems and try to fix mine.
But, this one's serious
I've had my Galaxy SIV GT-I9500 for 2 months now. I usually try CyanogenMod and other roms(Omega and Crash)
As I used to do so on my previous android (non Samsung) phones.
Lately I've been having a strange issue that I can't even tell if it's a battery problem or it's a software glitch or a mistake I made before.
The problem is the phone usually stops when using it ... Freezes and then restarts (that's normal but.)
The WEIRD thing is that the phone boots again automatically ... Then a dialog shows that "Your Battery is critically low"
And I'm sure There was more than 90% battery.
Well I tried to figure out why and how to fix it... I found a similar problem but no one found what's the matter.
Things I've tried:
1- Flash Stock System, Kernel and everything else (100% Stock)
2- Flash A custom rom ...
3- Flash another custom rom.
4- wipe data/factory reset
5- Remove SD Card
6- Remove Sim Card
7- Tried Most custom kernels
9- Flash a Modem the right one for my country (Iraq)
Well, None of these helped
The problem usually appears at anytime . Most of it when using the phone not when Idol
Do any of you guys have any Suggestions for me ? or even a fix ?
Thank you ... If I find a solution I'll let you know so that people will benefit.
Thank you XDA
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
hey, let me help you.
what was the situation when this wierd thing happened?
eg. were you playing game?
or surfing internet. or any other..
was your phone rooted?
did you installed xposed framework?
(i've seen most blue screens in Xposed)
if you have installed xposed framework then either remove recently installed modules or completely remove xopsed framework.
and if your phone hasnt been rooted, and you are facing blue screen problems, i think you havent factory reseted your phone, so perform factory reset and wipe cache frome recovery..
hope this helps.
Hey Vrushabh thanls a lot for your time , This happens only sometimes like once in a week.
I had rooted my phone earlier but after this crash i formally uprooted my phone and from last 4 days it has no problem .... THANKS AGAIN BRO.
Now my question is that , what was the reason behind this type of blue screen error...?
I have the same problem with my Grand 2. It automatically got an official update 4.4.2 and since then whenever I use it for a while specially on facebook, the cell gets restarted after giving a blue screen. I have made the factory data reset and since then its a bit improved but the problem still not gone altogether. Please if you can give any solution?
DEEP1994 said:
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
Click to expand...
Click to collapse
i try to boot into the safemode but no use the blue screesn restart problem still happend
what about the new rom NI2 , saying it fix the problem , did any1 try it ?
Grand 2 Duos Bluescreen
Hi all,
I also encountered the blue screen and restart error. This happens randomly like using Whatsapp, 9gag or Facebook. It also restarts for no reason at all.
The phone is not rooted by the way. I tried running it on safe mode and nothing happened. After normally booting it, it crashed twice. First with a blue screen and the second was an automatic restart.
Thanks
I tried ni2 but no luck . blue screen and restart again
2Hourse ago i Downgrade to 4.3 and now i have not any problem.byby **** kitkat by damet samsung:
Reason of Blue Screen Death
gn_hanna said:
i try to boot into the safemode but no use the blue screesn restart problem still happend
what about the new rom NI2 , saying it fix the problem , did any1 try it ?
Click to expand...
Click to collapse
I think this happens because some times Apps are trying to write something on prohibited areas of system , and that's why OS restarts Itself to prevent data looses .
Are the people having this problem on SM-7102 and perhaps the phone bought/CSC from India?
peman2010 said:
2Hourse ago i Downgrade to 4.3 and now i have not any problem.byby **** kitkat by damet samsung:
Click to expand...
Click to collapse
Bro @peman2010, pls tell the detailed process of Downgrading from KK to JB...............
Sent from my SM-G800H using Tapatalk
SD card access permission denied
DEEP1994 said:
I think this happens because some times Apps are trying to write something on prohibited areas of system , and that's why OS restarts Itself to prevent data looses .
Click to expand...
Click to collapse
yes you are right ,
I realties that the system can't write to my SD card access permission denied
Is there any solution for this issue?
How to fix permission for both system area as you mentioned above and the SD card access
gn_hanna said:
yes you are right ,
I realties that the system can't write to my SD card access permission denied
Is there any solution for this issue?
How to fix permission for both system area as you mentioned above and the SD card access
Click to expand...
Click to collapse
no its not bcuz it cant read Sd card or something like that
it happens due to system error
and ya u can get access to sd using the xposed module
Sanjuujosephh said:
no its not bcuz it cant read Sd card or something like that
it happens due to system error
and ya u can get access to sd using the xposed module
Click to expand...
Click to collapse
On 4.4, Google bolted down write access to the external SD except the folder named Android.
SDCard Fix App
WaseemAlkurdi said:
On 4.4, Google bolted down write access to the external SD except the folder named Android.
Click to expand...
Click to collapse
did you check the SDCard Fix App
http://forum.xda-developers.com/showthread.php?t=2684188
Update:
After testing SDFix: KitKat Writable MicroSD
It is still the restart problem remains as it is although I can write to the SD card and move apps to
My device is rooted now
Is there any other solution !!??
DEEP1994 said:
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
Click to expand...
Click to collapse
I have the same error . i already flash official 4.4.2 firmware & clear all data & factory reset . but i still have the same problem .
plz let me know if anyone can solve this .
what is the best rom for the device without any issue (restart,blue screan,sdcard write access,.....)
gn_hanna said:
what is the best rom for the device without any issue (restart,blue screan,sdcard write access,.....)
Click to expand...
Click to collapse
None
My grand 2 got same problem
I have random reboots/blue screen during fb/viber/ etc..
while also watching vids via MXplayer pro
i hate it so much..
can some1 give me a detailed tutorial for downgrading to 4.3 JB? i have this prob since upgraded to kitkat
juck401 said:
I have random reboots/blue screen during fb/viber/ etc..
while also watching vids via MXplayer pro
i hate it so much..
can some1 give me a detailed tutorial for downgrading to 4.3 JB? i have this prob since upgraded to kitkat
Click to expand...
Click to collapse
You can download official FirmwareVersion from sam mobile, just google it. And flash it through Odin 3.7, i hope it will help you .
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Hi Mate,
Not saying this is your problem but i seen some people having issues with the power button , symptoms are similar to your random reboots like in constant reset....check the power button see if is stock and easy way to check is try to go to recovery without pressing the power button.....if is really stuck or short out you should be able to go to recovery without ( for a short time) ....that will prove that the problem is coming from there...
Of course if is very sporadic wait until is happening for testing ..
I had the same problem before because I disabled knox using supersu. What I did was delete all knox related apps and everything is good.
Many users had this problems with Knox as well. Try to uninstall everything relating to Knox, maybe it will work
Gesendet von meinem GT-I9505 mit Tapatalk
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Delete all knox related apps via "titanum backup" and you are good to go! :good:
martikip said:
Delete all knox related apps via "titanum backup" and you are good to go! :good:
Click to expand...
Click to collapse
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
pimpl said:
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
Click to expand...
Click to collapse
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
Indeed, I have never had a problem again, since I deleted the Knox-stuff. Just do it and the problem will be solved!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
It's right uninstall Knox and be happy
Gesendet von meinem GT-I9505 mit Tapatalk
I have the same issue at the moment - Phone is completely standard (Not rooted). All has been good until the morning of the 30th August when there was a new firmware update applied. I had already had the Kit Kat update earlier in August and the phone had been working with no issue, since this 220Mb odd 'patch' the phone will just randomly reboot, I say random but it just seems after it has been idle (Screen off) for a while on unlocking I can start an app (pretty much anything) and about 5 seconds later the phone will reboot. As the OP mentioned it is a faster than normal reboot and it doesn't play the normal start up sound either.
I am not sure what the update did, it mentioned ironically that it was fixing stability issues!!! - Is there a way without rooting the phone to roll back the firmware to before the patch?
Cheers.
Factory reset worked too
I have been struggling with a similar problem on my GT-I9505 since receiving a system update on May 30, 2014 -- random reboots many times a day, plus fairly reliable reboots about 30-40 seconds into any received phone call. I tried cleaning caches, uninstalling recently installed apps and then other unneeded apps, installing new updates, and lots of other things. My last resort was rooting and removing Knox as suggested here. But first I tried a factory reset, and it worked! I've now gone several days without an unintentional reboot. It's a pain to have to restore backups and reinstall apps, but it was worth it. I hope this information is helpful to someone.
Issues on my CF auto-rooted GT i9505
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Idebutterpiep said:
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Click to expand...
Click to collapse
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
No do I have to?
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
I guess this will help. Knox often causes this issues. Just uninstall everything relating to Knox with Titanium Backup
Sent from my Galaxy S4 using Tapatalk
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
c0dewana said:
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
Click to expand...
Click to collapse
I think I solved my problem: I deleted all Knox related items and when I rebooted my phone again it stucks on the Samsung logo. I installed the stock I9505XXUGNG8-DBT again with Odin. Installed CF Auto-root.and Phill''s CWM again. Installed Supersu again.
Now everything is working again without the frozen screen, time synchronizes and no booting by incoming phone call anymore.
Hi Guys
I have a N910F Runing 5.1.1 working fine but I have a big issue when I switch off or Restart the phone it won't boot up so I have to pull out the battery and let it for 1 minute or more then it boots up somtimes it gives me emmc error
The problem started when I updated to 6.0.1 then I tryed flashing the 4 files firmware with PIT for both LL and MM but with no avail the same symptoms so I decided to flash TWRP and Keyubi V5 Rom it's Smooth but not able to restart the phone or switch off to switch on again the only thing thats working is the Hot reboot. I need you guys to help me sometimes I need to switch off my phone so I don't have to take the battery out everytime I want to switch on the Phone
I will be glad to hear some suggestions or fixs please.
Thank you
AndroMor said:
Hi Guys
I have a N910F Runing 5.1.1 working fine but I have a big issue when I switch off or Restart the phone it won't boot up so I have to pull out the battery and let it for 1 minute or more then it boots up somtimes it gives me emmc error
The problem started when I updated to 6.0.1 then I tryed flashing the 4 files firmware with PIT for both LL and MM but with no avail the same symptoms so I decided to flash TWRP and Keyubi V5 Rom it's Smooth but not able to restart the phone or switch off to switch on again the only thing thats working is the Hot reboot. I need you guys to help me sometimes I need to switch off my phone so I don't have to take the battery out everytime I want to switch on the Phone
I will be glad to hear some suggestions or fixs please.
Thank you
Click to expand...
Click to collapse
So, you're running 5.1.1 or 6.0.1?
Sent from this galaxy
pr1jker said:
So, you're running 5.1.1 or 6.0.1?
Sent from this galaxy
Click to expand...
Click to collapse
Running Note 5 port Kyubi SDX R2 (5.1.1) for now
Hello, I am facing the same issue. Mine is note with att unlocked recently by att. Currently running 6.0.1 with Feb 2017 security patch. I have changed nothing in terms of software still facing this issue. Let me know if you have got any solution.
Thanks
P.D.
lash a Note 7 port, My phone went off in the process... ever since then.... Its impossible to make a reboot without pulling out the battery.....
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
kdizzy07 said:
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
Click to expand...
Click to collapse
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Mufrad said:
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
kdizzy07 said:
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
Click to expand...
Click to collapse
Sometimes you have to flash bootloader again separately, specially if it was changed to an later version than the one you are flashing through odin, and I would suggest a custom touchwiz rom which is close to stock but with bloat removed and some speed tweaks maybe for the most bug free experience. But also maybe give stock android roms a try, most bugs should be ironed out.
Mufrad said:
if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
OK, last night I tried a couple of things:
1. I flashed Slim6 6.0.1.build.2.1 and twrp-3.2.3-0-klte (with wiping) - didn't help.
2. I took the sim card & sd card out - didn't help.
3. I ran logcat from ADB using USB debugging to see if I could get the error before the restart - While the phone was connected and logcat was running, the phone never restarted. Even when the screen timed out and turned off. (I guess the phone doesn't count this as "idle")
oh, and thanks for all the assistance so far
The fact that it happens on custom ROM leads me to think hardware. The fact that it doesn't happen if I keep the phone "busy" leads me to think software. What should I try next?