[URGENT] Error SW CHECK CHECK FAIL: [aboot] Fused 5> Binary 1 - Android Q&A, Help & Troubleshooting

Hello everyone !
I have a serious problem on my cell phone and I am desperate to solve it, I am even willing to reward for help (I mean it).
I have a Galaxy S8 (SM-G950U1 SnapDragon), I bought it at BestBuy Mobile and unfortunately do not know which carrier it is.
I was trying to do Root in it, but it was giving failure, it appeared the following message:
Error SW CHECK CHECK FAIL: [aboot] Fused 5> Binary 1
From what I understand I'm trying to flash an AP / PDA / Firmware in a different version, but how can I find out which version to download the correct firmware?
Thank you !!!

Thread closed, as it's a duplicate of this thread.

Related

A310F "SW REV. Check Fail Device 4. Binary 3" error

I installed the firmware of another country to the phone and made an error. I am getting the error "SW REV Check Fail Device 4. Binary 3" when I install my old firmware. Please help me.
jabieff said:
I installed the firmware of another country to the phone and made an error. I am getting the error "SW REV Check Fail Device 4. Binary 3" when I install my old firmware. Please help me.
Click to expand...
Click to collapse
Help

Help with Odin flashing FRP locked SM-T827V

Hello, I was recently given a Tab S3 (Verizon) by a friend, and it was FRP locked. When asked, the friend said that she had no Idea which account might have been on it, and none that she tried worked, so I was stuck. So far I have tried a lot, and most recently, I have been trying to use Odin to flash a Combo file that I found for this model, but it fails to flash, and the tablet states:
Code:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 0
A couple of questions:
1) What does this mean?
2) Is this because it is FRP locked?
3) If it is, am I SOL?
4) If not, am I SOL anyway with the FRP lock?
I have had some experience with android modding, so I'm not a total noob, but don't take that for granted, I may have missed something very stupid/obvious.
The current firmware is: Oreo/T827VVRS2BRJ1
The combo firmware is: Oreo (I think)/T827VVRU0AQB9
Odin reports FRP Lock is on
Well, I managed to get firmware to flash by getting the same version that is on the tablet currently, but the flashing did not help, because FRP lock is still on. I even went as far as to get a partition table file and completely nuke the nand, which was probably a stupid idea, but nevertheless, even that didn't work to remove the FRP lock. Any ideas?
Thanks, SciFI101
P.S. Also note that the firmware that flashed was not a combo file, I have no idea what the difference is, do I need a combo file to remove FRP?
Flash combination firmware and then remove the google account and delete the Google account on device administration. Flash back original firmware all done.
Which combo firmware should I flash? Any that I have tried have failed with the SW REV CHECK FAIL error.
Also, the stock recovery seems to be shagged, after the blue "Installing updates"/"No Command" screen, the screen goes almost entirely dark, but it is still the same blue screen with Andy in the middle. It still boots into the OS and download mode otherwise. flashing BL and/or AP doesn't seem to fix it

Tab S6 Verizon ( T867V ) To ( T865 )

Hello everyone, I wanted to know if someone managed to change the Verizon software to the T865, I tried and I get Secure Check Fail: abl
I have seen that this error has to do with the binary but my Tab is at 3 and the software that I want to pass is at 3 and I tried another at 4, any solution?

SM-A217F check fail VBMETA

Hi there,
So I recently bought a Samsung galaxy a21s second hand from a friend (NZC model) and I've been attempting to install custom recoverys on this phone (I do have a decent bit of experience with this) how ever whenever I try to flash anything that has vbmeta in it, it will post on the phone screen "CHECK FAIL (VBMETA)" and "DEVICE 0x5" Aswell as "0x0"
Is there anyway to fix or atleast diagnose this as its very irritating
Thanks
Can you post an image of the error in download mode? It may be version mismatch or you're trying to flash a version that is lower than the current one. Device 0x5 represents the current bootloader version. Or it may be that you need to disable encryption.

Boot Loop and does not enter recovery screen

Hi folks,
my trusty S3 (SM-T825) got broke unexpectedly. It showed "100% battery" in the morning but was unresponsive. A forced shutdown did reboot the device up to the logo-screen - from where it rebooted again. So obviously it's stuck in a boot loop.
Unfortunately, it does not enter "recovery" either (home) (up) (power). However, it DOES enter "ODIN mode" (home) (down) (power). There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
The device is still as original as it can be.
Any chance I can revive it or does that more look like a mainboard problem?
I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
smallfreak said:
...... There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
Click to expand...
Click to collapse
Afaik you should be able to flash stock with OEM lock active BUT idk if FRP will block flashing process.
If that happens it's imo afterwards in the same state as before so at least it won't worsen it.
Gonna loose all your data anyhow.
Got Smartswitch? This might help as well.
smallfreak said:
....... I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Click to expand...
Click to collapse
You can't replace recovery without OEM unlock.
smallfreak said:
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
Click to expand...
Click to collapse
Dunno if I'm qualified enough
Next turn ...
I tried flashing TWRP into the AP slot with SamFW FRP-Tool (ODIN). This worked so far but got me a note on the tablet "custom recovery blocked due to FRP lock".
Checking boot on the tablet - as before. Boot loop.
Next turn ...
Code:
Select file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Select file CP_T825XXU3CTA1_CP14962504_CL17011592_QB28791445_REV00_user_low_ship_MULTI_CERT.tar.md5
Select file CSC_ATO_T825ATO3CTD1_CL18361310_QB30233690_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 00:47
Reading... FAIL
unchecking CP and CSC, leaving only AP.
Code:
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 10:00
Reading... FAIL
Reboot tablet in download-mode, next turn: Try BL + AP:
Code:
Select file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Checking file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Checking file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Flashing (1/20) emmc_appsboot.mbn.lz4 OK
Flashing (2/20) lksecapp.mbn.lz4 OK
Flashing (3/20) xbl.elf.lz4Flash failed
Flash time: 01:26
Tablet moans about
SW REV CHECK FAIL : [lksecapp] Fused -1 > Binary 0
Click to expand...
Click to collapse
So maybe the firmware revision is different to the currently installed one? The latest file is from 2020 and since I did the usual OTA updates, this should be the version installed. But even if not, it sould not matter to upload a newer one, right?
Anything I can check?
So then obviously "Game Over"
Another piece of expensive waste that otherwise could have served well for years to come. Yes I know, selling something just once is an inferior business model to repeatedly draining my account for the same service.

Categories

Resources