[Samsung Galaxy Player 4.0, 5.0] Ben456:
Hi! Long story short, I was messing up some things with android stock apps than force closes appeared. I then needed bring back a backup so I flashed package_us2.3.5.tar.md5 which work but I had clock app problems. So not really knowing what I was doing I flashed with the .pit file provided here with repartition checked and I started getting E: cant mount errors...

This is where it went ugly: I mistook 4.0 and 5.0 .tar and .pit file... So basically I am the owner of a brick. I mean it, black screen brick. But with the unbrickable resurector I could get it back to download mode and heimdall could pull the pit file + odin would detect the device so I guess I am not that unlucky... or so I thought.

Odin always fails after full NAND write, doesn't matter with what I try.

Heimdall (run in linux):

Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
.glassechidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
Serial No: "?"

length: 18
device class: 2
S/N: 0
VID:PID: 04E8:6601
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 0

Uploading PIT
PIT upload successful
Uploading KERNEL
0%
File Part #0... Response: 0 0 0 0 0 0 0 0

1%

File Part #1... Response: 0 0 0 0 1 0 0 0

3%

File Part #2... Response: 0 0 0 0 2 0 0 0

5%

File Part #3... Response: 0 0 0 0 3 0 0 0

6%

File Part #4... Response: 0 0 0 0 4 0 0 0

8%

File Part #5... Response: 0 0 0 0 5 0 0 0

10%

File Part #6... Response: 0 0 0 0 6 0 0 0

11%

File Part #7... Response: 0 0 0 0 7 0 0 0

13%

File Part #8... Response: 0 0 0 0 8 0 0 0

15%

File Part #9... Response: 0 0 0 0 9 0 0 0

16%

File Part #10... Response: 0 0 0 0 A 0 0 0

18%

File Part #11... Response: 0 0 0 0 B 0 0 0

20%

File Part #12... Response: 0 0 0 0 C 0 0 0

21%

File Part #13... Response: 0 0 0 0 D 0 0 0

23%

File Part #14... Response: 0 0 0 0 E 0 0 0

25%

File Part #15... Response: 0 0 0 0 F 0 0 0

26%

File Part #16... Response: 0 0 0 0 10 0 0 0

28%

File Part #17... Response: 0 0 0 0 11 0 0 0

30%

File Part #18... Response: 0 0 0 0 12 0 0 0

31%

File Part #19... Response: 0 0 0 0 13 0 0 0

33%

File Part #20... Response: 0 0 0 0 14 0 0 0

35%

File Part #21... Response: 0 0 0 0 15 0 0 0

36%

File Part #22... Response: 0 0 0 0 16 0 0 0

38%

File Part #23... Response: 0 0 0 0 17 0 0 0

40%

File Part #24... Response: 0 0 0 0 18 0 0 0

41%

File Part #25... Response: 0 0 0 0 19 0 0 0

43%

File Part #26... Response: 0 0 0 0 1A 0 0 0

45%

File Part #27... Response: 0 0 0 0 1B 0 0 0

46%

File Part #28... Response: 0 0 0 0 1C 0 0 0

48%

File Part #29... Response: 0 0 0 0 1D 0 0 0

50%

File Part #30... Response: 0 0 0 0 1E 0 0 0

51%

File Part #31... Response: 0 0 0 0 1F 0 0 0

53%

File Part #32... Response: 0 0 0 0 20 0 0 0

55%

File Part #33... Response: 0 0 0 0 21 0 0 0

56%

File Part #34... Response: 0 0 0 0 22 0 0 0

58%

File Part #35... Response: 0 0 0 0 23 0 0 0

60%

File Part #36... Response: 0 0 0 0 24 0 0 0

61%

File Part #37... Response: 0 0 0 0 25 0 0 0

63%

File Part #38... Response: 0 0 0 0 26 0 0 0

65%

File Part #39... Response: 0 0 0 0 27 0 0 0

66%

File Part #40... Response: 0 0 0 0 28 0 0 0

68%

File Part #41... Response: 0 0 0 0 29 0 0 0

70%

File Part #42... Response: 0 0 0 0 2A 0 0 0

71%

File Part #43... Response: 0 0 0 0 2B 0 0 0

73%

File Part #44... Response: 0 0 0 0 2C 0 0 0

75%

File Part #45... Response: 0 0 0 0 2D 0 0 0

76%

File Part #46... Response: 0 0 0 0 2E 0 0 0

78%

File Part #47... Response: 0 0 0 0 2F 0 0 0

80%

File Part #48... Response: 0 0 0 0 30 0 0 0

81%

File Part #49... Response: 0 0 0 0 31 0 0 0

83%

File Part #50... Response: 0 0 0 0 32 0 0 0

85%

File Part #51... Response: 0 0 0 0 33 0 0 0

86%

File Part #52... Response: 0 0 0 0 34 0 0 0

88%

File Part #53... Response: 0 0 0 0 35 0 0 0

90%

File Part #54... Response: 0 0 0 0 36 0 0 0

91%

File Part #55... Response: 0 0 0 0 37 0 0 0

93%

File Part #56... Response: 0 0 0 0 38 0 0 0

95%

File Part #57... Response: 0 0 0 0 39 0 0 0

96%

File Part #58... Response: 0 0 0 0 3A 0 0 0

98%

File Part #59... Response: 0 0 0 0 3B 0 0 0

100%

ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.

ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Re-attaching kernel driver...

On a side note, I thought perharps the battery was uncharged since I have read somewhere it doesn't charge when the "not phone" is in this state. True, it doesn't charge when to connected to a computer, a wall charger is fine. Why is that?

AND usb jig doesn't do anything on this case. But I haven't tested it on another phone which I will do soon.

Any ideas? I don't want to send back it to samsung as I might happen to me again (or to some of you)

Thanks!