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
Related
New to messing with android and odin so bear with me.
I have confirmed the target device is a verizon phone model and I am using a verizon stock firmware.
I had a friend give me a Galaxy S6 SM-G920V as he wasn't using it anymore and my S5 bit the dust. I got a sim card put in it and activated. During the init the phone lost power and bricked the rom. So, I got the latest odin build and what I thought was a good firmware build and flashed the phone. I still get the startup failed message when I boot. So I called verizon and got some information about their specific firmware and started searching again. I found this thread that claimed to have the firmware I needed.
https://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
I have tried to use Smartswitch and verizon utilities to detect and repair my device but neither of them will recognize my phone is connected even after installing the samsung drivers.
My process for flashing the device are as follows:
Power on phone into download mode.
Select AP and load the .tar.md5
Check boxes for auto reload and F. Reset time
Connect Phone, it gets recognized
Click start
The firmwares I have tried:
ODIN version: 3.10.6
1st attempt :
Android 6.0.1
PDA: G920VVRS4CQA3
CSC: G920VVZW4CQA3
result: PASS, does not boot, teal screen of death with startup failed. flashed a second time and now its boot looping.
2nd attempt:
Android 5.0.2
PDA: G920VVRU1AOC3
CSC: G920VVZW1AOC3
result: NAND write fail. Flash aborts.
Is there something I am doing wrong here? Someone with more experience please correct me.
Also here is the log for the whole operation for the 2nd attempt:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mwdaue01 said:
New to messing with android and odin so bear with me.
I have confirmed the target device is a verizon phone model and I am using a verizon stock firmware.
I had a friend give me a Galaxy S6 SM-G920V as he wasn't using it anymore and my S5 bit the dust. I got a sim card put in it and activated. During the init the phone lost power and bricked the rom. So, I got the latest odin build and what I thought was a good firmware build and flashed the phone. I still get the startup failed message when I boot. So I called verizon and got some information about their specific firmware and started searching again. I found this thread that claimed to have the firmware I needed.
https://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
I have tried to use Smartswitch and verizon utilities to detect and repair my device but neither of them will recognize my phone is connected even after installing the samsung drivers.
My process for flashing the device are as follows:
Power on phone into download mode.
Select AP and load the .tar.md5
Check boxes for auto reload and F. Reset time
Connect Phone, it gets recognized
Click start
The firmwares I have tried:
ODIN version: 3.10.6
1st attempt :
Android 6.0.1
PDA: G920VVRS4CQA3
CSC: G920VVZW4CQA3
result: PASS, does not boot, teal screen of death with startup failed. flashed a second time and now its boot looping.
2nd attempt:
Android 5.0.2
PDA: G920VVRU1AOC3
CSC: G920VVZW1AOC3
result: NAND write fail. Flash aborts.
Is there something I am doing wrong here? Someone with more experience please correct me.
Also here is the log for the whole operation for the 2nd attempt:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You can't downgrade the S6 back to 5.0.2. Verizon locked the bootloader so you can't downgrade it to 5.0.2 and only around 5.1.1 around OK1 to QD1. (5.1.1 - 7.0)
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.
Hey guys I have an unlocked, att branded s22 ultra that i bought in las vegas. I want to flash it to the unlocked firmware. ive tried the att/xaa flashes and neither of them work. i keep getting the same error. i have enabled developer mode.
the errors are
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> persist.img
<ID:0/008> userdata.img
<ID:0/008> misc.bin
<ID:0/008> carrier.img
<ID:0/008> Home Binary Download
<ID:0/008> Total Binary size: 9431 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> aop_devcfg.mbn
<ID:0/008> aop.mbn
<ID:0/008> apdp.mbn
<ID:0/008> bksecapp.mbn
<ID:0/008> cpucp.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
anyone got any ideas? does my att sim card need to be inside or can I use any sim card? is there anything else is developer mode settings that I need to enable other than developer mode in general?
anyone?
Two things to have in mind, make sure they have the same baseband/bootloader and the second one, make sure you're using the patched version of odin
ccjl said:
Two things to have in mind, make sure they have the same baseband/bootloader and the second one, make sure you're using the patched version of odin
Click to expand...
Click to collapse
How do I verify the baseband and bootloader? Also could it be that my usbc cable doesn't have fast enough data output? I know it transfers data like pics videos etc so I assumed it was good enough. Thanks for your time.
Got to
settings > about phone > software information
In your phone, and in the list you'll see the baseband version, make sure the firmware you're trying to flash has same version, and if you're using the cable that came with your phone, that shouldn't be a problem. Again make sure you're using the latest patched version of Odin, there are a lot of fake ones online
ccjl said:
Got to
settings > about phone > software information
In your phone, and in the list you'll see the baseband version, make sure the firmware you're trying to flash has same version, and if you're using the cable that came with your phone, that shouldn't be a problem. Again make sure you're using the latest patched version of Odin, there are a lot of fake ones online
Click to expand...
Click to collapse
mine is S908USQU2AVDI and i cant find a file for that. its att branded but carrier unlocked.
tried the S908USQU2AVDJ file and it seems to be working..
looks like i corrupt the phone lmao... this is the only file that actually installed but now it doesnt work
can someone plz help me
I was getting these errors when I was connected with a bad USB cable, or via a USB HUB
pepa3205 said:
I was getting these errors when I was connected with a bad USB cable, or via a USB HUB
Click to expand...
Click to collapse
your s22 ultra is from att?
my is exynos, those errors was on old NOTE 10+
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.
Left Verizon with their S22 Ultra in frustration over botched 5GUW rollout. Happy with AT&T but want Verizon firmware gone (and to have VoLTE). Had great luck with Odin the last time. Here's the error string. Have tried different USB ports and cables:
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img
<ID:0/006> carrier.img
<ID:0/006> userdata.img
<ID:0/006> misc.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 10293 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> aop_devcfg.mbn
<ID:0/006> aop.mbn
<ID:0/006> apdp.mbn
<ID:0/006> bksecapp.mbn
<ID:0/006> cpucp.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions?
ncstewart66 said:
Left Verizon with their S22 Ultra in frustration over botched 5GUW rollout. Happy with AT&T but want Verizon firmware gone (and to have VoLTE). Had great luck with Odin the last time. Here's the error string. Have tried different USB ports and cables:
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img
<ID:0/006> carrier.img
<ID:0/006> userdata.img
<ID:0/006> misc.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 10293 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> aop_devcfg.mbn
<ID:0/006> aop.mbn
<ID:0/006> apdp.mbn
<ID:0/006> bksecapp.mbn
<ID:0/006> cpucp.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions?
Click to expand...
Click to collapse
I don't know which version of Odin your using but this below Patched 3.14.1B has never failed me
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
You can try Odon 3.13 patched
kraz01 said:
You can try Odon 3.13 patched
Click to expand...
Click to collapse
Thanks! I figured out I was trying to go to an older software version (ATT) so instead downloaded the SM-S908U1 version. Now I get the "fail! SHA256 is invalid" message! Any suggestions?
Which AT&T firmware version are you trying to use? Are you using the latest version?
S908U1UES2AVHL (SM-S908U1)
ncstewart66 said:
S908U1UES2AVHL (SM-S908U1)
Click to expand...
Click to collapse
That is the firmware for the unlocked version. You need the U firmware.
kraz01 said:
That is the firmware for the unlocked version. You need the U firmware.
Click to expand...
Click to collapse
Oh ok - I was going to do that originally but Sammobile's latest version of that is from March and Odin wouldn't let me flash an older version.
If you want to change from Verizon to AT&T.....just change CSC.
Download the SamFW app and just switch. It's as easy as that. No flashing etc.
wr3cckl3ss1 said:
If you want to change from Verizon to AT&T.....just change CSC.
Download the SamFW app and just switch. It's as easy as that. No flashing etc.
Click to expand...
Click to collapse
Don't I have to flash to get rid of the blinding VZW banner?
ncstewart66 said:
Don't I have to flash to get rid of the blinding VZW banner?
Click to expand...
Click to collapse
U mean the boot screen? If yes then...yes by changing CSac to ATT....no more VZW apps and boot. You'll get AT&T and boot and apps.
ncstewart66 said:
Don't I have to flash to get rid of the blinding VZW banner?
Click to expand...
Click to collapse
Go here to my thread
Enable & Select Bands thru Dialer (S22 Fam) /CSC CHANGE (S22 & MORE)
***Tested on S908U & S908U1*** But not limited, to those specific models. S22 Family should also be compatible as well...as the NEW FOLD 4. Thanks @Abaddon BAND SELECTION: To ENABLE all bands, please do the following: (See pictures attached...
forum.xda-developers.com
Or here...to a very good good guide...
How to Enable All Bands Through Service Menu on US/CA S22 series (including Sub-6 and mmWave)
What is this? This is a guide on how to enable all LTE and 5G bands on the US or Canadian S22 series phones by going through the service menu. This guide is mostly based on this S20U guide by mellojosh, but has been adapted for the S22U phone...
forum.xda-developers.com
Thank you wr3cckl3ss1, it looks straightforward and easy enough, the only issue I have is whether ATT has a CSC for S908U later than March available, which doesn't seem to be the case on SamFW or SamMobile - doesn't make any sense but it seems my phone won't allow updating to "older" versions.
wr3cckl3ss1 said:
Go here to my thread
Enable & Select Bands thru Dialer (S22 Fam) /CSC CHANGE (S22 & MORE)
***Tested on S908U & S908U1*** But not limited, to those specific models. S22 Family should also be compatible as well...as the NEW FOLD 4. Thanks @Abaddon BAND SELECTION: To ENABLE all bands, please do the following: (See pictures attached...
forum.xda-developers.com
Or here...to a very good good guide...
How to Enable All Bands Through Service Menu on US/CA S22 series (including Sub-6 and mmWave)
What is this? This is a guide on how to enable all LTE and 5G bands on the US or Canadian S22 series phones by going through the service menu. This guide is mostly based on this S20U guide by mellojosh, but has been adapted for the S22U phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Ignore my last message - it seems to have worked using SamFW and just updating the CSC to ATT! Thank you!!!!!