Related
Hi folks,
I've got a Verizon LG G2, and I've performed the following tweaks:
- Disabled a few unneeded services (e.g. verizon location agent, sync service, etc. using the built-in android capability
- Rooted via "ioroot" technique
- Installed ClockWorkmod Superuser app (for some reason the ioroot app wasn't prompting before allowing root)
- Backed up and then uninstalled extra cruft using Titanium Backup.
Lately I noticed that there's an OTA update available. However, when I try to install it, it reboots and eventually gives me a 0x1117008 error. Through a little bit of searching, I concluded that 0x1117008 was perhaps an error indicating that the device had been rooted. And sure enough, the Status section in About Phone did indicate "rooted" in Rooting Status.
Through using Voodoo OTA Rootkeeper, I was able to un-root the phone. I also removed other traces of the SuperUser apk and used the "forel.lee" trick to reset the "Rooting Status" property back to "unrooted". However even after all of this, the update failed with 0x1117008. "Rooting Status" still shows "unrooted" after the failed update, too. So my next strategy was to restore the bundled cruft apps via Titanium Backup, and re-enable the unneeded services (and subsequently performing the root removal steps). And sure enough, 0x1117008 once again.
My questions at this point are:
- Is 0x1117008 really because the error detected that the device was rooted? Or is it perhaps some generic message that could mean multiple things?
- If 0x1117008 is indeed because root was detected, does that imply that the update process does a different/more-thorough check for a device having been rooted? And if so, what indicators of having been rooted might I be missing? e.g., could it even be going as far as detecting the presence of apps such as Titanium Backup Root as indication of being rooted?
- Other posts indicate that a way to get the OTA update working is to do a factory reset and then upgrade from there. But that'd blow out all of my data such as text messages and app-specific stuff, right?
Any questions or suggestions on how to proceed would be greatly appreciated. I'm not overly concerned about this incremental upgrade, but my fear is that when the KitKat update eventually comes out, I'll be in the same boat. Worst case scenario, I suppose a factory reset combined with the same steps that I used to migrate data from my old phone (Google online backup, SMS Backup & Restore, etc.) might allow me to do it. But that was a headache I'd like to avoid if at all possible.
Thanks!
d3leted
Well, I tried doing a factory reset, and it still resulted in a 0x1117008 error on attempting to install the OTA update! It wasn't really straightforward, but here's what I did to get the phone updated:
Create Titanium Backup Root backup
Create SMS Backup & Restore backup
Via adb shell, make a tarball of all of /sdcard
Get a copy of that tarball via adb pull
Do factory reset. This will clear everything in /sdcard!
Remove evidence of root
Use LG Mobile Support Tool to get latest ROM. I can't link to it, but google for B2CAppSetup.exe The option to update the software is available via a menu option. It's about 2GB and takes a while to download.
Re-root (ioroot 1.7)
adb push sdcard tarball back on device
Extract sdcard tarball via adb shell
Restore messages via SMS Backup & Restore
I had unchecked the option to have Google back up my apps during one of my factory resets, and this apparently deleted my online backups. So my app restores were manually via Titanium Backup
It's possible that this upgrade may have succeeded without doing a factory reset, which would have made things much easier. Also, I did note that during the Firmware Update process, it said "UNROOTED" on the screen. It's not clear if it would have succeeded if it were detected as rooted.
Edit: It appears that SMS Backup & Restore is redundant, as Titanium Backup can restore SMS messages. And Contacts as well. (I have a number of non-google-synced contacts)
forrestgump2000 said:
Well, I tried doing a factory reset, and it still resulted in a 0x1117008 error on attempting to install the OTA update! It wasn't really straightforward, but here's what I did to get the phone updated:
Create Titanium Backup Root backup
Create SMS Backup & Restore backup
Via adb shell, make a tarball of all of /sdcard
Get a copy of that tarball via adb pull
Do factory reset. This will clear everything in /sdcard!
Remove evidence of root
Use LG Mobile Support Tool to get latest ROM. I can't link to it, but google for B2CAppSetup.exe The option to update the software is available via a menu option. It's about 2GB and takes a while to download.
Re-root (ioroot 1.7)
adb push sdcard tarball back on device
Extract sdcard tarball via adb shell
Restore messages via SMS Backup & Restore
I had unchecked the option to have Google back up my apps during one of my factory resets, and this apparently deleted my online backups. So my app restores were manually via Titanium Backup
It's possible that this upgrade may have succeeded without doing a factory reset, which would have made things much easier. Also, I did note that during the Firmware Update process, it said "UNROOTED" on the screen. It's not clear if it would have succeeded if it were detected as rooted.
Edit: It appears that SMS Backup & Restore is redundant, as Titanium Backup can restore SMS messages. And Contacts as well. (I have a number of non-google-synced contacts)
Click to expand...
Click to collapse
I'm getting the same error... do you have any suggestions on how to get the update applied without the full reset? Thanks.
Edit: LG Support Tool finally worked to complete the update.
Encounter the same error while doing ota update. G2 rooted.
trickskevry said:
I'm getting the same error... do you have any suggestions on how to get the update applied without the full reset? Thanks.
Edit: LG Support Tool finally worked to complete the update.
Click to expand...
Click to collapse
I encounter the same problem here while updating via OTA. Please guide me. Did u do factory reset using LG Support Tool or did u simply update kitkat via PC Suite? Will it also encounter the same error when using the latter method?
Anyone Helping with This???
dhs.sun said:
I encounter the same problem here while updating via OTA. Please guide me. Did u do factory reset using LG Support Tool or did u simply update kitkat via PC Suite? Will it also encounter the same error when using the latter method?
Click to expand...
Click to collapse
I have the same problem, I have not seen anyone with help for us???
Reviving an old thread. I'm getting the same error with the Latest January 2015 update. Rooted with towel root. Stock ROM, no frozen apps. My Wife's stock unrooted G2 updated fine.
David
Same error here. Rooted with Towel Root and stock rom. Wifi hotspot mod is about the only thing I've done with the root. Wondering if reverting the hotspot mod will allow it to update.
Hello, I recently got the September update for Moto X Pure and I want to know how to update my phone. I've read around and it seems that I need to restore to unrooted stock before I can flash the image as opposed to just flashing the image without doing anything else then re-install TWRP and reroot. Can anyone provide steps in how to do this?
Do you have systemless root?
Open SuperSU, settings, full unroot. if you have Xposed installed, you'll need to flash the xposed uninstaller through TWRP. Now to remove TWRP, you need to download the latest stock rom and flash only the recovery.img from your computer.
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Sean89us said:
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Click to expand...
Click to collapse
Is there a way to stop the constant notifications that I have a system update that needs to be applied?
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
eigerzoom said:
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
Click to expand...
Click to collapse
The OTA update in January, dated Sept 2016, is 40.2MB in size and build number 24.221.8.en.US.
Not sure what is chewing up 700mb of data, but it isn't the OTA... Do you have automatic update on in the Play Store? There were tons of large updates in January, I may be exaggerating but it seemed like 2-3 times a "normal" month.
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.
Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
no its not working......After install recovery stuck in Samsung Flashing logo....
TWRP is making the devices get stuck on Samsung logo....
I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.
Having root and no encryption sucks. Think I'll wait
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.
guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip
sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.
CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly
Hello all,
today I would like to first tell about my successfull installation of 2 ROMs and ask a important question.
1. Successfull ROM installation
Using the guides from loquenz at https://www.chinamobilemag.de/tutorials/nubia-z17-twrp-root-google-play.html and from furiousjay at https://geekaxe.com/root-nubia-z17-unlock-bootloader-flash-twrp-recovery/ I successfully flahed the TWRP and installed the ....CNCommon_V2.39 and the ...CNCommon_V2.44 ROm and upgrade to it (!).
It alll went well and the phone is running.
I then installed the GAPPS onto it and it went fiine too, but I am still having issues (see later).
2. Question 1 FIRMWARE:
When I run on my V2.44 level of firmware the phone tells me that there is the V2.48 level of firmware waiting to be installed. I downloaded (in the phone, not TWRP) it and have it install. It rebootet. But after reboot it ended up in TWRP. There i said reboot and rebooted my phone. I was able to get into the phone but there is a little one to the upper right at the settings icon which brings me to system update and again downloading the same update.
I can install it again, but still end up in TWRP and after rebooting the system, with the update (2.48) not installed. And the system telling me that there is an update waiting for me.
This goes on and on. I have not found a way to end this circle.
Q: Is there a way to hvae a reboot NOT end up in TWRP? Or is this not the culprit?
Any ideas of what went wqrong and what I can do?
3. Question 2 GAPPS:
(this is separate from the above)
I also installed the Full_Dynamic_GApps-7.1.x-20170121.zip package via TWRP.
The GAPPS worked fine, but then started to aks me for reloging into my account (and didn'T let me).
Playing the filght mode trick helped, but only for a while, then the same again, that I needed to log in to my account.
Any ideas here? How can I uninstall the GAPPS and reinstall another package?
4. Question3 Permissions:
The phone didn't let me remove my Google account, saying that my adminsitrator wouldn't allow this!! How can I remove my Google account and re-add it? Which permission do I need to change and where?
Thanks a lot in advance for any light you can shed on this!
Thomas
I forgot to say that this successful installation means that you can go to a stock ROM and will get OTAs for the phone. I received the V2.48 via OTA!!
Not sure about qn1, but:
Qn2 GApps - when I tried to flash different versions from Open GApps, they automatically removed the old one as part of the flashing process. I think people seem to find the 'full' version works best.
Qn3 - I removed my Google account on the computer, I think it's somewhere on your Google account where you manage your devices/log-ins
tsiebold said:
Hello all,
today I would like to first tell about my successfull installation of 2 ROMs and ask a important question.
1. Successfull ROM installation
Using the guides from loquenz at https://www.chinamobilemag.de/tutorials/nubia-z17-twrp-root-google-play.html and from furiousjay at https://geekaxe.com/root-nubia-z17-unlock-bootloader-flash-twrp-recovery/ I successfully flahed the TWRP and installed the ....CNCommon_V2.39 and the ...CNCommon_V2.44 ROm and upgrade to it (!).
It alll went well and the phone is running.
I then installed the GAPPS onto it and it went fiine too, but I am still having issues (see later).
2. Question 1 FIRMWARE:
When I run on my V2.44 level of firmware the phone tells me that there is the V2.48 level of firmware waiting to be installed. I downloaded (in the phone, not TWRP) it and have it install. It rebootet. But after reboot it ended up in TWRP. There i said reboot and rebooted my phone. I was able to get into the phone but there is a little one to the upper right at the settings icon which brings me to system update and again downloading the same update.
I can install it again, but still end up in TWRP and after rebooting the system, with the update (2.48) not installed. And the system telling me that there is an update waiting for me.
This goes on and on. I have not found a way to end this circle.
Q: Is there a way to hvae a reboot NOT end up in TWRP? Or is this not the culprit?
Any ideas of what went wqrong and what I can do?
3. Question 2 GAPPS:
(this is separate from the above)
I also installed the Full_Dynamic_GApps-7.1.x-20170121.zip package via TWRP.
The GAPPS worked fine, but then started to aks me for reloging into my account (and didn'T let me).
Playing the filght mode trick helped, but only for a while, then the same again, that I needed to log in to my account.
Any ideas here? How can I uninstall the GAPPS and reinstall another package?
4. Question3 Permissions:
The phone didn't let me remove my Google account, saying that my adminsitrator wouldn't allow this!! How can I remove my Google account and re-add it? Which permission do I need to change and where?
Thanks a lot in advance for any light you can shed on this!
Thomas
Click to expand...
Click to collapse
1. you better download the China ROM v2.44 and install it via TWRP, dont forget to wipe chace and dalvik. It will make your phone like new
2. Go to Update and update your phone to v. 2.48
3. Unlock Bootloader, instal TWRP and root your devices using TWRP
4. Install Gapps Full
5. Wipe chace / Dalvik again.
So far, Google will running but with some issues like sometimes you need to re-authentucating google account again by go to flight mode by several minutes, gmail, photos and some other google apps. This is what we shoudl overcome while waiting for international rom
How do you prevent Twrp from jumping in (point 1 and 2) at the Reboot for the update?
I do have the China Rom V2.44 installed as explained in my post.
tsiebold said:
How do you prevent Twrp from jumping in (point 1 and 2) at the Reboot for the update?
I do have the China Rom V2.44 installed as explained in my post.
Click to expand...
Click to collapse
This is what I can suggest:
1. Do a NANDROID backup
2. Wipe all and flash 2.44
3. Update via OTA to 2.48
4. Install TWRP, Root and Gapps
5. Restore your data partition
Please do it at your own risk. I have not tried it yet.
OK, one additional day of trying...
I have reapplied the V2.44 update ROM through >setting>system update>local update
The following reboot did NOT stop in TWRP.
When the system was up it told me about the V2.48 update being available, downloaded it and I applied it normally (not using local update).
The following reboot also did not stop in TWRP but went through to the upgrade process.
So now I am at V2.48.
As said in other entries I did not (yet) manage to get Google Playstore to run.
I did not apply any Google distribution.
My phone has now updated to V2.54 via the OTA update system.
GAAPS still do not work, but I have personalized my phone to not use Google apps when the do not work, but use Nubia apps.
The support people in Germany and India were not helpful.. They refused saying that the phone is "only" (!!) sold in China.
I wonder whether we will see an international ROM at all, especially with the ZTE branch being sold.
tsiebold said:
My phone has now updated to V2.54 via the OTA update system.
GAAPS still do not work, but I have personalized my phone to not use Google apps when the do not work, but use Nubia apps.
The support people in Germany and India were not helpful.. They refused saying that the phone is "only" (!!) sold in China.
I wonder whether we will see an international ROM at all, especially with the ZTE branch being sold.
Click to expand...
Click to collapse
Working in a software company, I can understand why the Indian or German people would not help. I do less technical support than I did in previous years but I already had enough customers on my own so it would have been very problematic if I also had to answer to foreign customers (that and also the fact that a license purchased in foreign countries does not give us a dime so we are not inclined to help customers from foreign offices ).
Regarding the global firmware, the more time passes, the less I feel we're gonna have one. There are only speculations about an Indian release in September but nothing official. The phone is still on my wait list but it may not be the case anymore in October or November.
Hello guys,
I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization.
I formatted the phone after receiving the Oreo OTA and the phone is full stock.
Anyone know how to fix this issue?
Thanks!
VSTOLL said:
Hello guys, I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization. I formatted the phone after receiving the Oreo OTA and the phone is full stock. Anyone know how to fix this issue? Thanks!
Click to expand...
Click to collapse
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
v12xke said:
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
Click to expand...
Click to collapse
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates.
My build number ends with .019
VSTOLL said:
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates. My build number ends with .019
Click to expand...
Click to collapse
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
v12xke said:
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
Click to expand...
Click to collapse
There was no failed or hung syncs but I removed and added my account again anyway.
I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events.
My bootloader is locked.
VSTOLL said:
There was no failed or hung syncs but I removed and added my account again anyway. I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events. My bootloader is locked.
Click to expand...
Click to collapse
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
v12xke said:
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
Click to expand...
Click to collapse
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?
I found this post: https://productforums.google.com/fo...utm_source=footer#!topic/calendar/FzD9Y6ojci4
Theres a reply by Mikel Rodriguez that says:
"The cause of the calendar notifications failure is a change in the architecture of the calendar provider module. It is a content provider located at the application framework layer. Supposedly they changed the architecture of the module because it wasn't compatible with the doze feature of Marshmallow. So, all phones running Marshmallow or higher are fully affected by the failure. The only solution is to root, install titanium backup, make a backup of package com.android.providers.calendar, then uninstall it, then download and install the same package for version 5.1.1 (Lollipop). Because that version is not compatible with doze, it is necessary to remove it completely. Download "Boeffla Doze Control", open it and turn on "disable doze at start up" and "show toast message", then reboot, then open it again and check that doze status is off. That means that doze is not working. Calendar notifications will work again if you follow all the steps."
I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
VSTOLL said:
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?....... I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
Click to expand...
Click to collapse
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
v12xke said:
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
Click to expand...
Click to collapse
I'll wait for the next OTA then, and if it doesn't fix I'll try formatting and restore it with the Google tool you said.
By the way, I didn't received a incremental OTA. I live in Brazil, so the update arrived later here, I received it 2 weeks ago and was a 1GB download and I haven't received any security or incremental updates since that day.
I set an event and it'll remind me in 2 hours, I'll let my phone down and will not use it to see if the nofication will work, if it doesn't, I'll try this app: https://play.google.com/store/apps/details?id=com.github.quarck.calnotify&hl=en