Database Info

Soft Brick Help?

I just got a SGS2 Skyrocket and was using odin. It didn't make any progress for 3 hours so I unplugged (I know not to but I didn't know an alternative either). Anyway, I am now getting the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Error message. I read in another thread that I should re-enter Odin to try to fix it, but I can no longer get into download mode. What's the next step here? I know this topic has been discussed, but I really want to make sure I do this right.

When you see that "error" screen you should be in download mode. If not do this. Pull battery and reinsert. Hold the up /down volume and plug in USB. Should kick you into download mode.
Sent from my SAMSUNG-SGH-I727 using xda premium

iLiberate said:
I just got a SGS2 Skyrocket and was using odin. It didn't make any progress for 3 hours so I unplugged (I know not to but I didn't know an alternative either). Anyway, I am now getting the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Error message. I read in another thread that I should re-enter Odin to try to fix it, but I can no longer get into download mode. What's the next step here? I know this topic has been discussed, but I really want to make sure I do this right.
Click to expand...
Click to collapse
I had the same issue.. your in download mode.. try pushing your rom of choice through odin again, but use a different usb port. Your basically still in download mode.
Sent from my SGH-T989 using Tapatalk

capcanuck said:
I had the same issue.. your in download mode.. try pushing your rom of choice through odin again, but use a different usb port. Your basically still in download mode.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Yup, despite the error message you're seeing you should still be able to flash the stock .tar. The phone won't look like it's doing anything--you'll still see the error message--but if Odin sees it you should be fine.
I had this happen to me too and it worked fine.

Well I am at the step where you insert the TAR file for the PDA slot on odin and I can only get this far:
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
I used the i727 TAR instead of the i727R TAR file. That's the only thing I can imagine changing to make this work.
Am I suppose to be choosing a ROM at this point as well? Where do I get a pit file if I need one?

Here is process.
iLiberate said:
Well I am at the step where you insert the TAR file for the PDA slot on odin and I can only get this far:
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
I used the i727 TAR instead of the i727R TAR file. That's the only thing I can imagine changing to make this work.
Am I suppose to be choosing a ROM at this point as well? Where do I get a pit file if I need one?
Click to expand...
Click to collapse

Same Problem
Hey im new at this and i'm having the same problem. my issue is i have the error message and did what you guys said and reattempted Odin. it recognizes the phone and says
<ID:0/004>Complete(Write) operation failed.
and above the yellow box in Odin is a red box that says Fail!
i have tried this a few times and this is the only result i get.
i think i might have done something wrong with the tar file, i downloaded the correct one and i used 7-Zip to convert the rar to tar and odin now recognizes the file but idk if i was supposed to do that. Any help is greatly appreciated!
sorry for being an idiot i figured out what i did wrong

Yes you must unzip the. 7z file the tar is inside. Unzip it with 7zip then run odin and select the unzips tar file in the pda section of odin

Please help cannot flash Stock

So I messed up my s7 by flashing a wrong version of xposed and now I can't go back to stock.
Trying to flash it through Odin but I get a "sw rev check fail" message
Please help :'(

marcotics said:
So I messed up my s7 by flashing a wrong version of xposed and now I can't go back to stock.
Trying to flash it through Odin but I get a "sw rev check fail" message
Please help :'(
Click to expand...
Click to collapse
Are you sure you are flashing correct firmware and the latest version?

Yes, I'm trying to flash G930TUVS2APB8
Should I only do "AP"? Or try all four files?
What do I do in the CSC field? Load the CSC or HOME_CSC file?
Should I try the special Odin by PrinceComsy or 3.11?

This is what I get on Odin
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is what shows up on Odin

Fixed the problem!!! thanks

What was the solution? I'm having this issue as well

Try going into recovery and factory reset(wipe data)

It got fixed by using my pc rather than my laptop (had same drivers installed so no idea)
Also downloaded the absolute latest firmware from sammobile and latest Odin
Hope you can fix your problem man.
Note: if it doesnt let you flash stock I read that it may be because you're trying to flash something older, by default you cannot downgrade on s7

ODIN3 v3.13 Fails SW REV Check Fail (Fused 4 > 3)

Hey everyone,
Not a total NOOB but feel like one today...
I was stock ATT S8+ and accepted the OTA Update on Friday 6/23. After restarting the device, and optimizing apps, phone is stuck on unlocking padlock circle screen. Cleared cache through recovery, but have not done factory reset because I have data I'm trying to retain.
Downloaded Odin3 v3.13 and v3.13B and have tried all the Stock firmware I can find...but Odin keeps failing with similar logs:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> apdp.mbn
<ID:0/007> msadp.mbn
<ID:0/007> persist.img.ext4
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 4636 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone, I get SW REV CHECK FAIL : [abl] 4 > Binary 3
By Googling it looks as though I need BL v4? and I'm not seeing anything past BL v3 (CRD4 CRE2)...
Any thoughts (other than factory reset...that's my last option...well that and replace it through ATT/Samsung)...
What's up with Sammie anyway? Two months ago I lost access to my micro SD that was encrypted after taking an OTA update...not a happy customer..
Thanks and sorry for previously asking in the discussion forum...

That FAIL: 4 > Binary 3 means you need a Firmware with bootloader V4. Once you're on v4, you can't go back to v3. G955USQU4CRE9 is an example of a firmware with BL v4.

hazmad said:
That FAIL: 4 > Binary 3 means you need a Firmware with bootloader V4. Once you're on v4, you can't go back to v3. G955USQU4CRE9 is an example of a firmware with BL v4.
Click to expand...
Click to collapse
Thanks Hazmad! So, how long has it been taking after the OTAs come out for the files to show up? Really trying to avoid a factory reset (at least until I can pull some pictures off my phone!)...

dinglayne said:
Thanks Hazmad! So, how long has it been taking after the OTAs come out for the files to show up? Really trying to avoid a factory reset (at least until I can pull some pictures off my phone!)...
Click to expand...
Click to collapse
Not sure, it's different for each carrier. I hope you have backups, at least an adb backup. Samsung cloud backup does a decent job too. If you have a recent backup, it might be easier to factory resset, and then restore. If you don't have any backup, you risk losing all your data.
You can try odin flashing the BL & AP from T-Mobile's firmware https://androidfilehost.com/?fid=746163614322275144 (Don't mess with the CP or CSC). If you do that without the nand erase option checked, this should keep your user data (app data, pictures, etc) intact. If you'd like, you can try the BL file on it's own first. If that doesn't fix it, then try the AP file. Flashing the AP file (without nand erase) will reset your system settings, but leave your user data. Flashing the BL by itself should leave your system settings alone.
If you can't boot to system after that, you can also try a combo BL v4 firmware. That might be a lot more work than it's worth though.

[Help Needed] Failed Firmware update using Odin. Need help flashing correct firmware.

Hello,
I tried to update my wife's Samsung S7 firmware using Odin and managed to brick/boot loop it.
I need some help getting it working again.
Its an unlocked T-Mobile Samsung S7 (SM-G30T) from Ebay using a Virgin Mobile SIM and it originally had the G930TUVU4APK1 (Android 6.0.1) firmware on it.
It would not update OTA, so I downloaded the G930TUVS8CRJ1 (Android 8.0) from Sammmobile.com.
I opened Odin, selected the BL, AP, CP and CSC files and hit Start. The Odin log said "failed (auth)".
I exited Download Mode and tried to restart the phone, it would try to boot but it gave me the message "security error: this phone has been flashed with unauthorized software and is locked".
I downloaded and tried to flash the older G930TUVU4APK1 (Android 6.0.1) firmware, but it did not work.
I am able to get back into Download Mode and Odin still recognizes the phone. I think its possible to save it?
I should have never tried to do this, I feel terrible and I need some help. How can I fix this? Where can I find firmware that I can flash to fix this?
I would really appreciate your help! Thank you very much!!

I just tried to flash the older Android 6.0.1 firmware again. This time selecting only AP, CP and CSC.
This is what the Odin log says.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4661 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Something I noticed. Before I tried to update it, on the Download Mode screen, it said "Current Binary: Official".
Now it says "Current Binary: Custom". I think I need to get that to say "Official" again.

I would suggest that you download the firmware again and then try flashing it.....
As far as that custom binary thing is concerned.... That's not going to change as far as i know cause that tripped the knox.... And the warranty is lost... If it was there ..... So i hope u recover it again.... Also try getting into the recovery mode and format before flashing the firmware.... That might help.....
Let me know what happens....
All the best

Thanks for the help soyuz4u!
After spending a long night trying various things,
I was finally able to fix it by flashing the G930TUVS8CRJ1 (Android 8.0) firmware again using Odin. Except this time I used the "CSC..." file, instead of the "HOME_CSC..." file.
Originally I was trying to preserve the data on the phone, so thats why I used the Home file. However, after struggling for a while I eventually gave up hope and decided try it again, this time wiping everything out with the CSC file... and to my delight, it worked! Thank goodness! Its working perfectly on an official firmware!

Just as an FYI, USA model S7's can't be downgraded via Odin, so once you're on Oreo your only option to resolve issues would be to flash Oreo.

i doubt there is working stock firmware for android 6.0.X. I have tried several stock firmwares they all fail.

Change CSC

I was wondering if I changed the CSC on a Korean Note 20 Ultra if I would unlock US bands or if the hardware simply does not exist. Or could I just *#BAND# to activate them?

Zmantech said:
I was wondering if I changed the CSC on a Korean Note 20 Ultra if I would unlock US bands or if the hardware simply does not exist. Or could I just *#BAND# to activate them?
Click to expand...
Click to collapse
You can flash a modem.img that has been extracted from a Note 20 Ultra firmware that supports US radio bands.

Droidriven said:
You can flash a modem.img that has been extracted from a Note 20 Ultra firmware that supports US radio bands.
Click to expand...
Click to collapse
How would I extract the modem.img (I have a US version for now) and install it?

Zmantech said:
How would I extract the modem.img (I have a US version for now) and install it?
Click to expand...
Click to collapse
Use 7zip to extract the firmware file on PC, then, extract the files that are inside the firmware. I can't remember where the modem.img file is located inside the firmware, just extract the firmware files, then extract the files that come out of the firmware, then look through the files that come out of those files and you should see a modem.img or a modem.bin file somewhere.

Droidriven said:
Use 7zip to extract the firmware file on PC, then, extract the files that are inside the firmware. I can't remember where the modem.img file is located inside the firmware, just extract the firmware files, then extract the files that come out of the firmware, then look through the files that come out of those files and you should see a modem.img or a modem.bin file somewhere.
Click to expand...
Click to collapse
I found this would this work https://samfirms.com/samsung-note-20-ultra-5g-sm-n986u1-eng-modem-. Then I just flash via odin but which slot do I put the modem file in?
Should I just flash the CP from an unlocked US firmware

Zmantech said:
I found this would this work https://samfirms.com/samsung-note-20-ultra-5g-sm-n986u1-eng-modem-. Then I just flash via odin but which slot do I put the modem file in?
Should I just flash the CP from an unlocked US firmware
Click to expand...
Click to collapse
I suggest only flashing the modem. When you extract the copy of modem.img, convert it to an Odin flashable .tar file using 7zip with the highest level of compression. Then flash the modem.img.tar via Odin, place the modem.img.tar in the AP slot then click start.

Droidriven said:
I suggest only flashing the modem. When you extract the copy of modem.img, convert it to an Odin flashable .tar file using 7zip with the highest level of compression. Then flash the modem.img.tar via Odin, place the modem.img.tar in the AP slot then click start.
Click to expand...
Click to collapse
This is what I get. I turned OEM unlock on
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 97 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Zmantech said:
This is what I get. I turned OEM unlock on
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 97 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version of Odin are you using?
Do you have USB debugging enabled in the device's system settings?

Droidriven said:
What version of Odin are you using?
Do you have USB debugging enabled in the device's system settings?
Click to expand...
Click to collapse
3.14.1 Patched
Yes

Zmantech said:
3.14.1 Patched
Yes
Click to expand...
Click to collapse
Try 3.12 or 3.13
Do you know if the binary version of the modem is equal to or higher than the binary version of your currently installed modem? To check, look at the firmware build number of your currently installed firmware, the 5th character from the right end of the build number is the binary version. Then look at the build number of the firmware that you extracted the modem from, look at the 5th character from the right, if this number is equal to or higher than the number from your current firmware then the error isnt caused by a binary conflict.