[Completed] Samsung Galaxy note 3 - possibly bricked.. - XDA Assist

Hi,
I am new here, I've read the sticky so this seemed like the right place to post so here goes,
I have a Samsung Galaxy Note 3 (SM-N9005) which I have attempted (very unsuccessfully) to root, I followed some steps that others have done on various youtube videos using Odin3 and kingroot but unfortunately I believe my phone disconnected from the laptop while it was in download mode and now on each attempt I am left with the below message on recovery mode:
Firmware upgrade encountered an issue, Please select recovery mode in Kies and try again.
I tried Kies and have since found several articles stating that kies will never work if you have rooted or tried to root your phone.
When i try to download a new ROM or the original firmware ROM using the desktop Odin3 it fails every time now with the below transcript:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I've read many posts around the web suggesting ways to fix it but everything involves being in recovery mode which i cannot do, does anybody have any idea what i should do? please let me know if you need any further info, hopefully I am just being stupid and it's a really simple answer!

siv4444 said:
Hi,
I am new here, I've read the sticky so this seemed like the right place to post so here goes,
I have a Samsung Galaxy Note 3 (SM-N9005) which I have attempted (very unsuccessfully) to root, I followed some steps that others have done on various youtube videos using Odin3 and kingroot but unfortunately I believe my phone disconnected from the laptop while it was in download mode and now on each attempt I am left with the below message on recovery mode:
Firmware upgrade encountered an issue, Please select recovery mode in Kies and try again.
I tried Kies and have since found several articles stating that kies will never work if you have rooted or tried to root your phone.
When i try to download a new ROM or the original firmware ROM using the desktop Odin3 it fails every time now with the below transcript:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I've read many posts around the web suggesting ways to fix it but everything involves being in recovery mode which i cannot do, does anybody have any idea what i should do? please let me know if you need any further info, hopefully I am just being stupid and it's a really simple answer!
Click to expand...
Click to collapse
Greetings and welcome to assist. There are a few things it could be, you could try a different version of odin, it could be an older version of firmware you are flashing or a file has become corrupt. If you connect your phone to kies and select emergency firmware recovery then that will return your phone to stock
Good Luck
Sawdoctor

Related

GT-P5100 Firmware upgrade encountered an issue

Hi everybody, I tried to upgrade my GT-P5100 to 4.2.2 but something went wrong and now I have a black screen with this message:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably I have selected Re-Partition but I didn't have a PIT file
The tablet had the stock rom and was not rooted.
I have Odin 3.07 and this PDA file but the procedure fails:
P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5
Code:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can't start Recovery or Download mode.
Can you help me?
Please if I need some more files write me all the links to download them, because many of them were hosted by hotfile and are no more downloadable...
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
That´s the Black-Screen of Death! Downloadmode is on in this window Connect to your PC, Odin will get your device
There should be no Problem with the file itself "<OSM> Checking MD5 finished Sucessfully.." - bad download will give another output because the MD5 is not valid if it´s broken.
Make sure you uninstall KIES before using Odin and run Odin as Administrator !!!
Kies in installed and Odin is executed as administrator
So what should I do?
GT-P5100 restore stock rom firmware odin
SOLVED using this guide and this file
dylan6662 said:
SOLVED using this guide and this file
Click to expand...
Click to collapse
Hello, i have the same your prblem with my galaxy tab 2 10.1 !!!...
do you remember how you managed to solve?
Do you remember what was the file of "this link" (http://www.bergfiles.com/i/bf5bdebbf2hci0) that is no longer active?...
I have absoluty need !!
THANKS !!!
Still on trouble
I still can find the right link to download the necessary file to flash on my gt-p5100 like this case , my screen just still say "Firmware upgrade encountered......"
cant log into download mode
but still detect on odin
please help me.
Hi all. I have the same problem. A message "Firmware .... an issue" Tried different Odin versions. With 3.07 and 3.10 versions looks like flashing is ok, Odin shows no errors. But nothing on the tablet, there's not status bar. And when flashing finished, Odin shows no errors. But tablet really not flashed. What the problem can be? Who can help?
HELP HELP
andrezerotwo said:
HELP HELP
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...opment/odin-gt-p5100-4-2-2-stock-rom-t3022183
try this link, it is stock firmware.
further if it can't solve by just flashing firmware, you can try pit file. but be careful before flashing this with odin, be sure of what it will do, there are guides to explain the proper process.
http://forum.xda-developers.com/showthread.php?t=2552155
I have the exact same problem, tried different odin versions, flashed the stock firmware, also tried different pc's, but no solution.
this is the error I keep getting on odin, Tried Kies it says P3100 does not support initializing. A friend says maybe its a motherboard issue, is that possible or just a firmware problem? What should I do next?
This is the error I get in ODIN.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100DDCNA3_P3100ODDCNB1_P3100DDCLK1_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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
v1v14n said:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi! With my tablet the same. I understand that eMMC has died, need a replacement and reflashing of the programmer.
GT-P5100 Firmware upgrade encountered an issu
Hi All,
I have the exact same problem with GT P5100, I cannot update my 5100,Itried different odin (1.85,307,309,1,7) versions, flashed different firmwares, but no solution.
this is the error I keep getting on odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMD1_P5100DBTDMD1_P5100XXDLL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Many thanks in advance,

[Q] Win7 GT-P5110 Kies drivers & Odin - try to recovery stock image

I got a Samsung Galaxy Tab (GT-P5110) of which the tablet did not startup anymore, and know nothing about the prehistory.
I downloaded stock firmware from samsung site: http://samsung-updates.com/device/?id=GT-P5110
and downloaded the latest EUR version named : P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5
With Odin 3.07 I installed that image in download mode with default options left on. After that I got the following screen message on the tablet:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably something went wrong. Then I downloaded Kies from samsung site, installed it with all extra drivers and I got the problem that Kies never recognized the tablet. Reinstalled many times, tried different options, but the problem persisted (took me 8 hours totally). Battery of the tablet was fully loaded and before this problem I saw that it was loading correctly.
Then I read this excellent document : http://forum.xda-developers.com/showthread.php?t=1652398
Tried again with Odin 3.07 and 1.85 and could install the image with only the reboot option on in Odin, flashed successfully the image, but still the problem:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have much options left to look for. I was thinking about:
- driver issue
- wrong image
- wrong method
Can somebody help me to have this problem fixed ? I am willing to reinstall Windows 7 on this laptop.
Really nobody knows ?
never had problems here on Windows 8.
Maybe try flashing using Heimdall
But will I need a Heimdall image for that, because it does not accept the samsung image.
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
Click to expand...
Click to collapse
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
Click to expand...
Click to collapse
I am located in The Netherlands, and downloaded the specific image for the Netherlands, region PHN, used Odin 3.07 to install it, but still the same problem.
What can I do, wait for somebody who can give me a hint ? This is the first time I do a recovery of a Samsung tablet, and don't know how to continue with it.
Your help will be very much appreciated.
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Joery360 said:
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Click to expand...
Click to collapse
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
proconsoles said:
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Do you think that this problem is hardware related ??
Nobody knows ?
Same for me
I'm dealing with almost the same issue, except for my ODIN flashes it doesn't even succeed. I know this happened to it after I tried to use heimdall to update my CWM, but I have had no success getting anything to work. I've been without a tablet for like a week now, doing everything I can think of or find a walk through for. I mean for me, I wouldn't mind going back to stock as long as it works again. Here's what my ODIN is doing:
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm about to try the TWRP someone recommended above, I'll let you know how it goes
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I tried flashing a different version of TWRP and it looked like it was going to do something, but it isn't going. Here's what it did this time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_TWRP_2.7.0.1.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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Forgot to mention that I'm using Odin 3.09 on a p5113. Not that it makes huge difference.
Two things to try:
If you can boot into recovery, try the factory reset.
If not, have you tried Kies recovery mode?
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Maybe because Samsung / KIES Process running in background on your PC?
A Case of bad partitions
Deucethehero said:
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Click to expand...
Click to collapse
Try flashing with .pit file, partitioning set to on. Should correct partition problems. Somebody might have installed a non-android OS that botched. Look for a .pit file around the forum, you should find one. Good luck.
Thank you
Thanks for the tip, I'll give it a shot and post back with results!
Sorry for the late reply
Hey guys, I could have sworn that I posted back on Friday, but it's not here. Anyway, it's been a crazy few days for me traveling and school starting and all that.
About the tablet, I downloaded a pit file and it looked like it was going to work, but unfortunately it did not. I'm working on getting the tablet charged and set up to try again because I got a zip that had 2 pit files, so I'll try the other one soon. I'll post the results when I get them, thanks again for all the help!
Still not working, but I think some progress
Sorry to take so long responding, it's been a busy week.
So I just attempted to flash the .pit again, and it failed. Here's what Odin gave:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It says, "There is no PIT," but that's what I'm trying to flash, right? I'm a little confused, but I hope someone knows what that means.
Thanks for all the help guys!
New info!
So today I was messing around with the .pit file that I had, and I used an editor to make it exactly the same as one I found in another forum. After Odin told me that it failed, I went to reset the tablet, and it showed me the Galaxy Tab 2 screen, which it has not done for a few weeks now. Then I plugged it in and it shows the battery charging symbol. Currently it is a 18%, so I'm going to let it charge and then try booting it up again and see what I get. Hopefully all is well now, but we shall see here in a few hours.
I also was not aware that I needed to flash the system along with the pit, and once I had that going it made a little more sense to me.
I'm going to try to post that pit here if anyone wants it. Hopefully it will help someone else in the future.
Odin Flashed, but failed
So I got into normal old download mode on the device using that .pit file. Yay! However upon attempting to flash the stock os back on Odin gave me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEBLH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm going to look into other avenues, but this did set me back to the "Firmware upgrade encountered an issue... blah blah"

need some help. Soft bricked i925 verizon note 10.1

So i recently rooted my i925 with this universal method...
http://forum.xda-developers.com/showthread.php?t=2403230
https://www.youtube.com/watch?v=QCBLOhWavT0
Then I decided to try and run the casuall "Jailbreak" software to get a custom recovery and unlocked bootloader and i just checked "I did it" during the root portion since I already was... and now I'm soft bricked. I can only get into the download mode and tried flashing with odin but no luck might be doing something wrong... Also tried following the cyanogen instructions which involve flashing a cwm recovery in download mode but still no luck. Any help would be greatly appreciated!!! If I hold power the screen will just flash the download mode screen on and off. I pulled the back off and pulled power. No difference.
Any ideas guys? This is the first time I've bricked anything since I've been here and it's got me pretty worried...
Still stuck is anyone has any ideas.
2rz_taco_sr5 said:
Still stuck is anyone has any ideas.
Click to expand...
Click to collapse
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
tselling said:
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
Click to expand...
Click to collapse
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
2rz_taco_sr5 said:
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
Click to expand...
Click to collapse
Maybe try Heimdall commandline. You can flash individual pieces.
tselling said:
Maybe try Heimdall commandline. You can flash individual pieces.
Click to expand...
Click to collapse
I'm just going to warranty it out with verizon. Ive warrantied phones before with no issue. usually for amoled screens that get shadows before the year warranty is up. Hoping all goes well.
im having this same issue, device keeps starting and then fails out, is there a solution to this?

[Q] Firmware update failed and failed recovery with Kies

Hello,
I have a problem.
I used my Samsung Galaxy GT-P6800 until yesterday.
Yesterday I downloaded the latest version of kies and I installed it.
When I plugged my tablet to the program kies, this told me that there was an update available. So I accepted the upgrade.
Unfortunately not been successful upgrade. So I tried to make the recovery of the old firmware. I receveid again an error. Kies tells me to call the service center.
Now I am a tablet that does not turn on and that only goes in odin mode by holding down the power button plus the volume down button.
It should not be in recovery mode because if I try to press the power button for 10 seconds nothing happens.
How could I resolve the problem?
My tablet is not rooted.
I don't know what is the problem because doesn't compare the code error.
I do not know if it depends on the driver. I do not know if it depends on something else.
But I would like to re-use my tablet. Help me, please.
well,
I have used Odin to install CWM 6.0.3.0.
Then I have tried to install a rom take here: http://forum.xda-developers.com/showpost.php?p=21930183&postcount=2
P6800OXALQ2_P6800XXLQ2_HOME.tar.md5
but i read this message on Odin app.
Odin Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OXALQ2_P6800XXLQ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img
<ID:0/005> NAND Write Start!!
<ID:0/005> factoryfs.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How can I resolve, please?

Soft bricked Samsung Galaxy S6 - And I've tried A LOT of things, advice welcome!

Hey all
I've got a soft bricked Samsung Galaxy S6 where I can boot to the boot loader but not the Android OS. After trying lots of different things and reading a lot of the forum posts on here I'd come to a dead end so thought I'd start my own tread as I can't seem to see a solution for this issue currently.
Here's what I originally tried
So I've downloaded and installed Odin 3.10.6 and set that up on my computer just fine, it's a Vodafone Galaxy S6 so I downloaded appropriate firmware from here - http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387.
I then put the phone in to the 'Download mode' by pressing Volume Down, Center Home, and Power buttons and then connected the phone via USB to my computer. Then I start up Odin which seems to realise that the phone is there, in the top left I get '0:[COM5]' and in the log I get '<ID:0/005> Added!!'.
After this I press on the 'AP' button and navigated to the upziped .tar.md5 file which I stated I downloaded earlier. Odin takes a few moments to do it's thing and load the file. After about 30 seconds in the log I now have this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Now I press the 'Start' button and the process fails, here's what my log says;
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I've tried so far to fix the problem
Downloaded and installed the Samsung Galaxy USB drivers, restarted the computer and repeated the whole process - no change
Downloaded and installed an older version of Odin (Odin 1.85) and repeated the whole process, same problem
I've then tried this whole process again on the three different USB ports (two USB 2, one USB 3) on my computer but have the same problem
Repeated the whole process on my girlfriends laptop - same problem
So that's where I've got to currently and I've run out of ideas, can anyone point me in a new direction to try here or maybe I've missed something stupid?
Better, closer warmer
So I've gotten a bit closer with this one but still not solved the problem.
So I was trying to think of new ideas to try and resolve my problem - when the phone is in 'download mode' it a few facts and figures on the screen ... namely the model number which is 'SM-G920F' and also a few other interesting details such as 'Reactivation lock' is off. So there's another thing I can eliminate from my list.
Anyway I Googled the model number and found another Firmware to download from Sammobile .com
So I downloaded this Firmware and gave this a try and got a lot further - this time it seems to start to install actually almost all the way to the end before failing. Here's what my log says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPB8_G920FVFG3DPB8_G920FXXU3DPB8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The fact it's got this far to me means I'm cross USB drivers off the list too as surely the computer seems to know the phone is there right? ... So I'm not there yet but I seem to be much closer (I hope).
What I've done to try and fix it this time
After this first fail I've tried running Odin as Administrator, thought it may have been an permissions issue but I ran in to the same errors.
I thought I'd give it a try changing some settings in Odin and tick 'Flash lock' ... I know earlier it seems to have stated that reactivation lock was off but right now I thought I'd try anything - This completely stopped Odin in it's tracks when it got to 'Send lock information..' so this totally doesn't feel like the solution to me ...
So I'm stuck again until I think of something else to try ... If any of you lovely people out there have any clues or suggestions for something else I could try I'd love to hear from you ...
And I'm out of ideas!
Alrighty then!
I've tried this whole process with about 5 different firmware downloads now and I'm stuck simply because I'm out of places to download and try different firmware versions from.
Does anyone here have any suggestions for different firmware versions I could try or locations I could download and try different firmware versions from?
Any advice welcome!
N
try the CF- Boot for that phone, flash it with Odin
Richie G said:
try the CF- Boot for that phone, flash it with Odin
Click to expand...
Click to collapse
That's done it! Thank you!
And for all you future people reading this who might bump in to this post with the same problem here's what I did.
I found a 'CF Auto root' file for the version of my phone - CF stands for Chain Fire and you can get them from a quick google or from somewhere like www autoroot chainfire eu
This file is simply a tar.md5 file and you treat it like any other firmware file - In Odin click on 'AP' select the file and just hit start, as simple as that really.
N
hazardous_waster said:
So I've gotten a bit closer with this one but still not solved the problem.
So I was trying to think of new ideas to try and resolve my problem - when the phone is in 'download mode' it a few facts and figures on the screen ... namely the model number which is 'SM-G920F' and also a few other interesting details such as 'Reactivation lock' is off. So there's another thing I can eliminate from my list.
Anyway I Googled the model number and found another Firmware to download from Sammobile .com
So I downloaded this Firmware and gave this a try and got a lot further - this time it seems to start to install actually almost all the way to the end before failing. Here's what my log says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPB8_G920FVFG3DPB8_G920FXXU3DPB8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The fact it's got this far to me means I'm cross USB drivers off the list too as surely the computer seems to know the phone is there right? ... So I'm not there yet but I seem to be much closer (I hope).
What I've done to try and fix it this time
After this first fail I've tried running Odin as Administrator, thought it may have been an permissions issue but I ran in to the same errors.
I thought I'd give it a try changing some settings in Odin and tick 'Flash lock' ... I know earlier it seems to have stated that reactivation lock was off but right now I thought I'd try anything - This completely stopped Odin in it's tracks when it got to 'Send lock information..' so this totally doesn't feel like the solution to me ...
So I'm stuck again until I think of something else to try ... If any of you lovely people out there have any clues or suggestions for something else I could try I'd love to hear from you ...
Click to expand...
Click to collapse
solved ? if not do let me know
Bhargav Hegde said:
solved ? if not do let me know
Click to expand...
Click to collapse
Yes this is now solved thank you Bhargav

Categories

Resources