Hi there,
First of all, the firmware info of my GT-I9100 is as follow:
PDA:ZSKI3
PHONE: XXKI3
Date: 23/09/2011
Android 2.3.5
I am currently stuck on a firmware issue and it's in real need to be rescued. Here's the full story.
The device firmware recently just got an upgrade to ZSKI3 through KIES. However, it was pretty upsetting as the upgraded official stock ROM from Samsung still contains bugs (the upgrade aggravated the previous problem as it drains the battery rapidly, still) and thus I made a decision and took the risk, by downloading the official ROM and kernel from the following thread
http://forum.xda-developers.com/showthread.php?t=1075278
and had an attempt revert to my previous firmware version (PDA: ZSKG2; PHONE: XXKG1) by flashing it through Odin. Unfortunately, the program stated the flash process as "failed" on the status bar. Consequently, the phone could not be booted with a message stating "Firmware upgrade encountered an issue" whenever it turns on.
This is what it shows on Odin as a result of flash failure,
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008>
<ID:0/008> Receive Response form LOKE
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Such action sounds idiotic but I wasn't really aware of such issue before hand.
May I ask whether there is any firmware rescue method to resolve such problem?
Thanks in advance.
Leo
Is this classified as a brick? If this is the case how should it be fixed?
Thanks in advance.
i had the same problem but i flash it back to stock
you need to reinstall all you drives and try to reinstall Odin and try it again. i had the same problem and i fixed it by just reflashing it after a couple minutes of letting it 'cool' down
Firmware upgrade encountered an issue
Polycap said:
you need to reinstall all you drives and try to reinstall Odin and try it again. i had the same problem and i fixed it by just reflashing it after a couple minutes of letting it 'cool' down
Click to expand...
Click to collapse
Please can you tell how to reinstall all you drives and then fix it by just reflashing it. Sorry but i am new in android world. needs a Miracle man to help me out with this "Firmware upgrade encountered an issue".
I have Samsung Galaxy S2
Related
Hi, so i downloaded the version for my phone
GT-I9100_XEO_I9100XXKH3_I9100XXKH3_I9100OXAKH3.
I wiped factory/data reset, system something and dalvik cache.
I used odin to flash ticking only the PDA,
but it stuck for like 1 hour on this stage:<ID:0/012> factoryfs.img
Both the loading bar on the phone and on odin are on the same level.
Here is the full Message:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img
<ID:0/012> factoryfs.img
Any help please??
99nirc99 said:
Hi, so i downloaded the version for my phone
GT-I9100_XEO_I9100XXKH3_I9100XXKH3_I9100OXAKH3.
I wiped factory/data reset, system something and dalvik cache.
I used odin to flash ticking only the PDA,
but it stuck for like 1 hour on this stage:<ID:0/012> factoryfs.img
Both the loading bar on the phone and on odin are on the same level.
Here is the full Message:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img
<ID:0/012> factoryfs.img
Any help please??
Click to expand...
Click to collapse
Did you by chance check repartition? If so I think you may be in trouble.
Nope, i checked like 4 times before i clicked start, and i can see it now,
I didnt ticked Repartition...
99nirc99 said:
Nope, i checked like 4 times before i clicked start, and i can see it now,
I didnt ticked Repartition...
Click to expand...
Click to collapse
Okay well there may be hope. Pull the battery and then use the button combo to see if you can get to download mode if you can then I suggest you restart your PC and make sure your using a UBS connection that is on the back of your PC, do not use any USB hubs or front usb connections. Also make sure kies in not running in the back round as it can interfere with the USB connections.
I made a backup with Cwk so i hope nothing will go wrong...
I pulled the battery, and i got to download mode, but odin doesnt seem
to recognize the phone...
Edit: i just noticed on processes, that kies Was running...
but Odin doesnt recognize the phone now...
Edit2: Odin managed to recognize the phone, so i started the process again...
but i got an error:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img
<ID:0/017> factoryfs.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i try again?
99nirc99 said:
I made a backup with Cwk so i hope nothing will go wrong...
I pulled the battery, and i got to download mode, but odin doesnt seem
to recognize the phone...
Edit: i just noticed on processes, that kies Was running...
but Odin doesnt recognize the phone now...
Edit2: Odin managed to recognize the phone, so i started the process again...
but i got an error:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> cache.img
<ID:0/017> factoryfs.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i try again?
Click to expand...
Click to collapse
Well as long as you can get to download mode there is hope. Maybe try a different firmware package.
Are you using the Samsung USB cable or the HTC one?
Successful!!
I just tried it again and it worked!
Thanks alot everyone, especially the one who told me to check
if kies was running
Hi, I been stuck on cache.img for hours (i left it overnight) kies isnt running in the background and i tried many times, im trying to flash XWKI4.
I came across this post and im using a HTC cable to connect, is this a problem??
Edit: Kies really messed up my phone it kept failing on firmware upgrade, asked me to do firmware emergency but that wasnt working either, eventually the firmware upgrade worked BUT the phone doesn't recognise my SIM card so i want to reflash in ODIN
saffad said:
Hi, I been stuck on cache.img for hours (i left it overnight) kies isnt running in the background and i tried many times, im trying to flash XWKI4.
30 mins max
I came across this post and im using a HTC cable to connect, is this a problem??
Probably is not the correct cable as per instructions
jje
Click to expand...
Click to collapse
hah yea had the same problem, its always dam kies gw gw
Tell me about it, kies is useless.
I tried another firmware but thats stuck on boot.bin right now, i have to travel 2hrs to get my samsung cable!! no idea what to do now..phone doesn't start (says do an emergency recovery). Thinking of going to service centre, i know I haven't void my warranty.
. Thinking of going to service centre, i know I haven't void my warranty.
ROOT = warranty void .Custom rom = void warranty
So if you have neither you are ok if not you need to flash stock rom to unroot and set rom counter to zero with USB jig .
jje
JJEgan said:
. Thinking of going to service centre, i know I haven't void my warranty.
ROOT = warranty void .Custom rom = void warranty
So if you have neither you are ok if not you need to flash stock rom to unroot and set rom counter to zero with USB jig .
jje
Click to expand...
Click to collapse
i never rooted and i never flashed a custom rom, i never even flashed a rom, just used kies to upgrade..so i think im ok
saffad said:
i never rooted and i never flashed a custom rom, i never even flashed a rom, just used kies to upgrade..so i think im ok
Click to expand...
Click to collapse
Yes you are ok .
Kies update broke phone well known service call .
jje
I have got stuck on DATAFS. Should I pull out the battery and give another try or ?
THX
THX A LOT Revived my SII!
****ty kies that sucks my sii wile upgrading fw...
THX ODIN and XDA
how much time it will take via oden i have single file putted in PDA box file is about 1.5 gb
asadnow2k said:
how much time it will take via oden i have single file putted in PDA box file is about 1.5 gb
Click to expand...
Click to collapse
5 - 10 mins to flash an entire firmware. Unless u flashed the wrong file...
"To err is human, to forgive is divine"
Sent from my SGS II
1.5 Gb pda file?
What the hell are you flashing there?
Sent from the little guy
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Auth means you are using the wrong tar fille. Make sure you use the MI1 file if you took the latest update
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Ablac said:
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Did you get it to work? I made the same mistake with SafeStrap, and now I can only boot to the download screen.
I'm downloading the ROM you linked, but it will take another two hours.
EDIT:
Download finished. How do I install it? I was expecting a .tar or .md5 to use with ODIN, but the link contains a zipped .img
Did it work?
Ablac said:
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
alexbmex1 said:
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
dlist said:
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Click to expand...
Click to collapse
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
All done
artjef said:
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
Click to expand...
Click to collapse
Beautiful ROOT! It is back. Thank you very much for the link. Worked like a charm.
Good Day!
I have a kcc-cmm-sec-shve330k 32GB that i flashed using odin 3.09 and E330KKKUBML1_FULL_20140103.tar but it failed!
here is what happened with odin,
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E330KKKUBML1_FULL_20140103.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sdi.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> recovery.img
<ID:0/008> NON-HLOS.bin
<ID:0/008> modem.bin
<ID:0/008> hidden.img.ext4
<ID:0/008> boot.img
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) i dont have any clue why it works with others and not with my cp
this fw (E330KKKUCNC1_PROXYME20140319.tar) is ok and it works for me and im using it but this has issues with apps working on 4.2 and not working in 4.4. like my navigator sygic. any suggestions guys ???
Another question is, Is it normal that after flashing for few times testing 4.3 & 4.4 FW that when it done, all my sms, apps, name of carrier Oleh is there and not erased?
Thanks in advance!
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
es0tericcha0s said:
Odin is failing on the modem, it seems. What baseband do you have installed at the moment? Many of the newer Samsungs have certain protections built in that cause issues with downgrading past official 4.3.
But it is normal for your stuff to still be there. Most firmware packages do not automatically wipe the phone while it flashes, which is why you will see the recommendation to factory reset after Odin flashes when you get stuck in a boot loop.
Click to expand...
Click to collapse
E330KKKUCNC1
KERNEL 3.4.0-683274
[email protected]#1
Many thanks for the quick reply
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
es0tericcha0s said:
Yep, you're trying to downgrade, and the modem partition is protected by the new bootloader crap Samsung has been adding since 4.3. So, you should be able to flash a custom 4.2 or 4.3 rom, as often times the newer modems are backwards compatible, but can not officially downgrade with Odin. Some people have actually bricked phones from trying, though is rare. Usually it just fails like yours, but is not a good idea to take those chances. Please make sure to do a nandroid backup and also, more importantly, make sure your EFS folder is backed up and saved somewhere safe before you get too crazy with the mods.
Click to expand...
Click to collapse
Thanks again for the info. i guess I'll stick to 4.4 for now
ricotek14 said:
Thanks again for the info. i guess I'll stick to 4.4 for now
Click to expand...
Click to collapse
No problem. Yea, it sucks. Stuff like that is actually a deal breaker for me and makes me not near as interested in Samsungs (see my sig for phones I've used - many Samsungs) as I used to be, no matter the specs / features. If I wanted to be locked in like that, I'd probably be more interested in iPhones. You'd probably have more luck trying to sort out why the certain apps aren't working for you or wait for the developers to upgrade for KK - which is kind of ridiculous they haven't yet as it has been out since November.
So I was given this phone that is stuck in download mode and am having quite a few problems getting it flashed with odin.... it seems to fail every time. not sure on the original android version it was rooted on .. The only information I was given is that it was rooted at one point and then they did a factory wipe getting it stuck in download mode... Seeing as Im new to this whole scene any help would be much appriciated
Tried 3 different firmwares from a post here
and also tried to get kies to recognize the phone .. It will not ,It is stuck at connecting
<ID:0/003> Odin engine v(ID:3.1100)..
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update:
On download screen : sw rev check fail....
If i have to choose a certain version of the firmware is there anyway to check the version I need without having to turn on the phone?
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Matthew M. said:
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Click to expand...
Click to collapse
fuse 0 binary 5
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
You should go back to kies and see what version it flashed. That way if this ever happens again you can download that version and flash it through odin
Deleted
Serioussamuel said:
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
Click to expand...
Click to collapse
Can you explain how you did this? I am running into a similar problem and neither a firmware upgrade nor a kies initialization is working.
Same problem here, I also don't know what my phone bootloader or firmware, I'm also stock in download mode...hope someone can answer and help us...
Hello, I am trying to flash stock 7.0 to my Sprint Galaxy S7 Edge. On the screen on my phone on download mode it says that the phone is model SM-G935A, but on the back of the phone it says it is SM-G935P, kind of strange if you ask me. Well the reason I am here is because I keep getting flashing errors with odin. I usually get some kind of "Fail (Auth!)" error or something like that and then the phone usually displays out a fused binary error. I have looked everywhere to find a solution and have not yet found one. The last attempt that I made to flash my phone to stock 7.0, I have the log of activity from the attempt here:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I got the correct firmware for the device, as you can see it does not say "device model mismatch" or anything like that, but I can never get a clean flash, it always has some error that I cannot find the solution to.
So if anyone could help me that would be awesome! I am kind of new to android, and especially to Odin, and I would like to learn more so that I don't run into these issues in the future!
Michaelkintner35 said:
Hello, I am trying to flash stock 7.0 to my Sprint Galaxy S7 Edge. On the screen on my phone on download mode it says that the phone is model SM-G935A, but on the back of the phone it says it is SM-G935P, kind of strange if you ask me...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3489011
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.