35

This is because the command you used to invoke heimdall was, heimdall flash --recovery And, heimdall is caps sensitive, try this instead. heimdall flash --RECOVERY ./clockworkmod_6.0.3.2_jfltespr.img --no-reboot


14

Start off by making sure that you're plugged into a USB 2.0 port. Then, put the device in download-mode, $ sudo adb reboot download continue flashing with heimdall, $ sudo heimdall flash --RECOVERY recovery.img That should work, Initialising connection... Detecting device... Claiming interface... Attempt failed. Detaching driver... Claiming ...


13

Newer versions of Heimdall will accept a .img file for the --RECOVERY parameter and automatically download a PIT from the device to add the img contents to. $ heimdall flash --RECOVERY recovery.img Heimdall v1.4.1 [trimmed some output here] Session begun. Downloading device's PIT file... PIT file download successful. Uploading RECOVERY 100% RECOVERY ...


10

My partition was not called recovery but "SOS". You can check it by doing: heimdall print-pit --verbose from a terminal while the tab is in Download mode. I flashed my p7510. Gist: https://gist.github.com/pskiden/6311605


9

It depends on your PIT partition file. Before you do anything using heimdall, print the partition table of your phone. sudo heimdall print-pit The output of the file is the location assigned to each partition. For example on my Galaxy S3, I have something like this: --- Entry #20 --- Binary Type: 0 (AP) Device Type: 2 (MMC) Identifier: 19 Attributes: 5 (...


6

I had the same problem. Looking at the source of heimdal revealed that this message is send when no USB device is attached. And this was in fact the case. lsusb showed that the kernel is not aware of any USB device related to the Galaxy S: flo@flo-pc ~/data/cm9-sgs $ lsusb Bus 002 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 Bus 003 Device 069:...


6

I just a got an email from the Heimdall dev, he said it's not compatible with the Galaxy Mini. Thanks guys for your replies.


6

I also had a boot loop today, after flashing Semaphore's ClockworkMod Recovery according to these instructions, then trying to boot to recovery mode. What helped me out was the hint at the bottom of that page: to use Replicant's recovery.img instead: heimdall flash --KERNEL recovery.img --no-reboot Update: Note that the hint has now been removed with the ...


6

I was experiencing the same problem, and I found a solution that worked for me in a comment on Heimdall issue #228. The problem for me was that udev was reserving the phone as a modem when I plugged it in. If you run dmesg and see a line that says "This device cannot do calls on its own. It is not a modem.", then this could work for you. As root, create a ...


5

If you use Linux - download heimdall-frontend so you can use GUI. It is much easier. To flash using Heimdall you first need to specify .pit file. .pit stands for Partitions Information Tables, so Heimdall knows where it need to flash it. To flash TWRP using Heimdall follow this steps: Open Heimdall frontend. Go to Utilities tab. You will see Download ...


4

This is a because of a bug in Heimdall v1.4 RC1 -- the version that shipped with Ubuntu 13.04. What you'll want to do is upgrade Heimdall to version 1.4 final, or the latest version.. That should do it. Run heimdall info | head -n1 to get your current version.


4

ARM is currently not supported officially by heimdall. You might have luck compiling it yourself: https://github.com/Benjamin-Dobell/Heimdall/ My advice however: Use a supported platform once (Win/Mac/Linux-x86/x64) and enjoy on-device updates from then on via ClockWorkMod recovery (CWM) or RomManager. Reason: Heimdall is only needed to install a ...


4

Inside Heimdall zip there is a driver folder. Run the zadig.exe click options - List All Devices Choose your phone from the drop down list (on my pc it was "MSM8960" I could not get it to work correctly on my PC, onece plugged into laptop "SAMSUNG Mobile USB CDC Composite Device") Go through the drivers (WinUSB, Libusb0, Libusbk) and clikc Place drive ...


4

PIT stands for Partition Information Table. A PIT file is basically a set of instructions defining the phone partition layout. You should use a it if you want to re-partition the phone with Odin. You only need this file when repartitioning the device and you don't need to repartition it unless you mess up the partition table to begin with, or when ...


3

You are rooted. AFAIK Samsung bootloaders are already unlocked, you only need to flash the recovery to get the "root" Now for the problem. Go to settings->about phone and tap the build number 7 times to enable developer options. Then go to settings->developer options and there you should be an option similar to root access. Make sure you select Apps ...


3

I managed to solve as follows (on Linux): Cause of problem: In the PIT, there is no partition, called "RECOVERY" (duh). Keep in mind, the command is case sensitive. Have a look at the PIT: sudo heimdall print-pit --verbose On my phone the recovery-related partition was called "Kernel2" What worked is: sudo heimdall flash --Kernel2 recovery-clockwork-6....


3

See the following page for downloading the required files: http://www.theandroidsoul.com/how-to-root-xwjvh-android-2-3-3-rom-for-galaxy-s-i9000/ Install Samsung Kies but dont keep it running while flashing as it will interfere with the process. Required only for the drivers. Download CF-Root kernel. File name – CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip. Unzip the ...


3

One possible explanation is that you have confused recovery mode and download mode which are (I have just discovered) two different things on some phones, mine included. I had the same error and switching to download-mode fixed it.


3

From [INFO] What the ROM files mean boot.bin This is the Primitive Bootloader. Seems to make some basic initializations and finally loads the secondary bootloader. Sbl.bin The Secondary Bootloader. It loads the PIT, the Linux kernel, params.lfs and the modem. It also is responsible when the device is charging while it's off. This file contains ...


2

One effective way with Heimdall is to just run sudo heimdall flash --RECOVERY twrp.img Worked for me on an S3 AT&T Then when phone reboots, go into recovery via adb reboot recovery


2

Same problem, contemplating throwing away and buying a new one. But mine was previously encrypted for work, flashed a new GoldenEye rom, and when I booted it asked me to decrypt the phone. I put the old pw in but since the "answer" file was lost, the decrypt failed and the cellphone rebooted. Same behavior when I put in a pw I KNEW was wrong. So I have ...


2

There are a few options here, let's do the easiest first: Do not boot into Download mode from the "4 way menu" from the device, this will cause issues. Ensure you turn the device off and boot into recovery with the Volume Down + Power buttons. Ensure USB Debugging is enabled on the device. Ensure samsung-kies has no processes running, or just uninstall it ...


2

On recent Android devices, when you have Factory Reset Protection, which is enabled automatically when you setup a Google account, custom binaries (the files that are not signed by the OEM) are blocked (custom recoveries, boot, etc) for security reasons as one can bypass that lock and gain access to your data. So disabling OEM lock in the Developer ...


2

Preface I have found the solution to my particular problem now, but if someone else knows more about this feel free to improve my answer or post your own. Solution Annoyed with what I thought to be heimdall's fault, I turned to odin (not in a religious way). This, however, gave me the same error. Close to desperation, I decided to check everything ...


1

I also had a similar problem. I added the udev rule as suggested in GitHub (link above), but the phone still wouldn't download. Then I found another simple solution on GitHub: Disconnect the USB cable. Setup the flash in Heimdall Frontend or command line. Boot the phone into Download Mode. AFTER it's in Download Mode plug in the USB and flash immediately. ...


1

If none of the answers above worked, the answer might be as silly as it turned out to be for me. Two things you might need to try before bumping your head into your screen: Potential Fix 1: Reboot in download mode without having the USB plugged in and only plug it in after having pressed the button that allows you to continue embarking on this dangerous ...


1

This happened for me on v1.4.1. There's a few ways to fix it: Ensure you have the latest & greatest version of Heimdall Install all this: sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev Reboot your computer Try connecting on a different USB port - 3 of my USB ports didn't work, and one ...


1

A image file does not really need heimdall. Most devices that update via a .img file allow you to just put it on internal storage and rebpot to update. An alternative is to move it to your device, and install it via TWRP by loading the File in it.


1

Heimdall is a open source tool, used to flash firmwares for Samsung devices. Heimdall works some kind of different from Odin.Heimdall flashes individual files where as Odin flashes a package files. PIT file in Heimdall is used to tell your device how to boot. It is general format and are considered one of the original formats for Macintosh file for ...


1

Try disabling verification, via safestrap, and try both methods + Sideload again. I should ask, why heimdall and safestrap? Use Clockworkmod recovery instead of safestrap and ODIN over heimdall. Yes, they require you to get your stuff online beforehand, but clockworkmod has got me out of a lot of soft-bricks If I was boring, everyone I know would not ...


Only top voted, non community-wiki answers of a minimum length are eligible