Database Info

[Q] Heimdall help for Droid?

Hi,
I've just installed the latest Heimdall (v1.3) to try to flash my Droid Charge, as I'm running Ubuntu and therefore ODIN is not an option. I was running GummyCharged GBE 2 with CWM Recovery, and wanted to flash the new modem. However, Heimdall seems unable to flash any files to my Droid and now when I turn on the phone I get this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been trying to use Heimdall to fix it, but no matter what I'm trying to flash, I get an error message very similar to this:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Expected file part index: 1761653664 Received: -1
KERNEL upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Re-attaching kernel driver...
I also get red text at the top left corner of the download mode screen that says "RX_TIMEOUT".
The "Expected file part index" is different depending on whether I'm trying flash RECOVERY, KERNEL, LTEMODEM, etc., but it seems to always receive a -1. Can anyone help with this, or simply point me to a resource that will let me get my phone back up and running (that works on Linux)?
Thanks for any assistance,
Dave

Are you flashing with battery in or out?

Battery is out, phone is in Download mode.

tlx45 said:
Battery is out, phone is in Download mode.
Click to expand...
Click to collapse
Put the battery back in after you're in download mode.

Same result unfortunately.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

I'm having the exact same issue on a Mac with Loin running heimdall v1.3.1. Following the advice of this thread. I can get the pit to upload but nothing else. But that only bricked my phone worse. I can still get to the download mode but nothing rom related will ever upload. Anyone have ideas?
Part of my output with verbose.
Code:
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
PIT upload successful
Uploading RECOVERY
0%ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
File Part #0... Response: 0 0 0 0 1 0 0 0
ERROR: Expected file part index: 0 Received: 1
RECOVERY upload failed!
Ending session...
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: Failed to receive session end confirmation!
The libusb error -7 and RX_TIMEOUT leads be to believe that the charge is not receiving what ever the heck it wants. Tried using --delay but that seems to be for the handshake with Loke
With --verbose and --stdout-errors
Code:
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
0%ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 1094576 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
File Part #0... Response: 0 0 0 0 2 0 0 0
ERROR: Expected file part index: 0 Received: 2
ERROR: Expected file part index: 26880 Received: 1606416092
RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: Failed to receive session end confirmation!
ERROR: Failed to receive session end confirmation!

How I saved my Charge:
Odin 1.85
This pit file: http://forum.xda-developers.com/showthread.php?t=1111486
And EE4: http://forum.xda-developers.com/showthread.php?t=1172182
Let it boot
From here you can start from scratch. Hope this helps someone.

incharge said:
How I saved my Charge:
Odin 1.85
This pit file: http://forum.xda-developers.com/showthread.php?t=1111486
And EE4: http://forum.xda-developers.com/showthread.php?t=1172182
Let it boot
From here you can start from scratch. Hope this helps someone.
Click to expand...
Click to collapse
OP was asking about Heimdall specifically because he can't run Odin because he's on Linux.

Get Windows 7 (Microsoft gives away free 30-day trials), and use Odin.
Sent from my SCH-I510 using XDA App

shrike1978 said:
OP was asking about Heimdall specifically because he can't run Odin because he's on Linux.
Click to expand...
Click to collapse
As I was in the same predicament as the OP; after 12 hours of messing with heimdall I just ending up using a friends windows computer and about 10 minutes later my charge was working fine. I even tried emulating Odin with virtualbox and reactos then tryed wine but usb support became the issues for both. I tried everything but the only solution became this and it worked. Debloated EP3HA is amazing from EE4, it was worth the struggle.

Sad android...maybe paranoid

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:
Code:
[email protected]:/mnt/sda3/.../prime# heimdall flash --RECOVERY /mnt/sda3/.../prime/TWRP/recovery.img --verbose
it's 3.0.2.0 i think
Code:
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...
[email protected]:/mnt/sda3/.../prime#
...
worth noting:
Code:
Manufacturer: "Sasmsung"
S/N: 0
Code:
ERROR: libusb...
Code:
MTP device '[usb:...
Code:
gingerbread man in spotlight...again...
...
any helpful tips for a more fruitful communication with this 'droid?

[Lenovo P8 TB-8703F (wifi) ] Brick impossible to start and flash with QFIL

Hello,
I recently try to flash my Lenovo TB-8703F under Lineage ROM.
But not my device is completly bricked and I can't power on it anymore.
When I try to flash it again under Download mode with QFLASH I get the following message :
HTML:
01:07:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:07:28: ERROR: function: sahara_main:854 Sahara protocol error
01:07:28: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
can you help me? I just want to revive this tablet.
I've join th full log in attchment.
Thank you in advance for your help.
Ptitsnake

error: no such device: RemixOS/kernel

Hello. I have been using RemixOs for a some weeks now but one day, when i was trying to boot it up, it showed this error message
error: no such device: RemixOS/kernel
error: file 'RemixOS/kernel' not found
alloc magic is broken at 0x7dfbcdao : 7df097ao.
please i need some help to get the system working again

Samsung Tab E cannot download stock rom

After I attempt to flash a stock ROM through download mode on Samsung Tab E, Heimdall outputs this error when its 4% done:
Code:
Uploading SYSTEM
4%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Is this a problem with the storage?

Try using odin