Related
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.
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Wish I saw this earlier! Borrowed a friend's laptop just root the Note.
Good to know Heimdall 1.4 is working on it. I was hesitant to try it until it was confirmed working.
this worked perfectly ! Thanks !
Trying to Root Note 3 using this method but getting error message. I've uninstalled KIES from computer and I don't see it on the phone. Any help?
mrmarshall428 said:
Trying to Root Note 3 using this method but getting error message. I've uninstalled KIES from computer and I don't see it on the phone. Any help?
Click to expand...
Click to collapse
When you uninstalled Kies did you use the uninstall program or did you just delete it from the applications folder? I used the uninstall program I got on the KiesMac_3.0_Setup.dmg
What is the exact error you are getting?
mlpmail said:
When you uninstalled Kies did you use the uninstall program or did you just delete it from the applications folder? I used the uninstall program I got on the KiesMac_3.0_Setup.dmg
What is the exact error you are getting?
Click to expand...
Click to collapse
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Actually i deleted it from Applications putting it in trash then erase, thinking that would remove it all
---------- Post added at 03:10 AM ---------- Previous post was at 02:44 AM ----------
mrmarshall428 said:
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Actually i deleted it from Applications putting it in trash then erase, thinking that would remove it all
Click to expand...
Click to collapse
Edit: I figured it out. Thanks
mrmarshall428 said:
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Do you have any other program running that might be grabbing the phones usb connection? Parallels, virtualbox, fastboot, abd are a few things I can think of,
Try exiting any of these programs
If you have run adb since computer was rebooted try :
adb kill-server
I hope this helps, I can't think of anything else to try.
Knox
Only have a macbook as well wanting to know if this root method will mess with knox? I have read several articles about some root methods messing with the phone after rooting. can anyone confirm this?
khrizg35 said:
Only have a macbook as well wanting to know if this root method will mess with knox? I have read several articles about some root methods messing with the phone after rooting. can anyone confirm this?
Click to expand...
Click to collapse
This will trigger the knox flag disabling the knox features. There is now another way to get root that does not change the recovery partition or trip the knox flag, I have not looked into doing it, as I have already tripped my knox flag and as far as I can tell it cannot be undone.
mlpmail said:
This will trigger the knox flag disabling the knox features. There is now another way to get root that does not change the recovery partition or trip the knox flag, I have not looked into doing it, as I have already tripped my knox flag and as far as I can tell it cannot be undone.
Click to expand...
Click to collapse
So by tripping Knox we wouldn't be able to do a warranty exchange or phone cloak through t-mobile? Sorry for all the questions just wanna make sure I do this right and appreciate the help
khrizg35 said:
So by tripping Knox we wouldn't be able to do a warranty exchange or phone cloak through t-mobile? Sorry for all the questions just wanna make sure I do this right and appreciate the help
Click to expand...
Click to collapse
On another thread a user said he saw a note getting returned at tmo and they checked the system status in settings and in download mode. I'm gonna wait to flash anything until there is a way to get 100% back to stock.
mlpmail said:
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Click to expand...
Click to collapse
OH MY GOD!
i was a right panic attack because i couldnt do anything! followed your directions and BAM worked. Thank you so much! you got a paypal i can donate to?
mlpmail said:
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Click to expand...
Click to collapse
Would anyone be so kind as to walk me through this step-by-step or point me to a link that does the same? Please please please!
gilsmithii said:
Would anyone be so kind as to walk me through this step-by-step or point me to a link that does the same? Please please please!
Click to expand...
Click to collapse
Yes, I would like more help as well!!!
Worked for me too!
Worked for me too after UNINSTALLING Kies.
I deleted kies first and it returned "libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access"
Then I downloaded kies again. When it starts it offers you to uninstall.
After uninstalling everything started working.
It is qon macbook pro.
Thank you!
Please help! I'm getting this:
"heimdall flash --RECOVERY /Users/Lauren/Downloads/recovery-clockwork-6.0.4.6-hltexx.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...
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...
Does it matter if the Note 3 had the latest Lollipop based download from Samsung on it?
tmorterlaing said:
Please help! I'm getting this:
"heimdall flash --RECOVERY /Users/Lauren/Downloads/recovery-clockwork-6.0.4.6-hltexx.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...
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...
Does it matter if the Note 3 had the latest Lollipop based download from Samsung on it?
Click to expand...
Click to collapse
So picked up the phone this week and it I took the Ota by mistake. I have osx and mac only. I've tried mutiple versions of heindall only to get a similar error. I've tried multiple things found online and some xda. I simply cannot download the pit. Anyone have the pit for lollipop and any ideas on how to properly get heindall (latest mac version to play nicely)
Sent from my SM-N900T using XDA Free mobile app
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 trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
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 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...
jimmisavage said:
I'm trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
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 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...
Click to expand...
Click to collapse
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
ashyx said:
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
Click to expand...
Click to collapse
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
jimmisavage said:
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
Click to expand...
Click to collapse
Unless you can dual boot a Linux distro with W10 or download one of the Live Bootable from disk Linux distros. There's plenty about.
https://help.ubuntu.com/community/LiveCD
Finding time to try this is proving troublesome. What are the chances this will actually work (more than Odin)?
I'm just trying to work out if it's actually worth the time/hassle?
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
jimmisavage said:
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
Click to expand...
Click to collapse
Just flash the stock firmware.
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
jimmisavage said:
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
Click to expand...
Click to collapse
Don't try and use a fronted. Use the command line. There is no such thing as Heimdall Firmware as far as I'm aware.
Heimdall flashes images which can be extracted from the stock firmware.
If you search Google for Heimdall flash commands you will find the correct syntax required to flash images.
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
jimmisavage said:
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
Click to expand...
Click to collapse
That's more or less correct. You should be able to extract the image from the zip using the stock utility in Linux. Ensure md5 is changed to tar.
If not then Peazip for Linux or 7zip for Windows.
Thanks again! I'll have one more go at this tonight... if it doesn't work then it's going in the bin and I can go back to living my life
Whilst in work i decided to download the firmware again and see if i could extract the image from the zip.
I have successfully completed that. It's currently named 'T555XXS1BPL4_T555BTU1BPE2_T555XXU1BPD7_HOME.tar.md5'. Do i simply delete the .md5 on the end to leave the .tar or is there something more complicated than that? Shouldn't it be a .img or am i just being overly concerned about details?
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
jimmisavage said:
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
Click to expand...
Click to collapse
It seems you are making this more complicated than it needs to be. Admin is the root user on a Linux system.
The instructions at the link below pretty much explain what you need to do.
http://www.dudleymediagroup.com/Detail/id/installing-using-heimdall-on-with-linux-3547
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
jimmisavage said:
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Click to expand...
Click to collapse
I should think you'll be fine with 16.04 or 14.04
ashyx said:
I should think you'll be fine with 16.04 or 14.04
Click to expand...
Click to collapse
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
jimmisavage said:
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
Click to expand...
Click to collapse
From the directory where it is located try:
sudo dpkg -i ubuntu13.04-heimdall_1.4.0-0_amd64.deb
Got heimdall installed but i cannot flash anything.
Time to give up. Thanks for all the help
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.