GT-P5100 boot repair problem - GSM-Forum

Mrbenza · 04-09-2013, 08:38

If analyze Jtag Chain:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895]

Connecting to the target...OK
Set I/O Voltage reads as 2.60V, TCK Frequency is 8 MHz

Following devices are found on the JTAG chain:
Device on TAP #0: ID = 0xFFFFFFFE, IR Length = 0x06 bits
Total IR length: 0x0006 bits

********************************************

If try to Resurrect the phone:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895]

Connecting to the dead body...FAILED
None is detected.

I don't know the story of the tablet..
What's the problem? Maybe i need different resurrector DLL ( XLoader- )???
or it's a flash problem??

Thx in advance

**legija** · 04-09-2013, 12:22

Hi,
Xloader is deleted or not accessible, so JTAG is not enabled.
You should try to find omapflash package for this phone (like for i9100G).

BABAK NURI · 04-09-2013, 20:40

Hi
I Have Somthing For P5110 and P5113(Omap Flasher)...But I Think We Can Use For P5110
Please Contact Me Via Sonork For Tets This SW

Thanks

littmanr · 04-10-2013, 04:54

please post efs backup brother, im lost network on P5100. its possible to solve?
thanks

Mrbenza · 04-10-2013, 13:04

I've tried Omap for P3100 but whitout success..
Babak I'm waiting for you

zhildzik · 04-14-2013, 22:26

Did you found any solution to unbrick P5100. I have one P5100 with broken Xloader so unbrick with RIFF failed and i've tried with different versions/configs of OMAPFlash - nothing works. Looks like impossible to repair P5100 with deleted XLOADER

zhildzik · 04-17-2013, 22:11

Guys, is it impossible to unbrick P5100 with broken XLOADER with RIFFBOX?
Also no solution found with Omap Flasher.

I'm correct - we can't unbrick this device when XLOADER broken?

bluemind · 09-30-2013, 12:55

Quote:

Originally Posted by BABAK NURI

Hi
I Have Somthing For P5110 and P5113(Omap Flasher)...But I Think We Can Use For P5110
Please Contact Me Via Sonork For Tets This SW

Thanks

Hello,

I got a P5100 went to die during normal usage (i was just surfing on the web and then the P5100 turned off and never it started up again).

Any chance to try your SW with my Tab P5100?

Many thanks in advance.

kfxtech · 04-17-2014, 23:59

I also would like to try the omap flash package on my Tab 2 10.1 although my model is SGH-T779 which is same variants of P5100 etc does it matter? I get QHSUSB_DLOAD driver error when plugging in the tab with usb.

fantomasv · 05-14-2015, 01:25

please upload p5110 please

murad6229 · 04-06-2016, 08:24

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895]

Connecting to the dead body...OK
Detected dead body ID: 0x3BA00477 - CORRECT!
Set I/O Voltage reads as 2.59V, TCK Frequency is 8 MHz

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

WARNING: DCC Loader was unable to initialize FLASH1 chip. Error code: 0x00000034

No Resurrection Data is available for the eMMC Chip with Capacity = 0B
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14.68GB

ERROR: Selected FLASH Chip was not initialized by the DCC Loader.

olteanumarius91 · 09-17-2016, 13:20

Try resoldering the power management , and 34lm85am . I had the same issue as you had and for me this did the trick.

04-09-2013, 08:38	#1 (permalink)
Mrbenza Major Poster Join Date: Jul 2012 Posts: 49 Member: 1789765 Status: Offline Thanks Meter: 7	GT-P5100 boot repair problem If analyze Jtag Chain: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895] Connecting to the target...OK Set I/O Voltage reads as 2.60V, TCK Frequency is 8 MHz Following devices are found on the JTAG chain: Device on TAP #0: ID = 0xFFFFFFFE, IR Length = 0x06 bits Total IR length: 0x0006 bits ******************************************** If try to Resurrect the phone: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895] Connecting to the dead body...FAILED None is detected. I don't know the story of the tablet.. What's the problem? Maybe i need different resurrector DLL ( XLoader- )??? or it's a flash problem?? Thx in advance

05-14-2015, 01:25	#10 (permalink)
fantomasv Freak Poster Join Date: Jan 2005 Location: mexico city Age: 52 Posts: 359 Member: 106488 Status: Offline Thanks Meter: 24	please upload p5110 flasher please upload p5110 please

04-09-2013, 12:22	#2 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	Hi, Xloader is deleted or not accessible, so JTAG is not enabled. You should try to find omapflash package for this phone (like for i9100G).

04-09-2013, 20:40	#3 (permalink)
BABAK NURI Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43 Posts: 7,259 Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475	Hi I Have Somthing For P5110 and P5113(Omap Flasher)...But I Think We Can Use For P5110 Please Contact Me Via Sonork For Tets This SW Thanks

04-10-2013, 04:54	#4 (permalink)
littmanr No Life Poster Join Date: Oct 2005 Posts: 668 Member: 190377 Status: Offline Thanks Meter: 61	please post efs backup brother, im lost network on P5100. its possible to solve? thanks

04-10-2013, 13:04	#5 (permalink)
Mrbenza Major Poster Join Date: Jul 2012 Posts: 49 Member: 1789765 Status: Offline Thanks Meter: 7	I've tried Omap for P3100 but whitout success.. Babak I'm waiting for you

04-14-2013, 22:26	#6 (permalink)
zhildzik Junior Member Join Date: Mar 2006 Posts: 17 Member: 239082 Status: Offline Thanks Meter: 0	Did you found any solution to unbrick P5100. I have one P5100 with broken Xloader so unbrick with RIFF failed and i've tried with different versions/configs of OMAPFlash - nothing works. Looks like impossible to repair P5100 with deleted XLOADER

04-17-2013, 22:11	#7 (permalink)
zhildzik Junior Member Join Date: Mar 2006 Posts: 17 Member: 239082 Status: Offline Thanks Meter: 0	Guys, is it impossible to unbrick P5100 with broken XLOADER with RIFFBOX? Also no solution found with Omap Flasher. I'm correct - we can't unbrick this device when XLOADER broken?

04-17-2014, 23:59	#9 (permalink)
kfxtech Junior Member Join Date: Jul 2013 Location: Oregon Posts: 14 Member: 1980130 Status: Offline Thanks Meter: 0	I also would like to try the omap flash package on my Tab 2 10.1 although my model is SGH-T779 which is same variants of P5100 etc does it matter? I get QHSUSB_DLOAD driver error when plugging in the tab with usb.

04-06-2016, 08:24	#11 (permalink)
murad6229 Freak Poster Join Date: Mar 2009 Location: 75.BAITUN NOOR SHOPPING CENTER Posts: 163 Member: 987131 Status: Offline Sonork: 100.1614852 Thanks Meter: 25	Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Resurrector: [Samsung P5100 XLoader+ V1.0.4773.9895] Connecting to the dead body...OK Detected dead body ID: 0x3BA00477 - CORRECT! Set I/O Voltage reads as 2.59V, TCK Frequency is 8 MHz Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...OK WARNING: DCC Loader was unable to initialize FLASH1 chip. Error code: 0x00000034 No Resurrection Data is available for the eMMC Chip with Capacity = 0B WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14.68GB ERROR: Selected FLASH Chip was not initialized by the DCC Loader.

09-17-2016, 13:20	#12 (permalink)
olteanumarius91 Junior Member Join Date: Oct 2015 Posts: 3 Member: 2475155 Status: Offline Thanks Meter: 0	Try resoldering the power management , and 34lm85am . I had the same issue as you had and for me this did the trick.