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.

Problem downloading ICS sources using repo sync

Platform is kubuntu 10.04 in virtualbox VM
Anybody has any idea what this means or how to resolve it? Thanks in advance.
Encountered Error:
remote: Counting objects: 18, done
remote: Finding sources: 100% (10/10)
remote: Getting sizes: 100% (16/16)
remote: Compressing objects: 100% (8/8)
remote: Total 10 (delta 0), reused 4 (delta 0)
Unpacking objects: 100% (10/10), done.acking objects: 90% (9/10)
From <https>://android.googlesource.com/platform/ndk
4f085ae..e4cedbc master -> aosp/master
error: Failed to connect to 2404:6800:4008:c01::52: Network is unreachable while accessing <https://>android.googlesource.com/platform/packages/apps/CellBroadcastReceiver/info/refs
fatal: HTTP request failed
error: gnutls_handshake() failed: A TLS packet with unexpected length was received. while accessing <https>://android.googlesource.com/platform/packages/apps/CertInstaller/info/refs
fatal: HTTP request failed
error: gnutls_handshake() failed: A TLS packet with unexpected length was received. while accessing <https>://android.googlesource.com/platform/packages/apps/Camera/info/refs
fatal: HTTP request failed
error: gnutls_handshake() failed: A TLS packet with unexpected length was received. while accessing <https>://android.googlesource.com/platform/packages/apps/Contacts/info/refs
fatal: HTTP request failed
error: The requested URL returned error: 403 while accessing <https>://android.googlesource.com/platform/packages/apps/CellBroadcastReceiver/info/refs
fatal: HTTP request failed
Click to expand...
Click to collapse

any help?

Bump bump

It looks like repo tries to download files over IPv6 but your ISP is not prepared for it. How exactly you try to compile?
Look at this thread: http://forum.xda-developers.com/showthread.php?t=1386615

anonymous_coward said:
Platform is kubuntu 10.04 in virtualbox VM
Anybody has any idea what this means or how to resolve it? Thanks in advance.
Click to expand...
Click to collapse
github has been having problems over the last couple of days

[Completed] [Q] How to root T-Mo Galaxy Note 4 from Linux (Ubuntu/Debian)?

Any ideas? So far I've tried hiemdall, Jodin (which is friggen awesome) and towell apk.
Bottum line seems to be that I can't get access to the PIT.
Procedures up to this point: Dowload necesary images. Put phone into usb debug mode. Put phone into download mode and plug in. USB.
Q: Does it matter hat version of USB? I have both types of ports but was using the 3.0 at the time. I'll see if trying it on 2.0 has any effect.
A: It does change things but not for the better. On USB 2.0, the device is not even detected. Interesting.
Idea: The box in question is a custom built water-cooled war machine for gaming. I'll give this a try on my System76 laptop and see if results are different.
Output from hiemdall looks like this:
Code:
[email protected]:~$ sudo heimdall download-pit --output GalaxyNote4.pit --verbose --delay 50000
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://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:
http://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...
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
ERROR: Failed to receive handshake response. Retrying...
[email protected]:

jcllings said:
Any ideas? So far I've tried hiemdall, Jodin (which is friggen awesome) and towell apk.
Bottum line seems to be that I can't get access to the PIT.
Procedures up to this point: Dowload necesary images. Put phone into usb debug mode. Put phone into download mode and plug in. USB.
Q: Does it matter hat version of USB? I have both types of ports but was using the 3.0 at the time. I'll see if trying it on 2.0 has any effect.
A: It does change things but not for the better. On USB 2.0, the device is not even detected. Interesting.
Idea: The box in question is a custom built water-cooled war machine for gaming. I'll give this a try on my System76 laptop and see if results are different.
Output from hiemdall looks like this:
Code:
[email protected]:~$ sudo heimdall download-pit --output GalaxyNote4.pit --verbose --delay 50000
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://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:
http://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...
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
ERROR: Failed to receive handshake response. Retrying...
[email protected]:
Click to expand...
Click to collapse
I don't have your device, so I'm not an expert about it.
But I found a guide how to root a similar device (Note 2) ... also for Linux: Galaxy Note 2 Root Tutorials! [Windows/Mac/Linux].
And if you know how to flash something to your device on linux, you can use the easiest rooting method IMO: [SM-N910*] CF-Auto-Root.
If you have further questions about your device, just ask in the T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting forum.

Thread closed and thank you.

SM-G900W8 Heimdall Print-Pit error

when i follow the steps to load lineage from the lineage wiki and I get to the heimdall part where I type heimdall print-pit i get the following error:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
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: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
what can i do with this to fix it? Do i need to unlock the phone first? Has anyone had any success with this phone and loading lineage on it?

jack-server connection timed out error

Hello All,
I am facing error on building AOSP code for Android OREO.
~~~~~~~~~~~~
Connection to the Jack server timeout, retrying with debug
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8076 (#0)
* found 1 certificates in /home/rituraj/.jack-server/server.pem
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* Operation timed out after 0 milliseconds with 0 out of 0 bytes received
* Closing connection 0
[ 92% 56660/61548] cc out/soong/.intermediates/external/expat/libexpat/android_arm_armv7-a_static_core/obj/external/expat/lib/xmltok.o
^C21:06:43 Got signal: interrupt
ninja: build stopped: interrupted by user.
21:06:43 ninja failed with: exit status 2
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
Connection to the Jack server timeout, retrying with debug
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8076 (#0)
* found 1 certificates in /home/rituraj/.jack-server/server.pem
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* Operation timed out after 0 milliseconds with 0 out of 0 bytes received
* Closing connection 0
[ 92% 56656/61548] header-abi-linker out/soong/.intermediates/external/boringssl/libcrypto/android_a...oong/.intermediates/external/boringssl/libcrypto/android_arm_armv7-a_shared_core/libcrypto.so.lsdump
^C00:54:01 Got signal: interrupt
ninja: build stopped: interrupted by user.
00:54:02 ninja failed with: exit status 2
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
~~~~~~~~~~~~~~~~``
Please provide your input to resolve this error.
I am using 8GB RAM and Core i5 with Ubuntu 16.04 machine.
Thanks
Ritu Raj

any help you found?

Please let me know if you found any reason or fix to this problem. I'm building a different ROM but I keep getting the same problem... And it keeps happening at 92% as well, which makes me think there's something going on that can be fixed.