Database Develop

[ROOT] Galaxy S9 and S9+ Official Stock 8.0 MAGISK - UNOFFICIAL

Hello everyone this a little guide for rooting your Galaxy S9 and S9+ (EXYNOS) with Magisk
The Magisk file provided here is a modified one.
Quote:
READ THIS BEFORE ROOTING DEVICE
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, you can use Magisk Hide
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
This Magisk file is outdated, Magisk hide is not more working SafetyNet Fail
How to Use
Before Beginning I recommend update to the latest oreo update.
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option )
3.Download TWRP for S9 or S9+
4.Switch Off device
5.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
6.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
7.Select TWRP (tar image) with AP tab of Odin and Start
8.Once Successfully flashed, you will see 'Passed' in Odin tab
9.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
10.Select to allow modification
11.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
12.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
13.Flash no-verity-opt-encrypt-samsung-1.0 and then Magisk
14.Once flash successfully finish, Reboot to System
15.Open settings - Developer option - Look for OEM Unlock option. It will automaticaly change to unticked after some reboot don't stress it's normal.
16.MAKE A BACKUP IN CASE OF BOOTLOADER RELOCK.
Enjoy ! You have your Galaxy S9 or S9+ rooted.
Credits goes to jesec [url]https://forum.xda-developers.com/member.php?u=6371894[/URL] for the modification of Magisk.
Magisk 16.3 modified:
[url]https://mega.nz/#!ec9zkDIA!w8Q77oIZAUgKUSePDmTsVBwfTKjU8C81WGdCgIUnQvM[/URL]
no-verity-opt-encrypt-samsung-1.0:
[url]https://androidfilehost.com/?fid=962187416754474353[/URL]
Twrp S9:
[url]https://twrp.me/samsung/samsunggalaxys9.html[/URL]
Twrp S9+:
[url]https://twrp.me/samsung/samsunggalaxys9plus.html[/URL]

Does this work with SD or only Exynos?

But tabletmen! le omelette du baguette! you can not le steal le someones le elses le work!

It it you tabletmen? Lol

What about Android pay, or is it just Samsung pay which no one really cares about?
Who are the key Devs working on magisk and getting root bugs fixed on Oreo for the s9?
Sent from my [device_name] using XDA-Developers Legacy app

Unheard said:
Does this work with SD or only Exynos?
Click to expand...
Click to collapse
im guessing its mainly for Exynos, but than again he hasnt answered back so im hoping its for Snapdragon also. that would be solid. thank you.

Anyone tried this?

kijp15 said:
im guessing its mainly for Exynos, but than again he hasnt answered back so im hoping its for Snapdragon also. that would be solid. thank you.
Click to expand...
Click to collapse
If someone find a way to unlock the bootloader of the SD devices this Tutorial will work.

rxk said:
Anyone tried this?
Click to expand...
Click to collapse
Yeap I did it !

Hi guys.
After all phases of the process I go through the Developper Options menu and I have OEM Unlock setting turned off. I have turned it on again, reboot but still disabled in the Developper Options. It is safe to reboot and keep it disabled? Please see the attached image. Thanks.
{
"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"
}

So, I have rebooted my phone although OEM Unlock is disabled. And everything works fine, TWRP and root by Magisk included.

TidjyK said:
Hi guys.
After all phases of the process I go through the Developper Options menu and I have OEM Unlock setting turned off. I have turned it on again, reboot but still disabled in the Developper Options. It is safe to reboot and keep it disabled? Please see the attached image. Thanks.
Click to expand...
Click to collapse
You need to install the latest update on your phone.

TidjyK said:
So, I have rebooted my phone although OEM Unlock is disabled. And everything works fine, TWRP and root by Magisk included.
Click to expand...
Click to collapse
Greats but remain attentive that could brick the telephone.
To avoid any kind of problem DON'T UPDATE MAGISK.

frauchgu10 said:
You need to install the latest update on your phone.
Click to expand...
Click to collapse
The latest TWRP you mean?

Is this magisk the official version?

frauchgu10 said:
The Magisk file provided here is a modified one.
Click to expand...
Click to collapse
So this is not the official version.

TidjyK said:
The latest TWRP you mean?
Click to expand...
Click to collapse
No, the latest oreo update.

I have 2 problems after rooting in this way
1- Titanium backup dosnt show root & when i reinstalled it Crashed every time run .
2- Bluetooth reset every time turn off .
Can i unistall Magisk & then root with Supersu RC5 or i will face OEM problems ??

Need help.
after I modify prop.build (ro.config.tima=0) to fix samsung health. After reboot I lost root. Can I re flash magisk with oem unlock option disable?
please help..
-----
I rebooted my phone again and my root is back.
Tnx

rxk said:
Need help.
after I modify prop.build (ro.config.tima=0) to fix samsung health. After reboot I lost root. Can I re flash magisk with oem unlock option disable?
please help..
Click to expand...
Click to collapse
Yes

Device stuck in TWRP

Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
{
"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"
}

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
hey does your device have an working os ?

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported

Benjamin0702 said:
hey does your device have an working os ?
Click to expand...
Click to collapse
Benjamin0702 said:
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported
Click to expand...
Click to collapse
Like I said, I am stuck in TWRP. I can't boot anything and I guess I don't have any os anymore.

Are you frozen in a black screen?

Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.

mrtr33 said:
Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.
Click to expand...
Click to collapse
You need to erase the "misc" partition.

VD171 said:
You need to erase the "misc" partition.
Click to expand...
Click to collapse
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext

mrtr33 said:
View attachment 5264227
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext
Click to expand...
Click to collapse
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/

VD171 said:
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Click to expand...
Click to collapse
Now I get the following error when trying to install the xiaomi.eu ROM form SD Card:
Code:
E: unable to update logical partition: /system_ext
E: unable to decrypt FBE device
After installating and rebooting I am back at TWRP again.

Stuck On Fastboot (SOLVED)

I tried to uninstall magisk via twrp flashing boot.img but only appeared the fastboot screen, so tried to restore stock rom but still on fastboot
Tried MiFlash, XiaoMI tool v2, MiFlash Pro with so many fastboot roms, flashed custom roms (included the aosp derivates and the latest miui eu) and still no luck, at least twrp and custom recoveries works fine
Please help, I already spent to many days trying to fix it
Edit: Tried to flash vbmeta again and now it works

uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)

fonzacus said:
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
Click to expand...
Click to collapse
Basically i tried everything in the guide and other xiaomi guides (Except flashing via EDL), in the gui tools always show as "Success" and via fastboot all seems to be flashed correctly but still got the fastboot screen
Edit: Trying one more time with another vbmeta and instaled dotOS, Now it works

just a side note, miui >12.5.x were built to be more picky with everything in general. you mightve been blocked by miuis avb (custom vbmetas workaround this) when you were sent to fastb
hence why twrp 3.6.x includes an advanced installer option (workaround this and other brands)
as for trying to fully uninstall magisk, lots of others (including me) failed lots in the past on 23 and canary (and other forks), reinstalling again seems to fix it
thankfully you got it up and running, tho id recd something other than dot, i and others found it battery heavy for some strange reason ;P

good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.
{
"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"
}

xXchizaXx said:
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.View attachment 5650943
Click to expand...
Click to collapse
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?

fonzacus said:
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
Click to expand...
Click to collapse
Fortunately, you can install the Miui through the flash ROM, but unfortunately the Miui 11 version blocked me from starting up again, so I can't put any more ROMs in it.

How To Guide How to flash a GSI on Oneplus 10 PRO/T

MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA!​Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT!​
What does not work?​Fingerprint
face unlock
native camera app(Use gcam)
no notification slider
no modular refresh rate
no auto brightness(Not yet will be implemented)
no 5g(no worry no one uses it yet so)
maybe more let me know if you found a solution so i can add it under this post
I'm working on a overlay to fix some things for this device
What do I need?​A Unlocked bootloader Follow below.
Stock zip download this with oxygen updater(enable advanced mode and download your version)
Oneplus drivers Here
Latest Fastboot Enhance Here
And a GSI of choice you can get Here or Here dot os works good with this phone
Choose AB GSI and you don't need slim(Low system volume device's) or vndklite(For older device's)
Unzip and put all the things in a folder.
Start with installing the Usb drivers
and connection device to your computer. (no need to disconnect till your set)
If your in windows use
Code:
cmd
Unlocking Bootloader (This will wipe device)​
Go to Settings/About device/Version and tap the build number/version until you see your already a developer.
Spoiler: screen
{
"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"
}
Go to Settings/Additional settings/Developer options and enable OEM unlocking
Spoiler: screen
On your Computer open fastboot tool folder and open a terminal there and type
adb devices
Accept on your phone
adb reboot bootloader
wait till boot
fastboot flashing unlock
device will ask you to confirm if you want to unlock Confirm this
Spoiler: screen
Gathering your assets​On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Spoiler: screen
Preping device for GSI​On your computer open fastboot tool folder and open a terminal there and type
adb reboot bootloader
Wait till boot
fastboot reboot fastboot
you will see a screen with Chinese and languages as options don't do anything here.
On your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
than click on your device and go to partitions
Spoiler: screen
To make space for our new OS we need to make space so we are going to remove the old firmware left after update's
In the petitions tab type -cow and delete these volume's, Yes all volumes this will not affect your device
Spoiler: screen
Skip all above if you already on a GSI​The flashing of the GSI ​Make sure your GSI is a .img Unzip if its a xz/zip file
Now open fastboot tools folder and start a terminal there
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system Gsi.img
Spoiler: screen
wait till finished than on the phone click English and Format data and wait till it boots.
Spoiler: Pixel experience
Spoiler: CherishOS
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader
fastboot boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.

reserve

Back to stock
Very simple aslong you dont mess around with other partitions
Open the fastboot tools folder and start a terminal.
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system
fastboot flash system THE_SYSTEM_IMG_BACKUP_YOU_EXTRACTED
fastboot flash vbmeta vbmeta.img(Will remove gsi flash ability)
fastboot flash boot boot.img(Will remove root)
wait till finished than on the phone click English and Format data and wait till it boots. and your back to ****ty ColorOs

Absolutely what we need

Have anyone tried GSI on OP 10 T. Wanted to get a sense of this before I jump on.

Good man
I'll flash in the morning.
Cheers.

dladz said:
Good man
I'll flash in the morning.
Cheers.
Click to expand...
Click to collapse
Which one you took? Working fine so far?

I'm gonna make a overlay for our device this may box some issues and bugs

MrScarl3t said:
I'm gonna make a overlay for our device this may box some issues and bugs
Click to expand...
Click to collapse
Overlay?

lovesetcpu said:
Which one you took? Working fine so far?
Click to expand...
Click to collapse
I actually updated to beta 2, I couldn't help myself..tbh it's really good I'd recommend it.
Proximity sensor doesn't work for me or auto brightness but everything else is superb.. you can update directly from 12 to 13 using the update APK..
If you check the beta update thread on xda in this 10 pro section and you'll see it.. look for post #55

Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T

alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.

dladz said:
What didn't work or what did? Besides volte, I don't care for it here in the UK anyway.
But I'm interested in what is functional and what's not..
Appreciate you giving it a whirl.
Click to expand...
Click to collapse
Honestly it was pretty good overall. As mentioned in OP, finger print, DTW, face unlock, auto brightness, VOLTE (my requirement as my network works on that for voice), doesn't work.
Besides these fairly good, passes safety net without root, (may pass even with it), fast charging ( didn't exactly time it or measure, but was fairly close to the stock ultra fast charging experience), and the beautiful fluid AOSP experience, 120 hz rr and the performance was somewhat better than stock, at least for gaming. Got 2800+ on 3d mark extreme and got 95% stability on the stress test. FYI - OP 10 T

alanzaki073 said:
Thanks for the great guide on GSI. I managed to flash PE and Cherish OS, however, had to revert to stock as I couldn't get VOLTE to work. Tried all the ims in settings option, the GSI VOLTE FIX module but nothing helped. I can het LTE working, but not VOLTE. The problem is IMS is not registering. You have any suggestion to get the VOLTE working. BTW, my device is OP 10 T
Click to expand...
Click to collapse
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why

MrScarl3t said:
I will try tomorrow with OnePlus IMS apks maybe it will work. The phh IMS is not supported that's why
Click to expand...
Click to collapse
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus

alanzaki073 said:
So, is it gonna be stored in System/priv app? I'm currently back on stock (will check for the ims apk) but itching to flash either PE or Corvus
Click to expand...
Click to collapse
The name is org.codeaurora.ims don't know where it's located

I wish that it became more stable!
I can't stand with ColorOS 13 [OxygenOS 13] !!

Any luck on VOLTE?

Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well

yo-less said:
Just wanted to say thanks again, it's great that you took the time to explain what to do in detail. Was able to flash dotOS without problems and to go back to Oxygen OS as well
Click to expand...
Click to collapse
How was the experience?
Why you back to OxygenOS?

[HELP] Bootloop after installing magisk on Xiaomi Redmi 7A

Hi, I'm trying to root my Redmi 7A with Magisk. I have patched the recovery.img of my stock ROM (MIUI V12.5.2.0.QCMMIXM) and then flashed it with fastboot. Then I rebooted into the recovery, released the key combo and the system seems to boot properly but it block ath the MIUI splash screen.
Then I need to reboot normaly and the root is'nt installed.
I also tried with patching the vbmeta.img like said here but it's the same result.
Same result with the patched boot image
I know that all my data / settings are properly loaded (I can see my luminosity and reader mode during the MIUI splash screen)
That's all, I hope there is someone who know how to solve this.
Specs :
- Xiaomi redmi 7A
- Magisk v25.2
- MIUI verison : MIUI Global 12.5.2 stable (12.5.2.0QCMMIXM)
- stock ROM found here : xiaomifirmwareupdater.com
Thanks

Choucroute_melba said:
Hi, I'm trying to root my Redmi 7A with Magisk. I have patched the recovery.img of my stock ROM (MIUI V12.5.2.0.QCMMIXM) and then flashed it with fastboot. Then I rebooted into the recovery, released the key combo and the system seems to boot properly but it block ath the MIUI splash screen.
Then I need to reboot normaly and the root is'nt installed.
I also tried with patching the vbmeta.img like said here but it's the same result.
Same result with the patched boot image
I know that all my data / settings are properly loaded (I can see my luminosity and reader mode during the MIUI splash screen)
That's all, I hope there is someone who know how to solve this.
Specs :
- Xiaomi redmi 7A
- Magisk v25.2
- MIUI verison : MIUI Global 12.5.2 stable (12.5.2.0QCMMIXM)
- stock ROM found here : xiaomifirmwareupdater.com
Thanks
Click to expand...
Click to collapse
Firsly, here you have the general forum for your model here on XDA https://forum.xda-developers.com/c/redmi-7a.9077/
This thread has some insights for your issue https://forum.xda-developers.com/t/boot-img-patched-boot-img-files-patching-tool.4030777/page-3
As far as I remember, you need to patch only the boot image, patching other image like the recovery, won`t work, but read well that thread, you`d need to, firstly, patch the boot image with this tool https://github.com/YaAlex3/patcher-oss, and only after that, Magisk can patch the boot image, to be flashed.

Ok, I'll try this and give you an update.
Thank you

Hi again I have tried the patcher-oss but it give me the following output :
Exception: ERROR: Didn't find skip_initramfs, no need to patch.
I retried to flash this boot.img patched with magisk (with no error) and this time, idk why but MIUI don't boot and the bootloop stay on android splash screen.
The other patcher given I the thread don't work 'cause of a socket error and put the magisk.zip file don't fix it.
that's all, it's a little bit annoying so if you or someone have any idea on how to root this f****** device it would be very nice
Thanks

{
"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"
}
su command exist.
So the root worked
android booted properly
all my data / settings are still here...
but what the hell is with MIUI ????

Choucroute_melba said:
View attachment 5703915
su command exist.
So the root worked
android booted properly
all my data / settings are still here...
but what the hell is with MIUI ????
Click to expand...
Click to collapse
Not clear, you meant, now it`s rooted but device is not booting. Don`t let your post as a guess, it`s not clear what you did. These commands are from?

When my device boot it's firt boot Android with the "powered by android" splash screen and then MIUI boot with the MIUI splash screen.
In the case of my post, android has booted successfuly (Ihave access to adb and my phone shell) and when I execute the su command, nothing happens but it does not tell me that the commands is "innacessible or not found". so I deduced the command exist and the phone is rooted (maybe there is still something missing, I don't know, but it's a different behavior from when the phone is normal).
BUT MIUI refuse to boot and block on the MIUI splash screen.
That's why i said that Android booted properly and the phone is rooted, but maybe I'm wrong
Tell me if you have any question or if you want me to test something.
Also about the patcher, do you know if there is a way to make it work ?
Thanks

Choucroute_melba said:
When my device boot it's firt boot Android with the "powered by android" splash screen and then MIUI boot with the MIUI splash screen.
In the case of my post, android has booted successfuly (Ihave access to adb and my phone shell) and when I execute the su command, nothing happens but it does not tell me that the commands is "innacessible or not found". so I deduced the command exist and the phone is rooted (maybe there is still something missing, I don't know, but it's a different behavior from when the phone is normal).
BUT MIUI refuse to boot and block on the MIUI splash screen.
That's why i said that Android booted properly and the phone is rooted, but maybe I'm wrong
Tell me if you have any question or if you want me to test something.
Also about the patcher, do you know if there is a way to make it work ?
Thanks
Click to expand...
Click to collapse
If you can really boot to Android completely then, test the root status with some root app checker, if you can't do that, then the device didn't boot properly, in a way ADB can interact with.
Unfortunately, from what I did test it in the past, the tool works with some boot versions only. By the way you have a boot collection in the first posts, you can pick up from.

Hi ! I finally managed to install a custom ROM (Arrow Os) and then the root went by himself.
Thank you for your help