Caught in a Boot Loop, Samsung Galaxy S4
-
Caught in a Boot Loop, Samsung Galaxy S4
Since this is a non-Windows issue, I'm posting this thread in the chillout room. :)
I have a Samsung Galaxy S4 SPH-L720, 16 GB, Black Mist, Sprint. I bought it from SamsClub this past August and it's connected to the Sprint network through FreedomPop.http://www.samsclub....3.ip?navAction=
FreedomPop doesn't matter in this situation though, but I thought the extra information may help.
This morning I wanted to try rooting it with SuperUS which was already on my phone. Somehow the operation failed and the phone needed to reboot. So I rebooted it, but it would just sit there.. loading. It couldn't get past the FreedomPop loading screen, I left it for about 20 minutes but it was still loading and the back of the phone was really hot. I tried booting into Recovery Mode and that worked so I did a system restore in hopes that that would fix all my problems, but it still wouldn't get past the loading screen. So, I tried clearing the Cache and the Dalvick cache and that didn't help either.
So.. I decided to try to return my phone to stock using Odin and stock Firmware. Everything was going great, but then Odin stopped and said the operation failed. Here's the log.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now what do I do? I do not want to have to buy a new phone.
Thanks for any help.
-Chuck
-
-
Hmm, I'ts been a while since I've had a Samsung phone or used Odin, so I hesitate to really offer any suggestions. Are you familiar with XDA Developers forums? That's where I go to do all of the root and ROM stuff for my phones. I'd advise jumping over there and posting your issue in their S4 forums. Looks like the L720 S4 that FreedomPop uses is the same as the Sprint S4. Here's the link to the specific forum on XDA:
http://forum.xda-developers.com/galaxy-s4-sprint
-
Hmm, I'ts been a while since I've had a Samsung phone or used Odin, so I hesitate to really offer any suggestions. Are you familiar with XDA Developers forums? That's where I go to do all of the root and ROM stuff for my phones. I'd advise jumping over there and posting your issue in their S4 forums. Looks like the L720 S4 that FreedomPop uses is the same as the Sprint S4. Here's the link to the specific forum on XDA:
http://forum.xda-developers.com/galaxy-s4-sprint
Posted: Caught in a Boot Loop after Rooting | Sprint Samsung Galaxy S 4
Thanks, blackrose. :)
-
-
-
Oh good, I'm glad to hear you got it fixed. Doubly glad to hear that you didn't brick your phone with Odin.
I once bricked a Galaxy S2 so hard via Odin that neither Sprint nor Samsung could bring it back to life. Haha
-
Now my WiFi isn't working.
It wouldn't let me slide the switch over to the on position, it just flips back into the off position. I've tried taking the battery out and putting it back in again, but that didn't work. Only thing that may help, is something I saw here. Please help... My Galaxy S4 won't let me enable Wi-Fi - Android Forums at AndroidCentral.com
Internal SD Memory the Path /data/misc/wifi/ the File named wpa_supplicant.conf is having issue.
Not going to guess what what was done on your side only that wifi cannot read that file so it just shuts off.
you need root to view this file, I suggest renaming it, reboot then enable wifi again and it will create a new one.
you will lose all saved passwords from the beginning of time but will be able to use wifi again.
But I don't seem to have access to that file. He says I shouldn't need root access to view the file.
EDIT: Figured that one out too... phone is working like new again. :)
Last edited by Chuck38; 30 Jan 2016 at 10:27.