Stuck in "loop" after OTA 2.3.5 update on rooted Photon. Any way to get out of this?
Just curious if anyone knows any trick to get out of this loop.
I've got a rooted photon with 2.3.4, and I've been getting the notification to update to 2.3.5 from Sprint.
The message states that "a new update is available for your phone", and I've just been clicking the "install later" option because I know it doesn't work if my phone is rooted and I have a custom boot loader.
So I think this morning when my alarm was buzzing to wake me up the software update screen popped up and I accidentally clicked "Install now" when I was trying to snooze the alarm.
It rebooted into my bootloader, says it's trying to apply the update, and then says that it failed.
When I reboot the phone, it boots up like everything is normal, I get to my regular homescreen and then it realizes that the update didn't apply so it restarts immediately into bootloader, and the update fails all over again.
Does anyone know of any way to get out of this loop? Like, there has to be some flag flipped in the main system that's telling it that it needs to reboot to apply the OTA update. Is there a way to turn this flag off so I can keep using my phone like it was?
In the mean time I did a nandroid backup of the current state, and then restored an old nandroid backup from several months ago so I could use the phone for now (which sucks cuz I've made alot of little changes since then).
I haven't been on the site for a while, and I'm really busy throughout the day so I don't really have that much time to search through dozens of old threads, even through I tried looking for similar issues (considering if a fix for this problem exists it was probably discussed when this OTA update first popped up several months ago).
I'm sure this question has been asked a bunch so flame away if you must, but I'm just hoping someone can point me in the right direction if a fix or trick exists to get out of this situation without having to completely wipe my whole phone and start over.
Thank you,
--Hammy
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.
So I have a galaxy S4 that was rooted with build MI1. I started having issues with the screen flashing a green bar when being woken from sleep then turning completely black and staying that way (the phone has never been wet, just dropped lightly in its case). I thought maybe an app messed up something so I decided I should remove root and flash a stock rom so that I could return the phone to verizon if it turned out to be a hardware issue. I followed this guide to completion and the phone no longer has the samsung custom icon when booting up but when updating the firmware it fails each time. Any ideas? Any help would be much appreciated.
Also if you want more details about what my phone is doing here's a link to my original post
You might Samsung's Kies 3 program. Download and install on your computer. When it's finds the phone, you can update to factory settings.
Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
I'm in a same boat
Hey Mate ....!
I'm in a same boat i have tried almost everything Odin seems worked for 30 seconds and than it shows failed. I love this perticuilar handset allot it was gifted to me by very special it was awarded to me by my last company i want to save it please help me if anyone has the solution . What exactly happen to you , Same happen to me exactly same. please update if you get solution. Thanks in Advance.
Regards
Fazal
argethalm said:
Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
Click to expand...
Click to collapse
You might find your answer here I'm not clever enough to post the link so you get it "Longhand".
Go To Forum Galaxy SII General.
Scroll to [Guide} Fix an unflashable or soft bricked GSII (i9100G/P/T/ versions included)
Have a good read through it and if you dare go for it . It's a "back to the future" sort of thing, takes you back to "jellybean" and android 4.1.2. (The route I took anyway)! Good Luck!
same problem here! please help me get my phone back :crying:
argethalm, fazallfrd, ThiagovGuerra
I had same problem - but ....... it was software bricked. Like yours.
If I repair then all of you can repair like me.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808
Everything i take from this link.
You can rebuild with patient.
Hello. I have a 2012 Samsung Tab 2 that was branded for ATT and the model number is SGH 1497. It has been in a drawer for a year and I never use it but I thought I would experiment with it and try to install the Marshmellow Rom even though I am a noob at this stuff. My first problem was that I saw nothing for my version SGH 1497 but I did read on a forum that the Rom 5113 would work for that model. After going through a lot of websites I finally found one that seemed pretty easy and the root process went perfectly for me, no issues at all. I then followed instructions and downloaded the needed files and moved them onto my tablet and all was going well. I was then instructed to boot into recovery mode and that is where my troubles started. I believe it said to hold power and volume down key. Recovery mode would pop onto the screen but then vanish and it would never go into it. So I did more reading and someone had posted that I needed to download the toolkit and re-install a new recovery mode. So I did that just fine and still the same thing happened. I then tried 2-3 more of the other recovery modes and the same thing happened. At that time the tablet would still boot normally. So then I did something else and now my tablet wont turn on anymore. If I push power enough times the Samsung logo will pop onto the screen and then it goes away and that's it. It will turn on to download mode but that is it. Nothing else. Im not upset because I knew this could happen but I surely should have came here first. Is there anything I can do to get this thing back working again or is it hopeless??
Thank you for any help and advice.
Thomas
I was able to fix it by finding the exact same firmware that ATT put on this tablet and then using Odin to flash it. Works fine and is rooted.
Does anyone know of a custom rom that will work on this model sgh 1497??
Thanks.