Here is the solution to eMMC error

Search This thread

juandante

Member
Jan 4, 2018
44
9
Hello everyone,

I was pretty tired of the eMMC error, and I created a script that completely annihilate this error.

This error is due to the phone heating up, and the fact that custom kernels (maybe even the original kernel) don't read the sensors correctly and throttle the phone correctly. This script monitors the battery and all the CPU sensors and when it is higher than 82°C, throttle the phone.

It was tested on AEL Kernel that supports « Hard limit » command, but this script can be adapted on any other kernel. You may need busy box. You must root to run this script.

Must be placed in init.d folder.

You simply copy each script, and for example with Kernel Audiutor, create a new init.d and paste the script with the correct title.

script called cpu_temperature_daemon :

Bash:
#!/system/bin/sh
argu=$1
sleeptime=15
if ! [[ $argu = start ]] then exit ; fi
lock=0
while true;
do
maxnumb=0
cpuiscool=0
temp=$(cat /sys/class/thermal/thermal_zone*/temp)
tempbat=$(cat /sys/class/power_supply/battery/batt_temp)
if ((tempbat>410)) then if [[ $lock = 0 ]] then lock=1 ; sleeptime=7 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 65 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 65 > /sys/module/msm_thermal/parameters/limit_temp_degC ; fi ; fi
for line in $temp; do if ((line>78)) then if ((line<120)) then if [[ $lock = 0 ]] then lock=1 ; sleeptime=7 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 65 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 65 > /sys/module/msm_thermal/parameters/limit_temp_degC ; fi ; fi ; fi ; if ((line>10)) then if ((line<110)) then maxnumb=$(($maxnumb+1)) ; fi ; fi ; if ((line>10)) then if ((line<75)) then cpuiscool=$(($cpuiscool+1)) ; fi ; fi ; done
if [[ $maxnumb = $cpuiscool ]] then if ((tempbat<411)) then if [[ $lock = 1 ]] then lock=0 ; sleeptime=15 ; chmod 644 /sys/devices/system/cpu/cpu1/online ; echo 1 > /sys/devices/system/cpu/cpu1/online ;chmod 444 /sys/devices/system/cpu/cpu1/online ; echo 82 > /sys/module/msm_thermal/parameters/limit_temp_degC ; echo 82 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; fi ; fi ; fi
sleep $sleeptime ;
done

script called cpu_temperature_daemon_start to place in the same directory /system/etc/init.d/ :

Bash:
#!/system/bin/sh
numb=$(pgrep -lf cpu_temperature_daemon | wc -l) ; if [[ $numb = 1 ]] then exit ; fi
echo 75 > /sys/module/msm_thermal/parameters/core_limit_temp_degC ; echo 75 > /sys/module/msm_thermal/parameters/limit_temp_degC
nohup /system/etc/init.d/cpu_temperature_daemon start &


There is absolutely no more eMmc errors on the Note 4 that I tested. Of course, if you already have the error, script will not fix it. It will simply prevent a clean phone from having it by preventing overheat in monitoring all sensors. No big battery hog (insignificant). The script works by monitoring the all the sensors and reducing slightly CPU performance when the phone CPU is to hot (CPU > 82°C), or battery temp > 41°C.
 
Last edited:

juandante

Member
Jan 4, 2018
44
9
It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat
 
  • Like
Reactions: jonnyprogamer

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat
How do i fix a phone that has it? The "put cardboard under EMMC" fix lasted for like a week, my phone still works thanks to that Fix by using WakeLock (already it's been 8 months i think), but i don't want to use WakeLock anymore because it drains the battery a lot, plus since the eMMC is faulty the writing speeds are like 40MB/S so the phone is significantly slower.

I heard that this error was caused by Android 6 and immediately after i got the phone i flashed Android 5 stock, still i got like 6 months of use before this error (mostly only using Youtube and Discord).

Can i get the eMMC replaced to fix this? or i need an entire new motherboard? this phone is still really fast and usable even in 2023 with Android 5, but this error is really annoying and it makes the phone almost unusable, thanks.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat
If i end up getting another used Note 4 i will downgrade to LL and immediately apply your script
 

juandante

Member
Jan 4, 2018
44
9
If i end up getting another used Note 4 i will downgrade to LL and immediately apply your script
Yes, you simply have to copy paste each script in the /system/etc/init.d/ directory
I have put the correct tags and the script is now correctly highlited in my first post so you can easily see what it does.
Maybe for some kernels, you will need to adapt it.
Anyway, I can confirm to you that this limits dramatically the eMMC errors because the phone doesn't anymore overheat.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
Yes, you simply have to copy paste each script in the /system/etc/init.d/ directory
I have put the correct tags and the script is now correctly highlited in my first post so you can easily see what it does.
Maybe for some kernels, you will need to adapt it.
Anyway, I can confirm to you that this limits dramatically the eMMC errors because the phone doesn't anymore overheat.
Ok thanks, but is there anyway to fix this error on a Note 4 that already had it? maybe reballing the eMMC?
I don't think it's worth to me to get another used Note 4, because i don't know what the previous owner might have done with it and it might already be dead to be honest.
I think that reballing the eMMC / swap the motherboard is the only way to truly fix this (and then use your script or downclock the CPU to keep the phone safe)
 

juandante

Member
Jan 4, 2018
44
9
Ok thanks, but is there anyway to fix this error on a Note 4 that already had it? maybe reballing the eMMC?
I don't think it's worth to me to get another used Note 4, because i don't know what the previous owner might have done with it and it might already be dead to be honest.
I think that reballing the eMMC / swap the motherboard is the only way to truly fix this (and then use your script or downclock the CPU to keep the phone safe)
You must have high end specialized soldering tools to fix the problem. Anything less than that will just fix the issue couple of weeks only if you are very lucky. You will be more lucky to buy a second hand Note 4 because most people generally speaking sell it because they bought a new phone, not because of the eMMC error due to heavy phone usage... If you really want to save money, just buy a new motherboard (it's somewhat cheap today).

Also, I think I had a eMMC symptom once (slow phone and the Note 4 was hardly booting), I managed with luck to boot the phone then applied the script, waited 1 day with the phone keeped on, and next the phone stayed somewhat fully usable for 12 months (with some random reboots now and then). So I think if you apply the script enough early when you get the first bad eMMC sign it is somewhat enough early to "revert" the issue if I could say so. I. E. The soldering is somewhat damaged and provoke random reboots but the script will prevent the phone from heating and damage even more the soldering.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
You must have high end specialized soldering tools to fix the problem. Anything less than that will just fix the issue couple of weeks only if you are very lucky. You will be more lucky to buy a second hand Note 4 because most people generally speaking sell it because they bought a new phone, not because of the eMMC error due to heavy phone usage... If you really want to save money, just buy a new motherboard (it's somewhat cheap today).
Thanks, i guess i will try to find another Note 4, i might know someone that knows how to do BGA reballs, but even then i think that the issue are not the solder balls under the E-MMC.
Because it doesn't make sense, un-leaded solder melts at about 215C, and the EMMC isn't a big chip (so it's not like a GPU which can ""stress"" the solder balls when it gets hot and then cold).

For this reason alone it can't cause any cracks in the balls (unless you drop the phone but then again it's pretty unlickely to happen), what im thinking is that the EMMC chip just dies, it's not the solder beneath it, it's either a fault in the chip itself or a bug which gets triggered by something (like the Note 1 Superbrick).

Maybe we should take apart our phones with the issue, check the model number and report it here, probably those will be the fauly chips (this issue happened on the 360 and PS3 as well, everyone saying "it's the solder" and instead it was the GPU itself which dies because of the heat-cooling cycles).
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
Also the stock rom doesn't have init.d support.
I know that PimpMyRom adds init.d support (tested on old chinese Android ICS tablet), i don't know if it works with Lollipop tough.

I just got my emmc reballed, when i get my phone back im gonna reflash latest 5.1.1 Or CM and use this script.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
We will see if it lasts since the reball has been done with leaded solder, if it does not then it means that the fault was (and still is) the EMMC chip all along :=>
 

dave678

Senior Member
Aug 17, 2019
465
47
I know that PimpMyRom adds init.d support (tested on old chinese Android ICS tablet), i don't know if it works with Lollipop tough.

I just got my emmc reballed, when i get my phone back im gonna reflash latest 5.1.1 Or CM and use this script.
Oh I have a brand new Sprint Note 4 running Kitkat and a Tmobile Note Edge running Kitkat
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
Android 4.4 stock uses the less resources of all but it's not smoother / faster than LL

Android 5.0.1 IS faster / smoother than 4.4, but uses more resources and it isn't optimized + very bad battery usage

Android 5.1.1 is the best stock from what i tested, less resources than 5.0 and good battery usage, also compatible with most apps from today.

Android 6.0.1 stock runs the worst (and according to a lot of people it was making the Emmc quickly because of the new hibernation when you turn off the display)


My reccomendation would be to either use stock Samsung 5.1.1 ROM or a Custom ROM (Cyanogenmod, Lineage, etc...)
 

dave678

Senior Member
Aug 17, 2019
465
47
Android 4.4 stock uses the less resources of all but it's not smoother / faster than LL

Android 5.0.1 IS faster / smoother than 4.4, but uses more resources and it isn't optimized + very bad battery usage

Android 5.1.1 is the best stock from what i tested, less resources than 5.0 and good battery usage, also compatible with most apps from today.

Android 6.0.1 stock runs the worst (and according to a lot of people it was making the Emmc quickly because of the new hibernation when you turn off the display)


My reccomendation would be to either use stock Samsung 5.1.1 ROM or a Custom ROM (Cyanogenmod, Lineage, etc...)
You have the F model which is hard to find on Ebay and you can yo yo between different firmware. The closest model to the F would be the W model which can also yo yo between different firmware. My model cannot do that as once you go up to 5.1.1 you can kiss goodbye the ablity to downgrade to Kitkat. I have it as a collector's item basically. It's not my daily driver as it wouldn't work on my carrier anyways.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
You have the F model which is hard to find on Ebay and you can yo yo between different firmware. The closest model to the F would be the W model which can also yo yo between different firmware. My model cannot do that as once you go up to 5.1.1 you can kiss goodbye the ablity to downgrade to Kitkat. I have it as a collector's item basically. It's not my daily driver as it wouldn't work on my carrier anyways.
Ah i see, well i got mine from a local online marketplace here in Italy (Subito), before i bough it on Ebay and it was "brand new", but it turns out it was just the SM-N910V version with the F firmware (found out quickly because US bands aren't the same in Italy, so i had connection issues) so i did a refund.

If you're in US yea i think it's going to be pretty hard to find an Europe model.
I use mine as daily driver, SD card, removable battery, IR blaster, easy to take apart, it's still a really good phone.
 

dave678

Senior Member
Aug 17, 2019
465
47
Ah i see, well i got mine from a local online marketplace here in Italy (Subito), before i bough it on Ebay and it was "brand new", but it turns out it was just the SM-N910V version with the F firmware (found out quickly because US bands aren't the same in Italy, so i had connection issues) so i did a refund.

If you're in US yea i think it's going to be pretty hard to find an Europe model.
I use mine as daily driver, SD card, removable battery, IR blaster, easy to take apart, it's still a really good phone.
I'm curious as to why the S5 doesn't suffer from the emmc issues as the Note 4 Snapdragon models since it also uses Emmc 5.0 like the Note 4.
 

jonnyprogamer

Senior Member
Jun 9, 2021
83
1
15
I'm curious as to why the S5 doesn't suffer from the emmc issues as the Note 4 Snapdragon models since it also uses Emmc 5.0 like the Note 4.
No idea, either it's actually the solder (doubt it, unleaded solder is more prone to cracks and breaking but melting temp is much higher than what the phone will allow) or buggy firmware / bios from samsung (already happened with Samsung Galaxy Note 1 with the Superbrick bug)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    It will happen eventually, it is due to the phone overheating (it is not just heating, it is overheating due to the sensors not correctly reporting temperatures) so even opening Facebook will make it overheat