[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3

[nkhater]

The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?

It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.

I could not boot before flashing this PIT file,

and if this theory is correct, I would have a clean "fresh" image after a booted the phone, in fact, when the phone successfully booted after flashing the PIT file, all my applications including root were all there, so it was not like a hard reset startup

 

[nkhater]

As much as I would like to see it work, I don't think it would be a good idea.

A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?

B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?

Something either is very right with this (a breakthrough) or is very wrong with this.

I was on MF3 when I rooted the phone and then installed TWRP using GooManager, and when I ran an update on supersu, supersu asked me if I have a custom recovery, I said yes, then the phone booted automatically to Download MOD with a custom boot logo, and not the Samsung default logo, I saw that custom logo only once, then it disappeared

 

[nkhater]

I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.

I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.

I was stuck on a Download Mod for almost half a day trying to get the phone recover, I can say one thing, ODIN and the attached PIT file did something to recover "soft unbrick" the phone, as the state of the phone differently changed

 

[mikecantreed]

I was on MF3 when I rooted the phone and then installed TWRP using GooManager, and when I ran an update on supersu, supersu asked me if I have a custom recovery, I said yes, then the phone booted automatically to Download MOD with a custom boot logo, and not the Samsung default logo, I saw that custom logo only once, then it disappeared

So now you have root on MF3 but no more custom recovery?

 

[nkhater]

And here is another example of someone getting out of a bootloop through Download (ODIN) mode:

http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11

Possibly, Odin triggered a similar reaction.

Actually, the original thread i pulled that post out of sounds very similar to what happened to the OP in this post.

Take a look at the OP of this post to see what I mean:

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

So, I think my theory is correct. The PIT file never actually flashed, it was the interaction between ODIN and D/L mode that overcame the bootloop.

But hey, feel free to keep messing around with the PIT file because you never know...

I tried flashing stock MF3 using ODIN, but no luck, always got this:

<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!


I even tried KIES firmware recovery, but it always failed

The PIT file saved me

 

[nkhater]

So now you have root on MF3 but no more custom recovery?

Yes I have root, and I did not have to root again,

Yes custom recovery "boot logo" is gone

 

[Little Bigboy]

i tried this before noon and it disnt wil work ?

 

[bprinehart]

Thanks for this fix. You just saved my buddy a whole lotta fustration and the fear of having to explain to his wife why he needs to buy a new phone!

 

[jd1639]

Thanks for this fix. You just saved my buddy a whole lotta fustration and the fear of having to explain to his wife why he needs to buy a new phone!

Did your buddy try to flash a custom recovery while he was on mf3? Is that what got him soft bricked.

 

[bprinehart]

Did your buddy try to flash a custom recovery while he was on mf3? Is that what got him soft bricked.

That's precisely what happened. We tried everything we could think of, and then finally I came across this post. He still has root, and all his data, apps, settings etc are still maintained. I tend to agree with those who think it is acting much like clearing the cache in recovery in that it's not doing anything per se to the phone, just clearing the boot loop.

 

[nkhater]

Thanks for this fix. You just saved my buddy a whole lotta fustration and the fear of having to explain to his wife why he needs to buy a new phone!

I am glad I was able to share this knowledge, believe me, I know exactly what you mean

 

[scott14719]

Sorry if this off topic but what's stopping someone from wiping the bootloader partition and flashing the MDL firmware?

I'm not sure if this would be done via a PIT file, ADB script or some other method but in general isn't this the path of last resistance for achieving root/bootloader access?

There is a lot of information throughout the AT&T S4 forum about this already, but a short version response is, to this date, it cannot be done. The reason(s) why are way to lengthy to post here, but I encourage you to research it.

That's precisely what happened. We tried everything we could think of, and then finally I came across this post. He still has root, and all his data, apps, settings etc are still maintained. I tend to agree with those who think it is acting much like clearing the cache in recovery in that it's not doing anything per se to the phone, just clearing the boot loop.

I agree 100%. Like I said, others have tries to flash extracted PIT files via ODIN on this phone before and although it reports as flashing successful, it in fact does not.

It is important to understand that if the PIT file had flashed successfully, you would be left with an unusable phone. It would be partitioned correctly, but there wouldn't be data left on it. It would take a firmware TAR (in this case MF3) to be flashed through ODIN directly after a successful PIT flash in order for a Kernel or ROM to be on the phone.

Again, I realize how it appears, but I think it's just a matter of handling D/L mode in such a way that it finally boots the phone correctly. It has been done without this PIT file as well (see the thread I linked in my last post).

Here's the thing. if this is still helping people (maybe just not in the way it appears to be), It's still a good thing. Maybe it's taking a little of the guess work out of trying to manually manipulate D/L (ODIN) mode to boot the phone and using ODIN to help boot it up a little quicker.

Hopefully some of the Devs can take a closer look at this, but I still think the PIT file isn't actually flashing through ODIN.

---------- Post added at 03:29 PM ---------- Previous post was at 03:18 PM ----------

I am glad I was able to share this knowledge, believe me, I know exactly what you mean

I have another question. Sorry about this, but I think it is important that we figure out what exactly is going on here.

When you used ODIN to flash the PIT file, did you check "repartiotion" in ODIN?

 

[jd1639]

Good question

 

[Little Bigboy]

this doesnt work, i tried it

 

[jd1639]

this doesnt work, i tried it

Can you only get in download mode? Did you try to flash a custom recovery on mf3 and that's what caused your problem? Just trying to figure out why sometimes this works and others not. Thanks

 

[mg2195]

There is a lot of information throughout the AT&T S4 forum about this already, but a short version response is, to this date, it cannot be done. The reason(s) why are way to lengthy to post here, but I encourage you to research it.



I agree 100%. Like I said, others have tries to flash extracted PIT files via ODIN on this phone before and although it reports as flashing successful, it in fact does not.

It is important to understand that if the PIT file had flashed successfully, you would be left with an unusable phone. It would be partitioned correctly, but there wouldn't be data left on it. It would take a firmware TAR (in this case MF3) to be flashed through ODIN directly after a successful PIT flash in order for a Kernel or ROM to be on the phone.

Again, I realize how it appears, but I think it's just a matter of handling D/L mode in such a way that it finally boots the phone correctly. It has been done without this PIT file as well (see the thread I linked in my last post).

Here's the thing. if this is still helping people (maybe just not in the way it appears to be), It's still a good thing. Maybe it's taking a little of the guess work out of trying to manually manipulate D/L (ODIN) mode to boot the phone and using ODIN to help boot it up a little quicker.

Hopefully some of the Devs can take a closer look at this, but I still think the PIT file isn't actually flashing through ODIN.

---------- Post added at 03:29 PM ---------- Previous post was at 03:18 PM ----------



I have another question. Sorry about this, but I think it is important that we figure out what exactly is going on here.

When you used ODIN to flash the PIT file, did you check "repartiotion" in ODIN?

When I had "successfully" flashed my pit file (I use the quotes because I really dont know if my pit went through)

Anyways, when I flashed my self extracted pit along with mdl I ticked the repartition...and when the device booted up my internal storage had been completly wiped...no data on it...pictures gone and roms gone and other files that were on internal...idk if that means the pit was successful or not...as I really dont know much about pits and odin. Tomorrow morning if I have time ill try flashing the pit only and seeing what that does to my device

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

 

[nkhater]

When I had "successfully" flashed my pit file (I use the quotes because I really dont know if my pit went through)

Anyways, when I flashed my self extracted pit along with mdl I ticked the repartition...and when the device booted up my internal storage had been completly wiped...no data on it...pictures gone and roms gone and other files that were on internal...idk if that means the pit was successful or not...as I really dont know much about pits and odin. Tomorrow morning if I have time ill try flashing the pit only and seeing what that does to my device

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

B Careful

If you are on MF3, for some reason Kies and Odin will not work even to flash back MF3 stock,

 

[mg2195]

B Careful

If you are on MF3, for some reason Kies and Odin will not work even to flash back MF3 stock,

Im not...im mdl...just tryingntobhelpnfigure out this whole pit thing

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

 

[scott14719]

Im not...im mdl...just tryingntobhelpnfigure out this whole pit thing

Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

It's possible that your PIT actually successfully flashed because:

A. You had "repartition" checked

and

B. The PIT you used from from your own device.

What you describe sounds like a successful PIT flash. Your device should be "empty" after a PIT flash because, basically, your phone is being reformatted and partitions are being set up. The ROM and Kernel (TAR) flashed through ODIN provides the DATA. Without the DATA, the phone would be useless. That is one reason I think the PIT file in the OP actually did not flash. If it had, there would be nothing on the phone to boot into.

 

[waldoelx7241]

this worked for me after i tried flashing a recovery from Goo. Don't try to flash custom recovery until a developers publishes one, it will give you the biggest headache. Im just happy I got to root and uninstall all the AT&T crap.