Can't Install CWM with Heimdall

fajrero

Member
Sep 22, 2014
29
1
0
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
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...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
 

Rakuu

Senior Member
Jun 16, 2014
2,410
818
0
Houston
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
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...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
Check the github, theres some forks you can try, i have a thread about this you can check.

Sent from my SM-G900A using Tapatalk
 

fajrero

Member
Sep 22, 2014
29
1
0
Check the github, theres some forks you can try, i have a thread about this you can check.

Sent from my SM-G900A using Tapatalk
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?
 

Rakuu

Senior Member
Jun 16, 2014
2,410
818
0
Houston
Last edited:

fajrero

Member
Sep 22, 2014
29
1
0
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
 

Rakuu

Senior Member
Jun 16, 2014
2,410
818
0
Houston
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.

Sent from my SM-G900A using Tapatalk
 

fajrero

Member
Sep 22, 2014
29
1
0
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.

Sent from my SM-G900A using Tapatalk
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.

However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
 

Rakuu

Senior Member
Jun 16, 2014
2,410
818
0
Houston
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.

However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
Same as my last post, havent used it so i wouldnt know. Also if you do softbrick youll need to get heimdall working or find a windows computer, which honestly, you can beat around the bush sith apps and stuff but at the end of the day i think youll need to use heimdall or odin.

Sent from my SM-G900A using Tapatalk
 

fajrero

Member
Sep 22, 2014
29
1
0
I went through the TWRP installation with the installer from the Play store, installing the latest version of TWRP. Just as it got to the step for the actual installation, it crashed...

So, I try to reboot into recovery, and I'm greeted by these words: "RECOVERY IS NOT SEANDROID ENFORCING. Set Warranty Bit: recovery". My heart sinks, but then I see the Team Win splashscreen come up, and I'm in TWRP. I tap the Reboot button, and it boots back into Android. Everything seems to be fine, aside from the crash during installation and this mysterious error.

I'd like to install Cyanogen, but I prefer deciphering this error first. From what I've been reading, most of the people getting this error have bricked their phones. Maybe I just got lucky? What is this error, and should I worry about it?