Database Users

[Q] SM-N9005 bricked, help needed!

I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?

k3000 said:
I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
Click to expand...
Click to collapse
try a different odin

jaythenut said:
try a different odin
Click to expand...
Click to collapse
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.

k3000 said:
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
Click to expand...
Click to collapse
Try 3. what ever the number is i think it's better

jaythenut said:
Try 3. what ever the number is i think it's better
Click to expand...
Click to collapse
Odin3v185
That's the one I used.

k3000 said:
Odin3v185
That's the one I used.
Click to expand...
Click to collapse
No not that one v 3.07

jaythenut said:
No not that one v 3.07
Click to expand...
Click to collapse
Just tried it again with ODIN v3.07 and got the same error message in ODIN
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

This is getting really frustrating...
I tried different ODINs running on XP, Win 7 and Win 8.
I ran ODIN as Admin or Standard user and I used different USB ports and cables.
Nothing seems to help.
For example, trying to flash stock ROM gives me this error in 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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....

toker_X1 said:
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
Click to expand...
Click to collapse
There is no error message on the display... that's exactly the text I see as well.
The only things that happens on the display the moment ODIN displays "FAIL", the blue progress bar freezes... I'd day it doesn't get further than 1-2%.

Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.

toker_X1 said:
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
Click to expand...
Click to collapse
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Why didn't you use ODIN 3.09 like guide here on XDA says?
Have you tried with that version?

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.

toker_X1 said:
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
Click to expand...
Click to collapse
Just tried... I get stuck at 2) again trying to flash the Kernel.

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
try stock firmware from www.samfirmwares.com with odin v3.09

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
Uhm, probably a dumb question, but did you use the CSC file as well? Didn't see that in the SS.

nabilsweet007 said:
try stock firmware from www.samfirmwares.com with odin v3.09
Click to expand...
Click to collapse
Unfortunately, no progress. Fails at the very same stage all where all my other efforts have failed, too.
Note: I am using the standard USB 3.0 cable which came with the Note 3. I have tried about 5 different USB 2.0 I have at home. Windows would not recognize a USB device being connected, but the Note 3 itself starts to charge the battery.

What was the csc of the phone before you tried the first flash?
Sent from my SM-N9005

SUCCESS!!
I went to the basement and dug out an old Win XP laptop, approx. 2002 vintage, which has not been used since probably 2005.
Plugged in my Note 3 with the USB 3.0 cable (of course at USB 1.0 speeds), re-ran Root de la Vega from scratch and voilà, it worked!
LESSON LEARNED: Do not use VMWARE FUSION/MAC to root. IT WILL BRICK YOUR PHONE.

[HELP] SM-N9005 LTE 32Gb Hard-bricked (SD: partial solution - mmc_read failed)

I've been reading many threads over the last 3 days, and I can't get back my SM-N9005 LTE 32Gb.
My N9005 (Portuguese TPH) bricked doing a firmware update from 4.4.2 N9005XXUGNG1 (Portuguese TPH) to 5.0 Lollipop N9005XXUGBOB6 (Poland XEO) with Odin 3.09. Odin said success (PASS), but phone never rebooted.
Solution #1: http://forum.xda-developers.com/showthread.php?t=2531224 Thanks @msmercy42 I learned a lot from it but none of the N9005 unbrick.img worked for me.
Solution #2: http://forum.xda-developers.com/showthread.php?t=2625332 Thanks @ValenteL finally my N9005 goes into ODIN/Download mode.
However, I belive that solution #2 isn't going as smooth as it should. This is what I get when I get the phone to start from SD card:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 163840 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
And then, Odin recognizes the phone.
Now I'm able to get Odin to recognize the phone, but I can't do anything with it. I've tried:
- flashing 4.4.2 N9005XXUGNG1 (Portuguese TPH) again - FAIL (see attachments) Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
- flashing N9005XXUGBOB6 (Poland XEO) again - FAIL
- flashing PIT files (tried 3 different ones) - FAIL Phone outputs another line, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
I wasn't able to get any unbrick.img from a N9005 Lollipop yet. Is this the final solution for my problem? Since I'm able to get to odin mode, shouldn't this unbrick be enough? What does it mean "mmc_read fail"?? Any help?!?! I don't know what else to do...
Thanks!!

Skactus said:
I've been reading many threads over the last 3 days, and I can't get back my SM-N9005 LTE 32Gb.
My N9005 (Portuguese TPH) bricked doing a firmware update from 4.4.2 N9005XXUGNG1 (Portuguese TPH) to 5.0 Lollipop N9005XXUGBOB6 (Poland XEO) with Odin 3.09. Odin said success (PASS), but phone never rebooted.
Solution #1: http://forum.xda-developers.com/showthread.php?t=2531224 Thanks @msmercy42 I learned a lot from it but none of the N9005 unbrick.img worked for me.
Solution #2: http://forum.xda-developers.com/showthread.php?t=2625332 Thanks @ValenteL finally my N9005 goes into ODIN/Download mode.
However, I belive that solution #2 isn't going as smooth as it should. This is what I get when I get the phone to start from SD card:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 163840 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
And then, Odin recognizes the phone.
Now I'm able to get Odin to recognize the phone, but I can't do anything with it. I've tried:
- flashing 4.4.2 N9005XXUGNG1 (Portuguese TPH) again - FAIL (see attachments) Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
- flashing N9005XXUGBOB6 (Poland XEO) again - FAIL
- flashing PIT files (tried 3 different ones) - FAIL Phone outputs another line, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
I wasn't able to get any unbrick.img from a N9005 Lollipop yet. Is this the final solution for my problem? Since I'm able to get to odin mode, shouldn't this unbrick be enough? What does it mean "mmc_read fail"?? Any help?!?! I don't know what else to do...
Thanks!!
Click to expand...
Click to collapse
I think you are actually doing everything correct, the reason is probably due to a corrupted MMC chip unfortunately.
That also explains why it failed during your first firmware update.

hallydamaster said:
I think you are actually doing everything correct, the reason is probably due to a corrupted MMC chip unfortunately.
That also explains why it failed during your first firmware update.
Click to expand...
Click to collapse
:/
No solution then?...
how should I solve this problem then? new motherboard? new MMC chip? ...
Assuming the chip is gone, is there anything else I can try before going to hardware repair?
Thanks for your response...
Is there any developer that can help me?
I'm also willing on trying to use a 5.0 PIT file or a 5.0 unbrick.img if someone can manage to get me one...

Skactus said:
:/
No solution then?...
how should I solve this problem then? new motherboard? new MMC chip? ...
Assuming the chip is gone, is there anything else I can try before going to hardware repair?
Thanks for your response...
Is there any developer that can help me?
I'm also willing on trying to use a 5.0 PIT file or a 5.0 unbrick.img if someone can manage to get me one...
Click to expand...
Click to collapse
AFAIK Lollipop ROMs boot on KK bootloaders, so that shouldn't be the problem.
Have you tried just to do a factory reset and see if anything happens?
If it doesn't work, what about installing a custom recovery from DL mode?
If that works try flashing a small AOSP rom.
EDIT:
Yes, if the MMC is corrupted, a new motherboard will be needed, unless ofcourse it's possible to do any HW repairs.

hallydamaster said:
AFAIK Lollipop ROMs boot on KK bootloaders, so that shouldn't be the problem.
Have you tried just to do a factory reset and see if anything happens?
If it doesn't work, what about installing a custom recovery from DL mode?
If that works try flashing a small AOSP rom.
EDIT:
Yes, if the MMC is corrupted, a new motherboard will be needed, unless ofcourse it's possible to do any HW repairs.
Click to expand...
Click to collapse
Can't get to recovery, so no factory reset for me...
I was wondering about installing a custom rom recovery from odin on last resort... I'm still hopeful for the miracle of unbrick.img from a 5.0 to work. Than I'll call my Note 3 by "Fenix 3" instead...

Skactus said:
Can't get to recovery, so no factory reset for me...
I was wondering about installing a custom rom recovery from odin on last resort... I'm still hopeful for the miracle of unbrick.img from a 5.0 to work. Than I'll call my Note 3 by "Fenix 3" instead...
Click to expand...
Click to collapse
There is no stock recovery when you try enter?
If I were you, I would try to install TWRP recovery through Odin, then install a custom AOSP ROM.
If that works you can try test the MMC with software.

hallydamaster said:
There is no stock recovery when you try enter?
If I were you, I would try to install TWRP recovery through Odin, then install a custom AOSP ROM.
If that works you can try test the MMC with software.
Click to expand...
Click to collapse
I can only get the phone to get alive using SD card with unbrick.img on it (see post #1). Then I can get access only to ODIN mode.
Tried to flash TWRP recovery through Odin right now: FAIL.
Odin 3.09:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
... it's a no go then...

Skactus said:
I can only get the phone to get alive using SD card with unbrick.img on it (see post #1). Then I can get access only to ODIN mode.
Tried to flash TWRP recovery through Odin right now: FAIL.
Odin 3.09:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
... it's a no go then...
Click to expand...
Click to collapse
I see, sorry about your phone. Does indeed seem like you have a dead MMC chip.

:/ thanks for your kind help anyway...
Should I expect someone else to confirm this, get a 5.0 PIT, maybe a 5.0 unbrick.img for the microSD card trick, or are you 100% sure of that and I should stop pursuing the utopia of getting my phone unbricked?
Sent from my RIDGE 4G using Tapatalk

Skactus said:
:/ thanks for your kind help anyway...
Should I expect someone else to confirm this, get a 5.0 PIT, maybe a 5.0 unbrick.img for the microSD card trick, or are you 100% sure of that and I should stop pursuing the utopia of getting my phone unbricked?
Sent from my RIDGE 4G using Tapatalk
Click to expand...
Click to collapse
I would probably not give up either, you can say there is no harm in trying what there is to try.
Using a debrick.img from a 5.0 Android should not make a difference, but if you can find one, why not give it a try?
I have found 2 pit files you might try, AFAIK they are both recent:
http://www.4shared.com/get/lrO_9qAoce/CSB_signed_HLTE_EUR_OPEN_32G_0.html
https://hostr.co/ndxkZa6KqRTF
You can also try use the "Nand erase all" feature in Odin 3.09, but I think I've read somewhere that it requires you to have a backup of your EFS to restore properly.

hallydamaster said:
I would probably not give up either, you can say there is no harm in trying what there is to try.
Using a debrick.img from a 5.0 Android should not make a difference, but if you can find one, why not give it a try?
I have found 2 pit files you might try, AFAIK they are both recent:
http://www.4shared.com/get/lrO_9qAoce/CSB_signed_HLTE_EUR_OPEN_32G_0.html
https://hostr.co/ndxkZa6KqRTF
You can also try use the "Nand erase all" feature in Odin 3.09, but I think I've read somewhere that it requires you to have a backup of your EFS to restore properly.
Click to expand...
Click to collapse
I belive I've already tried the first one. I'm downloading them right now. ´
Can you explain further on about "Nand erase all" feature? I don't really know nothing about it, but I confess I'm a scared to use it.
EDIT: Both failed. "Re-Partition operation failed."

Skactus said:
I belive I've already tried the first one. I'm downloading them right now. ´
Can you explain further on about "Nand erase all" feature? I don't really know nothing about it, but I confess I'm a scared to use it.
EDIT: Both failed. "Re-Partition operation failed."
Click to expand...
Click to collapse
Appareantly the "Nand erase alle" setting formats the MMC, but that means you have to have a backup of EFS, else you cannot restore your IMEI... Thats what I think it was about. Sorry, about the pits, that was all I got.

Yet I can't thank you enough, since you're the only one how even tried to assist me with my problem so far!

I have another question yet... is it too late to create a EFS backup?
I've speed read some threads about Nand erase and that could eventually solve my problem.

Skactus said:
I have another question yet... is it too late to create a EFS backup?
I've speed read some threads about Nand erase and that could eventually solve my problem.
Click to expand...
Click to collapse
Unfortunately I don't think it's possible to backup the EFS without recovery/working android. So if it's deleted, you will just have another bricked stated, not being able to use it with your provider.
Have you tried just to flash a bootloader through Odin, see if that works? Or does it just quit instantly?

You need to flash with a PIT file and repartition checked. At least that's what I gathered from looking at the issue.

hallydamaster said:
Unfortunately I don't think it's possible to backup the EFS without recovery/working android. So if it's deleted, you will just have another bricked stated, not being able to use it with your provider.
Have you tried just to flash a bootloader through Odin, see if that works? Or does it just quit instantly?
Click to expand...
Click to collapse
I don't tried yet flashing just the bootloader, but i've tried to flash a bootloader among with other files, Odin Failed. Can you sugest which bootloader to flash?
So far I couldn't flash anything without Odin failing...
BTW, adb doesn't find the device either...

toastido said:
You need to flash with a PIT file and repartition checked. At least that's what I gathered from looking at the issue.
Click to expand...
Click to collapse
Thanks for your reply. I've already flashed almost 6 diferent PIT files, with and without AP, nothing worked for me so far. I belive that's because I haven't got any 5.0 PIT file yet. Would you care to share one?

Skactus said:
Thanks for your reply. I've already flashed almost 6 diferent PIT files, with and without AP, nothing worked for me so far. I belive that's because I haven't got any 5.0 PIT file yet. Would you care to share one?
Click to expand...
Click to collapse
Unfortunately I don't have one, and I'm on am n900t, so even if I pulled one it probably wouldn't help. :/ best of luck, and please keep us apprised of any progress and outcomes!

toastido said:
Unfortunately I don't have one, and I'm on am n900t, so even if I pulled one it probably wouldn't help. :/ best of luck, and please keep us apprised of any progress and outcomes!
Click to expand...
Click to collapse
Sure, If I get to solve this I'll also make a tutorial about it (I've find some guys with similar problem [mmc_read fail], but no one got to solve it yet.).

[Q] Bricked or not ? MMC: mmc_read fail.

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:
Enter CS for MD5 ..
Check MD5 .. Do not unplug the cable ..
Please wait ..
900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME.tar. md5 is valid.
Checking MD5 finished Sucessfully
..
Leave CS.
My S5 is well recognized by odin, it tells me blue com port 3 and
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:
Odin v.3 engine (ID: 3) ..
File analysis ..
SetupConnection ..
Initialzation ..
Get PIT for mapping ..
There is no PIT partition.
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
[Q] Bricked or not ? MMC: mmc_read fail. I'm afraid !

S7 EDGE - Possible bricked phone - Need help (Full details in thread)

Phone: Samsung S7 Edge, SM-G935F
Country: UK
Here is my problem. I had rooted my phone, installed TWRP, and flashed Renovate edge. Then I ATTEMPTED to encrypt the phone through
the setting "encrypt device" and I chose full encryption. The phone then wouldn't boot, it would only let me go into recovery, So I wiped the
phone with the intention of using a backup of the STOCK OS. After I wiped the phone it now won't let me boot into recovery to flash anything.
Current situation:
When I attempt to switch on the device: Custom binary blocked by FRP lock (small red writing on the top left)
When I attempt to boot into the recovery: Recovery is not seandroid enforcing (small red writing on the top left)
When I boot into download mode: It works and ODIN recognizes the device
Download mode information on screen reads:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Warranty Void: 1 (0x020c)
RP SWREV: B:1 K:0 S:0
I have already tried installing a stock ROM using ODIN and setting the phone into download mode, I get this error:
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<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)
On screen: Secure check fail : (PIT)
Where do I go from here? Now I just have a very expensive brick. Is there a solution to this? PLS HELP
My preferred outcome is reverting the phone to stock OS, I just want it working again.

Try flashing your phone with the firmware from:
http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
Follow the steps.
Do not tick "Re-Partition".

PROX_ said:
Phone: Samsung S7 Edge, SM-G935F
Country: UK
Here is my problem. I had rooted my phone, installed TWRP, and flashed Renovate edge. Then I ATTEMPTED to encrypt the phone through
the setting "encrypt device" and I chose full encryption. The phone then wouldn't boot, it would only let me go into recovery, So I wiped the
phone with the intention of using a backup of the STOCK OS. After I wiped the phone it now won't let me boot into recovery to flash anything.
Current situation:
When I attempt to switch on the device: Custom binary blocked by FRP lock (small red writing on the top left)
When I attempt to boot into the recovery: Recovery is not seandroid enforcing (small red writing on the top left)
When I boot into download mode: It works and ODIN recognizes the device
Download mode information on screen reads:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Warranty Void: 1 (0x020c)
RP SWREV: B:1 K:0 S:0
I have already tried installing a stock ROM using ODIN and setting the phone into download mode, I get this error:
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
FAIL!
Re-Partition operation failed.
All threads completed. (succeed 0 / failed 1)
On screen: Secure check fail : (PIT)
Where do I go from here? Now I just have a very expensive brick. Is there a solution to this? PLS HELP
My preferred outcome is reverting the phone to stock OS, I just want it working again.
Click to expand...
Click to collapse
If you flash latest firmware from Aug 16 you WON'T BE ABLE TO ROOT OR FLASH TWRP!
CF-AUTOROOT needs to be updated as well as TWRP.
If you just want to return to Stock and not root you won't have to worry about it then follow that thread that was provided for you.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F

drms12 said:
Try flashing your phone with the firmware from:
http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
Follow the steps.
Do not tick "Re-Partition".
Click to expand...
Click to collapse
s7freak said:
If you flash latest firmware from Aug 16 you WON'T BE ABLE TO ROOT OR FLASH TWRP!
CF-AUTOROOT needs to be updated as well as TWRP.
If you just want to return to Stock and not root you won't have to worry about it then follow that thread that was provided for you.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
Click to expand...
Click to collapse
:laugh: thanks guys, I'd been scouring forums for days trying to figure out what to do. I should've made a post earlier. Thank you very much. My phone is now working perfectly!
Is there a way to reset the knox counter and un-void the warrenty?

Nope
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F

system upgrade, firmware, USB debugging problem

Hello everybody,
I bought a Samsung Galaxy Note 3 (SM-N9005) phone. Firmware: N9005ZHUENF1. Android 4.4.2.
I tried to update the system, but the phone said "I am fresh". But, it is not true, because my girlfriend has a same phone and it updated across the OTA.
I installed the KIES to the my PC and my phone do not work with it. When I connect the phone to the PC with a USB cable, not working. When I connect my girlfriends phone everything nice.
I enabled the USB debugging mode, but it is not working. When I connect the phone to the PC with a USB cable the question is not arrive that I would like to enable the debugging mode. When I connect my girlfriends phone everything nice.
I think my phone is rooted, because I checked it with an app, and the app said "Yes, rooted".
My questions are:
- is it possible to upgrade my phone to the Lollipop?
- is it possible to put into the phone the original firmware (if it will be necessary)?
- is it possible to enable the USB-debugging mode?
I am waiting for your asks.
Best regards,
Zoltan

is it possible to upgrade my phone to the Lollipop?
Yes flash a firmware via Odin see stickies .
- is it possible to put into the phone the original firmware (if it will be necessary)?
Yes as above .
- is it possible to enable the USB-debugging mode?
Yes but its not required .

This the message in the Odin window:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SECURE CHECK FAIL: about
Please help!

What are you flashing ??

I downloaded the 5.0 lollipop and I would like to upgrade.

What firmware there are multiple firmwares for many variety 's of Note .

In the phone:
N9005ZHUENF1
ok, now i see that not the same what i downloaded

Odin failed flashing aboot.mbn which means the rom was not made for the phone or the bootloader in the rom is too old.

OK, I do not understand.
When I step into the download mode (volume down+home+power) I see these:
Odin mode
Product name: SM-N900A
Current binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm Securebot : Enable (CSB)
Ap SWRev: S2, T2, R2, A3, P2
Write Protection: Enable
OK, but in the settings menu my model number is: SM-N9005.
SM-900A or SM-N9005?
Please help somebody!

SM900A.
If that's what Odin mode says .
If its a new phone return to the vendor .
What does it say under the battery ??

under the battery: SM-N9005
in the recovery menu: kot49h.n900aucucnc2

Reads as possible fake.
Sent from my SM-N920C using XDA-Developers mobile app

The phone is a note 3 with a motherboard from AT&T based on the model number of Sm-n900a in download mode.
It appears that the phone has an AT&T motherboard in a note 3 international body.

So, what can I do?

All you can do is flash the latest rom for the n900a which is lollipop. The bootloader is probably locked which means you cannot install cwm or twrp. Only custom recovery that will work is safestrap.

thx, but I do not find it. Give me a link please.

gutanier said:
thx, but I do not find it. Give me a link please.
Click to expand...
Click to collapse
Your device is an AT&T Note 3 disguised as an international one, as said before.
I already had this experience with a Sprint Note 2.
So if you want simply upgrade to Stock Lollipop, here is the stock image.
If you want root, custom recovery and maybe custom ROMs, please follow this guide.
There are many customs roms supporting your device, so head to the AT&T Note 3 forum for more infos.
Good luck

THX folks, I did it, I have Lollipop on my Note 3. THX again. :good:

Hi folks again.
Mission 2: root.
How can I do it simple? SM-N900A Lollipop 5.0

http://forum.xda-developers.com/note-3-att/general/root-lollipop-att-note-3-safestrap-t3132475