Hi folks. Longtime rooter and reader, but first time poster.
I attempted the S4 (VZW) s/w upgrade released today, using Kies, and during the process it froze and error-ed the following on my phone:
"Firmware upgrade encountered and issue. Please select recover mode in Kies & try again."
Of course, I've attempted the emergency recovery option a few times in Kies with no success. It will recognize my phone and the emergency recovery file, but will not actually send any data to the device to flash back to pre-s/w update.
So, I did a bunch of reading and d/l-ed a few stock roms to flash back using Odin (3.07). I get the same error with all roms as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> Erase...
<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)
I can go into more detail on the roms attempted if necessary, but this seems like a phone/user issue as all the rom attempts responded with the same authorization error.
Thoughts and/or next steps?
Edit:
I was able to get Kies to start an emergency recovery d/l, but it failed part way through. Pic of error attached.
Same Problem
Hey man,
my gs4 is failing at the same part....did you happen to figure out a solution?
most of galaxy S4 new security ( i545, i9505, SC-04E) phones end up with aboot.mbn coz of old firmware version. check firmware version before write with odin. i got same prob with SC-04E new security comes with MUAMG2 firmware. i have try to downgrade with MUAMDI and MUAMF1. both ends with aboot.mbn error. but it worked with MUAMF2 version.
always try to update with same or new version. downgrade will end up with this error.
regards..
same issue
i have the same issue with my phone, anyone found a solution yet?
Related
Hi Guys
I was having some trouble connecting my Galaxy S2 to my comp this evening to transfer some photos. Downloaded and installed Kies and it said there was a software update. Went through with it, upgrading to Icecream Sandwich (or w/e its called) but during the installation process it failed (can't remember the exact error message).
My phone is now unable to switch on, just showing the error message:
"Firmware upgraded encountered an issue. Please select recovery mode in Kies and try again."
Unfortunately, Kies will not locate my device and will not go through with recovery.
After some searching I came accross this forum, and specifically http://forum.xda-developers.com/showthread.php?t=1449771]this thread.
I've worked my way through that. I can flash the kernel succesfully through Odin (says pass) but when I try and flash the firmware it fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEW_BOOTLOADER.tar.md5 is valid.
<OSM> I9100PBVKL2_I9100PORALB1_I9100PBVKL2_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Get the same trying to use Bootloader aswell.
Now I'm guessing my warranty is now voided, so is there anything I can do to save my phone or is it completely b0rked?
Help much appreciated.
Some details from under my battery
Model GT-I9100P
SSN: I9100PGSMH
Any other details you need?
Bare in mind i cannot get into the phone at all.
Is it possible that I need to use the ICS recovery package rather than the Gingerbread?
i think u need full rom with pit and ur phone will work
Hi, thanks for your reply.
Unfortunately I'm in work and don't have a comp with full access. Any chance you could possibly link the files I need or at least point me in the right direction.
Many thanks.
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
I attempted to root my phone through Odin pushing superuser and twrp onto it as tutorials told me to do, and my phone literally goes to the boot logo and then stops. I have tried a million times to flash a stock rom back onto it but it won't push through either Odin or TWRP without error messages. It lets me flash a cyanogenmod rom through TWRP but the screen just goes back when I boot it up. Is my phone done for? Can I fix this somehow?
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
es0tericcha0s said:
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
Click to expand...
Click to collapse
I have tried using both Odin3_v3.10.6 and Odin3 v3.12.3. The files I have attempted to flash are XSG-J700HXXU2BPF9-20160629164434, CAU-J700HXXU1APA3-20160106083224, SM-J700H_J700HXXU1AOK5_J700HOLB1AOK1_5.1.1-MYM, and J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).
My phone's model number is J700H/DS. The error I am receiving is <ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J700HXXU1APA3_J700HOXY1AOL1_J700HXXU1AOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
from Odin and
"sw. rev. check fail. device:2, binary:1" on my phone's screen
Thank you for your reply, I am actually incredibly stupid and left the DS out of my model number and was therefore getting the wrong firmwear. I fixed it.
I had a n8010 with a custom ROM flashed into it and it was operating Android 4.1.2. In order to be able to receive the latest updates and revert to the original ROM (which I did not back up at the time) I tried flashing with Odin 3.12 after booting the tablet into download mode. However, the process failed and the Odin log is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I tried a second pass and it also failed in the options tab only "Auto Reboot" and "F. Reset Time" were clicked and AP type was ticked for the ROM ending with "tar.md5". I think my tablet is in the state what is called soft brick, how can I recover it and install the default stock ROM?
The device also has an SD card and when I unplug it Odin is stuck at "SetupConnection" step; I think this is an important observation. The Odin mode screen has the following information:
ODIN MODE
PRODUCT MODE: GT-N8010
CURRENT BINARY: Samsung Official ---Yet it still refuses to update so I attempted all of this.
SYSTEM STATUS: Custom
AP SWREV: A2
EDIT: After removing and inserting the SD card Odin was able to perform an installation of the stock OS. I hope it is a clean install and still have no idea why these problems occurred.
Thanks in advance
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Summary
1. Checked if USB Debugging on
2. Preceded to use CF Auto Root to root
3. Downloaded: system apps remover, root checker, root browser, and greenify in the play store.
Problem
I used system app remover to take out some sprint bloat-ware and apps, but doing so caused the device to kick into a soft brick. I might have deleted some core system files, not sure.
Solutions Attempted
1. Using the usual tricks, I tried to use Odin to flash stock firmware, however, I get the error message above and restart.
2. KIES and Samsung Smart Switch, don't connect to this phone.
3. Devices in recovery modes say ADB & SD Card apply update are disabled.
Can anyone help me out? Links to guides, of similar nature are helpful! Also, can someone help me find a good site to download the .tar.mdf files? For the Note 4 firmware; Sammobile is very slow.
I have a similar problem
Please how did you know the right firmware to download. Mine is on bootloop and I don't know the right firmware to download for ODIN. Smart Switch and Kies are not working for me too.