I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
OK. So I have flashed back to stock many times and taken the LP OTA. Never had an issue. Just started up first run went through it and hit update when I was ready. Instant OTA showing available for download. Now since I restored to stock again and and now the OTA will not show. Tried the return to stock several times and ATT shows no issue with their update service. Even though I am on Straight Talk and not AT&T they were nice enough to try and work through the problem without success.
Just wondering if anyone else has run into not getting the OTA suddenly and had taken it before.
Thanks.
Hey Guys, quick question...
Its been a couple of weeks that I have a notification from T-Mobile to do a software update.
I'm rooted and running a pretty stock 6.0.1 Rom. I tried seeing what happened if pressed install now.
It restarted and went to my custom recovery and then I just rebooted, once at my home screen I was notified
that the installation failed. Is there any way that i can get this install to complete or if its not recommended,
any way to have the notification to stop pestering me.
Thanks!
Anybody?