Related
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
My GPS and Snapchat would never work correctly on almost any ROM I tried, so today I decided to go back to stock which I have done multiple times.
I used the root66 file that I used a few months back. It looked as if it worked but then wouldn't get passed the download screen. I then downloaded yet another stock file to restore it.
It then worked. Started fine. Everything looked GREAT..... BUT now it wont pick up signal. IT wont read my SIM card and the APN Verizon network is greyed out. Everything else is perfect. But what good is this phone if it cant pick up any signal?
Can someone PLEASE help me. Ive spent 6 hours trying to figure this out and cannot.
Now that you flashed that file, do a factory reset and you should be golden
Sent from my SCH-I605 using Tapatalk 2
dahaight said:
my gps and snapchat would never work correctly on almost any rom i tried, so today i decided to go back to stock which i have done multiple times.
I used the root66 file that i used a few months back. It looked as if it worked but then wouldn't get passed the download screen. I then downloaded yet another stock file to restore it.
It then worked. Started fine. Everything looked great..... But now it wont pick up signal. It wont read my sim card and the apn verizon network is greyed out. Everything else is perfect. But what good is this phone if it cant pick up any signal?
Can someone please help me. Ive spent 6 hours trying to figure this out and cannot.
Click to expand...
Click to collapse
我的手机也不能上网了。悲剧
Had the same thing happen to me. Clean the cahe in recovery mode. Then factory reset. It worked for me as well.
joecool73 said:
Had the same thing happen to me. Clean the cahe in recovery mode. Then factory reset. It worked for me as well.
Click to expand...
Click to collapse
Not working here either ... One bad flash or missed wipe and it's
Clearing cache then factory reset isn't fixing it.
http://forum.xda-developers.com/showthread.php?t=2077653 is the XDA fix to restore the IMEI but getting the right driver combo so I can get it onto my phone has been a serious pain in the neck ... been working on it for almost a week.
Here is exactly what I have and did.
Verizon Note 2 sch-i605 VRAMC3 build. This is completely stock never been rooted. Used Odin v3.07 and root66_VZW_stock_system.tar file. I did this on my windows xp sp3 PC. Here are a couple of screen shots before and after root. Now after I rooted, I did have to clear the cache and factory reset phone in recovery mode to get it to boot up. Make sure that you root the phone with Odin v3.07 and only have the PDA and f reset time checked. Ive made that mistake before myself. If that does not work, try flashing the complete stock Verizon ROM back to the phone. That will put the phone into its factory state, ie new out of the box. I always have a full non rooted stock copy just in case. The stock file is called Stock Verizon Note 2 I605VRAMC3_I605VZWAMC3_VZW. This is the most current build.
The 1st pic is before root, the 2nd pic is after root, the 3rd pic is of Odin finishing and shows what options are selected.
Notice the build number and android number are now different.
I'm having the same problem as well. What I did though was I installed phoenix 17 on my i605 like an idiot and realized it wasn't going to work so i went back to the rooted touchwhiz. However, I can't seem to get service no matter what I try. Could somebody post a link to the root66 download?
try to flash the file via odin: toltevzw_mj9_official_firmware.tar.md5 it works for me when i flash the stock 4.3 rom
I got a Note 2 yesterday, bought it used. I turned it on, everything seemed normal. I took it to Verizon, they activated it for me in the store, and while I was there, the lady activating it also accepted an OTA software update. I have no idea what version I was on, or what the OTA was. When I got home, the phone shut down as part of the OTA, and everything appeared normal. The little android with a box screen came up, cycled through the progress bar, etc. However, when it was done, the phone rebooted, and froze on the "Samsung Galaxy Note II" screen. I gave it a while, then battery pulled, tried everything I could think of. Couldn't get into the recovery menu. It would get to Odin, but that was it. Anyways, after a very stressful night working on it, I found the thread here:
http://forum.xda-developers.com/showthread.php?t=2040264
I downloaded the "Alternate Restore Mirror" link, put the phone in download mode, and installed from Odin on my computer. The phone booted up, everything worked beautifully.
Then, tonight at work, I checked for software updates, and was informed that there was an available update. I downloaded and installed it(I think the phone said it was 7MB?), and THE SAME THING HAPPENED. Phone is frozen on the "Samsung Galaxy Note II" screen. I plugged it into my laptop, put it in download mode, and did exactly what I did this morning. Odin says everything was successful, and reboots the phone. But it hangs on the "Samsung Galaxy Note II" screen, no matter what I do. I've tried searching, and followed every guide on how to unbrick it I can find, but no matter what software package I use, it fails on "sboot.bin". The only one that will work and not fail is the "Alternate" in the link above, but when I use that one I still have a bricked phone.
I -really- need advice here, guys. I'm in way over my head.
So, a little more information. If I have a ROM that doesn't have an sboot.bin attached to it, it will write just fine and not show any errors. However, the phone will hang up on the "Samsung Galaxy Note II" screen. If I write a ROM that tries to write sboot.bin, it fails. Every time.
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Jiggabitties said:
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Click to expand...
Click to collapse
I did. When it tries to write either image, it fails on sboot.bin. Every image that includes sboot.bin fails on sboot.bin so far. I -really- don't know what to do.
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
viper31573 said:
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
Click to expand...
Click to collapse
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
skiahmutt said:
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
Click to expand...
Click to collapse
not sure what else to tell you that would help
viper31573 said:
not sure what else to tell you that would help
Click to expand...
Click to collapse
Well, the best place I can think to start is to nail down exactly what's happening, then try to figure out WHY it's happening. Once I know the what and why, the solution should be apparent. While I'm not against someone chiming in with a fix that works but I don't understand, I'm here to learn, and would like to come to a better understanding of the issue.
First: what is sboot.bin?
Second: do I need a specific sboot.bin for a specific ROM?
Third: what can cause sboot.bin to fail?
Fourth: is there a way to push just sboot.bin to the phone through Odin or other software?
Fifth: am I fixating on sboot.bin when it's not my issue?
Sixth: did you really read my whole post and get to this point? Wow, thanks! I appreciate you taking the time to try and help me, folks like you are what make the community so strong!
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
viper31573 said:
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
No worries. Thanks for the effort at least!
Okay, a bit of an update... I unzipped and removed sboot from a couple of the ROMs I have, and they flashed successfully, but the phone still hangs on the "Samsung Galaxy Note II" screen... I feel like I'm on the verge of figuring this out, I -know- it's got something to do with sboot now.
Can I write JUST a bootloader to the phone without writing anything else? If so, how?
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
also try flashing the pit file.
mike7728 said:
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
Click to expand...
Click to collapse
I think it was the 4.3 update. So, what's the knox bootloader, and what ROM can I flash to the phone that'll work with the knox bootloader?
For starters (so there isnt misunderstandings )
1) I'm complete noob who's successfully rooted few times with root/custom ROMs, but I'd be very grateful if you can still break down explanations to their simplest (I usually use the site http://galaxys4root.com/ to help me)
2) My device is Samsung Galaxy S4 (Verizon), SCH-i545, Android Jelly Bean 4.2.2. Unfortunately, I'm not even sure what build I have since I have no clue where to find it, but if someone can direct me, I'd be glad post it
3) I originally rooted my phone according to the steps in the link http://forum.xda-developers.com/showthread.php?t=2380325 and it worked fine
I did a factory reset on my phone after failing to "move my downloaded apps to my external sd card with Root Explorer (a root app)". Apps couldn't open and home page lagged/glitched. The reset was successful, but I still had SuperSU from root, and also wanted to update to 4.3 to rid the update message that kept popping up. I used Odin, but that's when trouble started. Every Odin tutorial I went for unrooting S4, said that the first box to the left was supposed to be yellow when the phone connected, but mines stayed blue (see image attachment)
I redownloaded Odin/SAmsung USB Drivers thinking they were out of date, but it didn't do anything. When I tried going into Android Sys Recovery Mode (press volume up/home/power button then release power button) It told me "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried downloading Kies and updating, but it didnt even detect my phone. I've tried flashing every stock firmware I've found, but nothing works.
Thing is, I dont even know if I'm soft or hard bricked (or just plain noob ) but I can go into Odin mode just fine, I just have to take out the battery every time and wait a few minutes. However, I cannot go into the sys recovery mode, since all I get is the Kies message. Also, when I just normally turn on my phone, it automatically goes straight to sys recovery.
If anyone can help me resolve this problem, I will be very much appreciated. Thanks for reading the long post! XD
nyankat said:
For starters (so there isnt misunderstandings )
1) I'm complete noob who's successfully rooted few times with root/custom ROMs, but I'd be very grateful if you can still break down explanations to their simplest (I usually use the site http://galaxys4root.com/ to help me)
2) My device is Samsung Galaxy S4 (Verizon), SCH-i545, Android Jelly Bean 4.2.2. Unfortunately, I'm not even sure what build I have since I have no clue where to find it, but if someone can direct me, I'd be glad post it
3) I originally rooted my phone according to the steps in the link http://forum.xda-developers.com/showthread.php?t=2380325 and it worked fine
I did a factory reset on my phone after failing to "move my downloaded apps to my external sd card with Root Explorer (a root app)". Apps couldn't open and home page lagged/glitched. The reset was successful, but I still had SuperSU from root, and also wanted to update to 4.3 to rid the update message that kept popping up. I used Odin, but that's when trouble started. Every Odin tutorial I went for unrooting S4, said that the first box to the left was supposed to be yellow when the phone connected, but mines stayed blue (see image attachment)
I redownloaded Odin/SAmsung USB Drivers thinking they were out of date, but it didn't do anything. When I tried going into Android Sys Recovery Mode (press volume up/home/power button then release power button) It told me "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried downloading Kies and updating, but it didnt even detect my phone. I've tried flashing every stock firmware I've found, but nothing works.
Thing is, I dont even know if I'm soft or hard bricked (or just plain noob ) but I can go into Odin mode just fine, I just have to take out the battery every time and wait a few minutes. However, I cannot go into the sys recovery mode, since all I get is the Kies message. Also, when I just normally turn on my phone, it automatically goes straight to sys recovery.
If anyone can help me resolve this problem, I will be very much appreciated. Thanks for reading the long post! XD
Click to expand...
Click to collapse
Looks like you connected in Odin. Flash you stock recovery .tar using PDA ONLY.
Use this link to download the factory image fr the build that your on. You can find out what build your on by going to settings->about phone. Unless you have flashed a modem/radio your current build will be listed under "baseband" it sounds like your on me7 but double check before you download and flash. Fell free to post any other questions. I'll keep an eye out in case you need more help. http://forum.xda-developers.com/showthread.php?t=2301259
[GUIDE] No-Wipe Factory Images (Restore from any soft-brick without wiping data)
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Shaftamle said:
Looks like you connected in Odin. Flash you stock recovery .tar using PDA ONLY.
Use this link to download the factory image fr the build that your on. You can find out what build your on by going to settings->about phone. Unless you have flashed a modem/radio your current build will be listed under "baseband" it sounds like your on me7 but double check before you download and flash. Fell free to post any other questions. I'll keep an eye out in case you need more help. http://forum.xda-developers.com/showthread.php?t=2301259
[GUIDE] No-Wipe Factory Images (Restore from any soft-brick without wiping data)
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Click to expand...
Click to collapse
Oh wow......turns out that I just didn't flash the right .tar file and didn't use PDA. Thanks for helping out! And to think I got so worked up over it....
nyankat said:
Oh wow......turns out that I just didn't flash the right .tar file and didn't use PDA. Thanks for helping out! And to think I got so worked up over it....
Click to expand...
Click to collapse
No problem. Always be extra careful when using Odin. Sounds like you might have got lucky. That's one of the easiest ways to hard brick is flashing wrong file or from non pda., from what I've read.
Glad I could help though.:beer:
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
This firmware is the unmodified Lollipop (Android 5.0) firmware downloaded through Samsung Kies. In case you need a copy of the firmware so that you don't have to keep downloading it through Kies, I'm providing you with a copy via the link below. It's odin flashable. Use the "AP" or "PDA" button to flash it onto your phone.
1. Download the stock Android 5.0 ROM (Lollipop) - Sprint N900P ONLY! - androidfilehost.com/?fid=24391638059060029
2. Download the official Samsung Kies. - samsung.com/in/support/usefulsoftware/KIES/
3. Download Odin 3 or later. - samsungodindownload.com/download/
4. Open Samsung Kies, and connect your phone. Wait for it to install the needed drivers.
5. Open Odin and make sure that it says it's "Added!"
6. Click the "AP" button and open the downloaded ROM.
7. Wait for it to finish verifying the checksum.
8. Make sure that "Auto Reboot" and "F. Reset Time" are the only boxes checked. (The default)
9. Click "Start" and wait for it to go. (Sometimes it gets stuck when it says "Setup Connection" and then you need to unplug your phone and restart Odin. - BE CAREFUL! Make sure it really is stuck or you'll brick your phone!)
10. [Optional] Flash TWRP (twrp.me) or CWM. (clockworkmod.com) TWRP is more free than CWM in the sense that the CWM ROM Manager has a payware version. If you're feeling generous towards those who spend countless hours each day for fun and to make your life a bit easier, throw them a few bucks. Both are freely available.
WARNING: Odin can brick your phone if you don't know what you're doing. If you break it, just buy another $800 device. I'm providing these instructions and the ROM without any warranty. You do with them what you feel is best.
That this is a zip file, it is not seen my Odin.
THANK YOU THANK YOU THANK YOU! You helped me save what I thought was a dead phone with this!
Is there a mod to change the launcher to 5x4
mac01843 said:
That this is a zip file, it is not seen my Odin.
Click to expand...
Click to collapse
Not sure if you've figured it out yet but you'll have to extract the .tar file from the zip, then Odin will be able to see it, the .tar file that is.
Thank you, thank you, thank you. This totally saved my bacon after a moron at the Sprint Store (and perhaps me for letting him look at it) replaced the SIM and then said that there was nothing they could do for the phone since it had been rooted.. now I have a way to reactivate the phone before switching back to a decent ROM.
This worked like a charm!
Anyone have a mirror?
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
can I keep it unlock?
Can I keep my KITKAT 4.4.2 NOTE 3 Sprint unlocked after updating this stock firmware? I'm newbie and English is not my mother tongue.
Yes you can!
Anyone? On CM as well and would looove to have an Odin flashable Stock ROM
tusker559 said:
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
Click to expand...
Click to collapse
Or maybe point me (us) in the direction of finding something similar?
Anyone else getting invalid MD5 checks in ODIN with this one? Does anyone have an valid download link? Trying to switch back to Stock so I can pull the 6.0 OTA and fix my GPS issues.
Edit:Georgia Mirror is valid
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
iletumi said:
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
Click to expand...
Click to collapse
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
how did you access the georgia mirror?
404 error on file link.
Nevermind. Tried again and it downloaded.
misterkatanga said:
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
Click to expand...
Click to collapse
Factory reset and it works now! Thank u!!!!