Database Info

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

Help with FRP Bypass for SM-J737A (AT&T).

UPDATE: Thanks to a helpful video I was able to get back into the phone. It required for you to have a locked SIM card and just following all the steps in the video
Here is the video if anyone is having similar issues: https://www.youtube.com/watch?v=1p-affHYB8s&t=189s
Very new to this but my brother gave me a Samsung galaxy J7 model sm-j737a. I do not have the google account associated with it, neither does he, and so I tried using odin to flash the stock firmware in it but I keep getting a fail in writing. I am not sure if its the firmware that I am using that is wrong or what (Full Firmware J737AUCU1ARE6_J737AATT1ARE6_8.0.0 BY Windows4Droid). Does anyone have the official stock firmware for the SM-J737A? Is there another way to go about this? Below I listed what it says when I try to install it in Odin3 13.1. Any help for this noob would be greatly appreciated. Thanks!
Once I click Start, I get this:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3964 M
<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> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Is the firmware your trying to flash the correct bootloader? ( the 5th number from the right of the firmware name... E.G. .....2AUSR1 the (2) would be the bootloader version. They usually need to match accordingly or be higher than the one on the phone already.

Anyone know how to bypass same phone on pie?

X axis mirror issue, secret code won't work, can't flash to stock

Hi there XDA give mind, hoping you can help. I have 3 problems with my SM-G920I
1) The X axis on the touch screen is mirrored. Probably from an incorrect firmware flash previously. People say the fix is the *#2663# secrect code, however when I attempt the code I get the message "connection problem or invalid mmi code". The other secret codes work and I can make calls fine so it's connected to the network. People say I need to flash back to an earlier stock rom then it will work, so:
2) I grabbed the earliest stock firmware I could find (SM-G920I_1_20160728095841_9gdnxsh93c) and attempted to flash it in the AP in Odin which fails:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3487 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> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
3) The device thinks it's an SM-G920F, this probably occured during a previous flash (possibly Xtrestolite ROM might have done this?). I'm not sure how much of a problem this is for step 1, would this impact it?
I can flash TWRP no probs and I've got a couple of ROMs that will flash. Currently the device is currently on XtreStoLide Deo Mod v.3.3 - DPDP, baseband G920FXXU5DPL5. Any help appreciated in getting this handset out of mirrored X axis mode and onto any recent OS like LineageOS would be appreciated.

SM-G930V - trying to flash SM-G930A firmware but failing

I've read that multiple people were able to flash their SM-G930V to SM-G930A firmware and be able to get all of the LTE bands of AT&T. However, I am not able to, I am trying to flash G930AUCU4CRE4 and this is what i'm getting:
<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> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
On the phone screen I am getting an error as well after this. I was able to flash G930UUESACSF1 so the phone model now says SM-G930U, I picked AT&T's version from Sammobile, the phone works and i'm getting all LTE bands, however I am still trying to get the SM-G930A firmware so I can do VoLTE. When calling with the G930U firmware, it puts the phone call over HSPA. Any ideas? Am I not doing the right options on odin or something? I am using Odin 3.13

wer8/ said:
I've read that multiple people were able to flash their SM-G930V to SM-G930A firmware and be able to get all of the LTE bands of AT&T. However, I am not able to, I am trying to flash G930AUCU4CRE4 and this is what i'm getting:
<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> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
On the phone screen I am getting an error as well after this. I was able to flash G930UUESACSF1 so the phone model now says SM-G930U, I picked AT&T's version from Sammobile, the phone works and i'm getting all LTE bands, however I am still trying to get the SM-G930A firmware so I can do VoLTE. When calling with the G930U firmware, it puts the phone call over HSPA. Any ideas? Am I not doing the right options on odin or something? I am using Odin 3.13
Click to expand...
Click to collapse
kinda surprised Odin let you do this as the firmware youre flashing is for a different model phone. try the modded Odin 3.13

youdoofus said:
kinda surprised Odin let you do this as the firmware youre flashing is for a different model phone. try the modded Odin 3.13
Click to expand...
Click to collapse
I just tried Odin3 3.13 3B modded, same thing. I have read that this error is common when trying to flash an older version than what is already on the phone, but I believe G930AUCU4CRE4 is the newest or second to the newest. The phone definitely took SM-G930U firmware because it shows as the model number on the download mode although this is definitely a 930V model, so I don't understand why it won't take this 930A firmware
The phone says SW REV CHECK FAIL: [aboot] Fused 10 > Binary 4
[1] eMMC write fail: aboot
same on odin:
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.

wer8/ said:
I just tried Odin3 3.13 3B modded, same thing. I have read that this error is common when trying to flash an older version than what is already on the phone, but I believe G930AUCU4CRE4 is the newest or second to the newest. The phone definitely took SM-G930U firmware because it shows as the model number on the download mode although this is definitely a 930V model, so I don't understand why it won't take this 930A firmware
The phone says SW REV CHECK FAIL: [aboot] Fused 10 > Binary 4
[1] eMMC write fail: aboot
same on odin:
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
Click to expand...
Click to collapse
prior to the S8, all the samsung phones for the different carriers were physically different, especially the gsm vs cdma variants even tho the cdma ones still have gsm card slots. The U firmware working isnt too much of a jaw dropper, i guess, but the A version failing inst a shock at all, even with modded Odin. Why do you need the A version again?

youdoofus said:
prior to the S8, all the samsung phones for the different carriers were physically different, especially the gsm vs cdma variants even tho the cdma ones still have gsm card slots. The U firmware working isnt too much of a jaw dropper, i guess, but the A version failing inst a shock at all, even with modded Odin. Why do you need the A version again?
Click to expand...
Click to collapse
Voice over LTE which is only offered in the firmware meant for the particular carrier. Verizon's is called "hd voice calling" which you must use Verizon firmware to be able to get, AT&T is VoLTE which you have to use AT&T's version. Right now when I make a voice call it switches to HSPA which doesn't sound as great and seems to have less coverage. In my area when calling someone it takes 5-10 seconds on the "dialing" screen before it actually starts ringing, almost like it has to find an open channel or something on the cell tower, I'm just guessing at this point. But I figured if it could do voice over LTE it would connect instantly with the best cell coverage. It still seems like there should be a way to do this, I've read others doing exactly what I am doing with success, but when I try it, it fails.

wer8/ said:
Voice over LTE which is only offered in the firmware meant for the particular carrier. Verizon's is called "hd voice calling" which you must use Verizon firmware to be able to get, AT&T is VoLTE which you have to use AT&T's version. Right now when I make a voice call it switches to HSPA which doesn't sound as great and seems to have less coverage. In my area when calling someone it takes 5-10 seconds on the "dialing" screen before it actually starts ringing, almost like it has to find an open channel or something on the cell tower, I'm just guessing at this point. But I figured if it could do voice over LTE it would connect instantly with the best cell coverage. It still seems like there should be a way to do this, I've read others doing exactly what I am doing with success, but when I try it, it fails.
Click to expand...
Click to collapse
cant you sideload safestrap and flash a custom AT&T based ROM?
that wont help with that bands tho. I know that certain phones only like certain versions of Odin, maybe try an older version

Question Odin Patched secure check failed : : up_param

Ok, hope everyone is doing well.
Trying to change the country firmware of a Galaxy a12 "SM-A125U - USA T-mobile" to an "SM-A125F - XTC Philippines" so I can use the sim card slot and get over-the-air updates. After a number of failures, I decided to flash one of the American firmware just to see if it works, and success no problem. Its when I try to change the country is when I get an error I have to see no one else get "secure check fail up_param" with this
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 5491 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> preloader.img
<ID:0/006> lk-verified.img
<ID:0/006> up_param.bin
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
Using the Home_CSC, cause if I use the CSC it gives me a pit error. I have redownloaded the files from 2 different websites multiple times in case of corruption but I am at my wit's end and need someone smarter than me to help out. Thanks

any luck w a solution? same issue when flashing twrp or magisk. trying modified vbeta and extracted boot.img from magisk patched ap file which i rearchived to boot.tar w 7 when ap file failed. same result.
using latest twrp-3.7.0_11-0-a12.img from twrp me and magisk latest as of 12 26 2022. odin patched 3.14.1
thank you for any advice or suggests anyone may have. H

rojen000 said:
Ok, hope everyone is doing well.
Trying to change the country firmware of a Galaxy a12 "SM-A125U - USA T-mobile" to an "SM-A125F - XTC Philippines" so I can use the sim card slot and get over-the-air updates. After a number of failures, I decided to flash one of the American firmware just to see if it works, and success no problem. Its when I try to change the country is when I get an error I have to see no one else get "secure check fail up_param" with this
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 5491 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> preloader.img
<ID:0/006> lk-verified.img
<ID:0/006> up_param.bin
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
Using the Home_CSC, cause if I use the CSC it gives me a pit error. I have redownloaded the files from 2 different websites multiple times in case of corruption but I am at my wit's tp+adb and choose adb tab in program + csc option.
Click to expand...
Click to collapse
have you tried the free samFW.com program called samlFW frp? it can reset csc codes vis ADB while phone is in regular mode. dial *#0808# to set usb to mtp+adb and then go to adb tab in program + csc option.
I was amazed it worked. ignore xploit failed msg. reboot. prosper.