Can't seem to update to MA7 - Sprint Samsung Galaxy Note II

It seems my phone is stuck on ALJC. I flashed the stock recovery via Odin and did a temp unroot, downloaded the OTA update. The phone rebooted and went to the stock recovery and appeared to be installing the update. Upon reboot, my phone was back in rooted condition (not sure if this is normal for voodoo unroot or not). This has happened twice. The first time it happened I had not noticed it, but now that it has sent a second update request to me today, which I used the same method only to discover that it doesn't seem to work. Now when I request an update it tells me no update is available. Suggestions?

Ignore this thread, I said screw it and just did it all manually.

Related

Need Help

Ok I have the system update that was pushed a few weeks ago. Every time I try to update it it will just go to the home screen and I lose the ability to update for a week when its pushed again. It is a rooted phone but no custom roms. Any ideas why? I called VWsupport and they called HTC and HTC said try wifi or a full factory reset... I don't want to do the reset but I will try the wifi unless someone has a better idea.
You don't need the update since I believe you will lose root once it's installed and there is nothing in the update other than changes to verizon's bloatware like VCAST, etc.
That's strange. Although it makes you (temporarily) lose root, it should still install. However, it wont if you've touched any of the stock apps in any way- those have to be returned to 100% stock status for an OTA to install correctly. If you do get it to go, as long as you're s-off, all you have to do is re-flash clockwork and su to reacquire full root status

[Q] Rooted Inc2 Keeps rebooting

So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
Click to expand...
Click to collapse
Bumping, no one seems to be able to tell me a thing on what this means, what can be done to fix, etc. Any help is appreciated.
Wipe cache, dalvik, and system, then flash a different ROM.
If it continues after that then its likely the phone. And nothing to do with root.
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
Click to expand...
Click to collapse
Any chance you can take a picture of said screen?
What's weird, it sounds like you're describing the stock recovery screen. But you're still able to access CWM?
You probably want to update CWM on the phone and see if that helps out, one thing you want to do instead of changing kernels is re flash the rom again. Once it reflashes wipe data/cache (Do a factory reset basically) as well as the dalvik cache and boot into the ROM without restoring anything.
Just sign into google and see if it stays up and stable at this point, if it does something that's being restored is probably the culprit or a bad app that continuously tries to run.
By the way, the phone comes with stock sense 2.1, above that is sense 3.0
2.3 is the version of android that runs behind sense. Either 2.3.3/2.3.4/2.3.5 are all versions of gingerbread.
Try a different rom, if it continues, it's probably a hardware problem. My wife's first Incredible rebooted constantly, probably upwards of 2 dozen times a day. We had it replaced and the new one has been fine.
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
I thought I read some where that other INC2 users were having similiar issues and it was due to the new android market OTA update.
Edit: Nevermind the other thread here in the forum suggests it could be some kind of HTC OTA update that is messing things up.
WorldOfJohnboy said:
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
Click to expand...
Click to collapse
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
klarson said:
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
Click to expand...
Click to collapse
I am in the process now, but I have had a GB/Sense 3.0 ROM as well as stock GB Rooted, both have ended up doing the same thing. I think I am going to manually cancel the OTA after flashing a new ROM to see if that will stop it from automatically doing so (if that is the issue).
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Conduitz said:
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Click to expand...
Click to collapse
It's not the new market. It has something to do with the OTA's on your phone. Regardless if the OTA was actually downloaded onto your phone or not it's going to fail because the stock recovery is no longer the default recovery which is one of the prerequisites it needs to install.
A wipe is needed to keep this from happening, at least load up the gingersense ROM and that should get rid of the temp OTA file that was downloaded to your phone.
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
WorldOfJohnboy said:
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
Click to expand...
Click to collapse
What i'm hoping is that the OTA files are on the phone and will get wiped with a new ROM. However if they're stored on the SD card all the wiping in the world won't help.
I'm not sure where the OTA files are stored and would like someone to verify for certain if that's the case. I'm just speculating right now on where it's stored but I know the market update is done just like the apps not an OTA.
I also know that the OTA will prompt you for the download. You know the whole download and install now or install later deal?
Well, did a wipe of all things (twice) and installed my fresh ROM. This time after installing all my Apps and doing my restores, etc, I went into the Settings under Software Update and did a check new, it says "No New Software Update Available." Also, under status, it just says the Source is Verizon Wireless, the rest are blank. (I believe at one time, all the fields were populated.)
I am holding out hope that this will work for us. Anyone know of a piece of software, etc. that will log all of the phone's operations? I am curious to see if it is trying to auto-update with OTA software updates.
I'm having the same problem. I can't even get it to wipe because when I start in recovery it goes straight to do you want to start update and if I try to start the phone it restarts and I get the exclamation point. Anyone have any ideas? Thanks!
Update
I took the sd card out and was able to boot to recovery and do a wipe. Phone is working normally for now, how would I go about disabling the OTA's so it doesn't happen again?
I can confirm this is being caused by an ota update. Have 2 inc 2's and both locked up. Both running rmk gingersense. Fixed by clearing cache and davlik. Rebooted phone and saw failed ota update error. Renamed otacerts.zip until rom is fixed. Otacerts is located in /system/etc/security.

Zenfone 2 ZE550ML wont update to latest update 2.18

The update showed up on my phone and so I updated it after unrooting my phone, removing lucky patcher, freedom, sd booster, and so on. After downloading the update, phone rebooted showed it was updating then Error. Rebooted the phone then the update was no longer there, tried using System update but to no avail.
My question is.. how do I fix this for me to be able to update to the latest?
I'm getting a similar problem. However instead of doing what you did to unroot and such, I flashed the 2.17 via their recovery and now I don't get the prompt for 2.18 update at all.
Its confusing as to why its acting like this :/
I already removed all root applications and unrooted the phone then did a factory reset but afterwards it put me to one of its old build and wont freakin update anymore.. Any help regarding this would be very much appreciated..
I am open to rooting and manually flashing the latest build.. Problem is, I was a Sony user whom just switched to zenfone.. So i have no idea how to or what to flash on our zenfone 2..

[ZE551ML] Dead Android bot on OTA update but update was succesful

I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.
you haven't finished , actual OTA is 2.19.40.18
I haven't received that update yet. 2.18.40.12 was the older update and was the one I downloaded/installed.

[ZE551ML] Dead Android bot on OTA update but update was succesful

I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time.
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.

Categories

Resources