Related
Hello. I have been searching for hours like a mad man on Google for a solution to my problem, but i'm having no luck. Excuse the nooby nature of this post please. So I rooted my Galaxy S4 and I am trying to get it back to stock by flashing the AT&T md5 onto my phone (Galaxy S4 SGH-I337) through ODIN and it fails every single time. Initially, with ODIN 3.07, it would return something like fail (auth). Then I tried with ODIN 1.85, but that version returns "Complete(Write) operation failed." In addition, I attempted Kies but it too failed (no specific error code), and now the phone wont boot. It says that the firmware upgrade encountered an issue. I am not able to access stock recovery or TWRP because it will automatically go to Download Mode with "Could not do normal boot" in the top left corner if I in any way attempt to access it. I am using the stock cable with USB Debugging enabled. I also tried two different computers, two different cables (one being stock of course), and tried every single usb port on both computers. What went wrong? I will give you my upmost respect if you can solve this. I also am absolutely willing to supply any information you may need. Just ask. (Please don't be bricked. Please don't be bricked)
-With kind regards, Branden.
Let me guess you had the att mf3 firmware and tried retoring by flashing the MDL firmware via odin? You said md5 so I assume mdl? You might at this point still be able to fix it visiting a best buy near you if it has a samsung center. Also att store can reflash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click Here throw this thread in the MF3 pile... guys we got another noob here, take a trip to your closest best buy and hope the samsung experience will flash the mf3 update for u
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
jd1639 said:
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
Click to expand...
Click to collapse
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
If you never got twrp to work then I'm almost positive you have mf3 firmware. You're best bet is best buy and have them re-flash the firmware.
Astrophysicist789 said:
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
Click to expand...
Click to collapse
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
gandes said:
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
Click to expand...
Click to collapse
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Astrophysicist789 said:
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Click to expand...
Click to collapse
Your welcome
And just so everyone knows...md5 is part of the package name I believe... (.tar.md5) or could be referring to md5 checksum...anyways as was mentioned and you acknowledged, best buy is your best bet
Sent from my SGH-I337 using Tapatalk 4
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ralphie1267 said:
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is the dreaded one! Root your device and flash a custom ROM or use titanium backup to freeze the update apps.
Sent from my SGH-I337 using Tapatalk 2
Gentlemen/Ladies,
I was putting custom roms on my phone last night, trying a few different out. Obviously I misread (or didn't read) some instruction somewhere and ended up with this lovely message when turning my phone on:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So, what are my options? Can I use Odin or ADB or something to at least get the phone back to stock or am I completely effed and have to walk into a Verizon store? I'm open to suggestions and will probably try all of them.
Please advise,
phoyce
Flash a stock ROM via odin
DSA said:
Flash a stock ROM via odin
Click to expand...
Click to collapse
I did (tried) as you suggested. Obviously I'm doing something wrong.
I downloaded the stock Verizon Galaxy S4 SCH-i545 VRUAMDK md5 from [galaxys4root.com/galaxy-s4-stock-firmware]. I boot the phone into download mode, open up Odin (3.09) and flashed using the file above. Odin still fails on the first block.
Is this because what I downloaded was for Android 4.2.2 and my phone was/is 4.4? Or am I downloading the wrong file or simply going about this the wrong way?
Thanks a lot for the help, as you can see I'm still learning.
- phoyce
phoyce said:
I did (tried) as you suggested. Obviously I'm doing something wrong.
I downloaded the stock Verizon Galaxy S4 SCH-i545 VRUAMDK md5 from [galaxys4root.com/galaxy-s4-stock-firmware]. I boot the phone into download mode, open up Odin (3.09) and flashed using the file above. Odin still fails on the first block.
Is this because what I downloaded was for Android 4.2.2 and my phone was/is 4.4? Or am I downloading the wrong file or simply going about this the wrong way?
Thanks a lot for the help, as you can see I'm still learning.
- phoyce
Click to expand...
Click to collapse
you need to post in your relevant forum, this is for the international s4's
http://forum.xda-developers.com/galaxy-s4-verizon
but no, once you have got kitkat on your phone, you cant downgrade just like that
flash a kitkat stock rom via odin
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
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.
Hi Everyone I'm not even sure if anyone is going to reply to this but heres the deal. yesterday i flashed a custom rom to my phone s4 (sgh-i337m unlocked carrier) i have twrp3 installed for custom restore and i did make a restore file when my phone was still on lollipop, and i think that the backup worked because the boot screen is back to stock but now heres my issue, i power up my phone i get past the "galaxy s4" screen but get stuck on the samsung animation, i gave up on it after it sitting there for 2 hours then i removed the battery and then flash installed 7.x nougut onto it, but cant get playstore but thats just minor but what i do want is to go back to full stock no root, i feel that ive made a mistake and im just not comfortable with it anymore even if i loose all my stuff thats fine ive had the phone for a week, i do have odin on my computer but dont know how to use it because theres icons like bl, ap, cp and csc i dont know what those are well i know ap for installing twrp. I'm needing help like yesterday
You will have to download the stock ROM and flash it with Odin. Stock ROMs can be downloaded from sammobile.com, but download speeds are slow for non-premium users.
Flash guides can be found with everywhere.
Confirm that the model # is sgh-i337m in download mode. If it is, do this:
download Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNHMbaSWjgVwWQGtMVr1TvJSsXWUcA
download the latest 5.01 firmware from here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-I337M/BMC/download/I337MVLSGQB1/125370/ (This is for Bell but it doesn't matter because Rogers, Bell, Telus, Koodo, and Fido use the same ROM with some minor carrier customization). Unzip the file once to create a tar.md5 file;
put the phone into download mode;
open Odin and click on PDA, select the tar.md5 file;
connect the phone to the computer using the original Samsung USB cable;
uncheck everything except f reset time and flash the phone;
when you see the word RESET in the status window, remove the USB cable from the phone, remove the battery, replace the battery; boot the phone into recovery mode, factory reset, and reboot.
How to get into download mode: https://www.youtube.com/watch?v=7nC2vX492wI
How to get into recovery mode: https://www.youtube.com/watch?v=LkrUVSxGW9g
The correct forum for the sgh-i337m is here: https://forum.xda-developers.com/galaxy-s4-att
audit13 said:
Confirm that the model # is sgh-i337m in download mode. If it is, do this:
download Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNHMbaSWjgVwWQGtMVr1TvJSsXWUcA
download the latest 5.01 firmware from here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-I337M/BMC/download/I337MVLSGQB1/125370/ (This is for Bell but it doesn't matter because Rogers, Bell, Telus, Koodo, and Fido use the same ROM with some minor carrier customization). Unzip the file once to create a tar.md5 file;
put the phone into download mode;
open Odin and click on PDA, select the tar.md5 file;
connect the phone to the computer using the original Samsung USB cable;
uncheck everything except f reset time and flash the phone;
when you see the word RESET in the status window, remove the USB cable from the phone, remove the battery, replace the battery; boot the phone into recovery mode, factory reset, and reboot.
How to get into download mode: https://www.youtube.com/watch?v=7nC2vX492wI
How to get into recovery mode: https://www.youtube.com/watch?v=LkrUVSxGW9g
The correct forum for the sgh-i337m is here: https://forum.xda-developers.com/galaxy-s4-att
Click to expand...
Click to collapse
Thankyou i did fully verify everything before hand and yes it is sgh-i337m i actually got a different rom fully working and i do thank all users that did view and help me out. I did find a way to get gapps installed wothout issues. I still cant restore the device back to stock but i actually bought a replacement stock phone and use this one that were communicating on now. So now i have two phones completely identical minus the fact that one is unlocked from at&t and the other was never locked to anything.
Pwnycorn said:
You will have to download the stock ROM and flash it with Odin. Stock ROMs can be downloaded from sammobile.com, but download speeds are slow for non-premium users.
Flash guides can be found with everywhere.
Click to expand...
Click to collapse
Took a while but finally acquired 2 stock roms one telus and one sasktel. I will probably do a rom swap one day
The non-aws version of the s4 sold in Canada is the sgh-i337m. You can cross flash roms from any carrier as they are all the same except for a bit of customisation by adding their own apps.
A quick download source is updato.com.
Btw, the Canadian s4 forum is here: https://forum.xda-developers.com/galaxy-s4-att
I'm stuck also on the samsung animation screen, and flashing a stock rom does nothing for me it's stuck. I can't even go into stock recovery. everytime i do try it just say recovery booting and loops back into samsung screen. is there any way to fix this?
Thanks I'm new to the site and didn't know there was a Canadian s4 forum, I thought it was a specific device forum because my phone isn't att because att is not active on my area, we have telus, koodo, rogers, sasktel and bell
SPheDaGhost said:
I'm stuck also on the samsung animation screen, and flashing a stock rom does nothing for me it's stuck. I can't even go into stock recovery. everytime i do try it just say recovery booting and loops back into samsung screen. is there any way to fix this?
Click to expand...
Click to collapse
One thing I did because I was in the same boat and it sounds like your stuck in a soft boot is download lots of roms to a SD card and trial and error, use the latest version of twrp and flash the first version of twrp to the phone with Odin there's lots of YouTube videos to assist you, also when using a custom rom (in my experience) is that you also have to download gapps to gain the full google/android experience and it's safer to download apps with Google playstore compared to using a browser. Also when flashing remember to wipe catche and delvic before rebooting. Hope this helps and if your using the same kinda device as me I'd recommend the 7.1.2 rom by JDC it works pretty good and it feels like the s8