Sony to Extend its AOSP Program to Other Devices

Sony will be offering its users the possibility to use AOSP ROMs as an alternative to the … more

Project Ara Smartphone Will Run Modified Android L with Hot Swapping

Project Ara is a very exciting topic–both for hardware and … more

Streamline Android Theme Customization with Graphic Porter

I dont have a custom theme on my Android phone, and the reason for this is because … more

Boost the Brightness of Your Sony Xperia Z1’s LED

I think the last time anyone has ever used a physical torch to find their earphones, … more
Post Reply

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

15th March 2014, 04:18 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
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/show....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.
16th March 2014, 08:27 PM   |  #2  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Really nobody knows ?
17th March 2014, 12:01 AM   |  #3  
Recognized Contributor
Thanks Meter: 9,480
 
5,004 posts
Join Date:Joined: Mar 2013
More
never had problems here on Windows 8.
Maybe try flashing using Heimdall
17th March 2014, 12:40 PM   |  #4  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
But will I need a Heimdall image for that, because it does not accept the samsung image.
17th March 2014, 01:05 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by proconsoles

But will I need a Heimdall image for that, because it does not accept the samsung image.

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 ?
18th March 2014, 09:30 AM   |  #6  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by proconsoles

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 ?

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.
18th March 2014, 09:56 AM   |  #7  
Joery360's Avatar
Senior Member
Flag Netherlands
Thanks Meter: 490
 
644 posts
Join Date:Joined: Aug 2012
Donate to Me
More
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
19th March 2014, 02:56 PM   |  #8  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by Joery360

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

I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/show...04&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.
22nd March 2014, 01:27 PM   |  #9  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by proconsoles

I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/show...04&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.

Do you think that this problem is hardware related ??
26th March 2014, 12:50 AM   |  #10  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Mar 2014
Nobody knows ?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes