yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
So I think I've bricked my phone. First time. Ever.

I have an AT&T branded S4 that is barely two days old. Here is what happened.

After I installed it, AT&T apparently pushed an OTA update to the phone. Thinking nothing of it, of course I updated.

Then I rooted it using this method: New Root Method for AT&T Samsung Galaxy S 4 (OTA MF3)

I checked everything, phone was rooted correctly etc

Installed TitaniumBackup Pro and did both an update.zip backup as well a standard backup (to a 64GB SD card)

Woke up this morning, phone had apparently rebooted itself because it was stuck on the AT&T logo screen. Several attempts to reboot it, yielded same results. Curiously, during bootup, there is an open lock symbol with the word Custom underneath. The Samsung flash screen plays, then it goes to the AT&T logo screen. And stops. I waited over 15 mins each time before deciding that something was definitely amiss.

Booted into stock recovery mode (VolumeUp + Home + Power) and did wipe/data factory reset

Booted into stock recovery mode again, this time tried wipe cache partition. It displayed Erasing and then Error! - and phone rebooted. That's when I knew something bad was up.

So I did what comes naturally. I came here. :)

I found this thread and followed the instructions. Since I'm a software developer and having done all this before with previous phones, this was all straighforward

When I booted into Odin (VolumeDown + Home + Power then VolumeUP) mode, what I saw concerned me. See that last line? Is that normal?

Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable

Continuing, I ran the Odin update from the first post of this thread. That's when, after a single Blue dot appeared on the phone (under the "Do not turn off target!!!) it failed. Here is the output.

<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/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

And two new lines appear on the phone, which is exactly what you see over in this thread

ODIN MODE

PRODUCT NAME: SGH-I337

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

CSB-CONFIG-LSB: 0x30

WRITE PROTECTION: Enable

START [224,1440]

SW REV. CHECK FAIL : fused: 2, Binary: 1

So, how screwed am I and how can get back to stock? I am going to assume that the OTA update that I received was MF3.

Note that, as previously mentioned, I have a full update.zip TitaniumBackup as well as a complete backup on the ext SD card

Thanks for your help in advance!
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
Still trying to resolve this.

Thus far, I have tried the Kies emergency recovery, which also fails with a message about an error and to contact Samsung Service.

Then I tried updating MF3 over itself, using the OTA file located here. This I think gave some info on what may be happening.

As you can see from the shot I took (using my iPhone5, LOL!!), there are a couple of errors. One is an assert in a package and the other is about being unable to mount /sdcard1

I think /sdcard1 is the internal storage, though I remember that one being /sdcard0 when the phone was in fact working. /sdcard is the external storage from which I was able to apply the OTA update mentioned above.
[AT&T Samsung Galaxy S 4 Android Development] mdanish4:
+10...

. Exactly same situation here... someone to help?? I am stuck on (FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN)
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
If after trying to using Kies recovery you are stuck at the Yellow triangle and unable to enter download or Odin recovery mode, use the step in this thread. The Cure for Kies Update Error Triangle Screen. When my Kies emergency recovery failed, I was stuck in this state and this simple step reverted me back to where I could enter download and Odin recover mode again.
[AT&T Samsung Galaxy S 4 Android Development] thacounty:
That's download mode not recovery. Use the other volume button when holding power.
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
That's download mode. If you read my previous post, you would see that recovery is to hold VolumeUp + Home + Power, then release Power when your phone vibrates.
[AT&T Samsung Galaxy S 4 Android Development] mdanish4:
Brother thats what I am saying.. when I press v9lume up and home and power button it gives me that (failed to normal boot. Odin mode). I know how to get in recovery bro my recovery is screwed... I am able to go to download mode and able to boot my device in to rom.. but unable to go to recovery.
[AT&T Samsung Galaxy S 4 Android Development] thacounty:
Are you using this on a tmobile phone?
[AT&T Samsung Galaxy S 4 Android Development] mg2195:
Just so everyones clear, yiu dont have to hold the home button when entering download or recovery just volume up or down when booting up. if my phone is on ill just extend power menu hit reboot and hold volume up if I want recovery...no need to add extre stress to your home button and wear it out.

And to mdanish...your phone is workimg except recovery...leave it alone. Based on other threads/posts it appears your on mf3, there is nothing you can do if that's the case
[AT&T Samsung Galaxy S 4 Android Development] mdanish4:
Naw man.. I have I337...

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

Allright.. thats what I am gonna do now... (sigh)
[AT&T Samsung Galaxy S 4 Android Development] Aou:
My guess is that they will simply Odin flash it with MF3 without looking twice, charge you some money, and send it back. Again, that's only a guess, because I've never personally dealt with them. There are some reports here on the forums of people sending in "custom" phones, I believe.

EDIT:

Oh, and the phone is still rooted. Unless you've rebuilt/re-flashed your /system partition somehow, it's all still there. Root lives in /system, and all stock methods of wiping will not touch /system (apart from a proper Odin flash).
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
Thanks.

I am going to send it back to Samsung today and hope for the best.

Either way, since the phone is new, they couldn't possibly charge me more than the insurance deductible or what the guys at mobiletechvideos.com would charge (about $60) to do a JTAG restore of the system partition. So I think it's worth a shot.
[AT&T Samsung Galaxy S 4 Android Development] MaxCarnage:
Glad this is here; I borked my recovery and am going to need this to get back my customizations. Thanks!
[AT&T Samsung Galaxy S 4 Android Development] mdanish4:
What is here?? And how u will getvur customizations back since u bricked your recovery? Please share.
[AT&T Samsung Galaxy S 4 Android Development] MaxCarnage:
What I think I've done is I tried to flash a custom recovery that I didn't notice wasn't LOKI patched, so now the phone gives me a "non-AT&T approved software" error whenever I try to boot into the recovery. I figure I'll ODIN it back to stock with the image in the OP, run the root/recovery flash again, restore my nandroid, and be golden again. But getting it to boot back into the OS again by itself was a pain, and I was pretty irritated with myself (and AT&T) this morning.

EDIT: mdanish4, I just went back and looked at your posts and my issue is nothing like yours; I didn't (and wouldn't) take the OTA, I just messed up my recovery. I'm still on MDL. Sorry if I got your hopes up; I honestly didn't even read most of this thread.
[AT&T Samsung Galaxy S 4 Android Development] mdanish4:
U were on AMF3 uodate?
[AT&T Samsung Galaxy S 4 Android Development] MaxCarnage:
No.
[AT&T Samsung Galaxy S 4 Android Development] MaxCarnage:
Adam, between this and your CASUAL tool, I am back in business on my favorite ROM. I know you don't need to be told that you're the man, but I feel obliged to let you know that I recognize your manliness too. Thanks brother.

---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------

It bears asking: what firmware version does it have on it?
[AT&T Samsung Galaxy S 4 Android Development] indie_dev:
Last night, I was busy with work, so I didn't do much with the phone other than setup the Google a/c and set it down to download everything. Since this is just a second phone (my primary phone is an iPhone5), I really didn't want to mess with it until I had more time today. As such, I didn't even bother to check the firmware, after taking the DSC tech's word for it that it would be the latest, in this case MF3.

This morning, I picked it up the phone to see if everything was downloaded. Right there on the screen, it informed me of an AT&T software update.

Bracing for impact, I asked it to remind me later. Then I checked the device. Lo and behold, it's got MDL on it!!!

Since my previous phone was new and I haven't had much time to find out the differences between MDL and MF3, let alone the benefits of upgrading to MF3, now I'm stumped on what to do. LOL!! :confused:
[AT&T Samsung Galaxy S 4 Android Development] MaxCarnage:
What you need to do is go to the S4 General forum and read every sticky in there. Just the fact that after everything you went through in this thread dicking up your phone that you would ask what the benefits of upgrading to MF3 might be tells me that you still have some learning to do. :p Don't do anything until you've done that. I recommend you start here, and don't just skim it, read it:

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

You're well on your way; just need to get the basics down and learn how to use the forum properly.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Boys, can we please stop and get back on topic.
[AT&T Samsung Galaxy S 4 Android Development] henry333:
Thought I had a chance to use the stock firmware here. The display on my <2 month old AT&T S4 stopped working suddenly for no reason - it still +rang when someone called. I tried to put the phone into recovery or download mode but had no ways to know whether it succeeded.

When I took it to a AT&T Device Support Center, the support person came back with

1. The phone had water damage (I felled into a pond the day after I got the phone)

2. There is a hair-line crack on the edge of the screen (not aware of the problem and have no idea what happened)

Even neither problem is an obvious cause of the display problem, I will likely have to pay the full price of the phone if I send it in for warranty service. I can understand the water sensor issue but even issues like hair-line cracked are spelled out in the multi-page agreement we signed.

Eventually, I ended up paying some kind of exchange fee (~$180+tax) and got a new phone without having to admit any wrong doing.

The new phone came with MF3 firmware which means no custom ROM for me for a while. Oh well, I am grateful that it can be rooted.
[AT&T Samsung Galaxy S 4 Android Development] Naddict:
Thread cleaned lightly as things were going off topic and I do not like to see trolls who want to argue over childish stuff that only serves to clutter development threads.

If you have nothing to offer, at least respectfully, then I suggest you log off and find another place for that mess.

Let's get back to the furthering of development.
[AT&T Samsung Galaxy S 4 Android Development] SNadler:
Does anyone have a working link to AMDL for ODIN?

I have tried to DL two nights in a row now from here and it has been failing.....

Thanks in advance!
[AT&T Samsung Galaxy S 4 Android Development] SNadler:
I did look there, never used it before so I may not be seeing it but I cannot find it there either......
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
You have to register, but it's free. Click on firmware.
[AT&T Samsung Galaxy S 4 Android Development] SNadler:
Thanks, I am trying now.......
[AT&T Samsung Galaxy S 4 Android Development] havlaz:
hi, i'm getting fail always in odin.

why?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Do you know what firmware you're on? Is it mf3. Look at your baseband in setting, more, about phone
[AT&T Samsung Galaxy S 4 Android Development] havlaz:
Now i can boot the phone. It takes me strate to download mode.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
You most likely were on mf3 firmware. Odin doesn't work. When it goes to download mode can you cancel, vol down?
[AT&T Samsung Galaxy S 4 Android Development] havlaz:
i did what you told me, got into download mod then press vol.dow, the the phone booted android normally!

and yes, im on MF3 version.

2 things:

1) i steel cant get into recovery (take me to download mode)

2) can i flash cwm on this ver.?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
You can not flash cwm. You have the mf3 firmware. Because you tried to flash with odin with mf3 firmware you no longer have recovery mode. You're going to have to wait until there is a firmware package for mf3. In the mean time do a lot more research on what you can do and can't when on mf3. You're a flash away from a brick!
[AT&T Samsung Galaxy S 4 Android Development] alfmetal:
My first rom install was on a bootloop then I repeteated all the steps and now my phone works just fine, dont skip anything. Im on mf3 by the way
[AT&T Samsung Galaxy S 4 Android Development] phillytothemax:
correct if im wrong this is for unbricking but it can be used for flashing back to a different version because the mf3 version is not rootable at the moment??
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
Firmwares-I337UCUAMDB_I337ATTAMDB_ATT
[AT&T Samsung Galaxy S 4 Android Development] phillytothemax:
that didnt help even in the slightest. i want to know if this will take my mf3 s4 to other version.

the thread is about unbricking i want to know if i can use it for something else
[AT&T Samsung Galaxy S 4 Android Development] blacknet101:
After I restore my S4 to stock, how can I make it so that unlocked icon doesnt show when you boot up the phone?
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
It's Been said all over the site about MF3 if you already upgraded it to MF3 you cannot downgrade so does this answer your question my Friend!
[AT&T Samsung Galaxy S 4 Android Development] joeybear23:
If someone is to lazy to search it is perfectly acceptable to be too lazy to respond to them.
[AT&T Samsung Galaxy S 4 Android Development] phillytothemax:
well thank you my good sir
[AT&T Samsung Galaxy S 4 Android Development] phillytothemax:
so searching for something guarantees you finding it?? are you stupid or what?
[AT&T Samsung Galaxy S 4 Android Development] Bradl79:
where can i find an MDL version
[AT&T Samsung Galaxy S 4 Android Development] fourdigit:
Please try to stay on topic. All you are doing is cluttering the thread.
[AT&T Samsung Galaxy S 4 Android Development] joeybear23:
So you're incapable of figuring out the search feature yet you're questioning my intelligence...

When you brick your phone because you are too impatient to research what you're doing to your $600 device, please just give up and get an iPhone.
[AT&T Samsung Galaxy S 4 Android Development] Gurny:
Followed Indie_Dev lead...

Thanks Indie_Dev, I basically followed your outline here - down to the Candy Crush while I waited at the AT&T DSC. I had your exact same situation with my s4. The rep tried a few things but couldn't get past the yellow triangle screen. I played dumb and was like "I was trying to use that Kies thing to update." Then he said "I'll just swap this out for a new device." It was hard not to laugh as the rep was trying to Google how to fix it.

Now I'm off to root the new one.

Much obliged!
[AT&T Samsung Galaxy S 4 Android Development] kman79:
Quick question.

For those that are on the MF3 firmware and are rooted, if/when a new firmware becomes available for the ATT GS4, those that are on a rooted device wouldn't be able to update to the new firmware correct? If my memory is correct, having a rooted phone causes an update to fail?
[AT&T Samsung Galaxy S 4 Android Development] joeybear23:
I was rooted before updating to MF3 and retained root with Voodoo Root Keeper. Unless Samsung changes their update method it should still work the same.
[AT&T Samsung Galaxy S 4 Android Development] dvsdlite:
I have read we can unroot. We are still stock on mf3, no custom roms. So aslong as you didn't delete anything you should be fine and also able to update.
[AT&T Samsung Galaxy S 4 Android Development] neincraft:
Can anyone post a mirror?
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
You can also get it at sammobile.com
[AT&T Samsung Galaxy S 4 Android Development] bigblue95z:
Was hoping this would take me back to 100% factory state. Unfortunately just took me back to the stock firmware, with all user files, wallpaper, etc. Is there something that I can do to make it back to 100% factory state. Does checking 'Nand Erase All' wipe everything first?

Edit: Want to be sure everything that was in '/' directory would be wiped and then put on the factory firmware.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
reboot to factory recovery and do a factory reset there.
[AT&T Samsung Galaxy S 4 Android Development] bigblue95z:
Thought that just wipes /data and /cache? Granted that'll get rid of user data, but does that take out the extra init.d stuff and garbage that was in the / directory? Been flashing a bunch of ROMs and thinking of selling.
[AT&T Samsung Galaxy S 4 Android Development] spacecowboy618:
This really saved my phone many thanks
[AT&T Samsung Galaxy S 4 Android Development] lowspeed:
I thought that my phone had a charging issue (Turns out 2 days kept untouched revived it)

But in the meanwhile I installed the AMDB firmware from this thread.

What's the procedure to getting root plus custom recovery? Does the LOKI method still works on this firmware?

Thanks!
[AT&T Samsung Galaxy S 4 Android Development] jvanbrecht:
Has anyone tried jtagging and reverting back to the previous firmware?
[AT&T Samsung Galaxy S 4 Android Development] rpcortazar:
Lost space

Hello everyone.

at some point install a ROM to test, the problem I espacion decreased the storage on the device.

I try going back to the stock ROM via Oldin, did not work.

Anyone know any way to get back to the stock ROM and recover the lost space?

Greetings and thanks.
[AT&T Samsung Galaxy S 4 Android Development] gage0727:
was wondering??

Adam, or any of you smart people in here. My s4 took the up date and right now i am not rooted. I have been waiting for a recovery to be created. I was wondering though if their was a way to make my own recovery type to be used with odin and a pit file. I was reading how this guy used it to recover from a brick situation. I really want to be rooted to do away with at&t software and such, not really worried about custom rom's all that much would be nice but not all that big of a deal.

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

their is the thread dealing with using a pit file. Any help or pointers would be great.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
The update your phone took I'm assuming is mf3. There is a root method for it and you can put safestrap on which includes a recovery. Search for it.
[AT&T Samsung Galaxy S 4 Android Development] gage0727:
sorry i seen that saftstrap, just not read up on that part yet. was planning on it. kinda been away for a while waiting for the bootstrap to get unlocked.
[AT&T Samsung Galaxy S 4 Android Development] chnoor:
A quick question , my SGH-I337m is currently running TWRP and Google Edition ROM. If I download ROM from Sam Mobile and flash it with ODIN, will it bring my phone back to original state? Will this also flash radio automatically as currently my radio is also modified to enable AWS BANDS. thanks.
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
Yes it will including the radio
[AT&T Samsung Galaxy S 4 Android Development] rav4kar:
But this is for SGH-I337.
[AT&T Samsung Galaxy S 4 Android Development] waynebike:
Just thought i'd mention that you can use this to successfully recovery from a botched encryption.

Backstory:

I was forced to encrypt my device for work and in the process of doing so, encryption failed, I was basically stuck in a loop, it wouldn't accept my encryption password and entering it like 10 times would tell you that it was going to wipe the device (which was expected), however it would wipe the device and then return to "please enter your encryption password" which it still wouldn't accept. It would do this regardless of which TW rom i tried to load and regardless of how many times i factory reset via TWRP. I found no way around this other than using this method to revert to stock.

Upon doing this and booting up for the first time, i was STILL prompted to enter my encryption password, however entering it and letting it fail it rebooted and wiped the device, FINALLY fully removing the encryption password and i can now load TWRP back on and use any TW rom i want. Encrypting is a huge PITA, will never do that again lol.
[AT&T Samsung Galaxy S 4 Android Development] ravi_mytouch:
Downgrade to Older versions from UCUEMJ6

Can I use this to go back to STock Firmware on my Brand New Galaxy S4. (i337). I am on build JSS15J.I337UCUEMJ6 and I CANNOT ROOT IT or cannot SIM unlock it through any of the methods.

PLease help
[AT&T Samsung Galaxy S 4 Android Development] jd1639:
No, you can't go backwards on firmware. You can only flash mj6 or newer.
[AT&T Samsung Galaxy S 4 Android Development] jherring002:
A big booboo... DO NOT DO THIS

So - to make a long story short i rooted my SGH-I337 (MF3) to get rid of bloatware.. I wasnt trying to flash any roms (though I would like to) because I read of all the headaches with MF3.

Long story short, i screwed something up. My phone would boot... but it would only be responsive for 3-5 minutes and was very VERY laggy.

I got home, did some googleing and found a thread that said to fix this, use Samsung Kies and restore it. Sounded great! Started to restore - i got to 75% and failed. Tried the emergency restore.... Failed. Tried it again.... Failed. Started all over... 75% and failed. As I looked at the file it was trying to install, I noticed it was MDL (i think... md something anyways) Well crap. I drove 60 miles, one way, to best buy so that they could flash it back to factory. They plugged my phone in and.... incompatible device. At that point we called Samsung and they tried a few things. Nothing would work. So they sent me a Label to send them the phone. It is there now, and hopefully they don't say that I voided my warranty because of rooting it. I really enjoy that phone, but I must say I will never buy a phone from a carrier again... Reguardless if my warranty is voided or not, I will still use that phone for a while. Maybe eventually, someone will find a way to unlock MF3. Once that happens, I'm all over it.

TL;DR

DO NOT try to restore to MDL if you are MF3.

I know I have seen this around the forums, and am sorry I didn't catch that kies was installing that sooner.
[AT&T Samsung Galaxy S 4 Android Development] imgladuhateme555:
Will this also get rid of the "Custom" thing with the lock at startup? I'm selling my S4 and am trying to get it back to as stock as possible. Thanks!

Edit: After finishing the flash, it has removed the lock and "Custom" boot.
[AT&T Samsung Galaxy S 4 Android Development] gravedigger76:
Well yes... In all the reading you did you missed the fact that you can't Odin or keys back once you on mf3.…

In either case someone did a huge thing for the community and got everyone files to restore from similar bricks like yours

Check out the thread here

http://xdaforums.com/showthread.php?p=46888516

Sent from my Nexus 7