Hello, I have been using my S4 for over a year with this issue, I installed screen adjuster free from the play store to "fix" the problem as you can see in the images, but increasing the brightness from the sytem damaged my battery over time, so I'm asking for help again. It happened when I went back to stock with odin after installing cyanogenmod with the installer (that time I did not wipe), it rebooted with the those lines (so then i wiped but they remained) They are everywhere no matter the ROM, even in recovery (using TWRP, also tried Philz) so this is not an accesibility setting. I have tried every kind of format except two, nand erase and re-partition. Can anyone help me to really fix the problem?
Related
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Same problem on same phone
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
I was using a CM10.1 nightly build for my i9505 and attempted to install the AVAST Anti-Theft feature using the root install method. On the first attempt at installation there was a free-space error, in which the amount of free space shown in the /system partition had overflowed and showed negative free space. To work around that error I filled up my /system partition until there was only 100mb free and then the install worked. All went well until I did a reboot; the phone hung at the i9505 screen.
I tried rebooting the phone and removing the battery for a short while, but nothing worked - the phone still hung at the i9505 screen. However, all other functions worked, so I just reflashed CM10.1 after wiping /cache, /data (but not /data/media), /system, and the Dalvik-cache (though that is in /cache AFAIK so pretty redundant). All was fine after that reflash, other than the annoyance of having to set everything up again (didn't make a backup recently).
Obviously the Anti-Theft wasn't very secure if it could be removed by a simple reflash. But to be fair, I highly doubt any software can protect itself from a format!
Anyway, just letting people know that I can confirm this this problem exists, and how I fixed it on my phone.
ingvarr_zaag said:
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware using odin
Go to stock recovery there factory reset and wipe
Reboot
Note all data will be lost take backup b4
.
sheomualjy said:
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
Click to expand...
Click to collapse
I had Clockwork Recovery installed but I couldn't use it, because after reboot the screen was black. I managed to get to android recovery and flashed stock Samsung ROM by Odin. It didn't help.
After 2 weeks in service it's possible that today I get my phone back. Finally, because two weeks with Samsung Galaxy Advance were miserable.
Actual status on service's page says, that they replaced main board in my phone.
BTW: no Avast Anti Theft ever again.
Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Lennyz1988 said:
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
Click to expand...
Click to collapse
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
PePeMoke said:
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Click to expand...
Click to collapse
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
For CWM I do not know..
I use TWRP and there you can select what should be wiped under "advanced wipe".
You can select system, boot, data, cache and internal storage.
If you got TWRP use this!
Note that everything on your phone will be deleted including custom recovery.
You'll have to flash it again via Odin afterwards.
Then flash the ROM and Gapps via custom recovery.
I do not know whether this will solve the problem because it really could be a hardware issue as Lennyz said..
Maybe you should wait with that after the company repaired it again.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
It's possible but not in your case. There is no software booted when you are in the recovery except the recovery itself.
@SwoodGrommet
Could you figure it out?
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)