Database Users

[Q] Root Attempt after OTA - ODIN Failed (FAIL! Auth)- Secure Check Fail Cache

This has been a long day...
I previously rooted my N900V Note 3 using the Root_de_la_Vega method. Everything was fine until last night when I stupidly accepted the OTA update from Verizon. I lost root because I forgot to persist Super User. Without thinking I started to reroot using the original Root_de_la_Vega method. The ODIN attempt failed.
This is the message stream from ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the top of my Note 3 it says SECURE CHECK FAIL : cache
My phone will now only boot into ODIN download screen, and gives me the message: "Firmware upgrade encountered as issue. Please use Software Repair Assistant & try again."
My guess is that I have tried to flash/download a mismatched ROM.
Any suggestions on how to get past the ODIN boot screen and back into normal operation?
Any help would be appreciated, obviously...

Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.

NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
How/where do I find the PIT file?

http://forum.xda-developers.com/showthread.php?t=2483380

NeoMagus said:
http://forum.xda-developers.com/showthread.php?t=2483380
Click to expand...
Click to collapse
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?

cmubigguy said:
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
Click to expand...
Click to collapse
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it

NeoMagus said:
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
Click to expand...
Click to collapse
I guess I'll just wait for a safe way to root post-OTA. I can live with no root for a while. Thanks for helping out, I shot you some cash for your time and not making me feel like a complete idiot.

I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3

goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse

goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
I just tried what rhymes with bingo, and it didn't work. It's likely because I just took the OTA straight away without using Kies or unrooting through SU. What was your unroot/re-root method?

I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one

NeoMagus said:
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
Click to expand...
Click to collapse
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?

cmubigguy said:
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
Click to expand...
Click to collapse
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread

NeoMagus said:
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
Click to expand...
Click to collapse
Do now. It turns out I needed to reboot my laptop after I installed Kango.
I'm back rooted!

I wasn't previously rooted. I took the OTA then rooted with bingo. Then installed safe strap with no problems.
Sent from my Galaxy Note 3

NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
This worked for me, I flashed the pit for MJ7 and was able to get out of soft brick

Had the same issue, resolved with .pit solution above. Can we include a note in the N900V Root de la Vega instructions? IE: If you have update to Baseband version N900VRUBMJ7, attempting to flash through Odin will fail on cache writing.

I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.

kalagula said:
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
Click to expand...
Click to collapse
After you install Kango, don't enter the download mode, just boot the phone as normal and make sure USB debugging is on. Attach the phone to Kango, and it will download and install the necessary drivers. Once those are done, you can attempt to root, but it likely won't take. Restart your computer, and then reattach the phone. Try to root method again, and it should work. That's what worked for me.

cmubigguy said:
Try to root method again, and it should work.
Click to expand...
Click to collapse
Yeah, mine just sits there for a while, after which it says "ROOT failed! NotSupport". Bummer!
Edit: after 5 tries, it worked. Still got the ROOT failed error, but I did get root! Thanks for your help.

Bricked Device

I got a S4 today and I rooted it, and flashed CWM recovery, backed up the firmware, rebooted and everything was good. I updated the phone an hour so later and the boot hung on yellow Sprint screen. I rebooted into recovery and re-flashed my backup but that didn't fix the device. Now I've been trying to flash back to stock using Odin and this is what I see.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I was on 4.3 when this all started so I am attempting to flash the MK2 file back on my device. I removed the drivers, and re-installed and that made no difference. Any advice would be great.

Did you accept an OTA? Or did you try to flash a stock MK2 ROM?
I'd say flash an older tar if possible, especially if you plan to root again or install a custom ROM. The MK2 bootloader has KNOX enabled, so any root/custom ROM installs trip the counter.

sorry if this doesn't help, but have you tried different versions of odin? also tried different usb ports? idk what you're flashing or if this is what you want, but there's a stock mk2 rom on this thread if you wanna' try that. http://forum.xda-developers.com/showthread.php?t=2575470

I believe it updated via OTA after I activated it today. This was before I rooted. I am currently trying to flash the MK2 Rom. I've also tried MJA which is older. Is there an different older one that could work? I am planning on rooting again, but was going to run the stock rom for the time being. I've never an a touchwiz rom so I'm interested in trying it.
I have tried 3.09, 3.07, 1.85 for versions of Odin. All the same error.
I'm able to flash TWRP recovery from Odin without the error, but not the stock rom which is a bit confusing to me.

When you say
I updated the phone an hour so later
Click to expand...
Click to collapse
what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.

leaderbuilder said:
When you say what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.
Click to expand...
Click to collapse
I updated some apps and rebooted. Always find that this best after a lot of app updates.
Odin running as admin on Win 7 64. Mostly been using 3.07. USB cable is the new one that ship with the phone.
I've been looking for a stock recovery I can flash with Odin but can't seem to find one. Can you provide a link? Maybe I'm just missing it?

Are you flashing the full MK2 including boot? There's some thing where the phone refuses to boot into an MK2 ROM unless you've updated the bootloader as well.

I got the full rom from here: http://forum.xda-developers.com/showthread.php?t=2601443 I also tried flashing MJA too and I get the same message in Odin. I'm sure that I have the MK2 bootloader as it shows my knox being 0x1.

Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.

cruise350 said:
Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.
Click to expand...
Click to collapse
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.

benpfeil said:
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.
Click to expand...
Click to collapse
Hmm, you're doing or missing something because in the last week or so there have been about five or ten people with close to the same issue (HELP, I'M BRICKED, MY LIFE IS OVER...etc.) and we've mangaged to get them all work. I've posted dozens of replies to those people and they've been able to get up and running following others and my advice(s).
Spend some time and go through the first few pages of the Q&A, Help forum and read all the way through some of the similar posts. Then try what is suggested in them.
You will resolve your issue. IF you don't, just warranty your phone or grab an iPhone.

I broke down and stopped into Sprint tonight. I had tried the process on 3 different PC's and still no luck. They tried to flash it and weren't able to as well. The woman in the store told me they could not exchange it because they do not have the phone yet. I was confused by this. The phone that I have has "Sprint Spark" on it which is a tri-band phone and the stores do not have it yet. My company has a large plan with Sprint and we get our phones shipped directly to us. She said I would have to have my procurement person request a new phone for me. My model is actually SPH-L720T. My guess is that this was causing my issues.
Thank you to you all who tried to help out.

My model is actually SPH-L720T. My guess is that this was causing my issues.
Click to expand...
Click to collapse
YEP!
That would be the problem.

leaderbuilder said:
YEP!
That would be the problem.
Click to expand...
Click to collapse
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.

benpfeil said:
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.
Click to expand...
Click to collapse
I didn't think XDA had a forum up yet for SPH-L720T.

Sammobile.com has the mk5 tar file for the 720T.
Sent from my icrap 2 using Tapatalk HD

[Q] Galaxy S4 (i337) on 4.4.2 Rooting/Recovery Issues!

Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. The phone can be plugged in and charging and still discharge until it dies. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:

Nati0n said:
Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:
Click to expand...
Click to collapse
SGH-i337 has a locked bootloader. That prevents us from replacing the stock kernel and recovery. The only working recovery we have is safestrap.
The bootloader also prevents a downgrade unless the versions are compatible. NB1 and NC1 are compatible and so you should be able to flash the stock NB1 firmware using Odin.
Since you have root already, you can install safestrap after setting SELinux to permissive mode. Use the selinuxmodechanger app from play store for that.
All things AT&T thread.

So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?

Nati0n said:
So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?
Click to expand...
Click to collapse
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.

sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?

patstar5 said:
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?
Click to expand...
Click to collapse
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

drock212 said:
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!

patstar5 said:
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!
Click to expand...
Click to collapse
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.

sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Ah okay understood, thanks for linking me to that thread I will look through those Touchwiz based roms. I was hoping to go to a Google Play Edition ROM too but from what I'm reading a lot of things don't work on it.
Thanks again everyone for your knowledge and advice. In reality do you think flashing a custom Touchwiz based ROM will address my issues or should I just downgrade to NB1? And is there REALLY no way to unlock the S4 bootloader on GSM devices? I thought someone did it on a CDMA version recently.
UPDATE: I should have reread the first post, after installing SELinuxModeChanger and setting it to permissive, I was able to get SafeStrap to install and boot properly.

You need to have selinux in permissive mode. Use selinuxmodechanger app for that.

jmjoyas said:
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.
Click to expand...
Click to collapse
OK, downloaded first file here:http://forum.xda-developers.com/showthread.php?t=2674223
After flashing, I can do OTA update to get one NC1?

Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.

Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
All the ROMs listed in the all things at thread will work.

Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.

Nati0n said:
Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.
Click to expand...
Click to collapse
Every time you reboot the phone, you will lose WiFi. You can recover it by soft rebooting the phone.

s4 recovery issues
Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
could you tell me the steps you took? i'm stuck with a rooted samsung s4 also. this is my phones info. i would appreciate the help. many thanks will come your way.

Help with Rooting Galaxy S4

Hello, everyone. I'm new to this site, and have come here because I've gotten a bit desperate. I have been trying to root my AT&T Galaxy S4 (Model number: Samsung-SGH-I337, Android version 4.4.4) for a long time and have been unable to. I have tried multiple programs, such as Kingo Root, Root Genius, and towelroot. Nothing worked until someone I know told me to go to TomsGuide (a website; I tried to post the link, but was unable to) and follow the steps. It seemed to work at first, because I now have SuperSu and Superuser in my apps.
However, when I open the Superuser app, a message pops up: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." There are two options: Cancel and Recovery Install. Nothing happens when I click Cancel; when I click Recovery Install, I receive this message: "There was an error installing Superuser. Please send a log of the error to the developer."
I have also gone into My Files on my phone and found the apk files (there was one on my SD card and one in the phone's memory). I installed both, but when I opened it, I either received the same message as above or this one "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
I am not sure what to do now and have been unable to find the answer to this problem yet. Any help would be appreciated. I am also new to this kind of stuff, so detailed explanations would be nice. Thank you in advance.

Kingroot DESKTOP will root a S4. Look for my post on the subject.
Unfortunately I haven't figured out how to include links in my posts from Tapatalk. Maybe someday.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

This thread should help you out: http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553

Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.

phoenix_fire said:
Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
Click to expand...
Click to collapse
Agreed.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.
Click to expand...
Click to collapse
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.

creepyncrawly said:
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.
Click to expand...
Click to collapse
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.

phoenix_fire said:
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.
Click to expand...
Click to collapse
Baseband is the modem. Usually when stock firmware is installed, kernel, system and baseband will all be the same, although the modem can be installed individually, but you would probably know about it since you would have had to do it yourself. So let's assume that you are on NJ5 system. When you look in about device, "Build Number" should tell you which system and kernel is installed.
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.

creepyncrawly said:
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Click to expand...
Click to collapse
Wow! Thanks; I'll give this a shot. I'll look for a tutorial for using Odin, but I'd appreciate if you could post one for me as well.

creepyncrawly said:
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.
Click to expand...
Click to collapse
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?

phoenix_fire said:
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?
Click to expand...
Click to collapse
From what you say above, you tried to flash the pit file alone, without a firmware. From what I understand, it is usually flashed in conjunction with a full firmware. It may not work when flashed by itself.
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
When Odin flash fails, it is very often a problem with the connection between the computer and the phone, so it is always a good idea to make some changes and try flashing again. Use another cable, use another port on the computer, especially one that is connected directly to the motherboard on a desktop pc, or even use another computer. Also, you might try a different version of Odin. If you are using v3.09 or similar, you might try v1.85 which you can download from my Download Repository (see link in my signature.)
Try again to flash the NC1 kernel, as in step 3 of the guide.
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different. In Odin 3.09, the PDA slot is named AP.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer and into the phone.
3.) Shut the phone off.
4.) Put the phone into download mode.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
11.) When complete, you will get a PASS (or FAIL if unsuccessful).
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.

creepyncrawly said:
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
Click to expand...
Click to collapse
I wish I had thought of that, too.
creepyncrawly said:
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
Click to expand...
Click to collapse
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.

phoenix_fire said:
I wish I had thought of that, too.
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.
Click to expand...
Click to collapse
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.

creepyncrawly said:
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.
Click to expand...
Click to collapse
Hi. Sorry about the late response; I've put trying to root my phone on the back burner for now, since I am really busy at the moment and things aren't going to slow down for a while. I'm going to attempt to figure it once more around Christmas time, so you'll hear from me again around then! Also, I just wanted to thank you for your help thus far; I appreciate it!

Looking for Samsung Galaxy On5 SM-G550T1 Stock ROM Please Help!

So, I upgraded my phone yesterday from the Samsung Core Prime to the Galaxy On5 and the phone was great. I used it through out the day and then proceeded to root the device last night using an app called Root All Devices, which is supposed to detect your phone and tell you what to download and how to root that specific phone. Well, its obvious that it didnt work or else I wouldnt be here. I cannot even get into recovery mode. The phone only allows access to the downloading screen, nothing more. I have searched all night looking for a ROM for SM-G550T1 to use with Odin, but came up with nothing at all. I did try to use the SM-G550FY (Indian version?) but that had the exact same result in Odin. When i tried to root the core prime I had similar problems, but once I located the stock ROM for it it worked perfectly. From past experience with my Core Prime I knew to turn on OEM unlocking (FRP lock is off), allowed unknown sources, turned on USB debugging, and the USB drivers are already installed, so everything is great as far as that goes. My carrier is MetroPCS also. Below is the failed result from Odin:
<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/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If someone or anyone would be kind enough to create and upload the stock ROM for the SM-G550T1 (MetroPCS), I would be extremely grateful and I know many others would be as well. Thank you guys. Please help us.

I've been trying to root my on5 sm-g550t with no luck, no methods work. I think this is because this phone is not well known. My carrier is t mobile and can barely find any info on the U.S. device. So I guess try the Indian root on the phone? I have such a hard time and I just want to find a method to root it.

Leo2nardo said:
I've been trying to root my on5 sm-g550t with no luck, no methods work. I think this is because this phone is not well known. My carrier is t mobile and can barely find any info on the U.S. device. So I guess try the Indian root on the phone? I have such a hard time and I just want to find a method to root it.
Click to expand...
Click to collapse
Using TWRP you can install SuperSU to root. I had success with this method last night.
http://forum.xda-developers.com/android/development/recovery-official-twrp-on5ltetmo-galaxy-t3422730

Flyingcow29 said:
Using TWRP you can install SuperSU to root. I had success with this method last night.
http://forum.xda-developers.com/android/development/recovery-official-twrp-on5ltetmo-galaxy-t3422730
Click to expand...
Click to collapse
I can also confirm the aforementioned TWRP method works. I held the power,volume up, and home buttons just till the samsung logo appeared
when rebooting into TWRP recovery.:good:

Flyingcow29 said:
Using TWRP you can install SuperSU to root. I had success with this method last night.
http://forum.xda-developers.com/android/development/recovery-official-twrp-on5ltetmo-galaxy-t3422730
Click to expand...
Click to collapse
Does this flash the T-mobile version of the phone or the metroPCS version? I need the metropcs icons and so on...

MetroPCS
L1ghtF00t said:
Does this flash the T-mobile version of the phone or the metroPCS version? I need the metropcs icons and so on...
Click to expand...
Click to collapse
I would like to know if you have determined if this will work on MetroPCS. I am looking for the same info.

JckSpade888 said:
I would like to know if you have determined if this will work on MetroPCS. I am looking for the same info.
Click to expand...
Click to collapse
The link says it will "work" for metroPCS, but i dont know if it provides the user with t-mobile icons when completed or metroPCS icons.

i am in a similar situation i did not know about oem unlock, i cannot use my phone it only goes into download mode. i am in dire need of the stock firmware for the g550t1

on5 bricked now because of bad firmware
If anyone finds the T-Mobile firmware version, please let me know where it is located. The Indian version does not work. My on5 has became brick because of a firmware issue. The model number is SM-G550T. Thanks in advance.

klystron01 said:
If anyone finds the T-Mobile firmware version, please let me know where it is located. The Indian version does not work. My on5 has became brick because of a firmware issue. The model number is SM-G550T. Thanks in advance.
Click to expand...
Click to collapse
there's a twrp backup of it at https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing if you're able to get it going would you be able to make me a stock recovery.img and system.img?

bandtab said:
there's a twrp backup of it at if you're able to get it going would you be able to make me a stock recovery.img and system.img?
Click to expand...
Click to collapse
i have tried it ordin can not transfer one file at a time unlike other files related to rooting i have the problem of opening the clean factory folder and getting a few files and i cant AP one file at a time ...any way around this ? (soft-bricked) thanks and i have a boot.img if that helps?

Boot.img
killereddie said:
i have tried it ordin can not transfer one file at a time unlike other files related to rooting i have the problem of opening the clean factory folder and getting a few files and i cant AP one file at a time ...any way around this ? (soft-bricked) thanks and i have a boot.img if that helps?
Click to expand...
Click to collapse
Can you load the boot.img somewhere so that we can get it? There are ways you can convert a TWRP image to a bootable image, according to what I have read.

klystron01 said:
Can you load the boot.img somewhere so that we can get it? There are ways you can convert a TWRP image to a bootable image, according to what I have read.
Click to expand...
Click to collapse
Have you guys try smartswitch?

britchel said:
Have you guys try smartswitch?
Click to expand...
Click to collapse
Yes, the firmware files aren't available for it to work

klystron01 said:
Can you load the boot.img somewhere so that we can get it? There are ways you can convert a TWRP image to a bootable image, according to what I have read.
Click to expand...
Click to collapse
No guarantee this won't mess everything up, but it's the boot.img I got from that stock twrp backup, and it flashes fine to my phone.
https://drive.google.com/file/d/0BwpP0WNhAe9vTDUwdmE1dVRNV3M/view?usp=sharing

bandtab said:
there's a twrp backup of it at if you're able to get it going would you be able to make me a stock recovery.img and system.img?
Click to expand...
Click to collapse
I have TWRP installed but it wont flash the file it just errors out everytime is there anything speical I need to do to install the file?
Thanks

By any chance, did u do a factory reset?

britchel said:
By any chance, did u do a factory reset?
Click to expand...
Click to collapse
Tried to. Originally I couldn't get into recovery mode bc FRP was blocking me from using the TWRP recovery, but I just got a copy of stock recovery.img and flashed it so I can access recovery mode again finally. But I can't really do anything with it, no /system access, no USB access, so I can't wipe anything or do anything with recovery mode it seems.

bandtab said:
Tried to. Originally I couldn't get into recovery mode bc FRP was blocking me from using the TWRP recovery, but I just got a copy of stock recovery.img and flashed it so I can access recovery mode again finally. But I can't really do anything with it, no /system access, no USB access, so I can't wipe anything or do anything with recovery mode it seems.
Click to expand...
Click to collapse
Don't do it...you're to make it worst...
Try reinstalling again. With and without Odin

britchel said:
Don't do it...you're to make it worst...
Try reinstalling again. With and without Odin
Click to expand...
Click to collapse
reinstalling what tho? i've got nothing to reinstall, and how would I reinstall anything without odin?
what I need is just a system.img for my phone, if I could get a stock version of that I think I'd be fine, but it's not easy getting one