Database Users

Error Flashing Modem: Secure Check Fail: mdm

I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.

AHLASSICH said:
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
Click to expand...
Click to collapse
Hey there, I'm trying to update my I337M's modem as well (I have a post in this forum) so I'm in the same boat as you. From the looks of it, it seems like you're not using the correct modem firmware. If you'd want to update I believe it's something like UMUEMK6 for our phones, I've tried looking around and I can't find it anywhere. Hopefully that offers some direction but I'm waiting to see as well since I'm having the same problem with Google ROMs as well (The data signal never works).

Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up

For some reason, yours is the only version of the mk6 modem file that worked for my i337m after I was on 4.3 GE and went to old MDJ modem to try sim unlock. Which didn't work, sigh... Thanks!
SimonPalmieri said:
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
Click to expand...
Click to collapse

@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.

jk2rd said:
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
Click to expand...
Click to collapse
Bootloader and modem are not tied together..... MK6 is the latest modem and works with 4.4.2 roms (for I337M), once the actual 4.4.2 update drops for i337m we will be able to update to that modem.

Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?

MK6
jk2rd said:
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
Click to expand...
Click to collapse
First you need to decide if you want to sim unlock the phone, still possible on mvluamg1, not possible on MK6. I would make sure you have a copy of modem.bin for mvluamg1 first, just incase. Then flash the MK6, I run MK6 on 4.4.2 GErom since we don't have a kitkat modem for i337m yet... once there is I will be updating.....
PS if you can find files that have md5 checksum, that is always good because then you can check the file to make sure it is complete. I had that issue flashing the MK6 modem, first file I downloaded failed in Odin, plus it had no md5 for me to check. Second one I donwloaded had the md5, which I checked and it flashed perfectly....

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*
Rogers is the only carrier who pushed this update, it was pulled shortly after, due to corruption. I had to spend literally ALL day downloading this. I downloaded it 7 times before i got a OTA zip that passes a CRC check and extracted properly. What a pain in the butt it is i had to convert my Telus device to Rogers fully down to modding the EFS to get this done.
Prerequisit: You must be on a 5.1.1 compatible TWRP as well as a 5.1.1 rom when flashing these packages or your going to get stuck in a binary miss match. While there is a fix for this with out the W8 5.1.1 odin packages, it takes a lot of musical flashing. So be sure to be on a compatible 5.1.1 rom, Kernel and TWRP first.
As always, you flash at YOUR OWN RISK. I will of course try to provide support if I am online, If you appreciate how much the pain in my butt was, and you didn't have to do this your self. Click Donate.
The Bootloader MUST be flashed via ODIN 3.10.X or higher. in the BL slot. Hence why its a tar. Sorry no flashables, Samsung locks the boot loader areas to everything but their own signed recovery, from their own signed update.zip
BO8H BL
BOI1 BL
BOI6 BL *LATEST*
The modem is TWRP flashable
BO8H Modem
BOI1 Modem
BOI6 Modem *LATEST*
You can get ODIN 3.10.6 HERE
Samsung USB Drivers HERE
Fingerprint confirmed working by my self. on custom 5.1.1 roms and stock.

You're my hero, lets have sex together

virulentt said:
You're my hero, lets have sex together
Click to expand...
Click to collapse
LOL the new "FIRST!"

-Mr. X- said:
LOL the new "FIRST!"
Click to expand...
Click to collapse
It works thanks a lot haha. No homo btw <3

Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?

anuben said:
Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?
Click to expand...
Click to collapse
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.

-Mr. X- said:
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.
Click to expand...
Click to collapse
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
redownload the Bootloader, your .tar could be corrupted.

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Yes i flashed it via BL. Whats your actual device.

Worked perfectly for me. So glad to have a working fingerprint scanner on a 5.1.1 custom rom. Thanks
Sent from my SM-G920W8

Easiest way to do it is just make sure the Bootloader is loaded on Odin first on your PC then reboot to recovery and flash the modem package, select reboot and choose Download so it reboots to download mode, plug the phone to usb and flash in Odin and you're done!
Sent from my SM-G925F

I'm now getting some new "not enforcing" red text during boot. Is that expected?

BlackRabbits said:
I'm now getting some new "not enforcing" red text during boot. Is that expected?
Click to expand...
Click to collapse
Yep that's normal.
Sent from my SM-G925F

-Mr. X- said:
Yes i flashed it via BL. Whats your actual device.
Click to expand...
Click to collapse
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3

I've been using Arter97's back-to-n0t3 v3 with his 3.5 kernel, SO SMOOTH I lose around 5 to 7% overnight. You guys should give it a try!
http://forum.xda-developers.com/galaxy-s6/development/to-n0t3-bring-larger-fun-to-flagship-t3179857
http://forum.xda-developers.com/gal...development/arter97-kernel-galaxy-s6-t3171246
*** Download links are on his website (careful, the 3.6 version of his kernel isn't for our device, use the 3.5 g920tw8 one ***
http://arter97.com/browse/S6/
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
that's not for the edge... you could brick your device flashing a non-edge bootloader to an edge one.

anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.

-Mr. X- said:
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.
Click to expand...
Click to collapse
holy fuk i shouldn't be doing drinking and flashing :silly: thank you though. appreciate your help...:good:

Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.

caanda45 said:
Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.
Click to expand...
Click to collapse
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I would flash TWRP on your 5.0.2 device as it sits, then i would choose your 5.1.1 rom of your liking. Put it all on your storage on the phone except the bootloader tar. Flash the rom, modem and what ever else in TWRP. then in the TWRP reboot options reboot directly to download/bootloader. and odin the bootloader. boot the device normally and you're good!
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader

-Mr. X- said:
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader
Click to expand...
Click to collapse
Perfect, I was on that rom for awhile with 5.0.2 and some stuff missing..So the best plan is
1. Re Root and Flash TWRP
2. Back up
3. Flash 5.1.1 Rom
4. Flash Bootloader with Odin
5. Flash Modem with TWRP
And then I should be good to go? Where does the Audio patch come in?
Any other suggestions or order to my plan?
Thanks again for your time and hard work!!!

Phone won't boot, even into recovery mode

Hi all, im desperate for help here!!
I flashed Dr Ketans Rom to my Note 4 a couple of days ago but decided to try to go back to stock today due to a bug with my email. Anyway, a long story short, my phone failed the flashing process with odin whilst trying to flas the latest stock firmware from sammobile and then my phone refused to start up again.
I now get a screen telling me the firmware up grade process went wrong but I cant even reboot into recovery to install anything else.
I have tried flashing both TWRP and Philz recovery but both just flash the title screen on and off but never load up.
I have tried 2 firmware versions from sammobile and both end in fail, it seems like I cant flash any firmwares with odin which is a right pain because I cant get to recovery to install a zip file....
Please help, Im sooooo stuck!
Edit - this is the log from Odin if it helps anyone... Ive now tried software 4.4.4 also but nothing works.
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.

0-0-0 said:
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
Click to expand...
Click to collapse
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.

sudburys said:
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
Click to expand...
Click to collapse
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.

0-0-0 said:
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
Click to expand...
Click to collapse
No probs...
Thanks for the try anyway

I9505 bootloader flash odin complete(write) error (SOLVED)

Okay so I was trying to update my bootloader and modem using the tutorial I found here. But odin refused to install it and left me with a softbricked device. Now I have tried to flash the new bootloader again, the old bootloader, changed pc, changed usb cord and port, tried heimdall but still not working. Now it starts to install the bootloader and odin log goes like this
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Any help?

It's possibly because the bootloader you are trying to flash is not compatible with your S4 model.
If you can't flash the bootloader separately, flashing a stock ROM package may work. Also, try a different Odin version and also another Windows.

Yeah I tried to flash the stock rom but the same thing happened. I have tried 3 different odin versions and 2 windows.

Could this be because I've changed my usb port? Odin seems to always disconnect my phone after failing and then reconnects again.

Google and download PIT file GT-I9505
Flash bootloader with pit file selected

@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.

Strephon Alkhalikoi said:
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Click to expand...
Click to collapse
It says Product name: GT-I9505

Good. The USB port on the device could cause this if it's damaged or defective. You want to check its connections in the device and also clean the port with a bit of rubbing alcohol to be safe.

Yes I got it solved. I don't know how but I think that the problem was that both usb cables I tried were damaged though they worked before. I tried third usb cable and the same error came up then I tried again and it flashed the stock succesfully. How can I mark this solved?

Go to your first post and change the title. If you can't do that, add a line to the post noting that the problem was resolved.

Note 3 stopped booting, goes straight to Download screen with mmc_read failed message

This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
My trusty Galaxy Note 3 N9005 32GB has been giving me a few minor file errors recently, so I re-installed from a nandroid backup (ROM is MagMa NX VX PCE 6.0.1) with Phantom kernel) and it's been great for a few weeks now, performing better than ever in fact.
However yesterday, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."
I can't get into Recovery or use ADB, so I ran Odin on my PC and it showed the device as Added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin started sending the TWRP .tar file normally, it quickly reported "Get PIT for mapping ... There is no PIT partition". The phone screen showed "UDC START" then "MMC: mmc_read fail". The USB port and USB cable are the same ones I've been using for some recent adb pull backups so they should be OK.
I tried installing a new PIT file (first from a previous backup of my own setup, and then from generic versions for this device) but Odin with AutoReboot, Re-Partition, and F.Reset Time ticked showed:
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone showed:
UDC START
MMC: mmc_read fail
I then tried downloading a 4files repair installation of a stock Lollipop ROM (the most recent I could find for this device, N9005ZSUGPJ2) and used Odin to install the included PIT, AP, BL, CP and CSC files, with Nand Erase All selected too:
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time, the phone showed:
UDC START
MMC: mmc_read fail
ERASING USERDATA PARTITION...
I could really do with some expert help or advice here from anyone who knows more about these things than I do... or do I have an unexpected brick on my hands? Thanks!
Andre

I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
here is the procedure you have to follow...
PLEASE.....DO NOT skip ahead, just follow my instructions in sets,
Here are the Files you NEED to download:
Odin3 v3.10.zip
CHARGE the device to 100% Battery BEFORE beginning!
Download and extract the Files.
Open ODIN, place each of the Files in corresponding boxes:
BL = BL
AP = AP
CP = CP (MODEM)
CSC = CSC
Please select these Check-boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
START!!
After it reboots, WAIT 10 Minutes, Skip the Wizard and perform a Factory Data Reset!

rayman95 said:
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
Click to expand...
Click to collapse
Which phone version, or which 4files?
Phone is a Galaxy Note 3 N9005 (UK 32GB).
File was from https://zfirmware.com/download-samsung-repair-firmwares/ , version http://www.mediafire.com/file/9ux01...3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
I was hoping to be able to use this device until the Note 10 is released, but maybe I'll have to settle for an S10+. Problem is, I prefer my nice Note 3 to anything they have released since (removable battery, no stupid curved-edge display, proper physical front buttons away from the main screen, a bigger - OK, wider - display than anything since, etc)
Andre

andrewilley said:
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
Click to expand...
Click to collapse
From my own experience, this problem is a manufacturing defect that affects a lot of samsung devices produced from Q3 of 2014 until Q2 of 2015. The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
However, I managed to fix a Galaxy S5 with the method I already described. And that has been presented as a momentary solution by several xda users, like here.
I wrote : momentary solution because this error is definitely a hardware failure, a fixed device will only work for a random period then the problem will get worse until the device become completely unusable.
Fortunately, you can buy a new motherboard for less than 30euro. And that's what I recommend you to do.

andrewilley said:
Galaxy-Note3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip[/url] . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
Andre
Click to expand...
Click to collapse
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware

zlazaar said:
The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
Click to expand...
Click to collapse
I've been noticing a few file-read errors over the last 5 months or so, which I put down to bad blocks even though e2fsck -cfv showed zero errors. I thought a reformat and nandroid restore had fixed it, but obviously if the problem is lower down that might just have been delaying the inevitable. I suspect that installing a new mobo would not really be a good long-term plan as that could just as easily have the same issue (as they'll all be 4+ years old by now).
rayman95 said:
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
Click to expand...
Click to collapse
I'll try the KitKat version (normally I'd look for a BTU version, but beggars can't be choosers as the saying goes). If I can at least get it running for now and restore my backup via TWRP then I can do a more relaxed and controlled switchover to an S10+.
Andre

Whatever I try, I can't get a new PIT file to re-partition the memory:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2252 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
Phone shows MMC: mmc_read fail
Does anyone have a known good PIT file for the UK Note 3 N9005 32GB, along with a matching BL/AP/CP/CSC combo (any ROM version would do) that they would be willing to either upload or point me to?
Thanks,
Andre

I guess I probably should treat this device as a brick now and get it replaced, no other suggestions?
Andre

sammobile forum ??

JJEgan said:
sammobile forum ??
Click to expand...
Click to collapse
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre

andrewilley said:
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
Click to expand...
Click to collapse
i send you my french files....

take here my files...

Thanks, I'll download and give them a try when I get back on home wi-fi. I fear I'll probably get the same results, but at least I'll have tried everything before giving up on it.
Andre

File downloaded, thank you. There doesn't seem to be a matching PIT file in there though, just the BL, AP, CP and CSC. Is that correct? As stated earlier in the thread, the PIT seems to be corrupted on my device, so was hoping for all 5 files to match...
Andre

rayman95 said:
take here my files...
Click to expand...
Click to collapse
I did try the 4files in your ZIP, but without a new PIT file I got the same partitioning error as before:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Andre

the pit HERE...
good luck..

rayman95 said:
the pit HERE...
good luck..
Click to expand...
Click to collapse
Many thanks for all your help, but still dead even with the correct PIT I'm afraid.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this phone is on its way to the Great Home for Expired Technology in the Sky.
Andre

Just read some user not this phone replaced eMMC chip.
From Aliexpress