Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.
Related
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working
adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.
adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.
adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Don't install TWRP yet. The people who are infinitely smarter than I am will make a TWRP that will work for OB1, and that's way above my pay grade. I hope this helps someone.
[Tutorial] How to flash a new boot.img via Fastboot
Hey Guys, since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode) If you have fastboot already installed on your...
forum.xda-developers.com
Here's how to use it.
getting 'unable to parse kernel log' error
peachypickle said:
getting 'unable to parse kernel log' error
Click to expand...
Click to collapse
it worked fine for me.
How install oxygen os open beta 1 android 11 with keep rooted? Any video tutorial?
it's not too bad...
Install the OTA
Go to magisk manager and pick install.
pick install to inactive slot (after OTA)
make sure you don't have any modules enabled that may be incompatible.
reboot
when the 11 TWRP drops, you can install it as a magisk module to gain custom recovery back
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
spheady said:
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
Click to expand...
Click to collapse
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
spheady said:
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
Click to expand...
Click to collapse
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
LokifiedMee said:
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
Click to expand...
Click to collapse
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Crazyinsanejames said:
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Click to expand...
Click to collapse
Ohh couldn't find Orangefox dual boot's post today so here is the twrp file. It's not really worked on right now and has option to flash magisk on R11 Pass but the copy of magisk is no good on the R11 OS but has magisk. 20.4 option for a Q10 is, when it IDs it. You'll see. The script options. PS orangfox dual booting with three different drives rocks. Also it has a app manager and a magisk mange GUI. Almost forgot beta 10 version 17-19 will not successful y flash this twrp. But any other copy for the phone on xda or OnePlus.com work fine. It's a encryption variety problem. If your password becomes corrupt (only on OS can have password type security on a dual boot setup... I got away with using the same password on both OSs for a minute though. ) in the root partition thiers a directory called Ffiles, with .zip you can flash while TWRped to fix a few things like that. Other than that let me know. Lol I want to mention Evey time you flash an OTA or anything that will alter the work this twrp installs, you need to flash the file afterwards, before rebooting. And reboot after flashing it so everything links up. Of coarse you can select to reboot right back to recovery. Best luck I couldn't find their post on xda so that's why I typed up so much. Lol I'll be funny again I don't know who this stuff on how to downgrade really but thiers a Windows tool that has capibillities err what ever to flash a OTA of 10 in fastboot mode. Anyways no worries. It's called all-in-one flash tool. Works on maney OnePlus phones. Maybe for encrypted data partitions. I run unencrypted stuff I do not like encryption on any electric devices.
aNGERY said:
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Click to expand...
Click to collapse
I just want to say thank you. I tried the new magisk update and it didn't work. I could get to recovery and figured I had PB1 for Andoid11 anffd I would flash to gety baclk to working. Of course I lost root, but was able to get it back with magisk_patched_Ei056.img flashed to boot. It works fine. Can hang with root until TWRP gets updated.
VERY APPRECIATED.
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Crazyinsanejames said:
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Click to expand...
Click to collapse
Well found out thevendor.img didnt work lol. Anyways heres cheap trick i found if your not on an OS with twrp
http://Link removed
aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.
SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
I'm pretty sure it's insinuated that it's pertaining to OOS11. Don't be willfully obtuse.
SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
35090 for Android 11 on the OnePlus 7 pro will not work without decrypting it.
Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
actually I take that back.
Download TWRP for guacamole
Download TWRP Open Recovery for guacamole
dl.twrp.me
Here you go, 3.5.0_9-0 is the one release on 12/28. Install it and let us know how you like it!
spheady said:
Lol nice it worked. Lol it also
Ty tried for fun. Think thos thread is for ppl trying to boot a .img file of twrp. Can this flash via fastboot. So twrp to twrp I think ill keep my dual boot Twrp its not so basic.ty
Click to expand...
Click to collapse
You can reboot to recovery from the OS with this twrp installed?
Hi, i'm trying to root my CN version 13.0.5 without the twrp, I'm using the magisk to patch the boot file, but after patch and use the command "fastboot flash boot boot.img, the mi 11 ultra just stuck in the mi logo. I'm not been able to root my phone, right now, how to root the CN version 13.0.5?
i did the same root with the android 11 and worked, something change?
hi, did you install magisk canary and not magisk stable?
I have just Root Xiaomi.eu A12 Miui13 with the same method and it work.
Hi. FIrst - better to use Magisk 23.0 - as you will still have Magisk hide. But more important - just the "fastboot boot boot.img" command instead. Once you have booted without issues you can go into Magisk and patch the real boot image file from there and restart. This is how it always worked for me. Not really sure what is the big difference there but as I said - that worked for me.
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot flash boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
marcel112 said:
When you are running the miui 13, copy the boot.img from fastboot folder to your phone(remember the location). Open magisk app, choose install and search for boot.img on your phone. After patching is done, copy the patched file into your fastboot folder on pc. Boot into fastboot, type fastboot boot (and drag the patched file from fastboot folder here) and hit enter. after flashing fastboot reboot
Click to expand...
Click to collapse
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Afg Playa said:
Does that Format my Data? And how do i remove the Patch(remove magisk)?
Click to expand...
Click to collapse
It does not format. That's just for root. You can flash the rom in fastboot again or flash the boot.img again from the folder images
thiagoserrao said:
Thanks for the help, i'll try to patchin a few hours and back here to give the feedback!
Click to expand...
Click to collapse
Did IT Work?
Afg Playa said:
Did IT Work?
Click to expand...
Click to collapse
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
thiagoserrao said:
Using CN no, i tried with the rom downloaded but didn't worked. So i take a step and installed the EU version, not been able to connect to android auto and other stuffs was killing me!
After install the EU version, i just did the same steps to root the boot, and worked without problem
Click to expand...
Click to collapse
Great, It also worked for me Xiaomi.eu 13.0.9.0.
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
User1977 said:
I have difficulties too rooting my Mi 11 Ultra with Android 12. I have installed the latest canary of Magisk and when I patch the boot.img and flash it the device stucks on Android logo. When I boot the device with fastboot boot magisk_patched***.img I'll get a black screen.
Can anybody post a patched boot.img from Xiaomi.eu 13.0.9.0 Rom? Perhaps it works when I flash this one on my device.
Click to expand...
Click to collapse
i just lost my root without reason, i just restarted my phone, than no root anymore and not being able to installing again ;D. what a hell
Start from the beginning by flashing unpatched boot.img and use Magisk v23. V24 has nothing but problems. I was frustrated for a few hours with it and going back to v23 solved everything.
I'm new here on this site and idk if I'm doing I correctly but I need help with it. I'm a noob to rooting and Twrp stuff. I have unlocked my bootloader and have tried to watch videos about rooting and read articles but I couldn't understand. That's why I am posting this thread. Could someone explain things to me in the most simple way and how can I avoid bootloops or stuff like that if I come across one. I'd appreciate it very much.
I think it is best to start with reading the "HowTo" guides
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Alright I'll try it, thanks
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Hello Sir, sorry to disturb you again. I have installed the adb, fastboot and fastbootd drivers. I need your help with something, should i continue with the latest version of Magisk? I have Redmi note 10 pro (sweet)
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Elinx said:
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Click to expand...
Click to collapse
Im following the guide that you have given the link for. And by update do you mean I can install new updates of the phone (because I know after rooting you can't or won't receive updates) or do you mean magisk by it? Well I want to modify and tweak with my Phone appearance and install some modules. For now Im not going for custom roms. Since I just want to root my phone for now, could you please tell me what do you mean by original stock boot.img? Because I have downloaded and extracted the rom contents that i have in my phone (following the guide). I know I am asking too much, sorry
p.s. what would you like to suggest me to use the latest version of magisk or some old version?
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Elinx said:
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Click to expand...
Click to collapse
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Bilalbilly87 said:
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Click to expand...
Click to collapse
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Elinx said:
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Click to expand...
Click to collapse
I have installed Twrp and Magisk As well. I was able to install some modules but with some modules I'm having this problem and I don't quite understand why. I downloaded it from GitHub like the zip file and after flashing.
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Elinx said:
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Click to expand...
Click to collapse
Thank you for helping me. Actually i was having problem with flashing the modules, because the contents are in the zip file in a folder and they need to be outside of any folder meaning all those files need to be in the zip instead of being in a folder in the zip. I'm good to go as i checked and its installing now.
kon kkonsay modules use krra ha hmy bhi bta
MehtabMad said:
kon kkonsay modules use krra ha hmy bhi bta
Click to expand...
Click to collapse
English forum....
Laptapper said:
English forum....
Click to expand...
Click to collapse
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
MehtabMad said:
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
Click to expand...
Click to collapse
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Sorry for late reply. Everything has been working okay with modules altho i didnt install alot of them but a few. So i guess there weren't enough modules which provided me any customization for Miui 13 because i had the wrong concept. Now i want to take it a step further, i want to flash a custom rom. I have looked and searched. Have decided to go for either Pixel Exp A12 or AncientOS A12 (It has alot of customizations). Now i want to ask you a few questions that i have in mind.
1) Should I flash Custom Rom through Twrp?
2) If so, do i need to flash that Dm verity file (because when I installed twrp in my stock rom which im still using rn, they told us to do that to avoid bootloop and to keep Twrp permanent so do i also need to do it with custom rom?
3) And if its safe to flash through Twrp, Could you please tell me how to (through twrp if its safe)?
4) Which Rom should i go for? Pixel or AncientOs
lineage Os
Laptapper said:
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Click to expand...
Click to collapse
yes the problem was with magisk module, thermal profile disabler. i removed it and everything is stable now