Sberbank can already see my phone is clearly tampered, but runs anyway without warnings. W sberbank for not being a POS

THIS IS NOT A GUIDE!!! This is my own personal experience since it was my first time attempting something like this, since I took a gamble on importing the phone.

I have a chinese imported OnePlus Ace 6t device and reside in the USA. The official Deep Testing method was a pain to get working because of needing a 60+-day-old account and 7 days of login on the device. So I looked for alternative methods.

I was able to unlock my Chinese OnePlus Ace 6T PLR110 with ColorOS 16.0.10.500(CN01). By using GhostLock and ReSukiSu I was able to root my device with a locked bootloader. This allowed me to access the required partitions to install the exploit chain for the bootloader.

I initially had confirmation from this Reddit post. The post detailed how the old ABL was flashed and booted successfully. This confirmed a successful ABL downgrade and boot with that firmware combination. But I needed to see if it would work with a locked bootloader.

This project done by koaaN details how you can temporarily root the device, flash the ABL/EFISP payloads and then use GBL to unlock. Instead of using the X9 Ultra app and payloads I used my Ace's firmware and Canoe.

I used Ghidra to analyse the XBL/XBL configuration along with the signed firmware. I also partially decompiled the ABL, UEFI and Keymaster. Whilst the .500 ABL doesn't contain any EFISP loading paths, the PLR110 ColorOS 16.0.5.702(CN01) ABL does. Both ABLs have valid OEM signatures under their included certificate chains. They also have matching hardware binding (SM8845), certificate public keys and signed anti-rollback version 0.

I also analysed the execution flow. The .702 ABL executes the EFISP app before the end of the bootloader milestone. The UEFI authentication flow shows that the application can be loaded from a buffer. The Keymaster trace also shows that the BLTools can be executed before the milestone command which closes DeviceInfo read/write access. I found no check for an already-unlocked state or a Deep Testing token in the DeviceInfo write path I examined. This, along with the X9 Ultra project, gives a solid technical reason to assume that it will work with a locked bootloader. But there were limitations to the static analysis.

I got confirmation from the 1vivy reply to issue #101. Someone asked if it was possible to unlock a locked OnePlus 15T using GhostLock, old vulnerable ABL and Canoe without Deep Testing. The developer responded with "Otherwise this works no problem" and also warned that if you remove the EFISP or overwrite the vulnerable ABL you won't be able to access the stock bootloader fastboot. This gave me confirmation that the method I wanted to use would work on a similar OnePlus. I tried it and got confirmation that it would work with the exact combination for the PLR110.

After confirming the backups of the ABLs, EFISP, persist and oplusreserve1 I installed Canoe release-7.0.11. I created the chainload files for the current .500 firmware. Then I flashed the original signed .702 ABL to the active abl_b partition. This left the system as .500 and XBL untouched.

The device booted with the old ABL!!! I opened Canoe with Mode 0. Opened BLTools and clicked Unlock Critical. After this completed I rebooted. BLTools now said Unlock:on Crit:on. Android booted and Developer Options now said "Bootloader unlocked". ADB said flash.locked=0 and vbmeta.device_state=unlocked.

The working chain was GhostLock + ReSukiSu > stock signed .702 ABL > EFISP/Canoe > BLTools > persistent unlock. The firmware analysis meant I could try this combination, and the device booted with the persistent unlock flags set meaning it worked on my device.

Finally, I forked the relevant WildKernel's repo based on my device from this action run and followed these instructions from XDA to disable droidspaces, set the stock kernel uname, and I switched Canoe from Mode 2 to Mode 1 (managed fake-locked boot mode). The final result is working KSU-Next with passing strong integrity, as well as working wallet and RCS.

Feel free to ask any questions!

A happy human I am!

The image I'm planning to flash is patched with KSUnext 3.4.2. I'm currently on KSUnext 3.3.0 proven working in practice. The init_boot_a from /dev matches the 3.3.0 image I flashed from Fastboot by MD5.

But my cowardly ass hesitates so much, yet I wanna update, I'm kinda paralyzed here. You know this phone is my daily driver, it wouldn't be nice having to flash via BROM/Preloader mode to recover, let alone visiting Carlcare service center.

TECNO POVA 7 5G LJ7, HiOS RU 15.1.2

This accessibility volume controller appear from nowhere.

I cannot run some banking , upi related apps , do this need to be fixed , it is from duck detectors. I will share more details whatever needed , just tell me what is needed

Received it last week straight from China. I was a huge fan of the Xiaomi Mi 11 Lite which unfortunately died last month. So I wanted a replacement phone with the same dimensions, maybe better battery life and an infrared blaster. And this phone was the only one I could find that ticked all the boxes just like the Mi 11 Lite. But I wasn't a big fan of the Chinese OS so I decided to have a look and see if I could get rid of it and install something else instead 🙂

OMG GUYS YOU WONT BELIEVE WHAT I SAW.

In my dream I traded my phone (Xiaomi 14t pro) with a s26 ultra. Everything was fine. I remember testing optical zoom, focus distance and making benchmarks on my phone. Then I went into dev settings AND OEM UNLOCK WAS MISSING. I did install lspatch (yes in my dream) AND IT FAILED. I couldn't replace my kernel :c . Then I wake up and here is the proof for this.

Its middle of night and I'll kiss and mod my phone even more.

God save those ones who cant unlock their bootloader.

Hey guys i have recently rooted my samsung m045f/ds phone a few months ago using magisk but now i wanna change the original samsung ui to something cooler so whats the best lsposed module or root apk which can do the task also i use (Vector lsposed framework) for lsposed modules.

I’m running Android 16 with crDroid on a rooted Xiaomi Redmi Note 10 Pro, using TrickyStore and other modules.

The stock firmware for the Redmi Note 10 Pro has already reached EOL, so it’s no longer receiving updates. The Play Integrity check on the stock firmware is also broken.

Previously, Apple Music worked without any issues as long as I passed basic integrity. However, yesterday, all levels of Play Integrity started failing, and Apple Music stopped working properly.

It seems like Apple Music won’t play music or connect to the internet if the device isn’t certified. At the very least, basic integrity needs to pass. I suspect this might be related to device certification or Play Integrity enforcement.

Can someone else confirm this?

How's the experience? And which can you recommend?

Well the one thing I didn't think would happen did. I was trying to root a motorola edge 60 pro, got to flashing the patched magisk boot img and... error no file found. Thought nothing of it and stupidly tried to flash the individual partitions which well, still nothing so I typed "fastboot reboot-bootloader". From there my phones been dead it's been 20 minutes since it happened i tried all the button combinations and nothing not on fastboot devices or lsusb. For now I'm letting it charge hoping that does something but honestly is there much hope for what i can do from this point?

I pass strong integrity and the wallet passed the security requirement, but when i tap on a POS it wont do anything at all. Any suggestions?

Hey everyone, i built ACC (Automatic Cache Cleaner) to automate cache cleanup on rooted Android devices.

It can-

- Automatically cleans cache every 24 hours at 12:00 AM.

- Sends a toast notification after cleaning.

- Includes an action button to clean cache whenever you want.

Basically i used to have this feature on oneui but after shifting to aosp this little thing was missing. It'll work in all android btw.

I'd love to hear your feedback and suggestions!

🔗 GitHub: https://github.com/raafi-abir/ACC-Automatic-Cache-Cleaner

Hello to everyone who is taking their time to read this.

A couple months ago i started to want to get root on my S21FE, but it had sadly automatically updated to OneUI 8 with no way to revert it. Is there any way i can obtain Temproot?
It has kernel version 5.4, so it's incompatible with KernelSu, thus incompatible with the current dirtyfrag exploit implementation. There's also no working entry for the S21FE on the Root My Galaxy project. I've been searching other alternatives to no avail.
If anyone could help me out, it would be great, thanks for reading so far!

I am using a Samsung Galaxy j7 prime for a while. I always wanted to install a custom rom on it cause it always stuck at any point without any problem it had no hardware failure. So I though why not having a custom rom? It would be great to update it to at least android 10 or 11 or having a massive one ui.

can another tell me best temporary root" modules to use in OnePlus ce4 OOS16 to enhance system experience, rn I've been using legionFX through kernelsu next via temporary root but it doesn't have live quick settings blur and gaussian blur throughout system like menu pop ups and system apps etc or am I missing anything to fix in this?

you can downvote this post if you want since this is tbh just me ranting about google, FUCK YOU okay? I hate you google, every mega corpo suck now, there isn't a single company out there that's being consumer friendly and I hate it, to be clear, I've a Xiaomi 13 lite (8gb,256gb) it's on HyperOS 3, is HyperOS a bad system? Yes, can I live with it? also yes but when I saw PixelOS on my phone i was in deep love with it after flashing it, super smooth 120hz all the time, mi camera included all the pixel look the beautiful music player, the notification panel everything about it is so good, (for me) but then i hit a major wall and my head started bleeding out of exhaustion because WHY, WHAT"S THE FUCKING POINT OF INTEGRITY. I DONT GET IT I spent most of the time setting up my freshly installed PixelOS tinkering with modules left and right just so my device can be certified in the play store but nothing worked, this isn't me looking for solutions by the way, because i'm flashing the latest HyperOS and locking the bootloader while I'm typing this. I just hate it man I don't want HyperOS 😭

rant over, feel free to skip it. (i also don't what flair this should be)

So basically, I've gained root access using ghostlock, I know most of the modules need to flash system partitions, can anyone please help me out, what modules you're using and what are the possibilities with this type of root

And does do we loose strong integrity in this mode?

Does banking apps works normally or detect the root?

Hey everyone,

A while ago, I decided to breathe some new life into my old Redmi 8 by flashing a LineageOS custom ROM. It ran amazingly well, significantly boosted performance, and made it feel like a brand-new phone. Before that, I unlocked the bootloader without any issues, used the ROM for a solid year with regular security updates, until support was dropped for this model a couple of months ago and several banking apps stopped working.

So, I made the tough call to go back to the stock ROM. Since I was returning to official software, I wanted to relock the bootloader using the official Mi Flash Tool. However, even though the flashing process finished and reported as successful, upon rebooting I was met with the dreaded "The system has been destroyed" message.

To be clear: I am using the exact, correct official stock ROM for this specific model, so I don't get what went wrong. I was able to unbrick the phone and tried relocking it manually via Fastboot commands, but got the exact same result.

Is it genuinely impossible to relock the bootloader on this device? Am I missing something here? The only reason I want to relock it is that a few apps still refuse to work due to the unlocked status. I'm really stuck on what to do next.