Develop Bugs

Any to Bring Back Android Subsystem?

I liked project astoria bcoz it solved the app gap problem.
Many hackers here are able to hack W10M beyond levels. so I wanna know if there is any way to bring back. Android subsystem?
Maybe a copy past of the android subsytem file found in older builds? and some registery changes?
Sent from my E79 using Tapatalk

No, there is no way to bring Astoria back. It is hard blocked within the kernel, plus system policies prevent it from running.

snickler said:
No, there is no way to bring Astoria back. It is hard blocked within the kernel, plus system policies prevent it from running.
Click to expand...
Click to collapse
Wait... What??? You mean to tell me that they disabled Hyper V "within the kernel"?
How would that even work? And why the hell would they go out of their way that much?
If a consumer can't easily enable it, it is essentially a non-issue to whatever concerns prompted them to disable it in the first place....
But, regardless of that, who cares? As soon as we have SecureBoot unlock, we can break out of the chain of trust and simply patch the Kernel. F U C K MS!

snickler said:
No, there is no way to bring Astoria back. It is hard blocked within the kernel, plus system policies prevent it from running.
Click to expand...
Click to collapse
hard blocked from kernel? then how WSL works in pc? mobile and pc uses the same NT kernel
Sent from my E79 using Tapatalk

iammomin said:
hard blocked from kernel? then how WSL works in pc? mobile and pc uses the same NT kernel
Sent from my E79 using Tapatalk
Click to expand...
Click to collapse
They might use the same kernel, but they can very well configure it in different ways. Especially for different architectures.

Shad0wKn1ght93 said:
But, regardless of that, who cares? As soon as we have SecureBoot unlock, we can break out of the chain of trust and simply patch the Kernel. F U C K MS!
Click to expand...
Click to collapse
If we can patch the kernel then we can Re enable the android subsystem and make it work again?
Sent from my E79 using Tapatalk

Shad0wKn1ght93 said:
Wait... What??? You mean to tell me that they disabled Hyper V "within the kernel"?
How would that even work? And why the hell would they go out of their way that much?
If a consumer can't easily enable it, it is essentially a non-issue to whatever concerns prompted them to disable it in the first place....
But, regardless of that, who cares? As soon as we have SecureBoot unlock, we can break out of the chain of trust and simply patch the Kernel. F U C K MS!
Click to expand...
Click to collapse
At one point, they completely blocked LXSS.sys from running in the kernel after 10571 (this COULD be changed since RS1, I haven't checked but still most likely the case. I'd love to be proved wrong on that one though ) . They also blocked loading of the aow.wim and the AOW runtime service in the kernel, the winload.efi and some other core files. They also pushed file system policies to prevent the execution of the aow.wim. I'll have to look back to see if I can find the exact policy changes, but it was already rolled up in 10571 on forward.
Also, I'm almost certain they put changes to block certain functions from executing in the case that lxss.sys was loaded.

snickler said:
At one point, they completely blocked LXSS.sys from running in the kernel after 10571 (this COULD be changed since RS1, I haven't checked but still most likely the case. I'd love to be proved wrong on that one though ) . They also blocked loading of the aow.wim and the AOW runtime service in the kernel, the winload.efi and some other core files. They also pushed file system policies to prevent the execution of the aow.wim. I'll have to look back to see if I can find the exact policy changes, but it was already rolled up in 10571 on forward.
Also, I'm almost certain they put changes to block certain functions from executing in the case that lxss.sys was loaded.
Click to expand...
Click to collapse
Here is a tweet from the Windows Insider "Core":
https://twitter.com/tfwboredom/status/770908902946930688
Although it is a bit older.

todarkness said:
Here is a tweet from the Windows Insider "Core":
https://twitter.com/tfwboredom/status/770908902946930688
Although it is a bit older.
Click to expand...
Click to collapse
Yeah, I saw that when he posted it. @tfwboredom - Did they happen to let up on the restrictions they had?

snickler said:
At one point, they completely blocked LXSS.sys from running in the kernel after 10571 (this COULD be changed since RS1, I haven't checked but still most likely the case. I'd love to be proved wrong on that one though ) . They also blocked loading of the aow.wim and the AOW runtime service in the kernel, the winload.efi and some other core files. They also pushed file system policies to prevent the execution of the aow.wim. I'll have to look back to see if I can find the exact policy changes, but it was already rolled up in 10571 on forward.
Also, I'm almost certain they put changes to block certain functions from executing in the case that lxss.sys was loaded.
Click to expand...
Click to collapse
Well, if what you say is correct, then it seems they thought of this as a security risk indeed.... But, all of these checks should be TRIVIAL to bypass after killing secure boot. Getting Astoria running is a different story of course. Windows 10 changes more often that longhorn under the hood...

Shad0wKn1ght93 said:
Well, if what you say is correct, then it seems they thought of this as a security risk indeed.... But, all of these checks should be TRIVIAL to bypass after killing secure boot. Getting Astoria running is a different story of course. Windows 10 changes more often that longhorn under the hood...
Click to expand...
Click to collapse
Possibly. It'll take quite the modification to system files. They do some stupid and annoying checks in the most awkward dlls that you wouldn't even think of.

snickler said:
Possibly. It'll take quite the modification to system files. They do some stupid and annoying checks in the most awkward dlls that you wouldn't even think of.
Click to expand...
Click to collapse
I know... But I have my hopes up.

Shad0wKn1ght93 said:
I know... But I have my hopes up.
Click to expand...
Click to collapse
CMD as System access,Project astroria,Android on Windows phone ,disabling Secure boot ,these are not much useful as you think of,WM 10 is in continuous development ,you can't patch It for not much useful thing,even you did they can't work in next update/new features
Personalisation and performance hacks are always welcome.start up fellows don't try these and blame our forum members like not replying and all, its a free time participation they may have their busy life.if something wrong read the post reply's thoroughly gain some information research it & get it done.:good:

Shad0wKn1ght93 said:
I know... But I have my hopes up.
Click to expand...
Click to collapse
After patching the kernel, we can make it work again?

raghulive said:
CMD as System access,Project astroria,Android on Windows phone ,disabling Secure boot ,these are not much useful as you think of,WM 10 is in continuous development ,you can't patch It for not much useful thing,even you did they can't work in next update/new features
Personalisation and performance hacks are always welcome.start up fellows don't try these and blame our forum members like not replying and all, its a free time participation they may have their busy life.if something wrong read the post reply's thoroughly gain some information research it & get it done.:good:
Click to expand...
Click to collapse
These are just the starting of new era of w10m. hacking is always there to identity the loophole of the system.

todarkness said:
Here is a tweet from the Windows Insider "Core":
https://twitter.com/tfwboredom/status/770908902946930688
Although it is a bit older.
Click to expand...
Click to collapse
even he wants it. I will also dig through it

This is a very interesting thread. I hope some of you are taking this project on. MS removing Project Astoria capabilities was a very poor decision, especially now in hindsight as there hasn't been much in the way of new and exciting apps for W10M. Having the capability to run Android Apps on a linux subsystem would help to keep many of us hold outs from defecting to other platforms. If someone is looking into this please start with the Lumia 950 series of devices if possible.

MBXONE said:
This is a very interesting thread. I hope some of you are taking this project on. MS removing Project Astoria capabilities was a very poor decision, especially now in hindsight as there hasn't been much in the way of new and exciting apps for W10M. Having the capability to run Android Apps on a linux subsystem would help to keep many of us hold outs from defecting to other platforms. If someone is looking into this please start with the Lumia 950 series of devices if possible.
Click to expand...
Click to collapse
I'm working on bringing it back on a spare 1520. If anyone has any more information about how exactly they disabled it, I'd appreciate it.

ninjaofbacon said:
I'm working on bringing it back on a spare 1520
Click to expand...
Click to collapse
Could you please explain what are you doing and how your are "working on" it? Do you have a latest Windows 10 core sources plus old trunk with the project "Astoria" sources?
Could you provide any sample of the high-end whitehat's successful projects you've already worked on and released to the general public?
Or you just speculating with the irresponsible words on the public forum, looking for some cheap popularity?

sensboston said:
Could you please explain what are you doing and how your are "working on" it? Do you have a latest Windows 10 core sources plus old trunk with the project "Astoria" sources?
Could you provide any sample of the high-end whitehat's successful projects you've already worked on and released to the general public?
Or you just speculating with the irresponsible words on the public forum, looking for some cheap popularity?
Click to expand...
Click to collapse
^This.
---------- Post added at 01:08 PM ---------- Previous post was at 01:07 PM ----------
MBXONE said:
This is a very interesting thread. I hope some of you are taking this project on. MS removing Project Astoria capabilities was a very poor decision, especially now in hindsight as there hasn't been much in the way of new and exciting apps for W10M. Having the capability to run Android Apps on a linux subsystem would help to keep many of us hold outs from defecting to other platforms. If someone is looking into this please start with the Lumia 950 series of devices if possible.
Click to expand...
Click to collapse
Rest assured, *IF* it is accomplished, it will probably come to your device eventually.

New OTA: NPN25.137-83

New update for me to install. I downloaded it, but haven't installed it yet.
I'm in the US on the Sprint network. Showed the August 2017 security update. I can't remember if there were other fixes or updates. It was only 168mb.

Just had it pop on mine in the last 5 minutes... On AT&T in North Dakota, already 50% though updating... I grabbed the url though: https://mobilesupport.lenovo.com/us/en/solution/MS122856
Moto G5 Plus - Maintenance Release Notes
INTRODUCTION
Motorola is excited to announce a new software update for Moto G5 Plus by Motorola. This update brings important improvements to your phone.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.
ENHANCEMENTS
This update introduces changes including the following:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.
INSTRUCTIONS
For a successful installation, we recommend installing this update when the battery in your phone is at least 50% charged and you are connected to a Wi-Fi network.
If you have received a notification message for this update:
Select "Yes, I'm in".
After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated.
If you have not received a notification message for this update, follow the steps below to manually update your phone:
Select the Settings icon in the apps menu.
Select "About phone".
Select "System updates".
Select "Yes, I'm in". After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated.
Additional Information
If you have difficulty with this upgrade, visit us at www.motorola.com/mymotog.
Click to expand...
Click to collapse

After boot system info for those interested...

acejavelin said:
After boot system info for those interested...
Click to expand...
Click to collapse
Installing now myself.
Does Lenovo ever publish what the changes actually are? Hopefully some security updates.

androcraze said:
Installing now myself.
Does Lenovo ever publish what the changes actually are? Hopefully some security updates.
Click to expand...
Click to collapse
Moto says the same as most other manufacturers... see the post or link above.

acejavelin said:
Moto says the same as most other manufacturers... see the post or link above.
Click to expand...
Click to collapse
Thanks. I've come over from the N5. We discussed my ROM at one point. How are you liking the G5+?
EDIT:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.

androcraze said:
Thanks. I've come over from the N5. We discussed my ROM at one point. How are you liking the G5+?
EDIT:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.
Click to expand...
Click to collapse
Ahhh... I knew the name sounded familiar and it just clicked.
I like it a lot actually, battery life is amazing and that seems to be my major thing lately, most other things seem of less importance now days, but to be honest it has been a solid device going on 6 or 7 weeks now. It just works.

acejavelin said:
Ahhh... I knew the name sounded familiar and it just clicked.
I like it a lot actually, battery life is amazing and that seems to be my major thing lately, most other things seem of less importance now days, but to be honest it has been a solid device going on 6 or 7 weeks now. It just works.
Click to expand...
Click to collapse
I agree. I have no complaints, and the battery life is crazy compared to the N5. Four days compared to nightly charges.
It's a solid device right now, and appears to more than equal the N5.
I'm on factory for the time being. I may try rolling my own, but this is a different ecosystem than the Nexus world.

Anyone in india got that update??

Another update? UGH! I guess it is going to be like this from now on.... Repetitive updates...
Still on -35 and getting -35-5 announcements. Still haven't even updated to -35-5, -35-67 showed up, now -35-83?
Is it still rootable? Are there FULL FW's so I can upgrade or do I need to upgrade to -35 and let it update to -83? Do I need to be on -35-67 before the -35-83 is capable of being installed?

m4f1050 said:
Another update? UGH! I guess it is going to be like this from now on.... Repetitive updates...
Still on -35 and getting -35-5 announcements. Still haven't even updated to -35-5, -35-67 showed up, now -35-83?
Is it still rootable? Are there FULL FW's so I can upgrade or do I need to upgrade to -35 and let it update to -83? Do I need to be on -35-67 before the -35-83 is capable of being installed?
Click to expand...
Click to collapse
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.

I'm on NPN25-137-67 XT1686 Indian Varient
I didn't got any update?

Can someone grab the update zip? I'm on Verizon and it doesn't show for me....

acejavelin said:
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.
Click to expand...
Click to collapse
Don't get me wrong, updates are great, but not if you are rooted and you have to go through a process to root then reconfigure the phone since it's not an OTA, you have to reflash a STOCK rom to allow OTA's, then you have to root (if possible, not sure if -83 is yet...) and then setup the phone the way you want it..

mikeyinid said:
Can someone grab the update zip? I'm on Verizon and it doesn't show for me....
Click to expand...
Click to collapse
Same here,a update zip would be much appreciated. Thanks

acejavelin said:
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.
Click to expand...
Click to collapse
Huh... Why not wait and add the patch for BB? Odd... So the safest thing to do is to not even be using BlueTooth at all until it's patched? It's been 3 weeks right? 9-12 or was it 9-11 (what a coincidence)

m4f1050 said:
Huh... Why not wait and add the patch for BB? Odd... So the safest thing to do is to not even be using BlueTooth at all until it's patched? It's been 3 weeks right? 9-12 or was it 9-11 (what a coincidence)
Click to expand...
Click to collapse
Well... that's debatable... Although this vulnerability is real, the chances of being effected by it are so remote in most cases is so infinitesimally small that changing your usage habits probably isn't necessary.
Why the August one, probably because that is when they had is scheduled and it was nearly complete when the Sept update came out so they decided to just finish and release it anyway, why let the work go to waste. For Moto it is usually a couple months behind anyway.

acejavelin said:
Well... that's debatable... Although this vulnerability is real, the chances of being effected by it are so remote in most cases is so infinitesimally small that changing your usage habits probably isn't necessary.
Why the August one, probably because that is when they had is scheduled and it was nearly complete when the Sept update came out so they decided to just finish and release it anyway, why let the work go to waste. For Moto it is usually a couple months behind anyway.
Click to expand...
Click to collapse
My bad, I went out of sync with time for a min. It's AUGUST security the one on this -83 (not SEPTEMBER) so I am guessing there is another update coming!
Did you root your -67 (if you have -67?) My bootloader is already unlocked, do you know if Moto will eventually lock this (maybe Google forcing them to any time soon?)
Moto devs can unlock bootloaders and phone has ugly start image but other than that it all works as intended. (BTW, I am using SuperSU and BusyBox on my -35, not the Magisk root - I use Wifi Tether Router and doesn't work with Magisk)

m4f1050 said:
My bad, I went out of sync with time for a min. It's AUGUST security the one on this -83 (not SEPTEMBER) so I am guessing there is another update coming!
Did you root your -67 (if you have -67?) My bootloader is already unlocked, do you know if Moto will eventually lock this (maybe Google forcing them to any time soon?)
Moto devs can unlock bootloaders and phone has ugly start image but other than that it all works as intended. (BTW, I am using SuperSU and BusyBox on my -35, not the Magisk root - I use Wifi Tether Router and doesn't work with Magisk)
Click to expand...
Click to collapse
Another update coming? I suppose, but since we just got this one I don't expect it for 3-4 months and that puts it in the timeframe of Oreo so this might be our last update to Nougat.
As far as the bootloader thing goes, I don't see Moto stopping this or actively blocking rooting, nor do I see Google doing this either.
I don't unlock or root anymore, just don't see the benefits.

mikeyinid said:
Can someone grab the update zip? I'm on Verizon and it doesn't show for me....
Click to expand...
Click to collapse
+1. I'm on 43-5, a Verizon-exclusive update, and am not seeing an OTA. Chances are it's incompatible with my version and I'll have to reflash -35 and get the OTA. I'd suggest anyone else having this issue does as well. I'll report back as soon as I flash.

Oct. 2018 Google Pixel / Nexus Security Update

https://source.android.com/security/bulletin/pixel/2018-10-01
Announcements
There are no Pixel or Nexus security patches in the October 2018 Pixel / Nexus Security Bulletin.
Click to expand...
Click to collapse
:angel: :cyclops:

Seems like we're back to not being able to push the updates through

murso74 said:
Seems like we're back to not being able to push the updates through
Click to expand...
Click to collapse
I don't understand. I downloaded and adb sideloaded the October OTA minutes after it posted. I had no problem whatsoever.
My comment was about the "security update" having no security updates / patches.

Still September Patch Level?
Pkt_Lnt said:
I don't understand. I downloaded and adb sideloaded the October OTA minutes after it posted. I had no problem whatsoever.
My comment was about the "security update" having no security updates / patches.
Click to expand...
Click to collapse
After upgrading to the October image, does you system show though that the system security patch level is still September, 2018?

cmexec said:
After upgrading to the October image, does you system show though that the system security patch level is still September, 2018?
Click to expand...
Click to collapse
No, shows October 5 2018 which is crazy, because I got the update on October 1, and did not know the P2XL was a time machine to take me into the future! :cyclops:

Pkt_Lnt said:
https://source.android.com/security/bulletin/pixel/2018-10-01
:angel: :cyclops:
Click to expand...
Click to collapse
Update took ages for me. The download and the install was sooooo slow... . After the update (one full day) I have about 25-30% less battery with the same usage.
(This is not a real measure, just a feeling)
Charged faster over 90% (sometimes it says @95% : 18 mint to max. Now It was faster.
It was not on the change log list but I have less display flickering during the environmental light changes...
And Now the notification led alerts are sometimes not working with some apps. (example Gmail.)
Maybe I'm going to reset my phone.
And yes I'm on Oct 5. security update

still no update for me. Shouldnt we all have access to the update ?

Relayers said:
still no update for me. Shouldnt we all have access to the update ?
Click to expand...
Click to collapse
You do too have access.
https://developers.google.com/android/ota#instructions
You have a Pixel phone and you are an XDA member, nothing stopping you.
It was posted yesterday morning and I had my phone update within 15 minutes. :good:

Pkt_Lnt said:
You do too have access.
https://developers.google.com/android/ota#instructions
You have a Pixel phone and you are an XDA member, nothing stopping you.
Click to expand...
Click to collapse
useless comment, well done !

Relayers said:
useless comment, well done !
Click to expand...
Click to collapse
XDA Developers gives you the knowledge and tools to do it yourself instead of sitting around waiting for someone else to do it for you. Use that knowledge and tools to take control of your phone! :good:

Pkt_Lnt said:
XDA Developers gives you the knowledge and tools to do it yourself instead of sitting around waiting for someone else to do it for you. Use that knowledge and tools to take control of your phone! :good:
Click to expand...
Click to collapse
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).

Relayers said:
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).
Click to expand...
Click to collapse
Seems not.....you obviously dont understand how the push happens....short answer is no, not everyone has access to it at the same time. android 101.

Pkt_Lnt said:
No, shows October 5 2018 which is crazy, because I got the update on October 1, and did not know the P2XL was a time machine to take me into the future! :cyclops:
Click to expand...
Click to collapse
Same for me, also Oct. 5 security level

cmh714 said:
Seems not.....you obviously dont understand how the push happens....short answer is no, not everyone has access to it at the same time. android 101.
Click to expand...
Click to collapse
Yet he "knows more than you do"... and probably more than anyone else on xda

Relayers said:
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).
Click to expand...
Click to collapse
@Pkt_Lnt fully understands what he did, but you apparently missed his point. Then again, you claim to know more than he does. And yet you still have so much to learn.
Regards,
Someone who has forgotten more than what you've learned.

reporting back: finally got the OTA, I guess I should have remembered its always around the 5th of the month.

Relayers said:
reporting back: finally got the OTA, I guess I should have remembered its always around the 5th of the month.
Click to expand...
Click to collapse
Well good. Guess you can't blame the parents or (Trump) anymore! :laugh:

I still haven't gotten the update.

t2jbird said:
I still haven't gotten the update.
Click to expand...
Click to collapse
Updates are staged and not everyone will receive one the first day. Download the update from Google's servers and sideload it if you don't want to wait.

t2jbird said:
I still haven't gotten the update.
Click to expand...
Click to collapse
Are you enrolled in the Android Beta Program? Try un-enrolling. Then, check for updates again. The OTA should be pulled to your device this time round.

What is this feature??

Guys.
I just realized there is a new feature on my phone.
I never allowed it to be installed, phone never asked if I wanted it and I have all updates turned off. All updates!
Stock, no root, Jan 2020 firmware.
You can find in under settings/google and it will be the very first position.
What is that?
How do I remove it?
View attachment 5042325 View attachment 5042327

it's a part if google app update
https://www.google.com/covid19/exposurenotifications/

I have all updates turned off!
Both, the system and apps.
From the very first day I switched on the phone.
What the hell?

DonAndress said:
I have all updates turned off!
Both, the system and apps.
From the very first day I switched on the phone.
What the hell?
Click to expand...
Click to collapse
but u can't turn off google frameworks update and google play store. btw it's google

faizauthar12 said:
but u can't turn off google frameworks update and google play store. btw it's google
Click to expand...
Click to collapse
This is outrageous.
That's my phone now and I should be able to do whatever I want with it and block whatever I want.
They should have asked if I wanted any kind of f**king update.

You do not own the software on your phone. Please review the terms and conditions set my Google.

DonAndress said:
Guys.
I just realized there is a new feature on my phone.
I never allowed it to be installed, phone never asked if I wanted it and I have all updates turned off. All updates!
Stock, no root, Jan 2020 firmware.
You can find in under settings/google and it will be the very first position.
What is that?
How do I remove it?
Click to expand...
Click to collapse
It's something that was being developed months ago, it makes your device search for devices in the background periodically for potentially COVID-19 infected people.
If someone is infected, they have to report it on their phone and it flags other users around if you're near someone who had/has COVID-19 or not.
It uses Bluetooth

Yepi69 said:
It's something that was being developed months ago, it makes your device search for devices in the background periodically for potentially COVID-19 infected people.
If someone is infected, they have to report it on their phone and it flags other users around if you're near someone who had/has COVID-19 or not.
It uses Bluetooth
Click to expand...
Click to collapse
Yeah. Good thing I still have Nokia 3310

its a framework, it needs an app to work with it to be of any use . without the app from your local country etc it does nothing.

How can you be so sure? How do you know it doesn't work in the background anyway?

DonAndress said:
How can you be so sure? How do you know it doesn't work in the background anyway?
Click to expand...
Click to collapse
How can you be sure little green aliens are not running the world? Do you have Bluetooth on ? do you track what data you receive on Bluetooth? its a framework module...not a secret conspiracy to take over the world... ( again )

DonAndress said:
How can you be so sure? How do you know it doesn't work in the background anyway?
Click to expand...
Click to collapse
Its a framework. That means, apps sit on top on the frame ... like building a house, you need a base ( frame ) . This " Base" lets others build whatever house they want on top ... the actual "base" does nothing, how do I know... its a framework. if you are so paranoid, stop all you're google, amazon frameworks and see what happens, spoilers, your phone won't work. Next, stop all the frameworks in windows if you use that .. spoilers, it won't work ....then put everything into a box and leave it there

DonAndress said:
Yeah. Good thing I still have Nokia 3310
Click to expand...
Click to collapse
If you want to live life without being tracked, I suggest you move to Mars.

Yepi69 said:
If you want to live life without being tracked, I suggest you move to Mars.
Click to expand...
Click to collapse
I think "curiosity" is already there

Question Block 13 update?

I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?

I assume if your phone rooted, automatically updating will fail

It doesn't, and I lose root, that's what I thought last security update— which is why i'm concerned

christiebunny said:
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
Click to expand...
Click to collapse
Yes tap build 7 times for Developer Settings and disable automatic updatea

You could unlock the bootloader (which would require a device wipe) and then reinstall your current build of Android manually. That would be one of the only ways to officially disable automatic updates as well as update notifications.

I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
You may be able to delay it some buy factory resetting and some other things, but it's a big "maybe", and ultimately I don't think there's any way for you to avoid it.
biggiesmalls657 said:
Yes tap build 7 times for Developer Settings and disable automatic updatea
Click to expand...
Click to collapse
The OP you quoted says:
christiebunny said:
I've already got 'automatic updates' turned off, but that isn't stopping it.
Click to expand...
Click to collapse

roirraW edor ehT said:
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
Click to expand...
Click to collapse
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Maybe it was even the same person mentioning it 3 times, lol. Not really sure.
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or just a fluke situation.

Lughnasadh said:
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Didn't go back to check the posts.
Click to expand...
Click to collapse
I think I've seen more than one person report this too, but wasn't sure, and as I always say, I keep forgetting the old stuff. What was I talking about?
Lughnasadh said:
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or something else is going on.
Click to expand...
Click to collapse
I suspect (but pretty obvious) that they have ways of force-pushing updates through despite the automatic update setting (or it's broken in typical Google fashion), but I think it's the former.
Then I believe they made a command decision that the vulnerability is too bad and that they felt they must force it on everyone. Again, given Google's reputation, this could've easily been an accident as well - "who pushed the red button!?!?!?"
And then the further command decision to push over top of modded, or at least simply rooted, devices as much as possible. I wonder what happens in the case someone has truly modified their software more aggressively at the root level. It wouldn't surprise me if it would've still overridden in those cases.
While, of course, those would be questionable actions for them to take (if these are actually true in the first place), I either partially or mostly agree with them, but just on principle, I can't wholeheartedly agree with them. Somewhere in the 40%-99% range.
If true, hopefully this is a very rare occurrence and not going to be how it is from now on. I will wait patiently to observe how things go.

What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!

Annil said:
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Click to expand...
Click to collapse
V4A, at least in my case. I'm not updating until its compatible, or I find a better alternative.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
Android 13 cannot be modified is one reason...

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
Could you explain your theory on this?

christiebunny said:
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Click to expand...
Click to collapse
Compatibility seems remarkably intact, magisk works as intended, and there is no evidence of any change in what control you have.

96carboard said:
Could you explain your theory on this?
Click to expand...
Click to collapse
Modified SystemUI bootloops.

Tulsadiver said:
Modified SystemUI bootloops.
Click to expand...
Click to collapse
Ok? How are you modifying it?

96carboard said:
Ok? How are you modifying it?
Click to expand...
Click to collapse
Same way I always have.

Tulsadiver said:
Same way I always have.
Click to expand...
Click to collapse
That answer really doesn't help anyone.

96carboard said:
That answer really doesn't help anyone.
Click to expand...
Click to collapse
Any like these:
Stand alone Clock, Navbargone, Battery Icon Gone, etc. Mods
For stock rooted only. For most part, these cannot be flashed together. These mods use the SystemUI Patcher Module Template by @Jai_08 By @cool_modules on telegram. After Installing this module, your screen will relock after every reboot of...
forum.xda-developers.com