Database Users

[Q] heimdall v1.4.0 - Ubuntu 12.04 64

Hello,
Having issues with heimdall on Ubuntu 12.04.
I was trying to flash ClockworkMODs recovery but i just hit this issue:
Code:
sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.6-jfltexx.img --no-reboot
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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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
0%libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Its been a while since i have done this, but i'm sure i have no issues before on this system.
Anyone know what the issue is?

I don't know what the issue is, but version 1.3.2 of Heimdall worked. I think the issue is in the latest version of heimdall somehow. The error thrown by libusb seems to be of the "not supported" type.
[/COLOR]
-=nezero=- said:
Hello,
Having issues with heimdall on Ubuntu 12.04.
I was trying to flash ClockworkMODs recovery but i just hit this issue:
Code:
sudo heimdall flash --RECOVERY recovery-clockwork-touch-6.0.3.6-jfltexx.img --no-reboot
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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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
0%libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=12
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Its been a while since i have done this, but i'm sure i have no issues before on this system.
Anyone know what the issue is?
Click to expand...
Click to collapse

memstick said:
I don't know what the issue is, but version 1.3.2 of Heimdall worked. I think the issue is in the latest version of heimdall somehow. The error thrown by libusb seems to be of the "not supported" type.
Click to expand...
Click to collapse
Hey, I know this thread is somewhat old... But I am running ubuntu 12.04 x64 as well. I only saw 1.3.2 in i386 at the github downloads for heimdall. Did you just install libusb-1.0 i386 as well to get heimdall 1.3.2 to work?

evarInward said:
Hey, I know this thread is somewhat old... But I am running ubuntu 12.04 x64 as well. I only saw 1.3.2 in i386 at the github downloads for heimdall. Did you just install libusb-1.0 i386 as well to get heimdall 1.3.2 to work?
Click to expand...
Click to collapse
Hey guys! Just wanted to let you know that if you are still having this issue, you need to update your kernel. If you are unsure how to do this, just drop me a line and I'll give you some links and info. Just remember to rebuild heimdall and libpit.

similar issue
I think i have a similar problem
i am using heimdall 1.4 on ubuntu 12.04, when i try to flash cwm recovery the program stops at detaching driver and does not even proceed to "Initialising protocol..." in the above image.
using samsung i9082
could someone help please.

yogneo said:
I think i have a similar problem
i am using heimdall 1.4 on ubuntu 12.04, when i try to flash cwm recovery the program stops at detaching driver and does not even proceed to "Initialising protocol..." in the above image.
using samsung i9082
could someone help please.
Click to expand...
Click to collapse
same, same device

sorry but... heimdall, works on i9500?

I9505 problem

Hello,
My phone got stuck in a boot loop suddenly, during normal use.
Now I am trying to get it working again.
I have tried several tutorials to reflash stock firmware/unbrick the phone but without any success.
Now I am at a point where I have no idea how I should continue. Maybe someone of you guys can help me what I can try next, before I have to accept that it's dead.
I am able to boot into download mode, not into recovery mode.
When I am trying to turn on the phone the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
When I am trying to flash a stock firmware file (I9505XXUHOJ2_I9505ATOHOJ1_ATO or I9505XXUFNB9_I9505AUTFNA2_AUT) Odin starts the upgrade and fails with Complete(Write) operation failed.
I have tried different cables, usb ports, odin version, with/without admin priviliges without any success.
Any ideas how i could get the phone running again?
Thx and br,
Christian

Flash the firmware in the BL/Bootloader location in Odin to resolve the "Firmware encountered an issue" warning.

Hello,
I have tried to flash my 1 file firmware with the BL button:
"There is no PIT mapping."
When I am adding a PIT file (so I am using PIT and BL) the error is "Complete(Write) operation failed." again.
Also I tried to extract the Bootloader from my 1 file firmware but i am not sure which file i should use (the tutorials are all referring to sboot.img). My firmware contains only
aboot.mbn
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
tz.mbn
Any ideas?
Thx and br,
Christian

Take your phone in for service. It sounds like you have a hardware issue, especially if the PIT file doesn't work.

I have tried to flash with it with heimdall and it looked better than with odin:
J:\stefan\stefan\I9505XXUHOJ2_I9505ATOHOJ1_ATO\entpackt>heimdall flash --APNHLOS
NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --HIDDEN hidden.img.ext4 --MDM m
odem.bin --RECOVERY recovery.img --RPM rpm.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn -
-SYSTEM system.img.ext4 --TZ tz.mbn --CACHE cache.img.ext4
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.
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading ABOOT
100%
ABOOT upload successful
Uploading BOOT
100%
BOOT upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading MDM
100%
MDM upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL2
100%
SBL2 upload successful
Uploading SBL3
100%
SBL3 upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading TZ
100%
TZ upload successful
Uploading CACHE
100%
CACHE upload successful
Ending session...
Rebooting device...
Releasing device interface...
Now it hangs at the Samsung Galaxy S4 boot logo or shuts down immediately after the logo flashes up.
br,
Christian

@maschi86
Again, like @Strephon Alkhalikoi said, hardware issue.
Sent from my GT-I9500

krasCGQ said:
@maschi86
Again, like @Strephon Alkhalikoi said, hardware issue.
Sent from my GT-I9500
Click to expand...
Click to collapse
It's so hard to accept .
Thank you guys.
br, Chris

SM-910V Soft Bricked!

Hey guys, I have the 910v I tried to manually update with Odin to 5.1.1. This isnt rooted or unlocked. Odin failed with the following error on my phone:
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
I have tried the VZW Software repair with no luck, as well as PIT file. Please help me get this thing working again! It just boots to a screen saying Software update failed and to run repair software on computer.

greg_gorrell said:
Hey guys, I have the 910v I tried to manually update with Odin to 5.1.1. This isnt rooted or unlocked. Odin failed with the following error on my phone:
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
I have tried the VZW Software repair with no luck, as well as PIT file. Please help me get this thing working again! It just boots to a screen saying Software update failed and to run repair software on computer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/debrick-procedure-t3370661

Thanks for the reply. I wish I would have saw that earlier. I ended up fixing it by re-flashing the PIT file.

Note 4 - Not able to flash system

So, I purchased a damaged Note 4 and took the motherboard and put it in a Note 4 with broken motherboard. When booting up the phone the first time there was only TWRP and no system so I tried flashing it with original firmware but it failed. After this I've tried downloading ROMs and flashing through TWRP but it did not work. Recently I tried to follow this guide:
https://forum.xda-developers.com/no...ebrick-img-t3488114/post69489251#post69489251
To reinstall the firmware on the phone and I've managed to flash boot, recovery and PIT(different flash) but it fails every time when flashing system. On the phone I had error message:
[9] eMMC write fail: SYSTEM
ODIN : flash write failure
and in Odin it said:
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
I've tried several times, changed the cable, different USB-ports, re-installing drivers, tried Odin 3.07 and 3.09 but get the same error every time. Also tried emergency reset through Smart Switch but it didn't worked either.
Now I've tried to install TWRP and if I try to boot into it I get directly to Download Mode and the to text says:
Could not do normal boot.
ddi: mmc_read failed
I have tried eveything I can think of and have had no success so far. Anybody who gan give some pointers on how to approach this? Or could it be hardware fault and I should just scrap the device? It's the European version, SM-N910F.
Thanks in advance!
Edit: If somebody gives me the solution that helps me get the phone working I can donate $25 through PayPal as thanks for the help

Ahh, the infamous eMMC memory error. It sometimes appears when flashing TWRP and a custom rom, but then never appears when flashing a stock rom. However, if it appears when flashing stock, then I'm sorry to say but it's a fatal hardware error: your memory is on its way out. Your only solution is to either replace the board or get a new device.

As the dude above implies. eMMC is destroyed. Note 4 and galaxy s3 had these problems... it's hardware based unfortunately...
Sent from my SM-G955F using Tapatalk

SGH-M919: No PIT Partition, Unable to boot to recovery. pls Help

Hello All,
My Device is S4 SGH M919(T-Mobile USA), Not Rooted and have been running on Lineage OS 17.1 + TWRP recovery for several months until recently when the phone started to randomly shut off mic or reboot or crash often. nandroid backup used to be my savior. In an attempt to resolve the issue, I tried to reformat the phone, install different Lineage OS versions 17.1 and 18.1 which didn't improve my situation. I then switched to Lineage recovery(which I now regret was a bad move!) which not only improvised my situation but I lost ability to perform nandroid backups since then. I have been trying to revert to TWRP recovery but am facing the several issues which are listed below. My phone is very unstable now; it boots sometimes, crashes often and most times it gets stuck trying to enter recovery. i am able to get into download mode.
Issues:
Missing/Corrupted PIT Partition
Unable to boot to Recovery
Frequent crash
Troubleshooting Attempts Performed:
Flash PIT partition file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401).​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 0 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash stock android via ODIN with/without PIT partition file
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2616 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash TWRP recovery using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Get PIT for mapping..​<ID:0/003>​<ID:0/003> There is no PIT partition.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash TWRP recovery + PIT file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1303)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Checking PIT Partition using Heimdall
heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
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:
Donate | Glass Echidna
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 receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Things already verified
Connecting to PC USB Port with original quality USB cable; Tried changing USB cable and the port
Installed required samsung USB drivers
tried with multiple ODIN versions which all used to work in the past
How to recover from here?
May be I am not using the correct PIT file? I tried and couldn't find many so far.
Assuming there is no physical damage to the board inside, what additional steps I could try to get back to recovery mode? I look forward for your expert suggestion/next steps here.
Thank You!

Tried taking this to a Samsung service center but as expected they denied looking into this citing the phone is too old, is no longer being supported and better buy a new phone.
I am still wondering if I can revive this phone so that I can use this to continue experimenting with custom ROM.. Any options still worth trying to revive this phone?