How can I fix this? I want to go back to stock. No root. Please see below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
I need help with this ASAP.
If you haven't found it already, go to Droidstyle's Restore Guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ). Section 1b has step by step instructions on how to restore the phone. Make sure you use the pit file with the correct firmware version when doing the restore.
Unless you have a Note 2 that never had a firmware update since the phone's release in 2012, then you can't use the VRALJB stock restore image. Droidstyle warned that it would fail at sboot.bin if you try it. Also, if you ever upgraded to 4.4.2, then you can't downgrade back to 4.3 or 4.1.2 because of bootloader issues.
If your phone is currently on 4.1.2 bootloader, then you can restore back to that firmware version. If it's on 4.3 bootloader, then restore back to that... and if it's on 4.4.2, then restore back to that. After returning the phone to Stock, boot into recovery and wipe cache & do a factory reset... as Odin doesn't seem to fully wipe everything.
Droidstyle's link for 4.1.2 looks to be down.... but recognized XDA Developer imnuts has the 4.1.2 VRAMC3 Odin file on his Android File Host site here: https://www.androidfilehost.com/?fid=23159073880932932
Also...if needed, here's a link to the Verizon stock 4.4.2 firmware: ( http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/ ).
Good luck!!
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
GiantsFan91 said:
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Volume up+home+power button would put phone in Recovery mode if it was functioning properly.
You need to use Volume Down+Home+Power button to put the phone back into Odin mode (aka Download mode). From there, you can Odin flash the appropriate firmware to restore the phone. If you're not sure what version of Android you had on the phone before you tried to restore it... then I'm not sure which version you should use.
I used 4.1.1 Jelly bean.
GiantsFan91 said:
I used 4.1.1 Jelly bean.
Click to expand...
Click to collapse
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
I downloaded CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar and fail! I put sch-i605-16gb.pit and CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar. No good.
mattnmag said:
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
Click to expand...
Click to collapse
How? I have no recovery. I can't get in recovery.
You need to put phone into download mode to restore with ODIN... not into recovery.
I did..i restore with ODIN. No good.
You tried to restore back to 4.1.1. It will fail at sboot.bin every time and won't work. You need to restore back to a different firmware version.... whatever version you were on before you tried to Odin flash the 4.1.1 firmware. If your phone was updated to the newest 4.4.2 firmware them you will only be able to restore back to that firmware version because the bootloader is locked.
Bricked Galaxy Note 2 while updating to 4.3
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
christherock said:
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
tried that
mattnmag said:
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
Click to expand...
Click to collapse
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i used file name I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
and i used pit file sch-i605-16gb.pit
as stated before im still kind of new at this so any information you could provide me would help a ton.
christherock said:
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
Click to expand...
Click to collapse
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
the phone was on 4.1.2 before i attempted the update
mattnmag said:
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
Click to expand...
Click to collapse
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
christherock said:
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
Click to expand...
Click to collapse
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW/
found it
mattnmag said:
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
christherock said:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
I would still use the pit file. If you follow Droidstyle's Restore guide, (but just use the ODIN 3.10 version and the 4.4.2 firmware from Sammobile)... that will hopefully help you to get it restored.
The Sammobile site says not to have the repartition box checked.... but if you use the pit file, it automatically ticks the repartition box (which is what it's supposed to do.... so leave it ticked when using the pit file).
PS: Also make sure you're right clicking on ODIN and running it as Administrator....and disable all antivirus programs and close other running programs in the background when running Odin.
If your friend doesn't want the phone on 4.4.2 and it was never on 4.4.2 previously, then you could try reflashing 4.3 onto the phone using Odin 3.10 just to see if it would work with the newer Odin version. If it doesn't work, you could try 4.4.2.
Related
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
John90uk said:
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
haiderijaz said:
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
Click to expand...
Click to collapse
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
JJEgan said:
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
Click to expand...
Click to collapse
The problem started when i plugged my phone on charge, when i unplugged it the phone turned off and continued to restart after samsung logo screen. I then tried kies to upgrade and initiliase but when that reached 4% it would say an error occured. This happens constantly. I then closed kies and tried flashing a Stock rom with ODIN but it keeps saying FAIL in red.
Also afrer kies recovery it now says firmware upgrade encountered an error.
John90uk said:
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
Click to expand...
Click to collapse
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
haiderijaz said:
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
Click to expand...
Click to collapse
I am not using both softwares at the same time. Its a GT-I9300.
John90uk said:
I am not using both softwares at the same time. Its a GT-I9300.
Click to expand...
Click to collapse
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
haiderijaz said:
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
Click to expand...
Click to collapse
I can only get into download mode. When i try entering recovery mode i get a screen which says firmware upgrade encountered an error an issue. Where do i go from here?
Product code in download mode if blank its SDS .
JJEgan said:
Product code in download mode if blank its SDS .
Click to expand...
Click to collapse
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
John90uk said:
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
Click to expand...
Click to collapse
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
haiderijaz said:
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
Click to expand...
Click to collapse
It was from the UK. And i have tried to flash a T-mobile Uk firmware as it was on t-mobile. Thanks guys
Recovery mode and rooting are irrelevant to your issue. Try flashing the rescue firmware from the general forum, if that fails then you'll probably need a new motherboard.
Sent from my GT-I9300 using Tapatalk
Hi to everyone,
i had a problem with my galaxy S2 i9100 with stock ROM 4.1.2 with root executed by philz temporary recovery, i hope someone may help me.
Yesterday i was taking a picture and suddenly my phone showed Galaxy S2 logo, I think started bootlooping. I tried entering in recovery mode, sometimes showed "Applying csc etc." but never entering in recovery menu, other times blank screen.
So I decided to flash stock JB ROM with odin, my phone can enter in download mode correctly and stated original samsung binary and counter 0.
I used latest branded H3G stock ROM downloaded from sammobile: I9100XWLSD_I9100HUILS4_HUI Odin recognized phone but stucks on
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100HUILS4_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<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> cache.img
<ID:0/004> NAND Write Start!!
I followed this troubleshoot trying with multiple odin version, more cables but nothing worked. So i tried flashing philz custom kernel PhilZ-cwm6-XWLSD-OXX-4.87, odin started writing NAND but received write failed, i checked download mode and now i have custom binaries and increased counter with yellow triangle during power on.
After i tried to flash an old bootloader, and this flash was succesfully completed, but not resolved any problem.
Finally i tried to flash wipe JB leaked ROM linked in troubleshoot thread linked above with three separete files for PDA, CSC and MODEM but no luck. now when i power on, phone shows "Firmware Upgrade encountered an issue" message.
What can i do? Any suggestion will be appreciated
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
shionv plain
knuckles1978 said:
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
Click to expand...
Click to collapse
Do you mean selecting PDA from sammobile and pit file? Where can i get the stock one for pit?
I read about repartitioning with pit files that's a risky procedure that can brick phone definitively are there other safer procedures?
EDIT: Tried to flash stock ICS without pit and still not working
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.
So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
es0tericcha0s said:
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
Click to expand...
Click to collapse
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nynten said:
So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
Click to expand...
Click to collapse
If Odin fails to work when you try to flash the firmware, then try to flash the ROM again, but without closing Odin. Sometimes we have to try like 5 times for it to work.
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
es0tericcha0s said:
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
Click to expand...
Click to collapse
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Nynten said:
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Click to expand...
Click to collapse
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
es0tericcha0s said:
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
Click to expand...
Click to collapse
Thanks, worked perfectly.
:good::highfive::victory:
Hi guys. I have a galaxy s6 that I tried to flash with official firmware 5.1.1 via odin. I was rooted before that. The flash failed and now it says to use Verizon's software utility to restore the phone. That utility doesn't work and the reps at the store had never heard of it.I literally can't fix the thing. No amount of flashing in download mode helps. It always fails.
Anyway, I went to Verizon and they are sending me a replacement in two days. In download mode it still says that the firmware is official. However it also says samsung custom. (Assuming the root) I don't know if Verizon will backcharge me for this. Is there any way to get rid of the custom status? When I put it in the box to return it I'll leave it on the System Software Update Failed screen.
Remember I can't flash via odin, that just fails. Samsung smartswitch doesn't recognize the device. Recovery mode is a no go.
Thanks for the help!
What's the error message in Odin?
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
es0tericcha0s said:
What's the error message in Odin?
Click to expand...
Click to collapse
in seems to always fail. I can go back to download mode or be instructed to restore via Verizon's software assistant. Here is what odin has to say. It fails at the system.img Verizon G920V
<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..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mrao said:
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
Click to expand...
Click to collapse
I was not on 5.1.1 at the time. I downloaded 5.1.1 from sammobile or one of the other firmware hosting sites. I also tried 5.0.2 but that gives me a nand error.
Would perhaps flashing a pit file work? The problem is the the one firmware I originally tried to flash (5.1.1) doesn't have a pit file. The other firmware 5.0.2 does have one but it's only 4kb. I'm not sure if that's right.
Just in case anyone finds this in the future. I figured out how to fix this. I had have a working phone to install verizon's upgrade assitant. It would not work from the exe I found on the internet. From there I had to install it in a virtual machine because it did not like Win 10. From there I simply plugged in my device and it restored it. Use this method if odin doesn't work. I WILL NEVER ROOT AGAIN!
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
es0tericcha0s said:
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
Click to expand...
Click to collapse
Odin failed a flash and I could not reflash with odin again. I don't ever want to have that happen again. It wasn't the firmware I triple verified it before I flashed it. It was the correct firmware.