SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2 - Galaxy Note 3 Q&A, Help & Troubleshooting

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 said:
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
Click to expand...
Click to collapse
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

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.

ValenteL said:
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.
Click to expand...
Click to collapse
Thx,
The Shell terminal Emulator, have you link for download ? it's for windows ?

warhacke said:
Thx,
The Shell terminal Emulator, have you link for download ? it's for windows ?
Click to expand...
Click to collapse
Is for Android, on Play Store. To see this on Note 3 (if it work).

Thanks
ValenteL said:
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.
Click to expand...
Click to collapse
Thanks for your support.

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

jt_04 said:
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
Click to expand...
Click to collapse
Seems it is. Make sure you flash correct recovery for your phone/android version.
Sent from my SM-G925F

Can you still boot into download mode? If you can, flash TWRP using Odin 3.07.

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 LOCKN
WARRANTY VOID:0X0
sw rev check fail (aboot) fused 3 binary 2

The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?

frp lock
audit13 said:
The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?
Click to expand...
Click to collapse
No the phone is a SM-G935 t-mobile

Since the phone is not an n9005, not many people in this forum will b able to help because the n9005 doesn't have the frp option.
http://forum.xda-developers.com/tmobile-s7-edge

Related

[Q] stock rom flash fail

Hello,
-sorry for my english I dont speak well but...
phone: I9505
I was testing cyanogemod 10.1.3 for a while but then I decided get back to stock rom, did full wipe and put this ROM I9505XXUBMF8 into Odin and start flashing but he said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8_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> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-then I couldnt go to system, recovery just to download mode so I flashed TWRP.
(I tried another stock rom, odin, PC but always same problem.)
-then i tried get back CM 10.1.3 via TWRP and it flashed and work without problem.
-then I tried flash omega rom via TWRP and it flashed without problem but booting is very slow and during the logo Samsung it takes about 10mins to boot into system and device is very hot.
-Everything about Kies and antivirus is off.
-Using just original USB cable.
-what says download mode:
ODIN MODE
PRODUCT NAME: gt-i9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
START [224, 1440]
SW REV, CHECK FAIL : FUSED : 2 , BINARY : 1
Any ideas how to resolve this?
Thank you
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
samersh72 said:
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
Click to expand...
Click to collapse
Thank you so much, I was looking for something all day but i didnt sure what Im really looking for

[Q] Soft brick on Samsung S4 but cant write stock rom?

Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
VeryStealth said:
Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
Click to expand...
Click to collapse
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
VeryStealth said:
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
Click to expand...
Click to collapse
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
VeryStealth said:
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
Click to expand...
Click to collapse
U can flash It if it is 4.4.2 ....nd I dont get your last line ???
Sent from my GT-I9500 using Tapatalk
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505PHNEMK5_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
following happend with the downloaded version of stock rom.
now trying with .pit file
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
so i guess its not the pitt file?
is anything damaged? or do i have a faulty rom combo?
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
VeryStealth said:
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
Click to expand...
Click to collapse
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
VeryStealth said:
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
Click to expand...
Click to collapse
Glad u sovlved ur prblm bt from nxt tym read before flashing any custom rom u may hav flashed some wrong one
Sent from my GT-I9500 using Tapatalk

[Q] Need help recovering a bricked SM-900W8

This morning I updated my Note 3 (SM-900W8 on the Canadian Rogers network) to 5.0.
I had rooted this device before then, and had used Titanium Backup to backup all my apps/data. When the initial OTA update failed, someone pointed out that it was because the phone was rooted. So, figuring I had this backup in hand, I factory-reset my phone and went through the update - though I used the Samsung KIES app as it was quicker to download the firmware update than over my phone's WiFi.
Once the phone was on 5.0, I went to restore the backup... and found that Titanium Backup only works when the phone is rooted. Oops.
So, I figure that I need to root my phone again. I find instructions on how to root a note 3 and start to work through it. I go to the link for "Download appropriate CWM or TWRP recovery for your Note 3" and find the one that says "KitKat/Lollipop Android 4.4.2 CWM Recovery" and pick the one "SM-N900W8 Canadian Note 3 – CWM Recovery", because 5.0 is 'Lollipop' and my phone is the SM-N900W8. I attempt to use this with Odin, and Odin reports 'FAIL!' and the phone is stuck on "Downloading - Do not turn off target !!'. I give this a while just in case things take a while to happen... and nothing does, so I figure it did fail. I have no alternative but to turn off the phone now.
And restarting it, the phone comes up in "ODIN MODE" with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The messages at the top of my phone on this screen are:
Code:
ODIN MODE
PRODUCT NAME: SM-900W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
I connect the phone up again, select the Recovery tool in Kies... and the phone is not detected. No matter what I try.
So then I try and download the official firmware N900W8_RWC_N900W8VLU2DOC4_N900W8OYADOC4 from Samsung Updates and try to use Odin to recovery it that way.
Again, the update fails... time and time again.
The Odin messages output is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLU2DOC4_N900W8OYADOC4_N900W8VLU2DOC4_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now have a bricked phone, and no idea how to fix it.
What can I do?
frysco said:
What can I do?
Click to expand...
Click to collapse
1. Reflash STOCK firmware 5.0 for your device: HERE. Factory reset your device when finish of boot.
2. Use TWRP (You can flash this ONE via ODIN) and root your device then.
3. Don't restore your data of android 4.4.2.
I've managed to fix things.
From other searching around, it seems that trying to use Odin via VMWare Fusion on a Mac is a 'known issue' where it gets stuck at this point.
Installed a trial version of Parallels and a basic Win XP install, re-flashed and it WORKED!

Cant find firmware SMG900VZKV

So phone is stuck in bootloop and trying to use Odin to fix. But I cant find the firmware download for the Samsung Galaxy s5 it's the SMG900VZKV model through Verizon. Can anyone help me download this? I've looked everywhere for this and can't seem to find it. Please help.
im in the same situation please if you get some information let me know please!QQ
...
Hatesthunderbolt said:
So phone is stuck in bootloop and trying to use Odin to fix. But I cant find the firmware download for the Samsung Galaxy s5 it's the SMG900VZKV model through Verizon. Can anyone help me download this? I've looked everywhere for this and can't seem to find it. Please help.
Click to expand...
Click to collapse
My friend i was the same problem cuz i cant enter inside the phone but i get and other phone with the same model and them i can enter inside the phone and the exactly model is G900VVRU1ANCG download this firmware and enjoy again your phone!
Hatesthunderbolt said:
So phone is stuck in bootloop and trying to use Odin to fix. But I cant find the firmware download for the Samsung Galaxy s5 it's the SMG900VZKV model through Verizon. Can anyone help me download this? I've looked everywhere for this and can't seem to find it. Please help.
Click to expand...
Click to collapse
Here is the link to all the latest firmwares from Samsung:
http://samsung-firmware.org/model/SM-G900V/
Sent from my SM-G900V using XDA Free mobile app
Yea that firmware worked man. And as far as the Samsung website. Did not work. I went as far as calling them and they still couldn't help. Said for that particular model it was a copyright issues or some sorts. Anyways I got it back going but with the newest firmware... :/ But hey better than having a bricked phone!
Tried them all please help
Hey,
I've tried all the firmware and still bricked phone, read thru hundreds of post, still cant figure this out. What am I missing? OUt of all the files this one gets the furtherest in ODIN, -900V_Downgrade_to_NCG.tar\G900V_Downgrade_to_NCG.tar.md5, but provides the error below.
ODIN results:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/005> File analysis..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> persist.img.ext4
<ID:0/005> recovery.img
<ID:0/005> NON-HLOS.bin
<ID:0/005> modem.bin
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone shows:
Odin Mode
Product Name: SM-900v
Current BInary: Samsung Official
System Status: Custom
Reactivation Lock (KK): OFF
Qualcomm secureboot: Enabled (CSB)
RP Swerv: S1, T2, A1, A2, P1
Secure Download : Enabled
UDC Start
Sys rev check fails : Refer 2 > Binary1
Secure Check Fail: system
Software Update FAiled
Your device didn't update successfully. Use the verizon software repair assistant blah blah blah.
I have no access to system recovery only Odin mode. Any suggestions will be great and helpful.

[HELP] Samsung Galaxy S4 Stuck In Bootloop

Hi guys,
I rooted my GS4 (SGH-I337 running 4.4.4) but wanted to update it but was receiving an error that said "install interrupted". I then used flashify to flash back to stock firmware that i downloaded from SamMobile. However, after I rebooted the phone, it became stuck on the ATT logo screen. I have tried to use Odin but I get a fail message. Here are the logs:
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is what the phone says on Odin Mode:
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
emMMC Burst MODE enabled
START [224,1440]
SW REV. CHECK FAIL : FUSED : 5 Binary : 1
I have tried Odin v3.10.6, 3.09, 1.85, 3.07, and 3.04 with the same result. I read in some forums that using a pit file would help, but I receive a fail message using it saying, "Re-partition operation failed".
I have also tried wiping cache partition and factory reset through recovery mode with no success.
Any help would be appreciated, thanks in advance!
-Daniel
bump
Odin stops at aboot.mbn because the rom you are flashing has a bootloader that is older than the bootloader on the phone.
audit13 said:
Odin stops at aboot.mbn because the rom you are flashing has a bootloader that is older than the bootloader on the phone.
Click to expand...
Click to collapse
How can I find the appropriate rom?
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
audit13 said:
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
Click to expand...
Click to collapse
Thanks, I will try that.
audit13 said:
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
Click to expand...
Click to collapse
Ok so i booted into recovery mode, this is what it says:
Android system recovery<3e>
KTU84P.I3377UCUFNJ5
This may help: http://forum.xda-developers.com/showthread.php?t=2616221
It worked!! Thanks so much man, you're awesome.
Thanks for letting us know it worked

Categories

Resources