Database Users

Trying to fix Vibrant with Heimdall... could REALLY use some help, tried everything.

So I was trying to flash the ICS alpha and it cut short and went to a bootloop and would not go into recovery via button presses or adb commands.
Here's what I did...
- Put phone into download only mode and with s1_odin_20100512 pit and T959UVJFD.tar tried to flash with Odin. It repeatedly kept getting stuck on different parts of the flash, so I gave up and tried Heimdall.
- Now with Heimdall, I use the same packages and get a firmware.xml error. For the life of my I can't find a Heimdall package for Vibrant back to stock, nor do I even know how any of that works...
Would really appreciate any help I can get trying to get this phone back! It gets to download mode no problem each time... is there hope?

If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.

amburator said:
If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.
Click to expand...
Click to collapse
could you be super duper helpful and provide me a download for flashing kernel with CWM via heimdall? no luck so far

I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.

amburator said:
I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.
Click to expand...
Click to collapse
I'm using Heimdall 1.3. I've extracted the zImage and packed it into a .tar and loaded it into Heimdall but I get a firmware.xml missing error... any ideas?
Thanks so much for your help.
EDIT: Nevermind, figured out how to do it. Now I'm getting a ERROR: Failed to received response. Searching google tells me I should install libusb drivers, gonna try that.

Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.

amburator said:
Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.
Click to expand...
Click to collapse
First off, thank you so much for your help. This is my first time using Heimdall, just got done finishing the README.
Here's where I'm at... I figured out what you just said a few minutes before you sent it, haha.
Oh, important side note.. I'm on a MAC. I think I'm experiencing a driver issue right now, given this:
-------------------------------------------------------
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:6601
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
ERROR: libusb error 1032320 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
-------------------------------------------------------
Thoughts? I reinstalled Heimdall and went to customize and tried just the libusb package. I'm going to restart and try diff USB port now.

Fuuuuuck yeah, I got it. Thanks SO much for your help. How can I ever repay you?
EDIT: To be helpful to any googlers in the future - it was fixed by reinstalling libusb from the Heimdall 1.3 installer, restarting, and repeatedly trying alternate usb ports and putting it into download mode over and over again.

Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.

amburator said:
Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.
Click to expand...
Click to collapse
I found a package on the forms but was getting a firmware.xml error. Manually downloaded/created PIT file from phone, then extracted package, and loaded up each component (modem, param, kernel, etc) indivudally and flashed without a hitch. Huzzah!

Allright!
Congrats!

Heimdall Galaxy S4 I337 Full Recovery

I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
===================WINDOWS VERSION, by popular request================================
Instructions here were done on a Windows 7 PC
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your PC, open up a Command Prompt (Click the "start" button, and type in cmd and hit enter), and navigate to the location you extracted the tar.md5 files to
8) In the command prompt, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware

Thanks for taking the time to do this. Provides an Odin - like option for Linux users like myself, and of course, Mac users too.
Sent from my GT-I9505G using xda premium

I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.

Encryption Failed everytime i reboot any fix?
Deleted

Interested in any solutions you guys found for your listed issues, as I have an iMac also--

tom_callahan said:
I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
Click to expand...
Click to collapse
Im having that inaccessible /data partition and ODIN is not working for me. It flashes successfuly in ODIN, but upon boot it just hangs on the Samsung Galaxy S4 logo. When i go into the stock recovery, it shows the broken android and the cannot mount/data error. Its starting to become a real headache for me. I don't have a Mac tho, so i don't think your tool would work for me.

Monkz said:
Im having that inaccessible /data partition and ODIN is not working for me. It flashes successfuly in ODIN, but upon boot it just hangs on the Samsung Galaxy S4 logo. When i go into the stock recovery, it shows the broken android and the cannot mount/data error. Its starting to become a real headache for me. I don't have a Mac tho, so i don't think your tool would work for me.
Click to expand...
Click to collapse
Heimdall works on any platfork, mac/linux/windows...you just need java installed and your good to go, just use the command prompt instead of terminal. this was also stated in the op
You know...im surprised nobody has made a one click heimdal package yet...heimdal is so much better than odin imho
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
Heimdall works on any platfork, mac/linux/windows...you just need java installed and your good to go, just use the command prompt instead of terminal. this was also stated in the op
You know...im surprised nobody has made a one click heimdal package yet...heimdal is so much better than odin imho
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I'm going to try this when i get home then. I just want my phone to come to life again. Crossing my fingers that this will work! Things were perfect, i don't know why restoring a nandroid and updating my kernel has caused this to become such a terrible issue.

Seems to have worked. It's hung on the AT&T logo for a couple minutes though. How long after you did this did it take to boot up the first time? I'm afraid to pull the battery and screw something up.
---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------
Never mind, I rebooted to recovery and factory reset just like you said in OP and now it's booted up to the setup screen. Thanks for this man. I really needed to return to stock and didn't want to have to install Windows just to run Odin. Much appreciated!

Try doing just hidden or system, and see if those flash correctly. If they do then come back after those and flash recovery
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

housry23 said:
Seems to have worked. It's hung on the AT&T logo for a couple minutes though. How long after you did this did it take to boot up the first time? I'm afraid to pull the battery and screw something up.
---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------
Never mind, I rebooted to recovery and factory reset just like you said in OP and now it's booted up to the setup screen. Thanks for this man. I really needed to return to stock and didn't want to have to install Windows just to run Odin. Much appreciated!
Click to expand...
Click to collapse
Glad this worked for you, I was struggling to find a clear method to use heimdall to repair, which is exactly why I wanted to post help for any others.

tom_callahan said:
Glad this worked for you, I was struggling to find a clear method to use heimdall to repair, which is exactly why I wanted to post help for any others.
Click to expand...
Click to collapse
Ugh...I returned to stock so that I could trade this S4 to someone on CL for a HTC One. He had no idea what CM10.1 was and so I figured it'd be best to trade him for a stock unrooted. So, I used your instructions to return to MDL. The guy flaked. Never showed up. GRRR! I kept getting bugged about the OTA, but never took it. I figured I'd just rerun CASUAL when I wake up in the morning and root it then. Well, apparently the update ran without me pressing the continue button. I'm so angry!
I wonder if this would work to roll back? Has anyone successfully rolled back to a previous firmware using Heimdall? I'd try, but I want to be sure I won't brick or mess anything up. Anyone?

InstigatorX said:
I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.
Click to expand...
Click to collapse
well ive been trying to make a one click package for heimdall however i too am facing this error, ive narrowed it down to the system.img.ext4 anyone have any ideas whats going wrong?

I am also getting an issue when trying to flash hidden or system, both files claim that the computer cannot open them not sure what the problem is as i have redownloaded and checked the files to make sure all is well and can't seem to figure it out.

works great flashing the UCUAMDL firmware downloaded from Adam's thread, and using Heimdall 1.40 on Mac OS X 10.8.4

Is there a video on how to do this step by step? Im confused on how to execute commands. Or even better is there a way to do this in the front end/ using the gui of heimdall to get back to factory from a custom ROM?
PS using a Mac

white.noise said:
Is there a video on how to do this step by step? Im confused on how to execute commands. Or even better is there a way to do this in the front end/ using the gui of heimdall to get back to factory from a custom ROM?
PS using a Mac
Click to expand...
Click to collapse
I did this on a MacBook Pro running OS X 10.8.4, it was very simple and straightforward. PM if you need help after reading the instructions in the OP

mg2195 said:
well ive been trying to make a one click package for heimdall however i too am facing this error, ive narrowed it down to the system.img.ext4 anyone have any ideas whats going wrong?
Click to expand...
Click to collapse
I am also having this problem, but it is with the second line of commands ;modem.bin/NON-HLOS.bin/Aboot.mbn/tz.mbn.
It might be a bug with this release.
By the way I am running windows 7 64 bit.

tom_callahan said:
I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
===================WINDOWS VERSION, by popular request================================
Instructions here were done on a Windows 7 PC
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your PC, open up a Command Prompt (Click the "start" button, and type in cmd and hit enter), and navigate to the location you extracted the tar.md5 files to
8) In the command prompt, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Click to expand...
Click to collapse
i need help. heidmall can't open large files for example my system.img (2367450528 byte)
I recompile heidmail with -D_FILE_OFFSET_BITS=64
now it can open my system.img
but i got new error:
ERROR: Failed to confirm end of file transfer sequence!
I know that there is patch for this error.
do anybody have this patch?
I downloaded latest sources but still have this error
I don't have 64 bit pc to flash...
please help me
debug
[201.975789] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x8395014 has callback 0xb7763480
[201.975840] [00000c5b] libusbx: debug [bulk_transfer_cb] actual_length=1024
[201.975900] [00000c5b] libusbx: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 8
[201.975985] [00000c5b] libusbx: debug [libusb_submit_transfer] arm timerfd for timeout in 120000ms (first in line)
[201.976044] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[201.976097] [00000c5b] libusbx: debug [handle_events] poll() 3 fds with timeout in 60000ms
[201.984117] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[201.984242] [00000c5b] libusbx: debug [reap_for_handle] urb type=3 status=0 transferred=8
[201.984307] [00000c5b] libusbx: debug [handle_bulk_completion] handling completion status 0 of bulk urb 1/1
[201.984374] [00000c5b] libusbx: debug [handle_bulk_completion] last URB in transfer --> complete!
[201.984434] [00000c5b] libusbx: debug [disarm_timerfd]
[201.984480] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x8394c0c has callback 0xb7763480
[201.984539] [00000c5b] libusbx: debug [bulk_transfer_cb] actual_length=8
ERROR: Failed to unpack received packet.
SYSTEM upload successful
Ending session...

Same problem
InstigatorX said:
I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.
Click to expand...
Click to collapse
Did you ever figure this out? I am having the same exact problem. Not sure what to do next. Any help will be appreciated!

[Q] How to Root, Flash Recovery and Roms in Linux Mint 17

My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE

TowelRoot app with Sprint code " 1337 0 1 7380 4 0 " worked for me my first attempt at root. Thanks Mr. W0lf and anyone else involved. Video tutorial link below:
http://youtu.be/ZGwMs8JPBhE
I still would like to see tutorials on how to Root, Flash Recovery and Roms for Linux Mint users
Sent from my SPH-L720 using XDA Developers App

Josey Wales said:
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
Click to expand...
Click to collapse
You don't use wine or samsumg drivers when rooting from linux. Install heimdall and flash using the heimdall command line.
untar the odin package, then flash the extracted image files separately with heimdall
heimdall on linux is all I use for flashing odin packages. Note The partition names are case sensitive, and differ between phones, but this example is for gs4.
mv odinpack.tar.md5 odinpack.tar
tar -xvf odinpack.tar
extracting blah blah blah...
boot.img
recovery.img
system.img.ext4
...
eg. > heimdall flash --RECOVERY recovery.img --BOOT boot.img --SYSTEM system.img.ext4 ...etc.
here's the gs4 partition names and typical gs4 image file names for heimdall command reference:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
I use fedora, which uses yum for installation:
> sudo yum install heimdall
I think mint uses synaptic, which I'm not familiar with, so you're on your own there. You could go crazy and use synaptic to install yum, then use the above yum command. Probably a bit much.

Thanks for your input. I read through the Hemidall topic posted here but I guess I didn't read enough. I'm kind of new to Linux, still learning my way around performing commands from terminal. I'll go ahead and uninstall Samsung drivers from my home pc when I get in later and give Hemidall a shot
Sent from my SPH-L720 using XDA Developers App

Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through

Josey Wales said:
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Click to expand...
Click to collapse
You should find the tar files inside the odin rom zip files
If you're trying to be cautious, you might want to test out the heimdall functionality first by flashing say, just the cache only from one of the stock roms. If it fails halfway through, it's no biggie. Just clear cache until you get it working. Use the above flash command that contains the --CACHE partition as a reference. Just be careful not to flash boot.bin from NAE or you're done. The procedure is the same as using odin, except you unzip and untar the rom manually with linux, and flash the untar'd images with the heimdall command as above.

r0ckstar said:
You might want to test out the heimdall functionality first.
Click to expand...
Click to collapse
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here

Josey Wales said:
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Click to expand...
Click to collapse
You still have to go into the folders to access the files. you flash the files, not the folders. cd into the philz directory, look for the recovery.img or whatever name it is there, then from that directory: heimdall flash --RECOVERY <case sensitive name that's in there>, hopefully recovery.img as to be unambiguous. If you're flashing from the correct directory, you should see the file when you do ls -la command. Otherwise, you would have to add the path to the file name when flashing from a different location. You're almost there.

I tried flashing Philz Recovery in Heimdall a few times and got this error:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I tried different USB cables and the one included with my device

Josey Wales said:
I tried flashing Philz Recovery in Heimdall a few times and got this error:
I tried different USB cables and the one included with my device
Click to expand...
Click to collapse
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.

r0ckstar said:
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
Click to expand...
Click to collapse
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App

Josey Wales said:
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Click to expand...
Click to collapse
Usually, this type of error means that either something else in linux is already using the usb port, or there's a heimdall installation issue.
check permissions (755) on heimdall.kext if your version has it.
I don't know where mint puts it.
The simplest thing to do is try every port one by one, BUT restart the computer before each attempt. I've had to do this myself in the past. If that fails, try downgrading your heimdall installation to 1.4.0. I think that's the earliest version that still supports L720. Every flavor of linux is a bit different in this regard, and there's many variables involved here. These kinds of things are typical for linux users. It's not for everyone, only people with awesomeness. Remember, we're pioneers of sorts using heimdall/linux when everyone else is using windows. Failure is not an option (or at least the admission of failure is not an option)...

Update baseband without windows?

Hi!
I have a current CM13 and TWRP (3.0.2) with a G900fxxu (Android 5.0) baseband. Have not been able to figure out how to update to a 6.1 baseband. I tried:
- Flashing the modem with dd (over adb, running as root). Even though I can read the modem partition (/ dump it to sd card) and even chmod the device +w, dd just gives me a write error and refuses to do anything at all... Tried both with CM13 dd and with a (allegedly) fully functional busybox installed as system app.
- Using Heimdall (on bleeding edge linux, compiled and tried several current forks), but it is currently so full of bugs and fail that even If I got it running I'm not sure if I would dare to use it for anything that could (soft)brick my phone.
- Replacing the modem of a TWRP backup and "restoring" that: With TWRP < 3, it seems to work but really it doesn't do anything. With TWRP > 3, It freezes at ~95% which forced me to take out the battery (but - luckily - that did not do anything either).
- Restoring (most of) the stock rom. It refuses to do an update and tells me to use "kies" or something instead. Possibly because I did not want to restore stock recovery + unroot the device (that's not an option ATM, since I'm not totally sure if I have a way to CLEANLY get TWRP + root back on there once it's gone).
( I "confirmed" that both the partition inode and the image I was trying to flash were "probably ok" prior to all those attempts by using images from multiple sources & examining both images and the raw partition in a hexeditor. They all looked mostly the same and reassuringly firmwary :3 )
Any hints on what I should look at / try next?

xdmeh said:
Any hints on what I should look at / try next?
Click to expand...
Click to collapse
Hi xdmeh
As you already covered almost everything ...
[Release] JOdin3 CASUAL Cross Platform and Web-Based Flashing For Samsung Phones
EDIT: Seems the main site is unstable. Just to make sure you will get it the direct link to the binary is JOdin3CASUAL-r1035-dist.jar
To start it, open your terminal and:
Code:
$java -jar JOdin3CASUAL-r1035-dist.jar
Java 1.8 seems mandatory.
Please let us know your results.
Nice regards.
.

Jodin is basically a Heimdall wrapper, if one doesn't work the other likely won't as well.
Sent from my Galaxy S5 using XDA Labs

yes... while Jodin seems to takes care of some of the workarounds needed to make Heimdall work automatically, it makes the whole process a lot less transparent - looks easier but even more risky than just using Heimdall and working around all problems manually.
I'd feel much more comfortable just using dd... or simply cat. So: Does noone have an idea why that doesn't work? Or is it normal that that partition is write-protected now? Did samsung/google do some black magic here to block all write access on a low level somehow and forgot to make the node un-chmod'able or am I just doing something wrong?
Also: Couldn't find any good info on what would happen if I broke the modem partition. Is the display + HID driver on there? The usb driver? Would I still be able to get [adb/ssh/heimdall] over usb or even the display + TWRP working in recovery without a modem partition somehow so that I could fix it?

Oops, posted this in the wrong thread...
(and noone told me, so I'm guessing noone is reading this. But I'll fix it anyways. )

So, I compiled heimdall from git, used the workarounds:
Code:
# download pit first
heimdall download-pit --output ./DOWNLOADED.pit --verbose
# reboot / enter download mode again
heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin --pit DOWNLOADED.pit --no-reboot
# press buttons to enter download mode again without reboot, repeat twice
heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin --pit DOWNLOADED.pit --no-reboot
heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin --pit DOWNLOADED.pit --resume
... and it looked like it worked despite some error messages: The download mode progress bar jumped around and heimdall said (top cropped):
Code:
81%
83%
85%
87%
89%
91%
93%
95%
96%
98%
100%
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
MODEM upload successful
Uploading APNHLOS
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
0%WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
11%
23%
35%
47%
59%
71%
83%
95%
100%
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
APNHLOS upload successful
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Rebooting device...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Releasing device interface...
...but the baseband version didn't actually change.
I have no idea why this isn't working... what did I miss?

OEM unlocking doesn't show up

Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
Any solutions?

yokodos2003 said:
Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
Any solutions?
Click to expand...
Click to collapse
There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).

matteo0026 said:
There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).
Click to expand...
Click to collapse
There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.

yokodos2003 said:
There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.
Click to expand...
Click to collapse
I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.

matteo0026 said:
I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.
Click to expand...
Click to collapse
Anything for unlocking bootloader for SM-T837P?

Sunhawk01 said:
Anything for unlocking bootloader for SM-T837P?
Click to expand...
Click to collapse
It isn't the right place to ask about galaxy tab s4. Anyway, since software is made by sprint, I guess there aren't any ways to unlock thr bootloader there

Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.
I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2
"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.
lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031
Still no device shows up with fastboot.
When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.
Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
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...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.
Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.
With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.
Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.

jirido said:
Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.
I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2
"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.
lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031
Still no device shows up with fastboot.
When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.
Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
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...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.
Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.
With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.
Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.
Click to expand...
Click to collapse
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.

matteo0026 said:
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.
Click to expand...
Click to collapse
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.
And no windows in sight here... First time ever said.. SADLY !!????

jirido said:
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.
And no windows in sight here... First time ever said.. SADLY !!????
Click to expand...
Click to collapse
Then, if you don't have Windows, it's ok to use Heimdall, but you have to use it correctly. Use .img file, and if it doesn't work, rename the file to recovery.img

Yes. Just as you said. I did reinstall stock to all partitions and then flashed an older twrk to recovery after having rebooted. Then I updated it to latest. And now it works. I am a bit on the fence if I should root or not.. But Yeah.
Thanks guys.