[Q] Going back to Stock - Soft Brick Help - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!

AzWizzard said:
So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery after you Odin back mf9?

AzWizzard said:
So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!
Click to expand...
Click to collapse
when i soft-bricked my galaxy s4 (sprint) I just re-rooted the phone using Odin & cf-autoroot...if you wanna update to the latest version for the s4 download the NG5 tar file & flash it through Odin & you should be ok...as far as getting back unrooted factory condition I'm not sure if there's a factory image available yet...not saying there isn't but I haven't seen one

ROMANTiC KiD said:
Did you try a factory reset from stock recovery after you Odin back mf9?
Click to expand...
Click to collapse
Thanks! That worked and got it to boot. It's updating now too!

Related

[Q] Bricked AT&T Samsung Galaxy S4

Hello all, if anyone could please help me, I would be extremely grateful.
I updated my Cyanogenmod nightly to the release for December 8th, 2013. The download seemed to be fine, it rebooted into the twrp, and then it rebooted, but then my phone never loaded back up. I tried restarting my phone with the power button, and eventually resulted to the battery pull, but yet my phone still wouldn't load.
I then tried going into the twrp again, and tried to flash a nightly upload that I had used from December 4th, it seemed to of loaded, but again my phone never loaded up.
I tired all day to use Odin to flash the ATT stock firmware, but I kept getting an ODIN FAILED error. I tried several different firmware downloads for ATT, and again, still no luck.
I am really upset over this, and would love to know why the update didn't work, and MORE IMPORTANTLY, how do I fix my device???
Samsung experience shop
Go to a Best buy with a local Samsung Experience center. They can flash the Latest 4.3 software on it from your carrier as long as it turns on and gets to download mode. I did the same thing to mine a month or so back and it saved my phone haha. Its a cool tool they have that i wish i could some how pirate haha
jonathanml86 said:
Hello all, if anyone could please help me, I would be extremely grateful.
I updated my Cyanogenmod nightly to the release for December 8th, 2013. The download seemed to be fine, it rebooted into the twrp, and then it rebooted, but then my phone never loaded back up. I tried restarting my phone with the power button, and eventually resulted to the battery pull, but yet my phone still wouldn't load.
I then tried going into the twrp again, and tried to flash a nightly upload that I had used from December 4th, it seemed to of loaded, but again my phone never loaded up.
I tired all day to use Odin to flash the ATT stock firmware, but I kept getting an ODIN FAILED error. I tried several different firmware downloads for ATT, and again, still no luck.
I am really upset over this, and would love to know why the update didn't work, and MORE IMPORTANTLY, how do I fix my device???
Click to expand...
Click to collapse
I'd still try Odin. If you go to best buy, once you get 4.3 no custom recovery or cyanogen
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
I'd still try Odin. If you go to best buy, once you get 4.3 no custom recovery or cyanogen
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I was actually able to unbrick my phone using the Kies app for Mac. I don't know why I didn't try this earlier. I suppose I was trying to hold onto my root, and ability to flash custom roms onto my phone. Less than 24 hours of stock firmware, and I'm already annoyed. I also ran an update from At&T, and now I'm on 4.3. I'm still a n00b when it comes to the rooting and flashing. Yes, I can manage to follow and read directions to get my phone loaded with custom roms. But here's where I'm at now....
I'm running an unrooted AT&T Galaxy S4 with 4.3. I want Cyanogenmod back, and I want it now!!!
What do I do next????
jonathanml86 said:
I'm running an unrooted AT&T Galaxy S4 with 4.3. I want Cyanogenmod back, and I want it now!!!
What do I do next????
Click to expand...
Click to collapse
PRAY?
hnldriver77 said:
PRAY?
Click to expand...
Click to collapse
ok, but seriously. what can i do? and how do i do it?
you can root it, but that will trip the knox counter to 0x1,
id suggest going into download mode to see if you've tripped the knox counter to 0x1, if not and you want no warranty go to the original dev thread and look for ways on rooting there
if your wanting warrenty, your pretty much hooped then bud...
sopra rsorsifi
hnldriver77 said:
you can root it, but that will trip the knox counter to 0x1, but if thats not a issue then look in the original development thread...
Click to expand...
Click to collapse
What is the overall summary and importance of this knox counter?
Unfortunately at this point, you have root through vroot or kingo and that is all I can say. You cannot install a custom recovery, so no cyanogen
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] In a bit of a pickle

I feel like I am either about to really break my phone or fix it with this next flash, some guidance would be amazing!
Started off months ago with Sprint L720 MF9 out of the box and rooted it. Eventually I got around to loading Sacs 4.3 back in January and had no troubles. After getting the OTA update notifications again, I decided it was time to flash a 4.4 ROM and I followed this thread.
Got the NAE modem loaded, flashed philz 6.08.9, and loaded the stock MK2 ROM listed in the instructions. The phone booted and I went through the initial setup without any issues. Baseband and software both say NAE, but then I noticed I have no sound at all. The phone powers off automatically after a while as well. Loading anything from the Play store takes forever, however, the stock web browser runs just fine.
Should I be concerned about no audio or will this be resolved with going to the 4.4 ROM listed in the guide (no data wipe)? I kind of want to flash a rooted stock MF9 ROM and start over...
Any help would be appreciated.
Edit: Flashed to 4.4.2 and SSDD. I finally got sound back though by flashing the MK2 modem, just need wifi working now.
Reckoned said:
I feel like I am either about to really break my phone or fix it with this next flash, some guidance would be amazing!
Started off months ago with Sprint L720 MF9 out of the box and rooted it. Eventually I got around to loading Sacs 4.3 back in January and had no troubles. After getting the OTA update notifications again, I decided it was time to flash a 4.4 ROM and I followed this thread.
Got the NAE modem loaded, flashed philz 6.08.9, and loaded the stock MK2 ROM listed in the instructions. The phone booted and I went through the initial setup without any issues. Baseband and software both say NAE, but then I noticed I have no sound at all. The phone powers off automatically after a while as well. Loading anything from the Play store takes forever, however, the stock web browser runs just fine.
Should I be concerned about no audio or will this be resolved with going to the 4.4 ROM listed in the guide (no data wipe)? I kind of want to flash a rooted stock MF9 ROM and start over...
Any help would be appreciated.
Edit: Flashed to 4.4.2 and SSDD. I finally got sound back though by flashing the MK2 modem, just need wifi working now.
Click to expand...
Click to collapse
Usually your sound issue can be resolved by flashing another ROM.
As far as WiFi goes I just had this problem myself. If your bootloaders NAE and your modem is MK2 , try flashing the NAE modem back. That's what fixed it for me.
I'll not up to speed on all the quirks of the sprint s4 since I'm usually using a Verizon s4 . but it seems to me that if you have a NAE bootloader, it isn't cooperating with downgrading the modem either. Never was a problem for me when my phone was on MK2 build , but with each OTA the security gets upgraded too. Almost doesn't make sense to me though as Sprints bootloaders are unlocked.
Maybe someone else can shed some light on this.
Try NAE modem and see what happens,... bet your WiFi will be back like mine was.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Usually your sound issue can be resolved by flashing another ROM.
As far as WiFi goes I just had this problem myself. If your bootloaders NAE and your modem is MK2 , try flashing the NAE modem back. That's what fixed it for me.
I'll not up to speed on all the quirks of the sprint s4 since I'm usually using a Verizon s4 . but it seems to me that if you have a NAE bootloader, it isn't cooperating with downgrading the modem either. Never was a problem for me when my phone was on MK2 build , but with each OTA the security gets upgraded too. Almost doesn't make sense to me though as Sprints bootloaders are unlocked.
Maybe someone else can shed some light on this.
Try NAE modem and see what happens,... bet your WiFi will be back like mine was.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm actually still on MF9 bootloader. I did end up flashing back NAE modem last night and battery pulled after. All is working now! Thanks.

[Q] Sprint GS4 with repeated System Update

My Sprint Samsung Galaxy S4 (rooted with CF-Auto-Root) has been repeatedly downloading and notifying me of a 398.8MB update. It comes up every couple of weeks and I have allowed it to install several times.
I maintain root after the reboot, but it keeps coming back. I'm currently on Android version 4.3 (MK2 build).
Is there anything I can do to get past this update and hopefully get 4.4?
Thanks in advance.
Krosscheck NYC said:
My Sprint Samsung Galaxy S4 (rooted with CF-Auto-Root) has been repeatedly downloading and notifying me of a 398.8MB update. It comes up every couple of weeks and I have allowed it to install several times.
I maintain root after the reboot, but it keeps coming back. I'm currently on Android version 4.3 (MK2 build).
Is there anything I can do to get past this update and hopefully get 4.4?
Thanks in advance.
Click to expand...
Click to collapse
I am not sure you can stop the update box from going away (short of a custom rom).
I believe you just have to deal with it, if you want to stay on 4.3
VandyCWG said:
I am not sure you can stop the update box from going away (short of a custom rom).
I believe you just have to deal with it, if you want to stay on 4.3
Click to expand...
Click to collapse
Hi Vandy. Sorry if I wasn't clear in my question. I don't want to stay on 4.3...I want to get to 4.4 (Kit Kat), but it seems like I'm stuck on this 389.8MB update that keeps coming back even after I have allowed it to install.
I'm hoping that someone else has experienced this "repeated" update and can tell me how I can go about moving past it so that I can get to some newer updates.
Thanks - Chung in NYC
Your best option is to install the full NAE stock tar file with Odin. The update is failing because you either have a custom recovery installed, modified system files, or deleted something. OTAs can't complete unless your stock. Look for a thread from random45 in the android development thread and download the NAE stock tar from there. You won't lose any of your data, but you will have to reroot your phone afterwards.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Your best option is to install the full NAE stock tar file with Odin. The update is failing because you either have a custom recovery installed, modified system files, or deleted something. OTAs can't complete unless your stock. Look for a thread from random45 in the android development thread and download the NAE stock tar from there. You won't lose any of your data, but you will have to reroot your phone afterwards.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot - I will try that now!
- Chung in NYC:good:

Need some help

Ok so my phone has been rooted for a few months now and ive used custom roms with no problems, I was recently going to update my Negalite rom but I wound up downloading the wrong rom it was negalite for a different phone. Anyway that is now the only rom on my phone I have already cleaned everything and realized after that it was the wrong rom. Now my phone doesn't boot up I can get to download mode no problem anything else doesn't really work, ive tried flashing the stock tar with odin but keep getting a failed message.
Anything I can do or did my stupid mistake screw me completely?
Edit: Cant even get into recovery mode
When I got my Sprint S4, I thought I was cool since this was my second Android phone and I had experience with custom ROMs and rooting on my old phone. So, I got cocky and in a hurry and managed to flash a T-Mobile ROM on the phone. I had a small heart attack when the T-Mobile logo appeared during boot. Anyway, using ODIN, I was able to quickly get the stock Sprint setup back on the phone and start over. You should be able to do the same thing. If you don't care about Knox and want the latest, just try this thread, and you should be all fixed up pretty quickly:
http://forum.xda-developers.com/showthread.php?t=2663619
If you're worried about keeping an older bootloader things will be more complicated.
nobody291 said:
When I got my Sprint S4, I thought I was cool since this was my second Android phone and I had experience with custom ROMs and rooting on my old phone. So, I got cocky and in a hurry and managed to flash a T-Mobile ROM on the phone. I had a small heart attack when the T-Mobile logo appeared during boot. Anyway, using ODIN, I was able to quickly get the stock Sprint setup back on the phone and start over. You should be able to do the same thing. If you don't care about Knox and want the latest, just try this thread, and you should be all fixed up pretty quickly:
http://forum.xda-developers.com/showthread.php?t=2663619
If you're worried about keeping an older bootloader things will be more complicated.
Click to expand...
Click to collapse
At this point I just want my phone back lol, im almost done downloading that file from that thread im praying it works but if its the same tar file I already tried it prolly wont. If I get fixed I wont mess with custom roms cause ill prolly be updating my phone soon.
Sounds like you odined an old tar from either 4.3 or 4.2.2. Do you know what stock ROM or boot loader you were on before flashing the wrong rom?
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Sounds like you odined an old tar from either 4.3 or 4.2.2. Do you know what stock ROM or boot loader you were on before flashing the wrong rom?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Im sorry im kinda of a noob with this, before I flashed the rom I was using Negalite before that I was on 4.4.2 and boot loader is the recovery right? I was using phillz
EDIT: ya know what the one from that link seems to be working so far, I think ive got it...will update in a few if it works
Second Edit: OK it successfully booted up, im good. im assuming its different flashing roms now right? If so im staying away from it

Is my phone rooted, if yes how do I flash?

Here's my situation. Last year I bought a Samsung Galaxy S4 unlocked AT&T (SGH-i337) phone from ebay. I am using Cricket. A few months back I tried updating it by going to the update area and checking for an update. I am on 4.2.2 and wanted to upgrade to KitKat. Well my phone tells me every single time it's up to date even though I know it's not. I decided to use Kies to see if I could update it using that instead. Kies tells me my firmware is also up to date. I gave up for a few months.
Now that Lollipop is out for my phone I tried once again doing the same things. Once again both ways say my phone is up to date. I looked through multiple forums to finally find a possible answer. My phone may have been rooted at some point and apparently if it was, it can't be upgraded. I read it needs flashed back to stock. I looked at a nice long guide on here on how to flash back to stock and saw you need to know which boot loader you have?
Please help me guys. I'm assuming my phone was rooted and have never rooted myself but I want to flash to stock so that I can upgrade to Lollipop. Any help would be greatly appreciated!
Flash the nb1 tar file in Odin and then let it ota up to 5.0.1. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 9 using XDA Free mobile app
I flashed it successfully and am now on 4.4.2 however OTA and Kies both still say my device is up to date. At this point it doesn't look like I will ever be able to update using these two ways. I looked around trying to find a Lollipop flash but didn't know if any of them were safe. Can anybody point me toward a safe stock flash for Lollipop, or does this not exist yet?
GMLancers58 said:
I flashed it successfully and am now on 4.4.2 however OTA and Kies both still say my device is up to date. At this point it doesn't look like I will ever be able to update using these two ways. I looked around trying to find a Lollipop flash but didn't know if any of them were safe. Can anybody point me toward a safe stock flash for Lollipop, or does this not exist yet?
Click to expand...
Click to collapse
The ota's are rolled out in phases. You might have to wait a day or two for it to show up
Edit, alternatively you can read thru this carefully, http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app

Categories

Resources