Samsung sgh-1337 download my pictures windows 10 - have
How do I restore stock firmware [or] CyanogenMod to a Samsung Galaxy S4 (AT&T) displaying the following firmware error message in recovery mode:
I encountered this same situation and was able to get back to a base level using Heimdall on Mac OS X El Capitan 10.11.2.
I have used Heimdall to flash firmware to my Galaxy S4 before, but I ran into problems more recently getting it installed on El Capitan. I had to get the signed patch that is available in this thread https://github.com/Benjamin-Dobell/Heimdall/issues/291. I found some good Heimdall basics and insights here at xda and here at kossboss.
I followed the steps below from xda (but using Heimdall instead of ODIN): HOW TO GET TO ANY KITKAT 4.4.2 (NB1, NC1, NI1) OR 4.4.4 (NJ4, NJ5) BASE. In my case, I wanted to just get the phone up again, so I chose NB1...
- Power off phone
- Boot into Download Mode --- press and hold BOTH power and volume down buttons --- when you see "Warning!" screen... release both buttons --- press volume up to continue
- Connect phone to PC via usb cable on pc...
- Extract .tar.md5 from Stock NB1 OTA file
- (NOTE): Here I used unrar to extract the tar.md5. Then, I removed the .md5 extension and extracted the tar contents. There were 15 files.
Right click Odin and run "as administrator"- Click AP button and select extracted tar.md5 file
- Click Start
Instead of ODIN for steps 5 - 7, I used Heimdall as follows in three passes of flashing and rebooting to Download mode (see step 2 above).
I happened to experience intermittent USB errors () during several attempts. By trial and error, I noticed that the errors were more common on the large system.img.ext4 file and had moved it to the final pass. By flashing the recovery and boot partitions first, I noticed the benefit of bringing online the firmware recovery process, which could open up some additional possible alternatives like ADB sideloading. Absent of any issues, I believe the flashing could be done in one pass, but I haven't confirmed.
It is important to note that the errors that I was getting was resolved by moving my USB cable to a different port on my MacBook Pro. I had read to check the cable and switch ports in other situtations, and after seeing the intermittent failures, this seemed to be the trick that allowed me to successfully flash the large system file without error and ultimately get the phone running.
-