Related
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...
I've recently been playing around on my shield tablet with a couple of different roms and rooting, but I ended going back to stock - albeit with root and twrp installed. I downloaded the stock image from Nvidia's own download site and everything well and now it wants to install 5.4 over OTA. I figured that was fine, I'd have to re-root and, possibly, reinstall twrp, but that's not a hassle so I went ahead with the update.
Unfortunately, when it rebooted to install it actually rebooted into twrp. I figured that was OK, since I could just flash the update manually. I found it from /data/data/com/nvidia.ota/ and went to flash it. It failed, however, with error e3003 - complaining about the update file being older that the existing system file. The only solution I could find on googling was to make suer you went through the updates systematically and in order. Since my tablet had been restored to 5.2 I tried flashing the 5.3 update, but it gave me the same error.
I'm now somewhat stumped as to how I can actually go about getting my tablet back up to date again...
My phone no longer sees OTA updates so I have been stuck using the factory images for the last few months. This month when I run flash-all.bat I end up with:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
< waiting for any device >
Sending 'bootloader' (8361 KB) OKAY [ 0.214s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
and the update fails. I am currently using the 4/27/2020 copy of platform-tools and validated that bootloader bootloader-sargo-b4s4-0.2-6355063.img is in the local directory so Im a bit stumped.
I ended up having to sideload the OTA update.
Dunno if you've tried this yet, but you can factory reset your device and backup, then see if OTA works.
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Different-But-Similar Issue
darkmeridian said:
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Click to expand...
Click to collapse
In my case, I uploaded the wrong boot image via flash.android.com; what I thought was beta 1 of Android 11 was a pre-Developer Preview of Android 12 (S). Since I still had the last full image of Android 10, I went back and flashed that (to scrub my flub). The OTA of 11 beta 1 came in on schedule once I had done that. Tomorrow, I'll hopefully (barring heat) take the new Google Camera for a drive - looking at changes since 7.2 - which shook things up merely on the NightSight/Astrophotography end. I seriously doubt that this will be 7.4 (which was unique to the Pixel 4), as I had seen nothing indicating that even Google was going to cross-port any of 7.4's feature set to the rest of the Land of Pixel.
I tried using flash-all for the first time for the June update and also got errors and an unbootable phone. So I went back to the sideloading method that has always worked fine for me and that fixed the problem. My phone is also rooted with magisk.
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.