I've been trying to root my T-Mobile Marshmallow Note 4 using CF Auto Root but it doesn't seem to be working properly. I downloaded the correct auto root file for my model (SM-N910T). I opened the Odin that downloaded with the auto root file, clicked AP, loaded the .tar file and then I click start. Odin then says RESET! and the follow:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Meanwhile my phone reboots and gets stuck at the Samsung Galaxy Note4 screen with the following text at the top of the screen.
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I can take out the battery and get back to the boot load screen.
I've been able to root this phone before using CF Auto but on an older version of android, is this a marshmallow issue? I'm obviously still not very experienced with this so any help would be appreciated.
T2K86 said:
I've been trying to root my T-Mobile Marshmallow Note 4 using CF Auto Root but it doesn't seem to be working properly. I downloaded the correct auto root file for my model (SM-N910T). I opened the Odin that downloaded with the auto root file, clicked AP, loaded the .tar file and then I click start. Odin then says RESET! and the follow:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Meanwhile my phone reboots and gets stuck at the Samsung Galaxy Note4 screen with the following text at the top of the screen.
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I can take out the battery and get back to the boot load screen.
I've been able to root this phone before using CF Auto but on an older version of android, is this a marshmallow issue? I'm obviously still not very experienced with this so any help would be appreciated.
Click to expand...
Click to collapse
Go to download mode and Flash twrp recovery in odin and from twrp recovery flash supersu.zip you will get permanent root.this is universal method and it always works.
Twrp n910t download
https://mega.nz/#!DIFFVSpQ!bUCEAa-VRdkeT4VgMJ-4cUXuo-ZiYbihOSWiw6Ic_wo
Supersu.zip latest download
https://mega.nz/#!XAsUjARJ!XqYZkle6wTarq1a8-zAnhwrbd4IdpzpJryNCAU3g9k4
Related
HI my phone was wokring perfect till i tried to dometic unlock my phone following a tutorial from here , when i when to flash the zip the odin fail now imstuck in a black screen i only can boot into download mode but cant go into my recovery , i tried diferent odin and stock tar file but odin keep failing. my phone had the 4.4.2 NG2 i tried that tar but no luck ether , in download mode i have something saying write protection enable i dont know if this is the reason i cant flash the tar. can anyone help me get my phone back to work pls .....
this is what im getting from odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I'll try to help, not that good myself though. What happens when you try to go into recovery?
I'm having the same problem. Only this phone was dropped by my friend on its top left corner and hasn't booted since then.
I successfully flashed the stock NAE tar through Odin last night but it still won't boot. I also cannot boot into recovery. It simply vibrates but nothing shows up on the screen at all. I can only boot into download mode intermittently.
Can't figure out why it would flash but not boot.
Recently I updated my phone to a lollipop using the standard updates verizon pushed out. After doing this I decided to root my phone, which didn't end well. I used several different methods like towel root, which said my device wasn't supported, and I tried using odin. Neither worked, so I decided to try and downgrade Android back to 4.4.4, which didn't work either. Both times I used odin it failed. Any way I can root or downgrade with this current update, or is there some kind of odin fix?
You can't root using 4.4.4 or 5.0, only the NCG, which is 4.4.2, build or lower. To Odin items you need to boot into download mode, which can be done by holding home+volume down+power on start. Once in download mode flash the NK2 tar, factory reset in recovery mode, and then setup. Then download towelroot, boot into download mode again, flash a ncg kernel, and root using towelroot. Now boot into download again and flash the NK2 kernel. Setup SuperSU, install busybox, and install safestrap recovery. Then follow the instructions in the general section of the vz s5 to get root on lollipop.
I know you have to put it into odin mode, and I think my main problem with odin is that the bootloader is locked. Any way to unlock it?
calebp123 said:
I know you have to put it into odin mode, and I think my main problem with odin is that the bootloader is locked. Any way to unlock it?
Click to expand...
Click to collapse
Not currently. What's the error message on Odin?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
calebp123 said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
Click to expand...
Click to collapse
You can't install Philz on a locked boot loader. Not only that, but you're using a klte version. If the boot loader was unlocked you'd need a kltevzw version. You can downgrade to NK2 using the stock tar here: http://forum.xda-developers.com/showthread.php?t=2784880
TL;DR: My phone is in a bootloop. Attempts to flash back to stock or perform a factory reset haven't worked.
Originally posted on Reddit at r/AndroidQuestions and r/TechSupport. Please forgive me if this is an oft-discussed topic, but I've yet to find anything that's helped me.
A little background: I rooted my Samsung Galaxy s5 (Verizon) in August, 2014. No third-party ROM was installed; just root with Nova Pro, Gravitybox, and Xposed. I had no issues until about 2 months ago when my phone stopped rotating. It'd start rotating again after removing the battery, but eventually that stopped working, too, even in safe mode. I assumed I installed something weird, so I did a factory reset. That didn't fix the problem, though, so I intended to flash the stock ROM for a total reset. Earlier this week, my phone wouldn't connect to wifi. I powered off, removed the battery, and powered back on. And lo, le loop.
Solutions I've attempted:
1) Removing my microSD card. Didn't work.
2) Cache wipe. When I hold the power, home, and volume up buttons, I arrive at this screen. I'm not sure if I can get to the menu shown in the video. Factory reset and safe mode don't work, either. I'm guessing this is because I didn't set up a custom recovery? I'm honestly not familiar with CWM and TWRP.
3) Flash to stock ROM. I did exactly as this guide instructed. I put the ROM on the SD card, then flashed the firmware and kernel. Odin said it was successful and outputted this message (apologies for the wall of text):
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VZW_BOC4_RETAIL_FIRMWARE_ONLY.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> boot.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sdi.mbn
<ID:0/003> tz.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NI2_stock_kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)​Upon completion, the phone just kept rebooting as it had before.
4) Flash to factory ROM. I downloaded the files for my phone mentioned in this tutorial, but they were in this format, so I'm not sure how to run this in Odin (which is looking for .tar, .md5, etc.).
IN CONCLUSION...
Thoughts? Opinions? Questions?
Did I make any mistakes when attempting the solutions above?
If you are collectively baffled, what are my options? My warranty is voided by my root, is it not? Is there an online service that repairs soft bricks for a nominal fee?
Thank you for your time.
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"
ok let`s start from the start, i tried to root my note 3 sm-n9005 and failed to succeed.
i used the cf auto root guide, odin said success but my phone failed to boot and went straight to recovery mode.
then, i tried using odin 3.07/09/11/185 to rewrite into the stock rom, but odins says FAIL and gives nothing in return.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i just want get my phone back with android that above 4.4
please help :crying:
Looks like the ROM you are trying to flash is not made for your phone or the ROM is older than the ROM currently installed on the phone.
Are you using the original Samsung USB cable? Tried different USB cables and ports?
For Root note 3 use Towelroot by Chainfire.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk
Download Official 5.0 ROM from Sammobile and flash it in Odin, after it try to root phone...
In dialog this looks like firmware file is damaged
The firmware doesn't look damaged, the firmware you are trying to flash has a bootloader that is older than the bootloader in the phone.
isn't chainfire's root method called cfautoroot?
download one more time...