I’m having a problem flashing via ODIN or anything else… I have a Sprint SPH-L720 MF9 everything. I am using a mac with VMware fusion and windows xp and 7. I have also tried everything below on a native windows 7 machine.
I started with MF9 and had rooted and ran TriForce 3.1 for a long time. Everything was working fine, so I never updated. I didn’t want to get tangled up in the knox mess. I decided to go ahead and update last night and I went through using unknownforce’s instructions and downloads. I tried to flash NAE modem only, but odin failed. Now it won’t boot, just goes to the download mode page. (the one that says to recover using kies) it also allows me to enter download mode (power+volume \/)
I’ve tried:
Odin full MF9 firmware (as my phone started with this, and I’ve never flashed anything knox)
Odin MF9/NAE modem
Full MF9 odin restore (there’s a thread that has the whole exe that does everything)
All of these with adding a pit file.
Every time, odin fails. It seems to be failing at the modem.bin, but who knows. It doesn't seem to transfer for very long, perhaps 2 minutes.
I’ve gotten to the “screw it” stage and loaded Kies (tried both mac and windows xp and 7) and tried to do a recovery there. It won’t recognize the phone right now though. It just sits there, basically. EDIT: It sees the phone and sits there trying to connect, but eventually times out.
Odin can see the phone and attempts to flash, but again, runs into the problems above. I can’t download the firmware through kies due to being a sprint phone and no S/N. I'd prefer to avoid knox, but if I have to, I'm fine with going that route. If I'm not out of warranty yet, it will be soon. As long as that's the only big ramification, I don't really care.
Anyone have any ideas? Need more information?
Update: I was able to get part of the NAE update to work. The Knox bootloader. That's it. It's not tripped, but it's now showing in download mode. Still can't get any further, however.
Sent from my Nexus 7 using Tapatalk
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
2WhiteWolves said:
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
Click to expand...
Click to collapse
The linked page for unknownforce is actually the page I was using to update the first time. The problem is, odin fails no matter what I do... I appreciate the suggestion though.
Try different usb cable and usb port. Someone mentioned to uninstall kies it will cause issues with odin. You can try that or uninstall drivers an install it again. Or try different versions of odin. I use 1.85 and some versions thats starts with 3. Since you already flashed NAE tar. You can not flash any version before NAE. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Called sprint who transferred me to Samsung, they couldn't talk me through it. The phone wouldn't show up in kies for them. They did mention, to my great relief, to steer clear of the sprint store. They instructed me to head to best buy and go to the Samsung store inside. Apparently they supposedly have a tool to reflash the phone there... We'll see later today. I'll post back with my results. I have 28 days left in my warranty. Just in time, it seems.
I didn't try using 1.85, but had tried 3.07 and 09. Kies came later. I originally used the drivers recommended in other threads. I only have two ports on my main machine, but did try another machine without success. Cords as well. Actually I did a backup with one of the cords right before trying the flash. Who knows.
Now that the warranty is nearly gone and I'm surely knoxed now.. Is there anything I need to watch out for? Does it make it much different to flash or is it just the flag for my soon to be nonexistent warranty?
Sent from my Nexus 7 using Tapatalk
Update:I took the phone to Samsung inside Best Buy. They hooked it up to a laptop and got it working within 20 minutes. They flashed 4.4.2 onto the phone, and to my surprise, everything was as I left it, minus root, and with Sprint ID added. Somehow, through everything, my data partition was untouched. Even more interesting, all of my apps and everything work. I was on TriForce ROM 3.1... Only thing I've noticed is that my data connection isn't consistent. It will drop out, and stay out until I toggle airplane mode. Still says I have signal, and can make calls.. I think a full restore may be in order.
Moral of the story? The SWAS (Store Within A Store) Samsung is running in Best Buys is pretty decent. They took no time at all, in the grand scheme of things. Unfortunately, I wasn't able to see the software they used. He tried Kies at first, but moved on quickly.
Related
So my phone was rooted and had viperrom v4 on it. Long story short, I did a factory reset by accident and couldn't get any further than clockwork. I tried to flash it using the stock pit file and tar/md5 pda via Odin but can not get any farther than "Leave CS...).
I removed clockwork so all that I have on my phone is the standard recovery. Suggestions?
odin is inconsistantly successful
I have worked myself into a frenzy with fears of not being able to recover my phone. If you can get into DL mode you can odin back. Persistance is the key IMO. I have heard some people telling others to reboot and just run ODIN, not use the stock cable, move the USB port to one off the board itself, do a happy odin dance and place 50 dead wasps (not the Protestant type) on an altar.
Personally I just go at it. Again and again.
There are two versions of odin out there and a couple of instructions on if you should put the tar in the PDA or Phone section.
I am no expert but have had the most luck with the older version of odin and the PDA section. I have no idea what the differneces are.
Good luck. . .but I believe that if DL mode is able to be gotten to you are still able to recover your phone.
Hope this helps.
j
Try disabling your firewall and or antivirus before using odin. that helped me. Something was blocking the traffic on my pc
jus posted something like this, can you get into the phone after bringing back the stock recv? if not then this might help you...http://forum.xda-developers.com/showthread.php?t=899770
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
apel69 said:
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
Click to expand...
Click to collapse
Try odin 1.85 I use that to odin back to stock and dont worry about the other ones just make sure auto reboot is checked.
Also are you sure the phone you have is the sprint gs4 sph l720 jfltespr?? Cause odin a tar file not for the phone could potentially brick the phone.
Sent from my SPH-L720 using xda app-developers app
I would try to download the stock rom from a different source if you can. These tar files are so large for this phone that the possibility of a bad download is pretty high. Also, make sure you don't have to extract the actual .tar file first from the archive you download. Lots of these stock roms are repackaged into a zip file and you need to extract the tar file for use in Odin before installing.
I am back in business. I have my phone and home internet back now. Yeah. I used the same stock ROM I had since it was the same as sammobile which was also a zip file and I already had it on my system. I just used Odin 1.85 instead. I guess I could have done this earlier and prevented a near stoke but everything else I had done seemed to get me deeper in a hole. These large zip files have always made me a bit nervous but I haven't found where to get one otherwise.
I have some follow up questions.
1) Why would it flash with Odin 1.85 and not with 3.0.7?
2) Is CWM's SU not compatible with the S4? Everything was working fine until I switched this from chainfire to CWM using ROM Manager.
3) Is there a good source with unzipped ROM's?
Chainfires SuperSU is much better with JellyBean than cwm SU. For some reason most people that try to switch to SU from SuperSU have the same problem you had.
Sent from my icrap 2 using Tapatalk HD
Okay. I decided to go with chainfires after this fun little ordeal. The few small things I preferred from CWM is not worth it. Besides it looks like chainfire made some upgrades since I last looked at it. I guess I was lucky with my S3 because I converted several times.
Thanks for all the help everyone.
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
re: official stock firmwares
lstat said:
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
Click to expand...
Click to collapse
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Misterjunky said:
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Click to expand...
Click to collapse
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
lstat said:
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
Click to expand...
Click to collapse
I would keep trying Odin. Try different usb ports, don't use hub. Make sure you have the original usb cord. If it can get into download mode there's hope.
I tried flashing through Odin a few more times today with no luck, even tried to repartition with a .pit file and that failed. I think my phone is just screwed.
test
testtesttesttesttesttesttesttesttesttesttesttest
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Kevinnme said:
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Click to expand...
Click to collapse
How exactly were you able to do this? Kies doesn't recognize the phone in download mode.
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Kevinnme said:
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Click to expand...
Click to collapse
Unfortunately this doesn't seem to be working for me, either. Kies is not recognizing my phone in emergency firmware recovery on OS X or Windows.
See if you can find help making kies to recognize your device. I think you should be able to since you used Odin.
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Reinaldo33897 said:
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, on both a Windows box and through Parallels, neither have worked.
lstat said:
Yes, on both a Windows box and through Parallels, neither have worked.
Click to expand...
Click to collapse
Same problem. I tried flashing Ktweaker, install failed, and now the phone just vibrates every few seconds.
I have tried installing the PIT file, as well as the original firmware. Trying to reinstall the recovery ends with a "Fail" message.
Totally stumped.
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
lstat said:
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Did the same thing
I'm running Triforce 4.0 on MJA. My phone acts like it's looking for a signal but can only find LTE. The data on LTE works fine. Wifi also works. In my settings, it says my phone number is unknown (I have gotten it to also just say 0 while trying to get it to work) and my MIN is also unknown. It says my PRL version is 1, even after updating it. Everything worked fine until I tried flashing a new rom which wouldn't even boot. I restored my nandroid backup and that's where this whole mess started. Tried flashing the MK2 modem in odin, and even though it flashed successfully, it changed nothing and my settings also still say I'm on MJA.
I even went to the Sprint store, and a helpful fellow tried to flash it back to complete out of the box stock using Kies but it threw up an error and soft bricked me. Fudged up the flash counter somehow, too. He said he couldn't get me a replacement because he obviously knows I voided the warranty, but told me to go to another store and just tell them it was a 4.3 update gone awry and they'd get me a replacement because it was in a state where you really couldn't tell it was rooted. It worked, and they ordered a new one but said it'll take two days. In the meantime, I decided that I could get to the bottom of this because I still have data on my internal storage I want. I unbricked it, got my nandroid backup running and now I'm pretty much right back where I was earlier today. And I'm out of ideas. Does anyone know what it means when the phone forgets its own number? What can cause this? How can it be remedied? How can it be avoided?
Since you already tripped the counter and the Sprint guy you took it to was a boob..
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 re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
leaderbuilder said:
Since you already tripped the counter and the Sprint guy you took it to was a boob..
You could grab the MK2 .tar from [snip]snip[/URL] (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 re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
Click to expand...
Click to collapse
I was going to try downloading that, but I've already downloaded two other firmwares and I have an extremely small amount of data I can use per month (10GB) because I'm using Verizon's LTE. Nothing else is available where I live. My bill is already going to be $200, so I made one last ditch effort to get things to work without wasting ANOTHER gigabyte because not only did I not want to wait 7 hours for that download, I didn't want to download it at all because the previous firmwares I downloaded wouldn't even flash. They fail in Odin. Er, one of them does, anyway. The other one I downloaded was just not the right firmware.
So I tried just random things and typed ##72786# into the dialer. Phone rebooted, and everything works now, somehow. I'm still not sure what causes this, but as long as I can reliably fix it any time it happens then it's not a big problem. Now I just have to tell the guys at the other Sprint store that I don't need the replacement. Thanks for the help, by the way!
Skeezixmccat said:
I was going to try downloading that, but I've already downloaded two other firmwares and I have an extremely small amount of data I can use per month (10GB) because I'm using Verizon's LTE. Nothing else is available where I live. My bill is already going to be $200, so I made one last ditch effort to get things to work without wasting ANOTHER gigabyte because not only did I not want to wait 7 hours for that download, I didn't want to download it at all because the previous firmwares I downloaded wouldn't even flash. They fail in Odin. Er, one of them does, anyway. The other one I downloaded was just not the right firmware.
So I tried just random things and typed ##72786# into the dialer. Phone rebooted, and everything works now, somehow. I'm still not sure what causes this, but as long as I can reliably fix it any time it happens then it's not a big problem. Now I just have to tell the guys at the other Sprint store that I don't need the replacement. Thanks for the help, by the way!
Click to expand...
Click to collapse
Glad you got it back with Activation.
Thanks for reporting the solution too! Helps the community.
leaderbuilder said:
Since you already tripped the counter and the Sprint guy you took it to was a boob..
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 re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
Click to expand...
Click to collapse
What do you mean he was a boob? Lol
Sent from my SPH-L720 using Tapatalk
I would like to add that simply going to the option in settings to activate the device never worked, nor did updating PRL, profile, etc. Any time I tried to just reactivate the device using the option to do so, it would say there was an error.
sorry if this is a dumb question, but...
if you go into your mobile network settings, is your cdma subscription set to nv? if not, try switching that.
edit: sorry if i came a little late but i think that's the problem.
hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.
MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip
And it works--
rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:
myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:
Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you
Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk