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...
Related
Hi everyone!
I've just received and successfully installed a system update for Android 5.1.1 and it says exactly zero about itself. Even Android's version hasn't changed.
Does anyone have any idea what it fixes? I surmise it fixes two recent holes but 10MB sounds a little too much for that.
I also got but nothing happened
Sent from my Nexus 5
I got it, I'm updating manually since for some reason my phone never wants to update the regular way.
It addresses the Stagefright vulnerability
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
ApTeM said:
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
Click to expand...
Click to collapse
flash it through ADB
I use this thread as reference just to make sure I don't miss any step but there are a few others threads like this. http://forum.xda-developers.com/google-nexus-5/general/guide-update-rooted-device-to-5-1-lmy47d-t3050789
OTA install error
I got the OTA notification to download & install the Stagefright patch. Every time I try to install it, it says "error!" shortly after it starts to install and shows the android with a red exclamation point.
My nexus 5 is stock & unrooted.
Any idea what's causing this and how to force the install? If not, I can sideload OTA with ADB later tonight.
Thanks!
I think the build number should have changed to LMY48I.
vagosto said:
flash it through ADB
Click to expand...
Click to collapse
adb fastboot
I've had my first freeze and first complete blackout since this small update
This should be the monthly update mentioned on main page
This update is worthless: http://www.theregister.co.uk/2015/0...efright_fix_wont_be_resolved_until_september/
I will skip it.
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.
Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!
nitro32 said:
Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!
Click to expand...
Click to collapse
Hey, maybe something go wrong in your update process. To make sure its no issue on the official SW side, i would recommend to do a clean flash:
- backup all your important messaging stuff like whatsapp, telegramm, signal via inbuilt backup function.
- do a backup via the google backup function found in settings / sync photos via the google photos app
- if you have important files on your internal storage, do a backup of it on your pc / flash drive
- then, flash the latest factory image avaiable (use factory image, NOT OTA update) (dont use -w, to preserve data).
- After it setup your phone again. Patch the boot.img (extract it from the factory image you flashed) with magisk and flash it, install root (magisk).
This way you can ensure, that its not a SW error / bug from google.
When you want/need to manually apply a update, follow the instructions in the agisk thread for P3a: https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Really, thers is no need to flash the radio, etc files by yourself, just follow the instructions to preserve root and flash the ota.
It may take about 40mins of work, but you can be sure, that if the issue persist its not your fault.
Cheers!
Hi, bejunk. Thanks for taking the time to reply. I'm a little slow to respond because I was hoping someone else might chime in. Not that I don't appreciate your advice, but what you described is pretty much exactly what I did leading up to this point - flashing the latest factory image without -w to preserve my data. I also didn't really seek out to flash the radios myself, that's just part of the flash script provided with the factory image:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-sargo-g670-00042-200421-b-6414611.img
fastboot reboot-bootloader
sleep 5
fastboot update image-sargo-qq3a.200705.002.zip
I guess I'll try wiping my data this time and trying again. Was hoping to avoid that. And failing that, flash back to the January image and see if that gets things working again, unless there are any other ideas.
Will post back the results.
Did a factory install again as mentioned, this time leaving -w enabled, and so far so good. Haven't noticed any wifi drops in the last couple of days, and I'm able to connect with 5 GHz again. No idea what failed previously, but glad things are back to normal now. Aside from that wifi issue, my 3a has been extremely reliable. Hated to see that record ruined.
I use to root everything from phones to tablets for years. But lately I've given it all up. I need reliability and security and you're not going to truly get that with some of these cooked ROMs. No matter how so-called reputable these chefs are. You really don't know anything about them.
Glad you got your situation fixed. I can remember going through the same thing many many times. Frustrating as hell.
Nylo
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Palaryel said:
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Click to expand...
Click to collapse
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
iMaterial said:
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
Click to expand...
Click to collapse
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
If you want to be able to receive OTA updates it still might fail (generic error "Installation Problem") depending on what you did with root. If that is the case you'll have to reflash completely via NOST (but in most cases you can do so without erasing user data, hence keeping your apps/settings).
Palaryel said:
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
Click to expand...
Click to collapse
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
iMaterial said:
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
Click to expand...
Click to collapse
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Your only option now is to actually reflash everything with NOST (if you want to keep user data uncheck the "Erase user data" box before flashing). After the flash your system should update without any issues (will update 3-4 times, takes a while). In case you reflash like this and it doesn't want to update, the only option is to reflash again while deleting all user data, apply all updates and the re-root.
NOST download:
Code:
https://tmsp.io/fs/xda/nb1/tools/nost/NOST-v0.6.exe
Stock image (NB1-5150-0-00WW-B05):
Code:
https://tmsp.io/fs/xda/nb1/firmware/NB1-5150-0-00WW-B05.qlz
Palaryel said:
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Click to expand...
Click to collapse
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
iMaterial said:
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
Click to expand...
Click to collapse
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Palaryel said:
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Click to expand...
Click to collapse
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
iMaterial said:
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
Click to expand...
Click to collapse
Actually I forgot about File Explorer, which I also use in root mode. Also nothing Greenify does should actually compromise the system partition in away that prevents updates. But like I said, with this phone its a bit tricky, I've never been able to pinpoint the exact issue thats doing so. For OTAs to work seamlessly the phone has to be reverted to stock (unroot, stock recovery, stock hosts, unchanged system partition, etc), but apparently theres something more to it since at times even after flashing everything back to stock the updates would fail (in which case only a full revert to stock, including user data fixed the issue).
Also, what you wrote about big, clunky phones: thats exactly the reason I'm thinking about Pixel 4a/5, theyre both under 6'', hence relatively small and perfectly usable with one hand. Nowadays its become the trend to go 6,5+'' for flagships which I'm not really fond of.
Does somebody have that latest and last stock MR for October 2020 (00WW_5_16A) ?
Someone please help me.
"Fastboot devices"
(My device show up)
But after that, I can't enter any command.
It says Waiting for device.
My device show up in fastboot device as well as in Manage Devices in settings as Fastboot.
My Sp is October 2020.
I root my phone last July SP, bit lost root access after update.
Can somebody post the link to the latest Full OTA October 2020? Thanks
How to check your current security patch level. I want to root my phone, bootloader already unlock
Please someone help me
My current bulid no is
00WW_5_15G
Which image i use in above list
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.