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"
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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)
HELP ME please.
I can flash the backup although it gets stuck at yellow boot screen. but that does get rid of the seaandroid enforcing
If someone could help me as well I'm having a similar problem. I have tried using multiple Odin versions and many stock SM-G900P 4.4.2 firmwares from multiple sources, but always have the same messages pop up.
Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
USB debugging is on and Odin does recognize the device is connect, I have also already installed the drivers again just to be sure. I have used Odin before with no trouble maybe its the fact the phone is from sprint and on lollipop since sprint is stingy on unlocking -_-. If someone could point me in the right direction or 100% working firmware links I'd appreciate it. I have also tried going about this through Heimdall and failed not even being able to obtain the pit file. If someone could provide a working one I'd also appreciate it I am fully aware it may brick the phone as everything else may do. Or show me the me the step by step to flash with Heimdall with a .tar. I'll take any advice thank you
you can try the newer firmware ok4
maybe this will work . unzip and place md5 in ap slot of odin
http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667
Sprint new locked bootloaders
unteaglejohnk said:
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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)
HELP ME please.
Click to expand...
Click to collapse
I have the same problem myself and it took me a few minutes to realize what the problem is. I just got a new phone from Sprint because my other one the USB port was basically broken I couldn't connect or charge. So after a few failed attempts at flashing a ROM I decided to look at my firmware and realized that it was the new updated bog1 version. Sprint decided to lock all the boot loaders so as of this moment I don't know how to flash any ROM or downgrade as the bootloader will not let you. As a matter of fact just last night I was walking into Walmart I pulled my phone out of my pocket to look at it and it was just finishing up installing some security policy updates. My phone then immediately restarted and got stuck at the spark screen. Just the fact that I was rooted sent my phone into a boot loop. As of right now the only thing I can do is reflash the stock bog 1. I have managed to get access to this one and I'm working on modifying the bootloader in anyway I can. I'm a little newer to this but I catch on pretty quick. As of now I have all the permissions unlocked for me to access all the files in that stock bog1 rom but haven't found a way to make them stick yet. I'm going to have to break down each individual file and hopefully I can come up with a solution or anybody for that matter because I'm a few months away from my contract being up and if I can't root my phone and customize it I don't want it. If they want my phone lock down and toddler mode then they can pay for it that's how I look at it lol. Make sure you turn off automatic security updates. There's also a post in here of how to clean that out so you don't have the newest security policy update. I know the exact file the bootloader is in but haven't found a way to get into it or modify it yet even though I have permission. It shows it copying /deleting but doesnt change. There is way too many people in this world to not have someone come up with a solution by now and anytime I search for it I get results from a year to five years ago , hardly anything recent thanks google. I also posted on times and started a thread I'm trying but I'm not as advanced as some of these developers on here but I am determined lol
I finally got it to boot up. Just took like 20 mins. Now it boots sometimes while others it won't and says process has stopped responding after the yellow screen. Why does it do this. The rom is official rom directly off Samsung kids.
may have cracked bootloader BOG1 G900P
i have been playing in thr sys files and today i managed to get a custom animation boot installed. after that i flashed a modded bog1 file from philz. it took and succesfully booted and am now reinstalling all my apps. i think i over wrote or blocked my bootloader. ill get back when i know for sure:laugh:
http://samsung-updates.com/device/?id=SM-G900P
Good evening all.
My cousin just brought me his galaxy grand prime G530H and the phone was booting but very slow. He asked me to format it for him. So I hard reset the phone and wiped data but when I started the phone, the virus is still there and the phone was not working properly it even has a launcher of its own (hola launcher). It looks as if the virus became part of the system. I'm not able to uninstall it. The only thing I was doing is to disable it. But once I connect to the internet, the phone hangs and I can't do anything. What is the solution. is there a way to wipe it. This is the first time I see this. anyone had this issue before. Please need your assistance.
Ok here is another update. I tried to flash it with original stock rom from sammobile using Odin. I load everything and click start.
the writing fails with the following error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone can suggest anything
Not sure if had applied an update that caused to become like that but this is my only conclusion and my cousin is saying that he did not do anything. Is there an image that I can restore it with that will undo this
Ok guys Please ignore my problem. I was able to find the solution in another thread and found the correct flash and flashed my cousin's phone and now it has been revived. Thank you XDA
I am new to Andriod world. I was trying to down grade GT-N7000 from Android 4.1.2 to ICS 4.0.4. With my bad luck during the process while device in download mode and ODIN started the cable accidently got unplugged. Since then I am not able to get in to recovery mode and it keeps flashing "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I tried that but no luck as it asks for recovery code..serial and model number entries did not work. However, it can still get in download mode so I tried reflashing with ODIN and following is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRK_N7000XXLRK_N7000ORALP2_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> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So that's where I am at this moment and hoping some of you experts can help me out to revive this phone. Please accept my advance thanks for taking the time to help.
Hey guys, thats probaly the wrong place to ask for help, however I got really stuck with Odin3.
I tried to install a custon rom, which I downloaded from sammobile.com, but when I try to flash my phone I get this error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Maybe it's important to know that my phone has currently no OS running, well at least TWRP says that.
I tried 3 different Roms, but nothing seems to work.
I also tried Smart Switch but it does not work either.
I tried it on 2 PC's with the original cable, with other cables and in every Port my PC has.
Thank you for everyone who wwants to help!
its stock rom not custom
have you tried with newer version of Odin?
the latest should be 3.12.3