N910F problems - emmc read fail/ flashing stock no longer boots the phone. - Galaxy Note 4 Q&A, Help & Troubleshooting

Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.

engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely

Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.

engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart

I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.

golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.

engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...

I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this

Related

[Q] GT-i9500 has no OS installed.

Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Well first thing is get the latest stock firmware for your variant from my sign and get odin 3.07
For download mode power off phone unplug,, press volume down home and power all together till something pops up and release then press volume up and connect to pc
Open odin click pda and select that firmware u downloaded start the process
For more info check my sign help thread link it has more options on the same
.
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Flashing through odin is one option.... some users have reported that there were some hiccups when installing omega 14 because of the aroma script.....try a different rom...there are many others to choose from....or you could flash stock via odin as said on the earlier comment good luck
Feedback
Today I attempted to use ODIN to flash now I am still currently attempting this. When I press the volume down key, power, and home button it takes me to the custom recovery TWRP instead of download mode. The phone did this when I first purchased it. When I still had what appeared to be the stock rom it would always take me to the recovery. When I would use the volume up instead of down it would take me to the factory test mode now mind you this happened when the OS was still installed. When i try that combination now i just receive a blank black screen. Are there any other ways to boot into download mode?

Huge problem S4 not working anymore..

So this is my sad story..
I bought a second hand Samsung S4 (i337M Telcel) Unlocked, the day i got it, i tested in front of the seller everything was nice and smooth.. So i payed..
I was very excited and i proceed to make the Root proccess, at beginning i was having issues with the drivers and Odin, then i was able to fix it..
Anyways long story short i ended up with the ROOT, CYANOGENMOD CM11, and PHILZ 6.. The first day was working fine my cellphone.. (I must say i rooted in my life at least 4 devices even an S4 i9500 all of then with success and not a single problem.. Using them form months and even gears.. The latest was a Moto E..)
Ok so the i337M was working good since the first morning with the root, but in the afternoon it just turned off one time.. Was weird but i didnt pay much atention..
The second day i was listening music and suddenly it turned off, and since then the cellphone is not able to keep on for more than 10min..
Some times i can load the complete OS and ofter 2 min it turn off sometimes at the Samsung S4 logo turn off something i must say is that the Device every single time i turn it on, on the Samsung S4 screen says "kernel is not seandroid enforcing" in red letters, some people say it happens when the root process is not made correctly some says it normal because its rooted..
I already installed from Odin the Stock ROM from SamMobile, and the problem is exactly the same.. A friend of mine told me it could be the Logic Card AKA Motherboard.. But i want to believe its just a software problem.. Cuz' before i rooted cellphone was working..
- Download mode: Works like a charm not a single problem and basically its the only way i keep trying different options to install on the phone..
- Discovery mode: With CWM sometimes works good, sometimes it just turn off, with Philz runs good not turning off or something and its how i was able to wipe data, cache, dalvik, factory reset to the cellphone..
Im thinking in starting over like pretending i didnt do anything to the cellphone, try again the root, the rom, the PHILZ (dont know how to call it).. and hope for the best..
Any advice or reliable links where i can download the correct files for my S4 i337M.. You are basically the last reliable source i have to fix my S4 if you give up with me, then i must admit my cellphone has passed away ..
Hope you can help me thanks in advance and have an excellent day!!:laugh::good:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
creepyncrawly said:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
Click to expand...
Click to collapse
Thanks for your reply.. I still dont know how but with Philz recovery, i was able to make a full wipe, i mean it deletes everything every single folder previously made was erased, and i can tell you that because i have a folder called ROOM where i places my ROM, Kernel, etc.. So i can flash them in discovery..
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..
Just two advices.. Never ever download files from Youtube ****y links.. Always go to the source.. Youtubers are assholes.. Real help and information comes from real people that knows what they are talking about like this forum and also updated and real ROM's come from the main source not Mega o Linkbucks...
Other advice embrace your self to do it.. Study every single question you have in Android, from KERNEL to ROM and ROOT.. Isn't that difficult..
One more question, Which ROM with Lollipop would you suggest to install i have the i337M?
SUNDR1V3R said:
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..]
Click to expand...
Click to collapse
May I make a suggestion? Now that you have the phone working, can you possibly just use it for a week without doing anything to it? Don't try to root it or do anything other than text, make phone calls, and install a few programs. This will establish a baseline of behavior for your device, so you'll be able to tell when its behavior is out of the ordinary.
I understand your desire to make it your own. I got my S4 brand new from AT&T and said that I would wait at least a month before rooting it or changing roms, in case there was a problem and needed to return it. I had good intentions, but I couldn't stand it anymore and rooted it after only 3 days! It will take a lot of patience, but you really need to use it for more than a few hours to make sure that the hardware is okay.
I agree take baby steps, week stock, week root, week recovery. Figure out if its hardware or one of the steps is causing it.

Stuck in bootloop after un-installing Flipboard

I'm usually fairly good at troubleshooting my own stuff but this really has me stuck in the same place for a few hours now.
So basically Flipboard has been nagging me(well play store is, not the app itself but anyway) so I said to myself why don't I uninstall it since I've never used it and don't plan to, and besides I hate to have pointless apps installed. So I open TitaniumBackup and I see it is installed as a system app, I thought what's the worst that can happen? so I do uninstall it and a minute later my phone shuts off. I try to turn it on and it doesn't go past the Samsung Galaxy Note 4 flash screen, it either reboots or stays like that.
I try to go into recovery to restore a backup and I can't, it is stuck at Recovery Booting and again it either stays like that or reboots and does it again and again and again.
Now, I haven't made any changes or installs on my phone for weeks now, so this is either because I unistalled Flipboard(I know I shouldn't have risked it since it was a system app but I really could not see it going this way) or the hardware is on it's way out(don't see what else could it be).
I figured I should flash a stock rom with odin, I can get into download mode, and reinstall everything from scratch.
I took a stock image from xda and flashed it and it does exactly the same thing.
Right now I'm downloading another stock image from sammobile for my country/provider to see if this will change anything.
What else can I try? I'm completely stuck and I really don't want to send the phone back like this, I doubt amazon is gonna be happy about it.
Specs:
N910F
Emotion Revolution 12.1 Rom
POK1 BL&CP
TWRP 2.8.7.0
Really sorry for the double-post. I'm quite desperate and need my phone for work.
Since last post I've tried flashing N910FXXU1COH4_N910FH3G1COH3_H3G.zip through Odin from SamMobile and it did the same thing with rebooting constantly.
Then I've installed Kies and went to Tools -> Firmware Upgrade and Initialisation and gave it the model and S/N and it downloaded something and everything went all right, the phone reboots and I'm back in the same circle, it just shows me the splash screen(in some video's I've seen that after this procedure they get the splash screen and then the android bot with a progress bar, I don't get that, I only get the splash screen and reboot) and reboots.
I thought this was a last resort thing? Is the phone completely dead or is there something I can try?
Again sorry for the double-post.
Update: still no progress so I've contacted Amazon and they said to send it back so hopefully this works out in the end, no matter how annoying the waiting time will be, if you do have any suggestions on what I should try please let me know as I haven't posted the phone yet.

N910F stock crash and bootloop after 6.0.1 update

Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update

Samsung Note 4 N910F is not stuck in bootloop, still doesn't really boot

Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?

Categories

Resources