Database Develop

I can't install kernel with heimdall before Cyanogenmod 10.1...

I would like install Cyanogenmod 10.1 on my i9000. I installed on my Ubuntu 12.04 heimdall 1.4 deb (for Ubuntu 12.10).
The guide is tho official guide on wiki's Cyanogenmod: wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
1. Download Semaphore's ClockworkMod Recovery, and the Heimdall Suite:
2.Power off the Galaxy S and connect the USB adapter to the computer but not to the Galaxy S.
3.Now boot the Galaxy S into download mode by holding down Home & Volume Down. Accept the disclaimer. After this insert the USB cable into the device.
4.Place Semaphore's ClockworkMod Recovery file into the Heimdall directory.
5.On the computer, open a terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage --no-reboot
When I try to apply the kernel, this is the answer:
Code:
[email protected]:~$ sudo heimdall flash --kernel zImage --no-reboot
[sudo] password for domenico:
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...
PIT file download successful.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Releasing device interface...
[email protected]:~$
What's up? Where I'm wrong?

Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot

whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
THANKS!!!

How to open a terminal??
Hi
Please help! On the computer; How to open a terminal and run command...??
Thanks in advance

whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
Yes it worked
Thanks mutch

[Q] Heimdall protocol error

Hi, on mobile i enter to download mode and on pc in terminal i run following command
Code:
sudo heimdall flash --recovery recovery.img --no-reboot
but error occurred:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!

[Q] ERROR: Partition "factoryfs" does not exist in the specified PIT. [SOLVED]

[Q] ERROR: Partition "factoryfs" does not exist in the specified PIT. [SOLVED]
Code:
K:\GT-19000\HEIMDALL\Heimdall Suite 1>heimdall flash --repartition --pit m110s.p
it --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boo
t boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem mo
dem.bin
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...
libusbx: error [cache_config_descriptors] unexpected configuration descriptor si
ze (actual) for '\\.\USB#VID_0000&PID_0538#5&ED9EEE6&1&1'.
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.
ERROR: Partition "factoryfs" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
I tried this method to flash eclair back on my m110s. I am currently running cm7. But it gives above error. The flashing works fine using Odin but causing my baseband/imei missing. Any idea why?
EDIT: LOL, I guess Uppercase matters in windows compared to linux.

[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai

[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai
Q&A for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Flashing ROM from Mac OS X
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.

jvigneshcs said:
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
Click to expand...
Click to collapse
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo

tetakpatak said:
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for you response. I tried with my Samsung Galaxy Grand Duos GT-I9082 with suitable recovery.img.
Later I installed using Odin from Windows machine.

Successfully tested on Samsung Galaxy S4 Active (GT-I9295)
The frontend sucks But after some research I understood the logic and managed to (re-)flash my phone with I9295XXUCNH2 . I didn't need to repartition and had a valid .pit file on the phone, so it is pretty straightforward:
Code:
sudo heimdall flash --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4

Cannot load PIT from S3 Neo
Hi,
I want to root my i9301. This requires odin... Since I am on linux, I tried Heimdall. But I fail already downloading the PIT file.
Looks like usb problems, any idea?
Code:
Heimdall v1.4.1
...
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...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
tried i8730 using same cable at motherboard usb port.
worked fine with "WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
Ubuntu 16.04 Kernel 4.4.0-34-generic
thanks
Edit: solved, used odin on windows instead.

"No Sim Card" error after flashing

Hi, I've been trying to update my rom, and seem to have messed up the RADIO partition on my J700t.
I've tried flashing it back from stock via heimdall, and it fails
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RADIO
0%
ERROR: Failed to receive file part response!
ERROR: Retrying...
ERROR: Expected file part index: 0 Received: 1
ERROR: RADIO upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Restoring from TWRP backup doesn't seem to fix this problem. I was thinking about using dd to manually flash it from within recovery but I don't know what the correct partition to dd to would be, and that seems like something I should figure out before I break it harder.
Anyone have this problem before? Anyone know a fix, or have ideas? Thank you in advance.

I think that your best now is try to use the original rom using Odin

rgazapo said:
I think that your best now is try to use the original rom using Odin
Click to expand...
Click to collapse
Can't use Odin, no Windows, using Heimdall. Heimdall gives the above errors when trying to flash certain partitions

Okay fellas, I fixed it! Turns out it was an issue with Heimdall that was fixed in version 1.4.2 (I was using the version available in the repos, 1.4.1)
Had to compile from source to do that, and usually that leads to problems but in this case, it worked the first time, no problem, using only the information in the documentation.
Heimdall sure is some *terrific* software and I would like to thank Benjamin Dobell very much for his work on it. Not only does it work real good, but honestly I can't say I've ever seen any software compile correctly the first time I tried it, but Heimdall did. That's pretty impressive. Thank you, Benjamin, for your work on this.
See the following output if you're interested:
Code:
$ heimdall flash --RADIO modem.bin --verbose
Heimdall v1.4.2
Copyright (c) 2010-2017 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: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
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: 83
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: 02
max packet size: 0200
polling interval: 00
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...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
PIT file download successful.
Uploading RADIO
0%
3%
6%
9%
12%
15%
18%
21%
24%
28%
31%
34%
37%
40%
43%
46%
49%
52%
56%
59%
62%
65%
68%
71%
74%
77%
80%
84%
87%
90%
93%
96%
99%
100%
RADIO upload successful
Ending session...
Rebooting device...
Releasing device interface...

hmm - i’m using v1.4.2 w my J700T and I am getting the “ERROR: Failed to receive file part response!”
I’m going to hunt down a Windows machine so I can try Odin...

quick update: using Odin 3.14.1 on Win10 solved this issue for me.
how do we (and do we need to) nudge the dev that this issue is still outstanding in other configurations?