Amazon Fire TV Stick vs Chromecast – XDA TV

There is no doubt that Amazon is a huge player in many markets, and they want to be a huge … more

Fight the Heat and Conserve Battery with EaseUS Coolphone

Memory hungry Android applications are often responsible for making our device … more

Battery Charged in 30 Seconds? Maybe in 2016

Phones and tablets are getting more and more power hungry with each passing generation. Their … more

ZArchive Manages Your File Archives

Today smartphones are quite powerful devices that can handle multiple processes at once. In fact, some of … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Heimdall help for Droid?

OP tlx45

6th October 2011, 05:30 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2011
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:



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
Last edited by tlx45; 6th October 2011 at 05:47 PM.
6th October 2011, 05:32 PM   |  #2  
Senior Member
Thanks Meter: 36
 
154 posts
Join Date:Joined: Dec 2010
Are you flashing with battery in or out?
6th October 2011, 05:47 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2011
Battery is out, phone is in Download mode.
6th October 2011, 05:49 PM   |  #4  
shrike1978's Avatar
Recognized Contributor
Flag Atlanta, GA
Thanks Meter: 3,095
 
3,413 posts
Join Date:Joined: Jun 2011
Donate to Me
More
Quote:
Originally Posted by tlx45

Battery is out, phone is in Download mode.

Put the battery back in after you're in download mode.
6th October 2011, 05:52 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2011
Same result unfortunately.
6th October 2011, 05:58 PM   |  #6  
lufc's Avatar
Retired Senior Moderator / Resident Priest
Flag Blackpool UK
Thanks Meter: 1,532
 
9,521 posts
Join Date:Joined: Oct 2007
Donate to Me
More
Please use the Q&A Forum for questions Thanks
Moving to Q&A
25th October 2011, 08:08 PM   |  #7  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2011
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!
Last edited by incharge; 25th October 2011 at 09:24 PM. Reason: I keep trying
26th October 2011, 05:38 AM   |  #8  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Oct 2011
How I saved my Charge:
  1. Odin 1.85
  2. This pit file: http://forum.xda-developers.com/show....php?t=1111486
  3. And EE4: http://forum.xda-developers.com/show....php?t=1172182
  4. Let it boot
From here you can start from scratch. Hope this helps someone.
26th October 2011, 04:22 PM   |  #9  
shrike1978's Avatar
Recognized Contributor
Flag Atlanta, GA
Thanks Meter: 3,095
 
3,413 posts
Join Date:Joined: Jun 2011
Donate to Me
More
Quote:
Originally Posted by incharge

How I saved my Charge:

  1. Odin 1.85
  2. This pit file: http://forum.xda-developers.com/show....php?t=1111486
  3. And EE4: http://forum.xda-developers.com/show....php?t=1172182
  4. Let it boot
From here you can start from scratch. Hope this helps someone.

OP was asking about Heimdall specifically because he can't run Odin because he's on Linux.
26th October 2011, 06:28 PM   |  #10  
Senior Member
Thanks Meter: 105
 
320 posts
Join Date:Joined: Aug 2010
More
Get Windows 7 (Microsoft gives away free 30-day trials), and use Odin.

Sent from my SCH-I510 using XDA App

Post Reply Subscribe to Thread

Tags
droid, heimdall
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes