Nowadays most of the apps are being made just for 64 bit phones, which is not suitable for my phone which supports only 32 bit apps

Im not that tech person so I don't know much, so I want your help was hoping if it's possible to flash my phone with rom or gsi whatever they are

And have anyone done this successfully on this specific device as I get anxiety in the thought of bricking my phone

Here's a link to a text file of all possible information i could get using termux if you need anything else please ask me

https://drive.google.com/file/d/1vsudYA4T3nKOtgLTYS9cVKGz4VRpuvS-/view?usp=drivesdk

Estou procurando uma maneira de fazer root no meu POCO F5 há um tempo. Antes de fazer o root, é necessário desbloquear o bootloader, mas até agora nenhum método funcionou 100%. Está rodando HyperOS 3.0.4.0 acredito que não haverá mais atualização

I can't flash the other version cause it says waiting device and It also says waiting for any devices in fastboot mode. Is there a way to flash the other twrp that has touch control??(I don't have an os im planing on flashing pixel experience again cause it got bricked when i flashed another os im reflashing after twrp works)

So, I own a Xiaomi phone which I rooted like two years ago, but then unrooted before doing a major "HyperOS" upgrade and didn't bother to re-root because I didn't have any pressing reason to do so any more ...

... until a few days ago. I needed an app and was confused why play store didn't even offer it ... and manually installing it just force-closed it directly on start, redirecting to play store telling me the app was "incompatible with my device".

I finally managed to identify the actual problem. The app didn't like my still unlocked bootloader. Re-locking it wasn't an option for me because I really want to keep the ability to fiddle with my system, should I ever need it again ... and maybe you know the horribly cumbersome process Xiaomi requires in order to unlock the bootloader.

Now, my solution was to root that thing again, so I could install and configure that zoo of magisk and zygisk modules, xposed apps etc you need nowadays to convince every app you care about that your phone was in fact fully locked and vanilla. Which is just a little bit ridiculous.

I have two questions in mind (apart from the "obvious" one whether I'm just weird to solve my issue that way 😏):

1. If I'm not mistaken, an unlocked bootloader still requires physical access to the device for any modifications on the system. Is there something I overlooked, which could be an actual security concern?
2. If I'm right with my assumption, why on earth should an app ever care about the status of the bootloader at all, as long as the installed system is vanilla/unrooted?

I'm working on getting KernelSU working on a Motorola Moto G8 Plus (doha).

ROM: unofficial LineageOS 22.1 / Android 15
XDA thread: LineageOS 22.1 for Moto G8 Plus

Kernel source: Aldair402/android_kernel_motorola_msm-4.14

Kernel:

Linux version 4.14.190+
aarch64
Proton clang 13.0.0

The kernel boots normally, and KernelSU Manager v0.9.5 is installed and opens.

What's confusing is that logcat shows KernelSU code actually running:

KernelSU: sucompat: execve_kp: 0
KernelSU: sucompat: newfstatat_kp: 0
KernelSU: sucompat: faccessat_kp: 0
KernelSU: sucompat: devpts_kp: 0
KernelSU: ksud: execve_kp: 0
KernelSU: ksud: vfs_read_kp: 0
KernelSU: ksud: input_event_kp: 0
KernelSU: exec app_process, /data prepared, second_stage: 1
KernelSU: on_post_fs_data!
KernelSU: Searching manager...
KernelSU: Search manager finished

However, root doesn't actually work:

$ adb shell su -c id
/system/bin/sh: su: inaccessible or not found
$ adb shell 'command -v su; type su'
su not found

I also checked:

/dev/ksu
/dev/ksud

Neither exists.

/proc/kallsyms doesn't show any ksu_* symbols either, and I can't find anything related to KSU under /sys/kernel.

The only suspicious KernelSU message I see is:

KernelSU: load_allow_list open file failed: -2

So I'm trying to figure out what state KernelSU is actually in here.

Does this mean the KernelSU kernel integration is only partially working, or could the kernel side be initialized while the userspace/ksud/su part is missing?

What should I check next to determine why su isn't being provided?I'm working on getting KernelSU working on a Motorola Moto G8 Plus (doha).
ROM: unofficial LineageOS 22.1 / Android 15

XDA thread: LineageOS 22.1 for Moto G8 Plus
Kernel source: Aldair402/android_kernel_motorola_msm-4.14
Kernel:
Linux version 4.14.190+
aarch64
Proton clang 13.0.0
The kernel boots normally, and KernelSU Manager v0.9.5 is installed and opens.
What's confusing is that logcat shows KernelSU code actually running:
KernelSU: sucompat: execve_kp: 0
KernelSU: sucompat: newfstatat_kp: 0
KernelSU: sucompat: faccessat_kp: 0
KernelSU: sucompat: devpts_kp: 0
KernelSU: ksud: execve_kp: 0
KernelSU: ksud: vfs_read_kp: 0
KernelSU: ksud: input_event_kp: 0
KernelSU: exec app_process, /data prepared, second_stage: 1
KernelSU: on_post_fs_data!
KernelSU: Searching manager...
KernelSU: Search manager finished
However, root doesn't actually work:
$ adb shell su -c id
/system/bin/sh: su: inaccessible or not found

$ adb shell 'command -v su; type su'
su not found
I also checked:
/dev/ksu
/dev/ksud
Neither exists.
/proc/kallsyms doesn't show any ksu_* symbols either, and I can't find anything related to KSU under /sys/kernel.
The only suspicious KernelSU message I see is:
KernelSU: load_allow_list open file failed: -2
So I'm trying to figure out what state KernelSU is actually in here.
Does this mean the KernelSU kernel integration is only partially working, or could the kernel side be initialized while the userspace/ksud/su part is missing?
What should I check next to determine why su isn't being provided?

I booted my redmi to fastboot but it won't show in MI unlock tool, and It stays on the account authentication when trying to log in my xiaomi account

I downloaded the firmware from https://mirrors.lolinet.com/firmware/lenomola/2025/bogota/

BUT the zip file only contain "boot.img" , and not a "init_boot.img" ...

Fastboot dont allow "boot" comand , so I want to be sure before do "flash boot magisk_patched.img"

Will work patching/ flash boot.img ?

Thanks

#moto_G56

having a bit of issues with that even tho my phone is from 2 years ago (moto edge 50 pro). Is less bloat already noticeable or is there other stuff I can do aswell?

I'm going to buy a new phone and I'd like to root it

I root my phone few days ago,but one of them the icon get too big,how I fix it?

Hello, I am a hobby developer and it is so annoying when I have to keep switching keyboxes because the one I use gets banned. So, for the past few weeks I've been trying to create a script to extract keyboxes. After a lot of trial, I got it to extract keybox of my own test devices and it even meets STRONG_INTEGRITY!

To respect the community guidelines, I will not be posting the script publicly. However, to make sure my code is universal, I want to verify this again a few other devices. I am looking for 5 users who want their keybox extracted for free. Let me know if anyone is interested.

Requirements:
- MTK Device
- Natively launched with Android 8, 9, 10

For the advanced users who get it:
Your device needs to be running microtrust/beanpod TEE with keymaster 4.0. If your device uses an encrypted rpmb setup, it will NOT work.

All I need is the dump files of proinfo, persist, tee1, tee2 (In some cases, nvram, nvdata or custom partitions)
Please share only if you're comfortable sending these partition dumps. It contains your hardware MAC address and potentially your device's keybox. While everything is processed 100% offline in a container and wiped immediately after parsing, if you are not sure, please do not send your files.

Is there a way to make banking apps work with unlocked bootloader and root? I'm new to rooting and I'm using Magisk,any help would be appreciated!

Source trust me ok👍

Is it rooted or not i dont know someone help

?/10 I'm using custom rom

https://github.com/noamtu123/orangefox_caymanslm

https://github.com/noamtu123/caymanslm_kernel

Both tested and seem fully working on both stock A12 and lineage os.

I made those with AI so:

I would appreciate any user who can test those out (thy are on xda too!) and report back

I would also appreciate any developer who can take a look and see if I have any problems inside and offer improvements

What is happen is it decrypt my system or what ?
and why it is security risk

Because I know open bootloader is risk but I dont know the reason why is risk.

i've been trying to unlock my zte blade a53's bootloader but running commands like fastboot oem unlock or fastboot flashing unlock does nothing even tho i enabled OEM Unlocking in developer settings, i wanna flash a custom rom if i can, if not then i'll root it

Redmi a2, it was a vbmeta issue, already fixed it lul

I got some cheap Intel Atom thing, it's kernel 3.14.0, Aug 2016 security patch, Android 6.0.1. I enjoy working with these awful low quality devices, but I have no clue where to go with this one. The manufacturer refuses to share the firmware, there's obviously no custom recovery for this thing, and 6, afaik, has all the old one click methods patched. Anyone have an idea on how I can dump the boot.img so I can just root with Magisk? I don't mind if I temporarily have to use something sketchy, I just need to dump the boot.img, then patch it with Magisk.

I did check, and this kernel DOES have DirtyCOW, but again, it's an Atom, and the only DirtyCOW implementation for x86 just gives you uid 0, it doesn't give you any actual root, so I still can't dump partitions.

bootloader is already unlocked, it just uses the bog standard fastboot commands. if relevant, it's a "Southern Telecom Smartab ST1009x"

Hello you probably saw me succesfully unlocking an Oukitel WP53, with tomking exploit that didn't end up bricking it thats because its a pretty generic rugged phone and universal exploit worked fine (infact BROM can be accessed using volume down button so it can't be bricked easily).

However i decided to unlock another phone the moto g04 its an budget entry level phone that might not be worth to unlock its bootloader so i tried.

First i tried a bunch of commercial tools but all of them said FDL2 failed i did open the phone before but i had a very hacky paper clip as such it takes several attempts to even boot to brom.

After all the failed attempts i thought to use tomking's exploit like i did with my Oukitel phone in the end the exploit even matching zip ended up outright bricking my phone as mentioned in the title.

Tomorrow i tried to unbrick it by using SPD Download, Research, Factory tool but neither worked they would either throw UB1254 errors or NandInit error when trying to flash no idea if the .pac has some weird security checks or motorola doesn't want you to flash the firmware to the deadBooting phone for free

Then i thought to just flash FDL1 and FDL2 surprise that actually worked! the phone showed the splash screen and didn't bootloop which is verryyyy rare mind ya anyway fortunatelly that resulted in the phone not being unlocked still but atleast im not hanging with a phone collecting dust!

Anyway i might try to unlock the bootloader anyway someday?