Database Users

[Q] Soft Bricked my S4

Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.

tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.

xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.

tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.

Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441

When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.

Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?

Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.

tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.

Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.

Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.

Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.

Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.

Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.

Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.

Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.

tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] Help! Error Updating from MJA to MK2 on Sim Unlocked Phone

Hi,
I have looked all over this website and others for the solution to my problem. If there is a thread for this then I am sorry, but I couldnt find it.
I recently moved from the US to Mexico. I took my SPH-L720 to a phone technician to get my SIM unlocked and am now using it on the Iusacell network. Everything was working fine until I tried to install the MK2 update. The OTA update downloaded just fine, but when it is installing it gets about halfway and then displays a dead Android robot with a red triangle and an exclamation mark and the word "Error".
I do not believe that the phone technician rooted my phone. I think he flashed my modem to MDC. My build number is MJA. My software version is MDC.
Can anybody help me? My phone seems quirky after the MJA update, especially battery life. I am hoping MK2 will fix everything. Also, I have a Mac and not a PC.

newyorkcfc said:
Hi,
I have looked all over this website and others for the solution to my problem. If there is a thread for this then I am sorry, but I couldnt find it.
I recently moved from the US to Mexico. I took my SPH-L720 to a phone technician to get my SIM unlocked and am now using it on the Iusacell network. Everything was working fine until I tried to install the MK2 update. The OTA update downloaded just fine, but when it is installing it gets about halfway and then displays a dead Android robot with a red triangle and an exclamation mark and the word "Error".
I do not believe that the phone technician rooted my phone. I think he flashed my modem to MDC. My build number is MJA. My software version is MDC.
Can anybody help me? My phone seems quirky after the MJA update, especially battery life. I am hoping MK2 will fix everything. Also, I have a Mac and not a PC.
Click to expand...
Click to collapse
Sounds like there is a whole lot going on with your phone setup with so many inconsistancies.
If the Modem(baseband) is MDC - which it woul probably have had to be to do the SIM unlock stuff, and your build is MJA but your software version is MDC you've got a lot of stuff to look at.
How did the tech flash your phone? PC Odin? or via a zip/recovery. If it was flashed via a custom recovery (meaning you have one on your phone) then the OTA will fail/error. Same thing with a custom kernel - failure of OTA. Stock boot/kernels are required for OTAs to work.
The latest update is actually MK2 and not MJA by the way.
You can flash a .tar using Heimdal. Sammobile has the full MK2 one here.
BUT you'll probably need to do some fancy stuff with you APNs to get it to work on your current network - time to see tech who helped you again.

leaderbuilder said:
Sounds like there is a whole lot going on with your phone setup with so many inconsistancies.
If the Modem(baseband) is MDC - which it woul probably have had to be to do the SIM unlock stuff, and your build is MJA but your software version is MDC you've got a lot of stuff to look at.
How did the tech flash your phone? PC Odin? or via a zip/recovery. If it was flashed via a custom recovery (meaning you have one on your phone) then the OTA will fail/error. Same thing with a custom kernel - failure of OTA. Stock boot/kernels are required for OTAs to work.
The latest update is actually MK2 and not MJA by the way.
You can flash a .tar file using Heimdal. Sammobile has the full MK2 one here.
BUT you'll probably need to do some fancy stuff with you APNs to get it to work on your current network - time to see tech who helped you again.
Click to expand...
Click to collapse
Thanks for replying so quickly! I am very new to all of this stuff. If I flash the .tar file will that fix everything? Do I need to root my phone to flash the .tar file? Also, will my SIM remain unlocked or will it relock?
As for the APN, I think I already know all of the necessary info to input because when the tech unlocked the SIM he didn't input the APN info.
BY the way I know MK2 is the latest build and that is why I am trying to update from MJA to MK2. I'm sorry if I didn't make that clear in the OP.

Sorry, I also forgot to mention that I don't know if the technician flashed it with Odin or a zip/recovery because I left my phone there for a few hours. Is there a way to check?

newyorkcfc said:
Sorry, I also forgot to mention that I don't know if the technician flashed it with Odin or a zip/recovery because I left my phone there for a few hours. Is there a way to check?
Click to expand...
Click to collapse
See if you have a custom recovery.
Boot to recovery - Power off. Then Power on+Volume Up+Home button and see if something like CWM, TWRP or Philz recovery loads.
If it is just Spring/Samsung recovery then he flashed the modem via Odin and not a custom recovery. Either way just power off to boot again.

leaderbuilder said:
See if you have a custom recovery.
Boot to recovery - Power off. Then Power on+Volume Up+Home button and see if something like CWM, TWRP or Philz recovery loads.
If it is just Spring/Samsung recovery then he flashed the modem via Odin and not a custom recovery. Either way just power off to boot again.
Click to expand...
Click to collapse
It is the stock Samsung recovery. I guess he used Odin.

[Q] "Downloading.... Do not turn off target!" after TWRP

Can I get a little help here? I have a rooted, otherwise stock i337 that I just used the TWRP root app. I wanted to make a backup of my phone before I flashed a new rom. It downloaded jflteatt and I verified and installed it to /dev/block/mmcblk0p21. then i tried to make a backup, and i'm stuck at "Downloading.... do not turn off target!!!" In the upper left corner there's a "Could not do normal boot. ODIN Mode.
I found the post "[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3" but am hesitant to use it, as I am not sure that is what I need to do. I also found some other similar posts, but for different devices so I am again hesitant to rely on those.
I tried pressing home, power and volume down, but it just resets back to this screen. Also, I originally posted this request on the TWRP page, but I think it should be here. If so, I will delete it there.
Please help?

@kamikazees
If you could give more detail that would also help other to help u....such as what firmware that u are running before bricked...... well seem to me that u are either MF3 or MK2 firmware and u installed TWRP ...... u can only install safestrap recovery if u are on MF3 or MK2 firmware. ....Follow my thread http://forum.xda-developers.com/showthread.php?t=2621279 it should get u back to MK2 firmware. .....goodluck
Swyped From MK2 Dark Venom SS Edition

Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.

kamikazees said:
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
Click to expand...
Click to collapse
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.

DeadlySin9 said:
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
Click to expand...
Click to collapse
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.

kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
The first one is in img format and won't work through ODIN, but you can use those commands from terminal emulator to flash it if you download it. Otherwise, the TAR files do work just fine.

kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
If you are rooted and can actually boot the phone then I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery. I've been using Safestrap and TWRP since I was on MF3. I have also successfully flashed the tar files through Odin to get to MK2 with no problems. If you are rooted then its a really good idea to use Safestrap with TWRP for a recovery. Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable. The stock recovery on this phone is pretty much useless.

megamanDJ said:
...I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery... Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable.
Click to expand...
Click to collapse
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!

kamikazees said:
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
Click to expand...
Click to collapse
There is actually a way to flash a rom to the stock slot, but I haven't done it. Somewhere in the Safestrap threads explains how to do it. I think you can even get it back to normal if you change your mind.

need help guys at&t s4 brick. desperately

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

AT&T Galaxy S4 Recovery fails at 24%

My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.

StephenTiz said:
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
Click to expand...
Click to collapse
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.

No recovery options
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software

No recovery options
sway8966 said:
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
Click to expand...
Click to collapse
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software

StephenTiz said:
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
Click to expand...
Click to collapse
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.

Woop Woop!
sway8966 said:
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Click to expand...
Click to collapse
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.

StephenTiz said:
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
Click to expand...
Click to collapse
I am glad that it works out for you.
Rooting is so easy from that point. Just get towel root and root it. The link also included in my previous post. After the root you might need to disable the AT&T OTA update too. The instructions are also in that post too.