Hi guys. Like a bunch of other threads around here, my Note 4 (N910F) was pretty much the perfect device until about 4 days ago at which point it started rebooting a lot. At first I suspected an app update to be corrupt or something and the cause of this, so I cleared cache, but no joy. It also then began to hang whilst booting on occasion, so I did a factory reset. No joy. Since then things have gotten worse, occasionally it will boot into recovery mode, sometimes it'll say it's in download mode etc. I've had a screen when it bumped me into Odin Mode that said mmc_read failed. I've had kernel panics where it complained about EXT4-fs throwing errors. Okay, so the internal storage has gone bad, I understand that. It's 22 months old, has a 24 month warranty.
However... as per the thread title, when I get into Odin mode, it says:
Code:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
Downloading...
Do not turn off target!!
Thing is, I've never rooted this phone. I've never installed anything but OTA firmwares. I've considered it certainly, but there was just no need to like there was in past generations. I've never installed any cracked apps. On the occasions when I can get the phone to boot, and go to Settings > About Device > Status, it tells me that it's official. So why is Odin saying it's Custom? And are Samsung going to refuse a warranty repair because of this? I'm also not entirely clear on what System Status in Odin reflects. Is it meant to be the current firmware, or is it a lifetime counter that says whether it's ever had another firmware on it. The thing that puzzles me is that I got the phone new and I really, really mean it when I say it's always been stock and official. My baseless theory is that if it can't boot, it can't read some blocks so can't properly hash the filesystem, hence saying it's custom. On occasions where it can boot, it can read those blocks and can complete some kind of hash.
I just want to get it fixed, but I suspect I'm not going to get them to fix it under warranty.
Any thoughts?
EDIT:
It just occurred to me that at no point had I deliberately gone into download mode myself, I'd only ever been in it when it couldn't boot. So I tried it. This is what it shows:
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
Downloading...
Do not turn off target!!
This kind of backs up my theory that the "system status: custom" bit is coming from it not being able to read blocks on the eMMC when it starts.
Related
Hello everyone I have a Note 3 SM-N9005 which is already rooted and had custom rom working fine.But since i bought my phone from eBay seller it won't work in GSM mode.It used to work fine in WCDMA mode but not on AUTO and GSM mode and showed not registered on network.
Someone told me in XDA that i need to go to a repair shop which has SPT BOX.
So i found one for $17 but he is saying that my phone got SOFT BRICKED in the process.CAN you guys help me to get back to normal..
He is saying that flashing the stock rom in odin will fix the problem.Plz if someone can help me out..
When phone is turned it looks something like this..
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, A2, A3, P3
WRITE PROTECTION: ENABLE
UDC START
Sooo it's about 3 days that I'm having problems with my Samsung Note 4.
The phone is about 6 months old and I tried to root it when I bought it without success, so I put the original firmware again (As after successful (or insuccessful?) rooting the phone keept bootlooping all the time). With a few tricks (that I cant remember) i made it working again.
3 days ago I was charging the phone while browsing on google chrome and the phone suddenly turned off and went in a bootloop. I tried installing the original firmware again (Odin says "PASS!" at the end of the process) but it still wont go work. Tried to wipe cache and data, still nothing. Samsung Kies wont recognize my phone to do an emergency recovery.
Another strange thing is that I can enter in download mode but not in recovery mode.
"ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START"
That's what it says in download mode and have no idea what it means.
Anyone can help? Im about to freak out
Thanks in advance
Anyone?
Still none? Im using my phone as paperweight right now..
alpacino15 said:
Still none? Im using my phone as paperweight right now..
Click to expand...
Click to collapse
Are you using genuine usb cable? it's a must. Also do NOT use USB 3 port
Couple weeks back I rooted my device and worked for a while until it restarted making it stuck on the logo screen, I tried flashing the firmware with Odin and it says it was successful but when my phone restarted it was still stuck on the logo screen, I don't know if this is any help but when Its on download mode in the top left it says
Current binary: Samsung official
System status: Custom
FAP lock: On
Qualcomm secureboot: Enable (CSB)
RP swrev: S1, T1, H1, R1, A1, P1
I've tried searching up online and tried different versions of Odin but yet nothing works, it still says successful but still stays on the logo screen, if there's any way to fix it please let me know
cvisio said:
Couple weeks back I rooted my device and worked for a while until it restarted making it stuck on the logo screen, I tried flashing the firmware with Odin and it says it was successful but when my phone restarted it was still stuck on the logo screen, I don't know if this is any help but when Its on download mode in the top left it says
Current binary: Samsung official
System status: Custom
FAP lock: On
Qualcomm secureboot: Enable (CSB)
RP swrev: S1, T1, H1, R1, A1, P1
I've tried searching up online and tried different versions of Odin but yet nothing works, it still says successful but still stays on the logo screen, if there's any way to fix it please let me know
Click to expand...
Click to collapse
I have same problem
cvisio said:
Couple weeks back I rooted my device and worked for a while until it restarted making it stuck on the logo screen, I tried flashing the firmware with Odin and it says it was successful but when my phone restarted it was still stuck on the logo screen, I don't know if this is any help but when Its on download mode in the top left it says
Current binary: Samsung official
System status: Custom
FAP lock: On
Qualcomm secureboot: Enable (CSB)
RP swrev: S1, T1, H1, R1, A1, P1
I've tried searching up online and tried different versions of Odin but yet nothing works, it still says successful but still stays on the logo screen, if there's any way to fix it please let me know
Click to expand...
Click to collapse
Are you sure you are flashing right firmware ?
Also try to do a factory reset in recovery
Hi there,
I wanted to put Cyanogenmod on an J500FN and went straight to Odin without enabling developer options Why? Bc I am dumb.
Since Odin failed I cant even get into recovery mode. Can't enter a password. Can't do anything, really.
Normal start and Recovery Mode start result in the screen showing the Android logo and then turning yellow/green before fading to black.
Download mode is working. I tried Kies, Smart Switch, Odin. Each time it fails and a read line on the phone appears ("Mom Mode. Can't Download"). Using stock firmware from Sammobile results in the same outcome.
Download mode says:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP Lock: Off
WARRANTY VOID: 0x0
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
MOM MODE. CAN'T DOWNLOAD (<--- Added in red each time Odin fails)
Is the phone toast?
Thanks!
1.Try doing wipe data before flashing the firmware.
2.Try flashing Stock LP firmware.
3.Try to flash using Heimdall, which doesn't have some restrictions that Odin has.
4.Nand erase all option in odin might help a bit.
5.If none of these works i guess you need to flash the device using Z3x box or jtag. Go ye visit a samsung service and hopefully they manage to fix your problem.
JayFivehundred said:
Hi there,
I wanted to put Cyanogenmod on an J500FN and went straight to Odin without enabling developer options Why? Bc I am dumb.
Since Odin failed I cant even get into recovery mode. Can't enter a password. Can't do anything, really.
Normal start and Recovery Mode start result in the screen showing the Android logo and then turning yellow/green before fading to black.
Download mode is working. I tried Kies, Smart Switch, Odin. Each time it fails and a read line on the phone appears ("Mom Mode. Can't Download"). Using stock firmware from Sammobile results in the same outcome.
Download mode says:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP Lock: Off
WARRANTY VOID: 0x0
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
MOM MODE. CAN'T DOWNLOAD (<--- Added in red each time Odin fails)
Is the phone toast?
Thanks!
Click to expand...
Click to collapse
Send it to me if you are gonna throw it away
JayFivehundred said:
Hi there,
I wanted to put Cyanogenmod on an J500FN and went straight to Odin without enabling developer options Why? Bc I am dumb.
Since Odin failed I cant even get into recovery mode. Can't enter a password. Can't do anything, really.
Normal start and Recovery Mode start result in the screen showing the Android logo and then turning yellow/green before fading to black.
Download mode is working. I tried Kies, Smart Switch, Odin. Each time it fails and a read line on the phone appears ("Mom Mode. Can't Download"). Using stock firmware from Sammobile results in the same outcome.
Download mode says:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP Lock: Off
WARRANTY VOID: 0x0
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
MOM MODE. CAN'T DOWNLOAD (<--- Added in red each time Odin fails)
Is the phone toast?
Thanks!
Click to expand...
Click to collapse
have you read this post https://forum.xda-developers.com/galaxy-j5/how-to/how-to-unbrick-galaxy-j5-sm-j500h-t3536287
100% it s something that you can do to fix it .. Just search hard i had problems like this on many phones ( not booting and things like that) and i fixed them after some google .. all i can say is Good Luck mate Ps:don t throw it..
EDIT
My bad didnt read your full post.
I was gonna mention Smart_Switch_PC_Setup
Thanks everyone for your comments and suggestions
I have tried everything I could think of and read about. Unfortunately, there was no debrick image for the model I need.
Ultimately, after days of extensive searching and trying, I give up at this point.
Either way, great forum, and thanks again for all the comments!
JayFivehundred said:
Thanks everyone for your comments and suggestions
I have tried everything I could think of and read about. Unfortunately, there was no debrick image for the model I need.
Ultimately, after days of extensive searching and trying, I give up at this point.
Either way, great forum, and thanks again for all the comments!
Click to expand...
Click to collapse
Send it to me
Can someone help me please. My phone is in ODIN mode, I'm very dumb when it comes to phones and computers, can anyone offer a solution.
ddi: mmc_read failed
ODIN MODE
Product name: SM-G360T1
Current Binary: Samsung official
SystemStatus: custom
FAO Lock: on
Qualcomm secure boot: enable (csb)
AP Sswrev: s1, t1, h1, a1, a1, p1
At first change the battery or buy a new one.
After its not work flash stock firmware
I know this thread is old but i can help you
First of all maybe the battery is so drained it cant read the nand due to lack of energy. Try charging it for a few hours or overnight. If it dosent do anything at all, change the battery. If it still dosent work, go to the next step
If the above method dosent work, Try flashing the stock ROM using Odin.
If it still dosent work, your device is bricked