I installed the original file using TWRP the day it came out. Now the phone wants to OTA update everyday. It's driving me nuts. How can I fix this? I've already rooted the phone and installed FK kernel which I'm sure isn't helping. Any reply would be greatly appreciated. THANKS!
Exactly which update did you install? There were two, the major YNG1TAS0YL and the incremental YNG1TAS17L. So if you only installed the first one you still have the incremental to go.
XDA Moderator
Transmitted via Bacon
As timmaaa said, your probably getting the incremental update that was released a couple of days after CM12 was released. I also get that update constantly.
Related
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
Hi there,
I am wondering what's up with the incremental update model adopted by OnePlus. I would appreciate if anybody would explain and this would be helpful for others having the same or similar questions.
Here is the scenario:
I received the phone with 22R version of the ROM. Since then I did not install the updates.
Under the Settings -> About Phone -> System Updates, it is always showing the 25R as the available update and not the latest.
When I raised a ticket with the OnePlus team regarding why the latest version is not being shown, here below is the response I received:
Have you already tried a Hard reset on your device? If not, here's how to do it:
1. Back up all your important files and information, as the process will erase all data
2. Shut down the phone, and turn it back on while holding the Volume Down button until you feel it vibrate
3. Once in Simple Recovery, select "wipe cache partition" and swipe to the right or press the power button
4. When you get the "Cache wipe complete" message, continue and select "wipe data / factory reset" to fully reinitialize your ROM
Click to expand...
Click to collapse
However, I do not quite understand why I would need a hard reset of the phone to see the latest updates. Anyway, my questions are as below:
1. What is this incremental update model is all about?
2. Is it that we cannot update to the latest version unless we go through all the incremental updates?
3. In one of the posts about updating to 38R version (latest as of this writing) needs to be done on top of 33R only.
4. What would happen if we update from 22R to 38R?
Any answers that would give an insight are appreciated.
Thanks.
This is standard procedure. This is how most phone companies roll out their updates usually. This is how OTA updates work.
An OTA update is not a complete system, it's a patch that needs to be applied to the correct preceding build. That's why they need to be taken in the correct order. I don't see what your problem is though, just take the updates in order and you'll be fine.
Transmitted via Bacon
I understand it is a standard procedure, but I have not seen that the latest update would only be shown after all the previous updates taken. It does not make sense.
Let's say there are ten incremental updates have come and the user would want to update the tenth version (assuming that the user had not taken previous update releases).. then he would not need to go through the hassle of updating all the previous update releases to take up the latest.
From your explanation, does it means he has to update the phone ten times?
On the other hand, in the case of OnePlus One, what would happen if the user want to update from 22R to 38R?
Sent from my SGH-M919 using XDA Free mobile app
uresh.kuruhuri said:
I understand it is a standard procedure, but I have not seen that the latest update would only be shown after all the previous updates taken. It does not make sense.
Let's say there are ten incremental updates have come and the user would want to update the tenth version (assuming that the user had not taken previous update releases).. then he would not need to go through the hassle of updating all the previous update releases to take up the latest.
From your explanation, does it means he has to update the phone ten times?
On the other hand, in the case of OnePlus One, what would happen if the user want to update from 22R to 38R?
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
A user cannot update from XNPH22R to XNPH38R. There is no 22R to 38R. All of them are incremental updates.
XNPH22R -> XNPH25R -> XNPH30O -> XNPH33R -> XNPH38R.
If you hate doing all the updates then simply flash the fastboot images that'll get you to XNPH38R. But at the time 38R factory images aren't out yet, they will be soon. Latest factory image is 33R.
But I agree, OnePlus should be shipping the new devices with at least XNPH33R.
uresh.kuruhuri said:
I understand it is a standard procedure, but I have not seen that the latest update would only be shown after all the previous updates taken. It does not make sense.
Let's say there are ten incremental updates have come and the user would want to update the tenth version (assuming that the user had not taken previous update releases).. then he would not need to go through the hassle of updating all the previous update releases to take up the latest.
From your explanation, does it means he has to update the phone ten times?
On the other hand, in the case of OnePlus One, what would happen if the user want to update from 22R to 38R?
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
I think you're failing to understand how updates work. It makes perfect sense. Yes, the user needs to update ten times because they are patches that build on top of very specific already existing firmware. You can't install 38R on top of anything but 33R.
Transmitted via Bacon
Incremtal 33R-> 38R
Hey
I read about the incremtal updates
My Question is
Why I don't see this update even though I'm looking for it ?
I'm at 33R and I ask CM updater for new updated and Nada
Got OPO chinse version
twrp 2.8.0.1
CM 11 S 33R
thank you
yosef_a said:
Hey
I read about the incremtal updates
My Question is
Why I don't see this update even though I'm looking for it ?
I'm at 33R and I ask CM updater for new updated and Nada
Got OPO chinse version
twrp 2.8.0.1
CM 11 S 33R
thank you
Click to expand...
Click to collapse
You're not seeing the update because not everyone gets it at the same time, it's a staggered roll out.
Transmitted via Bacon
This is normal, if you think this is unbearable. Do a clean install of windows seven right now. You will be getting patches after patches.
Nothing new
zephiK said:
A user cannot update from XNPH22R to XNPH38R. There is no 22R to 38R. All of them are incremental updates.
XNPH22R -> XNPH25R -> XNPH30O -> XNPH33R -> XNPH38R.
If you hate doing all the updates then simply flash the fastboot images that'll get you to XNPH38R. But at the time 38R factory images aren't out yet, they will be soon. Latest factory image is 33R.
But I agree, OnePlus should be shipping the new devices with at least XNPH33R.
Click to expand...
Click to collapse
OnePlus One is currently being shipped with XNPH33R.
So I got my opo last summer and I was sooo excited to get it. I got the invite that morning and at that moment I changed my mine from getting a nexus 5 to getting the OPO. So a few months past and I finaly found out how to root my device and I did everything I could to preserve it. So one day I update my OPO and all of a sudden my Device wasn't rooted anymore! I wasn't completely devastated and everything looked fine. Then another month past and I got a notification for an update I think 33R or something like that so I didn't really care as much so I left it alone. I tried to fix it but nothing. So I didn't care. But now that the OPO is getting the update for android 5.0 soon or maybe its already out I really need to fix this NOW! So if anyone can help it would be the most helpful of you cause I'm starting to think of getting a new phone. But the OPO is such a great phone I don't want to get rid of it for a while. Please help! I really need to know how to fix this!
Just download the updates and flash them sequentially, with a reboot in between each update. You'll find them here
http://forum.xda-developers.com/showthread.php?t=2857110
http://forum.xda-developers.com/showthread.php?t=2906746
Transmitted via Bacon
I'm confused as to what the problem is? If it's not having root anymore, you need to download SuperSU zip and flash that in your custom recovery like twrp our whatever you have.
Every time you do an update the SuperSU file can be flashed, it won't do any harm but it'll make sure you retain root
Sent From Lollipopified Bacon Goodness!
So I'm currently running optipop 5.0.2 and google is trying to push an ota update. I have declined but it still is appearing in my notifications and is downloading in the background. I hadn't noticed it was downloading until my phone alerted my that I had used 3gb in the past 2 days. Is there a way I can stop it from downloading/disable it? I've read similar posts and I haven't really seen a way to stop the wakelock/downloading,just the notification. As I don't have unlimited data, I'd like to stop it if possible. In addition, I have tried to accept the ota to see if it would fix it, but it doesn't install since I am rooted and running twrp.
Any suggestions?
riahim said:
So I'm currently running optipop 5.0.2 and google is trying to push an ota update. I have declined but it still is appearing in my notifications and is downloading in the background. I hadn't noticed it was downloading until my phone alerted my that I had used 3gb in the past 2 days. Is there a way I can stop it from downloading/disable it? I've read similar posts and I haven't really seen a way to stop the wakelock/downloading,just the notification. As I don't have unlimited data, I'd like to stop it if possible. In addition, I have tried to accept the ota to see if it would fix it, but it doesn't install since I am rooted and running twrp.
Any suggestions?
Click to expand...
Click to collapse
? What's Optipop? A custom rom? Then why in the hell is it receiving the official OTA update from Google? Ask the ROM dev.
I know who wouldn't touch that stuff.
beekay201 said:
? What's Optipop? A custom rom? Then why in the hell is it receiving the official OTA update from Google? Ask the ROM dev.
I know who wouldn't touch that stuff.
Click to expand...
Click to collapse
Yes, It's a custom rom. I have no clue why it is receiving an official ota update...
Yeah, I'll ask the rom dev to and see what he says.
Phone is S-off, Rooted
Running Android 5.0.1
TWRP 2.8.5.0
My screen prior to going into recovery states: Software Status "Official"
I'm getting the VZ software update notifications. Does anybody have any idea what this update is for? When it has tried to auto update in the past, it has failed, which is expected.
Wasn't sure I needed to bother with updating my phone or grabbing an updated ROM for anything groundbreaking.
Thanks!
paulsoncpa said:
Phone is S-off, Rooted
Running Android 5.0.1
TWRP 2.8.5.0
My screen prior to going into recovery states: Software Status "Official"
I'm getting the VZ software update notifications. Does anybody have any idea what this update is for? When it has tried to auto update in the past, it has failed, which is expected.
Wasn't sure I needed to bother with updating my phone or grabbing an updated ROM for anything groundbreaking.
Thanks!
Click to expand...
Click to collapse
We need more info than that. There are two 5.0.1 versions already out.
Sent from my Nexus 6 using Tapatalk
dottat said:
We need more info than that. There are two 5.0.1 versions already out.
Nevermind, just googled the OTA software update number (4.17.605.5_R4) and it relates to Stagefright patch. I am currently on 4.17.605.5
Is it something to be concerned with leaving as is or go ahead and update?.
Thanks
Click to expand...
Click to collapse