Question Feb 2021 OTA? Or just a "Finish Setup" thing? - Moto G Stylus (2021)

I don't know what it was that prompted an attempted download and install a couple days ago on my lady's Stylus 2021. Not sure if it was just an attempt to complete the "Finish Setup" nag that just wouldn't go away (which I had put off several times) or if it was possibly an OTA. I checked Motorola Support and found nothing even pending. And it isn't even listed here on Android Police (a list of phones likely to get Android 11 in 2021).
So I'm posting this Q here in case anybody can say more about any possible OTA on this phone.

Moondroid said:
I don't know what it was that prompted an attempted download and install a couple days ago on my lady's Stylus 2021. Not sure if it was just an attempt to complete the "Finish Setup" nag that just wouldn't go away (which I had put off several times) or if it was possibly an OTA. I checked Motorola Support and found nothing even pending. And it isn't even listed here on Android Police (a list of phones likely to get Android 11 in 2021).
So I'm posting this Q here in case anybody can say more about any possible OTA on this phone.
Click to expand...
Click to collapse
You could check this link.
They are not the OTA update.zips, but the full firmware
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Or LMSA has an update check.
Which also uses the full firmware to update.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

Moondroid said:
I don't know what it was that prompted an attempted download and install a couple days ago on my lady's Stylus 2021. Not sure if it was just an attempt to complete the "Finish Setup" nag that just wouldn't go away (which I had put off several times) or if it was possibly an OTA. I checked Motorola Support and found nothing even pending. And it isn't even listed here on Android Police (a list of phones likely to get Android 11 in 2021).
So I'm posting this Q here in case anybody can say more about any possible OTA on this phone.
Click to expand...
Click to collapse
Sometime in the last week (I don't remember what day) I got an OTA for the January 1 security patch. Maybe that was it?

sd_shadow said:
You could check this link...
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Or LMSA has an update check...
Click to expand...
Click to collapse
Derp (at me), I forgot about LMSA. Thanks a bunch (nice to hear from you specifically) and apologies for the late reply.
Edit to add, I will try LMSA to see if i can download this security update and flash it. If I can do that, maybe I'll also upload it and post a link in this forum.
jumphour said:
Sometime in the last week (I don't remember what day) I got an OTA for the January 1 security patch. Maybe that was it?
Click to expand...
Click to collapse
Yep, in fact the notice showed up again yesterday and this time I acknowledged and let it proceed. Of course it failed because root (after actually starting install). But I did confirm that it was a Security update. Thanks to you as well for replying.

Related

New maintenance release : Dec 2016 security patch

Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Just got mine
You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.
nothing in eu yet
iks8 said:
nothing in eu yet
Click to expand...
Click to collapse
As far we know so far, this is for the XT1575 only... just the December 2016 security update to 6.0, very minor update. Started rolling our about a week ago... a big push seemed to happen on the 14th and 15th with many users receiving it those days.
autosurgeon said:
You are not tricking it into checking with Google...The update comes from Moto servers. However the sim can cause the imei controlled rollout to not work correctly on some handsets thus removing the sim allows the phone to get back.in line so to speak.
Click to expand...
Click to collapse
Edited/fixed
it has been rolled out worldwide... its been like (3weeks ) since i updated it...
Got mine yesterday
Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.
Firefishe said:
Is there any way to update without wifi? I have unlimited data through Cricket Wireless but the system will only let me do it over wifi.
Click to expand...
Click to collapse
No, WiFi is required to get a Moto OTA.
Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.
strafer69 said:
Who the hell cares? This should have been the 7.x update! Too little too late Lenovo.
Click to expand...
Click to collapse
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Sent from my SM-G935P using Tapatalk
We should all agree that Pure program by GG is a fail. GG initiated it with HTC, Moto... with Pure Edition and commit that they would be upgraded just after Nexus lines
You guys are missing the point.
Nougat 7.1 came out in December. In order to have a smooth update to 7.1, you need the pre requisites which is the security update
piscesjoey said:
Exactly! There's absolutely no excuse why the Pure hasn't been updated to Nougat especially since the phone uses a damn near vanilla Android! HTC 10 & LG G5 had theirs for over 2 months now & some Samsung S7/S7E has been getting theirs over the past few weeks. My wife regrets buying this phone now over the Nexus 6P last year & now can't wait to dump this phone for the upcoming Galaxy S8+.
Click to expand...
Click to collapse
I understand your sentiment regarding the near vanilla, and I'm surprised Google didn't commit Lenovo to keeping the pure/style updated. Lenovo has given over to "standard business practices", which unfortunately means that the manufactures focus on updating their newest flagships first (Moto Z line, G5, GS7, HTC 10). This is nothing new and has been this way for a while. Once again, the rule applies: if you want the latest and greatest Android updates upon release buy a Google phone (Pixel). Aside from that I expect very little. If I want the latest and greatest, I turn to XDA and other sources for custom ROMs (which is nothing new for me).
_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting promoted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?
---------- Post added at 11:56 PM ---------- Previous post was at 11:56 PM ----------
_litz said:
Should be popping up on your device (you might have to pull the SIM to trick your handset into seeing the update).
If you want to sideload : https://dl.dropboxusercontent.com/u/22067374/Blur_Version.24.221.8.clark_retus.retus.en.US.zip
Click to expand...
Click to collapse
thanks for this, it was driving me crazy that I kept getting prompted to do this, but the update doesn't work with twrp and/or unlocked bootloader. How did you extract the update to sideload it?
It'll be another 2-3 months to even get 7.0 and than no more updates. That's why **** motorola/lenovo nobody buy the G6 or G6 plus so they finally go out of business!
Sent from my XT1575 using XDA-Developers Legacy app
you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
_litz said:
you don't extract it to sideload it ... you need to make sure you have original partitions (this will NOT apply to a modified system or boot), and then restore the factory recovery. Factory recovery has a sideload from ADB option.
If you have modified enough, you may have to backtrack to the last full system image (may 2016, I think it was), then do the sept update, followed by the dec update.
Those are available in other threads on XDA.
Click to expand...
Click to collapse
why is it so difficult to apply a few security patches. at this point i'll wait for nougut. I've been eyeing a few of the nougut roms, but I see comments about stability and features not working.
do we need to relock the bootloader too? or just no root, stock partitions, and stock recovery?

Stuck on June update - ta-1043

After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
I have TA-1043 and August update.
It sucks and Nokia seems to be silent on this. Everyone (or most) who have software build 2_22A_SP01 seem to be stuck on June. If you have a different build you are getting updates.
Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.
Ozhora said:
Same here : Nokia support reply that it's because my operator don't deploy that update over his network...
When I contact my provider he reply that it's not him who manage software updates on my phone.
I will try to contact Nokia support again with build number and the fact that others are stuck like me on June Update.
Click to expand...
Click to collapse
Bull IT Will come over WIFI. No problem.
No updates found over WiFi or cellular network
Hello,
go to
nokia.com/en_int/phones/security-updates
select nokia 6.1
and you 'll see that only 3 firmwares are on july update.
00WW_2_13B_SP03
00WW_2_22A_SP02
00WW_2_22E_SP01
I have 2_22A_SP01 and even with sim card out, in other words, Wifi only, no update is available and I (and many others) am stuck on June.
The option here is to unlock the bootloader and using OST LA, flash the system image again, there is a thread here to do this. For me everything worked fine, and I'm now on August SP
For people stuck with June Patch and a A or B builds variant, you can follow this guide (no bootloader unlock needed) :
community(dot)phones(dot)nokia(dot)com/support/discussions/topics/7000032724
It works and I'm now with the August Patch and a 2-22E build (I was 2-22A with June Patch before).
Follow exactly the different steps (skip Google account is very important)
eipi1 said:
After resetting my Nokia 6.1 phone, it still cannot find any update. Is anyone also stuck on the June patch ? Is that normal?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...pl2-222e-0-t3831764/post77389130#post77389130
It kinda worries me what HMD is doing. The shell is top notch and I actually applaud them for valuing scratch resistance over shatter resistance because one happens in an accident where the other is a constant bugger. But if they are going to do Android One with such problems Google better punish them for not staying up to standard.
Just got July SP on my 1043, however cannot install it...
Finally, phone updated on its own (without special measures), first to July, then to August security patch. Software is now 00WW_2_22E_SP02.
Could unlocked bootloader be the reason I cannot install OTAs ? Because I'm full stock since i flashed back 8.1 firmware using Ntools.
Try clearing data for Google Services Framework. It should work after that. I tried this yesterday but didn't get any updates. I just switch the phone off after that. This morning I powered it on, and 2 updates, July and August came in quickly. Just has to re-connect my google account and all is working well for now.
Hope this helps others.

WARNING to potential buyers of the Nokia 8

I just got done chatting with Nokia support (both chat and email) about getting the required unlock.key file that you need to unlock the bootloader for the Nokia 8, which they said they would unlock. First, a little background. The process Nokia wants you to go through to get the file is to download an apk of theirs which will analyze your phone a bit and then generate a code which you put into a form on their website to get the file emailed to you. Rather clunky but alright. I do so, but then I get an error when the apk runs. "Error messages: Device not support." Very well. I then talk to support. Chat had no idea how to fix it. Email fared just as well. I will copypaste the entire exchange. (Save for the original email I sent as I forgot to save it. Sorry about that.)
Nokia said:
Welcome to Nokia Mobile Care ,
​Thank you for your time writing us and thanks for using our Nokia 8 products. We understand why you came to us thats why we will try our best to assist you !
In order to assist you better and more accurately we would like you to provide us a little bit more information :
​
​- Could you please provide us the screenshot with the error message? Thank in advance!
​- How are you unlocking bootloader ? in which step are you at ?
​Additionally we will provide you the steps unlocking bootloader below :
​
1-Go to https://www.nokia.com/en_int/phones/bootloader, accept the terms and sign in
2-Scroll down until you see the phone validation form.
3-Download and install NokiaPhoneUnlockBootloader.apk, there is an included link on the page.
4-You will receive a validation code that must be entered into the form on the website along with the email used, note the validation code is only valid for 30 minutes.
5-You will receive an email containing a link to download a file, the name will contain your IMEI number and have an extension .key, it should be renamed to "unlock.key"
6-Start the phone in download mode.
7-Download and set up ADB
8-Start an ADB shell and run the following commands, unlock.key must be in the platform-tools directory from the ADB setup
fastboot flash unlock unlock.key
fastboot oem unlock
You should then see
Unlock success!
9-then run the command
fastboot reboot
​
Remember that you are important to us and we're looking forward to your response.
If you have questions or face any difficulties, please contact us at your convenience.
Wish you all the best.
Best regards,
Nokia Mobile Care
-----------------------------------------------------------------------------------------------------------------------------------
© 2019 HMD global All rights reserved.
Nokia is a registered trademark of Nokia Corporation.
HMD global is the exclusive licensee of the Nokia brand for phones and tablets.
-----------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
S5Guy said:
I have downloaded the official apk from Nokia to get the verification code to put on the website form. When I launch the app and put in my email though, it merely shows the error message shown in the attachment.
Click to expand...
Click to collapse
Nokia said:
Thank you for getting in touch with Nokia Mobile Care. It's important for us to have you as our customer.
I can see that you are trying to unlock your phone's bootloader, you have already downloaded the app and you are receiving the message saying that "device not supported".
​
HMD Global allows the bootloader on certain Nokia phones to be unlocked, allowing for customizations. This feature is intended for developers only.
​
Once the device is being unlocked, it is no longer covered by the manufacturer's limited warranty provided by HMD Global.
If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message "Device not Supported" this mean that your device is not supported to have the bootloader unlocked.
If you are facing some issue with your phone, you can send it to a repair center, out specialists has the information on how to handle it. Note that Nokia only provides the possibilities to unlock bootloader to developers.
We hope that the above information is useful.
Any other question you may have are always welcome. Please feel free to contact us again.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
S5Guy said:
"If you have religiously followed the steps my colleague provided to you on the previous e-mail and after it you have received the message 'Device not Supported' this mean that your device is not supported to have the bootloader unlocked."
^ This is not correct at all. At least for the Nokia 8. https://twitter.com/sarvikas/status/1045298106818949120
I have followed the prior instructions rigorously, but since the apk does not work, I must ask you for the needed "unlock.key" file. I am very well aware of the consequences of unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for getting back to us. ​I'm sorry to hear that the previous solutions didn't make any difference.
I can see that you are not happy about the previous answer you have had. I understand that can be frustrating sometimes.
As explained before the allowing will depend on many factors, as market, for example. If you have the app running well, if you have tried all the steps to have your bootloader unlocked and still receiving the message "device not supported" there is no other reason than that the app itself is saying the device you are trying to unlock is not supported.
Did you tried to uninstall and reinstall the app? did you tried to restart the process?
Note that here we are a customer care for technical issues customer may face with their device, we do not produce the rules or the policy we just follow then. There is no other advise to you at this moment.
If you have any other question not related to bootloader, please feel free to get back to us any time.
You can reach us via chat daily, English support is available 24/7. The live technical support channel is easily accessible from the Nokia support application your Nokia smartphone and from your PC, at: https://www.nokia.com/en_int/phones/support#contact-us.
Kind regards,
REDACTED
Nokia Mobile Care
[email protected] email is operated by HMD global, the exclusive licensee of the Nokia brand for phones and tablets. Nokia is a registered trademark of Nokia Corporation, visit us online at www.nokia.com/mobile-support
© 2019 HMD global All rights reserved.
Click to expand...
Click to collapse
-
So basically, to sum up, if you're thinking of unlocking the bootloader at all for any reason, steer WAY CLEAR of this phone. My phone may for whatever reason have fallen through the cracks perhaps, but a lot more people than me are reporting this issue. On top of that, I've checked my phone's IMEI to be sure it wasn't stolen or fake and it was perfectly fine and legit. Honestly, I hate that I have to post this message because the Nokia 8 actually has some features I like that aren't really on other phones, but because of this software travesty, I can't recommend it at all.
Nokia, if you're out there, this is a disgrace in both software and support. Please fix this.
Hi
I have the Nokia 8 TA-1012 but I have not tried to unlock the BL. I am currently on Pie so see no reason for doing so as I am happy with the OS.
As most people do not buy a phone to modify the OS I see no problem not recommending this phone for normal use.
Sent from my TA-1012 using Tapatalk
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
The only solution that doesn't rely on Nokia might be to tear apart their apk and use a rooted phone or an emulator to fake the properties it reads, so the app thinks it runs on a security patch that is supported.
But this approach requires people to send their IMEI to random people on the internet so there are additional risks.
ironman38102 said:
While I didn't unlock through official methods
Click to expand...
Click to collapse
I have heard someone else mention this as well. How did you unofficially unlock the bootloader?
THMSP said:
It is not related to models, but instead to the build ID's the phones run. (Nokia software is completely generic) Back when Nokia announced the unlock process and the october security patch dropped, phones on october patch started to
report the same issue the OP has encountered. One or two weeks later (after some public outrage ) the app started working again, likely because Nokia added the build ID of the october patch to their
database of allowed versions.
Click to expand...
Click to collapse
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
frankoid said:
Perhaps downgrading and then trying the unlock app again might work?: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
THMSP said:
To downgrade without an unlocked bootloader, you need a full OTA image that is configured accordingly, directly from Nokia. You boot into stock recovery and sideload that image, and in theory you should get an Oreo system.
However: The only full OTA downgrade I have done so far was using the revert-OTA from the Pie Beta Labs build. That gives you Oreo with November / December update and AFAIK those builds are not enabled.
The only other full OTA I know of happened it May, and it might be possible to sideload that one to get a system that you can then update and unlock on September / October patch.
But I never used this zip file so I don't know if stock recovery would accept and flash it if you sideload it.
If anyone here wants to try it out: You can download the file from my nokia cloud folder (https://bit.ly/nokia-nb1 - OTA Updates/NB1-488B-00WW-B01-update.zip).
I would be curious about the results. (Only oreo users should try this.. When you downgrade a Pie install it corrupts your userdata)
(I am intentionally not posting a detailed guide. If you can sideload this, you also know about the risks of messing with your phones software )
Click to expand...
Click to collapse
I'm your man. With nothing left to lose. o_o Will report back with the results ASAP.
I'm back and with bad news. The update process via the recovery menu seemed to run into an error where it complained about the timestamp on the update zip being too old, but for whatever reason, it proceeded anyway. OK, wiped the data (what data?) and did a factory reset, now it's booting up. I check the system information to be sure and it is 8.1.0. Installed the apk. Ran it. AND THEN...
Device not support.
I'm gonna try this with the zip mentioned in frankoid's post and do another update again, but honestly, it looks like Nokia just wants to be an asshole at this point.
!!!!!!!!!!!!!!! SUCCESS !!!!!!!!!!!!!!!!!!
This update zip is what you need: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
Thank you apple boy for this topic.
100% troll.
S5Guy said:
*snip*
Click to expand...
Click to collapse
Great to hear that you got it working! My zip likely not worked because it just throws you back half a year (where official unlock didn't even exist) - you would have to update until you find a security patch that works.
But if November patch worked for you thats great! Since the May OTA worked for you that also means that people could choose to use the unofficial (paid) unlock method so Nokia doesn't know about whether they are locked or unlocked (warranty reasons).
Those OTA zips are model-agnostic btw. Whether they say TA-1004 or TA-1012 doesn't matter, they are the same. Only google makes that distinction on their servers, the software doesn't.
foxbatul said:
Thank you apple boy for this topic.
100% troll.
Click to expand...
Click to collapse
What's less useful...
A detailed set of instructions aimed at helping other forum members
... Or your post?
On mine that option is greyed out...
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
theviking33 said:
Thank you that was indeed very helpful. Will do the same now...
If I can find out WHY on my device that option is greyed out. How can I overcome this? Thanks
Click to expand...
Click to collapse
Did you touch the option in the past at all? If you did, it will be greyed out. As long as it's switched on though, it's fine. (I heard it will "ungrey" itself after a week, but there you go.)
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
theviking33 said:
No, did not do anything and it is off and greyed. I don't think it will magically ungrey itself. I did however download that unlock.apk and sent out email and pin, now waiting if a reply will come with the unlock code and procedure. Its been a few hours and no reply, so perhaps that's not working either.
Click to expand...
Click to collapse
I'm assuming you have a brand new TA-1004? And yeah, you should have gotten back a code long ago.
Try some of these options. https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
It could be though that it's just been flat out disabled due to region or whatever. If the solutions in the above link don't work, try downgrading back anyway and then using the apk as explained in an earlier post of mine.
It seems to be a case of "flat out disabled". I did a factory reset already and this setting won't change. I actually bought 2 of those phones and on both is the same.
How do I see or find out what region they are for?
And for the booloader, seems I have to go the old fashion way now...
---------- Post added at 11:38 ---------- Previous post was at 11:25 ----------
I have the TA-1004 DS which is International. So wouldn't understand why ist greyed.
ironman38102 said:
While I didn't unlock through official methods, it might be good to figure out what models of Nokia 8 are affected. Maybe a specific model is affected?
Click to expand...
Click to collapse
Mine has same problem and I've also been through similar online-forum attempts to help.
Model: TA-1012
Hardware version: 3.1
Patch level: 1 Jan 2019
Build No: 00WW_5_11A, 00WW_5_110_SP01
Downgrade your phobe and you can unlock, i have the same phone and this is what i did. I downloaded my phone firmware,i place the update file on my external sd card, i reset my phone to factory stock, i shut down my device an while shut down i press vol + and plug in my cable, i wait for the no comand screen and press power while holding vol up and get in recovery where i update from sd card and boom oreo

Nokia 6 (2017) march security patch update now released !!

Hi y'all
So kinda happy today, Nokia HMD Global sent out a new security update for the NOKIA 6 (2017) model.
Not a big surprise but glad they are sending out patches for the phone.
Wish they could fix the bug and the lag on the Android Pie software though.
FOR DEVELOPERS,
PLEASE CREATE A CUSTOM ROM FOR THIS PHONE.
FOR USERS,
IF ANYONE WANTS TO DOWNGRADE THEIR NOKIA 6 (2017) TO OREO CHECK MY PAGE
I started to install this update last night and my phone has been on the "Installing security update" screen ta the same progress since.
I've tried restarting with Volume+Up but it comes right back to this screen no matter what. It's not showing up in adb/fastboot list either.
Anyone else having this issue? Is there any way to see extra debug info/what it's stuck on, or just to cancel the update entirely for now. I have some accounts tied to google authenticator on this device so I'd rather not lose data if possible.
Hello, could someone share update archives for TA-1000 cuz I am not receiving OTA after Feb 2019 ?
Try This
OscarOrSomething said:
I started to install this update last night and my phone has been on the "Installing security update" screen ta the same progress since.
I've tried restarting with Volume+Up but it comes right back to this screen no matter what. It's not showing up in adb/fastboot list either.
Anyone else having this issue? Is there any way to see extra debug info/what it's stuck on, or just to cancel the update entirely for now. I have some accounts tied to google authenticator on this device so I'd rather not lose data if possible.
Click to expand...
Click to collapse
Hi there,
I had the same issue, but never cancel an update when it is installing. You May or May not BRICK your device
Regards
KIBS2173

VS995 updated to 20d security patch

I just received a security update to my LG V20. Does this mean android 9 is next?
Dbrown53 said:
I just received a security update to my LG V20. Does this mean android 9 is next?
Click to expand...
Click to collapse
Same here. I was shocked to see an update
I've been prompted but have not installed it. Some traffic on android central addressing this but it's weird. Version goes to vs99520d (from 20c) but for someone who installed it, the date did NOT change from 1 Oct 2018. One person was told by LG that this is their patch (Verizon tech support knows nothing about it and it is not on their web site) but I've spent a couple hours on the phone now with VZ and LG tech support and they have not been able to find anything at all related to this patch. Maybe it's perfectly fine but who put it out and what's in it?
androidcentral post is here https://forums.androidcentral.com/l...ity-update-my-verizon-lg-v20.html#post6847295
Did the security software version change. Mine is at version 4 not sure what it was before.
My security software version is MDF v2.0 Release 4 on VS99520c.
thchipmunk said:
My security software version is MDF v2.0 Release 4 on VS99520c.
Click to expand...
Click to collapse
Mine is the same, the android central user was told (by LG) that it was a 'security patch' so he was comparing the date under 'Android security patch level' but maybe it's OK for that date to remain the same. At this point I'm more holding off because of being stubborn but I'll probably install it in the next day or two.
It's official Verizon is now showing it on there software update page for the LG V20.
If you update, can you keep root?
You can use the snoopsnitch app to see what the security patch is run the adnroid security patch tester and send a screenshot
So, just got a VS995 in the mail, unrooted. Which is the better root method:
The dirty Santa - https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Or this flashable zip - https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
baldybill said:
So, just got a VS995 in the mail, unrooted. Which is the better root method:
The dirty Santa - https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Or this flashable zip - https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
Click to expand...
Click to collapse
You need to use Dirty Santa to get unlocked bootloader then you can use zip file to flash oreo with root.
I was going to try to get root on VS99520d now that I have 3 V20's. Verizon is now claiming VS99520c is the latest. Using their software update utility VS99520c is all that is offered now. I do have a copy of what I believe are the OTA update files but God only know what to do with them. Hopefully WiFi calling now works on VS99520c now. This is the only reason I was interested in 20d in the first place.
Edit: I was just being impatient. I got the OTA update after about a half hour. I'm curious what the Verizon Update tool will say about this one "VZW Utility Application - LG"

Categories

Resources