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.
Related
I searched through other threads but I couldn't find an answer. I was just wondering if OTA updates install all of the updates at once to the latest firmware or if it asks to update each time to the next one.
Thanks for the help!
Updates are cumulative. Each update includes all of the previous ones.
hong90 said:
I searched through other threads but I couldn't find an answer. I was just wondering if OTA updates install all of the updates at once to the latest firmware or if it asks to update each time to the next one.
Thanks for the help!
Click to expand...
Click to collapse
It depends.
Last update was minor one and the size of it did not definitely allow to have all previous updates to be included.
For excample SGS3 last update to 4.1.1 also was different in size OTA vs Kies so ota was just a update and Kies had full rom.
Also when you buy new device you sometimes have to update it many times in a row - meaning they are not cumulative.
laving1977 said:
It depends.
Last update was minor one and the size of it did not definitely allow to have all previous updates to be included.
For excample SGS3 last update to 4.1.1 also was different in size OTA vs Kies so ota was just a update and Kies had full rom.
Also when you buy new device you sometimes have to update it many times in a row - meaning they are not cumulative.
Click to expand...
Click to collapse
Unless the update is adding a good amount of additional apps and feature, the size should be relative small increment between versions. The rule of updating is cumulative unless otherwise noted by the manufacture. As you could see going from ICS .30 version to JB .16 is big (adding Google now, and other stuff) the size jumped from 379,257 to 465,064 (this is already compressed). Another thing you could check is if you downgrade back to .30, what is the OTA version when you boot up?? If incremental is required, you should see .16, then .20 etc...but if you see .23, then that's all you need!
laving1977 said:
Also when you buy new device you sometimes have to update it many times in a row - meaning they are not cumulative.
Click to expand...
Click to collapse
Sometimes they are - in some other thread a direct OTA from 9.4.5.26 to 10.4.4.20 was sighted.
buhohitr said:
Unless the update is adding a good amount of additional apps and feature, the size should be relative small increment between versions. The rule of updating is cumulative unless otherwise noted by the manufacture. As you could see going from ICS .30 version to JB .16 is big (adding Google now, and other stuff) the size jumped from 379,257 to 465,064 (this is already compressed). Another thing you could check is if you downgrade back to .30, what is the OTA version when you boot up?? If incremental is required, you should see .16, then .20 etc...but if you see .23, then that's all you need!
Click to expand...
Click to collapse
When I click the update it doesn't tell me which one it is going to update to. Just current. I'm on .26 right now as it's a new device and I'm just trying to figure out what I need to do in what order to get cleanrom on it. This is prob a noob question but if I update to .23 will I be able to flash TWRP and cleanrom fine? Or should I update to .20 and wait on .23?
Hi,
I still can't update my phone to Oxygen OS or CM12 via the updater app (settings -> about -> Updates).
Do any of you know if and when this is going to be possible ?
Thank you,
Vid
vidra said:
Hi,
I still can't update my phone to Oxygen OS or CM12 via the updater app (settings -> about -> Updates).
Do any of you know if and when this is going to be possible ?
Thank you,
Vid
Click to expand...
Click to collapse
The updates are pushed in batches and hence some have already got it and some are still waiting. They are adding a new functionality similar to ok google (what I have heard) and hence there is a delay. So please wait until you receive the OTA.
You can flash COS 12 manually though.....
Oxygen will not come as an OTA. You will need to flash it manually.
There are several thread explaining the steps to be followed for manual flashing. Please refer those in case you go for manual flashing.
I know.. I know... No OTAs with root... It was a security update so I didnt think much about it until it actually hit me...
It was truly a mistake. I just got back into android after a few years hiatus.
Is there a way to go back without losing anything? Any kind of help would be appreciated!
Stock rom marshmallow. XT1540 1gb. Have TWRP.
Thank you!!
NZed said:
I know.. I know... No OTAs with root... It was a security update so I didnt think much about it until it actually hit me...
It was truly a mistake. I just got back into android after a few years hiatus.
Is there a way to go back without losing anything? Any kind of help would be appreciated!
Stock rom marshmallow. XT1540 1gb. Have TWRP.
Thank you!!
Click to expand...
Click to collapse
Just wipe caches and reboot...
I have rooted device with twrp installed, Do i need to flash stock firmware to update security patch update??
Because i have noticed that any kind of official update failed when we try to flash it on rooted device
amritmalviya said:
I have rooted device with twrp installed, Do i need to flash stock firmware to update security patch update??
Because i have noticed that any kind of official update failed when we try to flash it on rooted device
Click to expand...
Click to collapse
You need to be 100% completely stock to an OTA... Stock recovery, stock kernel, stock system partition... How you get there is up to you.
acejavelin said:
You need to be 100% completely stock to an OTA... Stock recovery, stock kernel, stock system partition... How you get there is up to you.
Click to expand...
Click to collapse
How to get stock system partition?
amritmalviya said:
How to get stock system partition?
Click to expand...
Click to collapse
Really? Restore your pre-root backup with TWRP or flash the stock images from the General Discussion section.
Remember that we do not have images for the latest security patches on some models yet, if you go back to stock, take an OTA, and root, ROM, or do something nasty to your device, there may be NO WAY to recover until, or even if, newer factory firmware images become available.
These updates are just security updates, they are not bug fixes in any way (at least from what has been shown), so there is no real world benefit to applying them if you don't need too. Security updates are mostly just feel good propaganda anyway.
acejavelin said:
Really? Restore your pre-root backup with TWRP or flash the stock images from the General Discussion section.
Remember that we do not have images for the latest security patches on some models yet, if you go back to stock, take an OTA, and root, ROM, or do something nasty to your device, there may be NO WAY to recover until, or even if, newer factory firmware images become available.
These updates are just security updates, they are not bug fixes in any way (at least from what has been shown), so there is no real world benefit to applying them if you don't need too. Security updates are mostly just feel good propaganda anyway.
Click to expand...
Click to collapse
Does a security patch update release mean preparation of naugat for our device?????
Or its just useless?
amritmalviya said:
Does a security patch update release mean preparation of naugat for our device?????
Or its just useless?
Click to expand...
Click to collapse
A security update has no correlation to a Nougat update, we are not getting it, even if we were it would have zero correlation to it... Except you would like need to have it to take the next OTA.
As far as being useless, no it isn't... it does contain some security update, which although they are not really important shouldn't be ignored without a reason, and being rooted/modified MAY be significant enough reason but that is your call. I would read the release notes, if it is just security updates it's probably worth skipping for now, if it is bug fixes or other updates then it is probably worth it to take but use caution modifying your system because you cannot flash a firmware that is older successfully and we don't have the "new" firmware versions yet.
Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*
KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.
If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!
I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.
That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.
If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.
Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1
No idea why this posted twice.
Thanks!
The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.
39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...
My phone doesn't see the May update, it says the April update is the latest one. Can anyone guess why?
daemonspudguy said:
My phone doesn't see the May update, it says the April update is the latest one. Can anyone guess why?
Click to expand...
Click to collapse
I don't know. I never wait for OTA to arrive. As soon as the factory image is available, I download it and flash it manually...so...
There's always a lag before the updates roll out via OTA. I don't even get them because I guess Google sees Magisk and just refuses to offer it so I also download the factory image and dirty flash it.
My son's 4a just got the update as I wrote this post...