Database Users

SGH-I337 Softbrick? Odin flashing fails.

I own a model SGH-I337 Samsun Galaxy S4. Yesterday it started encountering several errors saying that processes had stopped, mostly android.process.acore and google.process.gapps. So I decided to factory reset, this didn't help. The firmware reset but I still encountered errors. I read somewhere this could mean a corrupt firmware in the phone, so I tried to flash the stock firmware from my computer using Kies. This failed and the phone now has no real firmware. So I tried to flash the firmware using Odin. (I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5)
Log:
<ID:0/004> Added!!
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
The phone displays this:
Start [224, 1440]
SV REV. CHECK FAIL : FUSED : 2, BINARY : 1
It still fails. I'm using the stock usb cable on a good port. I have updated the usb drivers as well. I've tried ending all Kies processes on my computer before flashing. This phone has never been rooted/unlocked. Please help.

You have MF3 firmware and tried flashing MDL. That's only going to make things worse.
Unrooted and not modded, you're still under warranty. Visit an at&t service and repair center or a Samsung Experience store (in some Best Buys) to help get this sorted. Cheers

I went to att today and told them that I got an update and didnt do it but it forced it and got stuck on the black sceeen wit samsung logo. They reflashed the mf3 os and that was it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

xBeerdroiDx said:
You have MF3 firmware and tried flashing MDL. That's only going to make things worse.
Unrooted and not modded, you're still under warranty. Visit an at&t service and repair center or a Samsung Experience store (in some Best Buys) to help get this sorted. Cheers
Click to expand...
Click to collapse
Yea, last time I had a problem at&t tried to bull**** me saying it had water damage (it didn't and samsung fixed it for free) and wanted me to buy a new phone. Guess it can't hurt to try again though, thanks for the info.

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

It sounds like you have the MF3 firmware. At this point I guess all you can do with that is root it and use safestrap. No odin.

how do it flash 5.o1 lollipop on my s4 atnt i337 ? im on 4.4.2 kitkat

[Q] Stuck on Samsung logo, will not load safestrap, Odin failed on stock rom load.

I've been searching and found many threads but none that said what to do next in this situation.
I was trying out different roms and then it would not load past the sammy logo. This kept me from loading safestrap and fixing it.
I tried using odin to install stock rom.
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After that I tried different cables, usb ports, restarting the pc / phone, wiping cashe, factory reset and reinstalling kies. I made sure kies was not working in the background.
So far this is what I got from reading many different threads. Any Ideas?
I know you guys get stories like this a lot and it does get tiresome, but it would mean a lot to me if you help me out. Thanks.

So is my nand messed up? What does that mean?
Here is a thread that is similar but I don't think it will work for me.
http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867

I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
Have you look at this thread? This help me out a lot
http://forum.xda-developers.com/showthread.php?t=2926642

stric85 said:
I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
http://forum.xda-developers.com/showthread.php?t=2926642
Click to expand...
Click to collapse
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
Odin3v185
Thank you very much for your help.

Trying out the files in the thread you posted. Odin is definitely different and the stock rom probably is too.

Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.

darkmx-6 said:
Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.
Click to expand...
Click to collapse
Glad it worked! I just pointed you to the thread I used to Odin to stock on my s4, you did the rest.[emoji1] Thanks for letting me know I could be of little help!

Phones stuck in boot loop, probably corrupted ROM

I have an AT&T note 4 and the other day it just started boot looping. I asked a more knowledgeable person and he said that my rom was probably corrupt and directed me to xda for help. What I've done so far:
I downloaded the drivers,
I downloaded odin,
I downloaded the stock AT&T 4.4.4 ROM,
I connect my phone in download mode to odin,
I find the ROM,
I hit start and then it fails..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've gone online and some people said that the reactivation lock was on, but i don't know if there is a way to turn it off without my phone being able to boot up.
I've also cleared the cache partition and factory reset it many times.
Is there any advice or tips, or something I'm just missing? I've never done anything like this with phones before.
Thank you.

If you have (been) kept up to date with the firmware, you should be on 5.1.1.
That's the version you need, as 4.4.4 is not compatible with newer bootloaders.

JagDave said:
If you have (been) kept up to date with the firmware, you should be on 5.1.1.
That's the version you need, as 4.4.4 is not compatible with newer bootloaders.
Click to expand...
Click to collapse
Thank you, i'll give that a try next.

It worked and I was able to install 5.1.1, but unfortunately it does not solve the boot looping issue. Is there anything else that can be done to try to save my phone?

That really should have solved the problem. The only other thing I can think of is wipe data factory reset, while cache partition and while dalvik cache.
Other than that, or is possibly a hardware problem. It could even be something like the battery causing the problem.
If you are still in warranty, it may be worth sending to a service centre.

It turns out it was the battery, at least i learned how to root my phone lol. thank you.

Umm, so after inserting a new battery the bootloop case is gone?

Apparently it wasn't really a boot loop, it just looked like one. No one I took it to could tell the difference. Samsung reps, AT&T service people, geek squad etc.

EvaUnit24 said:
Apparently it wasn't really a boot loop, it just looked like one. No one I took it to could tell the difference. Samsung reps, AT&T service people, geek squad etc.
Click to expand...
Click to collapse
So what was it precisely?

Battery was shorting or something like that. New battery and phone works perfectly.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

EvaUnit24 said:
Battery was shorting or something like that. New battery and phone works perfectly.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks. You're giving me hope.

did you have luck? i changed the battery and still rebooting.

Wow, I really screwed up. Really need some help

I think I need some help from someone. I have a Galaxy S7 Edge (tmo) with the rom of a G935U from last year i believe It was originally a G935T from the store. I flashed a G935U Rom and it was all fine and dandy. Now, I want to go back to stock, so i downloaded TMB_G935TUVU3APG1 firmware and used Odin 3.12 Prince Comsy version and loaded up the AP, BL, CSC, CP. (I have the Samsung USB Drivers installed)
I then clicked on "start" and then got this error: constantly bootloop the "recovery booting"
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use a different firmware version and now my phone says "An error has occured while updating device software. Use the emergency recovery function in Smart Switch PC Software"
I installed Smart Switch, loaded it up, plugged in my phone, and Its saying "Unsupported Device"
I tried going into Emergency Software Recovery but I don't think it works (or im not doing it right). I click on "device initialization" tab and enter my phone model "SM-G935T" without quotes and it keeps telling me "please check the model name and enter it"
I am so stuck. I really hope someone can help me out. I have never had any issues before this.
EDIT: Still stuck, but got into Smart Switch and it was able to download a new rom, but when it tried to apply the rom to my phone, it came back with an error " Failed to update software due to an error. Do you want to run emergency Software Recovery?" and when i click "Emergency Recovery" nothing happens.
EDIT 2 : Retried with latest firmware. Error details below.
<ID:0/003> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Well, first off you're flashing old firmware. Download the latest firmware (Which for the 935U is QD2: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/), not just any random firmware you find.
Get back into DL mode and flash again using the modded Odin. Hold power, home and volume down. Eventually it'll restart in Download mode.
For best reults, Flash the QD2 files in Odin but for CP use the QE1 modem. (I made a thread with a link to DL from my Google Drive. Yes, you'll need to DL 2 firmwares. One U and One T firmware but all you want is the CP file from the QE1. Yes, it'll flash fine and it will give you much better signal. Latest U firmwares have had **** signal.)

joe3681 said:
Well, first off you're flashing old firmware. Download the latest firmware (Which for the 935U is QD2: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/), not just any random firmware you find.
Get back into DL mode and flash again using the modded Odin. Hold power, home and volume down. Eventually it'll restart in Download mode.
For best reults, Flash the QD2 files in Odin but for CP use the QE1 modem. (I made a thread with a link to DL from my Google Drive. Yes, you'll need to DL 2 firmwares. One U and One T firmware but all you want is the CP file from the QE1. Yes, it'll flash fine and it will give you much better signal. Latest U firmwares have had **** signal.)
Click to expand...
Click to collapse
So what is the newest firmware for the 935T? Because after using Smart Switch and having it attempt to fix my phone, it now reads as a 935T in Download mode. Do i still want both firmwares if I am going back to stock?
EDIT: After doing some quick searching, 930TUVS4BQC1 looks like the latest 935T firmware. So I would flash all but the CP from the 930TUVS4BQC1 and then flash the CP from the QE1 firmware? Not sure if it makes a difference, but I was NOT on Nougat when this issue occured.

Forkinator said:
So what is the newest firmware for the 935T? Because after using Smart Switch and having it attempt to fix my phone, it now reads as a 935T in Download mode. Do i still want both firmwares if I am going back to stock?
Click to expand...
Click to collapse
Doesn't matter, you can still flash U fw. If you want completely stock TMobile, find my thread of QE1. It's the latest, bone stock TMobile firmware.

joe3681 said:
Doesn't matter, you can still flash U fw. If you want completely stock TMobile, find my thread of QE1. It's the latest, bone stock TMobile firmware.
Click to expand...
Click to collapse
Alright I have a decent internet connection so i did as you said, Used the modem (CP) from QE1 and the BD, CSC, AP from QD2. At least this error was different. I don't normally have these issues so I am so lost and worried right now.
<ID:0/003> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

1. Try a better/different cable or port
2. Remove the .md5 off the end of each file name and try again

joe3681 said:
1. Try a better/different cable or port
2. Remove the .md5 off the end of each file name and try again
Click to expand...
Click to collapse
WTF!
Dude seriously wtf. It worked! I changed ports, and used a different cable.
I am in awe right now. I don't know what to say besides THANK YOU, YOU GLORIOUS BASTARD!
On a serious note, I don't know why that would have worked. I have always used the port/cable to flash roms. Thanks man, I went to T-mobile earlier and they said i would have to wait till tuesday for a new phone. Going to call them and tell them my phone fixed itself
You really saved me man. I wish there were more people like you. Definitely gonna donate to you.

Forkinator said:
WTF!
Dude seriously wtf. It worked! I changed ports, and used a different cable.
I am in awe right now. I don't know what to say besides THANK YOU, YOU GLORIOUS BASTARD!
On a serious note, I don't know why that would have worked. I have always used the port/cable to flash roms. Thanks man, I went to T-mobile earlier and they said i would have to wait till tuesday for a new phone. Going to call them and tell them my phone fixed itself
You really saved me man. I wish there were more people like you. Definitely gonna donate to you.
Click to expand...
Click to collapse
Thank you!!! I definitely appreciate it! Glad I could get you goin again!

joe3681 said:
Thank you!!! I definitely appreciate it! Glad I could get you goin again!
Click to expand...
Click to collapse
Seriously dude. When you go to bed tonight, remember, you helped a dumbass get his phone working(I know you have helped a lot of people)! Should give you warm fuzzies.
Hope that donation went through. Have a good one!

I'm just reading your message and can say I have a s7 cord and it won't even charge my phone anymore so yes
"WACK CORDS MATTER" when it comes to flashing.

g1-and-only said:
I'm just reading your message and can say I have a s7 cord and it won't even charge my phone anymore so yes
"WACK CORDS MATTER" when it comes to flashing.
Click to expand...
Click to collapse
This is so strange though. It must have happened between the last time I changed firmware and now. I always keep my cords in excellent condition and use the ones that came with the phone if possible.

Troubleshoot very weird boot problem

Sorry for the long post.
Got this sprint S7 as a 2nd hand unlocked phone a while back and worked quite nicely for almost a year. Now very often when I reboot it gets stuck on the LTE boot logo. While it is at it, it will burn through the battery in like 30m-1h, the phone gets very hot. This has already happened a handful of times so I try to never reboot unless very necessary. This doesn't happen on every single reboot though.
Right now it's showing the same issue. Before I've notice it'll do this for a few days and the like magic will start working again. It sucks because right now my phone is as good as dead.
The phone is not rooted and it's running stock ROM, with latest firmware and all updates(I checked for updates a couple days ago and there was none), but I don't know which exact version is at.
I've already tried rebooting into recovery and powering off and restarting from there. But no luck.
I had a strong suspicion this was due to switching sim cards (I moved a few months ago) and sometimes a "UICC unlock needed" (or sth like that) message has been shown but the phone continues to work. Today a friend mentioned it could be the battery. He said if the battery is damaged it could be causing problems on boot but I have no clue if that's true and/or how to check for it.
I'd thank anyone who could tell me how to troubleshoot this problem and find the real cause. I'm comfortable following some technical instruction to be able to grab logs from linux command line if someone taught me how.
Thanks in advance!

joel_gil said:
Sorry for the long post.
Got this sprint S7 as a 2nd hand unlocked phone a while back and worked quite nicely for almost a year. Now very often when I reboot it gets stuck on the LTE boot logo. While it is at it, it will burn through the battery in like 30m-1h, the phone gets very hot. This has already happened a handful of times so I try to never reboot unless very necessary. This doesn't happen on every single reboot though.
Right now it's showing the same issue. Before I've notice it'll do this for a few days and the like magic will start working again. It sucks because right now my phone is as good as dead.
The phone is not rooted and it's running stock ROM, with latest firmware and all updates(I checked for updates a couple days ago and there was none), but I don't know which exact version is at.
I've already tried rebooting into recovery and powering off and restarting from there. But no luck.
I had a strong suspicion this was due to switching sim cards (I moved a few months ago) and sometimes a "UICC unlock needed" (or sth like that) message has been shown but the phone continues to work. Today a friend mentioned it could be the battery. He said if the battery is damaged it could be causing problems on boot but I have no clue if that's true and/or how to check for it.
I'd thank anyone who could tell me how to troubleshoot this problem and find the real cause. I'm comfortable following some technical instruction to be able to grab logs from linux command line if someone taught me how.
Thanks in advance!
Click to expand...
Click to collapse
Have you tried reflashing the stock firmware via odin? If you could tell me which network you're using it on, I could point you to the firmware you would need. Here's a basic overview for the phones and their corresponding firmwares:
SM-G93OP- Sprint
SM-G930T- T-Mobile
SM-G930A- AT&T
SM-G930V- Verizon
SM-G930U- Universal, but you need the correct version of it for your carrier.

TheF|ipSide said:
Have you tried reflashing the stock firmware via odin? If you could tell me which network you're using it on, I could point you to the firmware you would need. Here's a basic overview for the phones and their corresponding firmwares:
SM-G93OP- Sprint
SM-G930T- T-Mobile
SM-G930A- AT&T
SM-G930V- Verizon
SM-G930U- Universal, but you need the correct version of it for your carrier.
Click to expand...
Click to collapse
Hi TheFlipSide,
I have a sprint version so I have SM-G93OP- Sprint
It is possible something might have gone wrong at some point in time but I have done factory resets before, I'm skeptical that the firmware itself could be the issue but I'm happy to give it a try.
Could you point me to the files needed to be sure I'm on the most accurate firemware (CP, BOOT, etc type of files).
Also, any issues with my phone being up to date with all the updates?
Personally I'd be happier to be able to flash sth like LineageOS but AFAIU there's not much support for this phone.

joel_gil said:
Hi TheFlipSide,
I have a sprint version so I have SM-G93OP- Sprint
It is possible something might have gone wrong at some point in time but I have done factory resets before, I'm skeptical that the firmware itself could be the issue but I'm happy to give it a try.
Could you point me to the files needed to be sure I'm on the most accurate firemware (CP, BOOT, etc type of files).
Also, any issues with my phone being up to date with all the updates?
Personally I'd be happier to be able to flash sth like LineageOS but AFAIU there's not much support for this phone.
Click to expand...
Click to collapse
You can't flash LineageOS on this phone because the bootloader is locked. You can get ODIN to flash the firmware with from here:
https://drive.google.com/file/d/0ByoIewGd_qk2MEZMb0l3Qlo4ek0/view?usp=drivesdk
Unzip it and click on the ODIN3 v3.12.7 file, you don't need to install anything it opens as an app.
Grab the firmware from here: http://updato.com/firmware-archive-select-model?record=48A2011F925C11E7963AFA163EE8F90B
Unzip it and select the files through odin:
CP in CP.
CSC in CSC.
AP in AP.
BL in BL.
Then go into options and select auto reboot and repartition, and keep everything else unchecked.
Hit start and wait for the firmware to flash.
Go into stock recovery, and wipe cache and factory reset.
Hit thanks on the posts if I helped you.

TheFlipSide thanks so much for helping me out.
Quick questions. The firmware link you sent is for SM-G930U. But AFAIK my phone is SM-G930P (Sprint model), since it even shows the Sprint animation on boot. Let me know if that was a small mistake or if theres a good reason to flash the Universal version on a sprint phone.
Also, assuming it was a small mistake I'm looking at that firmware page. Looks like the latest version for the SM-G930P comes in 3 flavors: VMU, XAS and SPR.
Do you know what those are and which one should i get?
Thanks again in advance!

joel_gil said:
TheFlipSide thanks so much for helping me out.
Quick questions. The firmware link you sent is for SM-G930U. But AFAIK my phone is SM-G930P (Sprint model), since it even shows the Sprint animation on boot. Let me know if that was a small mistake or if theres a good reason to flash the Universal version on a sprint phone.
Also, assuming it was a small mistake I'm looking at that firmware page. Looks like the latest version for the SM-G930P comes in 3 flavors: VMU, XAS and SPR.
Do you know what those are and which one should i get?
Thanks again in advance!
Click to expand...
Click to collapse
Use the SPR variant of the SM G930U firmware, as it comes without the Sprint bloat. If you still want to use the SM-G930P firmware, get it here: http://updato.com/firmware-archive-select-model?record=080CDA3799FF11E7963AFA163EE8F90B
As I said previously, you don't need to thank someone in a response post, just click the thanks button on a post which helped you.

bootlooped
TheF|ipSide said:
Use the SPR variant of the SM G930U firmware, as it comes without the Sprint bloat. If you still want to use the SM-G930P firmware, get it here: http://updato.com/firmware-archive-select-model?record=080CDA3799FF11E7963AFA163EE8F90B
As I said previously, you don't need to thank someone in a response post, just click the thanks button on a post which helped you.
Click to expand...
Click to collapse
Hi, sorry for the delay, life got in the way. So I downloaded the universal version SM-G930U (SPR) and followed the instructions and Odin failed.
Code:
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
I tried to run it again after unplugging the cable and plugging it back in and it failed again:
Code:
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> FAIL! (Auth)
Now I tried to restart and it's gotten itself on a boot loop =(
It's stuck in the blue "installing system update" page only for a second, then some white text on black screen shows up, and then it goes back to the blue page, and repeats. Basically is trying to boot into recovery forever.
Trying to reboot manually to get into download mode, or anything else also doesn't work.
Halp!

joel_gil said:
Hi, sorry for the delay, life got in the way. So I downloaded the universal version SM-G930U (SPR) and followed the instructions and Odin failed.
Code:
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
I tried to run it again after unplugging the cable and plugging it back in and it failed again:
Code:
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> FAIL! (Auth)
Now I tried to restart and it's gotten itself on a boot loop =(
It's stuck in the blue "installing system update" page only for a second, then some white text on black screen shows up, and then it goes back to the blue page, and repeats. Basically is trying to boot into recovery forever.
Trying to reboot manually to get into download mode, or anything else also doesn't work.
Halp!
Click to expand...
Click to collapse
You can't flash the U firmware if you are on the latest sprint firmware. Download the latest firmware from here
And follow the same directions for placing files into ODIN. You are getting the PIT error because of bootloader updates.

lvpre said:
You can't flash the U firmware if you are on the latest sprint firmware. Download the latest firmware from here
And follow the same directions for placing files into ODIN. You are getting the PIT error because of bootloader updates.
Click to expand...
Click to collapse
Hi Ivpre, thanks a lot for jumping in. So I managed to get my phone in download mode again. Also I google one more error that was showing up in the phone screen "Fuse 5 > aboot 4" (or sth like that, I can't remember exactly) and the internetz said that it was indeed due to having a version missmatch, the new one should be higher.
So I downloaded the latest G930P from sammobile site (G930PVPU5BQJ3) and got it to work again. I also found another thread to said the only thing to do is wait until a new G930U comes out.
What I don't fully get is that now that I've installed "latest" firmware. As soon as I configured the phone it said a new update is available. If I update it now, and a new version of G930U also comes out in a bit, will that mean I'll remain one version ahead? Should I not apply any updates until a new version of G930U is out? or should I try downgrading the current G930P ?
Thanks!

joel_gil said:
Hi Ivpre, thanks a lot for jumping in. So I managed to get my phone in download mode again. Also I google one more error that was showing up in the phone screen "Fuse 5 > aboot 4" (or sth like that, I can't remember exactly) and the internetz said that it was indeed due to having a version missmatch, the new one should be higher.
So I downloaded the latest G930P from sammobile site (G930PVPU5BQJ3) and got it to work again. I also found another thread to said the only thing to do is wait until a new G930U comes out.
What I don't fully get is that now that I've installed "latest" firmware. As soon as I configured the phone it said a new update is available. If I update it now, and a new version of G930U also comes out in a bit, will that mean I'll remain one version ahead? Should I not apply any updates until a new version of G930U is out? or should I try downgrading the current G930P ?
Thanks!
Click to expand...
Click to collapse
Yeah, apparently they just released a small update (QK3 maybe?) that patched an exploit. That update was just released the other day. You can take it or leave it, it shouldn't prevent you from installing the U firmware when it is updated.
If you really want to install the U firmware and can't wait, you can research PIT files, but it can lead to fully breaking the device if you mess up...personally, I would just wait. It was an old method that would work, but I'm not sure if it works on the new bootloader updates.

Hi Guys,
I'm on the same boat as joel_gil,
I've got S7 (originally purchased on sprint USA network) and now I've unlocked it using idoneapps without root.
I'm on G930PVPU5BQJ3 firmware at the moment and I'd like to flash G930U firmware which is network unlocked and not bloatware free.
I've downloaded the firmware below multiple times from sammobile.com and tried flashing using latest Odin 3.12.10 and everytime I am getting error message.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/SPR/download/G930UUES4BQL1/201542/
I have also tried XAS version as well but same result
SW check failed aboot fused 5 > binary 4 message.
I've got FRP and OEM unchecked and still its giving me same error.
I'd appreciate if you guys can have a look and help me please.
Many thanks in advance guys

tom_hungston said:
Hi Guys,
I'm on the same boat as joel_gil,
I've got S7 (originally purchased on sprint USA network) and now I've unlocked it using idoneapps without root.
I'm on G930PVPU5BQJ3 firmware at the moment and I'd like to flash G930U firmware which is network unlocked and not bloatware free.
I've downloaded the firmware below multiple times from sammobile.com and tried flashing using latest Odin 3.12.10 and everytime I am getting error message.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/SPR/download/G930UUES4BQL1/201542/
I have also tried XAS version as well but same result
SW check failed aboot fused 5 > binary 4 message.
I've got FRP and OEM unchecked and still its giving me same error.
I'd appreciate if you guys can have a look and help me please.
Many thanks in advance guys
Click to expand...
Click to collapse
You can't install the U firmware...the bootloader binary files are different. You will have to wait for the U firmware to catch up in order to install it. However, you can install the latest Sprint firmware without any issue.

I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5, and how to tell the files apart can be found here
https://www.arencambre.com/blog/2018...omment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.