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.

Atrix 2 Wont Boot into Fastboot mode

My sceen wont come back to life whenver it goes into standby. The phone is still one however. This started happening after the upate to version 2.3.6. I would like to try 2.3.5 again however my phone also wont go into fastboot mode " Vol up/down and power same time".
Whats wrong with my phone?

My A2 is sleeping/waking up easily on 2.3.6. Are you sure that you're holding the power button long enough to wake it up?
It's odd that your phone isn't booting into fastboot...
-First make sure you're completely powered down. First "shut down" then pull the battery.
-Hold the volume up+down buttons while reinserting the battery, then release them
-Hold the volume down buton, then hold the power button. Wait about 5 seconds then release both buttons.
-This should make you boot directly into fastboot.

My phone is acting up. I definitely can't get into fastboot mode. I tired the SuperCharged V5 rom and the same screen issue was present. I really wish I could get into fastboot so I could flash back to stock in hopes in hopes it fixes my issue.
Your intrustions are confusing. Most insturctions i read say hit volup and voldow along with power at the same time. This just boots the phone normally, im not sure exactly what your steps below are indicating...
Here is what I did.
1. Removed Battery for 10 seconds
2. While holding volup and voldown down, I inserted the battery and immediatley let go, proceeded by voldown and power. (Nothing happens at all)

I'm a n00b and dont know if this will help.
I had almost the same problem after updating to 2.3.6 with the first two Atrix 2. I was told by AT&T that the OS was corrupted during update. This was prior to me rooting phone.
I started having problems again when I went to Supercharge V5. What I had to do to get to fastboot was pull out the battery, reinsert battery and then hold down power button and up/down volumn at the same time for about 5 seconds.
This took me several trys before I could get fast boot.
I plugged phone to USB on computer and reinstalled 2.3.5 using RSDLite 5.6 and InLineFlash.
Again n00b and steps may not be exact but best I can recall. Good Luck.

No dice. What a shame!!! I just paid $300 for this phone off contract. I dont have the receipt as i bought it on Criagslist, however it was brand new "sealed box" and phone.
What a joke, I can't even boot into fastboot!!! Never ran into any issues like this before where I can't even try to reinstall fresh factory os.
Anyone else have any ideas? Please please help me!

Additional Details...
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Is there any other option for me or Im I out $300?
Thanks in advance.

Thats exactly what mine was doing with Supercharged V5 it stuck in that loop when I unpluged it form charger.
It took me over 5 attempts of pulling out the battery reinserting it and holding down power button and up/down volumn.
I also had RSDLite open and INLineFlash place in the File Box ready to go.
I was about to give up and get ready to buy another Atrix 2 when I was able to get fast boot.
It did take me almost half a day to get it running. I do think however that their maybe some files missing because it doesnt run to the level it did before Supercharged V 5 was installed.
Not that their is anything wrong with V5, but being new at all this I more than likely messed something up.
I hear what your saying I would hate to have to buy another phone. Good Luck.

Thanks for trying to help but I think Im SOL. I have tried this process like 100 times and still can't get into fastboot. Im so upset right now, this was just after my Xperia Arc was stolen, then i have to buy this $300 phone and 1 day later its bricked.... ugh.... FML!

ej_424 said:
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Click to expand...
Click to collapse
It sounds like it's probably not activating the screen at the boot menu... but the boot menu might be coming up and timing out to a normal bootup like usual.
You might be able to still get to fastboot.
Basically boot up into the "dark black screen" before the 10 second timeout...
Then press VolumeDown twice, and VolumeUp once to hopefully select AP Fastboot from the invisible menu.

You seem to be somewhat right!!! I did this and a drive stareted to install when i plugged it onto my computer. However when i load up RSD lite, I see "fastboot EDISON s" under moble on far left, port type is listed as USB.
When I hit start after loading the xml file with teh "replace" zip overwriten the 2.3.6 files for a 2.3.5 restore i get "Failed flasing process. 1/18.
Any further ideas? Seems we are moving in the right direction!

Im definitely in fastboot, just can't flash back to stock as I get an error. Any thoughts? I was running stock 2.3.6 rooted, then went to Supercharged V5 Update 2 but never booted succesfully. Now Im in fastboot but can't flash back to factory.
I apprecaite all the help and I feel we are getting closer.

You might go through the manual moto-fastboot method of flashing... this seems like a good start.
RSD lite is typically doing the flashing steps through fastboot in the background for you. You might be able to get a better idea of what the error is if you use moto-fastboot.
Gotta get some sleep, good luck

Im desperately looking for some help. The method posted above seems to be the same using RSD lite. As soon as i try to flash it fails, I dont even get to step 1. Is there logging that RDS does to help me out.
Since I can get into fastboot and RDS lite detects it, do you think its possible to recover my phone?

RSD Lite Log Messages
I was able to find the logs messages within RSD Lite:
Here is what I see (Fails right away)
02/22/12 10:39:52 New Log Started For Software Download.
02/22/12 10:40:04 The FlashLog key is turned off.
02/22/12 10:40:06 Multi upgrade started for 1 phones
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
02/22/12 10:40:06 ERROR: 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL. - on device ID 0.
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL.
02/22/12 10:40:06 ERROR: Failed flashing process. - on device ID 0.
02/22/12 10:40:06 Multi upgrade finished.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/22/12 10:43:15 --------------------------------------------------------
Any ideas?

ej_424 said:
Any ideas?
Click to expand...
Click to collapse
Hmm no idea... Are you using windows 7? There have been reports of problems with people using vista...
I would still try going through the steps in moto-fastboot. If you look at the InlineFlashing .xml document, you can see the steps in order.
To replicate rsdlite, you'd just copy moto-fastboot into the same directory, then run these from a command line there...
moto-fastboot <operation> <partition> <filename>
ie: from the beginning of the steps...
moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot reboot-bootloader
moto-fastboot flash mbmloader mbmloader.bin
moto-fastboot flash mbm mbm.bin
moto-fastboot reboot-bootloader
Click to expand...
Click to collapse
etc...

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?

Marquis MP977 MarquisPad serial disabled

Hi,
Because I could not find a reliable rooting mechanism I soldered a serial FTDI UB232, and I gain shell access.
The serial works ok as long I am in u-boot prompt.
Texas Instruments X-Loader 1.41 (Apr 12 2012 - 12:06:17)
OMAP4460: 1.2 GHz capable SOM
**** DDR SDRAM PATTERN TEST ****
DDR SDRAM DATA BUS TEST..... [PASSED]
DDR SDRAM ADDRESS BUS TEST..... [PASSED]
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4 (Nov 9 2012 - 20:33:58)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
printenv
bootargs=console=ttyO2,115200n8 [email protected] [email protected] init=/init vram=48M omapfb.vram=0:32M androidboot.console=ttyO2
bootcmd=booti mmc1
bootdelay=1
baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
ethact=KS8851SNL
Environment size: 285/131068 bytes
As soon android boots when everything is settled down, the tty input is totally ignored, though the shell
prints all the os messages. There is no prompt. ?!?
[ 33.844390] wlan0: moving STA 00:90:a9:a5:51:a1 to state 3
[ 58.387908] omap_cpu_thermal_manager:sensor 66200 avg sensor 59795 pcb 0, delta 18897 hot spot 85097
[ 58.397766] omap_monitor_zone:hot spot temp 85097
[ 58.887908] omap_cpu_thermal_manager:sensor 63800 avg sensor 59795 pcb 0, delta 17742 hot spot 81542
[ 58.897827] omap_safe_zone:hot spot temp 81542
no prompt
Any idea how to outcome and enable the shell tty input.
Here are the pictures of the serial soldering and the serial to usb adapter.
(The pictures are mine, from the stack-over-flow post)
{
"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"
}
The ftdi

I found and android for OMAP blaze (GB and a kernel from https://e2e.ti.com/support/omap/f/849/t/310839),
After having all cowboys engineering from Texas headaches I finally end up with:
boot.img cache.img fastboot mkbootimg MLO_es2.1_gp MLO_es2.2_emu ramdisk.img ramdisk-recovery.img recovery.img system.img u-boot.bin userdata.img zImage files.
I tried first a non destructive flash, trying to flash the system, (then boot, kernel, recovery / all of them encountering same error)
Linux console:
sudo fastboot flash system system.img
[sudo] password for mpang:
< waiting for device >
sending 'system' (110304 KB)...
OKAY [ 42.127s]
writing 'system'...
FAILED (remote failure)
finished. total time: 42.137s
marquis tablet serial output, as shown in previous post
OMAP44XX TAB # fastboot
I2C read: I/O error
I2C read: I/O error
Device Serial Number: 5C28000200000001
Fastboot entered...
Starting download of 112951340 bytes
................................................................................... many dots
downloading of 112951340 bytes finished
writing to partition 'system'
Wrong Image... Failed to program
How did we get here fastboot.c 993 ?
Anyone ?, Thank you

ERROR: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.

How do i fix this in RSD lite thanks!!
ERROR: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.
i have no clue i'm flashing stock firmware on motorola device