Database Users

[Q] [Soft Brick] At&t Samsung Galaxy 4S (MF3/4.2.2/SGH-I337) [[[HELP PLEASE]]]

Hi guys, I'm new to this site. I have a specific problem that I can't seem to find the answer for.
My phone: At&t Samsung Galaxy S4 (I made a typo in the title... )
Model: SGH-I337
I had MF3 version/4.2.2
I used various threads to eventually root my phone.
I was very happy.
I had to use safestrap
I was happy with safestrap
I had my stock in the stock rom slot
I had [ROM] Google Edition 4.3 [Clean][Deodex][276MB][2013.11.21] in first slot.
I was very happy with it.
Here is the thread http://forum.xda-developers.com/showthread.php?p=47718525#post47718525
I made a stupid move when I was finally done, I had my phone rooted, I had everything I needed, but it wasn't enough...
I did something in the mount options area in safestrap.. switched my sd to internal memory
My phone has been in a boot loop ever since on Samsung Image
I had Slot 1 active when this happened.
When I'm in recovery mode, all the options, including wipe data/factory reset doesn't work
I tried using a pit file in Odin to fix/failed
I tried using Odin 3.09 with stock firmware I found in some threads to try and get factory/failed
I get this in Odin along with fail "All threads completed. (succeed 0 / failed 1)"
I really want to fix my phone.
Preferably I would like it to stay as mf3
Does anyone have a solution?
A link to a thread I missed?
Something more recent?
I also tried Kies, but it was giving me trouble, I'll try it again as a last resort.
I hope there's a solution. ​

Kies 3
Kies 3 didn't work as well with emergency upgrade.

worried
joeydija said:
Kies 3 didn't work as well with emergency upgrade.
Click to expand...
Click to collapse
SW Rev Check Fail fused 2 Binary 1

Whoa.
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:

I spoke too soon.
joeydija said:
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:
Click to expand...
Click to collapse
Failed at the end.. I guess that's not the right order.. farthest I've got so far though, now when I boot I see Odin.
[Not the God]

hoorah!
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy

joeydija said:
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy
Click to expand...
Click to collapse
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!

of course
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Download link: https://mega.co.nz/#!MwAhlDyC!UOnkMFsUSctakHRfE1Mr95c1ymVwy1wBPu2yiPerros
If you've never used this site before
It's kind of weird
Press the DOWNLOAD button, it's RED
Wait for 100%
When you reach 100% it either starts downloading by itself or you press the download symbol
Good luck!

Summon odin
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!

Another Soft Bricked SGH-I337...
joeydija said:
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!
Click to expand...
Click to collapse
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and the following from the prompt on the S4 screen:
SW REV. CHECK FAIL : fused : 4, Binary : 2
Click to expand...
Click to collapse
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.

mythandier said:
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
and the following from the prompt on the S4 screen:
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.
Click to expand...
Click to collapse
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.

777
DeadlySin9 said:
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.
Click to expand...
Click to collapse
Thanks for helping that guy out,
I have a question...
What ROM would you recommend for a 4.2.2 MF3 At&t Galaxy S4 SGH-I337?
I've been using the ROM found in here.
I am new to the rooted world.
It's the first ROM I tried and I love it.
I can go a whole day with, at most, losing 25% battery life.
I love the minimalist aspects of it.
I don't know how to keep track of new ROMs for my build though.
I don't really want to change ROMs at the moment, because I have everything I need with this one,
but if you can give me some cool advice, that would be awesome.
Any help, information, would be appreciated.
-Joey

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

[Q] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!

[Q&A] [ROM][TAR] Stock OD2 Odin flashable

Q&A for [ROM][TAR] Stock OD2 Odin flashable
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][TAR] Stock OD2 Odin flashable. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

sprint l720t OD2 rom
I am trying to find a OD2 odin flashable rom to fix my s4 and can only find the .zip files for flashing in recovery or the odin for the l720 and i need to l720t flash.
The recovery on the device is gone and i cannot get it to come up in kies to do a emergency flash.
If anyone has a link to the tar file that would make my day much better thanks

alexrcb4buggy said:
I am trying to find a OD2 odin flashable rom to fix my s4 and can only find the .zip files for flashing in recovery or the odin for the l720 and i need to l720t flash.
The recovery on the device is gone and i cannot get it to come up in kies to do a emergency flash.
If anyone has a link to the tar file that would make my day much better thanks
Click to expand...
Click to collapse
so i understand you need the OD2 tar for the L720T. I'll have it up for you in a little bit.

alexrcb4buggy said:
I am trying to find a OD2 odin flashable rom to fix my s4 and can only find the .zip files for flashing in recovery or the odin for the l720 and i need to l720t flash.
The recovery on the device is gone and i cannot get it to come up in kies to do a emergency flash.
If anyone has a link to the tar file that would make my day much better thanks
Click to expand...
Click to collapse
I've uploaded it for you. You can download it here.

hello
i flashed my galaxy S4 l720 with lollipop 5.0.1 and my contacts didnt appears and the second thing is the language it contain only english .i want french and arabic language so this ROM is there french and arabic language or not

l720 OD2 download link
Does anyone have a mirror of this tar? for some reason i cannot download the file from media fire

alexrcb4buggy said:
Does anyone have a mirror of this tar? for some reason i cannot download the file from media fire
Click to expand...
Click to collapse
Sammobile.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I attempted to flash this firmware to my SPH-L720 and Odin 3.07/3.09 both gave me a PIT error message and the flash failed. I attempted to use a PIT file I found, used the repartition option in Odin but even after using that the OD2 flash still fails. Could someone point me in the correct direction to the proper PIT file for OD2 or upload one for me? Or, point me in the right direction on how to get this flash to complete with Odin?
Thank you very much!

I tried doing this.
Instructions:
1. Download and Extract tar above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit
I downloaded the odin file. After extracting I got two files - an MD5 and an extension file. My phone is plugged in to my laptop. My phone is showing the android logo and says "downloading... Do not turn off target!!"
When I try and follow the instructions given, at #3 I get stuck. I can't "open as administrator" - there is no option. I'm running windows 7.
I did not change the file name or anything. Am I doing something wrong? Missing a step? I am a bit of a noob but I can read and follow instructions.

Flying_NEB said:
I tried doing this.
I downloaded the odin file. After extracting I got two files - an MD5 and an extension file. My phone is plugged in to my laptop. My phone is showing the android logo and says "downloading... Do not turn off target!!"
When I try and follow the instructions given, at #3 I get stuck. I can't "open as administrator" - there is no option. I'm running windows 7.
I did not change the file name or anything. Am I doing something wrong? Missing a step? I am a bit of a noob but I can read and follow instructions.
Click to expand...
Click to collapse
try ignoring the administrator step. Just open up odin and proceed.

random45 said:
try ignoring the administrator step. Just open up odin and proceed.
Click to expand...
Click to collapse
I think I figured out it didn't download correctly. I don't have an exe file

Flying_NEB said:
I think I figured out it didn't download correctly. I don't have an exe file
Click to expand...
Click to collapse
That exe file being referred to is Odin
Sent from my SM-N910P using Tapatalk

I figured out what the issue was. Even though I was using a brand new Samsung cable... I changed both the cable and the computer(9 years old) I was using. Doing so allowed me to bring the phone back to life and flash this along with the modem after the reboot using Odin. Thanks for putting this up on the site!

How long should this tar take to flash? I saw in the other thread a line about it taking awhile but its been on writing system for a good 45 minutes. I've never flashed anything in Odin that took longer than 5 minutes so just curious if I should abort or let it keep rolling along.

bckoolaid said:
How long should this tar take to flash? I saw in the other thread a line about it taking awhile but its been on writing system for a good 45 minutes. I've never flashed anything in Odin that took longer than 5 minutes so just curious if I should abort or let it keep rolling along.
Click to expand...
Click to collapse
Only about 15 mins

Is the OP still fresh? I just got this Sprint Samsung Galaxy S4 SPH-L720T yesterday and good ol' Sprint aint what she use to be? Are the golden days of the SPH-D700 & 710 behind us? I'm not new to flashing but, it has been a while.. I saw someone post they flashed this and a modem. Then I seen some other posts talking about bootloaders? Do we have to play Legos with getting stock firmware now? I remember having multiple nandroid backups of CM, PacManROM,SlimBean, AOKP.. Things sure have changed a lot..
But, back to my original question, is the OP good for stock firmware or do we need to piece together bootloaders and such? I really want to root and flash some custom ROMs but, the beauty of the Epic 4G was that you could just go back to a fresh slate in a matter of seconds. Seems like a lot of the "stock" ROMs here are pre-rooted and pre this and pre that..
---------- Post added at 01:38 AM ---------- Previous post was at 12:47 AM ----------
I just flashed the L720T and everything went perfectly. Nothing seems out of place..

Samsuage Galaxy S5 SM-G900W8 - Google/Random Apps Crashing [4.4.2-6.0][Same Result]

Hello, So I am having a very strange issue with this phone (Samsung Galaxy S5). For the pass 3 days I have been trying to diagnose this problem and I can't seem to figure it out. I was wondering if someone could help me or guide me to the right path.
I went from stock 5.1 lollipop that came with the phone. Used ODIN to flash TWRP and flashed CM 12.1. Then I flashed GApps then everything was fine booted into it. Then the welcome screen came up and immediately noticed "google play service has stop" and this would happen every 1 min or so. I just kept ignoring it. With every reboot a variety of crashes would happen. For example most of the google apps would crash along side with some simple apps like facebook. For every reboot the crashes would be more or less the same. The crashes are native and the stack trace are some what different but don't really tell much of a story.
So I went from CM 12.1 to CM 13 with the same results. I clean flashed it, installed gapps ( The recommend opengapps ) and the same results. Varitey of google apps crashing again and again and again. So I tried different roms that were not based on CM and the same thing. I flashed back to stock and same thing. Which was very werid, so at this point I was stuck I didn't know what else to think of. I tried every method to ensure that all the cache was clear on google play services and other apps that were crashing. The interesting thing is that sometimes when download an app I get a variety of errors unable to download or install ranging from error code 902, 960, -2 so I used adb debugger to see what the heck was going on. I noticed that the md5 hash from installing apps (From google play store) weren't matching. So I assume okay perhaps corrupt wireless card but I used my mobile data same thing and still doesn't fix the constant google apps crashing. These issues that I have described are the exactly same thing for all the different roms I have tried from stock > CM12.1 > CM13 > Blisspop > OmegaRom > Stock (Again)> (Stock kitkat 4.4.2) so this issues doesn't seem like a software issue as the same results happen every time. I was wonder if anyone could shed some light into this issue its a strange issues and I am speculating it is a hardware issue. Thank you very much

Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)

*Detection* said:
Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)
Click to expand...
Click to collapse
Yes and I will proceed to flash the pit. I actually I was a thread about flashing the pit with the stock before I posted ill try it out and flash it with stock to see the results and yes I formatted everything including data

Ok so I reflashing it along side with the pit file you gave me. I think I did it wrong as I unticked the "Re-Partion" because it was giving me error "Re-Partition operation failed" and on the phone it says "Secure check fail : PIT" the device is fine on stock same crashing results. I know the pit didn't flash at all I am assuming lol

If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed

*Detection* said:
If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed
Click to expand...
Click to collapse
I am with Fido, and download the stock ROM under "Fido" on sammoblie and on one of the links on the fourm. And yes I figured unchecking it wouldn't do anything I just thought I would try it out lol.

Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8

*Detection* said:
Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8
Click to expand...
Click to collapse
I have tried that and it fails ODIN saying " Re-Partition operation failed " phone saying " secure check fail : PIT"

100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..

*Detection* said:
100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..
Click to expand...
Click to collapse
Yes 100 percent download mode with the combos vol down + home + power. I also tried using link2sd to actually move all apps to my external SD card and same results constant random google apps crashes with other apps. Along with that issue I also have random "unable to download" issues on google play store using adb to capture the logs and verified that the issues were occurring because of a MD5 hash not being match to the source which leaves me to believe that it can either be a storage issues corrupted the data as it is being written to or the wireless nic in the phone itself. Thank you very much ill also look into it on the threads to see if anyone has a similar issues. Its a very strange issue, if anything I will be doing more debugging to see of I can for sure verify it is a issues of the internal storage of the device. Also I would like to mention that I used TWRP "Repair" partion on all directory from /system to /data
Also yes I am using a native PC Windows 10 Pro

If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy

*Detection* said:
If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy
Click to expand...
Click to collapse
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.

Franco093 said:
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.
Click to expand...
Click to collapse
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing

*Detection* said:
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing
Click to expand...
Click to collapse
I JUST saw the same thread doing it right now!

Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick

*Detection* said:
Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick
Click to expand...
Click to collapse
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!

Franco093 said:
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!
Click to expand...
Click to collapse
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.

Franco093 said:
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.
Click to expand...
Click to collapse
And you are not doing anything else other than flashing stock?
You're not letting Google backup restore your apps or anything? Just 100% stock?
If it's still doing it after flashing the PIT (Nice job btw )it's either a buggy stock ROM, but if it was doing it with custom too, that rules that out,
Or a hardware issue
Have you tried creating a new Google account to test, in case something with your account is messing with settings/apps (Unlikely, but only thing I can think of atm)
Have you tried formatting or just removing your MicroSD card, and then factory resetting stock again, so you have 100% just the phone, purely with stock ROM, with a new Google account - to remove any traces of anything you've done since buying it

I do not have a microsd card connected to it. And I tried a custom ROM and same crashes google services and google app constantly crashing, I also get random download errors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I notice also that one of the google service crash was a memory violation error. Maybe the ram is corrupted

It is sounding more and more like a hardware fault, we've done just about all that can be done to rule out firmware (ROM)
KNOX will be tripped from you flashing custom too, so I'd say your only option is to pay for it to be fixed, or sell it as faulty and buy another one unfortunately, unless any other Android gurus have any ideas
Good luck
EDIT - One last thought, when you flashed the modded PIT on it's own, did you check to see if it had actually wiped the phone clean before flashing stock again? (Did it hang on the logo / black screen?)
Just wondering if the PIT did actually do it's job or not, after being modded