yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 General] phoenyxstarr:
I have been trying to fix my phone for ages & this guide was the first to get it off the dreaded "Firmware has encountered an error" message! So big thank you for that!

I'm still having a problem though. Before I got the error message, my phone was stuck in a boot loop. It is back in that loop now, after I completed STEP 1 - Odin to NB1 Stock and got a green "Pass" in Odin. I also did the steps to update my phone from the SD card.

The loop is a black screen, then my phone vibrates twice & then it shows the Samsung Galaxy S4 logo. Then after 5-10 seconds, it goes back to a black screen & starts over again. All told, the process takes about 40-45 seconds. Sometimes when the phone is in a loop, it will go further than showing Samsung Galaxy S4; it will actually start the Samsung animation. But before that finishes, the screen goes black & the boot sequence starts again.

What should I do now? I need to fix my phone because I need it for work as well as keeping in touch with family.
[AT&T Samsung Galaxy S 4 General] guut13:
Just to make sure I understand your issue...

You odin the NB1 base. Then phone boots up normal.

Then when you apply one of the updates, the phone boot loops? Which update is giving you trouble?
[AT&T Samsung Galaxy S 4 General] phoenyxstarr:
No, the phone never booted up normal after I odin the NB1 base. So I went ahead with the updates (all 3) and checked it after each update but it was still stuck in the loop.
[AT&T Samsung Galaxy S 4 General] guut13:
Thanks. You definitely want the phone to boot up the NB1 image before rebooting it and flashing the first update. Then you let the phone boot up before rebooting and flashing the next update.

There are only a few things that come to mind that would give you issues...

1. You have a different model. Can you look under the battery and confirm you have model SGH-i337?

2. The NB1 image you downloaded was corrupt. Which NB1 image are you using?

3. When Odin the NB1 image, you chose different options then the screenshot in post 1 has. (IE - was "auto reboot" and "f. reset time' the only boxes checked.

4. Driver issue. Unlikely since you got the "passed" message.

If all checks out. Can you try again, please? This time, after flashing, copy and paste the output of the message window. Maybe there is something there that will shed some light.
[AT&T Samsung Galaxy S 4 General] phoenyxstarr:
1 - I double-checked under the battery & it says "MODEL: SGH-I337"

2 - I used the files that were linked to in the first post.

3 - I made sure to only have the "auto reboot" and "f. reset time" boxes checked.

I will redownload the files from the links provided, retry & then past the message from Odin.

---------- Post added at 02:26 AM ---------- Previous post was at 01:45 AM ----------

The file I used was I337UCUFNB1_4.4_Stock_Odin_tar from here

The message from Odin:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> aboot.mbn

<ID:0/004> NAND Write Start!!

<ID:0/004> sbl1.mbn

<ID:0/004> sbl2.mbn

<ID:0/004> sbl3.mbn

<ID:0/004> rpm.mbn

<ID:0/004> tz.mbn

<ID:0/004> boot.img

<ID:0/004> recovery.img

<ID:0/004> persdata.img.ext4

<ID:0/004> system.img.ext4

<ID:0/004> modem.bin

<ID:0/004> NON-HLOS.bin

<ID:0/004> cache.img.ext4

<ID:0/004> hidden.img.ext4

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

My phone is in a boot loop right now, after flashing the above file & getting that message.
[AT&T Samsung Galaxy S 4 General] guut13:
Thanks for verifying and pasting the output. Nothing looks out of the ordinary.

You could try Odin the NB1 image again. This time with the PIT file that can be found in the OP of this thread...

http://xdaforums.com/showthread.php?t=2496517

(put the PIt file in PIT, NB1 file in AP, then Start)

If that doesn't fix it, then you might have a hardware issue. My only other recommendation is to take it to the Samsung Experience at your local Best Buy Store and have them take a look.
[AT&T Samsung Galaxy S 4 General] phoenyxstarr:
Even after trying that, my phone is still in a boot loop. I guess I'll check my Best Buy for the Samsung Experience to see what they say.

Thanks for helping me try to fix it!
[AT&T Samsung Galaxy S 4 General] guut13:
Sorry we couldn't get it. Let me know how it goes with the Samsung guys.
[AT&T Samsung Galaxy S 4 General] Kilbert:
Will this work with build i337ucufni1 ? I have yet to find a thread with that build #?
[AT&T Samsung Galaxy S 4 General] guut13:
Yes. All the references to NI1 in the first 3 posts are i337ucufni1.
[AT&T Samsung Galaxy S 4 General] gzronaglide:
Why does the ODIN downloaded indicate I9505 a Verizon model when this thread is about AT&T I337?

Who is this guide for?

Anyone using an AT&T Galaxy S4 (SGH-I337) AND...

-- has the MF3, MK2, MLD, NB1, NC1, NI1, NJ4, NJ5, OC3, or OC4 bootloader

-- wants to return their phone back to stock.

-- was told to “Odin back to stock” in another thread.

-- thinks they bricked their phone

-- is bored and wants to start fresh before flashing another ROM.
[AT&T Samsung Galaxy S 4 General] guut13:
Not sure what you are talking about. This thread is 100% ATT. I tested EVERYTHING in this thread myself on my ATT GS4.
[AT&T Samsung Galaxy S 4 General] gzronaglide:
Please check out the image of ODIN in the beginning of the original posting. The header of ODIN includes I9505. When I downloaded ODIN it was the same. Seeing a Verizon model number in the header made me nervous.
[AT&T Samsung Galaxy S 4 General] guut13:
Ah. Never noticed that before. But to help clear some things up.

Verizon model is i545.

i9505 is the model number for the international gs4... Basically, its the primary model worldwide.
[AT&T Samsung Galaxy S 4 General] imran yahya:
ho i use s4 at and t i337`

hi thanks a lot . I am very happy after downgrading my phone from lollipop 5.0.1(oc3) to KitKat 4.4.2(nb1).. now I rooted my phone with towel root...and now I am enjoying the full of my s4.thanks a lot for the method...it was my first time and I was scared but all was ok
[AT&T Samsung Galaxy S 4 General] Da_Goon:
Hello All,

I have a question if I may...

Is it possible to successfully ODIN back to NB1 stock if I am currently running Lollipop 5.0.1 (OK2) on my rooted AT&T GS4 i337?

The reason I ask is because I would like to flash the Albe95 S6 FULL PORT 4.6 custom Lollipop 5.1.1 ROM on my device but, that ROM requires a device to be running OC4. Since OC4 is a prerequisite I was thinking of ODIN back to NB1 stock and then following the proper methods of rooting and flashing to OC4 and then flashing Albe95 S6 FULL PORT 4.6 ROM via the following method http://xdaforums.com/galaxy-s4-att/development/port-albe95-s6-port-4-6-updt-30-10-15-t3241212.

Any thoughts and/or suggestions or better methods to having a 5.1.1 ROM on my device?

Thanks!

PEACE
[AT&T Samsung Galaxy S 4 General] guut13:
Yes. You can odin to nb1 from ANY base.

Before you do that, try flashing the ROM with your current base. Worst that can happen is it doesn't work and you odin nb1 anyway.

Check the index linked in op of you have questions on flashing.
[AT&T Samsung Galaxy S 4 General] Da_Goon:
Great advice! I was successfully able to flash the custom ROM from my current OK2 base, there was no need to ODIN back to NB1.

Thanks again!!!
[AT&T Samsung Galaxy S 4 General] ranros:
Am I reading this correctly in that there still is not a way to root an I337 with ok2?
[AT&T Samsung Galaxy S 4 General] guut13:
Correct. If you want rooted lollipop, you'll need to use the other bases.
[AT&T Samsung Galaxy S 4 General] xdause:
I looked around for a while now but I cannot seem to find my answer. I have nj5 and if I follow the root directions for nj4 is there an nj5 kernel you can install or do you leave it at nj4?

Thank you.
[AT&T Samsung Galaxy S 4 General] guut13:
Post 2 of this thread has the steps and links to all files needed to root NJ5.
[AT&T Samsung Galaxy S 4 General] cmekrishh:
thanks...but

First of thanks a lot... you saved me...

here the "but" part is that... after successfully updating to oc3 lolipop... s4 i337 hangs a lot... A lot means a lot..

Even if I reboot it... it sometimes hangs on AT&T logo or lockscreen and automatically reboots.. please help..
[AT&T Samsung Galaxy S 4 General] guut13:
Try the entire process over again. It's possible something didn't install properly.

If you still have the same issue, I suggest trying NJ4 to see if that clears it up. It's possible you might have a hardware issue.
[AT&T Samsung Galaxy S 4 General] mindstormer:
I have an AT&T Galaxy S4 I337 OC3 Android 5.0.1 on stock. Is it possible to unlock my bootloader or has it been bricked? If not, can someone link me to a guide to unlocking it? I've searched around this forum but I'm not entirely confident that the guides I've found are up-to-date or is for my specific phone. Also, when looking for custom ROMs, do I only need to pay attention to the build version (such as OC3) to ensure it is compatible? Any other tips?

Much appreciated.
[AT&T Samsung Galaxy S 4 General] guut13:
Hello. Guide is pretty much up to date.

No way to unlock bootloader. If you bricked your phone, try Odin nb1 to revive it.

Lookin the op for a link to the index with all rom flashing info. Basically, if you are on KitKat base, you can flash KitKat roms. If you are on lollipop base, you can flash lollipop roms.
[AT&T Samsung Galaxy S 4 General] Arasstor:
Hi,

Can I use the I337UCUFNB1_4.4_Stock_Odin_tar rooteable version to skip step 2 if I want to downgradefrom Lollipop 5.0.1 OC3?

Also, I have noticed that when I go to download mode there is a message in the left top corner that says Write protection: enable. will it be a problem if I follow your steps my current base version is lollipop 5.0.1 OC3

Regards.
[AT&T Samsung Galaxy S 4 General] guut13:
Not so much a downgrade. It's more of a wipe EVERYTHING and start fresh with NB1.

Not sure which step 2 you are referring to, but you can use the rootable tar file, if you want to stay on NB1. If you plan on upgrading to another KitKat base, better to use the regular NB1 tar file.

Can't recall the "write enbled" but I don' think it will be an issue.
[AT&T Samsung Galaxy S 4 General] Arasstor:
Rooting my Galaxy S4 i337

Thanks for your great tutorial guut13

when mentioned step2 I was referring to this tutorial : "HOW TO GET TO ANY KITKAT 4.4.2 (NB1, NC1, NI1) OR 4.4.4 (NJ4, NJ5) BASE" (sorry for the capital letters I just copied it) in STEP 2 - Flash Update(s) in Stock Recovery

So far the tutorial has worked for me, I wiped everything and started fresh with NB1, then I followed your second step (in HOW TO GET TO ANY KITKAT 4.4.2 (NB1, NC1, NI1) OR 4.4.4 (NJ4, NJ5) BASE) and I applied the upgrade for NJ4 because I wanted the kikat version 4.4.4 but now I don't understand the third step.

I want my phone rooted without Safestrap for now.

So, I did the following:

I download this files NJ4 --> NJ4_kernel.tar.md5 and NC1_kernel.tar.md5 from here :

1. Upload Towelroot and Safestrap zip onto External SDcard

2. Reboot into Download Mode

3. In Odin, flash NC1 Kernel file in the AP slot

4. Phone will reboot

5. Go into Settings > More > Security

--- check "Unknown sources"

--- uncheck "Verify apps"

Note: add this point the data or wifi wasn't working obviously because I changed the kernel to NC1 as you tutorial says.

6. Open My Files app, browse to Towelroot v3, click it, and install.

7. Open Towelroot and click make it ra1n

Note: when I clicked on 'make it ra1n' the app said it can't not be installed without connection.

then:

10. I Rebooted into Download Mode

11. In Odin, and I flashed the kernel for NJ4 in the AP slot

12. Phone will reboot when complete

13. the the wifi and data started worked again

14. I opened Towelroot v3 and clicked in make it ra1n but now the app says this doesn't work for your current android version.

So, I don't why I am doing something wrong or if I am misunderstanding something.

Could you advise me how to root my phone at this point(the step 3)?. So far I have installed kikat NB1 upgraded to NJ4.

Regards.
[AT&T Samsung Galaxy S 4 General] sway8966:
I do not know which guide you were referring to. May be guut13 might know. Please show the url of the post instead of the header.

If you odin the NB1 firmware then you can use Towelroot to root the phone.

You can use the stock recovery to upgrade to NJ4 using this NB1 to NJ4.

If you want to use the flashfire, install flashfire. (you can read the flashfire info here).

Then you install the I337UCUFNJ4_100%_Stock_Rooted_ROM via flash fire.

If you want to use to safestrap, first , you need to odin the NC1 kernel in order the safestrap to work. Then install the safestrap and flash the NJ4 rom via safestrap.
[AT&T Samsung Galaxy S 4 General] Arasstor:
This URL (guut13)

This is the guide I am talking about. http://xdaforums.com/showpost.php?p=56453108&postcount=2

and this the part of the guide I am trying to achieve: HOW TO GET TO ANY KITKAT 4.4.2 (NB1, NC1, NI1) OR 4.4.4 (NJ4, NJ5) BASE

So, I installed the NB1 firmware (step1) but then I upgrade it to NJ4(step2) and then I am trying to root the mobile(step3). But I am not sure if I need to install the NB1(step1) then root the mobile with Towelroot(step3) and then upgrade to NJ4(step2)?

is the order affecting the result?.

it's a lisle bit confusing.

Thanks in advance.
[AT&T Samsung Galaxy S 4 General] sway8966:
Mind you that the guide was written in 2014 and last updated in dec 2015.

in stpe #3 it clearly stated that towel root only works with NC1 kernel. That was why you need to odin the NC1 kernel before you use the towel root and then odin the NJ4 kernel. (However, in Feb 2016, when I update my phone, I found out that towel root works with NB1. )

In my previous post, I mistakenly told you that you odin the NB1, root the phone and , update with NB1 to NJ4 ota. If you do that you would loose the root. please disregard that line.

So if you install the NB1 (step1), then root the mobile with Towelroot (step 3), then if you want to upgrade to NJ4 you need to use either safestrap or Flash fire to flash the I337UCUFNJ4_100%_Stock_Rooted_ROM in order to keep your root.
[AT&T Samsung Galaxy S 4 General] Arasstor:
Hi sway8966,

Thanks for your reply but yesterday, I figured out what was the problem with my cellphone. After I completed the step 1 and step 2 which are install Kitkat stock 4.2 NB1 and then upgrade to the version you want (in my case NJ4). I successfully followed the instructions from step 3 to root the cellphone only (without install safestrap), but my problem was that when I opened Towelroot app, I didn't have signal on my phone which is necessary for the app to root the cellphone. I found the answer in the page 4 of this thread because guut13 mentioned that there (Link: http://xdaforums.com/showpost.php?p=56925595&postcount=37), but this is not specified in the guide in the step 3.

Thank you in advance for your help bro.
[AT&T Samsung Galaxy S 4 General] guut13:
Thanks for stepping in. As you pointed out... "towel root only works with NC1 kernel", Just to clarify...

There are 2 different NB1 odin files...

1. Stock NB1... This one is the EXACT image that ATT pushed out. This is the image you should use if you plan on upgrading to another base.

2. Rootable NB1... Someone, (muniz_ri, i think), took the Stock NB1 image and swapped in the NC1 kernel. This is why towelroot works with it. If you are planning on staying at NB1 base, you can use this image.

(NB1 kernel and NC1 kernel are so similar that swapping the kernels does not affect the modules.)

Glad you are all set. I added that note to the instructions on post 2.
[AT&T Samsung Galaxy S 4 General] marlins0397:
cannot update

Hey everyone,

I hope this problem has a simple fix, but after searching through most of the pages here I cannot seem to find exactly what I need.

I am trying to return my GS4 to stock so that I can sell it, but it doesn't matter what I do I cannot get it to take a kies update without the message "This device's version cannot be updated". From what I have read, this essentially means that I am rooted. I un-rooted and then used odin to NB1 as described in post #2 here and nothing has changed. What else do I need to do?

Thanks for any help!
[AT&T Samsung Galaxy S 4 General] guut13:
I've never heard of this phone updating with KIES... It only updates with the ATT OTAs. Follow the steps in post 2. It has links to all the files you need. Note - KIES is not one of them. In fact, I recommend uninstalling it as it doesn't always play well with Odin.
[AT&T Samsung Galaxy S 4 General] marlins0397:
Ok, thanks. Good to know.

However, I was trying to use KIES because the OTA updater says that I am up to date. How is that possible if I am on NB1 4.4.2??

Thanks!
[AT&T Samsung Galaxy S 4 General] Arasstor:
Hi guut13,

I have a quick question for you. is there a way to remove the custom logo (padlock image) in the animation boot?

because after I rooted my S4, I am getting that image there every time I restart my phone, I know is not an issue but it bothers me.

When I had my Samsung galaxy S2 I9100, I remember there was an app to remove the exclamation logo that appears when you root that phone. Is there something similar for SGS4?

Regards.
[AT&T Samsung Galaxy S 4 General] guut13:
Yeah... that's common. And after you fail to find an OTA, you have to wait 24 hours before checking again. So you have to forward your clock a day and it still fails. I don't think the GS4 ranks high on the ATT update priority list. Add to that that you are trying to upgrade an older firmware.

That is why we pulled the update so you can flash it on your time and not be dependent on ATT.

Yes. but it's a crapshoot. From way back on kitkat, sometimes it showed up, sometimes not... From what I recall... the less you muck with stock, the better chance you have. (IE - odin nb1 then upgrade to NC1. root and safestrap... you should be ok. If you update to another base, then have to flash back the nc1 kernel to root, and then odin the other kernel back... the lock appeared.)
[AT&T Samsung Galaxy S 4 General] userwaldo:
Using Heimdall on Linux to Flash NB1

I pulled together some information on using Heimdall to flash NB!, for those on Linux.

Thought I would share it here. Hope someone else finds it useful as well.

FLASH NB1 using Heimdall:

Power off phone

Boot into Download Mode

press and hold BOTH power and volume down buttons

when you see "Warning!" screen, release both buttons

press volume up to continue

Connect phone to PC via usb cable

On PC ... Remove .md5 and extract .tar from Rootable NB1

User Heimdall to restore to NB1: (MD5 files must be extracted)

This is based on info from this post.

NOTE: As the original poster said, each push will require a boot back into Odin’s Download Mode, hold the ‘volume down & home’ buttons in between reboots as soon as the screen goes black, then press volume up to ‘continue’. After 4th heimdall flash you’ll want to boot to the stock Recovery Mode (volume up on boot) and do a “Factory Reset / User Data Wipe”; this will insure you’re good to go.

sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img

sudo heimdall flash --MDM modem.bin --APNHLOS non-hlos.bin --ABOOT aboot.mbn --TZ tz.mbn

sudo heimdall flash --CACHE cache.img.ext4 --PERSDATA persdata.img.ext4

sudo heimdall flash --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --RPM rpm.mbn
[AT&T Samsung Galaxy S 4 General] guut13:
Thanks. Link added to OP.
[AT&T Samsung Galaxy S 4 General] SgtMac02:
HELP! I bricked it!

HELP! I bricked it!

Background info:

I was following instructions from this thread: "[How-To] I installed a custom Lollipop ROM on my AT&T Galaxy S4"

I executed all of the steps as noted in the OP (as far as I know) with one exception. I used a different ROM. I tried to flash the Resurection Remix ROM. When I got to the 4.3.7 step of that post, I couldn't get past the SafeStrap screen. I would press Continue 4 times, then the screen just went black and stayed that way. I tried multiple times. Then I tried going back into Recovery, and that wouldn't work either. Just black screen. Now, the only thing I can do is go into the stock recovery by pressing volUp+menu buttons. Tried re-flashing the roms that were on the SD card and it won't flash any of them.

When I try to flash, I get

verifying update package...

E: failed to verify whole file signature

E: signature verification failed

So...I figured I would try to Odin back to stock...which brings us here to this thread.

I tried to Odin back to stock (using "I337UCUFNB1_TWRootable_Full_Odin.tar.md5"), but Odin fails.

When I click start it just says "<OSM> All threads completed. (succeed 0 / failed 0)"

I couldn't find anything in the comments that was similar, so I'm hoping one of you fine intelligent folks might be able to help.

Any help would be GREATLY appreciated. I'm desperate here!

EDIT:

Based on suggestions from my other post HERE, I made a tiny bit of "progress"

I was using the same cables and ports I had previously used, but based on suggestions, I made sure to go and manually reinstall USB drivers, swapped around ports and cables, and tried to Odin again with a fresh download. I did note that Odin appears to be seeing the phone on the USB port. And now I get a different failure message. Here's the output:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> sbl1.mbn

<ID:0/003> NAND Write Start!! <ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/003> Removed!!

<ID:0/003> Added!!

If you think you might have some insights, please feel free to join the convo on either thread.
[AT&T Samsung Galaxy S 4 General] guut13:
Perhaps it was a bad download. Try again with the stock nb1 file. (Non-rootable)
[AT&T Samsung Galaxy S 4 General] SgtMac02:
Sorrry, I neglected to come back here and mention that in the other thread I got some help that got me out of my jam. I did, in fact, already try redownloding the original ROM and had no luck. But in the other thread someone linked me to a different version of Odin and a different stock ROM to download and flash. I was able to get up and running again after that. Thanks for your suggestion and attempt to help though.
[AT&T Samsung Galaxy S 4 General] guut13:
No worries. Thanks for the update. Checking out the other thread... My instructions points to the same stock NB1 image, so the issue must have been odin on your pc. Glad the newer Odin worked for you. What version of windows are you running?
[AT&T Samsung Galaxy S 4 General] SgtMac02:
Running Windows 7 Pro 64bit.
[AT&T Samsung Galaxy S 4 General] guut13:
Thanks. That's what I have too. Oh well, there goes that theory.