Nexus 5 not updating all Google apps - Nexus 5 Q&A, Help & Troubleshooting

I flashed my N5 back to latest stock and relocked bootloader. My problem is that the playstore does not show updates for all of the google apps, like keyboard or photos. Some do get updated though. I can still update them manually by searching them, but why does playstore not recognize them in the first place?

You can manually update the apps.
I prefer to leave my bootloader unlocked as relocking and unlocking wipes the phone.

Related

[Q] New to the Android world, i have afew questions for your

I'm totally new to the Android world and i spent many hours to read this forum to learn as much as possible about my device and what i can do with it. But now, i need your help on a few things.
KitKat vs Lollipop, does it make sense to upgrade to Lollipop now or should i wait? Is there any major know bugs?
Since that i only have a 8gb device, i would like to clean the apps as much as possible. There's many apps that i don't need but they can't be uninstalled. For example, all the Motorola apps (is there something that we really need from them?), a few google apps like Google+, Google Play Films, Hangouts, etc that i will never use.
I want a stable ROM that i don't need to patch every day to solves problems. When i read about CM12 for Moto G, i see people that have problems here and there and wait for the next daily build to give it a try. I don't want to play that game!
If i install a custom rom, i guest that future updates will not come from Motorola. How the updates work afterward?
It's ok if i must have my device rooted
I have read about stock lollipop optimized version by lost101 but it don't think that the versions currently available will work for me. I'm in Canada and the versions that i see is Brazil or Asia.
thank you for you help!
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Well what I will say is. I'm in the uk using lost101s BR optimized and I'm very pleased with it.
audit13 said:
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Click to expand...
Click to collapse
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
skoub2 said:
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
Click to expand...
Click to collapse
You must unlock boot loader first then flash a custom recovery (manually or there is a tool in the development section) then rooting next.
Unlocking the bootloader allows you to install non-Motorola software. With a locked bootloader, the only software that can be loaded on your phone would have to be digitally signed by Motorola.
Rooting gives you administrative access to the system files.
You may not need an unlocked bootloader to get root and you do not need root to unlock a bootloader.
Start here to get the bootloader unlock code: https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
I tried to install TWRP (any version available) but it take like 1 minutes to show the home screen and im not able to "swipe to unlock". So i have installed Philz recovery and then installed lost101 Retail Brazil 5.0.2 Stock ROM (Optimized) v1.1a. I'm playing with it right now and so far so good.

Unable to get OTA updates on Xperia Z5

Hello! I'm new here and actually the main purpose of my registration on this wonderful website is the amount of helpful and skillful people I saw in various threads I read before, giving me hope for the solution of my problem.
As stated in the title, I'm currently unable to get OTA updates on my phone.
Some time ago I unlocked the bootloader (so my bl is unlocked now) in order to have my Z5 rooted. Apparently something went awfully wrong while flashing the TWRP or perhaps I was just awfully stupid and missed a step... Anyways I ended up without any OS and started searching on the web for some solutions.
I came across FlashTool and XperiFirm, then downloaded and flashed the (at the time) latest firmware, which is the one i currently have (Service Menu shows "GENERIC_32.2.A.0.224"). So now my phone seems perfectly fine: stock rom, no custom recovery (as far as I know), no root privileges. The only problem it shows is the fingerprint hardware that stops working every once in a while; something a simple reboot fixes.
But I have been unable to update since then, with my "software update" tab showing no available updates (nor could I get one via Sony PC Companion, furthermore getting errors while trying fo repair software) while under "diagnostics" it clearly says "new software available".
I just want to get everything back as it was before, and to get my OTA updates to work; I'm not interested in custom ROMs or custom recoveries or SU.
I apologize in advance in case an identical thread had already been opened and closed; I hope you guys can help me solve this mess I did.
Thanks a lot
I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
scacio said:
I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Once you have unlocked the Bootloader ota updates don't work EVER only manually flashing the ftf via flashtool will get you updated. If you unlocked the Bootloader without backing up the drm/ta keys then re-lock the Bootloader ota updates will Not work. If you unlock the Bootloader and then re-lock with previously backed up drm/ta keys ota updates WILL work.
The drm fix does NOT replace the missing drm/ta keys it merely tricks the device into thinking that those required for x-reality, low light conditions, and noise reduction in the camera are there to reactivate those features.
Also DO NOT try to use a other Xperia devices drm/ta keys on your own unless you want a permanent paperweight.
Sent from my Xperia XA using XDA Labs
Ah, so I should have backed those up before unlocking the bootloader. It seems I'll have to spend a few minutes on flashtool every once in a while to get updates, nevermind.
Anyway is it worth it to try this DRM fix? I did not notice any changes to the quality of the camera.
And another noob question: if I flash this "modified kernel" will my device be wiped? Or I just flash it, reboot the phone and enjoy DRM features?
Just a quick update to let you know, I have installed the drm fix and rooted, the funny thing is that now I receive ota updates.. But of course I'm unable to install them. Not that I want them anyway, so no problem. I have reconsidered the potentiality of a rooted device and started to appreciate the benefits; thanks for the help

Is it possible to sideload OTA and downgrade with a locked bootloader?

Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
farfromovin said:
Title says it all. I have a 7.1.2 (beta) Pixel on VZW with a locked bootloader. I'd like to go back to 7.1.1 public static le release. I unenroll from the beta program and I haven't got an OTA to go back. It's been over 24hrs.
I know Google will eventually fix their OTA beta system, but in the meantime can't I do this manually?
I tried to side load the 7.1.1 OTA from Google via ADB and it gave me an error about being older than the version currently on the device. Is there a file I can modify in the OTA.zip to get around that or am I stuck as long as my bootloader is locked?
Click to expand...
Click to collapse
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
bobby janow said:
You're stuck for now. Don't modify anything that might brick the device since you can't recover with a locked bl. Just wait for the public release to be sent to the device. Why do you want to go back to 7.1.1?
Click to expand...
Click to collapse
Ok thanks. I didn't notice anything new with 7.1.2 other than a couple little bugs. I had some graphical tearing on the status bar initially and then wifi advanced settings continuously crashes if you try to open it. Personally, I like 7.1.1 better than the first beta 7.1.2.
Since the update to 7.1.1 any possibility to downgrade is blocked. Verizon pushed the update to block any method that allows bootloader unlock. If you were locked and took the OTA you are permanently locked. Although anything is possible do not hold out for a new exploit to be found. I have never seen a new method found to unlock a device that has had the exploit patched.

Flashing system image on Verizon Pixel 3 ?

Guys, I decided to opt in to the Android Q beta but unfortunately, no matter what I try, the OTA won't download and keeps pausing itself. So I decided to flash the system image from here: https://developer.android.com/preview/download.html
However, it seems like that requires a bootloader unlock.. The Verizon Pixel 3 has a locked bootloader (without possible unlock).. so it is possible to proceed while the bootloader is still locked? What might happen if I go ahead and execute "flash-all" script in fastboot?
Never mind this.. the OTA finally worked on cellular.. just never on wifi for some reason

Google Play Uncertified

After coming back to stock MIUI ROM my google play is displaying uncertified. I know it is because of the unlocked bootloader or at least that's what I think it is. Now is there any way for me to make my phone google play certified again?
This warning gets triggered and thrown when an unlocked bootloader, a rooted device, a flashed custom ROM, flashed custom packages such as Magisk, Xposed, and of course, installed Gapps on uncertified devices get detected by Google Play Services. Even as small as "enabling OEM unlock" on phone can trigger Google Play Services to throw an uncertified device error on Play Store.
What I'ld try do to fix it:
Disable OEM Unlock option from Developer Options if you have already enabled it.
If you have unlocked bootloader on your phone, then re-lock it.
Flash certified Gapps.
jwoegerbauer said:
This warning gets triggered and thrown when an unlocked bootloader, a rooted device, a flashed custom ROM, flashed custom packages such as Magisk, Xposed, and of course, installed Gapps on uncertified devices get detected by Google Play Services. Even as small as "enabling OEM unlock" on phone can trigger Google Play Services to throw an uncertified device error on Play Store.
What I'ld try do to fix it:
Disable OEM Unlock option from Developer Options if you have already enabled it.
If you have unlocked bootloader on your phone, then re-lock it.
Flash certified Gapps.
Click to expand...
Click to collapse
Yes, I'm right now on a custom ROM and it is certified. Now I want to go back to stock ROM and have it certified without locking bootloader (bypass it). Is there any way to bypass it and make google think and display it as a certified?
Hooblet said:
Yes, I'm right now on a custom ROM and it is certified. Now I want to go back to stock ROM and have it certified without locking bootloader (bypass it). Is there any way to bypass it and make google think and display it as a certified?
Click to expand...
Click to collapse
If you're flashing stock firmware, I think it'll mostly be certified. No need to re lock bootloader (that's what I think. Point me if iam wrong !!!)
Arc android said:
If you're flashing stock firmware, I think it'll mostly be certified. No need to re lock bootloader (that's what I think. Point me if iam wrong !!!)
Click to expand...
Click to collapse
I did flash Stock Firmware, ROM and it's displayed as uncertified MIUI Global Rom (Latest version) and the play store doesn't want to update itself at all. I can download google apps through play store but the play store just won't budge.
Had to flash stock MIUI and lock the bootloader. Now everything works fine as it did before.

Categories

Resources