Develop Bugs

Using heimdall with a Mac

I need some help,
I am trying to install CM11 on my Galaxy Tab Pro. I have a macbook pro running yosemite and I cannot get heimdall to work. I followed the guide on the CM's wiki page and I get this error message: (See bold at bottom of screenshot)
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...
ERROR: Failed to send data!Releasing device interface...
after sending the command through to push a new recovery. On CM's wiki page it says that if you encounter the error message you have to enter in these commands to disable the default usb drivers:
"On Mac OS X you may see this message: "ERROR: Claiming interface failed!". If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;-"
But when I enter these commands into Terminal it just comes up with this error message for all three of them:
(kernel) Kext com.apple.driver.AppleUSBCDCACMData not found for unload request.
Failed to unload com.apple.driver.AppleUSBCDCACMData - (libkern/kext) not found.
Does anyone have any insight as to why this isn't working for me. Would really like to get CM up and running on tabpro but with option currently not working and there being no other solution that works on mac's, Im kind of SOL right now. Any help would be greatly appreciated
-Thanks

Error flashing bootloader with heimdall

I need to update the bootloader on a T705 in order to run the Marshmallow ROM. Got the correct sboot.bin file but attempting to flash with heimdall gives the error "Failed to confirm end of file transfer sequence!":
Code:
# heimdall flash --BOOTLOADER sboot.bin
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
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.
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Can't use odin as I don't have a windows machine.
My pit shows the bootloader as read-only and zero bytes:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
Is that normal or does it mean the bootloader is locked? Sorry for my ignorance, don't have any experience flashing the bootloader.

Sorry I can't answer your questions but I'm also a non-windows user (Linux). To use the safer Odin I created a Windows VirtualBox VM with a Windows install iso I downloaded over the net. Subsequently it has been suggested by others that it would have been easier for my to have created a bootable usb. In any event you never have to activate the window license to use Odin just answer that pop-up by clicking later. I download the latest firmware (there is a firmware download tool thread in the general section), quickly and use Odin all in that VM.
I posted a how-to create such a VM in the general section but if doing it again I'd likely go the USB route but either way is likely safe than your current method.
Sent from my SM-T800 using XDA Premium HD app

You're lucky you even got Heimdall to connect on the tab s.
I've had zero success with it on either windows or Linux.
Stick with a VM as suggested. It takes literally a few minutes to set up.
https://dev.windows.com/en-us/microsoft-edge/tools/vms/linux/

Thanks for the advice. Heimdall on Linux previously worked well for me when I flashed TWRP on the same T705 a few months ago. This time though I'll try odin in a VM as you both suggest.

Got odin working. The VM was slightly problematic:
Couldn't get Virtualbox on Mac to work. VM couldn't see the tablet.
Under Linux, had to "modprobe -r cdc_acm" to get it to work, as described here
Even then, Odin was failing with a big red FAIL! message at the completion of the flash. Resorted to pirating Windows 7 and installing on a spare harddrive. Still got the Odin FAIL! So I think it was the files I was using. Would the slightly wrong version cause a flashing error? My tablet is an Australian T705Y and the images may have been for a different region.
Anyway, downloaded the complete official ROM from sammobile and that flashed fine using Odin. Then installed TWRP and now the Marshmallow ROM.

cr1key said:
Got odin working. The VM was slightly problematic:
Couldn't get Virtualbox on Mac to work. VM couldn't see the tablet.
Under Linux, had to "modprobe -r cdc_acm" to get it to work, as described here
Even then, Odin was failing with a big red FAIL! message at the completion of the flash. Resorted to pirating Windows 7 and installing on a spare harddrive. Still got the Odin FAIL! So I think it was the files I was using. Would the slightly wrong version cause a flashing error? My tablet is an Australian T705Y and the images may have been for a different region.
Anyway, downloaded the complete official ROM from sammobile and that flashed fine using Odin. Then installed TWRP and now the Marshmallow ROM.
Click to expand...
Click to collapse
yes I am curious how to flash only sboot.bin through odin (or any other means)

The heimdall command is at the top of the thread.
I never actually attempted the bootloader in odin. I tried flashing the modem (which I also had to update), but as that was failing I never progressed to the bootloader. For the modem I just used a tar file that contained modem.bin. Odin reads the PIT and figures out where which partition it should go in (in this case, RADIO). I expect it'd work for the bootloader too. The official ROM distributions are tar files containing *.bin files:
Code:
-rw-rw-r-- dpi/dpi 1148160 2015-10-23 00:29 sboot.bin
-rw-rw-r-- dpi/dpi 7592208 2015-10-23 00:29 boot.img
-rw-rw-r-- dpi/dpi 7803152 2015-10-23 00:29 recovery.img
-rw------- dpi/dpi 2313405472 2015-10-23 00:30 system.img
-rw-r--r-- dpi/dpi 40231200 2015-10-23 00:31 cache.img
-rw-r--r-- dpi/dpi 217281008 2015-10-23 00:31 hidden.img
-rw-rw-r-- dpi/dpi 28600832 2015-10-23 00:24 modem.bin
odin flashes each one in turn to the appropriate partition. Just use PDA to flash the tar file. Possibly you could use the BOOTLOADER (sometimes called just "BL") button, but I don't think it matters.

Need help flashing modem to my N910T

I've scoured the internet for hours trying to figure what I'm doing wrong with no luck.
I've recently flashed my N910T with _mone's developer build of lineageos. But it's not doing well with the old modem that I was using when i was back on CM12. So I've attempted to flash the modem using heimdall. I've tried both the EPK2 and EPG2 modems. Both times, heimdall throws an error back at me that says this:
ERROR: Failed to confirm end of file transfer sequence!
I've tried a couple different heimdall git repos (Benjamin Dobell's and a couple forks) just in case someone had fixed a bug in heimdall.
But is there something I've got wrong? Any idea why this is happening. I'm at a total loss. Any help would be hugely appreciated. My
Code:
> sudo ~/gitClones/karabijavadHeimdall/Heimdall/heimdall/heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin
Heimdall v1.4.1
Copyright (c) 2010-2014 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 data received, read 'empty' packet...
PIT file data receive completed, send kRequestEndTransfer...
PIT file download successful.
Uploading MODEM
100%
MODEM upload successful
Uploading APNHLOS
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: APNHLOS upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

can't flash twrp (no error - just not installed)

hello,
im trying to flash my S4 Mini with lineage os - first step installing twrp fails.
i tried using heimdall to to flash twrp with the gui and via cli, but fail the same way: they report no error at all! finish the flashing and reboot. when i then try to go into recovery the standard recovery is still there! everything is jsut as stock as it was before.
here is the cli output:
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-serranoltexx.img --verbose
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
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.
Uploading RECOVERY
0%
11%
22%
33%
45%
56%
67%
79%
90%
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
note that: i tried 2 different versions of the latest twrp (one compiled by someone from xda), and i tried the gui too - adding the path to the save pit -> same result.
my problem seems similar to this post:
https://forum.xda-developers.com/galaxy-s4-mini/help/heimdall-reboot-to-custom-recovery-t3474163
but there was no response
also, ive read that sudo can be problem for heimdall, but without sudo it cant access the usb....
if anyone has any idea, please dont be shy to attempt to help, or point to other places where i could get help thank you!
about me: this is literally the first time im having an android device (im a sailfish user), so forgive me the possible beginners mistakes. also, my host pc is runing mint19.

misc11 said:
hello,.
Click to expand...
Click to collapse
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
yes, the phone is still completely stock. not rooted, but apparently the bootloader comes unlocked with samsung phones...
the version is: GT-I9195. so, from your link, i understand that i HAVE to root it?

HemanthJabalpuri said:
Bro I think you are in stock.....
But which model? If i9192
Then root using https://forum.xda-developers.com/galaxy-s4-mini/general/root-root-s4-mini-i9192-2018-t3780235 and flash twrp.img using apps
Click to expand...
Click to collapse
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!

misc11 said:
thank you for your help! in fact, rooting the phone was the solution. installing twrp worked right away!
Click to expand...
Click to collapse
Thanks no worries
HemanthJabalpuri

Unable to install official Lineage 17.1 on SM-G960F

I'm following these instructions: https://wiki.lineageos.org/devices/starlte/install
But the first step fails: From within the Developer options menu, enable OEM unlock.
I don't have this option. Ok, doing this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Fine, OEM unlock appears in the menu. But I have to erase everything after enabling it - done. Now I have a completely new installed android 10. Yippie, I can start an endless loop
I try to continue without OEM unlock.
1. Installing a custom recovery using heimdall
Code:
heimdall flash --RECOVERY lineage-17.1-20200501-recovery-starlte.img --no-reboot
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...
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.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
On the phone it's written Only official released binaries are allowed to be flashed(RECOVERY) in red letters.
2. Installing LineageOS from recovery
Code:
adb sideload lineage-17.1-20200501-nightly-starlte-signed.zip
Total xfer: 1.00x
Errors on the phone:
Code:
...
E: failed to verify whole-file signature
Update package verification took 47.2 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.#1

Solved: The second try was successful.

Hi hukd, I understand that this is kind of necromancy, but do you have any idea what you did the second time? Was it perhaps 7 days after you launched into development mode? I'm having this issue, and am wondering if being in prenormal state is an issue, even after unlocking OEM.

Hey waveBidder, I would really like to help you, but I have absolutely no glue why it has worked the second time. If I did something different, it was accidental.