Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
Related
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?
I was read https://topjohnwu.github.io/Magisk/install.html. That link describe how to install Magisk in our device in few ways. I was interested "Boot Image Patching" section that tell us about rooting device without TWRP.
Before this, I have 5 redmi devices and 3 of it were rooted-well via TWRP. 1 bricked (totally bricked) :laugh: and 1 still un-rooted (Redmi 6A-cactus).
My spec of Redmi 6A are:
Security Level Patch: 2019-03-01
MIUI Version: Global Stable 10.2.8.0 (oCBMIXM)
Unlocked: False (i know that i should unlocked it later, i still waiting my 360 hours )
RAM: 2GB
Storage: 16GB
Since i found that link, i still wondering and keep searching about: "is anybody succesfull root their device (especially Redmi 6A with same spec above) with "Boot Image Patching" way?
if any, please let me know. i just want to hear their review and (of course) their experience.
thanks
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
Nice... i'll try that soon when my 360 hours run out..
thanks.
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
adista said:
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
Click to expand...
Click to collapse
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
adista said:
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
Click to expand...
Click to collapse
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
ahhl said:
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
Click to expand...
Click to collapse
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
adista said:
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
Click to expand...
Click to collapse
Use the TWRP-1020 instead, it works much better.
hi, i followed this video and i succes for install twrp https://www.youtube.com/watch?v=522RzZ7_uRM&t=254s
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Someone said to encrypt the data on settings, i don't know how though, if you fix it, next time, don't disable the forceencrypt.
Can you post questions in the questions and answers section next time?
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
ahhl said:
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
Click to expand...
Click to collapse
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
I have a similar problem
I was rooting my redmi 6a and now its bricked
First i intall the twrp, then i flash the Magisk with DisableEncryption, the first boot work fine, i update the magisk app and the new version isnt compatible with the magisk installed
Well i repeat the steps and then i lost the signal, in that moment i didnt know it is the IMEI lost, then i try to install Lineage OS 15.1 GSI for Redmi6a cause i think that is the solution
but the system dont boot, only boot the Xiaomi Tittle with "unlocked" (I unlock the phone before) and then get me to TWRP
Im only one with this problem?
I try use the MiFlashTool for flash the stock rom but not work, now im trying with MiFlashTool flash the MIUI9 and MIUI10.2 and other versions
I think, the problem maybe is the Boot.img
(Sorry for my bad English)
Edit-
I dont have any backup lol
---------- Post added at 02:23 AM ---------- Previous post was at 02:01 AM ----------
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
¿Can you share your correct steps to have the Lineage OS 15.1 in Redmi6A Please?
ahhl said:
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
Click to expand...
Click to collapse
This "contact manufacturer" error happens when you disable dm-verity, you can install Magisk without disabling it.
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Sorry for late post
Just make sure that you flash Fastboot ROM, not just STOCK ROM. I did that last time when my IMEI/Baseband are gone. Of course it will wipe all of your data. Just be prepare for it.. :laugh:
davidhozic said:
Can you post questions in the questions and answers section next time?
Click to expand...
Click to collapse
Ups sorry.. i didnt notice that is exists :silly:
No, it wasnt like that :laugh:,, actually i did confused where should i put this question, because in Question & Answers (for me) the topic just too general and i was thinking that my question (maybe) still in development because i didnt found that in Question & Answer...
All my fault, Sorry again,
jonaaa said:
Use the TWRP-1020 instead, it works much better.
Click to expand...
Click to collapse
that just un-official TWRP, right??
i will try that in this weekend. Last time i remember that i can not boot into twrp. Till now, my devices still unrooted. I flash it back to stock ROM. But, when OTA update notification comes and reboot for installing, it give me bootloop into twrp (not to system), and that's mean my TWRP still inside i just cannot boot into.
so, i'll try that TWRP-1020 this weekend. Thanks.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
I want to access /data/system/users//settings_ssaid.xml to know what my game unique id is.
But after some research i learned that i have to root to able to get there but i have almost zero knowledge about it.
Are there any guide to root Redmi Note 10 from the scratch? Thanks.
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm on official global ROM 12.5.3.0 RKGMIXM
And i turned on OEM Unlocking in developer mode yesterday (Which is confuse me a little a guide said i have to wait for 7 days for this but mine is nothing it's just switched to on)
OEM Unlocking is only one of the steps, but it does not unlock the bootloader. File a request with Xiaomi.
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
inn0ichi said:
...
i recommend only booting to twrp, not flashing it
...
Click to expand...
Click to collapse
Why do you recommend to only booting to TWRP instead of flashing it?
Pasarireng said:
Why do you recommend to only booting to TWRP instead of flashing it?
Click to expand...
Click to collapse
because the twrp developer instruction is to booting , not flashing
alonsoj636 said:
because the twrp developer instruction is to booting , not flashing
Click to expand...
Click to collapse
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Risk of bootloop
Pasarireng said:
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Click to expand...
Click to collapse
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Y
alonsoj636 said:
Risk of bootloop
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Click to expand...
Click to collapse
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Pasarireng said:
Y
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Click to expand...
Click to collapse
Yes , is the correct way
inn0ichi said:
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
Click to expand...
Click to collapse
Please confirm these;
*So we can:
Use TWRP only temporarily, only to root the phone (by flashing Magisk v23),
and then,
back to using the stock recovery on our RN10 afterward,
even if the RN10 is already rooted?
**If the answer for my question above is yes, then (in RN10 condition of Unlocked Boot Loader, Rooted, Stock MIUI & Stock Recovery) ;
Would we still get official OTA Update from Xiaomi (and can download and install the update- as how it's like before rooting the phone)?
Thank you in advance
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
StaryMuz said:
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
Click to expand...
Click to collapse
Thanks again, (and maybe I will try your suggestion later).. but (sorry)... your reply doesn't answer my questions.
(I think my questions are very clear and probably very easy to be answered by someone who has experience/knowledge about it (like you?).. no?)
Forgive my nooby questions.
But I really want to know as much as I can (especially about the answer for some questions I have inside my head about the matter, like I asked above),.. before executing doing something about my phone.
oops... I'm sorry for double send
In the past I rooted Miui and then continued to get OTA updates. However, this cannot be confirmed for all versions of Miui. Each new update changes the phone software and so what worked before may not work today.
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
First of all, I would like to point out that Magisk (root) is a security risk. Without understanding the issues, the phone is more easily exploitable.
To install, just download the magisk file with the ZIP extension. In recovery, select the install option and select this file. Once installed, exit recovery and boot the system. Once the system boots, use magisk and complete the installation it requests.
Lolitary said:
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
Click to expand...
Click to collapse
the answer above is right ... but i would suggest to flash Orange Fox zip and then Magisk zip... to avoid problems
isn't there decrypt.zip for RN10?
How to decrypt this phone?
I usually did that along with rooting with my android phones before this.
Edit:
Update:
It's ok now I understand how, after watching this video.