NOTE 4 910F ddi: mmc_read failed - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek

ask for a replacement

Can I check myself that is it mmc problem?

slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
use search, there are many threads that duscuss this issue:
http://forum.xda-developers.com/note-4/help/n910f-problems-emmc-read-fail-flashing-t3456721
http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821

slawekj74 said:
Can I check myself that is it mmc problem?
Click to expand...
Click to collapse
The best thing you can do is to flash another time the original firmware, adding the proper pit file for your model. This will repartition your internal memory. Worked for me on a completely dead 910f, so yours got more chance....
If after this steps the lags remains, only thing to do is asking for motherboard replace.....
Good luck

slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
Several threads exist on this issue and the conclusion we've come to in the T-Mobile Note 4 forums is replacement. In my experience, the issues got so bad that it rendered the phone unusable. Get it replaced under warranty while you still have it. Samsung denied my claim as I was out of warranty.

Phone has returned from service point - repaired. I will test it tomorrow

Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.

xhanatos said:
Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.
Click to expand...
Click to collapse
I held back myself from make my N4 rooted until Android 6 has appeared
So, mainboard has been changed and some parts of case ( very nice due to some scrapings on silver edge of phone).
New firmware was installed - XEF (France) instead of my previous DBT (Germany). Original CSC code is empty.

possible workaround
https://forum.xda-developers.com/note-4/help/workaround-mmcreadfailed-mmcwritefailed-t3564869

Related

[Q] Phone rebooting randomly - help needed

Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:

Stock SM-N9005 Restarting 4-5 times a day - need some advice

Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Do you have memory card installed? if so then scan you memory card for possible viruses.
Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse
Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh
syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?
Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C

[HELP] its Urgent,Important,why no one cansolve it??????

PLZ help me on this guys , im going mad on this
HOW TO SOLVE THE " DM-VERITY VERIFICATION FAILED NEED TO CHECK DRK FIRST " or when i install a stock rom this one first appears bUt not in reCovery " DEVICE DOESNT HAVE DRK , INSTALL DRK " ????????
it all happened after i deleted my imei then succesfully restored it with backup when downgrading from that god forsaken CM13 made by raymanFX (it was build 8 i think) , now OTAs and Security patches all face this issue in recovery when installing after being downloaded , now im in middle of nowwhere with no backup and ive tried everything but none works and im not a hacker nor an information thief just a member waiting for HELP... (SM-N910H)
:crying::crying::crying::crying::crying::crying:
! THERE IS NO OFFICIAL SAM CUSTOMER SERVICE IN MY CITY AND mobile merchants are not TRUSTWORTHY !
Someone told me that i need to find a cert file for my Phone and i found it , how is it related to DRK and what should i do with it??
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
yeah. try flashing samsung stock firmware with odin. have you done it
Sent from my SM-N920G using Tapatalk
YEP Odin flash is most of the time a good fix.
ankahuja said:
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
Click to expand...
Click to collapse
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
ArmanFGT said:
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
sudhakar35 said:
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
Click to expand...
Click to collapse
Thanks for the reply but the main problem is that any OTA that comes to note 4 i download them and the device says to restart to recovery to install the Update and i say yes but when it goes to recovery the recovery wont function well since it shows dm-verity error and supported API : 3 the update process fails to complete . My imei is as cool as always i havent had a problem with IMEI since i bought the phone
at least 10000 people have note 4 and none has had the problem ???? REALLY ?
seems like im pretty f***ed up
chappatti said:
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
Click to expand...
Click to collapse
dear chappati , according to that video i need a physical thing which is called a BOX and a software called GC PRO because that guy had my problem and fixed it with a clicking , but im reasearching for 5 months and nothing comes out . i need information PLZ
Hi, i used to had that problem too, when i first flash a custom rom to my N910G i back up my stock rom.. everthing including EFS.. after that then i wipe everything like normal procedure when u flash a rom. till then 1 day i wanna go back to stock rom i accidentally ticked EFS while i wanna restore that stock rom back up and then i thought it was nothing serious until i flash stock rom with odin and when i boot into stock recovery that dm-verity message was shown, did so much research but no luck. my n910G was on a Singapore firmware, that time it had a update i just try my luck by downloading the latest SG firmware and then that message was gone! m now already on MM no problems like that anymore
Deleted

Note 4 G910F Snapdragon weird issues / flashing and usage

Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk

O2U Note 4.... Broken?

So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.

Categories

Resources