[FIRMWARE] Stock SM-G930A PB5 Odin files - AT&T Samsung Galaxy S7 Guides, News, & Discussion

Stock SM-G930A PB5 Odin files.
Contains AP, BL, CP and CSC files. Place in corresponding places in Odin
https://drive.google.com/open?id=0B2xxd5WoIhEwaXppU2xjSWlwMm8
Tested using this version of Odin that was posted with S7 Edge restore files: https://www.mediafire.com/?2t2sjqxtogbkafk worked fine. I flashed all but the BL file.

---

Awesome!

---

very nice, ive seen people asking for this in multiple threads.

---

can you find the 930U files? may we can do the same the 935A

---

Upped to my Google Drive storage so no worries about disappearing

---

This version does not work, you need a newer
Odin got this error:
<ID: 0/004> Odin engine v (ID: 3.1203) ..
<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> emmc_appsboot.mbn
<ID: 0/004> lksecapp.mbn
<ID: 0/004> xbl.elf
<ID: 0/004> FAIL! (Auth)
<ID: 0/004>
<ID: 0/004> Complete (Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
On the phone appears:
* REV SW CHECK FAIL: (aboot) Fused 2> Binary 1
(1) eMMC write fail: aboot

---

User error. Worked fine for me.
Use the Odin I posted, flash everything but BL

---

Carlos Terán said:
This version does not work, you need a newer
Odin got this error:
<ID: 0/004> Odin engine v (ID: 3.1203) ..
<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> emmc_appsboot.mbn
<ID: 0/004> lksecapp.mbn
<ID: 0/004> xbl.elf
<ID: 0/004> FAIL! (Auth)
<ID: 0/004>
<ID: 0/004> Complete (Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
On the phone appears:
* REV SW CHECK FAIL: (aboot) Fused 2> Binary 1
(1) eMMC write fail: aboot
Click to expand...
Click to collapse
It is considered as downgrade and not allowed.
I am not sure the best way to bypass this.
You could either not flashing the BL file (unable to otc when I did this) or find a newer version >=APC

---

lovelybai said:
It is considered as downgrade and not allowed.
I am not sure the best way to bypass this.
You could either not flashing the BL file (unable to otc when I did this) or find a newer version >=APC
Click to expand...
Click to collapse
A newer version no longer found
What can cause if not flashing BL?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk

---

Carlos Terán said:
A newer version no longer found
What can cause if not flashing BL?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I don't quite know. It was totally usable but when I tried to OTA update, it failed so I flashed a newer version.
My experience is about G935A but I think there are G930A newer version roms around.

---

Is PB5 not the current version?

---

It works, but is the same that February update.

---

Well for now it's better than nothing and can recover a rooted or bricked phone I suppose.

---

Thank you for this. The newest FW baseband version for the AT&T G930A is "APF2".
The firmware posted will only work for people who are still on the same version or earlier as the posted FW version. It will not work for anyone with newer firmware regardless of which Odin version is used. Basically, this can not be used to restore to stock if you have the "APF2" firmware already on your phone. With a locked bootloader, firmware can not be down graded. This should still be helpful to those on earlier basebands.
If anyone finds the newest "APF2" firmware, please post a link to it.

---

scott14719 said:
Thank you for this. The newest FW baseband version for the AT&T G930A is "APF2".
The firmware posted will only work for people who are still on the same version or earlier as the posted FW version. It will not work for anyone with newer firmware regardless of which Odin version is used. Basically, this can not be used to restore to stock if you have the "APF2" firmware already on your phone. With a locked bootloader, firmware can not be down graded. This should still be helpful to those on earlier basebands.
If anyone finds the newest "APF2" firmware, please post a link to it.
Click to expand...
Click to collapse
I can flash back to APC even if I am APE(g935A).
From what I heard, unconfimed, I could flash the version whose nineth charactor of the firmware version string is not smaller. For apb, it is 1; for apc and above, it is 2.
Sent from my SM-G935U using XDA-Developers mobile app

---

lovelybai said:
I can flash back to APC even if I am APE(g935A).
From what I heard, unconfimed, I could flash the version whose nineth charactor of the firmware version string is not smaller. For apb, it is 1; for apc and above, it is 2.
Sent from my SM-G935U using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, thank you. This does sound correct. It has to do with the advancing numbers as you stated. Once the phone goes to "1" it can no longer go back to "0" and once it goes to "2" it can no longer go back to "1"...etc. Once the fuse has blown, it can not be restored without switching out the mother board to one with the previous version firmware. So I guess this means if the baseband version still has the same "nineth" number, give it a shot.
Again, thanks for the added info.

---

Ahh I see. This is my first go round with phones updated so much.

---

Its just an e-fuse not a physical fuse
Sent from my SAMSUNG-SM-G930A using XDA-Developers mobile app

---

So if that is right......to restore a phone to the original settings one would need the proper baseband version firmware for a G930A. Now the question is where can it be found?

---

I've been looking everywhere. PB5 is all I can find...