Related
I took my GNex in the evening from the Assistance Center where they changed my broken MicroUSB port.
They flashed on it 4.0.4 ICS and they unlocked the bootloader.
I update the system with OTA to 4.3 stock.
In order to try the Xposed Framework I used the Toolkit to take root access.
Then, connecting my Google account, when Play Store started to install all of my apps it prompted out an infinite list of error:
first (403)
then (920)
Flashed two times 4.3 stock via Toolkit, locked and unlocked, rooted and unrooted but... nothing.
Also tried to delete my account, delete play store data, delete framework data, wipe cache, wipe dalvik... nothing works.
Phone is uselss in this way... so if anyone has figured out what to do, please let me know.
omegakibou said:
I took my GNex in the evening from the Assistance Center where they changed my broken MicroUSB port.
They flashed on it 4.0.4 ICS and they unlocked the bootloader.
I update the system with OTA to 4.3 stock.
In order to try the Xposed Framework I used the Toolkit to take root access.
Then, connecting my Google account, when Play Store started to install all of my apps it prompted out an infinite list of error:
first (403)
then (920)
Flashed two times 4.3 stock via Toolkit, locked and unlocked, rooted and unrooted but... nothing.
Also tried to delete my account, delete play store data, delete framework data, wipe cache, wipe dalvik... nothing works.
Phone is uselss in this way... so if anyone has figured out what to do, please let me know.
Click to expand...
Click to collapse
I seem to have the same problem. I can't update nor download apps from the play store because I keep getting 403 errors.
Everything was fine until I flashed CM REMIX rom. That's when I started getting the errors. However nobody is complaining about anything like this on their thread. I've also tried using different gapps packages.
Could it be a server side thing? My other devices seem to be working fine on the same network...
evilnoxx said:
I seem to have the same problem. I can't update nor download apps from the play store because I keep getting 403 errors.
Everything was fine until I flashed CM REMIX rom. That's when I started getting the errors. However nobody is complaining about anything like this on their thread. I've also tried using different gapps packages.
Could it be a server side thing? My other devices seem to be working fine on the same network...
Click to expand...
Click to collapse
I saw on another android board that this is happening also on some brand new Nexus 5, activated just today.
Almost sure it's a server side thing at this point.
omegakibou said:
I saw on another android board that this is happening also on some brand new Nexus 5, activated just today.
Almost sure it's a server side thing at this point.
Click to expand...
Click to collapse
If it is, I hope it gets fixed soon, coz my phone barely has any apps right now...
If it's not a server thing I'll try to flash my old rom to see if it helps.
evilnoxx said:
If it is, I hope it gets fixed soon, coz my phone barely has any apps right now...
If it's not a server thing I'll try to flash my old rom to see if it helps.
Click to expand...
Click to collapse
I flashed 4.3 stock multiple time but id doesn't work
Right now it downloaded some apps and update some others... then started again to prompt that error.
Mah.
omegakibou said:
I flashed 4.3 stock multiple time but id doesn't work
Click to expand...
Click to collapse
Since you are flashing the official 4.3 rom, I really think the problem will just go away by it self (hopefully very soon)
Edit: It started working now all by it self!
evilnoxx said:
Since you are flashing the official 4.3 rom, I really think the problem will just go away by it self (hopefully very soon)
Edit: It started working now all by it self!
Click to expand...
Click to collapse
The problem disappeared in a couple of hours. It was a server side problem for sure!
omegakibou said:
The problem disappeared in a couple of hours. It was a server side problem for sure!
Click to expand...
Click to collapse
Just though you should know: droid-life.com/2014/02/11/psa-handful-of-android-device-owners-being-met-with-403-error-in-google-play
Avaliable from today? Now i installing new update
Odoslané z LT30p pomocou Tapatalku
Yes, it seems to work very well. Re-rooted with Nexus Root Toolkit v1.8.3. Just had to re-enable usb debigging first. The toolkit even updated itself with KTU84L binary (4.4.3 for Nexus2013).
I just updated mine, nothing different though, I guess its only bugs fix
Nam Huy Linux http://namhuy.net
Hi guys, so I got the notification about the update, but I forgot I had to have the stock recovery to install it, and I pressed the install update, it locked my bootloader, but didn't update to 4.4.3, now if I go to system update, press check for updates, it say I'm on latest update. What should I do now?
Szighy said:
Hi guys, so I got the notification about the update, but I forgot I had to have the stock recovery to install it, and I pressed the install update, it locked my bootloader, but didn't update to 4.4.3, now if I go to system update, press check for updates, it say I'm on latest update. What should I do now?
Click to expand...
Click to collapse
Boot into twrp, and flash it manually, you'll find the ota zip in /cache.
Unless you are serious/correct about it locking your bootloader, which I never heard of an update doing, then you got a different issue.
I did the same thing, but there's no update in that folder
Sent from my Nexus 7 using XDA Free mobile app
one got it, not the other
I've two Nexus 7 2013 units. One got the update message (and it worked) but the other has not. Tried checking for updates on it and it says it's up to date (running 4.4.2). No biggie, just curious that one got it but not the other.
Still haven't rooted either of them yet.
wkearney99 said:
I've two Nexus 7 2013 units. One got the update message (and it worked) but the other has not. Tried checking for updates on it and it says it's up to date (running 4.4.2). No biggie, just curious that one got it but not the other.
Still haven't rooted either of them yet.
Click to expand...
Click to collapse
Nothing to be curious about, it's just the way they roll it out.
Go to all applications and clear cache for google services framework. Then recheck for update..
mulperi said:
Go to all applications and clear cache for google services framework. Then recheck for update..
Click to expand...
Click to collapse
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
phazerorg said:
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
Click to expand...
Click to collapse
Yep. Agreed, it's much safer to just side load it.
Sent from my 831C using Tapatalk
phazerorg said:
Not trying to start that debate again, but anyone considering doing this should at least be aware of this article before doing it: Don't clear data for Google Services Framework
Click to expand...
Click to collapse
Agreed, blanket dumping of data certainly has it's place. I wasn't sure this was one of them. That and I'm honestly ot in any kind of rush to force updates. Still, it's been a few days and the one tablet is still not showing 4.4.3 as available yet. Both are logged into the same google account. No rush, my to-do list has PLENTY of other things on it...
Not sure if this is Z Play specific, but I'm running Android 7.0, with the 1st April patch
I've not used WiFi for a while, so I've got 37 updates for apps. Whenever I update, the first app gets to 100% downloaded but then just stays there. A reboot might let me update 1 app, but then the problem returns.
Any ideas?
MotoZPlayBoi said:
Not sure if this is Z Play specific, but I'm running Android 7.0, with the 1st April patch
I've not used WiFi for a while, so I've got 37 updates for apps. Whenever I update, the first app gets to 100% downloaded but then just stays there. A reboot might let me update 1 app, but then the problem returns.
Any ideas?
Click to expand...
Click to collapse
Go to your Apps section, see the System Apps, then clear all Data on the Play Store and try again.
Clear playstore data and try.
If that doesn't work then hard reset is the last option.
Jimi Mack said:
Go to your Apps section, see the System Apps, then clear all Data on the Play Store and try again.
Click to expand...
Click to collapse
Tried this, still doesn't work
MotoZPlayBoi said:
Tried this, still doesn't work
Click to expand...
Click to collapse
Sorry, that was the simple answer. The next step would be do a complete phone reset.
MotoZPlayBoi said:
Tried this, still doesn't work
Click to expand...
Click to collapse
I would first do the update to android 7.1.1. For me this fixed many bugs. And you get 06/2017 security patch with over 100 bug fixes. Just check, maybe the update is there.
I never was aware of this before. When I was setting up my phone again after unlocking my bootloader I saw that my play store is uncertified. Does this have to do with the bootloader?
GroovinChip said:
I never was aware of this before. When I was setting up my phone again after unlocking my bootloader I saw that my play store is uncertified. Does this have to do with the bootloader?
Click to expand...
Click to collapse
If you're running magisk after a few reboots it'll go certified or you can just go to settings apps Google Play Store clear data and it'll go back to certified
mac796 said:
If you're running magisk after a few reboots it'll go certified or you can just go to settings apps Google Play Store clear data and it'll go back to certified
Click to expand...
Click to collapse
I've cleared data a few times and it keeps coming back. Not running Magisk yet as I have some other questions I'm getting answers for first.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
I've cleared data a few times and it keeps coming back. Not running Magisk yet as I have some other questions I'm getting answers for first.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
Yeah I don't think you'll ever be certified if you run just SuperSU I believe the only rom that will say certified if you run it stock is pure Nexus other than that it'll always say uncertified until you install magisk.
It's not a big deal there's just a few banking apps and think of Mario run maybe Netflix which some of those you can get off the mirror site
mac796 said:
Yeah I don't think you'll ever be certified if you run just SuperSU I believe the only rom that will say certified if you run it stock is pure Nexus other than that it'll always say uncertified until you install magisk.
It's not a big deal there's just a few banking apps and think of Mario run maybe Netflix which some of those you can get off the mirror site
Click to expand...
Click to collapse
I'm not even rooted yet though :/
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
I'm not even rooted yet though :/
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
If you're not rooted or not on a custom rom I would go to settings apps Google Play Store and clear the data
The bootloader is a safety net check. Probably what's causing the issue.
pcriz said:
The bootloader is a safety net check. Probably what's causing the issue.
Click to expand...
Click to collapse
Gotcha. Thanks!
Sent from my Google Pixel XL using XDA Labs
Ok but what if bootloader was unlocked then relocked, never rooted, factory reset, and from fresh boot it says not certified. Even finished set up and cleared data / cache and still squat.
Granted its only blocking Netflix now but its still not "right" any ideas is greatly appreciated
[email protected] said:
Ok but what if bootloader was unlocked then relocked, never rooted, factory reset, and from fresh boot it says not certified. Even finished set up and cleared data / cache and still squat.
Granted its only blocking Netflix now but its still not "right" any ideas is greatly appreciated
Click to expand...
Click to collapse
Clear data and cache of Google Play Store. Then reboot. It should become certified.
[email protected] said:
Ok but what if bootloader was unlocked then relocked, never rooted, factory reset, and from fresh boot it says not certified. Even finished set up and cleared data / cache and still squat.
Granted its only blocking Netflix now but its still not "right" any ideas is greatly appreciated
Click to expand...
Click to collapse
Sure sounds like it should say certified after your steps. Sounds like there is some remnant of the certification on the Google side. Wondering if you have another device logged onto the same Google account (or one to start fresh with and test like an old phone that you could use over WiFi). Maybe it would resolve a conflict.
As for the Netflix block, the side-load version on the Netflix site works fine. The bootloader is unlocked on both of my boys' phones, but they are not rooted (so I can't use Magisk Hide on the Play Store). It still trips SafetyNet because of the unlocked bootloader, so I needed to install the .apk.
I just Magisk Hide root from Play Store and Google Play Services, clear Play Store storage and reboot phone. Then it goes back to being certified and I can find Netflix again without a problem, even with my bootloader unlocked.
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks