Develop Bugs

how can I fix this partition problem?

here are the snapshots. The first two are when I try to flash the stock GB rom. The other two are when I try to flash the stock ICS. The next one is when I try to flash the ICS all-in-one tool...
Nothing... I wanted to Re-partition my NAND. (I think is the last thing to do before to say it is a hardware issue).
Someone here in the forum post his .pit (http://forum.xda-developers.com/attachment.php?attachmentid=1557554&d=1355324369), but it can get it work either. The last picture is the error the odin gives me when i try to re-partition.

I don't really know, but I would try finding an Odin image with a separate known working PIT file.
Edit: Never mind, I see you are already trying that in another thread.

weird..
oldnoob said:
I don't really know, but I would try finding an Odin image with a separate known working PIT file.
Click to expand...
Click to collapse
I'm not finding it... I even have a friend who has the z3x box, and they only provide the one package md5 to flash.
I've been asking here in the forum, but just one person gave me a pit file, unfortunately it doesn't work for me.
I've been google it for about 4 days now. =(

for what it's worth, have you tried flashing with a different usb cable? maybe there is a bad connection.
also is kies installed on your pc? if so uninstall it. there may be conflicts with drivers. how did you get partition errors? you didn't have the box checked in odin that repartitions the device?
if all that is ok one last thing to make sure of that its not a problem in your pc. try using another pc, maybe a friends or neighbors. windows pc's are known to pick up bugs and malware undetectable by virus scanners which could have messed with drivers and other processes in the software. one of the reasons I stick to Linux, preferably ubuntu while when needed I run a virtual windows machine!

still with errors...
dbrannon79 said:
for what it's worth, have you tried flashing with a different usb cable? maybe there is a bad connection.
also is kies installed on your pc? if so uninstall it. there may be conflicts with drivers. how did you get partition errors? you didn't have the box checked in odin that repartitions the device?
if all that is ok one last thing to make sure of that its not a problem in your pc. try using another pc, maybe a friends or neighbors. windows pc's are known to pick up bugs and malware undetectable by virus scanners which could have messed with drivers and other processes in the software. one of the reasons I stick to Linux, preferably ubuntu while when needed I run a virtual windows machine!
Click to expand...
Click to collapse
I use ubuntu... i installed the heimdall 1.4... but the pit file still gives me error... is really weird...
I've tried to use the nvflash, but I don't know if I'm making something wrong or it just doesn't work... the heimdall gives me "usb write failed", and then I have to disconect the cellphone and take the battery out in order to try again...
you can check the pictures...

Litatus said:
I use ubuntu... i installed the heimdall 1.4... but the pit file still gives me error... is really weird...
I've tried to use the nvflash, but I don't know if I'm making something wrong or it just doesn't work... the heimdall gives me "usb write failed", and then I have to disconect the cellphone and take the battery out in order to try again...
you can check the pictures...
Click to expand...
Click to collapse
I don't think heimdall is compatible with our glides! Make a vm with Windows xp and install Odin!
Sent from my SGH-I927 using Tapatalk 2

I have tried to use Linux and my glide was never able to talk to my computer, I use debian and opensuse, so I had to reinstall over opensuse, so it works now with windows 7.

odin 3.07
well.. I've downloaded the 3.07 version of the odin... I saw in a snapshot that it had the box for "ERASE NAND ALL"...
well, I checked that box, the odin started to flash, but it got stuck a few seconds after the start...
Somehow it seems it did something, now I am able to flash any rom, I mean that the odin finishes the flashing process without any error, BUT....
But still stuck in the samsung logo... =(

Litatus said:
well.. I've downloaded the 3.07 version of the odin... I saw in a snapshot that it had the box for "ERASE NAND ALL"...
well, I checked that box, the odin started to flash, but it got stuck a few seconds after the start...
Somehow it seems it did something, now I am able to flash any rom, I mean that the odin finishes the flashing process without any error, BUT....
But still stuck in the samsung logo... =(
Click to expand...
Click to collapse
now that you have odin working, try flashing the official UCLJ3 update that contains the bootloader. I posted a guide for updating that. if not go back to gb and try the official gb update! most of the roms here don't include the bootloader and some don't have the modem or kernels! can you flash CWM recovery and boot it? if so, you might try booting recovery and wipe data, cache and format /system. then try one of the official updates! if none of that works, your best bet would be to hit Dman3285 up with a pm, maybe with a small donation he could get your phone going again! he's one of our best devs here.
Hope this helps.
Thanks

Waitasecond... Ubuntu...
PLEASE tell me you're not running Odin in a VM. PLEASE PLEASE PLEASE.
Strike what I had here before. Now that Odin is working, flash the PIT *first*. Make sure it's an untouched PIT dumped from a working Cap Glide. (If you need one, walk me through it and I'll dump mine.) Then do the UCLG9 oneclick (not UCLJ or UCLH). If it fails, do a battery-pull reset and try again. That *should* get you back to a functional device, and you SHOULD at that point be safe to flash UCLH or CM10/PACman.
And DON'T use Wine or a VM for Odin. It NEEDS a real Windows machine. I almost bricked my Glide trying to use a VM.

no VM...
roothorick said:
Waitasecond... Ubuntu...
PLEASE tell me you're not running Odin in a VM. PLEASE PLEASE PLEASE.
Strike what I had here before. Now that Odin is working, flash the PIT *first*. Make sure it's an untouched PIT dumped from a working Cap Glide. (If you need one, walk me through it and I'll dump mine.) Then do the UCLG9 oneclick (not UCLJ or UCLH). If it fails, do a battery-pull reset and try again. That *should* get you back to a functional device, and you SHOULD at that point be safe to flash UCLH or CM10/PACman.
And DON'T use Wine or a VM for Odin. It NEEDS a real Windows machine. I almost bricked my Glide trying to use a VM.
Click to expand...
Click to collapse
No, I have different partitions for Ubuntu and Windows 7... I'm running Odin on Windows 7...
About the PIT. I have two pit files from two members of the forum... Both of them gives me error. Check this picture: http://forum.xda-developers.com/attachment.php?attachmentid=1558361&d=1355347858
That's the error I get.
Please, dump yours and I will try that one... Both pits gives me the same error when I flash any of them...
To dump your pit, you should be on linux, download the heimdal 1.4 RC from here: https://github.com/Benjamin-Dobell/Heimdall/archive/master.zip. The 1.4 is only available for linux at the moment and It seems that previous versions doesn't supports the Samsung Glide.
Here you have the compilation procedure: https://github.com/Benjamin-Dobell/Heimdall/tree/master/Linux.
After that, you need to put your phone into download mode, and then run the following command in the terminal:
Code:
heimdall-frontend
This will run the graphic mode of the heimdall. Go to UTILITIES complete the pit's file name and dump it.
Hope you make it.

Shooting in the dark here...
You do have "Re-Partition" checked when you do the PIT, right?
Maybe if they were dumped with heimdall, you should try writing them with heimdall. Who knows, might be some file format shenanigans.
Can you flash the CWMR zip with Odin? It might get you recovery back, if nothing else, and then we could do some more advanced poking or dd'ing via ADB.

yes..
roothorick said:
Shooting in the dark here...
You do have "Re-Partition" checked when you do the PIT, right?
Maybe if they were dumped with heimdall, you should try writing them with heimdall. Who knows, might be some file format shenanigans.
Can you flash the CWMR zip with Odin? It might get you recovery back, if nothing else, and then we could do some more advanced poking or dd'ing via ADB.
Click to expand...
Click to collapse
I do have checked "Re-partition" and I get "FAILED" in Odin, and this error in the Glide's screen: http://forum.xda-developers.com/attachment.php?attachmentid=1558361&d=1355347858
When I try to run heimdall to re-partition and flash the recovery at the same time, I do this command:
Code:
heimdall flash --repartition --pit sghi927-orig.pit --SOS SOS.img
Here I get a weird error. It says something like "not such partition named PIT"... It seems like it takes the parameter "--pit" as a partition name. If I try just to re-partition, I get the same error. I don't know if this is a software error or I am the one who is doing something wrong.
I can flash through Odin and heimdall. Both finishes, but I don't know if they do something or not, because nothing changes, I just get the samsung logo, and no recovery.
The same with the CWMR with Odin, It goes through all the process, but nothing.
What do you mean with "poking"?
How can I get connected via ADB?

You can't get into CWMR so it doesn't matter.
Give the UCLG9 oneclick a spin, who knows, it might work.
Though, I'm starting to think that your download mode stuff is itself corrupt. You're probably gonna have to get nvflash working. Did you try that strace thing I mentioned in the other thread?

me too...
roothorick said:
You can't get into CWMR so it doesn't matter.
Give the UCLG9 oneclick a spin, who knows, it might work.
Though, I'm starting to think that your download mode stuff is itself corrupt. You're probably gonna have to get nvflash working. Did you try that strace thing I mentioned in the other thread?
Click to expand...
Click to collapse
I think that my download mode could be corrupted too.
I tried to use the nvflash, but everytime I tried to run the ./flash with any option in the terminal, I get "USB Write failed", and then I have to reset the phone taking out the battery. Maybe I'm doing something wrong, but I don't have any tutorial or something to know exactly how to use, because in another thread I've read that the nvflash could be locked, and you need to do something extra to bypass that.
What did you tell me in other thread? What do you mean with "strace"?
Any ideas?

Litatus said:
I think that my download mode could be corrupted too.
I tried to use the nvflash, but everytime I tried to run the ./flash with any option in the terminal, I get "USB Write failed", and then I have to reset the phone taking out the battery. Maybe I'm doing something wrong, but I don't have any tutorial or something to know exactly how to use, because in another thread I've read that the nvflash could be locked, and you need to do something extra to bypass that.
What did you tell me in other thread? What do you mean with "strace"?
Any ideas?
Click to expand...
Click to collapse
Literally just
Code:
strace -o nvflash-strace.txt {nvflash command}
With any luck it'll be a misconfiguration on your computer.

results..
roothorick said:
Literally just
Code:
strace -o nvflash-strace.txt {nvflash command}
With any luck it'll be a misconfiguration on your computer.
Click to expand...
Click to collapse
Well, I did you told me to.
Attached you will find the file. I get this in the screen:
Code:
[email protected]:/home/litatus/nvflash# strace -o nvflash-strace.txt ./nvflash --getpartitiontable pit.txt
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
[email protected]:/home/litatus/nvflash#

Litatus said:
Well, I did you told me to.
Attached you will find the file. I get this in the screen:
Code:
[email protected]:/home/litatus/nvflash# strace -o nvflash-strace.txt ./nvflash --getpartitiontable pit.txt
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
[email protected]:/home/litatus/nvflash#
Click to expand...
Click to collapse
The strace is a bit weird, apparently libusb doesn't strace well. But this is the only problem I could see:
Code:
ioctl(5, UI_DEV_DESTROY or USBDEVFS_BULK or USBDEVFS_BULK32, 0xbfbf1bbc) = -1 ENODEV (No such device)
Sounds like nvflash can't actually see your phone. Do you get the same error if the phone is not connected?
I might play around with nvflash myself if you can't figure it out.

I was screwing around with nvflash and it doesn't work on my (fully functional) device, and I KNOW my environment is sane. I think Samsung locked it with their own SBK, which odds are we will never figure out.
I've got one last shot in the dark for you though, which is why I'm-a-bumping. But first I need to double-check something
Run this:
Code:
heimdall print-pit
And post the output here.

Rooting JB OTA from OS X (no flash counter)

The short story (links explain each step) of rooting your OTA updated JellyBean d2tmo from OS X (Mountain Lion in my case).
If you've installed Kies for Mac, you need to clean up
Install heimdall 1.4 (probably have to build from source)
You can download a binary as well.-0
Download root66_TMO_T999UVDLJA ROM (in my case)
Unpack the downloaded file. It's in 7z format. You can download Unarchiver for OS X
Get adb (platform tools addition to android sdk), and make sure it is in $PATH
Run the commands below after connecting to mac
The heimdall command to run:
Make sure your computer can see your phone:
Code:
adb devices
Code:
adb-kill-server
Flash the rooted image:
Code:
heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Finally, to install CWM Recovery, try id_twin's method (worked for me). A note on this: after installing the ROM Manager app from Play Store, the app doesn't realize that CWM Recovery is installed, so it wants to flash it again. I happened to let it -- but that upped the flash counter on the phone. I've resolved it using Triangle Away.

Does this work for jellybean?
Sent from my SGH-T999 using xda app-developers app

xxqbnxx said:
Does this work for jellybean?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
According to the topic of the thread, this is specifically for Jellybean.

Not sure how to build heimdall can someone be of help please?
Sent from my SGH-T999 using xda app-developers app

xxqbnxx said:
Not sure how to build heimdall can someone be of help please?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Are you on OS X? Which version, if so?

OS X 10.6.8
Sent from my SGH-T999 using xda app-developers app

I wound up downloading a 1.4 binary for OSX, which I found on wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd . Please try that and let me know how it goes (it worked for me (TM)).
PS The outside link restriction, while understandable, is a bit silly.
xxqbnxx said:
OS X 10.6.8
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse

alecsharp said:
I wound up downloading a 1.4 binary for OSX, which I found on wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd . Please try that and let me know how it goes (it worked for me (TM)).
PS The outside link restriction, while understandable, is a bit silly.
Click to expand...
Click to collapse
Hey thanks for all your help man. I went and tired to build heimdall but i need xcode? do i ? i tired installing xcode took 3 hours to download and then i went to install it and it was going to take 4 hours to install. i thought that was to much and i might be doing something wrong. Sorry but as you can tell i am a Noob on this here. What am i doing wrong ?

xxqbnxx said:
Hey thanks for all your help man. I went and tired to build heimdall but i need xcode? do i ? i tired installing xcode took 3 hours to download and then i went to install it and it was going to take 4 hours to install. i thought that was to much and i might be doing something wrong. Sorry but as you can tell i am a Noob on this here. What am i doing wrong ?
Click to expand...
Click to collapse
Hi! If you download heimdall from that link I posted into the cyanogen wiki, you don't need to build/compile it. That download is precompiled, so all you have to do is the following:
Go to wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd <--- replace DOT with a . of course -- heimdall is independent of the type of phone you have, so don't worry that that page is for Galaxy S.
Download the heimdall 1.4rc1 zip file for OSX on that page. <-- Look for "
Code:
Mac OS X:
Heimdall Suite 1.4RC1 Command-line Binary: download
on that page.
Unpack the downloaded zip file, to find two files.
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
then you can just run heimdall (no front-end, just the command line tool) <-- see my original post up there for exactly how to do that.

OK thanks I'm going to have to wait for Monday to try this
Sent from my SGH-T999 using xda app-developers app

ok so after some work arounds i think i got it all set up. heimdall seems to be running on terminal. How safe is this ?

xxqbnxx said:
ok so after some work arounds i think i got it all set up. heimdall seems to be running on terminal. How safe is this ?
Click to expand...
Click to collapse
Well, considering what heimdall does, it's an inherently risky venture whether or not you have a GUI on it. The GUI lets you limit the amount of damage you can potentially do, of course, whereas the CLI is not as restrictive.
As far as those commands: I've run them on a couple of phones to successful ends. YMMV, of course.

im stuck i donwload the heimdall and the md5 file
but im stuck here
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
i dont have those folders
maybe im over looking this but can someone write a simpler tutorial?
no pun intended! maybe its just me, ive been googling how to root my s3 on a mac for so long!

Did you try this from the command line or Finder? If in Finder, did you try searching for those directory names?
beto0216 said:
im stuck i donwload the heimdall and the md5 file
but im stuck here
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
i dont have those folders
maybe im over looking this but can someone write a simpler tutorial?
no pun intended! maybe its just me, ive been googling how to root my s3 on a mac for so long!
Click to expand...
Click to collapse

OK... I had problems then I fixed them and then I found some more problems.
Here is what I receive:
Code:
$ heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Heimdall v1.4 RC1
Copyright (c) 2010-2012, 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...
ERROR: Claiming interface failed!
I didn't have any Kies kext's loaded as this is what I get:
Code:
$ kextstat | grep -v apple
Index Refs Address Size Wired Name (Version) <Linked Against>
126 2 0xffffff7f81e95000 0x36000 0x36000 org.virtualbox.kext.VBoxDrv (4.1.18) <7 5 4 3 1>
128 0 0xffffff7f81ed3000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (4.1.18) <126 7 5 4 3 1>
129 0 0xffffff7f81ed8000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (4.1.18) <126 5 4 1>
My process:
1. Phone -> Download Mode
2. Open Terminal
3. CD to the folder with all of the system files to be flashed
4. Run, verbatim, exactly what you said to run in OP
Any ideas?

Hi, basically that interface is busy and occupied by another process. Did you try unloading the Kies kexts anyway?
jhlax95 said:
OK... I had problems then I fixed them and then I found some more problems.
Here is what I receive:
Code:
$ heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Heimdall v1.4 RC1
Copyright (c) 2010-2012, 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...
ERROR: Claiming interface failed!
I didn't have any Kies kext's loaded as this is what I get:
Code:
$ kextstat | grep -v apple
Index Refs Address Size Wired Name (Version) <Linked Against>
126 2 0xffffff7f81e95000 0x36000 0x36000 org.virtualbox.kext.VBoxDrv (4.1.18) <7 5 4 3 1>
128 0 0xffffff7f81ed3000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (4.1.18) <126 7 5 4 3 1>
129 0 0xffffff7f81ed8000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (4.1.18) <126 5 4 1>
My process:
1. Phone -> Download Mode
2. Open Terminal
3. CD to the folder with all of the system files to be flashed
4. Run, verbatim, exactly what you said to run in OP
Any ideas?
Click to expand...
Click to collapse

alecsharp said:
Did you try this from the command line or Finder? If in Finder, did you try searching for those directory names?
Click to expand...
Click to collapse
I'm having the same problem.... i cant find any of those folders, and nothing comes up searching for each individual one in the finder. I then tried to type in the adress to the command line and it said directory could not be found. What am i missing here?

OSX Developer tools
fred8785 said:
I'm having the same problem.... i cant find any of those folders, and nothing comes up searching for each individual one in the finder. I then tried to type in the adress to the command line and it said directory could not be found. What am i missing here?
Click to expand...
Click to collapse
Do you have XCode installed?

alecsharp said:
Do you have XCode installed?
Click to expand...
Click to collapse
i do.....

fred8785 said:
i do.....
Click to expand...
Click to collapse
Thanks for verifying. Do you use homebrew at all? If not, can you install it and then run:
Code:
brew install libusb
That should create /usr/local/bin and /usr/local/lib directories. Use /usr/local/lib instead of /opt/local/lib at that point.

Root through osx help

Hi I just picked up a T-Mobile galaxy s4 and I've been trying to root it through osx. I've only rooted my phones through windows 7 so if anyone can help me, I would appreciate it. We can do it through team viewer if you want.
Thanks
Sent from my HTC One using Tapatalk 2

Optimusg2x said:
Hi I just picked up a T-Mobile galaxy s4 and I've been trying to root it through osx. I've only rooted my phones through windows 7 so if anyone can help me, I would appreciate it. We can do it through team viewer if you want.
Thanks
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Search heimdall.

KillaHurtz said:
Search heimdall.
Click to expand...
Click to collapse
I tried that but it only gives me an error and all of the fixes won't work but thanks.
Sent from my HTC One using Tapatalk 2

To try and help, Optimusg2x is right. On OS X, the only easy way I've found is to use Heimdall 1.4, which is the Odin equivalent on OS X. I rooted my S4 near its release date using Heimdall and by following ChainFire's CF-Auto-Root instructions. I'd like to disclose that I did this a very long time ago and I'm telling you this from memory because I'd like to help you, so anyone else that sees something wrong with my instructions, please correct me.
First download the package from his thread, and unzip it so you get:
Code:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 <-- remove the .md5 extension
Odin3-v1.85.exe
Odin3.ini
Remove the .md5 extension to make it a .tar file and extract the files from that, which should be:
Code:
cache.img.ext4
recovery.img
These are the files that you'll be using Heimdall to flash. There is a new version of Heimdall that came out recently, v1.4.0, in June, however when I rooted I used a release client v1.4rc1, which I should have uploaded in this post. Download and extract that, or use the official v1.4.0 (if you're running Mountain Lion) I only have instructions for the way I did it which was to use the command line to root.
At this point, put "heimdall", cache.img.ext4, recovery.img in a location you know how to get to, such as your desktop. Then place your phone into download mode
Open terminal on your mac
go to where you extracted the HEIMDALL contents, so say "cd ~/Desktop/" or wherever you extracted it to
To make sure you're in the right directory say "ls" and see if "heimdall gets listed"
if so, say "sudo ./heimdall flash --recovery ~/Desktop/recovery.img --cache ~/Desktop/cache.img.ext4" (Saying sudo may be unnecessary, but its a good precaution)
Wait a bit and let your phone reboot and you should now be rooted!

[Q] Unable to flash ClockworkMod Recovery using Heimdall

Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)

yogneo said:
Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)
Click to expand...
Click to collapse
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.

DMJoh said:
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.
Click to expand...
Click to collapse
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers

yogneo said:
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers
Click to expand...
Click to collapse
Baffin.pit wont be a problem.
Make sure you are doing the correct procedure. I am not that good in the process, so you should research a bit in this.
You can Get pit from here. But I dont think that its the problem of the pit u use.
By the way from where you got the IMG file?

got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557

yogneo said:
got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557
Click to expand...
Click to collapse
Are you using the frontend Heimdall or by executing commands in Terminal.
If you are using terminal try the frontend app too, i guess u are well aware of this.
And its too hard for me to get my device detected by Ubuntu, and so i prefered Odin later.
As you said it wont go further can you post the log messages in Heimdall window

I'm having problems installing LineageOS using Heimdall on my Galaxy S7

I've been attempting to install LineageOS onto my (Exynos) Galaxy S7 for a while now with absolutely no luck. I followed the LineageOS guide for my phone (can't link things yet, sorry) step by step, and have consistently not been able to get past this command:
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-herolte.img --no-reboot
On my phone, it displays what looks to be the very start of a white progress bar at the bottom. It never goes past this. The command exits saying the following:
Code:
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...
From what I've read online, Heimdall not working is a fairly common problem all-around. Something called Odin was rumored to work. The problem is, it was a Windows app, and I don't have any access to a Windows computer. I attempted to use it with WINE, but it wouldn't recognize my phone at all (and I had the right drivers, too).
Things I have tried:
* Running the heimdall command as sudo
* Checking my file integrity - I checked every file's MD5 / SHA256 hashes
* lsusb says that my phone is there and in download mode
* Bootloader's unlocked, USB debugging enabled
* Neither fastboot nor ADB recognize my device in download mode
I'm running Manjaro, but have access to a Mac if needed. Thanks for any help.
EDIT: Some people have said that Heimdall is always problematic with Samsungs and recommended using Odin.

Heimdall is outdated. There is a newer version for self compilers in github I think.
The version in Debian repo failed with my S5 at pit file downloading.

kurtn said:
Heimdall is outdated. There is a newer version for self compilers in github I think.
The version in Debian repo failed with my S5 at pit file downloading.
Click to expand...
Click to collapse
Do you have a link? I couldn't find it.

kyiami said:
Do you have a link? I couldn't find it.
Click to expand...
Click to collapse
https://gitlab.com/BenjaminDobell/Heimdall

The path of lest resistance
kyiami said:
I've been attempting to install LineageOS onto my (Exynos) Galaxy S7 for a while now with absolutely no luck. I followed the LineageOS guide for my phone (can't link things yet, sorry) step by step, and have consistently not been able to get past this command:
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-herolte.img --no-reboot
On my phone, it displays what looks to be the very start of a white progress bar at the bottom. It never goes past this. The command exits saying the following:
Code:
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...
From what I've read online, Heimdall not working is a fairly common problem all-around. Something called Odin was rumored to work. The problem is, it was a Windows app, and I don't have any access to a Windows computer. I attempted to use it with WINE, but it wouldn't recognize my phone at all (and I had the right drivers, too).
Things I have tried:
* Running the heimdall command as sudo
* Checking my file integrity - I checked every file's MD5 / SHA256 hashes
* lsusb says that my phone is there and in download mode
* Bootloader's unlocked, USB debugging enabled
* Neither fastboot nor ADB recognize my device in download mode
I'm running Manjaro, but have access to a Mac if needed. Thanks for any help.
EDIT: Some people have said that Heimdall is always problematic with Samsungs and recommended using Odin.
Click to expand...
Click to collapse
I am going to risk making the assumption that you know SOMEONE (anyone) with a Windows PC who can grant you access to it for the not more than the (hard to believe more than) ten to fifteen minutes it will take you to install Odin on it, flash the blasted thing, and be done with it. I realize you need to set foot into the territory of the evil Windows empire to do this, but Odin and the rest of the Ancient Norse Gods shall forgive you, I promise. It is so preposterously easy to do this with Odin that even a simple mind like mine can grasp it easily and do it without problems. At least I had none, and hopefully you shall have a similar experience (but as with all things out here, no guarantees). If it fails, it suggests a hardware problem to me, because this is about as straightforward as it gets. Just DO remember to turn OFF the automatic reboot in Odin because I believe THAT is what will trip KNOX on the device on the way out. Of course, with a rooted device running LOS, tripping KNOX is a somewhat less important consideration. GOOD LUCK

nezlek said:
I am going to risk making the assumption that you know SOMEONE (anyone) with a Windows PC who can grant you access to it for the not more than the (hard to believe more than) ten to fifteen minutes it will take you to install Odin on it, flash the blasted thing, and be done with it. I realize you need to set foot into the territory of the evil Windows empire to do this, but Odin and the rest of the Ancient Norse Gods shall forgive you, I promise. It is so preposterously easy to do this with Odin that even a simple mind like mine can grasp it easily and do it without problems. At least I had none, and hopefully you shall have a similar experience (but as with all things out here, no guarantees). If it fails, it suggests a hardware problem to me, because this is about as straightforward as it gets. Just DO remember to turn OFF the automatic reboot in Odin because I believe THAT is what will trip KNOX on the device on the way out. Of course, with a rooted device running LOS, tripping KNOX is a somewhat less important consideration. GOOD LUCK
Click to expand...
Click to collapse
Yeah, I've found a bunch of stuff saying that Heimdall just doesn't work on Samsung phones. It's just a hassle to get access to a Windows computer, and neither WINE nor gnome-boxes work (WINE doesn't have access to USB ports). I'll try that.

I had same problem on my N910C. Try this, i installed with this way.