Database Users

i9505 black screen after reboot

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.

Please help! System process not responding

Hello all. I've had a Verizon note 3 since release. I've been running HyperDrive 6 on 4.3 since I got the phone. I've had no reason to update at all, not to mention when I first got it I didn't understand knox so now my knox counter is 0x1. Its been great and themed and untouched for at least 3 months. Today I noticed everytime I opened an app it was upside down, and flipping my phone didn't help. So, I rebooted it.
Ever since that reboot about 3 hours ago I have been unable to get it to reboot fully. It boots up, gets to the lock screen and freezes for about 10 seconds then pops an error saying System process not responding "wait or close". I've done both options with no luck. I've booted into safestrap, cleared cache, recovered to my most recent (April) recovery, booted into stock rom slot, EVERYTHING ends in system process freezing and rebooting.
Why is it doing this out of nowhere? How do I make it stop? What is even wrong? I need this phone for work and in the 3 hours without it have already gotten crap via email for being unresponsive to phone calls.
I have zero idea how to update to KK with my knox counter voided. I'd prefer not to anyway since 4.3 HD6.0 worked great and was themed to my liking.
But I need this phone working, so I'm taking ideas.
Thanks for your help.

Have you tried using Odin if not might wanna start with that use a computer download the stock firmware tar file use Odin to flash the phone back to stock. That's what I would do I don't know what's wrong with you phone but that might help undo what was done.

burkechrs1 said:
Hello all. I've had a Verizon note 3 since release. I've been running HyperDrive 6 on 4.3 since I got the phone. I've had no reason to update at all, not to mention when I first got it I didn't understand knox so now my knox counter is 0x1. Its been great and themed and untouched for at least 3 months. Today I noticed everytime I opened an app it was upside down, and flipping my phone didn't help. So, I rebooted it.
Ever since that reboot about 3 hours ago I have been unable to get it to reboot fully. It boots up, gets to the lock screen and freezes for about 10 seconds then pops an error saying System process not responding "wait or close". I've done both options with no luck. I've booted into safestrap, cleared cache, recovered to my most recent (April) recovery, booted into stock rom slot, EVERYTHING ends in system process freezing and rebooting.
Why is it doing this out of nowhere? How do I make it stop? What is even wrong? I need this phone for work and in the 3 hours without it have already gotten crap via email for being unresponsive to phone calls.
I have zero idea how to update to KK with my knox counter voided. I'd prefer not to anyway since 4.3 HD6.0 worked great and was themed to my liking.
But I need this phone working, so I'm taking ideas.
Thanks for your help.
Click to expand...
Click to collapse
Sorry i got no idea what you can do, maybe oding back? But this is not the correct place to put a question... I am kind of sure you know that and if you didn't then read the forum rules.

Awesome ROM bro, I'll give it a try!!

Faulty hardware?

Recently I've been having problems with random lag spikes, reboots and suddenly the screen just going black. This has gradually started happening more and more. Sometimes I've also gotten a boot fail screen wich resets the phone into download mode, other times I've gotten a kernel panic message stating eMMC read fail. To get the phone running again I often have to try several reboots and pull the battery for a couple of seconds. The battery is brand new as I just replaced my old battery that was starting to instantly deplete at around 20%.
It seems like a couple of other people has had this issue.
I've been using the same debloated stock root rom for the past 3-4 months, and it has worked fine, until recently when these problems started occurring. I suspected the source of the problem was xposed modules or an app wreaking havoc on the device. First I tried uninstalling xposed through TWRP, but the problems still occured. Then I tried to do a factory reset through the settings menu, but oddly the phone just restarted without performing any reset. So i figured I had to do a wipe via TWRP, but I got some kind of mounting error. After installing TWRP v3 I managed to wipe and install a new rom.
I tried these roms but the problem still presists after several tries of flashes and wipes.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
The last thing I have yet to try is to do a clean stock flash through Odin, but chances seem dim as evidence points towards some kind of hardware failure. Flash chip maybe?
If it actually is hardware failure I have the problem of having modified the phone, so even if I go back to a stock unrooted rom the "Kernel is not seandroid enforcing" and "Set warranty bit: kernel" text will still show up during boot. If I am correct there is still no way to remove this, right? Luckily Norwegian laws are quite lenient when it comes hardware fault warranty, with up to 4 years of warranty for phones.
Will the service shop immediatly dismiss phones if they detected a modified system, even if it's 100% guaranteed that the problem is hardware failure? Has anyone had any experience with this?
I know a friend of mine got his rooted Nexus 5 replaced, but that didn't turn on at all, so I think they just replaced it without checking.

lameplx said:
Recently I've been having problems with random lag spikes, reboots and suddenly the screen just going black. This has gradually started happening more and more. Sometimes I've also gotten a boot fail screen wich resets the phone into download mode, other times I've gotten a kernel panic message stating eMMC read fail. To get the phone running again I often have to try several reboots and pull the battery for a couple of seconds. The battery is brand new as I just replaced my old battery that was starting to instantly deplete at around 20%.
It seems like a couple of other people has had this issue.
I've been using the same debloated stock root rom for the past 3-4 months, and it has worked fine, until recently when these problems started occurring. I suspected the source of the problem was xposed modules or an app wreaking havoc on the device. First I tried uninstalling xposed through TWRP, but the problems still occured. Then I tried to do a factory reset through the settings menu, but oddly the phone just restarted without performing any reset. So i figured I had to do a wipe via TWRP, but I got some kind of mounting error. After installing TWRP v3 I managed to wipe and install a new rom.
I tried these roms but the problem still presists after several tries of flashes and wipes.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
The last thing I have yet to try is to do a clean stock flash through Odin, but chances seem dim as evidence points towards some kind of hardware failure. Flash chip maybe?
If it actually is hardware failure I have the problem of having modified the phone, so even if I go back to a stock unrooted rom the "Kernel is not seandroid enforcing" and "Set warranty bit: kernel" text will still show up during boot. If I am correct there is still no way to remove this, right? Luckily Norwegian laws are quite lenient when it comes hardware fault warranty, with up to 4 years of warranty for phones.
Will the service shop immediatly dismiss phones if they detected a modified system, even if it's 100% guaranteed that the problem is hardware failure? Has anyone had any experience with this?
I know a friend of mine got his rooted Nexus 5 replaced, but that didn't turn on at all, so I think they just replaced it without checking.
Click to expand...
Click to collapse
if you flash stock unrooted firmware with odin it will no longer display "kernel or recovery are not seandroid enforcing" or "set warranty bit kernel" ....but the service center if they boot into download mode and check knox counter will be able to find out if the phone has been rooted previously because once knox counter changes from 0x0 to 0x1 after rooting there is noway to reset it back to 0x0.

dork997 said:
if you flash stock unrooted firmware with odin it will no longer display "kernel or recovery are not seandroid enforcing" or "set warranty bit kernel" ....but the service center if they boot into download mode and check knox counter will be able to find out if the phone has been rooted previously because once knox counter changes from 0x0 to 0x1 after rooting there is noway to reset it back to 0x0.
Click to expand...
Click to collapse
Yeah, just remembered that after flashing stock room through Odin just now. It's been a while since I've been on stock
I will give the stock rom a go for a couple of hours to see if the problems persists.

Seems like the issue still are there after Odin flash.
Could re-partitioning with a pit file help?
http://forum.xda-developers.com/not...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641

Unstable & Unusuable

It sounds melodramatic but maybe someone else has encountered the same problem and can help.
I got my phone last week and used it for a couple hours before I decided to root and flash a custom ROM onto the phone. I didn't realize that the kernel had dmverity and proceeded to try and root my phone like any other phone.
I followed the usual steps in installing root for the first time. I used Odin to flash twrp onto the phone and proceeded to restart into recovery. I had forgotten to copy supersu to my phone before I restarted it and this is where my problems began. I swiped on the twrp page where it warns of dmverity but because I didn't transfer supersu I had to restart the phone and get it on. The problem being the phone was now stuck in a bootloop and I somehow managed to get supersu onto the memory and flashed it. I was able to boot into the rom but it was extremely unstable. I could work for maybe 5 minutes before the phone froze, got very hot, then shut down. It would go into a bootloop and succeed maybe 1/20 times, all the while the phone got very hot. I flashed a custom rom onto it and it kind of worked but would still freeze and restart every once in a while. I found the stock bootloader, rom, cp, csc, and flashed those. My phone is now stock everything but the crashes still occur frequently (basically every time I try to use it) and I'm at a total loss as to what to do.
I've rooted all of my phones since I got my S3 several years ago and I've never had a problem like this. Anyone know how I can fix this? My phone is model G935w8 so I know it has the exynos processor and rooting is possible, but I must've done something horribly wrong for it to be like this. Any help is appreciated.

Bootloop: Upgrading Verizon Note 4 from 5.1.1 w/ root to 6.0.1 w/ root

After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
The details are below if it helps determine what might have happened, but if I can just restore her backup, she'll be happy, which means I can finally get out of the dog house.
I tried upgrading my wife's phone since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
Any suggestions?
Mike

Modify_inc said:
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
Click to expand...
Click to collapse
Not that I'm impatient, but I thought I had a backup phone I could put my sim card in until I resolve this issue. Only problem is I forgot it was an at&t phone. Duh!
From what I've read the Note 4 n910v is a robust and almost unbrickable phone. So I said what the heck, I'm going to restore my backup. I mean that is why before all instructions it is advised to make a full backup, so you can revert back, right!. I don't recall the instructions claiming there is a special process or order of steps to take before you can restore your backup.
So, I wiped everything and restored my full backup via twrp. Upon reboot, I finally had the "Kernel is not seandroid enforcing" and "Set Warranty Bit: Kernel" that I was accustomed to. I thought this must be a good sign, but then it went to a black screen, which I realized after about 20 mins, that it had powered itself off. So I tried it again and same thing, it doesn't reboot or even vibrate or flash the LED light. I can press the power button and it will come back on, so I know it turns itself off. So what would cause it to power off after displaying the first boot logo titled Samsung Galaxy Note 4 Custom w/ unlocked icon powered by Android?
The next thing I will try, unless hopefully someone advises me otherwise, is reflash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I assume that should be safe to do, and I'll just follow the directions for the "Easy Guide for How to Root Verizon Galaxy Note 4 (updated links and instructions)" though technically isn't the bootloader already unlocked since I have the red "Kernel is not seandroid enforcing" and the yellow, "Set Warranty Bit: Kernel" and the custom unlocked lock on my boot screen?
This is where I'm confused, I feel like this is not the issue, that it must be something else, but I'm at a lost.

Finally got my phone working! But no WiFi
I've finally got my phone working again! I just can't get the WiFi to work. I have tried three different modems but still the WiFi will not enable: N910VVRU2BPA1_Modem, N910VVRU2CPD1_Modem, and N910VVRU2CPF3_Modem. I even tried restoring the modem I had backed up, but still no go. I noticed that even when I restored my modem from backup, it still said my baseband was N910VVRU2CQL1, but when I flashed the other modems, they each updated the baseband correctly, displaying the correct baseband version, though still no WiFi.
Any suggestions?