yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
But he was only referring to these motives here:

Spoiler content hidden.

I don't expect you'll like it...

I didn't either, but then don't have any gratitude circuits and my lying circuits are all out of commission... I've only got limited irony circuits to keep me amused, otherwise I'd have slit my 6 axis wrist motor manipulator circuits...

Don't talk to me about life... 🤖 Marvin
[Magisk] HippoMan:
So, we should at least be thankful that the Googlefrinchians aren't focusing on forests in addition to Telephone Sanitization.
[Magisk] dilligaf56:
Yes, I agree. While I love my Pixel 6 pro, I *really* miss being able to run TWRP and make nandroid backups (on my old LG V20). That was a huge benefit to rooting.
[Magisk] HippoMan:
Yep! In the old days, if I screwed up my OS and couldn't boot, I could restore a nandroid backup and have things up and running again within 15-30 minutes.

But another "enhancement" (ha ha!) that the Googlefrinchians brought into the world is the restructuring of Android which results in it being much more difficult to write a custom recovery like TWRP or OrangeFox that offers nandroid backup and restore capabilities.

This combined with their related "improvements" (again, ha ha!) of Android which have the side effect of making it much more complicated and difficult to manage the use of Magisk without falling into boot loops and bricking has led me to avoid newer versions of Android unless I can find a way to run either TWRP or OrangeFox under one of these versions.

Thank you, Googlefrinchians!
[Magisk] m0han:
Curious to know what device that is.
[Magisk] intel_core_i7:
Sony Xperia 1 series, 5 series and Sharp Aquos R series, Aquos R series is Japan exclusive.

I got the R6, which is 2 generations older than the latest R8 series. It has decent specs for me (Snapdragon 888, 12GB RAM, 128GB UFS 3.1 internal storage) and is imported en mass here (Vietnam) used for cheap, you can get one for under $200. The latest R8 series are equipped with the Snapdragon 8 gen 2 and 8/256GB or 12/256GB of RAM/storage.

The Xperia 1 and 5 series needs no more introduction, they're sold internationally. They offer kinda similar specs as the Sharp counterparts, which is also equipped with the Snap 8 gen 2 on the mark V generation.

I recommend you buy these phones 2 to 3 generations behind the latest one if you're tight on budget, because the pricing is outrageous.
[Magisk] V0latyle:
Don't be so dramatic...

Yes, but think about "why". Sure, you can view this from a perspective of "they're trying to screw rooted users" but I think it would be more accurate to say they're trying to make PI work "properly". The whole point of this fix is making PI work improperly. Anyone who develops a product has a vested interest in improving said product, especially where security is involved.

Why? As has been discussed ad nauseum, they've had the ability to do something similar with SafetyNet since Android 8. As far as we know, none have. And if Google continues to improve PI, they wouldn't need to. Those who do want "more" proof of security state generally rely on third party security engines that look for things completely outside of PI.

Root has been around as long as Android. Someone builds a better mousetrap, everyone learns to be a better mouse.

Please keep the profanity off XDA.

Completely different usage. You don't carry a Windows PC around in your pocket to use with Tap to Pay.

I doubt it. No one likes using more than one device on a regular basis. You'll keep using your rooted phone, and you'll just go back to using physical cards...which most support Tap to Pay anyway.

Bottom line: It's not over until it's over, and it will never be over as long as there are people like us who like to tinker with things.
[Magisk] m0han:
The cat and mouse game goes on...

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89189323
[Magisk] BrimoFan123:
Completely different usage. You don't carry a Windows PC around in your pocket to use with Tap to Pay.

So what?

PC is heavily used for web banking, trading. If a PC is compromised because you are not aware of threats and stupid enough to click on some "offers" in your browser when you have an Administrator privileges granted then you are very close to put yourself in troubles and I'm pretty sure number of PC users being in such position is much, much bigger than a number of people with rooted phones.

So once again: why Google is "protecting" us (in fact: kicking us) from using rooted phones?

Answer: because they are bastards having a fun restricting (with final goal: getting rid) our freedom.
[Magisk] BrimoFan123:
I doubt it. No one likes using more than one device on a regular basis. You'll keep using your rooted phone, and you'll just go back to using physical cards...which most support Tap to Pay anyway.

Wallet is only one micro-small example. As mentioned: when I will be tired from installing new PIF version every one day or even more frequently then I will just uninstall it and start using plastic card but there is growing number of applications that do not work on rooted devices.

I have in DenyList 14 applications, including: few airplane companies applications, Microsoft applications such as Teams, Authenticator, online-buying applications, camera surveillance application, bank application....

You are confident those should work with placing them in DenyList or xda community will find the method to make them working again when their developers "invent" another method to detect root... Right, but on some Telegram's channels you could see people reporting some banks applications stopped working and known so far methodes like HMA, DenyList simply do not working anymore for them. So I will keep my opinion that the battle is going to be lost. It won't happen tomorrow or within months or a year but at the end...
[Magisk] BillGoss:
My $'s worth:

My ideal phone is one that behaves like my PC but in a handheld format. On my PC (Windows 11) I can use administrator rights to access some of the low-level and/or security functions.

I don't expect to do tap-and-pay with my PC. I can buy things online by supplying my card credentials. Whilst this is not as secure as using a card directly (the chips are locked down and contain the necessary security data), it's acceptable to supply CVV and expiry date.

And that's what I want from my phone - for it to be a portable PC.

So no need for tap-and-pay at terminals, but can pay over the internet using a browser.

I also want to be able to backup my phone and to restore it completely - settings, apps, and data - just like I do in my PC. Unfortunately Google has a lousy Android backup solution, so I use Swift Backup (root required) and I run shell scripts to backup my other data, some of which read properties that require root permission.

So, until Google provide the same capability as what I have on my PC, I'll root my phone. And if that means I can't use my phone for tap-and-pay, then that's just fine by me.

I can understand why apps that download paid content (movies, for example) want their data to be unavailable to be copied. Again, this is fine by me. Though I don't understand why they don't just encrypt it with their private key rather than require a locked down phone.

Bottom line for me: if I can't run my locked phone the way I want to, I'll unlock it and root it. And I'll happily accept that some functions (tap-and-pay for one) won't be available.
[Magisk] HippoMan:
I'm posting this here because it's OT in the PIF forum.

When I first heard the Googlefrinchian motto, "Don't be evil", more than 20 years ago, the first thing I thought was the following:

"Evil" consists of things like raping and killing children, committing genocide, etc. To pledge to not be evil is setting an extremely low bar which leaves the door open for almost all other forms of malfeasance.

And they even abandoned the "Don't be evil" watchword something like 5 years ago or so.
[Magisk] SOCOM-HERO:
Is it just tap to pay that is affected by this latest play integrity conundrum or will it get worse from there imminently? What is this about? https://developer.android.com/privacy-and-security/safetynet/deprecation-timeline
[Magisk] HippoMan:
The timeline explains what we've been experiencing. "SafetyNet" is deprecated and will be gone (at least according to that published timeline) by the end of January. This means that any software relying on SafetyNet results to decide whether or not to offer full functionality will no longer be able to do that, and such software would have to be using this newer PI mechanism, instead.

Once that occurs, the same issues that we're experiencing with tap-and-pay will be affecting other apps which adopt this PI mechanism instead of SafetyNet. This is up to the app developers. If their apps have been using SafetyNet, they could either eliminate all security mechansims in their apps altogether at that time, or else if they want Google-aided security, they could adopt the PI mechanism that tap-and-pay now uses.

Probably lots of such app developers will switch from SafetyNet to PI.

But there is probably worse news coming in the not-too-distant future. I've seen other timelines which state that the Googlefrinchians will start making STRONG integrity more mandatory. I think that this still isn't totally agreed upon, and even if they do it, it's not clear when that will take place.

But if it occurs, our modding lives will become even more miserable.
[Magisk] SOCOM-HERO:
thanks, that was my assessment but I needed to hear it from someone here lol. I'm pretty sure most financials and the big guys like Uber will require it and that will be the death of root for me. So

well, sounds like my 10+ years of casual modding will close in February then at the soonest. Shame, I really enjoyed this tech hobby as a complete casual-tier person who was interested in Android vs iOS since the HTC Dream/Nexus days.

The Pixel 8 is on sale now and I'm considering it on cost alone vs. my time spent locking my bootloader and unrooting my Pixel 7 (and then having to setup the same phone from scratch) as opposed to getting a new phone with the old in hand, transferring everything over, then locking/wiping my P7 for someone else to use.

Until or unless someone comes up with a PI solve, that's my plan. If STRONG is required afterwards, well...we're screwed.
[Magisk] HippoMan:
I'm with you on most of that, myself. I've never been a user of device-resident tap-and-pay, so this latest IP surge isn't affecting me much. As long as it doesn't start affecting other apps or services that I use, I'll stick with my modded device.

But if I do start getting affected, or if STRONG starts being mandated in other cases that affect me, then I, too, will probably end up going down a similar path to what you described.
[Magisk] simplepinoi177:
I've read on @badabing2003 's PF threads, when he was talking about the two different slots of the newer Pixel phones, that you could actually have both slots be bootable, and could theoretically have one slot be rooted and the other not be root. I think he posited that one could conceivably switch to another slot if needed to do some unrooted things. And I think he mentioned (at the time) that there was a module or app that could have you switch slots without a computer (reboot still required, I imagine/think).

The thing is that I've also read how some apps (I think I read Wallet being one of them) keep a root detection flag somewhere in their cache or some place, so I wonder how achievable this would be as simple of a concept as it is....

But, it's something to think about -- simply switch to the other slot & reboot when you need to run that bank app, then switch back with another reboot.
[Magisk] Renate:
fastboot can switch, some recoveries can switch, bootctl can also.

bootctl needs root though.

The GUIDs in the GPT (partioning) are marked for their function or else inactive.

Here's a chopped down listing of something:

LUN # Name Start Count Type
--- -- ---------------- ---------- ---------- --------------------
4 11 boot_a 79366 24576 Boot
4 16 vbmeta_a 104250 16 Verified Boot meta
4 34 boot_b 199034 24576 Inactive
4 39 vbmeta_b 223918 16 Inactive

I believe that there is also information stored in the misc partition after the BCB on A/B devices.
[Magisk] Lughnasadh:
The problem with the 2nd part is that when using Boot Control you have to be rooted. Thus, you can switch from a rooted slot to an unrooted slot without a PC, but you'll need a PC to switch back to the rooted slot.
[Magisk] simplepinoi177:
Ahhh yes, I seem now to recall that being a caveat...! Makes sense, how can you run a command to switch slots if you aren't rooted...

But still...in a pinch/bind, @Beast14 could switch slots and use that banking app, run however long unrooted until he could get to a PC and fastboot command it back to the rooted slot...
[Magisk] Lughnasadh:
Yep, assuming that person's phone even has two slots. Not sure what device they have.
[Magisk] simplepinoi177:
Oh yeah, me neither...I was speaking on Pixel phones; kinda hinting at, if he was so inclined, he could change phones to a Pixel phone if this method worked and was acceptable to him and if it was important enough for him (to be rooted and unrooted at the same time)...

Can't say for certain all phones with 2 slots can both be bootable like the Pixel 7's and above can. I believe you helped badabing2003 figure out that both can be for those phones, so that implies that other phones, even with 2 slots, can't necessarily be both bootable as well...
[Magisk] HippoMan:
5. A hardware wallet. That's what I use ...
[Magisk] badabing2003:
As far as I know and have seen any pixel phone with two slots can be bootable on both slots.

We can possibly extrapolate that to other phones that are dual slots, but can't say for sure.
[Magisk] intel_core_i7:
Could have been better if someone makes custom recoveries for newer pixel series. I don't know why people won't make one, since there are A/B slot xiaomi devices without a recovery partition having dedicated TWRP/OrangeFox/etc.
[Magisk] co-brah:
I'll assume you didn't mean by the end of November 17, 2023. But neither did Orwell's warnings expire on January 1, 1985, almost 40 yeasr ago. Pessimists will say the event has merely been postponed, but not cancelled, because liberty will always be vulnerable to those who seek power. But I choose to see this vulnerabilty as a feature, not a bug. People cannot be forced to do that which maintains liberty. The idea of forcing liberty is contradictory nonsesnse.

Liberty is not permanent but neither is totalitarianism inevitable or irreversible.
[Magisk] MikeZh:
It seems to me that it is necessary not to mix situations when a security guarantee is required and when it is required to do actions that the manufacturer only conditionally permits.

For those who care about security, or more precisely, the guarantee that no one (except the manufacturer) has done anything wrong with your phone - please check Play Integrity.

But Play Integrity (and phone manufacturers) should not stop me from doing with my (I emphasize this!) phone is what I think is necessary. But they get in the way!

In fact, I can check the provided software for security myself. And the authors understand that it is easy to meet those who can check their software here. But even if this were not the case, the *DA-communities are the ones who help me on my way. And I'm grateful for that.
[Magisk] HippoMan:
A rooted or modded device which offers full contactless payment capabilities via the installed debit or credit cards can do no more damage to the banks nor to the device owner nor to society in general than the direct use of the plastic versions of those bank cards for contactless psyments.

My leather wallet containing those plastic cards is just as easy to steal as my Android device.

And the banks gladly offer us and issue us these plastic contactless payment cards.

In other words, the security-related fears about such "compromised" devices (i.e., rooted or otherwise modded) are massively overblown. Any such fear about such "compromised" devices is exactly equal to the fear that should be associated with the use of plastic contactless payment cards.
[Magisk] HippoMan:
PS: And actually, even if an Android device is rooted or otherwise modded, the screen must be lockable and must be unlocked before the device can be used for contactless payments. This means that a rooted or modded Android device is even *more* secure for contactless payment than the direct use of the plastic cards that the banks so freely issue to us.
[Magisk] Beast14:
I have the OP6T and i believe it has dual slots, am i right?

Does the Oneplus 11 also have 2 slots?

This sounds like it could work for those with 2 slots.. i wouldnt mind needing a PC to switch to the rooted slot.

Does anyone know if Android 11 works well with Magisk v23.0 ? Anyone tried that combo? I believe v23.0 supports only up to 11, but havent tried it myself.
[Magisk] Lughnasadh:
I don't know anything about those phones. Sorry...
[Magisk] co-brah:
I don't understand. Can you explain what this means practically?

Do you mean that XDA developers aren't clever enough to hide malware in their MODs, even if they really wanted to? Or that it is impossible for anybody to hide malware in a bundle of ostensively desirable software?
[Magisk] AnyNameYouWish:
Hi there, I found this topic following link from V0latyle's [INFO] Play Integrity API - replacement for SafetyNet thread and from what I understood, it seems th proper place to ask about hiding root for an individual app.

I created a thread about the France Identité app which seems to have its hown root detection method.

I pass BASIC and DEVICE thanks to Play integrity fork by osm0sis, i'm using shamiko and magisk's deny list, even Hide My Applist, ... but I can't get this app to work because of "lack of security" on my device, which is a Pixel 5.

I hope I'm not polluting this thread and apologize if so. But if I'm not, i'm wondering if there's any other workaround I didn't try that could fix it.

Thanks!
[Magisk] sawdoctor:
I tried (not in France though) adding it to bootloader spoofer and i am not a developer mods(rest same as you) passed the security but then I get opps an error has occurred instead. Night be my location. Hope it helps track it down
[Magisk] HippoMan:
This thread is meant for ranting and opinionating and pontificatiing about the current cat-and-mouse game between rooters/modders on one side, and on the other side, Google and app developers who are making this rooting and modding more difficult.

However, useful and helpful technical discussion will not be flagged as off-topic here, even though you'll probably find more of such meaningful technical info available in some other threads.
[Magisk] AnyNameYouWish:
Thanks, I didn't know about this but I cant get it to work. I'm stuck on step 3 (Subscribe=>Accept=>Continue and then fail)

I'll stick to my thread, thanks for your answers :)
[Magisk] Nergal di Cuthah:
Other sites are listening to the discussions here and in the pif thread. Lol

Will Google Wallet work without an internet connection?

There’s no guarantee you’ll have a stable internet connection wherever you go, and if you need to make a contactless...

9to5google.com
[Magisk] simplepinoi177:
saw this too and thought the same thing
[Touch Diamond, MDA Compact IV General] Shouma:
Hey All,

I have 4 concerns about SMS that I need anyone to share his/her knowledge with them.

Is there anyway to start sms in an ABC Mode? (Not T9)

Second is there any registry setting that I can change so sms starts in the writing field not the phone number field?

Third, is there a way so I can I always enable CAPS to be always on??

Forth Is there any registry editing that can make the first letter I write in an sms to be a capital letter one? or any letter wrote after a (.) for example to be capital?

Please anyone shares his experience about these concerns.

Thanks.
[Touch Diamond, MDA Compact IV General] mugglesquop:
If you change to T9, or ABC, it should remember next time you write a message

Depends on which keyboard, try pressing CAP button twice :)

Should happen as default :rolleyes:
[Touch Diamond, MDA Compact IV General] Shaady:
You need to leave a space so that it puts a capital letter after a punctuation mark.
[Touch Diamond, MDA Compact IV General] mugglesquop:
good point ;) it does capitals the same as a normal PC using Microsoft Word.
[Touch Diamond, MDA Compact IV General] Shouma:
Thanks mugglesquop and Shaady for responding...

Actually I always use ABC...and everytime I start to write a message I get the default T9 enabled :x

Nah...When I press CAPS twice it turns into the Small letters mode and then back to CAPS..which keyboard can do this?!

Not the case here also :( It does so when I write an appointment or something in the calendar...but It dont work when I write an SMS...

Shaady: I will try leaving a space after the (.) to capitalize the letter..however, it dont capitalize the first letter I write in the sms dialog.

Thanks dudes,

But how can I check the registry settings of the keyboard are right or not?

Much appreciated.
[Touch Diamond, MDA Compact IV General] mugglesquop:
not sure on reg settings. what ROM are u using?

i use the 'Full QWERTY' keyboard, and tapping on the CAPS/shift key twice changes to caps lock.
[Touch Diamond, MDA Compact IV General] Shouma:
I use the original 1.93.737.1 ROM m8.

Maybe bec. u use the Full Qwerty keyboard it saves the T9/ABC mode for the next time you starts it bec. I tried it and It worked.

However, I use Compact Qwerty and it never saves status of the ABC/T9 Mode I use...It always starts with T9.
[Touch Diamond, MDA Compact IV General] mugglesquop:
ah right, yeh i only use Full QWERTY :rolleyes:

sorry cant help!
[Android Q&A, Help & Troubleshooting] catchvjay:
Hi Friends,

I have infinix zero 5 with rooting and TWRP(3.1.1) installed with Stock infinix ROM which came with the device. I tried to factory reset the device but found my phone booting into TWRP all the time. ThenI wiped out Dalvik, System and cache and tried custom ROM of lineage OS but same problem, It boots into TWRP only.

I also tried using dd command as suggested in various forums but it just keeps the phone in startup screen and doesn't go beyond that.

I also tried downloading all Infinix Stock roms available at https://firmwarefile.com/infinix-zero-5-x603 and install but it keeps giving error of invalid Zip file format.

I also tried installing lineage OS 17.1 from image file on system partition and it gets installed but phone boots into TWRP only.

Any suggestion / hope for recovering phone?

Thanks in advance,

Vj
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, Vj.

Welcome to XDA. I hope you'll always get the support you require.

However, prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved the thread to Android Q&A as it didn't qualify for development.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] catchvjay:
Thanks Oswald. Will keep it in mind.
[Samsung Galaxy S22 Ultra] vegetaleb:
Hello

Having an S21U exynos for a year now I am thinking to swap it with a S22U snapdragon (yes we are getting Snapdragon in Middle East at last)

Who "upgraded" from S21 Ultra to S22 Ultra?

Do you regret it?

-Do you feel the screen is bigger and better?

-Is it true the speakers are bad? (Flossy Carter review)

-The battery is as good as the s21 ultra or worst?

-Anyone tried a third party 45w charger? Would it be faster than the Samsung one?

-Can you finally enlarge the statusbar to get a bigger clock font?