Phone stuck and wont boot - Note Edge Q&A, Help & Troubleshooting

Hi, I recently fixed my note edge by installing 4.4 kitkat. A few days later I realized it was really slow and so I plugged it in and tried to flash marshmallow stock. This didn't work and now my phone goes automatically to download mode and every time I try to re-flash it it either insta fails or says aboot fused 2 binary 1. Also, I think i got twrp installed because it passed on odin but if I try to boot recovery it Says "Could not do normal boot and ddi: mmc_read failed". Thanks for the help!

https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335

Bordo_Bereli51 said:
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Click to expand...
Click to collapse
Thanks for the link but the files included in the guide are listed for the note 4 so how do I use that in note edge thanks for help

UPDATE
I have got phone into download/ odin mode but still need help as my flash fails in odin\
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

Same thing...
Here's my odin log.
<ID:0/008> Added!!
<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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
P.s I have the AT&T model.

UPDATE
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_N915AATT2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
It failed half way through on the phone it says
"ODIN : flash write failure"

1) ODIN 3.09
2) Get N915A 5.0.1 Modem
3) Get N915A 6.0.1 Firmware Stock (the AP file)
4) Get N915A 6.0.1 Modem
1)Place phone in DOWNLOAD MODE (volume down + home + power button)
2) Open ODIN 3.09
3) Place file N915A 5.0.1 Modem in CP
4) Place file N915A 6.0.1 Firmware.tar in AP box
5) Once ODIN is finished flashing the files power off your phone and go back into DOWNLOAD MODE, dont boot.
6) Place file N915A 6.0.1 Modem in CP box
7) Once the file is flashed your phone will be mmc error free and you will have a 100% working phone again.

thejug786 said:
Hi, I recently fixed my note edge by installing 4.4 kitkat. A few days later I realized it was really slow and so I plugged it in and tried to flash marshmallow stock. This didn't work and now my phone goes automatically to download mode and every time I try to re-flash it it either insta fails or says aboot fused 2 binary 1. Also, I think i got twrp installed because it passed on odin but if I try to boot recovery it Says "Could not do normal boot and ddi: mmc_read failed". Thanks for the help!
Click to expand...
Click to collapse
Tell me, how could you return to 4.4.4? I also have n915a on marshmallow, but I would like to return to kitkate. Tell me how you did it ??

"A few days later I realized it was really slow" tells us maybe that this is a emmc failure problem
https://www.sammobile.com/forum/showthread.php?t=30686
In this forum, this guy has the same problem like you. He tried different attempts. Even though he flashed succesfully and booted up, his phone was very slow and had freezing problem. A while later he got again the "Could not do normal boot and ddi: mmc_read failed" problem.

Related

[SOLVED] Hard-bricked my S6??

Hey guys, I just got my S6 (SM-920I) and went to root it the instant I got home. And that was where the problem all started. I used chainfire's auto-root and flashed it in odin under AP. The log in odin shows the firmware flash was successful but upon reboot my phone stays stuck on the boot logo screen. So I went to un-brick it by downloading the appropriate stock firmware for my phone (G920IDVU1AOD1_G920IOLC1AOD1_XSP.zip) (my phone is the Singapore variant of the 920I). This is the error I got on odin no matter how many tries I did.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IOLC1AOD1_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> cm.bin
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
And now I have no clue on how to fix and restore my phone back to its original state anymore. Help is greatly appreciated thanks!
EDIT: Solved... Just a simple reboot of my PC fixed the problem for me apparently...

Help my S6 from T mobile seems screwed

Idk whats going on I used the odin3 download stock firmware to try to restore the phone after boot loop I tried to install TWRP custom recovery it didnt reboot into and so i tried to restore through odin3 and stock frimware and it says failed. Any ideas thanks
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.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)
make sure re-partition is unchecked from the options tab.
Sent from my SM-G920I using Tapatalk
Try :
1. Using a different USB cable or USB port.
2. Redownload again your ROM as download errors can cause flash failures.
3. Lastly, consider bringing your S6 back to Samsung for warranty repair. Its free within your warranty period.
I hope this helps.

[Help] Galaxy S 6 G920W8 stuck on SAMSUNG logo during boot

So I have a samsung Galaxy S 6 (G920W8) that I cannot get to boot into Android.
I was able to get the device into recovery and download mode, and I'm able to install TWRP on the device, boots into that with zero problems.
I've been able to use TWRP to install custom ROMs and kernels, and I can use an older version of ODIN to flash the correct carrier ROM to the phone, but newer version fail on the NAND WRITE step. TWRP gives no errors when attempting to flash, and I have access to the whole memory of the device.
Is there any hope for this device?
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920W8VLU3BOL1_G920W8OYA3BOL1_G920W8VLU3BOL1_HOME.tar.md5 is invalid.
<OSM> End...
<Accidentally tried adding file before it was done unzipping>
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
That's the result in Odin after trying to flash that carrier ROM with Odin3 v3.10.7. Now the device is still boot looping. I don't understand what's wrong.
DisturbenChamp said:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920W8VLU3BOL1_G920W8OYA3BOL1_G920W8VLU3BOL1_HOME.tar.md5 is invalid.
<OSM> End...
<Accidentally tried adding file before it was done unzipping>
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
That's the result in Odin after trying to flash that carrier ROM with Odin3 v3.10.7. Now the device is still boot looping. I don't understand what's wrong.
Click to expand...
Click to collapse
Boot into recovery and factory reset.
Sent from my SM-G925F
Rosli59564 said:
Boot into recovery and factory reset.
Sent from my SM-G925F
Click to expand...
Click to collapse
I have tried that. The device continues to boot loop, even when wiped through official recovery or TWRP recovery.
DisturbenChamp said:
I have tried that. The device continues to boot loop, even when wiped through official recovery or TWRP recovery.
Click to expand...
Click to collapse
Try to reinitialize the phone with smart switch. Maybe it's the firmware you flashed with odin.
Sent from my SM-G925F
Rosli59564 said:
Try to reinitialize the phone with smart switch. Maybe it's the firmware you flashed with odin.
Sent from my SM-G925F
Click to expand...
Click to collapse
Smart Switch nor Kies will connect to the device., but odin and MTP via TWRP both work. I've attempted a 5.0.2 and 5.1.1 ROM from the carrier, the ROMs are from Sam-Firmware, and I am currently downloading a 6.0.1 file to attempt and flash..
Sometimes in Download mode it displays the following error:
Code:
SW REV CHECK FAIL. DEVICE: 3, BINARY: 1
OR
SW REV CHECK FAIL. DEVICE: 3, BINARY: 2

Help on T-mobile Note 5 SM-N920T failed to flash odin

I have this problem i cant reflash it on odin. Ive already rooted the device because when i get this it has a deep sleep issue so i fix it. After i rooted and install twrp recovery it works fine. But after i accidentally rooted again. It stuck up to boot loop t mobile logo.
Now when im flashin it on odin it say fails en recovery mode says.
SW REV. CHECK FAIL. DEVICE: 4 BINARY 3
Here is the log file i get from odin when im flashing a stock firmware on odin
GT-N920T T-mobile
Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N920TUVU3DPG1_N920TTMB3DPG1_N920TUVU3DPG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Somebody help me please? For this fix

SM-G955U1 boots directly to download mode with error message

The error message reads "An error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software."
Im picking up from a lot of you by reading various threads that this is no longer an option.
Backstory: This phone was given to me and from day 1 all the system apps would crash to the point where android would reboot. The phone wouldnt shut off completely like it was losing power, but it would go back to the second screen you see on boot. At this point, the settings reported the software build number as being G955USQS5CRI4, which i dont fully understand. Because on the back side of the phone, the model number reads SM-G955U1.
In an attempt to resolve this issue, i used odin and flashed various builds of g955u1 across a few versions of odin and even attempted some g955u builds. At some point during all of this, download mode switched from normal looking download mode to displaying a big ! in a triangle on the screen. None of the usual information youd see is displayed. However, odin still connects and it appears as though i can still flash. I fear i may have made a mistake.
This log is my latest attempt using SM-G955U1_1_20190709124427_xh7461wrxv_fac pulled from SamFirm. G955U1UES6DSG1 either XAA or VZW, i cant remember which.
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 5808 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> bksecapp.mbn
<ID:0/008> xbl.elf
<ID:0/008> tz.mbn
<ID:0/008> hyp.mbn
<ID:0/008> devcfg.mbn
<ID:0/008> pmic.elf
<ID:0/008> rpm.mbn
<ID:0/008> cmnlib.mbn
<ID:0/008> cmnlib64.mbn
<ID:0/008> keymaster.mbn
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> sec.dat
<ID:0/008> NON-HLOS.bin
<ID:0/008> storsec.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When this fails, on the screen of the phone, red text appears that says "secure check fail: system".
Does anyone have any suggestions on what I should do next? Im kind of stumped. Ive been at this for a couple days and cant seem to get different results. I have downloaded several firmwares attempting to resolve this and some of those i believe failed due to bootloader version, but the others typically say fail (auth) or SHA256 is invalid. Although that may be due to me kind of switching between odin 3.13.1 and some patched version of it with this ODIN3B logo in the banner. I would be grateful if anyone could offer me some advice or at least explain what is happening to me. Thank you.

Categories

Resources