Hello all,
A friend of mine has a galaxy note 2 from AT&T. I'm not clear as to what exactly he did but he says he had it unlocked and had custom firmware on his phone and the phone did an update on its own and locked up, but by looking up on the Internet all signs point to a soft brick. The phone only turns on and displays firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. My dumb as volunteered to help him as I thought how hard could this be? Anyway Kies failed to help. Secondly I followed the instructions on here as far as downloading Odin, downloaded stock firmware, downloaded Samsung drivers. I plug it in a all appears good in Odin. Mp5 file checks OK and once it starts running there is even a progress bar on the phone showing its downloading but once it gets to the end it fails every time. The screen on the phone displays
Odin Mode
Product name sgh-I317
Current Binary Samsung official
Current status: custom
Knox warranty void: 1
RP SWREV: A3
SW REV: invalid magic string
Any help would be appreciate I've almost had it with attempting to help. He apparently didn't know what he was doing now I obviously don't know what I'm doing.
Thatguycurt said:
Hello all,
A friend of mine has a galaxy note 2 from AT&T. I'm not clear as to what exactly he did but he says he had it unlocked and had custom firmware on his phone and the phone did an update on its own and locked up, but by looking up on the Internet all signs point to a soft brick. The phone only turns on and displays firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. My dumb as volunteered to help him as I thought how hard could this be? Anyway Kies failed to help. Secondly I followed the instructions on here as far as downloading Odin, downloaded stock firmware, downloaded Samsung drivers. I plug it in a all appears good in Odin. Mp5 file checks OK and once it starts running there is even a progress bar on the phone showing its downloading but once it gets to the end it fails every time. The screen on the phone displays
Odin Mode
Product name sgh-I317
Current Binary Samsung official
Current status: custom
Knox warranty void: 1
RP SWREV: A3
SW REV: invalid magic string
Any help would be appreciate I've almost had it with attempting to help. He apparently didn't know what he was doing now I obviously don't know what I'm doing.
Click to expand...
Click to collapse
Sounds like you are trying to install a version of the firmware that is older than the one that was on there. What is the build version that you are trying? What step is it failing at in Odin? I'd recommend getting the newest version of 4.4.2 to avoid the risk of trying to downgrade.
Odin fails right at the end. I see a green progress bar on the phone as well as on my pc screen. I'm at work right now so I'm not too sure as to exactly what or where it fails. What firmware do you recommend I attempt to place on it? Thanks for your reply also, I appreciate it.
Thatguycurt said:
Odin fails right at the end. I see a green progress bar on the phone as well as on my pc screen. I'm at work right now so I'm not too sure as to exactly what or where it fails. What firmware do you recommend I attempt to place on it? Thanks for your reply also, I appreciate it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
es0tericcha0s said:
http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
Click to expand...
Click to collapse
Which one do I pick?
Ok...update....
After using Odin to put this firmware on AT&T UCUCNE5 i317 Stock ODIN Note 2 the phone actually rebooted when finished and seemed like everything was normal. However it shows Samsung Keyboard has unfortunately stopped working every ten to fifteen seconds and will not stop. I tried clearing data and cache of the Samsung keyboard app and that did not work. I tried factory and data reset of the phone as well as wipe partition cache and none of that worked. Any suggestions?? I couldn't do anything so I
managed to use a Bluetooth keyboard to go to play store and download new keyboard app but I'm using my google account for that and I personally don't want him having my account on his phone.
I apologize for all the troubles, I'm trying to help him out and didn't realize I was in over my head with no experience on this.
Thatguycurt said:
Ok...update....
After using Odin to put this firmware on AT&T UCUCNE5 i317 Stock ODIN Note 2 the phone actually rebooted when finished and seemed like everything was normal. However it shows Samsung Keyboard has unfortunately stopped working every ten to fifteen seconds and will not stop. I tried clearing data and cache of the Samsung keyboard app and that did not work. I tried factory and data reset of the phone as well as wipe partition cache and none of that worked. Any suggestions?? I couldn't do anything so I
managed to use a Bluetooth keyboard to go to play store and download new keyboard app but I'm using my google account for that and I personally don't want him having my account on his phone.
I apologize for all the troubles, I'm trying to help him out and didn't realize I was in over my head with no experience on this.
Click to expand...
Click to collapse
You'll need to install a custom recovery, use that to wipe the system partition and data reset again then immediately reboot to Download Mode and reinstall the NE5 update.
You sir have been very helpful and I can't thank you enough. I was clueless coming into this thinking I could help my friend effortlessly but that was not the case. I've never had the intentions of rooting a phone or placing a custom mod on one but honestly now I'd like to try it lol!! With your help and this website I was able to fix his phone. I can't thank you guys enough. You're awesome!!!
Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Sportsmaniac13 said:
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Click to expand...
Click to collapse
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Skipjacks said:
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Click to expand...
Click to collapse
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Sportsmaniac13 said:
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Click to expand...
Click to collapse
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Skipjacks said:
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Click to expand...
Click to collapse
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Sportsmaniac13 said:
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Click to expand...
Click to collapse
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Skipjacks said:
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Click to expand...
Click to collapse
Okay. Thanks for the help anyways, I appreciate it.
Sportsmaniac13 said:
Okay. Thanks for the help anyways, I appreciate it.
Click to expand...
Click to collapse
OK, you've been moved to the Verizon forum.
The OTA failing quickly as you describe usually means that one of the files that the OTA is trying to update has been modified.
What you should do is figure out what build your phone is running (Settings, More, About phone, then look at "Build number").
That will tell you what you need to flash to restore the phone to stock, hopefully with a no-wipe image.
Thanks for all your help guys. I finally solved the issue, so I figured I'd post how I did it in case anyone else runs into something similar.
I actually updated the phone through Verizon Software Upgrade Assistant. I'm assuming that through doing this I flashed the phone back to stock. Once this was over, the phone notified me of another update, and this time everything went smoothly. The phone is now completely stock and completely up-to-date.
So if anyone has a similar problem, give Verizon Software Upgrade Assistant a shot.
Hi all,
Im new to the forum and did some searching but cant find the info i need. I tried rooting my verizon note 2 to casuals one click and didnt realize i had updated to android 4.3 prior. So it tried to root 4.1.2. Now my phone has the yellow triangle and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried kies and kies 3 and neither one recognizes my phone.The only way to shut the phone off is to pull the battery.When i reinstall the battery i have a brief window to volume down+home+power and it takes me to odin. I saw this problem in the forums for roms but couldnt find anything on rooting.Please tell me i can fix this and go back to stock, and i didnt lock my phone up for good.I know im an idiot and i didnt back up anything. Ive learned my lesson and will do more research before attempting this again.I also realized there is no root for 4.3 yet. My phone was stock before i tried all this. Its the verizon sch-1605.Any help is much appreciated. Thank you!
gilitin99 said:
Hi all,
Im new to the forum and did some searching but cant find the info i need. I tried rooting my verizon note 2 to casuals one click and didnt realize i had updated to android 4.3 prior. So it tried to root 4.1.2. Now my phone has the yellow triangle and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried kies and kies 3 and neither one recognizes my phone.The only way to shut the phone off is to pull the battery.When i reinstall the battery i have a brief window to volume down+home+power and it takes me to odin. I saw this problem in the forums for roms but couldnt find anything on rooting.Please tell me i can fix this and go back to stock, and i didnt lock my phone up for good.I know im an idiot and i didnt back up anything. Ive learned my lesson and will do more research before attempting this again.I also realized there is no root for 4.3 yet. My phone was stock before i tried all this. Its the verizon sch-1605.Any help is much appreciated. Thank you!
Click to expand...
Click to collapse
Couple of things:
- if you've received the 4.3 update, your bootloader is locked and (currently) un-touchable. Don't try to flash, well, anything.
- if you've received the 4.3 update, you've also received Samsung's odius KNOX technology. If you do try to flash anything most things (especially recoveries), you'll trip the KNOX counter and invalidate your warranty (I believe it also means you can't use your phone in enterprise setups that use KNOX)
The good news is that you can restore your phone to working order! You'll need to install the Verizon Software Upgrade Assistant. XDA member scoobysnack posted a link to download the software, though you can also get it from any functioning Verizon Samsung smartphone that's plugged into a computer.
After you've installed the software, turn your phone on and plug it into the computer. Run the software and select the tab on the left column titled 'Repair'. Click on the repair button near the right side and sit back & wait. The software will download the 4.3 OTA and install it. Like ODIN, it is imperative that you not unplug your phone during this process.
If you have trouble getting the software to recognize your phone, it may help to put it into download mode. I had to go through this myself (I foolishly forgot about the bootloader issue and tried to flash a recovery. Sigh).
You can achieve root for 4.3, but there are some serious concerns about Kingo, the software the provides root. XDA doesn't allow links to them due to unanswered questions about privacy concerns due to unusual traffic capture going between the software and (apparently) servers in China
thanks so much. ill try it in the morning when i get off work.
Also when i was in odin and plugged my phone in, the software on the pc didnt recognize my phone either. Is that something i should worry about. I guess the box was supposed to turn green but never did.Many thanks
ok so i got home today and tried downloading verizon software update from the link you gave and it wont open the program. Ive tried on 2 different computers. so i called verizon tech to see if they have it cause i can only find it on the website described eariler, and they said they dont have it. Its only in your phone. Well i cant access my phone to get it and im stumped. They said to go into a verizon store and they should be able to fix it. What are my options? I dont have any data on the phone i need to save so can i just go back to a previous version or wipe it out? Or do i have to do a custom rom? Thanks in advance.
gilitin99 said:
ok so i got home today and tried downloading verizon software update from the link you gave and it wont open the program. Ive tried on 2 different computers. so i called verizon tech to see if they have it cause i can only find it on the website described eariler, and they said they dont have it. Its only in your phone. Well i cant access my phone to get it and im stumped. They said to go into a verizon store and they should be able to fix it. What are my options? I dont have any data on the phone i need to save so can i just go back to a previous version or wipe it out? Or do i have to do a custom rom? Thanks in advance.
Click to expand...
Click to collapse
When you go into ODIN mode (turn off your phone, power on using POWER+HOME+VOL-DOWN), do you a line that reads 'KNOX WARRANTY VOID'? It would be in the upper left corner under 'SYSTEM STATUS'.
I ask because if you don't have that line, you didn't upgrade to 4.3 and your bootloader is NOT locked. You should be able to flash to 4.1.2 from ODIN and go from there (CASUAL to unlock & root, et cetera).
If you do have that line, then your only option is the VZW Software assistant. I'm uploading it now and I'll send you a link via PM. Please keep in mind that if you use the VZW Software assistant, whether your bootloader is currently locked or not, it most definitely will be locked after using it. If you're already locked, no harm done, but I'd make sure first.
Hi
I read many threads in many forums but still hope to get my data back as it represents bits of my life and more important than the phone itself, though some cases were similar but none exactly same plus i care much about my data and I never rooted, messed up with or even tried to do anything like that with my phone
here's what happened in details on my Samsung Galaxy S3 GT-I9300 maybe someone can help me
phone's SSN: -I9300GSMH
Made in Vietnam by Samsung
bought from Egypt where i live, SIM-free, not carrier locked, though i bought it from the carrier's (Orange subsidary in Egypt called mobinil) official store with warranty 1 year that now expired
the old firmware was 4.1.2, i got its build number from colleagues with similar phone bought same time as me I9300XXEMF6
here's what happened:
1- OTA firmware upgrade notification, downloaded package, options were cancel , install and install all package(somthing like that)
2- unfortunately chose install all package(yes i didn't read so i donno which version this was installing) and scheduled to start 5:20am
3- at 10:30am phone screen showing "starting apps"
4- after more than an hour still the same so i rebooted
5- stuck at samsung blue splash screen logo
6-removing battery and back in didn't help even for more than an hour, Samsung Kies won't recognize the device
7- Recovery mode give strange behaviour, didn't find similar in any forum, it brings the green droid man with a counter (like installing or loading somthing) reaches 27% exactly then this droid man flips on its back, red exclamation sign triangle on its belly and it dies, here's the ling to small video showing my mobile doing this
"https://drive.google.com/file/d/0B0RJAWx6Ec-MUUlncVdjWFp0c1k/edit?usp=sharing" (there's no spam in the link, so plz just copy paste in browser to view, this is important to help show my problem)
yes that's RECOVERY MODE-->phone reboots itself coming back to stuck at samsung logo
there are no options, no menu on recovery mode just the after pressing the (Vol Up+home+power) combination it starts by itself this loading something till it dies and restarts, it doesn't give me any options or any control or allow me to interfere
yes download mode is working but i really hope there is another option than flashing the mobile and loosing everything, my whole life history that was on the mobile
praying God someone can help find me something to make it continue past the 27% or even go back to normal without loosing any of my stuff
really looking forward to your support..i'll be waiting for it b4 i do anything
many many thanks
Flash firmware with Odin and next time back up you're data.
Thanks andrewwright
if you just could be more specific..is this the only solution?
if yes, then which firmware version to flash that won't risk loosing my data? 4.1.2? or a newer version?
please if anyone else with less risky suggestions,,please your help is highly welcome
Flash a custom recovery like philz, use aroma file manager to save your data to external sd card.
Go read and learn how to do this from philz thread in original development.
This won't enable your phone to boot, but might save your data -if it is still there.
Sent from my GT-I9300 using Tapatalk
Solved:good:
Hi all
Odin 3.09
and latest Egypt firmware 4.3 for the GT-I9300 from samfirmware .com solved everything... i guess 4.3 is the version that this OTA firmware upgrade was eventually taking my phone to but got stuck somewhere during the process
not a single bit of Data lost, everything is there pictures, sms, even the settings
Thank God :angel:
thanks everyone for trying to help
cheers
Wasn't sure if it would wipe you're data or not. Some do some don't. Can't tell the outcome till its done. Glad you solved you're problem.
Sent from my GT-I9300
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk