Database Users

Help with Odin FAIL

I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.

Also, redownload the tar file. It could be a bad download.

jd1639 said:
Also, redownload the tar file. It could be a bad download.
Click to expand...
Click to collapse
ok will try that.

here are the messages that I am getting
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2nd message
ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?

xBeerdroiDx said:
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
Click to expand...
Click to collapse
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.

jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
If you had mf3 on, no amount of odin is going to help.

jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
You must have taken the update to MF3. Essentially, you will not be allowed to downgrade firmware back to older versions. The way Samsung is writing the bootloader is there a monotonic counter only going in one direction, up. So if the bootloader has been updated to the latest version by an OTA, you can't revert it back. Currently I believe there is no workaround, but we have some awesome devs on this site so keep your fingers crossed.

jimsond said:
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Click to expand...
Click to collapse
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.

jeffreii said:
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
Click to expand...
Click to collapse
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859

jimsond said:
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.

jeffreii said:
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
Click to expand...
Click to collapse
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..

P.S in kies the current firmware version PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)

jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.

jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.

jd1639 said:
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
Click to expand...
Click to collapse
It look like I have mf3 So I f__k up. The phone is working

jimsond said:
It look like I have mf3 So I f__k up. The phone is working
Click to expand...
Click to collapse
Good to hear the phone is working. I wouldn't mess with it any more.

jeffreii said:
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
Click to expand...
Click to collapse
Thanks for your input I have a hard time saying on paper what was my problem. I like to talk things out and I use the link that you posted and I have root now..

[Q] Stuck while "fixing" my SGH-I337

Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.

What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I used ODIN to flash (What I'm very confident is) 4.3 Stock in the same manner I flashed the custom ROM.
I feel like that isn't specific enough for you though. I used Odin3 v3.09 first and then after several failures switched to Odin3 v1.85 as demonstrated in a few tutorials I've seen.

Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Let me attempt this thread's instructions before I make more of a fool of myself. Thank you for the assistance so far. I really appreciate it.

No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Seedeh,
The errors still continued as usual even with the explicit following of the linked directions. It appears that during the process:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that the "NAND Write Start" step isn't really even trying to write before it fails.
Kies "Emergency Firmware Recovery" also yields no success due to "Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.", which does persist each time I attempt to do so.
If you have any more suggestions, I'd be more than happy to attempt them.
Thank you.

AmpGuitarChase said:
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
Click to expand...
Click to collapse
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.

John The Rhino said:
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
Click to expand...
Click to collapse
John The Rhino,
Thank you for you assistance. I will surely give credit where credit is due
I've attempted the XDA Full Odin Tar MK2 link's instructions three times on two separate computers (one w8 and one w7) to no avail. I've triple-checked the instructions, but my Odin always fails when attempting to Complete(Write).
NAND Write Start!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
Complete(Write) Operation Failed
All threads completed. (succeed 0 / failed 1)
Odin settings: Auto Reboot checked, F. Reset Time checked, PDA = I337MK2_Full_Odin_Tar.tar file, nothing else is checked.
Device: Dev mode activated, USB debugging active, this is all verified after a recovery-initiated factory reset, device is in download mode.
Computer(s): Samsung Android ADB Interface drivers are installed, Odin does show a yellow bar upon device connection. MicroUSB cable is the default one that came with the device, all USB ports have been tried with the same results.
I tried to be as thorough as possible with my setup. I'll see if my process is correct now just in case that will help.
[Fixing Device to Working Status w/o wifi/data permissions] Flashed AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 via Odin
Automatic Reboot via Odin
[Device is back to working status w/o data/wifi permissions (No reset has been done)]
Power off
Reboot in Recovery Mode (Volume up + Home + Power)
Wipe data/factory reset command
Wipe cache (just in case)
Reboot
[Phone is now factory reset 4.3 MK2 (WiFi/Data permissions denied still]
Enable developer options
Enable USB debugging and Screen Stay Awake during charging
Power off
Boot into download mode (Volume down + Home + Power)
Open Odin3 v1.85
Bar in Odin for COM Port is yellow
Auto reboot & F. Reset Time are both checked
Load I337MK2_Combined_Odin_Tar\I337MK2_Full_Odin_Tar.tar.md5 in PDA slot
Screenshot of Odin before "START" http://i.imgur.com/oXufVNQ.png
Odin START
Wait for Odin to check .md5 compatibility
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Back to where these points began
Apologies for the length, but again I wanted to be as thorough as possible. My WiFi still won't turn on due to permissions issues and Data is on, but no 3g/4g/LTE comes through.
Surely I'm just missing an essential step or two.
Can you offer any further advice on this matter?

Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5

The bootloader on MK2 and later is encrypted and without the key it will always fail. ODIN sees the ABOOT is locked and cannot flash the complete image. AT&T and Verizon have chosen this method to keep you off their cheaper competitors. I had to take my I337 to Best Buy Samsung experience to have it re flashed so that it would boot after a refused OTA from MDL and now it is a paperweight.

jd1639 said:
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
Click to expand...
Click to collapse
I don't think Odin is the issue as it flashes what I like to call "The cure-firmware" .md5 AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5) file just fine every time with no issues with Odin. Only when I try to flash that file, it works. I wish there was a way to tell what exactly is going wrong with the other files. I also can't seem to find where I located this file, but whatever it's doing works on my S4. I'd like to find either a 4.2.2 or 4.4.2 version of this stock OS that would work.
I'm beginning to wonder if it'd be more worthwhile to reroot, reset the flag binary counter, reset, and drive an hour and a half away to the closest AT&T store and see if they can fix my device. Does this sound like it may be my best course of action?
Again, thanks for all the help guys. I means a lot.

There is no way to downgrade to 4.2.2 from MK2. The bootloader is locked. Read the guide for MK2 it will help you.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Check your APN settings re enter according to correct settings posted on XDA.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.

AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Loki does not work with MF3 and up

Congrats!
Sent from my SAMSUNG-SGH-I337 using Tapatalk

AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!

John The Rhino said:
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
Click to expand...
Click to collapse
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase

AmpGuitarChase said:
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
Click to expand...
Click to collapse
You're welcome. I'm glad it all worked out for you. As they say in the construction business, measure twice, cut once. Well same here, except I'd recommend as do others to read thrice (3x) FLASH once. Then you'll rarely have issues. Enjoy.

i337 same issue as original post
i have done the same research as posted in this link and read exhaustively every means google XDA and all the other pages dealing with rooting and flashing my AT&T s4 i337. I have ended up in the same boat as this guy with:
Baseband version - I337UCUFNB1
Build Number - JSS15J.I337UCUEMK2
i have attempted Kingo Loki, Motochopper, Odin(4 or 5 versions) adb flash in Linux(2 builds) and Winblows 7. My original desire was to have this build
https://www.youtube.com/watch?v=mJLKX_QWSpc
which got my hopes up immensely, as having wasted days upon days several times over the course of the last 9 months rooting this i337. The guy in the vid says he was able to get UT up and running following guidance from XDA. I want to be able to flash a twrp-like dual boot recovery to my device maintaining Andy functionality using UT as a daily driver.
I have read, as reading saves phones, everything I can glean from the aforementioned posts and forms, researched this thing to death and neded up with a phone with the knox-? security message listed in the original post. I have no Idea where to go from here, but know you guys do, as like a myriad of others, I worship this site like a god.
Please help an old retired disabled veteran of most of the sandy wars in the past 25 years. All I have now are my devices which bring me some comfort to my days.
I really need your help, as I've tried seemingly all and have a semi-dead i337.
buxtor, aka, Chief

Cannot mount '/data' in twrp. Is there anything left for me to try?

I am afraid i have turned my galaxy tab 4 7" (sm-t230) into an expensive coaster at this point.
It doesn't do much of anything anymore. When it's booted it does nothing but show the samsung logo sparkling and when i start it into twrp just about anything i do ends with "cannot mount '/data' and not much else.
the local storage shows 0 and through the filemanager i see there are the folders but no files inside the folders.
Ofcourse i am well aware that i must've done goofed somewhere in my enthousiastic attempt to install a custom rom and the increasingly frantic attempts after that somehow resulted in the tab not booting past the samsung logo to fix it (from trying other roms to using odo in different configs to get anything on it that worked, including kernels and such) probably only added to the result which i described above. I know that, if this is irreversably killed the tablet i have only myself to blame.
But somehow i still have a sparkle of hope there is a way to fix the damage my stupidity has caused. It's still trying to boot and when i try to install for example the stockrom rom zipfile the progress bar dutyfully progresses until its end and the message "successfull" even shows in blue. When i put the tablet into download mode Odin still gives the all clear like it should but it seems like its teasing me with those things. When i boot it stops at the logo and when i go into twrp and do anything it fails to mount '/data' and some actions result in other failures to mount folders.
So.... IS there anything i can still do? (flashing the stock samsung rom wont work at all by the way, from twrp)
any help in getting any rom doing anything similar to working would be an improvement and appreciated.

So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?

thisisapoorusernamechoice said:
So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?
Click to expand...
Click to collapse
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]

deuZige said:
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]
Click to expand...
Click to collapse
It's a good thing there's no audio recording of what i shouted here the last 30 seconds to a minute. Everything seemed to go perfectly in Odo. I started the tablet in download mode, started Odo, and connected the usb cable. then clicked ap and selected the tar file and removed the tick at f.reset time. then i clicked start. heres the messages odo gave me... errr i mean odin:
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0AOD2_T230PHN0AOD3_T230XXU0AOD2_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> SingleDownload.
<ID:0/004> timh.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> obm.bin
<ID:0/004> loke_1st.bin
<ID:0/004> loke_2nd.bin
<ID:0/004> DTim.Primary
<ID:0/004> DTim.Recovery
<ID:0/004> DTim.CP
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Odin showed the green square with pass and the tablet rebooted.
and didn't go further than the samsung logo.
which it show still.... i have exhausted my most vile, evil and offensive curseword vocabulary shouting (which my neighbours will probably not appreciate as it's 01:35 am right now) before starting to write this reply....
i guess i am, truely inescabably, F worded now ain't i??
i am so depressed right now i can't even tell ya.
anyway, any suggestions?
(thanks for taking the time to read my sorrows and replying by the way. it IS really appreciated.)

just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....

deuZige said:
just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....
Click to expand...
Click to collapse
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!

deuZige said:
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!
Click to expand...
Click to collapse
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
honestly, i have tested taking pictures, uploading them to google and i have added all new accounts where i could. That worked without error, and the picture worked, and uploaded. I am doing nothing else until i get back home tomorrow from the park where i'll be taking pictures of my son.
When those are safe, i'll do whatever you want!!!
again, i cannot express the greatness of my gratitude for this!!
[supplemental]
i must sleep now. gnight!!!
[/consciousness]

Seems like everything is working fine! No need for wiping and formatting data if you have no more issues. I guess your good to go!
Sent from my ZTE_N9511 using Tapatalk

Hey I'm sorry I never got back to you, and I feel like a total moron for forgetting to tell you to factory reset, glad @DUHAsianSKILLZ took care of things for @deuZige, I hope everything's OK going forward and I'll be happy to help if I can if it isn't.

Odin fails to downgrade Galaxy S4 from Lollipop to KitKat

All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan

Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.

GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!

Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.

Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!

Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.

GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!

You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.

GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?

Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.

Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.

It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.

You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.

Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-

100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.

I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.

@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.

Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.

Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.

[GUIDE] Root & Recovery for SM-N9208 Marshmallow (nobleltextc variant ONLY)

After sending my Note 5 into a bootloop (first one ever in my history of flashing & rooting 6+ Android devices ... first time for everything but not a record I wanted broken!!) following a "guide" posted by another user here, I figured I'd try to throw something a little clearer out here for all us n00bs looking to rec 'n' root their rockin' phone.
IMPORTANT STUFF BEFORE YOU START!!!
1. These steps worked for the Malaysian variant of the Note 5. *** IT MAY NOT WORK FOR YOU. *** (In theory, it should work for any phone with similar basebands; but then again, it may not.) This guide works perfectly for Note 5s with the following specs (Settings > About device > Software info):
Android version : 6.0.1
Build number: MMB29K.N9208XXU2BPD4
2. I'm just an amateur trying to eke a little more mileage out of what is (by most standards) an already decent phone and because I do have a love (and patience) for tinkering around with this stuff. *** I AM NOT A DEVELOPER, LET ALONE A PROFESSIONAL *** and I take no responsibility for your phone bootlooping, getting bricked, bursting into flames, or infecting patient zero. Fixing your phone will almost always take 100^ longer than the amount of time you spent messing it up in the first place - terradune's law.
3. Samsung has gone out of their way to be extra douchebaggy this time by hard-baking in bloatware that can't be removed/frozen even with TiBu, such as Smart Manager (com.samsung.android.sm, which is not visible in TiBu). If you think that rooting is going to be the answer to all your bloatware woes on the Note 5 (as it once was), this is your only warning that this time, it won't be.
-- BEWARE ALL YE WHO ENTER HERE --
-- LAST CHANCE TO EXIT THIS THREAD --
-- NO SERIOUSLY, I STAYED UP TILL 5AM TRYING TO FIX THE BOOTLOOP AND WAS SOUNDLY REMINDED WHY I'D BEEN SO WARY OF GETTING A PHONE WITH A NON-REMOVABLE BATTERY (my first, to boot ... ) --
Still here? Fine, here goes nothing:
GUIDE:
Part A - Rooting:
1. Backup, backup, backup. I started with a Note 5 fresh out of the box and updated straight away to Marshmallow before rooting, but if you didn't, then there may be apps / data you want to save & carry over. Once you're done with your backups (and have a copy of those backups somewhere safe like on your PC, in case things really go south), go on to Step 2 below.
2. {OPTIONAL STEP} Find and download the stock firmware applicable to your variant at Sammobile so that in case things go wrong, you'll have it close at hand to quickly restore your phone to working order.
3. At this point, if you're on Lollipop (Android version 5.1.1), you can decide if you want to update to Marshmallow. Because, in case you skipped the whole section of "IMPORTANT STUFF" above, this guide is for an N9208 on Marshmallow ONLY.
4. Head over to Chainfire's website and search for "nobleltextc".
5. Check (again) that your Build number matches the Build ID (MMB29K.N9208XXU2BPD4) - if it does, go ahead and hit Download.
6. Boot your phone into download mode (Power off completely, then press and hold Vol Down+Home+Power buttons all at the same time).
7. Extract the zip {CF-Auto-Root-noblelte-nobleltextc-smn9208} that you just downloaded into a folder.
8. In the folder, right-click on "Odin3-v3.10.6" (or whatever Odin version was included) and select "Run as Administrator".
9. Plug your phone in. One of the panels on the left side of the Odin window should light up blue. (If it doesn't, Google for a solution as you have an issue quite unrelated to this guide.)
10. Click on the "AP" button (DON'T TOUCH ANYTHING ELSE!!), navigate to the CF-Auto-Root folder and select "CF-Auto-Root-noblelte-nobleltextc-smn9208.tar".
11. Hit the "Start" button.
12. Wait for phone to reboot (this may take a while).
13. Enjoy rooted goodness.
14. {OPTIONAL STEP} Donate to Chainfire for being The One True Rooter of your Note 5.
Part B - Recovery:
*** If you don't know what recovery is, you probably don't need it. Rooting is often enough for most users' needs so you can stop right here unless you know what you're doing next. ***
1. Noblelte is the applicable TWRP version for the N9208 Marshmallow, so head over here and download {twrp-3.0.2-1-noblelte.img.tar}. There may be a newer version, but this is what's working for me. YMMV.
2. Go back to the CF-Auto-Root folder, right-click on "Odin3-v3.10.6" (or whatever Odin version was included) and select "Run as Administrator".
3. Plug your phone in. One of the panels on the left side of the Odin window should light up blue. (If it doesn't, Google for a solution as you have an issue quite unrelated to this guide.)
4. Click on the "AP" button (DON'T TOUCH ANYTHING ELSE!!), navigate to the folder where you downloaded {twrp-3.0.2-1-noblelte.img.tar} and select that file.
5. Hit the "Start" button.
6. Wait for phone to reboot (this may take a while).
7. Power off and boot into recovery.
8. Wipe cache and Dalvik cache. Reboot.
9. Enjoy your brand-spanking new Team Win recovery.
SOME DON'TS TO FINISH OFF:
1. Many N9208 rooting guides out there advise that you need an app called "CROM services" to unlock your phone, and that it is downloadable from the Galaxy Apps store. If you do a search in the Galaxy Apps store on your phone and come up empty (as I did), YOU (PROBABLY) DON'T NEED IT. Enabling OEM Unlock and USB Debugging in Developer Options is enough to allow you to gain root. Don't go Googling for the CROM services apk (as suggested) as the few sites providing a download link look somewhat dodgy and there is no guarantee that it would be a verified apk download of this app (translated: you might wind up downloading malware).
2. If you've followed this guide exactly, you have SuperSU and you DO NOT need to flash it separately (as some other guides advise). As such, DO NOT flash over SuperSU even if the TWRP recovery offers to do it. SuperSU was already installed when you rooted the phone in the first part of the guide above. (If you'd read the scrolling phone logs while CF-Autoroot was being installed, Chainfire provides the same warning.)
I hope that at least some of you Note 5 owners out there found this guide useful. Toodles!

Excellent tutorial. Works very well for Indian Note 5 Duos too

Great guide! Very detailed. I'm actually downloading from SamMobile the Philippine update for marshmallow. After the download I'll try to root it using this guide of yours and give you an update. Thanks again!
Edit: My build number ends in PE2 and chainfire doesn't have an auto-root for this version. sad.

Akia Azriel said:
Great guide! Very detailed. I'm actually downloading from SamMobile the Philippine update for marshmallow. After the download I'll try to root it using this guide of yours and give you an update. Thanks again!
Edit: My build number ends in PE2 and chainfire doesn't have an auto-root for this version. sad.
Click to expand...
Click to collapse
Nope, chainfire has autoroot for mm firmware
Sent from my SM-N9208 using XDA-Developers mobile app

If the Build Number is not match?
Same is SM-N9208 marshmallow, but with the Build Number end with PE2
Can I use the CF Root file with different Build Number but same Marshmallow, will it causing any problem?

Doesn't seem to work on a BRI device. Here my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> RQT_CLOSE !!

I can confirm that this worked on my Note 5 N9208 Duos with build number MMB29K.N9208XXU2BPE3 (Country: Philippines, Smart). I used the the downloadable file MMB29K.N9208XXU2BPD4 for CF-Auto-Root from the link mentioned above. Thanks! Great job!!!

thank you for this tutorial it worked on my n9208xxu2bpd5. hope i can now fix my battery draining problem.
*update: it fixed my battery draining problem. 0.7-0.9% per hour from 7% per hour.
thanks!

dosada said:
Doesn't seem to work on a BRI device. Here my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> RQT_CLOSE !!
Click to expand...
Click to collapse
It doesnt work because you need the CROM Service apk to unlock your bootloader. I am in the same boat as you
EDIT: Found the file, see my thread: http://forum.xda-developers.com/note5/general/unlocking-bootloader-tiawanese-sm-n9208-t3434961

nursefrail said:
thank you for this tutorial it worked on my n9208xxu2bpd5. hope i can now fix my battery draining problem.
*update: it fixed my battery draining problem. 0.7-0.9% per hour from 7% per hour.
thanks!
Click to expand...
Click to collapse
I have a slightly different build number( ending in PG3) and it solved my draining problem the instant I got root! It's a life saver!

PatelCartel said:
I have a slightly different build number( ending in PG3) and it solved my draining problem the instant I got root! It's a life saver!
Click to expand...
Click to collapse
Hi there.. Urs is PG3 and u using the same nobleltextc file to root?
Also wanna ask this root will increase the knox counter, I survey around forum said that counter could void warranty. (I am new to root).
Thanks.

may i know how to add TWRP without root?

weikit24 said:
Hi there.. Urs is PG3 and u using the same nobleltextc file to root?
Also wanna ask this root will increase the knox counter, I survey around forum said that counter could void warranty. (I am new to root).
Thanks.
Click to expand...
Click to collapse
This is my first time rooting too! And yes I used the root file for the build number which ended in PD4 (nobleltextc) while my phone was PG3. I used it because it had the same model number and the Android version as my Note. And I installed TWRP so I'm not sure how to check the Knox counter but a long time ago before I successfully got root I was trying to install TWRP and I believe it tripped the Knox counter. So if you're trying to preserve your warranty I don't recommend rooting or installing TWRP. I didn't have to worry about warranty so I did it. If you have any further questions just reply to this post. I'll he happy to help if I can!
---------- Post added at 03:36 PM ---------- Previous post was at 03:23 PM ----------
hairulnizams said:
may i know how to add TWRP without root?
Click to expand...
Click to collapse
Hey Hairulnuzams! So to add TWRP without root you use the same tutorial that the original poster of this thread gave at the end of his first post after the rooting instructions. That method does not require root but you will have to download Odin separately since you won't be downloading the root file. A WORD OF CAUTION: DO NOT DO THIS IF YOU DON'T WANT TO TRIP YOUR KNOX COUNTER! AND THERE'S NO GUARANTEE THIS WILL WORK! I tried to do this after checking out many tutorials but it did not work for me. However after getting root it worked perfectly. So it's up to you to take the risk if you choose to.
Here's the XDA Developers page for getting TWRP: http://www.xda-developers.com/how-to-install-twrp/
and here's another non-XDA page for using Odin: http://androiding.how/how-to-install-twrp-recovery-using-odin/ ( I personally turned on OEM Unlock AND USB Debugging)

jyeahhh...thx for this guild method bro..ur the man..i already root my samsung SM N9208 that i follow ur instruction and also download link..be sure all need to read carefully and use searching any forum to not wrong install that can brick phone. I also already brick my phone 1st time that try to root on lollipop..i upgrade to marchmallow and try to root and yeah done and already install TWRP and custom kernel SICKNESS...baterry almost very2 save use SICKNESS kernel.. +1 ur reputation bro..
sorry im from malaysia and this method work on me..
Buildnumber
N9208XXU2BPF1
Android Version
6.0.1

smeth_90 said:
jyeahhh...thx for this guild method bro..ur the man..i already root my samsung SM N9208 that i follow ur instruction and also download link..be sure all need to read carefully and use searching any forum to not wrong install that can brick phone. I also already brick my phone 1st time that try to root on lollipop..i upgrade to marchmallow and try to root and yeah done and already install TWRP and custom kernel SICKNESS...baterry almost very2 save use SICKNESS kernel.. +1 ur reputation bro..
sorry im from malaysia and this method work on me..
Buildnumber
N9208XXU2BPF1
Android Version
6.0.1
Click to expand...
Click to collapse
No problem! I'm glad to help!

PatelCartel said:
No problem! I'm glad to help!
Click to expand...
Click to collapse
Btw thanks again bro..hurmm i need suggestion bro..seems after i root my device and done with custom recovery install also kernal install at my device..when i try to play my game KRITIKA name..the game detect illigel program hack detected?can u advice how to hide root or any command can edit?because i already done with super su,hide root,set to prompt and clear play store cache,reboot and play the game but not success..i not want loose root with success this method to safe battery life with MM android..thanks in advance..
Sent from my SM-N9208 using Tapatalk

I would love to help but unfortunately I'm not familiar with how to do that. However someone is bound to reply to your post and if not you should post this question in another forum on XDA more suited to this question. Meanwhile you can check out this web page: http://www.makeuseof.com/tag/trick-apps-android-rooted/ I haven't tried any of these methods so I'm not responsible if they don't work or damage your phone. I recommend you research more into these methods and be careful! I hope I helped!

PatelCartel said:
I would love to help but unfortunately I'm not familiar with how to do that. However someone is bound to reply to your post and if not you should post this question in another forum on XDA more suited to this question. Meanwhile you can check out this web page: http://www.makeuseof.com/tag/trick-apps-android-rooted/ I haven't tried any of these methods so I'm not responsible if they don't work or damage your phone. I recommend you research more into these methods and be careful! I hope I helped!
Click to expand...
Click to collapse
Wow thanks in advance..alright i will try to more research..[emoji3]
Sent from my SM-N9208 using Tapatalk

I cant root this always happens:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.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> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Flash new firmware bro..but wait what firmware ver you using?i also have this problem before..
Sent from my SM-N9208 using Tapatalk
---------- Post added at 02:32 AM ---------- Previous post was at 02:27 AM ----------
smeth_90 said:
Flash new firmware bro..but wait what firmware ver you using?i also have this problem before..
Sent from my SM-N9208 using Tapatalk
Click to expand...
Click to collapse
Which firmware you using MM or lolipop?dont download wrong root package..because this file CF autoroot is two file for MM and lolipop ver firmware..also read carefully OP(orginal post) thread..dont forget to enable OEM LOCK AND USB DEBUGGING..[emoji106]
Sent from my SM-N9208 using Tapatalk