My Phone sprint S3 SPH-L710 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that. Okay I was advised to try this: forum.xda-developers.com/showthread.php?t=1840030. I never got the first bootloader to "pass" but somehow after I did it I was able to boot in to download mode. I tried to flash the second bootloader and it wouldn't even show up in the PDA line in Odin. I really need to get my phone working again as it's my only one I have and I'm traveling either later today or tomorrow.
Related
This is a very noob thing to do.
I have a Verizon S3 with a broken screen. So I was fooling around with it without reading the forum.
I have a fresh MF1 installed, then rooted and also installed ROM Manager. The foolish thing is that I used ROM manager to boot into recovery.
The boot failed. Now the stock recovery is gone. The worst thing is that, now I can't even get into Odin. The phone kept vibrating and give the yellow triangle, saying, System software not authorized by Verison wireless has been found on your phone.....
I do not know what to do now. I think the first thing I have to do is to get rid of the CWM recovery, which never worked in this case. Then I can get the Odin back.
I tried the download button combo. I got to Odin just once. And the Odin session did not complete stating that it could not find a COM port. So Odin is no go now.
Do I have to get on adb or bootloader level? How?
deleted.
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
BaSingSe said:
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
Click to expand...
Click to collapse
You got that warning message at boot because you didn't unlock your bootloader.
Sent from my SCH-I535 using Tapatalk
Alright, I was running LiquidSmooth 4.4.4 rom when I got an OTA update from them. I downloaded it and when to install it, and ever since, my phone will only boot to the liquidsmooth splash screen and just sit there. I tried to use CWM to recover to my last backup, and now it's completely gone. I'm back to download mode only, not CWM recovery. I figured I'd at least get the phone working and use Odin 3.07 on Windows 8 to flash it. Downloaded drivers for the verizon version of the GS3, installed, rebooted and set to work. Well, Odin won't see my phone. At all. I don't know how to make it connect so I can flash it. Anyone got any advice?
I have kies installed, but it isn't running.
I cannot boot into my phone whatsoever.
I had the usb repaired, and it will charge when plugged in and off.
Someone please help. It's been two weeks and I've tried everything I can think of.
Eroth said:
Alright, I was running LiquidSmooth 4.4.4 rom when I got an OTA update from them. I downloaded it and when to install it, and ever since, my phone will only boot to the liquidsmooth splash screen and just sit there. I tried to use CWM to recover to my last backup, and now it's completely gone. I'm back to download mode only, not CWM recovery. I figured I'd at least get the phone working and use Odin 3.07 on Windows 8 to flash it. Downloaded drivers for the verizon version of the GS3, installed, rebooted and set to work. Well, Odin won't see my phone. At all. I don't know how to make it connect so I can flash it. Anyone got any advice?
I have kies installed, but it isn't running.
I cannot boot into my phone whatsoever.
I had the usb repaired, and it will charge when plugged in and off.
Someone please help. It's been two weeks and I've tried everything I can think of.
Click to expand...
Click to collapse
Try to find a Windows XP PC instead...
well through sheer will and button pressing, I managed to persuade the tech gods to open a hole in the sky and allow me to get back into CWM. I'm restored and up and running again. Chalk it up to "No idea what broke, no idea what fixed"
/thread closed.
Hey guys so my phones kernel and stuff was slightly messed up I know this because wifi didn't always work and it wouldn't work at certain places and if I reset the phones settings or factory the wifi would show up. I then thought hey I need wifi so let me put a custom mod on it. I have rooted my phone easy but never put a custom mod.. I still dont know what it does or what a custom recovery is or whatever. I tried odin and it said failed a bunch of times. I then started trying to use apps like goo manager and busy box and such and had no idea what i was doing other than following instructions blindly and I ended up using an app that was glitched I believe and when ever I started the phone it went into recovery mode. Then I stopped using the phone for a quite a while and one of my friends said he could look at it and determined that it is screwed to the point of no return. So I thought why not go for one last swing at it did some more Youtbing and did another tutorial another tarp or md5 file or whatever it is. I now have that screen which says connect to Kies for emergency firmware recovery or something. I can still access download mode and such but the main problem is 1. odin is still not working 2. Kies is now not recognizing my S4 keeps telling me it doesnt recognize it. I have a Samsung S4 verizon build number is 2g6 I believe I know the ending is 6. Its curruntly on 4.4.2 kit kat.
TLDR: The phone says that i need to hook it up to kies for emergency firmare something but kies wont recognize my phone and I cant do a hard reset and When I flash with Odin it always says Fail when it gets to the boot part
Thanks so much guys you dont know how much any help would be. Please respond this is all I will be doing all day so I can give you all extra info asap.
My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.
congaman59 said:
My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.
Click to expand...
Click to collapse
see this
Newest odin
flash- said:
see this
Click to expand...
Click to collapse
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?
congaman59 said:
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?
Click to expand...
Click to collapse
install the version they work on it in the guide ..look for it ...you shall find it somewhere
having driver problem
Oden3 ver3.09 to do what you said. I still can't get the usb driver to work with my computer and phone. It is a SPH-L710 on sprint.
Okay got the driver but getting FAIL
I got the driver to work after I got the phone in to download mode. However every time I try to flash the VRALEC bootchain I get a fail. I have the phone in download mode.
got first bootloader to run. But
I got the driver to work after I got the phone in to download mode. I think I got the first bootloader to run even though it failed every time I tried to flash it. I however can't get the second one to even show up in Odin!
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
ton8_22 said:
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
Click to expand...
Click to collapse
You sound like you have a problem similar to what I had.
I was downloading 6.01 to install using KIES 3 and got no recognition from my Windows 7 based computer when I connected up and ran KIES.
I had the Sammy 1.55.5 USB drivers installed.
What I did it was use KIES,not KIES 3.
Samsung says KIES 3 but that turned out to be wrong in my case,although I'm not sure why?
I'm now running M/M and happily gutting the bloat out of it.
It feels better than new now!
Solved
Anyway, I already solved it!
ton8_22 said:
Anyway, I already solved it!
Click to expand...
Click to collapse
i have the same problem....
how did you solve it?