Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
JJ2013 said:
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
Click to expand...
Click to collapse
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Further details of whats been tried
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Yes, I neglected to include that I tried wiping cache first, then re-boot attempt, then cleared cache and factory reset, then tried to boot, then wiped cache and factory reset followed by CWM recovery then boot attempt, then cleared cache, re-boot attempt, then all over again and flashed stock - all with no change - boot loop prevailed. What troubles me is that with no other changes the phone froze and re-booted on stock firmware?? And weirder still that once it re-booted the first time it stayed alive for 5 minutes, then 2 minutes, then less than 1, to 'that's all folks' and continued to decrease how far it even went in boot attempt. To the 'slightly informed' like me that seems strange - that's why I was wondering if it could be a hardware failure causing ROM or RAM to be corrupted further with each boot attempt - or - with time 'on'.??
Will try one click mf9 and post back
rimgarciag said:
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
JJ2013 said:
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
Click to expand...
Click to collapse
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Very wise advise
ROMANTiC KiD said:
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
The title say's it all - but this is very wise advise for us all! Electronics can suffer from infant mortality issue's, and I would agree 101% with you!
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
No to 4.3
BIGSAMDA1ST said:
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
I am actually sure it was on 4.2.2 the day it died - still had the notification nag that update was downloaded. I was going to look for how to remove that 'nagging' notification but hadn't yet. Since I rooted the day I got it and installed CWM any OTA update (4.3) should have failed even 'if' I accidently hit the 'system update downloaded' prompt on my notifications screen, which I didn't. The phone had been on for about 4 hours when it first locked and re-booted while texting - and had it updated it would have had to re-boot which I think I would have heard/seen/witnessed some kind of evidence that it had. I think you are going in a good direction though, looking at all possibilities. I know from root checker it rooted successfully and since I made a CWM backup I know stock recovery was gone - so very unlikely 4.3 found it's way in.
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Will try removing SD card
cruise350 said:
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
No, I only installed but never opened or set up folder mount so that never even crossed my mind. I just got home and have a few things to try - and I think the first and simplest is removing the SD card! OK, tried that to no avail - boot loop get's to samsung logo and repeats. Tried to clear cache and factory reset with card removed and tried again after battery removal for 2 minutes. Same situation - nothing has changed. Will try 1 step restore next. Downloaded on my laptop but had to leave that with a co-worker for data aquisition project - have to download again here at home.
This is off track, but I have never asked for help and//or participated in a forum like this before. I am happily suprised by the intelligent, thoughtful responses I have recieved so far. Didn't expect anything, but am glad I asked - and even though I am still 'stuck' I have had incredibly good input into potential resolutions for this issue. Thank you all for the assistance so far
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Verified through download mode - no Knox line present
cruise350 said:
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
No luck - bricked or dead phone...
JJ2013 said:
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
Click to expand...
Click to collapse
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
JJ2013 said:
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
Click to expand...
Click to collapse
I haven't tried this and not sure of the possibility of it working but if you could establish a connection via fastboot or download mode to a computer running adb you could be able to pull the log from dev/log/ and see exactly what is going wrong.
Look here http://stackoverflow.com/questions/12995030/how-to-use-adb-pull-command for info on pulling files in adb
Sent from my SPH-L720 using XDA Premium 4 mobile app
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
HELP
JJ2013 said:
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
mndbtt said:
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
Click to expand...
Click to collapse
No garantee, but I had rooted mine before it went haywire and bootlooped. When I took it in they had the phone for 15 minutes in the back out of my site - expect they went into download mode and could see it was not original (rooted) but replaced it anyway without any fanfare. BTW, after 3 weeks with the new device I rooted it as before - this time using TWRP becouse I had recently helped a friend root a tablet and used TWRP recovery - liked it so... In any case, I have had my rooted S4 (#2) running without issue ever since.
Or at least i think its powering off - i punch in my encryption passcode, it goes to android splash screen, then zip...
I have been looking at other threads and searching (this forum is huge!) but not yet found an answer, certainly not one where i dont factory wipe.
The phone was on the official optus 4.3 firmware
What i did was I used Odin 1.85, and the appropriate CF auto-root from here (cant link yet, not enough posts)
Powered off the thing, took battery out for over an hour, twice, still the same
Just trying to re-root the phone so i can back it up again, it had been a while since using Titanium
Follow the typical instructions, seemed to go fine, it just gives me the green android screen for about two seconds after encryption key is put in and always goes off
I wiped the cache too, and i flashed the current firmware again using odin (Aus OPTUS 4.3 official) - still the same.
Anyone got any ideas for me>?
Valacer2 said:
Or at least i think its powering off - i punch in my encryption passcode, it goes to android splash screen, then zip...
I have been looking at other threads and searching (this forum is huge!) but not yet found an answer, certainly not one where i dont factory wipe.
The phone was on the official optus 4.3 firmware
What i did was I used Odin 1.85, and the appropriate CF auto-root from here (cant link yet, not enough posts)
Powered off the thing, took battery out for over an hour, twice, still the same
Just trying to re-root the phone so i can back it up again, it had been a while since using Titanium
Follow the typical instructions, seemed to go fine, it just gives me the green android screen for about two seconds after encryption key is put in and always goes off
I wiped the cache too, and i flashed the current firmware again using odin (Aus OPTUS 4.3 official) - still the same.
Anyone got any ideas for me>?
Click to expand...
Click to collapse
If your phone keep's turning it off by it self then try to use a spare battery.maybe the problem is the battery and check your battery as well if the serial number starts with BD and that should need to be change soon.
Sent from Hell ?
Repulsa said:
If your phone keep's turning it off by it self then try to use a spare battery.maybe the problem is the battery and check your battery as well if the serial number starts with BD and that should need to be change soon.
Sent from Hell ��
Click to expand...
Click to collapse
Tried two different batteries.
I would think it coincidental both would prove faulty right after i tried to root!
Thanks mate
I just wiped the phone - i had to get it working, ahh well
Hi, I think that I have done something to my new phone and it is not working right now. I was trying to root it, and followed the directions and it went into the rebooting phase. But now it does not want to get out of the rebooting phase. It keeps on turning off and on. I need help. I have looked all over to see if there is ways to root a gs5 sport and have come across a site that said do not try to root it. Now I am in trouble and would like to fix this problem. How do I factory reset this phone, root it if possible.
nate2mars said:
Hi, I think that I have done something to my new phone and it is not working right now. I was trying to root it, and followed the directions and it went into the rebooting phase. But now it does not want to get out of the rebooting phase. It keeps on turning off and on. I need help. I have looked all over to see if there is ways to root a gs5 sport and have come across a site that said do not try to root it. Now I am in trouble and would like to fix this problem. How do I factory reset this phone, root it if possible.
Click to expand...
Click to collapse
If you're stuck in a bootloop, pull the battery and boot to recovery, hold home, vol up and power until it boots to recovery, then select wipe cache then wipe data factory reset.
nate2mars said:
Now I am in trouble and would like to fix this problem. How do I factory reset this phone, root it if possible.
Click to expand...
Click to collapse
You can try the advice above, but it may not be sufficient. The poster there isn't very attentive to details.
Your phone is in a bootloop. If you are lucky and it's just due to a minor conflict then the above advice will prevail. But if your root was incomplete or any errors were written then it won't be sufficient. In that case you will need to use Odin to write a full factory firmware image to your phone to revert it to a proper working condition.
You should be able to root your phone. But we need to know the details of both your phone (model, firmware, baseband versions, etc) and a detailed description of how you tried to root it. In particular what file you tried to write and the Odin log that shows if any errors occurred during the root. Without those critical details we don't know what happened. If that information isn't available for some reason, then your best course would be to back up any files that are important to you. Then write a full stock firmware image to your phone and start over.
.
Deleted post, was going to say something I'd probably regret about probably the most bland person on XDA
"Bland".... lol
Sent from my SM-G900F using XDA Free mobile app
Luckily I don't have to listen to no more of it, s5 is gone. Note 4 is here. Laters
Hi,
I'm new to XDA forums, and this is the first time that have ever tried rooting my phone. I got it in my head that I wanted to root my Samsung Galaxy S5 SW-G900P so that I could add a hot spot mod. I followed a few tutorials which helped me accomplish root. I then added TWRP and that went fine as well. Then I added a WiFi Tethering Mod (unlockHotspot-1.4-NE5-DEODEX.zip) via TWRP. I was asked to wipe Dalvik cache which is where I think the problem started. I think I did something and stopped the delete process. I can't recall. I turned on my phone with anticipation of being able to use Hotspot. The phone started to boot as normal; the Samsung logo with lines moving around it showed; the yellow 4g 3d animated graphics showed; then the main 4g graphic showed and stayed on my screen which is where it stayed and nothing after that. Just the 4g logo. So, I pulled the battery and started my phone in recovery mode which took me directly into the TWRP interface. I figured that I needed to reload the 6gig backup file that I created (through TWRP) in order to bring my phone back to life. I believe that I was given options to install the recovery file which (I don't remember them all) already had a few check marks added to the options. However, there were other options such as the System and Recovery boxes that were not checked, so I checked those boxes as well. I reinstalled from the recovery backup file and everything seemed to work fine until TWRP rebooted the phone and now I am stuck going through the recovery booting process again. Every time I turn on the phone, I get to the teamwin screen which blinks and blinks. Did I brick or soft-brick my phone? I'm newb to this and need a little help to get my phone working again. Also, am I in the right part of the XDA forum to ask questions? Help me Obi-Wan Kenobi, you're my only hope.
@Uclid
Soft brick.
Go to sammobile, find your stock firmware, uzip it, flash with Odin in download mode and your phone will wake up from her sleep
Sent from my XT1528 using XDA Labs
Thank you, thank you! I really appreciate the reply. I downloaded the firmware this morning and just loaded it to my phone. All good now. Now, to get that hotspot mod to work.
Good to see you got your phone back up and running......but if you flashed the firmware with odin, you will have lost root and overwritten TWRP.......
You'll need both back before you can flash that zip......
http://i.imgur.com/rVnFwJM.jpg
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340