Database Users

[Q] Bricked or not ? MMC: mmc_read fail. I'm afraid !

Hy, I own an S5 G900F. I flashed a stock rom latest version then my S5 root before flashing a rom Omega 2. Everything worked perfectly until I decided to change my sdcard having taken care to move all the files present on my old sd card on news.
At start of my S5 nothing worked, I have the screen that lights up with the SAMSUNG GALAXY S5 logo, powered by ANDROID but the top right I have the following message in red: kernel is not enforced seandroid and yellow: set warranty bit kernel.
I can not switch to recovery since disappeared, I just can enter download mode.
With odin so I tried to flash my S5 with stock rom (XEF-G900FXXU1ANE2-20140519102224).
Here is the odin message when I load this rom:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> 900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully
<OSM> ..
<OSM> Leave CS.
My S5 is well recognized by odin, it tells me blue com port 3 and
<ID:0/003> Added!
Top right of the screen of my S5 I have these messages:
ODIN MODE
PRODUCT-NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
LOCK REACTIVATION (KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CBS)
SWREV RP: S1, T1, R1, A1, P1
UDC: START
I run flash with odin:
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
The flash stops with S5 on the screen messages:
MMC: mmc_read fail
ODIN: flash read failure
I do not know what to do! Is it a hardware brick or a simple software problem??
Thank you for trying to help me if it is possible. I hope to have been clear
best regards,
Sorry for my english, this is a google translation

Not bricked but you need to flash a pit file along with the firmware, look here http://forum.xda-developers.com/showthread.php?t=2737448 for the correct pit file or how to extract one if yours isn`t listed (need root for that).

Thank you for your quick response but I already tried to flash the pit with odin without success always with the same message MMC: mmc_read fail etc ...
SM-G900F_pit_16GB.zip (fail)
SM-G900F_pit_16GB_SER.zip (fail)
SM-G900F_pit_16GB_ETL.zip (fail)

Something, some glitch apparerently corrupted your kernel. And that (probably subsequently) corrupted your partition structure. You are soft bricked at this point.
As gee2012 suggested, you now need to flash both the PIT and a full stock image. Stop trying to flash random PIT files or you may end up hard bricked. You need to identify the correct PIT and use that one. The PIT file should match your phone model, original carrier (i.e. match your baseband) and ROM size.
Flash the correct PIT in conjunction with a full stock Odin image from the matching carrier. Note that stock firmware is flashed as a tar file, but the PIT file needs to be flashed as a PIT file, if you are trying to flash it while it's still zipped that alone will cause it to fail.
.

i having the same problem
i'm having the same problem with my sm-g3502L, i have the corect pit file and the correct rom, but always failed, please someone help me, its very important

MMC: mmc_write fail ... need your help

Forgot my S5 provided with Omega Software ... well everything went wonderfully.
After plugging in the charger it out and never came back on.
I'm still in the download mode and in the TeamWin recovery. He shows me but as storage in the system "0".
E: can not mount etc ...
Have naturally sought and found some, but was not doing the right thing.
I have tried so far:
-different Odin versions and various PIT
with the version Odin307 running at least the PIT file in the download mode by (download bar in the mobile phone but mmc_write with message fail)
Firmware July G900FXXU1ANG2_G900FDBT1ANG2_G900FXXU1ANG2_HOME.tar --- same message.
KNOX is set to 0x1 (4)
Odin:
<ID: 0/004> initialzation ..
<ID: 0/004> Get PIT for mapping ..
<ID: 0/004> Firmware update start ..
<ID: 0/004> aboot.mbn
<ID: 0/004> NAND WriteStartDocument !!
<ID: 0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
appears in the display as always MMC: fail mmc_write
I urgently need your support and perhaps one with the same problem and a suitable solution
Thx
What to do and in what order and what files I need I need?

Another bootloop issue

Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy

Hello again:
Zero replies, did I omit important information in my first request -- or am I just rehashing previous inquiries about boot loop problems? (I have read through all posts relating to boot loops but found no answers that solved the to write to Nand failures). Forgive me if it's here and I simply didn't recognize it. . .
So (succinctly) why might Odin fail to write when attempting to reload the original firmware: . . . NAND Write Start!! . . . FAIL! (Auth) . . .Complete(Write) operation failed. . . .All threads completed. (succeed 0 / failed 1)
What might I be doing wrong, or what might I try instead?
Thanks again
flyyboyy said:
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Click to expand...
Click to collapse

Same thing with me.. patience gets you through it..
The same thing happened to me, same phone and same contract carrier (Sprint).
I bought my phone from a third party who apparently restores it to near-mint condition. The OS it had was one of the first releases of 6.0 /marshmallow. I tried downgradingit back to 5 / lollipop because i heard that call recording was still enabled with that OS.
I used Odin versions 3.7 thru 3.10 i believe and flashed every version of 5 that was listed on sam mobile and samsung 's site and all of them either failed to initiate- citing the same readings and failure reasons in odin that you mentioned - or they "succeeded" and resulted in boot loops.
I also failed to flash any of the earlier ROM versions of android 6 than the one my SM-G900P phone came with.
Finally, i succeeded in flashing 2 types of ROMS, the version of 6 my phone started with, then subsequently the most recent version released earlier in march 2017 (this month).
Conclusion: i believe the order that you flash these roms for our model phone with our carrier matters. Flash your phone with ROM images from the version that it came with, and continue sequentially and chronologically until your boot screen finally shows something other than that lovely little sprint logo
Good luck with your son's phone, and please let us k ow how it goes..... as i think this may be a recurring theme we may see more often in the future. I imagine the problem lies with either odin, samsung sm-g900p, or the sprint/cdma ROMa we're dealt.
-Rob

Have you tried samsung kies yet? Odin is for rooting your phone. Samsung kies will put updated firmware in your phone. I have used it several times in the past on a sam phone. It will work. Its from samsung company.

G960F bricked odin

Hi guys!!
flashee the bootloader / modem of project alice by means of TWRP and once done that the phone was restarted but it did not advance of the bootloop.
I tried to flash the stock firmware by means of odin but I see several fails.
<ID: 0/005> Added !!
<ID: 0/005> Odin engine v (ID: 3.1301) ..
<ID: 0/005> File analysis ..
<ID: 0/005> Total Binary size: 5894 M
<ID: 0/005> SetupConnection ..
<ID: 0/005> Initialzation ..
<ID: 0/005> Set PIT file ..
<ID: 0/005> DO NOT TURN OFF TARGET !!
<ID: 0/005> Get PIT for mapping ..
<ID: 0/005> Firmware update start ..
<ID: 0/005> NAND Write Start !!
<ID: 0/005> SingleDownload.
<ID: 0/005> sboot.bin
<ID: 0/005> FAIL!
<ID: 0/005>
<ID: 0/005> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the vematana download mode the following appears:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G950F
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
RMM STATE: Prenormal
FAP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = S2MM005 hw: 6 boot: 7 main: 43
CARRIER_ID: TCE
WARRANTY VOID: 1 (0x030c)
RP SWREV: B: 3 K: 2 S: 2
DID: 030d0e321b02
EVT 1.1
LOT_ID = NBDVT
CHIP_ID = 030d0e321b02
nASV_Table_Version: 8
nASV_Group_CPUCL0: 4
nASV_Group_CPUCL1: 6
nASV_Group_G3D: 1
nASV_Group_MIF: 6
nASV_Group_INT: 6
nASV_Group_CAM_DISP: 6
nASV_Group_CP: 6
nASV_Group_PMIC: 0
nASV_Group_PMIC_CP: 0
PMIC_ID = 2 (e4)
LPDDR4 manofacturer = samsung
LPDDR4 process see = D18
LPDDR4 size = 4g
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 3, BINARY: 1
I have tried everything but I always appear fails.
I would really appreciate if you could support me with this, I am desperate.

Lavachita said:
Hi guys!!
flashee the bootloader / modem of project alice by means of TWRP and once done that the phone was restarted but it did not advance of the bootloop.
I tried to flash the stock firmware by means of odin but I see several fails.
<ID: 0/005> Added !!
<ID: 0/005> Odin engine v (ID: 3.1301) ..
<ID: 0/005> File analysis ..
<ID: 0/005> Total Binary size: 5894 M
<ID: 0/005> SetupConnection ..
<ID: 0/005> Initialzation ..
<ID: 0/005> Set PIT file ..
<ID: 0/005> DO NOT TURN OFF TARGET !!
<ID: 0/005> Get PIT for mapping ..
<ID: 0/005> Firmware update start ..
<ID: 0/005> NAND Write Start !!
<ID: 0/005> SingleDownload.
<ID: 0/005> sboot.bin
<ID: 0/005> FAIL!
<ID: 0/005>
<ID: 0/005> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the vematana download mode the following appears:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G950F
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
RMM STATE: Prenormal
FAP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = S2MM005 hw: 6 boot: 7 main: 43
CARRIER_ID: TCE
WARRANTY VOID: 1 (0x030c)
RP SWREV: B: 3 K: 2 S: 2
DID: 030d0e321b02
EVT 1.1
LOT_ID = NBDVT
CHIP_ID = 030d0e321b02
nASV_Table_Version: 8
nASV_Group_CPUCL0: 4
nASV_Group_CPUCL1: 6
nASV_Group_G3D: 1
nASV_Group_MIF: 6
nASV_Group_INT: 6
nASV_Group_CAM_DISP: 6
nASV_Group_CP: 6
nASV_Group_PMIC: 0
nASV_Group_PMIC_CP: 0
PMIC_ID = 2 (e4)
LPDDR4 manofacturer = samsung
LPDDR4 process see = D18
LPDDR4 size = 4g
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 3, BINARY: 1
I have tried everything but I always appear fails.
I would really appreciate if you could support me with this, I am desperate.
Click to expand...
Click to collapse
So do you have a s8 or 9 either way it sounds like your flashing older firmware than on the device. Hence that error. Try finding version 3 bootloader of your firmware

TheMadScientist said:
So do you have a s8 or 9 either way it sounds like your flashing older firmware than on the device. Hence that error. Try finding version 3 bootloader of your firmware
Click to expand...
Click to collapse
Sorry.
I have a S8 G950F but I do not understand how to do it

Lavachita said:
Sorry.
I have a S8 G950F but I do not understand how to do it
Click to expand...
Click to collapse
i see the device lol i went off the title
from what it looks your device is on a version 3 bootloader which is not downgradable
The error you show in odin looks like your trying to flash a version 1 bootloader
dont use this firmware but this is for referance only
Germany (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Spain (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Slovenia (Si.mobil)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
all of these have the 3 which means revision 3
Now all these have 2s
ain (Orange)
2018-07-12
8.0.0
G950FXXU2CRF7
Which cannot be flash through odin or any other methods as it is a downgraded bootloader
So if the error is corect you need your areas version 3 firmware

TheMadScientist said:
i see the device lol i went off the title
from what it looks your device is on a version 3 bootloader which is not downgradable
The error you show in odin looks like your trying to flash a version 1 bootloader
dont use this firmware but this is for referance only
Germany (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Spain (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Slovenia (Si.mobil)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
all of these have the 3 which means revision 3
Now all these have 2s
ain (Orange)
2018-07-12
8.0.0
G950FXXU2CRF7
Which cannot be flash through odin or any other methods as it is a downgraded bootloader
So if the error is corect you need your areas version 3 firmware
Click to expand...
Click to collapse
Could you give me the help with the firmware, please?

https://www.sammobile.com/firmwares/search/g950f/
Here try here just pic for your device and carrier a 3 version

TheMadScientist said:
i see the device lol i went off the title
from what it looks your device is on a version 3 bootloader which is not downgradable
The error you show in odin looks like your trying to flash a version 1 bootloader
dont use this firmware but this is for referance only
Germany (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Spain (Vodafone)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
Slovenia (Si.mobil)
2018-08-01
8.0.0
G950FXXU3CRGB
G950FOVF3CRG5
all of these have the 3 which means revision 3
Now all these have 2s
ain (Orange)
2018-07-12
8.0.0
G950FXXU2CRF7
Which cannot be flash through odin or any other methods as it is a downgraded bootloader
So if the error is correct you need your areas version 3 firmware
Click to expand...
Click to collapse
I have been fiddling with an ATT S8 for days, switch to TMB + upgrade to 8.0 at the same time. I've learned a TON because of everyone here and I've made my own mistakes.
I was running into fused and fails and this seemingly simple but overlooked information really solved my issue and helped me proceed to the final stages. You are amazing, thank you.
BTW A little tip for everyone... Unlock your SIM BEFORE you flash other roms, firmware or try changing carriers... If you don't, you may have to go back to the original carrier Firmware before their SIM Unlock code will work.

SGH-M919: No PIT Partition, Unable to boot to recovery. pls Help

Hello All,
My Device is S4 SGH M919(T-Mobile USA), Not Rooted and have been running on Lineage OS 17.1 + TWRP recovery for several months until recently when the phone started to randomly shut off mic or reboot or crash often. nandroid backup used to be my savior. In an attempt to resolve the issue, I tried to reformat the phone, install different Lineage OS versions 17.1 and 18.1 which didn't improve my situation. I then switched to Lineage recovery(which I now regret was a bad move!) which not only improvised my situation but I lost ability to perform nandroid backups since then. I have been trying to revert to TWRP recovery but am facing the several issues which are listed below. My phone is very unstable now; it boots sometimes, crashes often and most times it gets stuck trying to enter recovery. i am able to get into download mode.
Issues:
Missing/Corrupted PIT Partition
Unable to boot to Recovery
Frequent crash
Troubleshooting Attempts Performed:
Flash PIT partition file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401).​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 0 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash stock android via ODIN with/without PIT partition file
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2616 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash TWRP recovery using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Get PIT for mapping..​<ID:0/003>​<ID:0/003> There is no PIT partition.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash TWRP recovery + PIT file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1303)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Checking PIT Partition using Heimdall
heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
if you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Things already verified
Connecting to PC USB Port with original quality USB cable; Tried changing USB cable and the port
Installed required samsung USB drivers
tried with multiple ODIN versions which all used to work in the past
How to recover from here?
May be I am not using the correct PIT file? I tried and couldn't find many so far.
Assuming there is no physical damage to the board inside, what additional steps I could try to get back to recovery mode? I look forward for your expert suggestion/next steps here.
Thank You!

Tried taking this to a Samsung service center but as expected they denied looking into this citing the phone is too old, is no longer being supported and better buy a new phone.
I am still wondering if I can revive this phone so that I can use this to continue experimenting with custom ROM.. Any options still worth trying to revive this phone?