Related
Fixed!!! Thanks to Moscow Desire & BlackThund3r, for the leads to the final solution, and obviously bsg19071979 for the actual solution. The partition table was invalid. I ended up using "BadSector" (Had to follow multiple threads on XDA then over to TegraOwners, Then finally back here, to this post "http://forum.xda-developers.com/showthread.php?t=1691729&page=3"
bsg19071979 said:
can be fully corrected sector:
1. Download h??p://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
2. Run a501 A.bat
3. run recovery 1.7.3 -> "Mount and Storage" -> "Format /system"(better than twice).
4. Run a501 B.bat
Click to expand...
Click to collapse
So can someone tell me what i can do to fix this thing?
I was running Stock ICS 4.03, havn't cared much for it, & wanted to go back to Stock HC 3.2, so tried flashing "Acer_A500_7.006.03_COM_GEN1" from A500 Dev forum. (followed directions, but it would just give the android, on his back, with red exclamation point, then re-boot back into 4.03.)
Read somewhere that I should try using the update.zip file from within the archive directly (rather than renaming "SD_Acer_A500_7.006.03_COM_GEN1.zip" to "update.zip"
Tried that, seemed to work fine, then screen went blank when update was nearly finished, and now can only boot tablet in APX mode. (Lost recovery??)
I have tried replacing lost recovery using APX_v0.4A-flashTool-500Manager1.0.2, The manager says it detects the tablet in APX Mode, but when I try logs, it either just stalls at "Waiting for tablet" or says "No device connected"
Tried to install "EUUs_SBK_Acer_A500_1.016.05_COM_GEN1" (HC 3.01) and it will actually put the tablet into download mode, but will go no further. (At least I can see that the tablet's screen is capable of doing something, as opposed to just being black!)
Any Idea's what will get this tablet going again?
EDIT: Using APXFlash tool, for some reason, on 2 different computers, the text on the buttons doesn't show up, so, The only button I could see was "Dump My BCT", when I clicked it, I would get the BCT file not found message.
I found a tutorial (that showed where all the buttons were & wgat they say, & just used the default BCT. Still cannot get past the "Flashing Bootloader (EBT) stage two - uploading image..." message... nothing is happening, just stalled. Still need some direction...
Thanks
In short, being on stock ICS you also had the ICS bootloader and cannot just flash back to any earlier version. Most likely you now have several pieces of different ROMs embedded on your tab. Take a look at TimmyDean's excellent tutorial which will take you back to v3.2.1 and allow OTA updating: http://forum.xda-developers.com/showthread.php?t=1516012
Goodluck!
amphi66 said:
In short, being on stock ICS you also had the ICS bootloader and cannot just flash back to any earlier version. Most likely you now have several pieces of different ROMs embedded on your tab. Take a look at TimmyDean's excellent tutorial which will take you back to v3.2.1 and allow OTA updating: http://forum.xda-developers.com/showthread.php?t=1516012
Goodluck!
Click to expand...
Click to collapse
So, this is pretty much the same thing I was trying with the EUU file from Acer, and produces the same result. It goes as far as saying "Upgrade is under way. It may take more than 10 minutes." Then it appears to start flashing, (The progress bar starts to move) then errors out with the message "We are sorry! The upgrade process failed. Please follow the instructions for recovery" ( So, what exactly are the instructions for recovery?)
A note maybe worth mentioning, this Tab is stuck in APX mode, so when I get the prompt to enable USB Debugging, I am not aware of a way to enable it, also understood we didn't need that as we are using APX mode?
As well, I know I have the right CPUID, as I looked it up before starting the flashing process, and have just now verified it by liiking with USBDeview.
I am using 0380620044400497.
So, after conneccting the tablet, but before running the flash update, I opened a command window, & ran ADB devices. Got the following output:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Notice there are no attached devices, yet As I mentioned earlier, I do not know of any way to turn on USB de-bugging, and I am in APX mode, so I shouldn't expect to see a device through ADB, Correct?
So, is this going to work at all trying to load a bootloader/recovery if I cannot turn on USB de-bugging?
Sorry, again, Any thoughts?
Danny2 said:
So, this is pretty much the same thing I was trying with the EUU file from Acer, and produces the same result. It goes as far as saying "Upgrade is under way. It may take more than 10 minutes." Then it appears to start flashing, (The progress bar starts to move) then errors out with the message "We are sorry! The upgrade process failed. Please follow the instructions for recovery" ( So, what exactly are the instructions for recovery?)
A note maybe worth mentioning, this Tab is stuck in APX mode, so when I get the prompt to enable USB Debugging, I am not aware of a way to enable it, also understood we didn't need that as we are using APX mode?
As well, I know I have the right CPUID, as I looked it up before starting the flashing process, and have just now verified it by liiking with USBDeview.
I am using 0380620044400497.
So, after conneccting the tablet, but before running the flash update, I opened a command window, & ran ADB devices. Got the following output:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Notice there are no attached devices, yet As I mentioned earlier, I do not know of any way to turn on USB de-bugging, and I am in APX mode, so I shouldn't expect to see a device through ADB, Correct?
So, is this going to work at all trying to load a bootloader/recovery if I cannot turn on USB de-bugging?
Sorry, again, Any thoughts?
Click to expand...
Click to collapse
Edit: I just ran this again, tried loading an ICS bootloader this time, & noticed there is an error message earlier on in the execution that I previously missed. Please see attached Screen1 (screenshot)
Error is right after bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14)
message: nverror:0x4 (ox4) flags: 0
So, I used BlackThund3r's NVFlash, running in a command window, & captured the screen output in the attached .jpg. NVFlash starts, Attempts to format partition 4, then errors out with the message
"Command Execution failed cmd 13, error 0x12002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
NvFlash started
[resume mode]
Thats it, she hangs here & refuses to go further.
This mean anything to anyone?
Danny2 said:
Edit: I just ran this again, tried loading an ICS bootloader this time, & noticed there is an error message earlier on in the execution that I previously missed. Please see attached Screen1 (screenshot)
Error is right after bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14)
message: nverror:0x4 (ox4) flags: 0
So, I used BlackThund3r's NVFlash, running in a command window, & captured the screen output in the attached .jpg. NVFlash starts, Attempts to format partition 4, then errors out with the message
"Command Execution failed cmd 13, error 0x12002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
NvFlash started
[resume mode]
Thats it, she hangs here & refuses to go further.
This mean anything to anyone?
Click to expand...
Click to collapse
Fixed!!! Thanks to Moscow Desire & BlackThund3r for the leads to the final solution. The partition table was invalid. I ended up using "BadSector" (Had to follow multiple threads on XDA then over to TegraOwners, Then finally back here, to this post "http://forum.xda-developers.com/showthread.php?t=1691729&page=3")
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!
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)...
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.