Develop Bugs

4.4.3

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...

4.6.3 is up...

Just wondering if anybody has tried it since there are no posts. I wanted to see if anybody knew the changes.

They started rolling out, Amazon hasn't published download links yet (in case s#it hits the fan), so we will have to wait a little bit longer for qualified answers...
I have no intent to install on my device, but let's see what the changelog will tell us.
edit: BIN file download is available... Thanks to russy23 & wjchen0 for posting the updates. :good:
(Just got home from work and saw the links, nice work.)

I hope the update has a patch for the mms bug called Stagefright.

not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

Well, after the update a warning symbol with the message "Error" appears to the screen.
Now if I try to turn on the device it boots in the recovery mode and nowhere else.
Thx Amazon -.-

JowyOMac said:
Well, after the update a warning symbol with the message "Error" appears to the screen.
Now if I try to turn on the device it boots in the recovery mode and nowhere else.
Thx Amazon -.-
Click to expand...
Click to collapse
I Fixed the problem, I've done the wipe and the factory reset from the recovery. After that i've sideload the update from the pc to the adb fire phone console.
It Works

Any noticible changes??

russy23 said:
Any noticible changes??
Click to expand...
Click to collapse
Haven't seen anything yet. I'm not rooted, just have Google sideloaded. Upgrade went smooth, no issues.

jack9955 said:
I hope the update has a patch for the mms bug called Stagefright.
Click to expand...
Click to collapse
The Bug is possible only with the processing of mms information by Hangouts.
The Fire Phone, doesn't have Hangouts, so it probably wont be infected by the malware.
:cyclops:

JowyOMac said:
The Bug is possible only with the processing of mms information by Hangouts.
The Fire Phone, doesn't have Hangouts, so it probably wont be infected by the malware.
:cyclops:
Click to expand...
Click to collapse
It's not just hangouts that was affected by stagefright. Stock messaging, Facebook Messenger and whatsapp could also trigger it. To my understanding.
Sent from my Fire Phone using the XDA premium app.

russy23 said:
not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
thanks for the link.
Updated the 461013820 rom to 463001420 without any problem. non-rooted device with google play store installed.

The latest software version includes bug fixes.
this is what Amazon said about the new update, well i have to say more:
They fixed the bug of the AID Mode during the call, FINALLY!
They improved battery life. I say this because i've noticed a little improvement on the battery life.
They didn't fixed the bug of the headphone (When you disconnect the headphone while you are listening something such as Youtube, Music etc. If you replug the jack, It doesn't work anymore until you restart the device )
Did someone find anything else?

4.6.3 just being installed on my UK O2-locked Fire Phone (463001420). Looks like the download link is already up on Amazon UK - http://fire-phone-updates.s3.amazon...update-fire-phone-33.4.6.3_user_463001420.bin

I guess my phone tried to update last night... I woke up with my phone stuck in recovery, just continues to boot there... factory reset did not fix.
Help!!

if you are rooted, do you just loose root? Re-root after the update? Thanks.

Just got the OTA update not a big file at all
Installed the google apps..and so far so good

So for those who are wondering, after sideloading through adb, I was able to reroot using kingsroot and was also able to install safetrap and use it.

Any noticible changes??
Sent from my SD4930UR using XDA Free mobile app

russy23 said:
not sure about the changelog, but this page has the updates
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
thanks for the link. I noticed the 4.6.3 update is only for the unlocked version, while the AT&T version is still 4.6.1. When Amazon released the previous 4.6.1 update, they released versions for both AT&T and unlocked. Weird.

Same issue as ediebol reported. Stuck in Recovery. I've done the wipe and reset with no luck. Attempting to sideload, I get the * cannot read update.bin * error in ADB. File is copied to the ADB directory so it shouldn't have any issues finding it.
Anyone have any other ideas?

[Help] Updated to 9.5.2.0 - Google keeps on crashing

So I got my Mix 2 for a while now, it's not rooted.
An update notification popped up 2 days ago and I decided to update today.
Since the update, I get pop ups "Google has crashed", "Google keeps crashing", "Google Play Services crashed" etc.
As I said, my phone isn't rooted.
Is there anything I can do without going through restore and stuff like that?
Thanks !

royrosenfeld said:
So I got my Mix 2 for a while now, it's not rooted.
An update notification popped up 2 days ago and I decided to update today.
Since the update, I get pop ups "Google has crashed", "Google keeps crashing", "Google Play Services crashed" etc.
As I said, my phone isn't rooted.
Is there anything I can do without going through restore and stuff like that?
Thanks !
Click to expand...
Click to collapse
By the sounds of it, you have a chinese version, that must have had an unlocked bootloader and you must have been running Oreo beta to be able to get that update.
If you have the MIUI forum app, check it out, because people with the chinese 9.5.2.0 are having google problems.
I think the only way of fixing this is to flash the Global rom, or wait until they fix the chinese rom. Check out the MIUI forum app though, you might find help on there.
Good luck pal

royrosenfeld said:
So I got my Mix 2 for a while now, it's not rooted.
An update notification popped up 2 days ago and I decided to update today.
Since the update, I get pop ups "Google has crashed", "Google keeps crashing", "Google Play Services crashed" etc.
As I said, my phone isn't rooted.
Is there anything I can do without going through restore and stuff like that?
Thanks !
Click to expand...
Click to collapse
Same here but everything still works. Gmail, Playstore etc are ok on mine.

Cleared the data etc of the Google app?

Twotems said:
Same here but everything still works. Gmail, Playstore etc are ok on mine.
Click to expand...
Click to collapse
Google Assistant force closes constantly. Still getting the "Google Services has stopped" message infrequently but everything else seems to work. I hope they fix it soon because the Oreo update has no extra Chinese bloatware any longer.
Mackay53 said:
Cleared the data etc of the Google app?
Click to expand...
Click to collapse
That doesn't work either unfortunately.

Twotems said:
Google Assistant force closes constantly. Still getting the "Google Services has stopped" message infrequently but everything else seems to work. I hope they fix it soon because the Oreo update has no extra Chinese bloatware any longer.
That doesn't work either unfortunately.
Click to expand...
Click to collapse
Exact the same issue I have. Also google play store every once in a while will have authentication issue.

tigerjade said:
Exact the same issue I have. Also google play store every once in a while will have authentication issue.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-mix-2/help/google-apps-problem-china-oreo-rom-t3767516

How did you install google play on MUI 9.5?
In additional setting it doesn't have an 'allow unknown sources' option it just takes me to the individual app permissions
---------- Post added at 07:10 AM ---------- Previous post was at 07:07 AM ----------
I have the mix 2s If that makes a difference, any help would be much appreciated!
I've downloaded the google installer but it gets to 6% and gives me the same ' cannot install system applications from unofficial channels' error message after the installation is on 6%

rhysjones_! said:
How did you install google play on MUI 9.5?
In additional setting it doesn't have an 'allow unknown sources' option it just takes me to the individual app permissions
---------- Post added at 07:10 AM ---------- Previous post was at 07:07 AM ----------
I have the mix 2s If that makes a difference, any help would be much appreciated!
I've downloaded the google installer but it gets to 6% and gives me the same ' cannot install system applications from unofficial channels' error message after the installation is on 6%
Click to expand...
Click to collapse
You allow unknown sources on an individual app basis now.
Anyway follow these instructions for Google apps installation (same as the link in the previous post which you obviously didn't bother reading):
https://forum.xda-developers.com/mi-mix-2/help/google-apps-problem-china-oreo-rom-t3767516

royrosenfeld said:
So I got my Mix 2 for a while now, it's not rooted.
An update notification popped up 2 days ago and I decided to update today.
Since the update, I get pop ups "Google has crashed", "Google keeps crashing", "Google Play Services crashed" etc.
As I said, my phone isn't rooted.
Is there anything I can do without going through restore and stuff like that?
Thanks !
Click to expand...
Click to collapse
I got my google app working properly after installing the google go version.

Twotems said:
You allow unknown sources on an individual app basis now.
Anyway follow these instructions for Google apps installation (same as the link in the previous post which you obviously didn't bother reading):
https://forum.xda-developers.com/mi-mix-2/help/google-apps-problem-china-oreo-rom-t3767516
Click to expand...
Click to collapse
So which apps do i allow unknown sources for ?
I did read but as I assumed it was a fix for the issues that were being discussed i didn't think it applied to me
thanks

rhysjones_! said:
So which apps do i allow unknown sources for ?
I did read but as I assumed it was a fix for the issues that were being discussed i didn't think it applied to me
thanks
Click to expand...
Click to collapse
If you're using the China rom on Oreo it applies to you.
As you're installing each Google app it should ask you if you want to allow unknown sources.

Twotems said:
If you're using the China rom on Oreo it applies to you.
As you're installing each Google app it should ask you if you want to allow unknown sources.
Click to expand...
Click to collapse
Thanks again and sorry for my noobish-ness.
One final question, i see you have the mix 2, I'm guessing this will still work even tho i have the Mix 2s?
EDIT: so i tried to follow the instructions in that link but i got the parse error. it did however let me install google play and the framework. I am now therefore using the play store and it all seems to be working correctly. Will i encounter any further issues do you know?
Thanks

rhysjones_! said:
Thanks again and sorry for my noobish-ness.
One final question, i see you have the mix 2, I'm guessing this will still work even tho i have the Mix 2s?
EDIT: so i tried to follow the instructions in that link but i got the parse error. it did however let me install google play and the framework. I am now therefore using the play store and it all seems to be working correctly. Will i encounter any further issues do you know?
Thanks
Click to expand...
Click to collapse
The Mix 2s is virtually identical to the Mix 2 so it will work. This is a software issue with the MIUI China Oreo rom and applies to all Xiaomi phones since they all run the same basic software.
Read through that thread from the beginning and you'll find where someone solved his parse error. One solution is to uninstall all the Google apps and download the latest versions from Apkmirror or the Xiaomi forum.

Help Stopping Update to 11 Nag

I've searched and searched and seems no one wanting to stay with Android 10 has run into this problem (unless no one wanted to stay with 10!) I can't seem to figure out how to stop the update nag screen. My fear is that it is going to get accidentally tapped and then I'll be in for a world of work to get back. I've tried disabling all Play notifications but that's not working. The nag usually pops up about once a week. If anyone can help me out I'd appreciate it. Yes, rooted.

There was a thread here a while back about people trying to stay on nine and I believe there was a solution.
see if you can find that thread. same solution may apply to your issue.
Sent from my Pixel 3 XL using Tapatalk
Update: found it!
Not sure if this link will work for you...
https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
If the link fails, The previous thread was started by @KUSOsan on Dec 24 2019. You should be able to find it in search.

@chetqwerty
https://forum.xda-developers.com/pixel-3-xl/help/how-to-stop-date-update-pop-t4024669/page2
If the Tapatalk link doesn't work for ya

Many thanks to both of you, I'll give that a try.
Update with a hiccup:
C:\adb\XL\platform-tools _r30.0.3>Adb shell
crosshatch:/ $ su
Permission denied
Make sure to grant Shell SU rights in Magisk - Then don't freak out after the pm command runs successfully but Magisk keeps crashing until you force stop it, clear it's cache, and restart it to be able to disable Shell SU again.
Will report back if anything wonky results from shutting down the popup.

chetqwerty said:
Many thanks to both of you, I'll give that a try.
Update with a hiccup:
C:\adb\XL\platform-tools _r30.0.3>Adb shell
crosshatch:/ $ su
Permission denied
Make sure to grant Shell SU rights in Magisk - Then don't freak out after the pm command runs successfully but Magisk keeps crashing until you force stop it, clear it's cache, and restart it to be able to disable Shell SU again.
Will report back if anything wonky results from shutting down the popup.
Click to expand...
Click to collapse
If you are rooted you can just do it right from a terminal app on your phone without bothering with ADB. That's how I did it

@chetqwerty
I used terminal emulator which I think was just on the play store but f droid has some as well and there are plenty of other places

KUSOsan said:
If you are rooted you can just do it right from a terminal app on your phone without bothering with ADB. That's how I did it
Click to expand...
Click to collapse
Haha yeah I guess that would have been smart. Saw the ADB command in one of the links you and @CruelSun sent me and followed like a sheep without thinking of terminal. All good short of the Magisk scare which I thought at the time could have been related to changing a system file. A couple more days should tell me if the popup block worked which I would have no reason to think it wouldn't. Next project is to get Miracast working on this thing.

chetqwerty said:
All good short of the Magisk scare which I thought at the time could have been related to changing a system file..
Click to expand...
Click to collapse
Can't really help you with the Miracast but I didn't have any issues with magisk. What magisk are you using?

KUSOsan said:
Can't really help you with the Miracast but I didn't have any issues with magisk. What magisk are you using?
Click to expand...
Click to collapse
Sorry for ghosting you, been a busy month. Not sure which version as I hadn't updated Magisk since I decided to stop updating Android in April. I was using the current release channel at that time. Held off on that too because of the bad press that the revamped version was getting. Anyway it too is current now for what it's worth. I also wanted to update that as you reported in the other thread the method to kill the nag worked with no side affects. Three weeks and no pop-up. Thanks again.

@KUSOsan
Hey Friend - I'm thinking I might have found a side effect maybe? SafetyNet ctsProfile failure. Can you run Magisk SafetyNet check and see if you still pass please? Play Store had a security update last week which I believe may have flagged the state change for the popup. I can be totally wrong but curious if you are seeing ctsProfile failure also.
Thanks,

chetqwerty said:
@KUSOsan
Hey Friend - I'm thinking I might have found a side effect maybe? SafetyNet ctsProfile failure. Can you run Magisk SafetyNet check and see if you still pass please? Play Store had a security update last week which I believe may have flagged the state change for the popup. I can be totally wrong but curious if you are seeing ctsProfile failure also.
Thanks,
Click to expand...
Click to collapse
This may be a coincidence - first three weeks of this month there have been many reports of magisk safetynet check failures. Google seems to be hardening safetynet. Last week my pixel 2 started failing safetynet ctsprofile check and most banking apps and even amazon app would not work. Had to use universal safety net fix by kdrag0n (https://github.com/kdrag0n/safetynet-fix) installed through magisk, plus hide magisk in the app drawer, which I never had to do prior to last week.
Actually the amazon app issue was caused by adaway - adding *amazon* to the allowed list fixed that.

I had considered that, and still maybe the most logical solution, except that all apps including banking, (2 of them and both cloned so 4 fingerprint authenticating banking accounts working fine), Lastpass, Credit Karma, LifeLock, Netflix, all working with no problems. OCD Me hates it but other than the red box in Magisk (confirmed with other cts checkers), phone works great.

Question Android 13: APKs not from PlayStore now crashes at the opening

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