The CHEVRON certificate has expired on 25th november 2011 so CHEVRONWP.EXE won't unlock the device ( will come up with the UH,OH error).
TO PREVENT THAT, SET BACK THE DATE ON BOTH, PC AND PHONE, PRIOR TO 25TH.
Related
So a about a week ago I got a notification for a new security update but I skipped it due to the bad Internet connection i had that day, now whenever I check for a new update in (about phone) I can't find the update, what should I do?
Settings -> Lock screen and security -> Other security settings -> Security policy updates -> Check for updates
ssrij said:
Settings -> Lock screen and security -> Other security settings -> Security policy updates -> Check for updates
Click to expand...
Click to collapse
I tried that as well,it says that my security policy has already been updated to the last version!!
Any help?
I skipped it also, thinking it would ask again in a day or so, but it never did. Is May 1, 2016 the latest for the "Android security patch level"? If so, I guess it may have done the update on its own later that night?????
abcomputin said:
I skipped it also, thinking it would ask again in a day or so, but it never did. Is May 1, 2016 the latest for the "Android security patch level"? If so, I guess it may have done the update on its own later that night?????
Click to expand...
Click to collapse
Well yeah may is the latest, but mine shows 2 April not 1 may so It didn't definitely update automatically, 2 April is what I got first I bought the phone, it never changed
First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Gary02468 said:
First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
Click to expand...
Click to collapse
My device started the update this morning, it ran in around 253mb, so I would guess its a minor update. I haven't let it finish, I want to give the 935U a run
Got it now:
http://forum.xda-developers.com/att-s7-edge/how-to/g935aucu4apj4-oct-1-2016-security-update-t3496395
I got the update. They sneaked in Fullscreen app.
I manually checked for the update and got it just now. It's so irritating that ATT takes so long to release these updates to us!
Hurricane Andrew said:
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Click to expand...
Click to collapse
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
norbarb said:
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
Click to expand...
Click to collapse
Yup, I got it yesterday afternoon as well. I noticed they finally removed the deprecated Milk Music app as well.
Here is the current update: Android 6.0.1 Marshmallow
The details
Release date: November 8, 2016
Android version: 6.0.1
Security patch level (SPL): October 1, 2016
Baseband version: G935AUCU4APJ4
Kernel version: 3.18.20-9439621
Build number: MMB29M. G935AUCS4APJ4
File size: 285MB
The updates
What's new: Full Screen – Mobile Video Service and Android device security enhancements
What's changing: Improved volume for Enhanced Push To Talk (ePTT) and fix for calls failing to go to Voice Mail when calling non LTE devices
What's going: Milk Music
Via AT&T
All they put in the update was the Full screen App which can be disabled with Package Uninstaller
I bought my 6p directly from Google, and it isn't unlocked or rooted. It seems to be stuck on the Dec 2016 (NMF26F) update. Forcing it to check for updates says it is up to date even today, Feb 13 2017. Any ideas?
ericstephani said:
I bought my 6p directly from Google, and it isn't unlocked or rooted. It seems to be stuck on the Dec 2016 (NMF26F) update. Forcing it to check for updates says it is up to date even today, Feb 13 2017. Any ideas?
Click to expand...
Click to collapse
Enable "Android (or USB) Debugging" in Developer Options then follow the instructions to adb sideload a full OTA image:
https://developers.google.com/android/ota
This OTA image does not require an unlocked bootloader.
Sent from my Nexus 5X using Tapatalk
Yeah I would side load like it says above.
For some reason my phone doesn't receive OTA updates either. Idk what happened but ever since the stable 7.0 I wasn't able to receive. So decided to side load which is super easy to do.
Thanks for the suggestions. I was considering manually loading the update while I wrote the post. I'll try it tonight.
1) Original android version is 7.0 (with security updates to April 2017)
2) Security updates July 2017
3) Security updates Nov 2017
4) Updates to Android version 8.0 (Feb 2018)
If I"m to do a hard reset in March 2018, will my LG G6 be in 1), 3) or 4)? and if its in 3) or 4), can I get it back to 1)?
Thanks.
Whatever ROM you will be with any security update available at that moment, hard resetting the phone will delete any data, not ROM configuration. So you phone will be at vanilla state, like you've just unpacked it and turned it on for the first time, but with the ROM which was already installed right before the reset.
You can get back to 1) but there is no sense in doing so, old ROM, less fixes, everything outdated.
Got it, thanks!
good morning. i waited 8 days after flash stock rom G950FXXU3CRGH with 1 aug patch. yet isn't present the oem unlock button in developer options. i tried during week to do the trick of back date, with no success.... now this situation. what can i do for solve the problem? is perhaps for my rom impossible to unlock oem?
i restarted phone many times in last day....
the date of system is automatic today but i did the trick....
i hope a help
thanks
Same here
Same here with the S9 Plus SM-G965F.
I don't think I have it for a week since I booted and reseted the device but I'm afraid that the OEM unlock option (RMM prenormal) is not time dependent on the August patch - maybe Samsung blocked it completely and we actively need a workaround to get it back.
Definitely that manual time trick is not working anymore and it's waste of time to even trying it on the August patched devices.
hi there i had the same issue, so actualy this is the samsung security guard you have to wait like 7 days to get OEM Unlock button, i did the same but what i did is, changing the dates like for 20 days then i did the update manually few times then i reboot again and again like 10 times the same steps, but i did not get the oem unlock button, so i did wait like 2 days and i have it .
I have the August security patch and my oem unlock shows in the developer menu.