Database Users

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)...

[SOLVED SEEING RELINK INSTEAD OF QUALCOM] HELP!! OS GONE and NO TWRP

UPDATE: SOLVED THE RELINK PROBLEM AND UNBRICKED MY PHONE
Hi can someone help..
my phone was rooted and I was trying to flash the latest OTA but I accidentally deleted the partition or something idk... so TWRP said no OS installed so I couldn't boot my phone.
And then i followed some guides around and then that turns into me cant access the TWRP anymore.
What I can do left now is get it into fastboot. Can anyone help how to get my OPT alive?
From what I've been reading I need to use 'fastboot flash update ____". is this right? but i don't have the file. or at least i think i don't. i downloaded 2.2.0 signed flashable zip but when i tried to c:adb> fastboot flash update OnePlus2Oxygen_14_OTA_011_all_1512111634.zip it said "error: cannot determine image"
All help appreciated!! I'm sorry if this problem has been asked before but I tried to search solutions myself but ended getting one problem after another so i decided to ask.. thank you.

first flash twrp
then boot into twrp
connect your phone to pc you will able to see your internal storage
copy your OS to internal storage
flash it

sudhakarstoopy said:
first flash twrp
then boot into twrp
connect your phone to pc you will able to see your internal storage
copy your OS to internal storage
flash it
Click to expand...
Click to collapse
This looks very promising but when i tried "fastboot flash recovery twrp-2.8.7.0-oneplus2.img" it "FAILED: device is locked. cannot flash images"

Did you try to unlock the boot loader again?
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
Did you try to unlock the boot loader again?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Is it the "fastboot oem unlock"? it didn't work "remote: oem unlock is disabled" is there another way?

Okay now tell me what you did after you wiped your OS unknowingly ? ..
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
Okay now tell me what you did after you wiped your OS unknowingly ? ..
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I can't remember for certain but I think I went into TWRP and tried to flash the OTA update ONLY and not the full OS version (but by now there is already "No OS installed" message on TWRP) and when it didn't work i reboot system and couldn't get into twrp anymore.

https://forums.oneplus.net/threads/...-of-oxygen-os-2-0-for-oneplus-2.378300/page-2
Check this thread ... In 2nd page that guy have fastboot image get from him and try to flash the system image from fastboot ... All the best
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
https://forums.oneplus.net/threads/...-of-oxygen-os-2-0-for-oneplus-2.378300/page-2
Check this thread ... In 2nd page that guy have fastboot image get from him and try to flash the system image from fastboot ... All the best
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thank you so much. Hopefully they see my message.
In the meantime, anyone has other fix to recommend? T_T

skarfy said:
Thank you so much. Hopefully they see my message.
In the meantime, anyone has other fix to recommend? T_T
Click to expand...
Click to collapse
With pleasure
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
With pleasure
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Apparently it's already uploaded here. Do you know how to fix it now?

http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Dont know if this could work?

skarfy said:
Apparently it's already uploaded here. Do you know how to fix it now?
Click to expand...
Click to collapse
This will work... Download every file. extract them and put it in a single folder .. Connect your mobile in a fastboot and try to flash every single file individually
Refer these commands but these are not for oxygen os just for reference
''fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img"
Sent from my ONE A2003 using Tapatalk

oediv said:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Dont know if this could work?
Click to expand...
Click to collapse
I tried this, got stuck at step 7. Hoping for a reply on the thread.
sudhakarstoopy said:
This will work... Download every file. extract them and put it in a single folder .. Connect your mobile in a fastboot and try to flash every single file individually
Refer these commands but these are not for oxygen os just for reference
''fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img"
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Does the sequence matter or I can flash in any way I can?

skarfy said:
I tried this, got stuck at step 7. Hoping for a reply on the thread.
Does the sequence matter or I can flash in any way I can?
Click to expand...
Click to collapse
What happened at Step 7?
I unbricked my phone using that same guide.

tarun123t said:
What happened at Step 7?
I unbricked my phone using that same guide.
Click to expand...
Click to collapse
"7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install."
It said "the best driver is already installed" but I still can't find my phone in "MSM8994DownloadTool.exe".

skarfy said:
"7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install."
It said "the best driver is already installed" but I still can't find my phone in "MSM8994DownloadTool.exe".
Click to expand...
Click to collapse
have you tried manually updating the driver by selecting the file from QC folder?
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Step 6. Connect your OnePlus 2 to PC with USB cable. Then open ‘Device manager’. Hold volume + and power until your PC finds a new hardware (if it doesn’t work, try hold volume+ and volume- together). Now, find the item by the name of ‘QUALCOMM-HS USB Diagnostics 9006’. That’s your OnePlus 2.
Step 7. Now right click on it, and select ‘update driver’. Select ‘browse’ button and go to and select the folder where you extracted driver file’s in step 1. Update its driver using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder). Now this will install the new drivers for your Oneplus 2.

tarun123t said:
have you tried manually updating the driver by selecting the file from QC folder?
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Step 6. Connect your OnePlus 2 to PC with USB cable. Then open ‘Device manager’. Hold volume + and power until your PC finds a new hardware (if it doesn’t work, try hold volume+ and volume- together). Now, find the item by the name of ‘QUALCOMM-HS USB Diagnostics 9006’. That’s your OnePlus 2.
Step 7. Now right click on it, and select ‘update driver’. Select ‘browse’ button and go to and select the folder where you extracted driver file’s in step 1. Update its driver using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder). Now this will install the new drivers for your Oneplus 2.
Click to expand...
Click to collapse
Is this it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then I browse here "C:\Users\skrfy\Desktop\qc" and ticked "include subfolders". Is this right?
I did that step and it said already have the best driver installed. But my phone still doesn't appear in MSM8994DownloadTool

skarfy said:
I tried this, got stuck at step 7. Hoping for a reply on the thread.
Does the sequence matter or I can flash in any way I can?
Click to expand...
Click to collapse
Sequence doesn't matter
Sent from my ONE A2003 using Tapatalk

skarfy said:
Is this it?
and then I browse here "C:\Users\skrfy\Desktop\qc" and ticked "include subfolders". Is this right?
I did that step and it said already have the best driver installed. But my phone still doesn't appear in MSM8994DownloadTool
Click to expand...
Click to collapse
That's weird. Same thing worked for me a week ago.

J320FN: stock ROM: saving home? Custom .tar.md5 or by adb?

Hi all,
Could somebody please provide me a working link to a downloadable stock ROM for SM-J320FN ?
SSN: J320FNGSMH (Hungary, T-mobile), though any english speaking J320FN ROM will do.
I got "Custom binary blocked by FRP lock" message, almost sure I disabled OEM by accident before flashing faltisal's LineageOS (which worked pretty well so I'm going to reinstall it again, as soon as I have the device restored).
------
Ok, I've finally found some working sites with stock firmwares available. However all of the .tar.md5 images are single files. No separate bootloader, AP, CP, CSC, HOME_CSC. If possible, I would try saving some pics on my home folder.
The tar contains the following:
boot.img
cache.img
hidden.img
nvitem.bin
PM_sharkl_arm7.bin
recovery.img
sboot2.bin
sboot.bin
spl.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
Can wiping home be avoided by removing some .img from this .tar? Or could you provide some description how to make a HOME_CSC version of these?
I also looked another way: if I could backup via adb, as Android recovery works, but it's in sideload mode. Commands like adb pull or adb shell result in "adb: error: connect failed: closed".
Any solutions are appreciated.
Thanks in advance.

debi.janos said:
Hi all,
Could somebody please provide me a working link to a downloadable stock ROM for SM-J320FN ?
SSN: J320FNGSMH (Hungary, T-mobile), though any english speaking J320FN ROM will do.
I got "Custom binary blocked by FRP lock" message, almost sure I disabled OEM by accident before flashing faltisal's LineageOS (which worked pretty well so I'm going to reinstall it again, as soon as I have the device restored).
------
Ok, I've finally found some working sites with stock firmwares available. However all of the .tar.md5 images are single files. No separate bootloader, AP, CP, CSC, HOME_CSC. If possible, I would try saving some pics on my home folder.
The tar contains the following:
boot.img
cache.img
hidden.img
nvitem.bin
PM_sharkl_arm7.bin
recovery.img
sboot2.bin
sboot.bin
spl.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
Can wiping home be avoided by removing some .img from this .tar? Or could you provide some description how to make a HOME_CSC version of these?
I also looked another way: if I could backup via adb, as Android recovery works, but it's in sideload mode. Commands like adb pull or adb shell result in "adb: error: connect failed: closed".
Any solutions are appreciated.
Thanks in advance.
Click to expand...
Click to collapse
The solution I recommend is to install TWRP Recovery by flashing it using a tool like ODIN (search a tutorial on google for your phone). After flashing it sucessfully reboot your phone into recovery with key combination : Hold Home + Power + Volume Down until J3 2016 logo appear then go to Wipe section and select Advanced Wipe : Select System Dalvik Data Cache and dont select Internal Storage if u dont want to wipe your personal data.
Wait until it finish wiping then go back to TWRP Menu Home then choose Install and select the sdcard (path = storage/sdcard1) then select your stock rom and wait until it finish then reboot

Heimdall flash stock rom

Hi, I want to revert at stock ROM (SM-G935F) but, I'm on MAC. JOdin doesn't work, well I can start it, connect it but saying files are corrupt. Now, since I don't have a Win machine, I want to use Heimdall to flash stock ROM.
I unpacked the files but, from what I've read over the internet, more files would be required....
Atm, I can flash only these:
Code:
heimdall flash --CM cm.bin --PARAM param.bin --BOOTLOADER sboot.bin --RADIO modem.bin --CP_DEBUG modem_debug.bin --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Is this enough to revert to stock, if not, from where I can get the other files since are not in the archive from sammobile (after unpacking & unpacking & unpacking ... )
Thanks
PS: If any have a stock ROM (SM-G935F - galaxy s7 edge, UK unbranded) - that can be flashed with TWRP would be fantastic (deodexed or without bloatware or normal - doesn't matter).

So, I took a leap of faith and run the command. There were no issues, all steps were completed with success.
After Heimdall reboots your phone, you'll get a "No Command" screen. Wait there, will reboot automatically in the bootloader (the original one). Factory reset, purge cache, reboot. Welcome to stock android w/o Odin.
Mods: please close this. Thanks

f100019507 said:
Mods: please close this. Thanks
Click to expand...
Click to collapse
Thread closed as you requested.