Database Users

I just got an update notification for my 3G XOOM for HTK75D

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this all about?? Isn't this just 3.2.1 for the WiFi XOOM? I'm almost afraid to run the upgrade.

Yup. 321 it is. Got it earlier, upgraded, everything is fine.
Sent from my Xoom using Tapatalk

Ok. I just pulled the .zip and all of the files are dated the 25th, which was yesterday. Here is the file.

Why are 3g xooms getting this? Is this a result of downgraded xooms that used that update zip to fix the bootloader baseband?
Sent from my ADR6400L using xda premium

No. I never tried to update using the images from that other thread. I always wait a day or two before trying anything like that to see what happens. Still on stock 3.2. Only thing I've changed is the theme.

This is to bring 3G Xoom users up to the release build for 4G Xooms minus the radio but including all of the new security features present in HLK75D.
It also happens to contain the new 1.50 bootloader.bin which is required for those security enhancements.

Is it safe to add that zip file via cwm to a unlocked & rooted 3G?
I know it is not safe via ota
Or do we re-lock & unroot back to oem HR166 first and just take it via ota
Same update offered here today
?
New to the xoom here, is there a way to add this update while unlock & rooted?
I don't think changing the name to update.zip via cwm will work?
I maybe wrong.
In addition, if i re-lock and all back to HR166, have done it once to take the 3.2 ota update, can i just use the backup within cwm prior and restore settings and apps from that backup after this 3.2.1 update, or will that try to re-store the 3.2 os & boot onto now what would be 3.2.1?

Maybe someone here will be able to provide a walkthrough on how to get this updated. I'm rooted, but will this unroot me? will it lock the bootloader since there's a new bootloader update? I just don't feel like losing all my data and starting all the way back at HR166 again.

Am I likely to get this in the UK? I just checked for updates on my 3G Xoom and nothing shows!

I just said the heck with it and simply re-lock & unroot back to oem stock HR166 "3.0.1"
Then took the 3.1 - 3.2- 3.2.1 updates and started with a clean slate.
I did not have any custom roms and very little software, backed up the apk's and just started from scratch to avoid problems.
Yet I'd be interested in how to apply these ota update zips via cdw if possible for future references.

If my 3G Xoom is on 3.1 would this update take it all the way to 3.2? If so do I need to wait till it appears on my updates screen or is there another way?
Thanks.

Not sure about yours "international or US Verizon?", here in the states with the verizon 3G i went back to stock 3.0.1 re-locked + root, then it offered update 3.1 just over 28MB, then after that update 3.2 was available just over 15MB, took that one, then came update 3.2.1 just over 3.5MB
took that one.
To help it along i went into settings and to the bottom about tablet
Clicked the check update and they were available, once i did not even make it in there when the system told me one was available.
Again, this was on a non international USA Verizon 3G
Total time from start to finish including the re-locking and applying stock 3.01 was maybe 45 minutes in all.
My 3G has NOT been sent in yet for the LTE4G upgrade, hence the 3.2.1 and NOT 3.2.2
adamelphick said:
If my 3G Xoom is on 3.1 would this update take it all the way to 3.2? If so do I need to wait till it appears on my updates screen or is there another way?
Thanks.
Click to expand...
Click to collapse

this update breaks the android market. You cannot update existing apps .. the market constantly force closes.

Try clearing app data for your market

It checks your system first. If you've deodexed or overclocked (modified /system/app, /system/bin, or removed/overwritten files in /system/xbin, as well as the boot image / kernel) it'll abort the install.

I flashed a boot.img that was pre rooted for 3.2. Do I need to reflash a stock boot image first?

I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.

Now that would be great!!
kosenn said:
I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.
Click to expand...
Click to collapse

kosenn said:
I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.
Click to expand...
Click to collapse
Get back to that best buy, download and dump that update. You would be famous if it was 4.0
Sent from my Xoom using xda premium

al0vely said:
this update breaks the android market. You cannot update existing apps .. the market constantly force closes.
Click to expand...
Click to collapse
al0vely - your mrkt app is probably not fubar'd - HTK75D or HLK75D (update received w/ 4G LTE upgrade) contains an update to the google mrkt. If the app keeps cratering, try going to > Settings > Applications > Manage Applications > All >
Clear the cache & data on the following Apps:
Download Manager
Market
then reboot the device.
If that does not resolve the issue: back up any personal data that would not be backed up to the cloud > reboot into Android Recovery Mode > clear cache > reset to factory defaults > reboot.
That should fix the problem.
Cheers,
Hat.

[Q]Defy+ Custom Roms

Hi guys.
O have a Defy+ phone with Android 2.3.6 onboard
(4.5.1-134_DFP-231)
Pls help me. I cant fully understand how to flash any custom ROM on it?
Root and 2ndinit installed, but i can't install CM9 or AOKP rom for example.
I am booting to 2ndinit, entering recovery, do nandroid backup, do full wipe flash zip from SDcard, flash kernel( from this thread), and finally reboot. And got continious reboots.
What am i doing wrong?

are you wiping cache and dalvik cache after you install the rom? try this and it should boot. Also for CM9 dont install the bootloader. It did not work when I tried to install the bootloader, but fine when I installed without it.
I would try the latest CM7.2 from quartx I have the apr release and its fast, stable and I have had no trouble with it. Well apart from the baseband switcher in the options would not save the changes so had to install the app for it.
here is the link if you are not sure where to get it from
http://quarx2k.ru/cm7-nightly-defy+/?C=M;O=D
just put it on the root of SD card
boot into recovery (2ndinit or CM)
you can back up your data if you want (but sounds like you have done this so the file should still be there)
factory reset and wipe cache and dalvik cache
go to zip from sd and file from sd and zip the new ROM
wipe cache and dalvik catch
reboot.
Oh you can install gapps straight after CM7.2 as well if you want gapps on your phone
here is the latest gapps for CM7
http://goo.im/gapps/gapps-gb-20110828-signed.zip

Thanks, man, i'll try it. Will post a review later.

yeah if you install gapps you can do this straight after the CM7.2 flash
so once cm7.2 says its finished
go back and into install from sd select the gapps zip
install that (only about 9mb so wont take long)
then clear cache and dalvik cache
reboot.
All these ROMS might take upto 10mins to boot first up but thats normal.
if you installed Gapps it will ask you for your account details. Gapps only installs google play app and the google sync for your phone and contacts so it cant resync your contacts (there is a option to sync your apps.
I would choose not to do this as I ended up with 40 apps and most I didnt want lol. If you go into google play and hit the menu button (bottom left on the phone) and select my apps they will have all the apps you have installed and you can select the ones you want instead of having them all install at once then removing the crap ones.
I run V6 supercharger script and have the power control widget on the main screen so I leave everything off and set network to 2g unless I need it and I get 3 days out of the phone easy usually have like 20% left after day 3. So cant complain about battery.

kelbygreen said:
yeah if you install gapps you can do this straight after the CM7.2 flash
so once cm7.2 says its finished
go back and into install from sd select the gapps zip
install that (only about 9mb so wont take long)
then clear cache and dalvik cache
reboot.
All these ROMS might take upto 10mins to boot first up but thats normal.
if you installed Gapps it will ask you for your account details. Gapps only installs google play app and the google sync for your phone and contacts so it cant resync your contacts (there is a option to sync your apps.
I would choose not to do this as I ended up with 40 apps and most I didnt want lol. If you go into google play and hit the menu button (bottom left on the phone) and select my apps they will have all the apps you have installed and you can select the ones you want instead of having them all install at once then removing the crap ones.
I run V6 supercharger script and have the power control widget on the main screen so I leave everything off and set network to 2g unless I need it and I get 3 days out of the phone easy usually have like 20% left after day 3. So cant complain about battery.
Click to expand...
Click to collapse
WOW!Thet's...cool!I'll try to install in in a couple of hours!

yeah not sure if its the script that helps or what. I dont use the phone to much few short calls a day and hook it up to the car stereo when I am driving around. I would get to know the ROM first if you like it mod it further. but always do a nandroid backup first. If something happens then you can always revert back.
CM9 looks good and all but to me the usability of cm7.2 far outweighs the cm9. I have modded mine own theme to so its not like you are stuck with whats installed at first boot.
here are some screens of mine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Works great man!thank you! started in 2 minutes.fast smooth and ver-very customizable! Now will deeply explore CM7.2!

glad you like it. Its the best ROM so far I have tried and I been threw ICS, whiterabbit and a few others but all have problems in everyday use and I wanted something that you dont have to keep restarting things coz they freeze all the time.
cm7.2 has worked for everything I have tried so far.

IS Private Mode NOT Working for you after Rooting? - Try This... - LOLLIPOP

Thread Updated - This Thread is now about Private Mode in LOLLIPOP
What is Private Mode?:
http://www.androidcentral.com/how-use-private-mode-samsung-galaxy-s5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OLD KITKAT REFERENCE/SOLUTION BELOW
Is Private Mode working after you rooted your Note 4?
If the answer is no... try this flashabe zip:
Private Mode Fix
I have already demonstrated that Private Mode can continue to work after rooting/tripped Knox:
See post #24...
http://forum.xda-developers.com/not...-configure-fingerprint-scanner-t2919478/page3
Please, post results here...

If i understand correctly, it wont work for stock rooted. U have to use an rom

I can confirm this works on DynamicKat 1.2, but the quick setting did not show up. I am still glad that private mode is working now. Thank you TEKHD!

It's working for me using an Xposed module called XSecureStorage

Confirming that this works on a stock rooted deodexed rom on the Sprint Note 4.
Thanks!

OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app

Dumbo53 said:
OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I have been looking into this... I think it's actually the file:
system/framework/android.policy.odex
Flashable zip: (odex injection)
Can anyone with Jovy's ROM try this fix: (in order to verify if this fix makes Private Mode work with Jovy's ROM)
http://tek.serveftp.net/xda/Private_Mode_for_jovy_Fix_N4_tekhd.zip
If this works... All credit goes to you @Dumbo53
Quick Instructions...
1. Deactivate Xposed Framework
2. Reboot into recovery and flash file above...
3. Reboot... and see if Private Mode is working...

I'm on firekat v4 not jovy's rom, but I lost my private mode along the way. I thought it was when I tripped knox rooting with the temporary recovery cf autoroot uses.
This fixed my issue.
Rocking private mode currently. Hadn't been able to use it since the day I started rooting and flashing.

I've been trying to install the Xposed module for secure storage. However it says waiting for download for over 20 minutes now. Any ideas on this because I'd really like to use this feature of my phone. Thanks.
Sent from my SM-N910T using XDA Premium HD app

Ok the server for Xposed was down last night. It is back up now. I installed the Xsecurestorage module and private mode is working.
So for those of you with the Xposed framework installed, that's probably the easier route over installing a flashable zip file.
Sent from my SM-N910T using XDA Premium HD app

not sure whats different but im on stock rooted and neither wanam nor xsecure fixed my private mode. IDK

Did you try the flashable zip in the op?

flash did not fix on stock rooted rom. No Xposed installed yet

i was going to try flashing that file but if you say it doesnt work...
When updating my phone yesterday via odin, i flashed the update...checked private mode. (it worked)
Flashed root file and checked private mode...(it worked) Told SuperSU to not disable Knox. Checked private mode again...(it worked)
Installed Xposed...checked private mode.(private mode failed). I have tried the xsecurestorage and wanam module and neither worked. S health works fine. Just not private mode. Was pretty excited about being able to use this. My only other option i suppose is to go with a deodex rom that stays closest to stock i guess.

Just used this trick again. Firekat v5.
I think I lost private mode when I tripped Knox with cf autoroot:
Nice to have it back. Although, I'm going to need a more exciting life before I need it.

This actually soft bricked my phone. Stock but rooted and stuck at the tmobile scree.

Just used this trick again. Infamous 2.3:

Working for me on Infamous 2.2
Sent from a mobius strip

Hey guys.
I started another threat but TEKHD requested i put this here as well. I found a method that worked for the 910f and worked for myself.
In data/system/secure_storage delete the personalpage folder
In data/system/users delete privatemode_edk_1000.
This got it working on my phone. Still using Xsecurstorage in xposed and haven't tested yet with it not on.
http://forum.xda-developers.com/note-4-tmobile/general/how-fixed-private-mode-t2985441

This Fix didn't work for me, but, the one mentioned by @avengethis1 at THIS POST worked for me on my T-Mobile Note 4 N910T with Stock ROM and TWRP Recovery

Cant erase FOTA via fastboot, update snuck through

Hey gang, I doubled checked and couldn't come up with an answer but somehow Android System Update got past my frozen FOTA & Update Center (few others) as well as having system updates unchecked in Dev Options. I haven't installed the update & would love to stay on 10D.
So I boot into fastboot, run the fastboot erase fota and get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As most can spot I'm definitely in fastboot as the fastboot getvar all and fastboot reboot function just fine. I tried defrosting the fota & others and that also didnt work.

Which phone do you have?

androiddiego said:
Which phone do you have?
Click to expand...
Click to collapse
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.

2muchspl said:
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.
Click to expand...
Click to collapse
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.

androiddiego said:
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.
Click to expand...
Click to collapse
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.

2muchspl said:
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.
Click to expand...
Click to collapse
I hope this worked for you. I was afraid to try this even though it used to work on all my sammy phones, but I bit the bullet and it worked. @OvrDriVE 's ROM is great. I do a lot of lurking watching what is going on with each rom and I feel that Ovrdrive has the best. That's not to say anything bad about the other guys. They are very involved and actually help people out in rom threads that aren't even theirs. We have a great group of folks here. With that said, OvrDrive's I believe has the least complications and he is very responsive. I believe he came from a Note 4 which is where I came from and his reputation on the Note 4 was excellent.

“Google keeps stopping” after Android Oreo update

I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well.
Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

emaillenin said:
I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well. Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
Click to expand...
Click to collapse
Try wiping the cache partition from stock recovery. If you have TWRP (doesn't sound like it) wipe dalvik cache as well.

v12xke said:
Try wiping the cache partition from stock recovery. If you have TWRP (doesn't sound like it) wipe dalvik cache as well.
Click to expand...
Click to collapse
In the stock recovery, I see only these options:
Reboot bootloader - Restarts this recovery
Recovery mode - Boots up and then shows "No Command"
Power off
Barcodes - Shows barcodes of various things about the device.
Start - Starts the device normally, issue still exists
I don't see any option for wiping the cache partition.
I don't have TWRP installed, but will do if that is my last option.

Just figured out how to clear the cache partition from recovery mode. Just tried clearing the cache partition. But the issue still persists.

emaillenin said:
Just figured out how to clear the cache partition from recovery mode. Just tried clearing the cache partition. But the issue still persists.
Click to expand...
Click to collapse
It's kind of a long shot but you can go into settings>>apps and force close and wipe data from both Google App and Google Now Launcher, then restart the phone. If you are still seeing the error regularly then you download the full OTA (.019) and sideload it from recovery mode. You will not lose your data this way. If that sounds too daunting, you can also do a factory reset from recovery which will wipe your userdata, so be sure and back up your stuff before the factory reset.

It's kind of a long shot but you can go into settings>>apps and force close and wipe data from both Google App and Google Now Launcher, then restart the phone.
Click to expand...
Click to collapse
I can't do that, since I am not able to open Settings -> Apps. It gets closed as "Settings has stopped working"
If that sounds too daunting, you can also do a factory reset from recovery which will wipe your userdata, so be sure and back up your stuff before the factory reset.
Click to expand...
Click to collapse
Just did a factory reset. I didn't get the error for an hour. After setting up all my apps for half a day, the error came back. It is unfortunate that even stock Android has issues with Google's official app.

emaillenin said:
I can't do that, since I am not able to open Settings -> Apps. It gets closed as "Settings has stopped working"
Just did a factory reset. I didn't get the error for an hour. After setting up all my apps for half a day, the error came back. It is unfortunate that even stock Android has issues with Google's official app.
Click to expand...
Click to collapse
The problem is on your end. You will need to properly wipe your phone and reinstall Android. I would suggest you just go ahead and unlock your bootloader now, because unlocking at any point in the future will wipe the phone. After that is done, re-install Android 8.0. There are many tutorials on how to do this. It will not void any warranty you may have. It will give you more tools to work with in the future. Good luck.

emaillenin said:
I got a Nexus 6P and it received the Oreo update yesterday. After installing the update, there were few errors like "Gboard stopped working" etc., That happened only once and the device was working normally for few hours. Now suddenly, I keep getting "Google keeps stopping" in the launcher screen. When I close the popup, the launcher is reloaded and the popup appears again immediately. Phone is currently kind of unusable. Tried to open Settings, but that got closed as well.
Tried checking Play Store for the latest updates, but got none. Anyone else got this issue? Any idea if this can be resolved?
Click to expand...
Click to collapse
Try Nova launcher. It's working great. Best luck.

There is some critical error for the new android Oreo (for me is nexus 6p) which make a system crash on the desktop (google now launcher) and on settings (you can't open app list). It is can be created by any of your applications which you need to find. So only way to remove the app, in this case, it is to use a google play application or maybe some other launchers. For me, it was "6 Minute English". I find it via installing nova launcher and on the common app list, the application was shown without a logo, with green robot image instead.

Google keeps syopping after OREO update
I had the same problem with my Samsun Galaxy J7 after the update. I just unstalled the google from the apps. It went back to the previous version. Now the problem is solved