SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2

Search This thread

warhacke

New member
Jan 25, 2014
3
0
Hello everyone,
sorry for my english I'm french, I had a concern during an update of a custom rom, and since I no longer access the recovery (recovery bootloop) and when I want to put a stock rom j 'have this error message:
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
 

warhacke

New member
Jan 25, 2014
3
0
Hello everyone,
sorry for my english I'm french, I had a concern during an update of a custom rom, and since I no longer access the recovery (recovery bootloop) and when I want to put a stock rom j 'have this error message:
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2

ODIN SAY :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

My Phone SAY

ODIN MODE
Product-Name : SM-9005
Current Binary : Custom
System Status: Custom
Reactivation Lock: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY: 0x1
QUALCOMM SECURBOOT: Enable (CSB)
RP SWREV: S2, T2, A3, P2
WRITE PROTECTION: ENABLE

UDC START
 

ValenteL

Senior Member
Aug 25, 2011
2,167
902
Espinho
Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.
 

warhacke

New member
Jan 25, 2014
3
0
Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.

Thx,

The Shell terminal Emulator, have you link for download ? it's for windows ?
 

Bryanrd05

Member
Feb 17, 2015
10
1
Thanks

Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.

Thanks for your support. :D
 

jt_04

Member
Jan 18, 2015
10
4
the shell emulator has to be run on the phone? because i can't even start my phone anymore because i tried to flash a custom recovery
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,911
5,052
Toronto
Can you still boot into download mode? If you can, flash TWRP using Odin 3.07.
 

Rachelcharlyn

New member
Nov 18, 2015
4
0
So my phone got stolen and when i got it back i couldn't get in to it. So i tried to flash stock firmware with odin and here is the error i got in odin and the error the phone had. I would be greatful for any advice.

<ID:0/013> Added!!
<ID:0/013> Odin engine v(ID:3.1203)..
<ID:0/013> File analysis..
<ID:0/013> skip file list for home binary
<ID:0/013> persist.img.ext4
<ID:0/013> userdata.img.ext4
<ID:0/013> Home Binary Download
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> emmc_appsboot.mbn
<ID:0/013> lksecapp.mbn
<ID:0/013> FAIL! (Auth)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Here is what phone said
SYSTEM STATUS: Custom
FRP LOCK:eek:N
WARRANTY VOID:0X0
sw rev check fail (aboot) fused 3 binary 2
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,911
5,052
Toronto
The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?
 
  • Like
Reactions: kelvinkyw

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
    If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
    See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.
    1
    The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?