hey there!
I was trying to root my s6 Edge trough the Odin way. Evertime its failing halfway trough.
PHP:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zerolte-zeroltexx-smg925f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried it with the SpaceX and zeroltexx kernels. Can anyone help?
some info about the phone,
modelNoSM-G925FAndroid6.0.1Baseband MMB29K.G925FXXU4DPJHKernel 3.10.61-8821257
[email protected]#1
fri Oct 14 10:54 KST 2016
i have exactly the same problem.i tried with odin 3.07,3.11.,3.12 official roms for my samsung s6 edge g925f.
it stucks on nand write and then the red warning : fail . i tried also with kies and smart switch software but doesn't work.any solutions please?
Mickymuisjee said:
hey there!
I was trying to root my s6 Edge trough the Odin way. Evertime its failing halfway trough.
PHP:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zerolte-zeroltexx-smg925f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried it with the SpaceX and zeroltexx kernels. Can anyone help?
some info about the phone,
modelNo SM-G925F
Android 6.0.1
BasebandMMB29K.G925FXXU4DPJH
Kernel3.10.61-8821257
[email protected]#1
fri Oct 14 10:54 KST 2016
Click to expand...
Click to collapse
Flash twrp first.
Then flash this SuperSU through twrp. It will work
http://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Related
I need some help with flashing.
I was trying to flash the Litening rom with odin.
But odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004> modem.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So i cant flash any custom roms
Hi
I am trying to go back to stock android 4.2.2 Galaxy S4 Mini SPH-L520, and getting the following error from Odin, any suggestions?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L520VPUAMK2_L520SPTAMK2_L520VPUAMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know where I can find the pit file for Galaxy S4 Mini SPH-L520 ?
Hi everyone!
Hope you can help with this.
I have a Verizon Galaxy S4 with a completely dead (black) screen. It's not just cracked... i can't see anything.
I can connect it to my computer and see my files, so i know it's still alive, but i want to wipe it and sell it for parts, since the logic board and other stuff is still good.
This phone is NOT rooted.
I can't put it in debug mode because i can't see anything on the screen.
When i try to flash it with Odin, following the instructions for flashing to stock, i get the following:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried three or four times with the same results.
Any ideas what's going wrong?
I would prefer to reset to stock, but maybe i should just delete photos / contacts manually?
Thanks in advance for your help!
MaliaSleight said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Persistence pays off... i read a bunch of other posts about general Odin issues, and though i didn't find anything 100% the same as my issue, the theme was to try a different version of Odin and a different TAR. I did both and now i get PASSED!
Hello
I rooted my galaxy s7 edge using this link http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470.
i started having issues with the root, ex the phone would get stuck on the AT&T screen.
I tried going back to the stock image using this link https://boycracked.com/portfolio/galaxy-s7-edge-att-sm-g935a-firmware/.
Now i can no longer use Odin to flash anything, and i get this error dm-verity verification failed, int the recovery section.
Please Help!!!!!!!!
Thank you
update
<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/004> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am trying to root my s6 edge that is running Nougat, but when I use odin and the correct version of chainfire auto-root, my phone says "Secure Check Fail : (Recovery)".
Here is the log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroltevzw-zeroltevzw-smg925v.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have Auto Reboot and F. Reset Time checked in options. There is no checkbox to OEM unlock in my developer settings (although I am using the U.S. Version).