As the title says. Why are many developers switching to MagiskSU over SuperSU?
crazynapkinman said:
As the title says. Why are many developers switching to MagiskSU over SuperSU?
Click to expand...
Click to collapse
Detection. Or rather cloaking. Apps that detect SuperSU don't always detect Magisk. There is more to it, but that gets to the heart of things. (I was trying to figure out a way to say that without making a pun on "root of the matter" or "kernel.)
There is more to Magisk than that, but it defeats SafetyNet on many devices. Not so much on Samsung. Which is why what @tdhite is doing is so important.
koop1955 said:
Detection. Or rather cloaking. Apps that detect SuperSU don't always detect Magisk. There is more to it, but that gets to the heart of things. (I was trying to figure out a way to say that without making a pun on "root of the matter" or "kernel.)
There is more to Magisk than that, but it defeats SafetyNet on many devices. Not so much on Samsung. Which is why what @tdhite is doing is so important.
Click to expand...
Click to collapse
And what is it that he is doing aside from using Magisk in his kernel?
elesbb said:
And what is it that he is doing aside from using Magisk in his kernel?
Click to expand...
Click to collapse
Integrating Magisk into the kernel alone should allow Android Pay to work as well as apps such as Pokemon Go.
@elesbb have you looked at the Magisk thread itself? See https://forum.xda-developers.com/apps/magisk
Modules, guides, etc.
koop1955 said:
Integrating Magisk into the kernel alone should allow Android Pay to work as well as apps such as Pokemon Go.
@elesbb have you looked at the Magisk thread itself? See https://forum.xda-developers.com/apps/magisk
Modules, guides, etc.
Click to expand...
Click to collapse
I have briefly looked at it. I was under the impression it was simply flash in recovery and profit. Didn't realize it needed to be incorporated into the kernel. If it actually works to allow SafetyNet to pass, then sweet.
elesbb said:
I have briefly looked at it. I was under the impression it was simply flash in recovery and profit. Didn't realize it needed to be incorporated into the kernel. If it actually works to allow SafetyNet to pass, then sweet.
Click to expand...
Click to collapse
There is a whole discussion about the challenges of using Magisk on Samsung phones, which is what we are attempting to solve.
Let me offer this scenario: Nougat is coming. Maybe a month off before we have the new TAR. Once we get that, flash via Odin to return to stock, then flash a Magisk-enabled kernel. Profit!
At least that is the vision.
koop1955 said:
There is a whole discussion about the challenges of using Magisk on Samsung phones, which is what we are attempting to solve.
Let me offer this scenario: Nougat is coming. Maybe a month off before we have the new TAR. Once we get that, flash via Odin to return to stock, then flash a Magisk-enabled kernel. Profit!
At least that is the vision.
Click to expand...
Click to collapse
Don't mean to rain on your vision, but Nougat I feel will be more difficult in terms of rooting and such. Samsung is pretty good at preventing things. Root might be easy per say, but having all the safety checks come out clean, that will be a huge feat. I did find a guide where they say you can get SafetyNet comes back true with Magisk and a Samsung S6 (Euro version). I have this idea where Google (OEM) creates a sandbox to execute secure sensitive stuff at. That way we can still has root and security is still in tact. I need to converse with someone more intelligent on the matter to better refine my idea lol.
elesbb said:
Don't mean to rain on your vision, but Nougat I feel will be more difficult in terms of rooting and such. Samsung is pretty good at preventing things. Root might be easy per say, but having all the safety checks come out clean, that will be a huge feat. I did find a guide where they say you can get SafetyNet comes back true with Magisk and a Samsung S6 (Euro version). I have this idea where Google (OEM) creates a sandbox to execute secure sensitive stuff at. That way we can still has root and security is still in tact. I need to converse with someone more intelligent on the matter to better refine my idea lol.
Click to expand...
Click to collapse
Talk to thdite and amieldl143. Those would be the likely ones.
More intelligent than me, for sure!
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
For anyone interested in the challenges of rooting Nougat, this is a pretty good article: https://betanews.com/2016/07/20/android-7-0-nougat-root/
I think for me, MagiskSU being open source is the biggest win. SuperSU being closed source, and being now owned by some tacky Chinese entity, does not give me the warmest or the fuzziest of feelings.
The SafetyNet stuff is a game of cat and mouse - each time Magisk figures a way to pass, Google and OEMs come out with a different way to screw us over. I think the same thing is with SuperSU and suhide. Since I don't use AndroidPay/SamsungPay/PokemonGo/SnapChat/whatever, then it is not something I care much about that.
koop1955 said:
Talk to thdite and amieldl143. Those would be the likely ones.
More intelligent than me, for sure!
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
For anyone interested in the challenges of rooting Nougat, this is a pretty good article: https://betanews.com/2016/07/20/android-7-0-nougat-root/
Click to expand...
Click to collapse
I was speaking more so about talking to Google themselves lol.
elesbb said:
I was speaking more so about talking to Google themselves lol.
Click to expand...
Click to collapse
Good luck with that. Google is actively engaged in making it harder to root the phones and is protecting the interests of their OEM partners, in this case Samsung.
https://android-developers.googleblog.com/2016/07/strictly-enforced-verified-boot-with.html
elesbb said:
Don't mean to rain on your vision, but Nougat I feel will be more difficult in terms of rooting and such. Samsung is pretty good at preventing things. Root might be easy per say, but having all the safety checks come out clean, that will be a huge feat. I did find a guide where they say you can get SafetyNet comes back true with Magisk and a Samsung S6 (Euro version). I have this idea where Google (OEM) creates a sandbox to execute secure sensitive stuff at. That way we can still has root and security is still in tact. I need to converse with someone more intelligent on the matter to better refine my idea lol.
Click to expand...
Click to collapse
On the 'sandbox' -- Samsung really is a pioneer in using trusted execution environment (TEE) zoning. Stock ROMs already execute (using TrustZone) trustlets in the secure zone, in fact a trustlet in the secure zone is in control of the verification and allowance of loading kernel modules (thus the need to alter TIMA operations in custom kernels making modules available). ARM directly supports dual worlds. The kernel, however, is the key point for setting up the communications back-n-forth so generally provides for the bypassses and hiding. I think that's your point (?). Google isn't really necessary in this part of the world -- Samsung is really a leader in this area.
tdhite said:
On the 'sandbox' -- Samsung really is a pioneer in using trusted execution environment (TEE) zoning. Stock ROMs already execute (using TrustZone) trustlets in the secure zone, in fact a trustlet in the secure zone is in control of the verification and allowance of loading kernel modules (thus the need to alter TIMA operations in custom kernels making modules available). ARM directly supports dual worlds. The kernel, however, is the key point for setting up the communications back-n-forth so generally provides for the bypassses and hiding. I think that's your point (?). Google isn't really necessary in this part of the world -- Samsung is really a leader in this area.
Click to expand...
Click to collapse
Thanks for posting this, you always inspire me to do more research, to learn something new.
I found this article provides an explanation of how Samsung Pay is walled off and how Knox works: http://developer.samsung.com/tech-insights/pay/device-side-security
Interesting stuff.
Related
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.
I know this isn't available, is there a thread dedicated to working on it? Anyway the community can help?
Idk why nobody cares about xposed anymore. Last year people were so eager to get xposed on nougat/Oreo. So sad to see it forgotten
Came looking for pie xposed. Is there anything else that runs xposed modules? What are people doing?
Is Xposed gonna be out for Pie?
This thread, these posts... These people... So annoying.
It will come out when it's ready. Or build it yourself
McFlypants said:
This thread, these posts... These people... So annoying.
It will come out when it's ready. Or build it yourself
Click to expand...
Click to collapse
lol :silly:
You are wasting your time and energy trying to stop people asking for progress then ETA since the people who do that kind of thing is their only capability
I'm just gonna add my request too:........
PIE XPOSED PLZZZ
150208 said:
lol :silly:
You are wasting your time and energy trying to stop people asking for progress then ETA since the people who do that kind of thing is their only capability
I'm just gonna add my request too:........
PIE XPOSED PLZZZ
Click to expand...
Click to collapse
No offense..I just wonder if the last sentence is a bit confusing. People is capability?
Sent from my Nexus 6P using Tapatalk
McFlypants said:
This thread, these posts... These people... So annoying.
It will come out when it's ready. Or build it yourself
Click to expand...
Click to collapse
ZYMivan said:
No offense..I just wonder if the last sentence is a bit confusing. People is capability?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
McFlypants said that people should build xposed by themself rather than doing a SPAM of what, when, and how of xposed progress nowdays
I simply tell him to ignore it since it's their only skill, which mean people who do a SPAM on xposed progress will be more likely far from building xposed by self.
I'm not a native english speaker, but i believe i don't confuse anything in my words.. CMIIW
thandiBear said:
Idk why nobody cares about xposed anymore. Last year people were so eager to get xposed on nougat/Oreo. So sad to see it forgotten
Click to expand...
Click to collapse
yes, you are right. I was also thinking about the huge "mod-scene" .. as shown in XDAlabs-APP... Will all these people:
- be stuck on OREO?
- abandon their beloved mods and move on to PIE - the land of no Xposed-Mods ?
I must admit that I am still on OREO with my OnePlus6 BECAUSE I would have to bury some of my mods.........yes, you can laugh at me...but I am that strange
Any changes so far? Or still nothing? :crying:
Xposed Pie
The reason many people want to know when Xposed for Pie is available is because lots of other decisions are contingent on this. Pie is out, the Pixel 3 XL and 6T are out. Should I buy these, root, update, etc.? I am still using Oreo on my Pixel 2XL. I would rather wait until Xposed for Pie is ready, and then execute all those actions. UNLESS... Rovo dies and we are all doomed... I wish this wasn't so dependent on one person. This is kind of ridiculous. But once you get addicted to the options...
dresty said:
The reason many people want to know when Xposed for Pie is available is because lots of other decisions are contingent on this. Pie is out, the Pixel 3 XL and 6T are out. Should I buy these, root, update, etc.? I am still using Oreo on my Pixel 2XL. I would rather wait until Xposed for Pie is ready, and then execute all those actions. UNLESS... Rovo dies and we are all doomed... I wish this wasn't so dependent on one person. This is kind of ridiculous. But once you get addicted to the options...
Click to expand...
Click to collapse
Even if this is for XPosed, i would recommend you Magisk
Magisk is already available and works perfectly. Root is working, everything's fine.
I'm using xposed edge pro, this is enough reason not to update to pie. Anyone using this mod knows what I mean, nothing in pie or any normal apk comes close to what this mod alone offers.
Infact edge pro has sort of ruined my excitement for your average app because I'm finding that it can do just about everything especially when you dig deep into it.
dresty said:
The reason many people want to know when Xposed for Pie is available is because lots of other decisions are contingent on this. Pie is out, the Pixel 3 XL and 6T are out. Should I buy these, root, update, etc.? I am still using Oreo on my Pixel 2XL. I would rather wait until Xposed for Pie is ready, and then execute all those actions. UNLESS... Rovo dies and we are all doomed... I wish this wasn't so dependent on one person. This is kind of ridiculous. But once you get addicted to the options...
Click to expand...
Click to collapse
Use Magisk.
mikedavo said:
I'm using xposed edge pro, this is enough reason not to update to pie. Anyone using this mod knows what I mean, nothing in pie or any normal apk comes close to what this mod alone offers.
Infact edge pro has sort of ruined my excitement for your average app because I'm finding that it can do just about everything especially when you dig deep into it.
Click to expand...
Click to collapse
Try LMT.
RealFantaCoke said:
Even if this is for XPosed, i would recommend you Magisk
Magisk is already available and works perfectly. Root is working, everything's fine.
Click to expand...
Click to collapse
I'm confused. Can i use Magisk for Xposed modules? I already have used Magisk for rooting the device. The issue is you need Xposed framework to install the modules. E.g. Is it possible to install GravityBox with Magisk? Thanks for the clarification.
dresty said:
I'm confused. Can i use Magisk for Xposed modules? I already have used Magisk for rooting the device. The issue is you need Xposed framework to install the modules. E.g. Is it possible to install GravityBox with Magisk? Thanks for the clarification.
Click to expand...
Click to collapse
I've no idea why people are comparing Magisk and Xposed. Two tools for completely different purposes. No, you cannot get the functionality of GravityBox with Magisk.
dresty said:
The reason many people want to know when Xposed for Pie is available is because lots of other decisions are contingent on this. Pie is out, the Pixel 3 XL and 6T are out. Should I buy these, root, update, etc.? I am still using Oreo on my Pixel 2XL. I would rather wait until Xposed for Pie is ready, and then execute all those actions. UNLESS... Rovo dies and we are all doomed... I wish this wasn't so dependent on one person. This is kind of ridiculous. But once you get addicted to the options...
Click to expand...
Click to collapse
I agree. I don't get why it's so frowned upon to discuss the development, even though non of us have anything since Rovo has gone radiosilent. If nothing else, it shows that there's a demand, no? I personally was a little while was staying back on Oreo with my OP6 because of my Xposed mods, but seeing as the development seems so dead, it seems easier to just get un-used to the options that Xposed brings.
I mean the Xposed code is on GitHub. Seems like a great opportunity to learn java and Android internals for whomever is motivated enough
_genevera said:
I mean the Xposed code is on GitHub. Seems like a great opportunity to learn java and Android internals for whomever is motivated enough
Click to expand...
Click to collapse
Not all of it. Essential bits of codes are still not made public by rovo89.
I think most of the people out there have started using magisk modules a whole lot these days and so the popularity of xposed is not as much as it used to be.... Still hoping to get xposed as soon a s possible. I'm rocking aosp extended on asus Zenfone max pro m1. Eagerly waiting for xposed.
Magisk is better than Xposed!
dresty said:
I'm confused. Can i use Magisk for Xposed modules? I already have used Magisk for rooting the device. The issue is you need Xposed framework to install the modules. E.g. Is it possible to install GravityBox with Magisk? Thanks for the clarification.
Click to expand...
Click to collapse
No, sorry. I meant that Magisk is so much better than Xposed so you don't need Xposed anymore.
Really sorry for this mistake.
Title says it all, have seen lots of rumours that it might be enabled but nothing concrete.
It's already here with a magisk module,
I don't think anyone here knows anything beyond what's publicly known, which is that there have definitely been code tweaks that are geared towards face unlock, but who knows when or even if for sure.
As said, yes, also if you root you can use a Magisk Module to get face unlock.
Well, the code was added, face match is added on Google assistant but not working yet, everything seems to point out that will be implemented, but until front end setting's are added, we'll have to rely on a magisk module. My bet is that will be implemented in future builds, whether is android 13 or afterwards I guess we'll see
My guess is no, they are getting everything set up and tested for the Pixel 7, we won't see it.
TonikJDK said:
My guess is no, they are getting everything set up and tested for the Pixel 7, we won't see it.
Click to expand...
Click to collapse
That is my guess too.
acidspider said:
It's already here with a magisk module,
Click to expand...
Click to collapse
I can't get the magisk. I'm on AT&t. They will not let me unlock the phone.
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
Hi, I'm still on OS11, and I would like to know if there are any commands via adb to block future updates. I'd appreciate any help!
Adelino80 said:
Hi, I'm still on OS11, and I would like to know if there are any commands via adb to block future updates. I'd appreciate any help!
Click to expand...
Click to collapse
Turn off auto updates in developer settings
https://www.hardreset.info/devices/oneplus/oneplus-9-pro/developer-options/#:~:text=Developer%20Options%20OnePlus%209%20Pro%201%20Firstly%2C%20turn,option%20and%20find%20Developer%20options.%207%20Good%20job%21
can you use app inspector to search "update" in app list and post me the results
TheGhost1951 said:
https://www.hardreset.info/devices/oneplus/oneplus-9-pro/developer-options/#:~:text=Developer%20Options%20OnePlus%209%20Pro%201%20Firstly%2C%20turn,option%20and%20find%20Developer%20options.%207%20Good%20job%21
Click to expand...
Click to collapse
Thanks! Turned the option off!
do you like insecure system with 2Y old security patch? gg.
Hildanew said:
do you like insecure system with 2Y old security patch? gg.
Click to expand...
Click to collapse
Unfortunately, the Kennel is never updated by the manufacturers and therefore remains a security risk
ChrisFeiveel84 said:
Unfortunately, the Kennel is never updated by the manufacturers and therefore remains a security risk
Click to expand...
Click to collapse
Kernel is majority updated with ever major Android. btw, every Kernel is patched by regular Google updates like different supported builds Windows..
Good question, I am also still on A11 oxygen OS. It is smooth and stable. Why would I be crazy enough to update?
We also need instructions on how to prevent google play services annoying nag messages about old firmware updates. Anyone know how to stop google play from annoying us?
Mandy $ingh said:
can you use app inspector to search "update" in app list and post me the results
Click to expand...
Click to collapse
Update for what?
Hildanew said:
do you like insecure system with 2Y old security patch? gg.
Click to expand...
Click to collapse
Who you referring to?
immortalwon said:
Good question, I am also still on A11 oxygen OS. It is smooth and stable. Why would I be crazy enough to update?
We also need instructions on how to prevent google play services annoying nag messages about old firmware updates. Anyone know how to stop google play from annoying us?
Click to expand...
Click to collapse
Try turning off notifications....maybe?
on oos 13 use pm uninstall -k --user 0 com.oplus.ota using adb if you want to do the hard disable system update
TheGhost1951 said:
Who you referring to?
Click to expand...
Click to collapse
for someone who want stay on OOS11 now with "2y" old security patch.
Hildanew said:
for someone who want stay on OOS11 now with "2y" old security patch.
Click to expand...
Click to collapse
if you mean slowing down your phone, then yes, security patches are great!
An example: On windows 10, the original 1607 ltsb 2016 is probably the fastest and most smooth OS I ever used on win 10 series. Unfortunately if you install the "security patches", it becomes slow and high latency.
Same goes for android devices.
If you know what you are doing, then you don't need patches.
TheGhost1951 said:
Update for what?
Who you referring to?
Try turning off notifications....maybe?
Click to expand...
Click to collapse
I did, but I was wondering if there is a specific component u can disable from play services instead of turning off notification?
immortalwon said:
if you mean slowing down your phone, then yes, security patches are great!
An example: On windows 10, the original 1607 ltsb 2016 is probably the fastest and most smooth OS I ever used on win 10 series. Unfortunately if you install the "security patches", it becomes slow and high latency.
Same goes for android devices.
If you know what you are doing, then you don't need patches.
Click to expand...
Click to collapse
No man. If even, I'd rather be safe than fail. As with Meltdown and Spectre. Safety is safety and there is no other option for my good..
Hildanew said:
No man. If even, I'd rather be safe than fail. As with Meltdown and Spectre. Safety is safety and there is no other option for my good..
Click to expand...
Click to collapse
Propaganda, but you do you buddy. Sounding like a Google / security researcher shill. The average person doesn't need all these security patches. Unless you work in a high level government or military field, security is pointless. I don't need nanny updates from google to tell me how to use my device.
immortalwon said:
Propaganda, but you do you buddy. Sounding like a Google / security researcher shill. The average person doesn't need all these security patches. Unless you work in a high level government or military field, security is pointless. I don't need nanny updates from google to tell me how to use my device.
Click to expand...
Click to collapse
Have heard in the news about a rampant problem of androids being hacked.
No but sounds interesting. I would like to reiterate I am not fully against patching and updating a device / firmware to latest for security reasons. All I am saying is that a person should have the ability to block updates on an android or any other electronic device for that matter, not to be forced by Google or another megalithic corporation to move to the latest.
1) I fully agree that a user should have the right to not update
2) why a user would subject himself at a constant security risk is beyond me, but I strongly support his right to do whatever he wants
Freewill, freedom of choice be it good or bad. In that it is a matter of opinion, but it is still their choice! God gave us freewill, do we choose Him or choose the world? That is the single biggest choice one has to make!