[Q] Help, getting a 923 error. - Nexus 9 Q&A, Help & Troubleshooting

Ever since I came back from the android m preview I have been having difficulty with Google apps. I have gotten error 923.
Timeline:
Flash M preview, have fun
Go back to 5.1.1
- this where I first got the 923 error and nothing would update it the Google play store. Also had WiFi connection issues.
Went all the way to 5.0.1 didn't see any issues
Tried uploading DU and its minimal gapps package.
- got a lot of Google apps error not working or something
- I think this is also where I got an error on initial setup saying "there's an internal problem with your device. Contact your manufacturer for details.
Back to 5.1.1 same issue error 923

Try the steps listed in this post:
http://forum.xda-developers.com/showthread.php?p=61433504
You only need to go up to step 5. The steps after that are just for installing DU.
(Oh, and you can ignore that warning message you get on boot. It's not important)
Sent from my Nexus 9

Related

App installing error after installing xposed (Moto E2)

Hey there,
Sorry for making an extra thread. I am using Moto E2. I tried searching and applying the possible methods to get it working but nothing seems fine now.
This is the error which I am getting. Also each time i reboot it starts upgrading all apps.
xxxx can't be installed.
Try again, and if this problems continues, get help troubeshooting. (Error code : -504)
It was working good before I installed this :
- XposedInstaller_3.0_alpha4.apk
- Xposed-v75-sdk21-arm.zip
Methods I have tried :
Clearing data and caches
Removing Google account

Nexus 9 update failure

I'm a newbie and trying to sort out my issue. I don't know all the tech jargon, so please consider that if replying.
Yesterday I okay-ed the latest update for our Nexus 9 - stock standard on Marshmallow. Got a persistent error "'Nfc stopped working" and neither the Ok nor the Report option would close the notification. I still could see the install update notice behind but couldn't access it. I tried booting in safe mode and briefly got the message the device was corrupt. When the safe mode boot was complete, the same error message still existed and I could not close the error notification.
I then tried a factory reset but now the device doesn't even get beyond the continually animated dots.
I found this post: http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704 and went through all the steps.
I tried to load this OTA:
6.0.1 (MMB29S) Link 59ab9d2ad432610244e54696775316cf fc7b590e6e6cbda6c1afdecfaed72a065359eeee
I verified the checksum on the download and all is good.
However, I can't get the update to load and this is what I get on screen:
Supported API: 3
Send package to device with adb sideload <filename> etc.
Finding update package
Opening update package
Verifying update package
E: Footer is wrong.
E: signature verification failed
Installation aborted.
At top of screen is this information:
Android Recovery
google/volantis/flounder
6.0.1/MMB29S/2489379
user/release-keys
use volume up/down and power
Then the menu
I am at a loss what to do now. The Tablet was bought through Google Play Store, so I can't even take it back to where I bought it.
Thanks
Greg
Update
Just to let anyone reading this thread that I contacted Google and they are replacing the tablet.

UI system error

After upgrade apps yesterday I get "UI system error" on my screen when I hold down the Home button.
I tried everything including Factory reset, but again when standard apps are upgraded error message comes again.
There no 3rd party apps installed at the moment ONLY default apps.
How to solve this problem?
Thanks
Which ROM is on the phone?
No ROM, default OS, with root been made.
I tried to flash CM 14 or Lineage OS, but for both I get error during verifycation, says: can't verify whole-file signature.
I had the same problem (rooted phone but standard ROM) and found a youtube video where it told me to uninstall the last Google update which I did and it cured the problem.
centralman01 said:
I had the same problem (rooted phone but standard ROM) and found a youtube video where it told me to uninstall the last Google update which I did and it cured the problem.
Click to expand...
Click to collapse
Send the link please!
The phone must have a rom installed; otherwise, it would never boot to a system UI.
Hi,
I had the same issue and after checking around the web, seems to be google app's latest update at fault here. Go to setting and uninstall updates. Worked for me!
Yes! Google App was the problem thank you!
Yep, getting this issue on my stock rooted s3. Can't view recents, just crashes the ui. Out of the blue, phone hasn't been used for anything but calls and texts.
Beamed in by telepathy.

Help! Samsung Galaxy Tab 4 SM- T530NU

Hi! I recently rooted my tablet and removed some system apps/bloatware. Since doing so I get two reoccurring messages,
1.) Unfortunately Google Play services has stopped
2.) Unfortunately, the process com. google. process. gapps has stopped.
Also, when I try to set up any Google services, I get a message saying " Couldn't sign in there was a problem communicating with Google services try again later",
regardless how many times I try this message just repeats and doesn't sign me into anything.
I've tried to factory reset and everything I can think of, all with no luck. I'm guessing the firmware and gapps need to be re-installed, but I'm not sure. When I try to download anything it fails. I don't have a computer, so I'm hoping to be able to apply the fix to the tablet itself. I have also tried to unroot, but that hasn't made much difference . Again my model # SM T530NU, running 4.4.2. Any help would be greatly appreciated...

Stuck on Checking for Updates...

Every rom I try flashing gets stuck on checking for updates when I set up my mobile. It happened multiple times before but I went 1 step back and re-tried and It worked. Now It's just always checking for updates. Tried restarting several times, still the same. I fully wiped my mobile, flashed latest firmware for kate(7.12.14 including emmc_appsboot.mbn), latest rom(NOS & RR) and latest gapps(tried nano,micro,mini,aroma, same outcome). That keeps happening on NOS 8.1 and RR 7.1.2. Same flashing procedure followed for both ROMs. I always flashed ROMs this way and never had a problem. Any clue wth is going on? Using TWRP 3.2.1.0
Skipped the set up on NOS 8.1 and I get a message saying I can't connect to google services whenever I open up Play Store or attempt to add a Google Account. Still doesn't fix my issue skipping the set up.

Categories

Resources