Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I just put my 3 XL back to stock before selling it. I like my little 3a so I'm keeping this one.
I had to unlock -> flash factory firmware -> relock. Data is wiped definitely. You cannot downgrade with an OTA it will absolutely need reflashed and wiped with a factory image.
jmtjr278 said:
Anyone been able to revert to Android 10 from the developer preview without unlocking and using factory images? OTA back to Feb not working for me. Am I screwed into using it untill March OTA comes out since it will be newer? Any help would be appreciated
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I'm not surprised that you can't go back to the Feb OTA update and this means that the March OTA update isn't going to work either.
The "issue" is the fact that you have changed major Android versions - from Android 10 to Android 11. You can generally move to a higher version using an OTA update, but you can't downgrade or move back to a lower version without flashing a factory image. Even if the image is pushed out via an OTA update (like would happen if you revert to stock from a beta release), the phone still has to go through a factory reset to ensure everything is downgraded to the lower version. This is something that the regular monthly OTA updates aren't set up to do.
Long story short, you have two options - one is to go ahead an unlock the bootloader and flash the Android 10 factory image. The second is to wait until the Android 11 beta program starts, enroll in it and install the Android 11 beta, and then opt out of the program and be reverted to Android 10. To be honest however, I'm not 100% this will work because I really don't know if you can move from the Android 11 Developer version to the Android 11 beta version via an OTA update. In either case, you are going to experience a factory reset and loose all of your data and information, so plan ahead and backup anything you want to keep.
Solved. Unlocked bootloader, flashed factory Feb. Relocked. All set. Had issues work some apps and Android pay. All expected.
Sent from my Pixel 3a using Tapatalk
Related
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.
Right now I'm using 5.0.1
Kernel 3.4.0
Build Number LRX21Y
Software D85020f
Security Version MDF v1.1 Release 2
Am I completely up to date? Thanks guys.
Newest version is this
It updates security and adds volte
insanenyc said:
Newest version is this
It updates security and adds volte
Click to expand...
Click to collapse
My phone won't let me update it OTA or through LG tools. Keeps saying this phone has been suspected of rooting. I tried factory reset but it gave me the same result. How can I update and get around this thing knowing I was rooted? I'm not even sure how it knew because I went to stock without adding any accounts or apps -_-
jlgarr86 said:
My phone won't let me update it OTA or through LG tools. Keeps saying this phone has been suspected of rooting. I tried factory reset but it gave me the same result. How can I update and get around this thing knowing I was rooted? I'm not even sure how it knew because I went to stock without adding any accounts or apps -_-
Click to expand...
Click to collapse
Follow my G3 back to stock guide.
Sent from my iPhone using Tapatalk
I'm running a completely stock Nexus 5 that has never been rooted. It's gotten all updates going back to my purchase in November 2013, but has recently missed the last two security updates; still sitting on Build MMB29V (March 1, 2016), I've missed the midMarch and April updates. Any idea how I get back into the Google update queue? Don't think it's a matter of impatience. I know I can manually apply updates, would prefer to stay OTA. I've cleared the cache in Recovery as well as checked for updates while in Safe Mode. No go. Any other ideas?
You can sideload OTA via adb. That's very simple.
Sent from my Nexus 5 using Tapatalk
Very simple indeed, updated without a hitch and no user data erased. Glad I now know the process. Many thanks.
Enrolled in the google beta program but I'm not getting the ota for my pixel 2. It's been 72 hours. I got the ota for my pixel c within minutes. Anyone know how to force the ota or something?
It appears that people on the November security patch for 8.0 are not getting the 8.1 beta OTA pushed to them. Most likely need to wait for DP2 at this point.
Hopefully the preview 2 comes out soon.
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
You were on November security patch?
gm007 said:
You were on November security patch?
Click to expand...
Click to collapse
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
flakmunkey said:
Did the novembver security patch require any weirdness to get? I only ask because while i'm not sure if I had that installed, I do know for sure I had all of the most current OTA updates. I got the phone from Best Buy last Thursday and there was a software update when I first booted it. I check for new software this morning and it told me I was up to date. I then proceeded to sign up for the beta program, refreshed the update page that said I was up to date, and the 8.1 update was waiting for me
Click to expand...
Click to collapse
Some people didn't get November update and i read somewhere that they pulled the 8.1 preview for pixel 2 , that's why I'm asking.
http://www.androidpolice.com/2017/1...android-8-1-developer-preview-factory-images/
flakmunkey said:
I just signed up a few minutes ago, refreshed the system update screen on my pixel 2, and the update popped right up
Click to expand...
Click to collapse
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
mrnovanova said:
Well I'm 4 days in and still no ota ?
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
If it makes you feel any better I am in the same situation. 4 days no OTA. I am on the November Security patch.
Is it worth it to try flashing factory images to get back to September and then try to get the beta OTA?
I can confirm rolling back to September images does allow you to immediately get the prompt to download the 8.1 beta.
If you are impatient like me, it's worth a shot.
I will add this: Make sure your ADB and Fastboot are up to date! I ended up softbricked/stuck in the bootloader for awhile after flashing back to the September images. I finally figured out my old version fastboot was the problem. After getting the latest fastboot/adb it was a breeze.
I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.