Kernel is not Seandroid enforcing - Galaxy Note 4 Q&A, Help & Troubleshooting

I'm currently having "Kernel is not Seandroid enforcing" error message.
First, I rooted my phone, then preparing into flashing a custom ROM and kernel.
I downloaded Extended battery (v 2.91.45) - N910C/H for Kernel and Nemesis for ROM.
Wipe cache and etc then flash the kernel via TWRP first while I was downloading the Custom ROM.
Rebooted after I flashed the Kernel (maybe I screwed up here because I don't have any ROM installed yet?)
Phone couldn't go anywhere past the boot screen which shown "Kernel is not Seandroid enforcing" error message.
After searching the internet, people suggested to flash the stock ROM via ODIN, but then I have these errors on Odin 3 v3.04
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COJ5_N910GOLB1COJ1_N910GDTU1COJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And no response on Odin3 v3.12
<ID:0/005> 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..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
I'm flashing with the latest stock ROM in my Country.
Tried different USB ports
Tried different USB cables.
Tried factory reset/ manual wipes
OS : 6.0.1
Model : SM-N910C - Samsung Note 4
What else can I do on my end before sending it to shops ?

Lozyness said:
I'm currently having "Kernel is not Seandroid enforcing" error message.
First, I rooted my phone, then preparing into flashing a custom ROM and kernel.
I downloaded Extended battery (v 2.91.45) - N910C/H for Kernel and Nemesis for ROM.
Wipe cache and etc then flash the kernel via TWRP first while I was downloading the Custom ROM.
Rebooted after I flashed the Kernel (maybe I screwed up here because I don't have any ROM installed yet?)
Phone couldn't go anywhere past the boot screen which shown "Kernel is not Seandroid enforcing" error message.
After searching the internet, people suggested to flash the stock ROM via ODIN, but then I have these errors on Odin 3 v3.04
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COJ5_N910GOLB1COJ1_N910GDTU1COJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Model : SM-N910C - Samsung Note 4
What else can I do on my end before sending it to shops ?
Click to expand...
Click to collapse
i think you have a problem on your firmware. As you can see, you have a N910C and you are using the firmware for N910G, it's totally different.
Find a latest firmware for N910C.
And it's normal to have "Kernel is not seandroid enforcing" if you have a custom kernel installed

Related

Help plz I9505 stuck in bootloop

Hi,
tried to flash the 4.4 stock on my I9505 (was on 4.3, which worked fine).
4.4 didnt run smooth so I restored the old backup and ended up in a bootloop.
Tried to flash Samsung 4.3 stock via Odin but it fails every time giving me this message:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUAMDK_I9500MBCAMD6_I9500XXUAMDK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
any suggestions? Would be very happy!

[Q] Can't flash stock ROM SPH-L720

I installed CyanogenMod 10.2.1 on my rooted Sprint S4. Upon realizing that I could no longer connect my Gear 2 watch to my phone, I would like to reset my phone to factory settings, unrooted, with the stock ROM. I followed the guide at galaxys4root.com (xda won't let me post the outside link, but it is the first result when you Google "galaxy s4 root unroot") and used all the downloads from that page. However, upon trying to flash to my phone, I receive this error in Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can then shut down my phone and reboot back into CM just fine, but I really would like to have the stock ROM back so I can use my watch. If anyone could help me with this, I'd really appreciate it. Thanks!
GadgetGuy3 said:
I installed CyanogenMod 10.2.1 on my rooted Sprint S4. Upon realizing that I could no longer connect my Gear 2 watch to my phone, I would like to reset my phone to factory settings, unrooted, with the stock ROM. I followed the guide at galaxys4root.com (xda won't let me post the outside link, but it is the first result when you Google "galaxy s4 root unroot") and used all the downloads from that page. However, upon trying to flash to my phone, I receive this error in Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can then shut down my phone and reboot back into CM just fine, but I really would like to have the stock ROM back so I can use my watch. If anyone could help me with this, I'd really appreciate it. Thanks!
Click to expand...
Click to collapse
What version of ODIN are you using?
pontif said:
What version of ODIN are you using?
Click to expand...
Click to collapse
I've tried both 1.85 and 3.04, both present the same error
GadgetGuy3 said:
I've tried both 1.85 and 3.04, both present the same error
Click to expand...
Click to collapse
The stock nae forum suggests using 3.07
Put in pda slot
Be sure to power completely off before going into download mode
pontif said:
The stock nae forum suggests using 3.07
Put in pda slot
Be sure to power completely off before going into download mode
Click to expand...
Click to collapse
Just did all that, still got the error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Attaced is a photo of the screen of my phone after the flash fails. In case you can't read it, the text in the top-left corner says:
ODIN MODE
PRODUCT NAME: SPH-L720T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
WRITE PROTECTION: Enable
eMAC BURST MODE: enabled
START [244, 1440]
SECURE CHECK FAIL : aboot
Since you have the file already here is the link from Sammmobile. Also if you want ,download the Odin version that they provide. GoodLuck
GadgetGuy3 said:
Just did all that, still got the error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Attaced is a photo of the screen of my phone after the flash fails. In case you can't read it, the text in the top-left corner says:
ODIN MODE
PRODUCT NAME: SPH-L720T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
WRITE PROTECTION: Enable
eMAC BURST MODE: enabled
START [244, 1440]
SECURE CHECK FAIL : aboot
Click to expand...
Click to collapse
Well there's you problem says you have the l720T version of the s4. You need stock firmware for the sphl720 T version. Search for that specific device
BIGSAMDA1ST said:
Since you have the file already here is the link from Sammmobile. Also if you want ,download the Odin version that they provide. GoodLuck
Click to expand...
Click to collapse
There's no link in this post
Holy S*#@. Anyway just saw that @pontif just posted that you have the T version so the link I provided will not work.
---------- Post added at 01:57 PM ---------- Previous post was at 01:50 PM ----------
Here you go.. Its the latest for SPH-L720T
http://www.sammobile.com/firmwares/3/?download=28778
BIGSAMDA1ST said:
Holy S*#@. Anyway just saw that @pontif just posted that you have the T version so the link I provided will not work.
---------- Post added at 01:57 PM ---------- Previous post was at 01:50 PM ----------
Here you go.. Its the latest for SPH-L720T
Click to expand...
Click to collapse
pontif said:
Well there's you problem says you have the l720T version of the s4. You need stock firmware for the sphl720 T version. Search for that specific device
Click to expand...
Click to collapse
Alright, that was a stupid mistake on my part, I apologize. I'm downloading the L720T firmware from Sammobile now and I also downloaded Sammoblie's suggested ODIN, which is 3.09. I will post the results after the download finished and I try to flash it.
GadgetGuy3 said:
Alright, that was a stupid mistake on my part, I apologize. I'm downloading the L720T firmware from Sammobile now and I also downloaded Sammoblie's suggested ODIN, which is 3.09. I will post the results after the download finished and I try to flash it.
Click to expand...
Click to collapse
That worked. Thanks for your help.
PLZ HELP!!!
Hi, I am having the EXACT same issue but with SPH-L720 device. I've tried multiple odin's.....STILL....."FAILED"
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I desperately need to return to stock so I can update my device. It is not running well AT ALL.
Thanks in advance.
bbryson said:
Hi, I am having the EXACT same issue but with SPH-L720 device. I've tried multiple odin's.....STILL....."FAILED"
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I desperately need to return to stock so I can update my device. It is not running well AT ALL.
Thanks in advance.
Click to expand...
Click to collapse
Try downloading the NG2.tar. It's the most up to date.
Will do. Thank you!

5.1.1 910H root via CF-Auto-Root?

Does CF-Auto Root work for the new 910H variant 5.1.1 ROM?
I'm currently rooted with CF on 5.0.1, but I want to upgrade without losing root.
TIA.
Well, wanamlite is rooted running 5.1.1 so at least there's root for it. I'm currently running that on my N910H but I will download and install the official firmware
Not working!
I just flashed 5.1.1 stock rom on my SM-910H device. CF-Autoroot does not seem to work. After flashing the root MD5 file, i'm getting "RECOVERY IS NOT SEANDROID ENFORCING" + endless loop. I'll stay unrooted until solution is found.
krakenator said:
I just flashed 5.1.1 stock rom on my SM-910H device. CF-Autoroot does not seem to work. After flashing the root MD5 file, i'm getting "RECOVERY IS NOT SEANDROID ENFORCING" + endless loop. I'll stay unrooted until solution is found.
Click to expand...
Click to collapse
Yeah, same experience. I guess we'll have to wait until Chainfire releases a newer Auto-Root.
5.1 1 wont work with cf
Sent from my SM-N910G using Tapatalk
Guys you can get root by flashing Talexop kernel after upgrading to 5.1.1, just make sure to check if modem.bin is not present in the .zip file.
Flash AEL kernel, then it'll boot up
pedodroid said:
Guys you can get root by flashing Talexop kernel after upgrading to 5.1.1, just make sure to check if modem.bin is not present in the .zip file.
Click to expand...
Click to collapse
My 910H is now rooted with Talexop kernel. used twrp method.
pedodroid said:
Guys you can get root by flashing Talexop kernel after upgrading to 5.1.1, just make sure to check if modem.bin is not present in the .zip file.
Click to expand...
Click to collapse
Thank you, this worked for me.
maheshhtc said:
My 910H is now rooted with Talexop kernel. used twrp method.
Click to expand...
Click to collapse
hi can you upload taiexop kernel for 910h /5.1.1
thanks in advance
rajaib said:
hi can you upload taiexop kernel for 910h /5.1.1
thanks in advance
Click to expand...
Click to collapse
Go to Note 4 Android Development for Exynos & u will find a post of talexop for 910c. Install all in one kernel thru twrp. Sorry Im on 3G hence cannot upload myself. My device is 910H but u can use this kernel meant for 910c.
krakenator said:
I just flashed 5.1.1 stock rom on my SM-910H device. CF-Autoroot does not seem to work. After flashing the root MD5 file, i'm getting "RECOVERY IS NOT SEANDROID ENFORCING" + endless loop. I'll stay unrooted until solution is found.
Click to expand...
Click to collapse
donalgodon said:
Yeah, same experience. I guess we'll have to wait until Chainfire releases a newer Auto-Root.
Click to expand...
Click to collapse
sm-n910h
hi,
i have the same problem. : "RECOVERY IS NOT SEANDROID ENFORCING" + endless loop
i had 5.1.1 N910HXXU1BOF1 on my phone after rooting the phone with CF-Auto-Root-tre3g-tre3gxx-smn910h.zip - based on KTU84P.N910HXXU1ANJ4 4.4.4 this problem happened to my phone
i went to recovery at the bottom of screen says : "dm-verity verification failed"
i fully wiped the phone through recovery and reboot but again it says "RECOVERY IS NOT SEANDROID ENFORCING" and goes to samsung logo then suddenly restart and repeats again and again
i'm using Odin3 v3.10.7
i tried to flash 5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5_HOME.tar official single rom file but in odin it says :
Code:
<ID:0/008> Added!!
<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/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i searched for a pit file and found this four files:
SM-N910H_pit_mannyvinny
TRE3G_EUR_OPEN_HIDDEN50M
TRE3G_EUR_OPEN_MEA
TRE3G_EUR_OPEN_MEA
when i flash SM-N910H_pit alone odin log says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when i flash TRE3G_EUR_OPEN_HIDDEN50M alone it says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but nothing changed.
i searched for 4file rom : N910HXXU1ANIF_OXE1ANIF_Repair_Firmware
AP_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
BL_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
CP_N910HXXU1ANIF_1727235.tar
CSC_OXE_N910HOXE1ANIF_CL2815469_QB2398142_REV00_user_low_ship.tar
TRE3G_EUR_OPEN_HIDDEN50M.pit
odin log for this rom :
Code:
<ID:0/008> Removed!!
<ID:0/008> Added!!
<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..
<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..
<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..
<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/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i rooted the phone with "twrp-2.8.7.0-tre3gxx.img" by odin and changed the file system of "system" and "data" and "cache" to ext2 then changed it back to ext4 then repair it -one of my friend said it help- but nothing changed...
after all this operations my phone stuck In Samsung Logo , and its not going to next booting logo of samsung like before... and boot-loop not happen like before just frozen at that black and white logo....
but "RECOVERY IS NOT SEANDROID ENFORCING" message appear every time i try to go to recovery
please help me
is there any hope?
does my phone hard bricked?
if there is a solution please explain simply
PersiAndroid said:
sm-n910h
hi,
i have the same problem. : "RECOVERY IS NOT SEANDROID ENFORCING" + endless loop
i had 5.1.1 N910HXXU1BOF1 on my phone after rooting the phone with CF-Auto-Root-tre3g-tre3gxx-smn910h.zip - based onKTU84P.N910HXXU1ANJ44.4.4 this problem happened to my phone
i went to recovery at the bottom of screen says : "dm-verity verification failed"
i fully wiped the phone through recovery and reboot but again it says "RECOVERY IS NOT SEANDROID ENFORCING" and goes to samsung logo then suddenly restart and repeats again and again
i'm using Odin3 v3.10.7
i tried to flash 5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5_HOME.tar official single rom file but in odin it says :
Code:
<ID:0/008> Added!!
<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/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i searched for a pit file and found this four files:
SM-N910H_pit_mannyvinny
TRE3G_EUR_OPEN_HIDDEN50M
TRE3G_EUR_OPEN_MEA
TRE3G_EUR_OPEN_MEA
when i flash SM-N910H_pit alone odin log says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when i flash TRE3G_EUR_OPEN_HIDDEN50M alone it says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but nothing changed.
i searched for 4file rom : N910HXXU1ANIF_OXE1ANIF_Repair_Firmware
AP_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
BL_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
CP_N910HXXU1ANIF_1727235.tar
CSC_OXE_N910HOXE1ANIF_CL2815469_QB2398142_REV00_user_low_ship.tar
TRE3G_EUR_OPEN_HIDDEN50M.pit
odin log for this rom :
Code:
<ID:0/008> Removed!!
<ID:0/008> Added!!
<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..
<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..
<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..
<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/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i rooted the phone with "twrp-2.8.7.0-tre3gxx.img" by odin and changed the file system of "system" and "data" and "cache" to ext2 then changed it back to ext4 then repair it -one of my friend said it help- but nothing changed...
after all this operations my phone stuck In Samsung Logo , and its not going to next booting logo of samsung like before... and boot-loop not happen like before just frozen at that black and white logo....
but "RECOVERY IS NOT SEANDROID ENFORCING" message appear every time i try to go to recovery
please help me
is there any hope?
does my phone hard bricked?
if there is a solution please explain simply
Click to expand...
Click to collapse
Recovery is not SEAandroid Enforcing is normal with a custom recovery - To obtain Root on Stock 5.1.1 Firmware - you will probably have to find and flash a custom kernel.
In the mean time - Try a Factory Reset with TWRP to get you out of the bootloop
Sent From My SM-N910W8 Running SlimRemix V5.3
shaggyskunk said:
Recovery is not SEAandroid Enforcing is normal with a custom recovery - To obtain Root on Stock 5.1.1 Firmware - you will probably have to find and flash a custom kernel.
In the mean time - Try a Factory Reset with TWRP to get you out of the bootloop
Sent From My SM-N910W8 Running SlimRemix V5.3
Click to expand...
Click to collapse
i installed talexop_Kernel_N910C_5.1.1_C0J5_v1.05_aggresive but this it says "Kernel is not SEAandroid Enforcing" and when i try to go to recovery like before it says "Recovery is not SEAandroid Enforcing" and recovery automaticly restart after a few second . i flashed twrp-2.8.7.0-tre3gxx.img with odin again hpe to fix the recovery but nothing changed still recovery reset after a few seconds.
PersiAndroid said:
i installed talexop_Kernel_N910C_5.1.1_C0J5_v1.05_aggresive but this it says "Kernel is not SEAandroid Enforcing" and when i try to go to recovery like before it says "Recovery is not SEAandroid Enforcing" and recovery automaticly restart after a few second . i flashed twrp-2.8.7.0-tre3gxx.img with odin again hpe to fix the recovery but nothing changed still recovery reset after a few seconds.
Click to expand...
Click to collapse
Again - Both those notifications are NORMAL!
Flash the img.tar with Odin - And are you certain that you flashed the correct version of TWRP for your device?
Sent From My SM-N910W8 Running SlimRemix V5.3
shaggyskunk said:
Again - Both those notifications are NORMAL!
Flash the img.tar with Odin - And are you certain that you flashed the correct version of TWRP for your device?
Sent From My SM-N910W8 Running SlimRemix V5.3
Click to expand...
Click to collapse
so , what should i do now?
can you help me step by step?
yes "twrp-2.8.7.0-tre3gxx.img"

Recovery is not SEAandroid Enforcing | after CF-Autoroot 5.1.1 S-N910H

"please don't delete this thread
i really need help"
hi,
I flashed 5.1.1 stock rom on my SM-910H after rooting the phone with CF-Auto-Root-tre3g-tre3gxx-smn910h.zip - based on KTU84P.N910HXXU1ANJ4 4.4.4 this problem happened to my phone
"RECOVERY IS NOT SEANDROID ENFORCING" + endless loop
i went to recovery at the bottom of screen says : "dm-verity verification failed"
i fully wiped the phone through recovery and reboot but again it says "RECOVERY IS NOT SEANDROID ENFORCING" and goes to samsung logo then suddenly restart and repeats again and again
i'm using Odin3 v3.10.7
i tried to flash 5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5_HOME.tar official single rom file but in odin it says :
Code:
<ID:0/008> Added!!
<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/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i searched for a pit file and found this four files:
SM-N910H_pit_mannyvinny
TRE3G_EUR_OPEN_HIDDEN50M
TRE3G_EUR_OPEN_MEA
TRE3G_EUR_OPEN_MEA
when i flash SM-N910H_pit alone odin log says :
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when i flash TRE3G_EUR_OPEN_HIDDEN50M alone it says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but nothing changed.
i searched for 4file rom and downloaded the :
N910HXXU1ANIF_OXE1ANIF_Repair_Firmware :
AP_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
BL_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
CP_N910HXXU1ANIF_1727235.tar
CSC_OXE_N910HOXE1ANIF_CL2815469_QB2398142_REV00_user_low_ship.tar
TRE3G_EUR_OPEN_HIDDEN50M.pit
odin log for this rom :
Code:
<ID:0/008> Removed!!
<ID:0/008> Added!!
<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..
<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..
<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..
<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/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i rooted the phone with "twrp-2.8.7.0-tre3gxx.img" by odin and changed the file system of "system" and "data" and "cache" to ext2 then changed it back to ext4 then repair each one -one of my friend said it would help- but nothing changed...
at this point my phone stuck In Samsung Logo , and its not going to next booting logo of samsung like before... and boot-loop not happen like before just frozen at that black and white logo....
but "RECOVERY IS NOT SEANDROID ENFORCING" message appear every time i try to go to recovery
so when i ask about my problem on xda a user recommend me to flash a custom kernel
i found the Talexop Kernel
i installed talexop_Kernel_N910C_5.1.1_C0J5_v1.05_aggresive but this it says "Kernel is not SEAandroid Enforcing" and when i try to go to recovery like before it says "Recovery is not SEAandroid Enforcing" and recovery automaticly restart after a few second . i flashed twrp-2.8.7.0-tre3gxx.img with odin again hpe to fix the recovery but nothing changed still recovery reset after a few seconds.
please help me
is there any hope?
does my phone hard bricked?
if there is a solution please explain simply
please help
PersiAndroid said:
"please don't delete this thread
i really need help"
hi,
I flashed 5.1.1 stock rom on my SM-910H after rooting the phone with CF-Auto-Root-tre3g-tre3gxx-smn910h.zip - based on KTU84P.N910HXXU1ANJ4 4.4.4 this problem happened to my phone
"RECOVERY IS NOT SEANDROID ENFORCING" + endless loop
i went to recovery at the bottom of screen says : "dm-verity verification failed"
i fully wiped the phone through recovery and reboot but again it says "RECOVERY IS NOT SEANDROID ENFORCING" and goes to samsung logo then suddenly restart and repeats again and again
i'm using Odin3 v3.10.7
i tried to flash 5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5_HOME.tar official single rom file but in odin it says :
Code:
<ID:0/008> Added!!
<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/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i searched for a pit file and found this four files:
SM-N910H_pit_mannyvinny
TRE3G_EUR_OPEN_HIDDEN50M
TRE3G_EUR_OPEN_MEA
TRE3G_EUR_OPEN_MEA
when i flash SM-N910H_pit alone odin log says :
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when i flash TRE3G_EUR_OPEN_HIDDEN50M alone it says
Code:
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but nothing changed.
i searched for 4file rom and downloaded the :
N910HXXU1ANIF_OXE1ANIF_Repair_Firmware :
AP_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
BL_N910HXXU1ANIF_CL2815469_QB2396298_REV00_user_low_ship.tar
CP_N910HXXU1ANIF_1727235.tar
CSC_OXE_N910HOXE1ANIF_CL2815469_QB2398142_REV00_user_low_ship.tar
TRE3G_EUR_OPEN_HIDDEN50M.pit
odin log for this rom :
Code:
<ID:0/008> Removed!!
<ID:0/008> Added!!
<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..
<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..
<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..
<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/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i rooted the phone with "twrp-2.8.7.0-tre3gxx.img" by odin and changed the file system of "system" and "data" and "cache" to ext2 then changed it back to ext4 then repair each one -one of my friend said it would help- but nothing changed...
at this point my phone stuck In Samsung Logo , and its not going to next booting logo of samsung like before... and boot-loop not happen like before just frozen at that black and white logo....
but "RECOVERY IS NOT SEANDROID ENFORCING" message appear every time i try to go to recovery
so when i ask about my problem on xda a user recommend me to flash a custom kernel
i found the Talexop Kernel
i installed talexop_Kernel_N910C_5.1.1_C0J5_v1.05_aggresive but this it says "Kernel is not SEAandroid Enforcing" and when i try to go to recovery like before it says "Recovery is not SEAandroid Enforcing" and recovery automaticly restart after a few second . i flashed twrp-2.8.7.0-tre3gxx.img with odin again hpe to fix the recovery but nothing changed still recovery reset after a few seconds.
please help me
is there any hope?
does my phone hard bricked?
if there is a solution please explain simply
Click to expand...
Click to collapse
Okay first of all calm down your phone is not bricked or anything. "Kernel is not SEAandroid Enforcing" OR "Recovery is not SEAandroid enforcing" are common errors which happen when you flash custom recovery or root the phone. if you go to sammobile and download latest 5.1.1 COJ5 build and flash it it may solve your problem but the problem with "COJ5" build is that its bootloader is locked Once you have updated to 5.1.1 COJ5 you can't downgrade to 5.0.2 OR kitkat and there is no root for it yet. But since you have already tried your luck with PIT files i'd suggest first you flash twrp then format your phone, then download stock ANJ4 KITKAT from sammobile and try to flash it in odin....see if it works...if works then all good and if it doesn't work then download and flash "5.1.1 COJ5" build from sammobile. It will lock your bootloader but it may help in getting your phone back online !!!!
*as i always say i am not responsible if you damage your phone this is just my opinion on what i would have done if i were you....you can try this or wait for more expert opinion"
dork997 said:
Okay first of all calm down your phone is not bricked or anything. "Kernel is not SEAandroid Enforcing" OR "Recovery is not SEAandroid enforcing" are common errors which happen when you flash custom recovery or root the phone. if you go to sammobile and download latest 5.1.1 COJ5 build and flash it it may solve your problem but the problem with "COJ5" build is that its bootloader is locked Once you have updated to 5.1.1 COJ5 you can't downgrade to 5.0.2 OR kitkat and there is no root for it yet. But since you have already tried your luck with PIT files i'd suggest first you flash twrp then format your phone, then download stock ANJ4 KITKAT from sammobile and try to flash it in odin....see if it works...if works then all good and if it doesn't work then download and flash "5.1.1 COJ5" build from sammobile. It will lock your bootloader but it may help in getting your phone back online !!!!
*as i always say i am not responsible if you damage your phone this is just my opinion on what i would have done if i were you....you can try this or wait for more expert opinion"
Click to expand...
Click to collapse
there is no 5.1.1 " COJ5 " Build for SM-N910H , but there is for SM-N910C , and no ANJ4 KITKAT for both
I searched for latest firmware for SM-N910H and its 5.1.1 "COK1" , DOES IT DO THE JOB? like i said i flashed "5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5" and "4.4 kitkat N910HXXU1ANIF" and odin failed...
i keep getting <ID:0/008> NAND Write Start!! <ID:0/008> FAIL! Errors how can i be sure i'm not facingerror whe i flash ANJ4 KITKAT or 5.1.1 "COK1"?
is installing custom roms based on 5.1.1 like RulingLite from recovery helps getting phone back alive?
PersiAndroid said:
there is no 5.1.1 " COJ5 " Build for SM-N910H , but there is for SM-N910C , and no ANJ4 KITKAT for both
I searched for latest firmware for SM-N910H and its 5.1.1 "COK1" , DOES IT DO THE JOB? like i said i flashed "5.1.1 N910HXXU1BOF1_N910HOLB1BOF1_N910HXXU1BOC5" and "4.4 kitkat N910HXXU1ANIF" and odin failed...
i keep getting <ID:0/008> NAND Write Start!! <ID:0/008> FAIL! Errors how can i be sure i'm not facingerror whe i flash ANJ4 KITKAT or 5.1.1 "COK1"?
is installing custom roms based on 5.1.1 like RulingLite from recovery helps getting phone back alive?
Click to expand...
Click to collapse
i don't know about custom roms.......But you can try with kitkat and COK1 stock firmwares.

G900F Won't boot to ROM or Recovery

This all started when I tried to flash Clockwork recovery on my stock G900F. I used Odin to successfully load the recovery, but as soon as it booted it would get stuck at "Set warranty bit: recovery" and restart itself into the ROM. So then I tried TWRP and Philz Touch and got the same thing. Then I tried to flash CF-Auto Root to see if I could use root permissions to restart into recovery via the CWM app, but that too gave me the same error. I tried both with and without Auto-Reboot on to see if maybe the stock ROM was overwriting the recovery but that didn't fix it either. This entire time USB debugging was enabled so that's not it.
Since the point of me doing this was to install CM 14.1 anyways, I decided to try flashing a stock ROM. I tried a whole bunch of different rips and none of them worked. The ones that were compressed into .tar would give the following error in Odin:
Code:
<ID:0/006> 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..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The one that was broken into four separate files gives this error:
Code:
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For both types of rips I had both Auto-Boot and F. Reset Time on. I did once attempt to use the .pit file provided with the latter rip and attempt to re-format, but that didn't do anything except prevent my stock ROM from booting (it's now stuck at the Samsung logo). I can still boot into download mode.
What are my options from here? I'm a little disheartened that my stock phone was unable to load any of the recovery tools that I tried, but maybe I'm missing something.
I tried using the firmware linked in this thread. I tried flashing with both T-flash and repartition as well as just T-flash and it doesn't work.
I get about halfway through the download before it fails. This is the output from Odin:
Code:
<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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> T Flash...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> userdata.img.ext4
<ID:0/004> FAIL! (Erase)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can still boot into download mode and successfully flash any recovery I try, but I also still can't boot into recovery. Any help is greatly appreciated.
Turns out this was as simple as not having the version of the phone I thought I had.
Amazon told me it was a G900F when I bought it. The box says G900F. The sticker beneath the battery says G900F. The phone itself says G9006V.
When I searched to see if this has happened to anyone else, I saw more than a few confused and frustrated people learning this same thing the hard way as I did.
The lesson here is to trust what you see in download mode and disregard everything else. It's a bit slimy, but that's the world we live in.

Categories

Resources