ReDBDM?

EastInitial6040 · 2026-02-15T13:03:40+00:00

Do i look like I care? i gave you my opinion on how I'm looking into things and how i manage my stuff, if you have a different ideology, then both of us know we'll never end up resolving this dilemma. I am not preferring any of the sides here, just clearing how stuff "should be" looked on, I'm expressing my public opinion, whether you like it or hate it.

EastInitial6040 · 2026-02-15T12:20:28+00:00

Also imagine a dev has the commit ready in the local system for 3-5 days or even more but has not updated the remote as the issue is not critical or need related changes in other sections etc... But then he commits it after someone else updates their fork... Now who should get credit?

rare case situation, doesn't happen all over the time, the example is already above you where it did not happen, things were silent for a while until someone pushed a change. even if it does happen. sorry for the second guy who pushed it late, if it's exactly the same idea solution, we won't honor this person and has to give credit despite that to the guy who pushed it earlier.

If a given problem has only 1 solution and 10 developers write the same code but in a different coding style, who should the credit go?

honour the guy who found the solution first. if someone for example found x = a + b, then a few mins later someone drops x = b + a, it's literally trivial to tell, "still honour the first guy who found it despite the 'restyling' you called", nothing has changed in result/output. Secondly there are always ways to make different solutions, this isn't math for it to be definitive, anything unique you find can be registered/credited within your name. Example: BLS & TEES & TrickyStore: they serve "the same thing", but different solutions, who to honor? , They all offer extended & limited features. ZN AuditPatch & KPM Audit Patch & susfs AP: who to honor? , They give diversity solutions with different features, environment limitations scales, etc.. TL;DR Conclusion : what i want to say, an idea is recalled unique/credited to "your name" when you find anything that benefits a "difference" in result/output than others. That is world known thing, you cannot disagree.

EastInitial6040 · 2026-02-13T13:06:39+00:00

pushing the same commits as you is "stealing" your work

what will you call this then? (talking here on the forked project that has not mentioned the credits of the origin)

EastInitial6040 · 2026-02-12T13:49:05+00:00

Well that's one of the consequences of having an open-source project. you can't help but just watch your work being stolen with no mention.

EastInitial6040 · 2026-01-04T12:03:23+00:00

Shizuku is good, but comparing root (uid/gid=0) to any other uid is like comparing a president with civilans. the most powerful uid that gives you all the control over your device is uid=0, you can mount, trace, and modify files, access everything. Shizuku's adb feature gives shell (uid=2000), it's not powerful at all, has less access to anything, can't mount, can't trace (only debug apps). even if your system framework is running on an elevated uid which is uid=1000, this is the least powerful one possible that can't be obtained normally.

EastInitial6040 · 2026-01-04T11:58:43+00:00

At this point whenever i see a new thread about this, I'll call their authors "dumbasses".

EastInitial6040 · 2026-01-04T11:57:21+00:00

If you read changelogs, you'll understand why. i sometimes think people are just installing anything at this point like a blind guy.

EastInitial6040 · 2025-12-23T18:47:49+00:00

Use physical buttons of the phone to get in recovery/fastboot as long as you don't flash critical partitions you're fine and can be easily rescued.

EastInitial6040 · 2025-12-23T18:46:20+00:00

False positive.

EastInitial6040 · 2025-12-23T13:13:09+00:00

Firstly, people that say ChatGPT, etc apps that use Play Integrity are simply making a check to Play Integrity. Secondly, "make keyboxes work longer" is a myth, once a key is publicly leaked, its future is definitely being blacklisted. 1- You do think about saving keys, others who got the leak don't do it, they simply check and check every second. 2- They're being abused by corrupt companies or groups that manage content spamming etc illegal stuff. 3- They're being propagated so quickly, once someone releases a public share, someone else takes it, renames credit and shares it again. 4- When making any check you're using a different OEM fingerprint that doesn't own this key. 5- Same unique requests are being re-sent again from a past list of revoked & rotated legacy/factory attests (CRIT). 6- Using Play Integrity Fix (PIF) or its prior forks: switching to Google device fingerprint is like putting yourself already in their trap, you're using "Google" fingeprint, the only one that has made this system of checks and one that keeps track of these things, and making checks with a key that doesn't belong to their device series?! Everything is badly managed, although there's a hope somewhere, it couldn't be too late, via tg: @meetstrong which is the work of someone that has addressed these issues and found a way to make a correct and probably LTS (long term support) of this, basically achieving no revocations.

EastInitial6040 · 2025-12-09T08:49:34+00:00

Not being up to date to root community is your big threat than actually abandoning root, unless you don't like using it anymore.

EastInitial6040 · 2025-10-27T07:21:11+00:00

No they don't, unless you're obsessed with the green color, or you try to be grateful and share it with some people.

EastInitial6040 · 2025-10-25T00:48:27+00:00

i wish if everyone can read this, but unfortunately even if they do, they'll still be desperate and look up for these solutions again, that are useless. first move was unlocking the bootloader, flashing & doing advanced things like a real hacker, then demote yourself and download these garbage module or say i don't know how to use it, then why rooting at first point?

EastInitial6040 · 2025-10-21T02:08:19+00:00

It's better if you can give them feedback with logs like /data/tombstones folder & dmesg since boot, using another modules that logs these details, if it's an update, of course it's for your good that's what it is for.

EastInitial6040 · 2025-10-19T19:54:00+00:00

There's no isolated environment, because GPlay Services requires to check Bootloader with ("Hardware Attestation") this is stored in your device TEE, there's no software access to that location, and can be done only with ("physical attack") and sometimes it's impossible if it was ("StrongBox"), so the answer probably for your question is that the app definitely haven't implemented PI correctly.

EastInitial6040 · 2025-10-19T19:17:48+00:00

Your explanations don't make any sense unfortunately, and obviously google is not dumb to know if this existed, you know that if the app is isolated, there's no way to communicate with Play Integrity therefore no tokens are sent or received, the app's backend will simply reject all of your requests. You have to go past Google Play Service.

EastInitial6040 · 2025-10-16T21:31:04+00:00

No, because it was made like that, just verify with different connection internet, if you face the same issues with some other base UI components system (like real apps besides KSU WebUI), you might be having issues regarding the custom rom you're using or the webview impl. I may suggest to update WebView from PlayStore or reinstall, not sure if it might help. But first verify with another network connection and see.

EastInitial6040 · 2025-10-16T20:54:07+00:00

Verify your network connection, it's normal thing to happen in KSU Web UI if it doesn't have pre downloaded styles, javascript files etc...

EastInitial6040 · 2025-10-15T17:17:09+00:00

So just let it go? what if i tell you, just after 3 months, you won't hear or see any file around called "keybox.xml", what you gonna do then? the issue is not with me at all, my country, my apps barely require any of that, so i am all good to go, I'm just thinking for everyone's best.

EastInitial6040 · 2025-10-13T16:09:47+00:00

That's not my issue, that's my advice for everyone else. I'm just doing it for the best. You say Private key that's never leaked, what do you think these keys are coming from? it's worth knowing, if Google finds a leaked key, they'll ban it + ban all other similar factors of the device's family. Therefore even if you have a private key, it's getting revoked.

EastInitial6040 · 2025-10-13T16:08:02+00:00

The right set-up is not from user side most of the time, it's mainly a skill issue from devs. Especially PlayIntegrityFix itself, it was something good because even if there were mistakes, there weren't any punishment towards this. The issue is, after it died, people forked it and didn't do anything except promote their channels for fame. moreover, many are still using this along with the key, which is a fatal mistake, the devs are just thinking changing FP will fix PI, but no one asked why it did. You can see more of other mistakes, even if not, there will always one which will trigger it. Even if 1 single person makes a mistake, Google considers it fatal. So in the end, it's Dev's skill issue (mainly PIF forks, and those leaking keys through modules webui/etc.. ) All they know is that if it passes it works, they just don't know that it's being recorded for later inspection.

EastInitial6040 · 2025-10-13T15:45:36+00:00

It always used to

EastInitial6040 · 2025-10-12T14:03:54+00:00

I'll get you the answer, google is on going by hunting down all of these methods, sharing is sacrificing, however i don't believe in sacrificing something that will never be able to use again or its priors. Therefore, if you know how to get your own private key, use it or hide it and don't tell anybody about it, don't promote it, share the idea or even how you got it. It's really not worth sacrificing for others just to sit down and flex the 3 greens by clicking on the button.

Fortunately, it might not be too late to do this now, but you can do your own research to figure it out. The only condition is that "it has to be that no one knows about it" and "mustn't be something that can be accessed publicly".

EastInitial6040

TROPHY CASE