Hi everyone.
I apologize for my ignorance here, I own the S3, i am helping a buddy with an s4.
he attempted to root and is now getting an error message in his notifications. His wifi won't turn on and his SD card appears to me non-accessible.
Ultimately, we are trying to get a custom recovery installed to flash a custom rom. I have flashed CFroot via odin, but its not working, we do not seem to have root.
There are a few things i am looking for, and am having a tough time finding:
A full md9 stock odin tar
a odin flashable recovery (so we could just odin a recovery and flash a custom rom)
Remember we dont have root right now so we cant install recoveries via rom manager or goo manager.
I am really familiar with Galaxy devices, i think i just need some help from s4 regulars to find the files i need.
Any help would be really appreciated.
Here is the link for the Stock MF9 firmware. Its in a zip when you download. Just unzip and you will see the tar file. Place it in the PDA section of odin.
http://hotfile.com/dl/235555943/ff47da6/SPR-L720VPUAMF9-20130626162512.zip.html
Sent from my SPH-L720 using Tapatalk 4 Beta
I;ve been having some issues with my phone and I relized that I was on a leaked version of 4.3. Could someone let me know if this is the most current stock version of android for the sprint s4
SPH-L720_MF9_Stock_Factory_Restore(compressed archive).exe
http://www.rwilco12.com/downloads.p...PH-L720)/Stock ROMs/MF9/Full Restore/Unrooted
If so can I just use odin and flash this back onto the phone and ill be current or shall i say sprint current?
MK2 is the latest.
You could grab the MK2 .tar from here (the tar.md5 is in the zip, just extract the .tar.md5 and put that one file in the PDA slot of Odin) and flash it via Odin.
It'll reset everything (all partitions and modem etc.)
Then root via CF-Autoroot (it's in the dev section), add recovery using GooManager and then do what ever you want.
Hi there, I rooted this phone a while back and for some reason decided to also load a custom recovery (Pretty sure it's TWRP) even though I was using stock firmware and just wanted root. Now the phone's trying to do an OTA and it won't work of course because of my custom recovery. I was wondering if someone had a link to a stock recovery I could flash via ODIN/Heimdall? Thanks!
P.S. If you could include a step-by-step on what I need to do, that'd be nice. As far as I remember it's just putting the phone in Download Mode and flashing the .tar file via ODIN.
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
gus_zernial said:
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
Click to expand...
Click to collapse
Flash Stock Rom via ODIN.
Joku1981 said:
Flash Stock Rom via ODIN.
Click to expand...
Click to collapse
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Check this thread http://forum.xda-developers.com/showthread.php?t=3335065 I don't know if you have experience with Odin process. Google it preferably look at YouTube video, if you feel shaky on Odin concepts.
Sent from my SM-G935F using Tapatalk
gus_zernial said:
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Click to expand...
Click to collapse
1. "I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC." Reflash this FILE via ODIN coz you flashed wrong one and boot in it. Go to next step if doesn't work.
2. Flash Stock ROM via ODIN. SM-G935FD use the same firmwares that SM-G935F.
Careful with ODIN. Make sure you are running on the latest version, as I myself has problems using it for the Galaxy S7 Edge on an offer version
Sent from my SM-G935F using Tapatalk
maybe my question will be weird lol...how can i sofbrick a s7 g930p to be exact and then i can just unbrick flashing the U firmware? thanks.
Hello all!
I've had a family member brick their Verizon S5 because they thought they were being smart and now I've been given the task of fixing it. The S5 was on the stock PF4 build previously (no root and no unlocked bootloader) and then had the stock OC4 tar from SamMobile flashed onto it via Odin which obviously bricked it. Furthermore they flashed the PD1 stock tar on top of that thinking that being on the same Android version would fix the problem so right now I have a phone with PD1 firmware but a PF4 bootloader. The phone currently will boot to the setup menu but has a continuous stream of error messages that makes the phone unusable (if I were able to get it into MTP transfer mode I could potentially have Kies 3 fix this).
Unfortunately, SamMobile doesn't have the PF4 tar file online yet and I don't have a spare Verizon S5 to exploit Kies with to get the tar file (I was able to get an encrypted version of the PF4 build using Kies 3's feature that pre-downloads the most recent firmware automatically but it lacks any file extensions and I've no clue how to make it usable).
I know that people have access to the stock components of PF4 like flashable tars for the modem and bootloader and even a flashable zip for custom recoveries of the entire stock PF4 build so I was wondering if anyone could help me out with getting a stock PF4 tar file (if not I will just have to wait till SamMobile puts up the file).
Any help would be greatly appreciated!
Edit: Found the firmware via Samsung-Updates and fixed the phone so help no longer needed
Closed at OP's request.