Database Develop

Successful rooted OxygenOS Open Beta 8 (Nougat)

Step 1: flash phh superuser.
https://superuser.phh.me
Step 2: flash SuperSU SR5.
http://forum.xda-developers.com/showthread.php?t=2868133
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Why do you need to flash phh superuser when you're gonna flash SuperSU 2.78 SR5?

fiepi said:
Step 1: flash phh superuser.
https://superuser.phh.me
Step 2: flash SuperSU SR5.
http://forum.xda-developers.com/showthread.php?t=2868133
Click to expand...
Click to collapse
There is no need to flash PHH Superuser. I just flashed SuperSU 2.78 SR5 and it's working fine.

I want to uninstall apps with Root App Delete but it ask for root. I have flashed ,SuperSU SR5, in recovery. I'm on Nugat oos 8 beta, of course.

zTweaked said:
Why do you need to flash phh superuser when you're gonna flash SuperSU 2.78 SR5?
Click to expand...
Click to collapse
Yesterday. I try only flash SuperSU SR5 but no root

brath23 said:
There is no need to flash PHH Superuser. I just flashed SuperSU 2.78 SR5 and it's working fine.
Click to expand...
Click to collapse
fiepi said:
Yesterday. I try only flash SuperSU SR5 but no root
Click to expand...
Click to collapse
i'm was TWRP 3.0.2.128...flashed OOS beta 8, SuperSU SR5, all fine but no root and TWRP gone. reflashed TWRP with fastboot, reboot to recovery, from TWRP flashed SuperSU SR5, everything works now, no issues so far:good:

This topic is on the wrong place you should post in questions

All I did was reflash sr5 after I set up the device and apps and i was good to go. Only issue I had was bootloop when upgrading to beta8 and factory reset got it to boot again. I'm starting to think that any restoring of nandroid backups then trying to upgrade is borking something, but that's a different topic for a different day as I am very pleased with this rom

After flashing the rom (via modded twrp), flashed twrp and supersu 2.78 sr5. Rebooted to system. But supersu wasn't present. Rebooted to twrp and reflashed supersu sr5. Now everything's fine. No need install phh superuser. I guess it unroots the phone in the first boot and that's why we need to flash superuser twice.

Any idea on how to hide SuperSU (without xposed, of course)? suhider doesn't seem to be working with 7.0. I want to know for sure before I upgrade because of snapchat blocking rooted logins.

What a useless thread.

I'm facing problem when I'm trying to update my K20 Pro Chinese device.

My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me to solve this

L1mon said:
My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
Please help me to solve this
Click to expand...
Click to collapse
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go

zgfg said:
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go
Click to expand...
Click to collapse
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.

L1mon said:
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.
Click to expand...
Click to collapse
I answered you in the previous post that for OTA you must not have OrangeFox - you must reflash stock Recovery before you go for OTA

Development Redmi note 10 5G TWRP-recovery 3.5.2 android 11

This is TWRP that I compiled. I tested it myself. It works on this version, but the touch screen doesn't work
The decryption function is there, but it doesn't work properly, entering the correct password can't decrypt it, I hope someone fixes it
version:V12.0.6.0.RKSCNXM
android:11
Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This device tree, I referred to github
@mastersenpai05
This is my modified device tree
github @xxroot/twrp_camellia
flash :
fastboot flash boot boot.img
fastboot reboot recovery

Can i flash magisk with it?is backup working?Can i restore?

g465559090 said:
This is TWRP that I compiled. I tested it myself. It works on this version, but the touch screen doesn't work
The decryption function is there, but it doesn't work properly, entering the correct password can't decrypt it, I hope someone fixes it
version:V12.0.6.0.RKSCNXM
android:11
Download
View attachment 5463601
This device tree, I referred to github
@mastersenpai05
This is my modified device tree
github @xxroot/twrp_camellia
flash :
fastboot flash boot boot.img
fastboot reboot recovery
Click to expand...
Click to collapse
Why english is not working?And why I can't boot the phone?It only boots on twrp i cant boot my phone pls help

i think working only for global 12.0.6.0 dont flash on miui 12.5

wetito said:
i think working only for global 12.0.6.0 dont flash on miui 12.5
Click to expand...
Click to collapse
I tried its working but i can't boot to android,maybe flashing it to recovery partition can fix it

As I understand it, because there's no recovery partition, after using TWRP you need to boot back into fastboot and flash your normal boot image to be able to boot to Android.

skm_1 said:
As I understand it, because there's no recovery partition, after using TWRP you need to boot back into fastboot and flash your normal boot image to be able to boot to Android.
Click to expand...
Click to collapse
This phone does not have a Recovery partition. Its boot partition is integrated with Recovery, so if you have to swipe back to the official boot.img to boot android. If you want TWRP and Android to work, you'll need to modify boot.img

how do i back to mi recovery? Cause the recovery.img is not there with the rom fastboot type

Can't we have any developer? For this device...? It sucks.... Every other redmi phones have twrp and roms.. but not this one.

Should I update to Magisk 25.2 after flashing 24.3

According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385
Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.
Should I continue? Since this is after the fact?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.
So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.

Alright, I'll update the thread if everything goes well.
Thank you!

Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.
Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.

I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.

newt23 said:
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
Click to expand...
Click to collapse
Greetings Friend,
Can you attach the Dmverity Disabler zip?

OldNoobOne said:
Greetings Friend,
Can you attach the Dmverity Disabler zip?
Click to expand...
Click to collapse

Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?

Question Magisk-ing MIUI 14 EEA

Hello again,
So about 2-3 weeks ago, tried to flash Magisk on my Redmi w/ a boot image from the Recovery ROM of 14.0.1 EEA. Put it on my phone, patched, but after flashing the phone would boot to FASTBOOT. Tried patching the vbmeta, just in case, but no luck. OK, tried flashing the stock boot image, but IT STILL wouldn't boot, even if it was from 14's recovery or 13's FASTBOOT. Even went as far as flashing China ROM image. But here's where it gets interesting, but before that...
Last night I saw that now there's a FASTBOOT ROM available for EEA, so before bricking my phone again ( I'll explain), I want to ask if there's also somebody trying to root their phone on MIUI 14, and if they did, was everything alright?
Now the Chinese story! I said that I've flashed a China boot image on EEA, but it didn't boot. BUT I tried using XiaoMiTool to flash the correct firmware, cuz I had access to recovery and FASTBOOT, and it identified as camelliA, not camelliAN. It wasn't doing this before... Said it was bricked and it started flashing China 14.0.2 in FASTBOOT. Ofc it didn't boot. Then I tried w/ access to FASTBOOT to flash the Recovery 14 EEA boot image AND THEN connecting the phone, and THIS TIME, it showed camelliAN, even tho there's China ROM. Then I bricked it and flashed 13, then upgraded, tra-la-la-la, la-la, bulls**t stuff.
My thinking, is that the OSs boot image is somehow the source of identity for the device's specs and codename.
With that in mind, is there a way to successfully flash China MIUI 14 ROM on Global, and if yes, can it be flashed European or any global ROM's boot image on top of the Chinese ROM and identify w/ codename camelliAN instead of camelliA? AND THEN patched Magisk?
Just asking, ya know...

Currently running Magisk on MIUI 14 using a patched boot.img from the MIUI 14 EEA Fastboot ROM. I flashed the stock firmware first to make sure it booted. Then I flashed the patched boot.img. I went from MIUI 13 Global to EEA MIUI 14 however. I'm not sure if it's possible to use the EEA boot.img on a China ROM, this is my first Xiaomi device so someone will know more than myself. Already bricked it once No issues yet with root, even bypassed Play Integrity API for Google Wallet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}