Hi,
I want to get the 3-button mod working and then install CF-Root 1.2 on my JP0 Galaxy S.
I'm using Linux and therefore Heimdall and the documentation is a little 'light'. Could someone please confirm that the following procedure is correct for the 3-Button Mod...
1. Untar Aries_P-SBL.tar.md5 (produces boot.bin and Sbl.bin)
2. 'adb reboot download'
3. 'heimdall flash --boot boot.bin --secondary Sbl.bin'
4. Wait for reboot
5. Profit.....
Likewise for the CF-Root kernel the following...
1. Get the JPM version of the kernel (JPM=JPOish)
2. unzip CF-Root-JPM-v1.2-Busybox-1.17.1.zip (Produces the Kernel zImage)
3. 'adb reboot download'
4. 'heimdall flash --kernel zImage'
5. Wait for reboot
6. Gain root.....
Many thanks for whoever can answer this.
Dan
You'll have to specify a pit file with the --pit parameter. Other than that it should work fine.
That will not work without a pit file, try 512.pit if that does not work then try 803.pit or 513.pit.
The right line should be when using 512.pit:
Code:
heimdall flash --pit s1_odin_20100512.pit --boot boot.bin --secondary Sbl.bin
Thanks Ramad and Benjamin. I've got the pit file (bootloader??) and will flash when I'm feeling brave!!
(update , flashed the 3-button download, successful!)
Does that .pit requirement also apply when flashing the kernel?
Dan
Yeah a PIT file is currently required for all flashes performed using the stock version of Heimdall. This restriction will be removed in future releases.
fixed recovery/download buttons with Heimdall (under linux)
Samsung Galaxy S (locked to 3UK...)
GT-I9000
f/w 2.2
Assuming adb and heimdall are installed and phone is visible under linux ("lsusb", "adb devices") the following worked for me...without a ".pit file....(heimdall-1.1.1-1.1.x86_64 FROM OpenSUSE Build service)
"heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin"
the boot.bin & Sbl.bin are from GT-I9000_P-SBL_RCVDL_FIX_ODIN.7z...
I now get into recovery or download mode EVERY TIME with the three button salute...hope this help someone. NOTE: I'd first updated to 2.2...
Phone originally had 2.1.?? and no recovery/download access via the three buttons. After wallowing around with kiels and virtual box I took the phone into work & updated to 2.2 via the Samsung Kiels on a Win XP system...That proved the basic usb connectivity/update process functioned according to the way Samsung had intended giving me the confidence to work under linux...
regards
philvr
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!
After getting my GS3/i9300 I realized that I didn't have a Windows computer anymore to root it. So I was stuck finding an alternative to Odin. I had trouble finding one aggregated source of Mac info that was relatively recent (last post I see is from Feb 2012) and all in one place.
I'm on MacOS X 10.7.5 (Lion) which isn't the most current version. I'm also a noob so maybe I got lucky as I've seen many comments within the various threads where my steps didn't work for other people.
When you download Chainfire's Auto-Root zip file, you'll need to do things a bit differently than with Odin. After unzipping, you'll need to untar the .tar file as well. You'll want the recovery.img and cache.img files in a folder on your PC. You'll need to know the path to that directory.
Instead of using the Heimdall GUI (which I found confusing), I ended up finding Chainfire's comments about using the Linux/Terminal commands in one of his old posts. He said it was "hearsay" but I can confirm that it worked on my GS3. Credit goes to jzuijlek for posting it (his post).
You'll want to install Heimdall from here
Currently they're saying to install version 1.3.1 instead of 1.3.2.
After Heimdall installs, I suggest rebooting your Mac.
Now to the good stuff...
Boot your phone into download mode:
1) Unplug your phone from the computer.
2) Turn your phone off
3) Hold both the volume down + home button. Then press and hold power until download mode comes up. Then press the volume up key to continue.
3) Plug in your phone
4) Open up Terminal and then cd to your recovery/cache.img files directory
5) Then type in this command:
sudo heimdall flash --recovery recovery.img --cache cache.img
If all goes well then you'll see stuff being installed and your phone will reboot and you'll be DONE!
However, if you're like me, you got an error. The response from Heimdall said, "Claiming interface failed". It turns out that there may be conflicts with Kies kexts if you have it installed. If you don't have it installed and you're seeing this error, I'm not sure if I can help. I suggest uninstalling Kies as you won't need it after you root. I searched Google with my error and finally found this gem from March 2012!
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
As such, if you've installed Kies on your Mac and you're having this error, I suggest using the following commands. It seems some kernel extensions that Kies installs conflict with Heimdall.
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
After this, I tried to flash again and it worked like a charm!
Now you're rooted.
However, Chainfire doesn't support CWM in his CF-Autoroot anymore so you'll need to get CWM or some other recovery image (Philz, TWRP, etc.). You can search these forums but these links should be mostly correct
CWM (find the Samsung Galaxy S3 i9300 in the list: http://www.clockworkmod.com/rommanager
Philz (built on CWM): http://forum.xda-developers.com/showthread.php?t=2002953
TWRP: http://forum.xda-developers.com/showthread.php?t=1943592
You'll flash the same way as above with just the .img file
Boot into download mode using sequence above.
(Example with CWM)
Open up Terminal and cd to the directory with your .img file.
Then type:
sudo heimdall flash --recovery recovery-clockwork-6.0.2.7-i9300.img
For reference...to boot into recovery:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
I hope this helps! Let me know if you think I got anything wrong!
Is this still theway to root on mac?
I have s3 uk 3 network. 4.1.2 xxella.
I blieve my phone was open to sds attack before the xxella update. can i keep this recovery?
I would strongly advise against using Heimdall. Nothing against the authors, but I tried it and would recommend avoiding it. Simpler approach is to setup Windows (In my case Windows 7) in a VM environment (I bought VMware Fusion) and just use the normal Odin. You'll get far more support from people here, and less headaches.
While i agree that Odin is easier and gives you more help from the community, i used Heimdall anyway due to not having any wish at installing windows on my mac.
This method does work (as of may 2013), however:
-Uncheck the "reboot after flashing" option in Heimdall. When Heimdall has done its job, manually boot into recovery. This way your custom recovery wont be overwritten by stock recovery.
Happy flashing!
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!
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.