[Samsung Galaxy Core.] hadriankross:
INITIAL COMMUNIQUE:

...

"Samsung GALAXY CORE Prime"

("POWERED by android")

"metroPCS" ("t-mobile network")

"bong bong bong laa laa"

"buzz-buzz-buzz buzzzzzz"

(via usb cable to slackware--porteus variant: "Unable to open MTP device '[usb:001,013]'")

"buzz-buzz-buzz buzzzzzz"

("Unable to open MTP device '[usb:001,014]'")

"buzz-buzz-buzz buzzzzzz"

("Unable to open MTP device '[usb:001,015]'")

"buzz-buzz-buzz buzzzzzz"

("Unable to open MTP device '[usb:001,016]'")

"buzz-buzz-buzz" ...

...

System Recovery <3rd edition?> (up vol+pwr+home) appears normal for an os 5.1.1 Android.

(note: subject does not appreciate being called a "lollipop")

TRANSLATORS NOTES:

Android SM-G360T1, lmy47x.g360t1uvu1aofa, (unique s/n classified) not responding to Heimdall protocol...

Dreams of Replicant status wanning...

Suspect it (she?) is showing early stages of depression...

Z768G not so jealous now...suspect foul play ... >.> ... <.< ...

---

Heimdall output:

root@porteus:/mnt/sda3/.../prime# heimdall flash --RECOVERY /mnt/sda3/.../prime/TWRP/recovery.img --verbose

it's 3.0.2.0 i think

Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
www glassechidna com au

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:
www glassechidna com au/donate

Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"

length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
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: 82
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: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
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 request to end PIT file transfer!
ERROR: Failed to download PIT file!
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!
Releasing device interface...
Re-attaching kernel driver...

root@porteus:/mnt/sda3/.../prime#

...

worth noting:

Manufacturer: "Sasmsung"
S/N: 0

ERROR: libusb...

MTP device '[usb:...

gingerbread man in spotlight...again...

...

any helpful tips for a more fruitful communication with this 'droid?