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.
Hello guys,
I have owned my samsung galaxy s2 for years now without a problem ( never rooted or anything like that)
As you can probably already tell im not very tech savy. Unfortunetly just recently my phone will not turn on, or to be more precise, it gets stuck on the samsung logo whilst trying to boot up, a quick google search has told me my phone is bricked? I Can access download mode and recovery mode by holding different buttons ( again google)
I dont even care about the phone because its so old now, all i care about is the 500 or so photos I have taken since last downloading the photos off the phone.
From what I have read I need to use ODIN3 or some type of software to basically reinstall the phones software and make it work again but there are a million different sites/videos/advice threads out there and im not sure which one to follow.
most of them start by trying to "wipe user data" from recovery mode? does this mean my photos will be lost?
any help (including just pointing me in the right direction) will be greatly appreciated!
Download stock rom for carrier/country from Samfirmware, flash with Odin in download mode following instructions in thread stickied near top of Q&A titled ' Flash Stock firmware...'
MistahBungle said:
Download stock rom for carrier/country from Samfirmware, flash with Odin in download mode following instructions in thread stickied near top of Q&A titled ' Flash Stock firmware...'
Click to expand...
Click to collapse
Excellent! thankyou, SO just to clarify one more time, i WONT lose any photos?
Probably not, but, you either want a working phone or you don't. That should be the least of your concerns at the moment.
I apologize up front if this is has been previously asked. I found lots of helpful info on here searching through old threads but being a bit of a luddite I was a bit confused exactly which situation applied to me. I live in China and recently bought a s3 I9300I and attempted to root it using the chainfire method from the video on this site. Odin declared success but when the phone rebooted it just went back to download mode with a message at top saying, "Could not do normal boot, ODIN MODE." Turning it off and on, removing battery and retrying Odin flash produce no results. The most important thing of course is just to get the phone back to functioning but I'd also like it rooted if at all possible. I read that using Odin to install a custom kernel would root it and I would not be at all opposed to a good custom kernel. I read something about a binary counter that may need to be reset but that seemed to require doing something with the actual phone functions which don't seem to work. Odin still recognizes it when I plug it in and attempts to let me redo the rooting but it just shows a progress bar then reboots right back into download mode. Sorry if this is basic stuff but I'm kind of terrified of bricking this thing and am just not sure what the best course of action is here. Thanks for any help you can offer.
Chinese stock firmware is different to the international, there is a special thread in general forum on rooting etc.
Do you have a link to that thread? I have looked and cannot find anything that seems specific to this problem.
Please. Searching for "China" or "Chinese" gets me absolutely no relevant results. If this has already been covered can someone please direct me to the thread. I really need to get this phone working and am at a loss. Thanks.
Hi everyone, looking for some guidance here. Ive checked different solutions but I think I've got a unique combination of "dun goof'd"
History:
I have a Canadian (Bell) SGH-I747M that is rooted and was running the latest cyanogen.
Wanted to lend it to a friend who lost his job and needed a phone but he had a deal through rogers and my phone was locked to Bell.
I tried a few of the unlock code steps but I needed to be 4.1.2 or lower for it to work I heard so I tried installing 4.1.2 and thats where it went wrong. I did a firmware update to back it down and mid update it failed.
I can get it into download mode but not recovery. Letting it boot normally gives the message "Firmware upgrade encountered an issue. Please select recovery mode in Keys and try again" I don't think Keys works with cyanogen and even if it did, there is no serial # sticker behind the battery and since I can't boot into settings, I don't know the SN.
When I put it in download mode and try Odin using stockROMS.net oldest or newest image, Odin fails and the phone message is:
ODIN SW REV CHECK FAIL : Fused 2 > Binary 0
So long story short, any help is sincerely appreciated, my ideal state would be a working phone thats unlocked so my buddy can use it. IF that means an older OS, all good. Can I even fix this?? If you need more info I'll keep checking in... THANKS!
Report your own post and ask a moderator to move it to the i747 forum. Anything from this forum could hard brick it
boomboomer said:
Report your own post and ask a moderator to move it to the i747 forum. Anything from this forum could hard brick it
Click to expand...
Click to collapse
Understood - Can an Admin just delete it? I'll report it there.
I am new here so please excuse me if this is the wrong place to post this, however I am in need of some assistance
I have a Samsung Galaxy TAB3 10.1 - GTP5210
I encountered the little android flat on his back, so I have downloaded a number of ROMS that were applicable to the device and used ODIN (different versions) to flash the device. ODIN says it has been successful and the device reboots only to be confronted with the Android flat on his back. I have even tried downloading the JellyBean and KitKat kernels, and used the odin .img to .md5 bat file converter; this also failed.
I appreciate that the tablet is old but it is my daughters and would really like to fix it. There are no option to do recovery etc, I use the power-home-volume down button to get into download mode and then locate the md5 and use odin to flash it;
I would be extremely grateful if someone could help me, as I am at a complete loss as to what to do.
Thank you all in anticipation of anyone replying
I don't think you're going to find a lot of help for a tablet released in 2013. I'd Google "dead Android" with whatever version of Android you're running and see what the Internet tells you.
BarryH_GEG said:
I don't think you're going to find a lot of help for a tablet released in 2013. I'd Google "dead Android" with whatever version of Android you're running and see what the Internet tells you.
Click to expand...
Click to collapse
Good evening, thank you for your response, I kind of searched for that on the internet that has how I came to be here; as "the internet" says use android with the correct ROM and kernel..
So was hoping that someone here would be able to assist, for example could I use a later ROM what kernel do I need?
I have no idea what version I am using as it does not tell me in "download" mode
Also do I flash the kernel first and then the rom or vice -versa
I am not even certain whether I have a partition or not? I am assuming I do given that when I install the ROM it appears to accept it and then just goes into continuous loop.
I appreciate that the tablet is 3 to 4 years old but I would have thought there would still be support out there for it.
Oh just one other thing, I bought a new battery for it and replaced that, just in case it was that.
thanks in anticipation of replies