I keep losing my root after reboot - Xiaomi Mi A1 Questions & Answers

Hi, just as the title says everytime i reboot my devices after successfully installing magisk through a patched boot image file i lose root. Root works i also checked with the root checker when i don't reboot my device. What is causing this ?

Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.

tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
thanks i'll give it a try

emiljano539 said:
thanks i'll give it a try
Click to expand...
Click to collapse
Flash magisk 16.7

tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
now its working after i flashed the magisk by twrp thanks

ProchyGaming said:
Flash magisk 16.7
Click to expand...
Click to collapse
i just flashed by twrp and its working now

Doesn't twrp unable ota updates?

Related

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2

xposed help

Ok I have read and searched I'm no newbie but this phone is so weird I have unlocked bootloader what order do I take to get Xposed working on official 8.1?
gtshiftin6 said:
Ok I have read and searched I'm no newbie but this phone is so weird I have unlocked bootloader what order do I take to get Xposed working on official 8.1?
Click to expand...
Click to collapse
Root with Magisk. Inside Magisk download the Xposed systemless module and the Xposed Installer apk from the support thread
Sent from my PH-1 using Tapatalk
Do I need recovery to install magisk?
gtshiftin6 said:
Do I need recovery to install magisk?
Click to expand...
Click to collapse
You need to root first.
See this thread: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
gtshiftin6 said:
Do I need recovery to install magisk?
Click to expand...
Click to collapse
Yes...
rignfool said:
Yes...
Click to expand...
Click to collapse
No, you don't explicitly need recovery (TWRP) to install Magisk.
You do need recovery to install kernels or anything similar.
Magisk has a function that will patch the boot image file if you have a copy on the phone.
You can then copy that patched file to your computer and use fastboot to flash the patched boot image.
I have used that method before.
tech_head said:
No, you don't explicitly need recovery (TWRP) to install Magisk.
You do need recovery to install kernels or anything similar.
Magisk has a function that will patch the boot image file if you have a copy on the phone.
You can then copy that patched file to your computer and use fastboot to flash the patched boot image.
I have used that method before.
Click to expand...
Click to collapse
Well... Here's my take...
You know how to do that... Therefore YOU don't need recovery...
If someone with all the information available is still going to ask the question... Then THAT PERSON will NEED recovery...
Welcome to XDA
Need patched boot file
Does anyone have a patched boot file for Magisk on Essential Phone for the latest Android P Beta? The Magisk app won't patch my boot image and won't tell me why. If I have the file from somewhere else I figure I can just flash that and be done with it. (New to XDA! )
Just install Magisk Manager, download latest pie fastboot zip from Developer Overview from Essential website and grab the boot img and patch it

updated to 9.0.11 official. can't root now

I updated to OOS 9.0.11. i was using root before the update. But this update just unrooted my one plus 6t. And now i get to root it with magisk. I installed TWRP through ADB. It worked but when i tried to flash magisk in twrp. I couldn't find the magisk file in twrp.please help me.
swahmad76 said:
I updated to OOS 9.0.11. i was using root before the update. But this update just unrooted my one plus 6t. And now i get to root it with magisk. I installed TWRP through ADB. It worked but when i tried to flash magisk in twrp. I couldn't find the magisk file in twrp.please help me.
Click to expand...
Click to collapse
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Sent from my ONEPLUS A6013 using Tapatalk
phillymade said:
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Click to expand...
Click to collapse
Did you root yours while on on OOS 9.0.11?
swahmad76 said:
Did you root yours while on on OOS 9.0.11?
Click to expand...
Click to collapse
I have two 6Ts on 9.0.11 rooted. Magisk 18.0, no issues.
OhioYJ said:
I have two 6Ts on 9.0.11 rooted. Magisk 18.0, no issues.
Click to expand...
Click to collapse
I installed the stable magisk. But no luck so far. The problem is that i can't find magisk zip in twrp recovery mode to flash it.
phillymade said:
Let's see if we can help you But first, just an FYI, you have posted in the wrong section, you should have posted in the Question and Answer section....
Moving on, what version of TWRP did you flash?
follow the TWRP guide here and use Magisk version 18.0
TWRP https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Stable version. Then you should be fine.
Click to expand...
Click to collapse
And i flashed fajita version.
You need to fastboot boot twrp image and then sideload twrp installer, then magisk 18 on top of that.
BIGWORM said:
You need to fastboot boot twrp image and then sideload twrp installer, then magisk 18 on top of that.
Click to expand...
Click to collapse
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.
swahmad76 said:
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.
Click to expand...
Click to collapse
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).
sssarg said:
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).
Click to expand...
Click to collapse
Then tell me what to do all over again?
Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Sent from my OnePlus6T using XDA Labs
swahmad76 said:
Did you root yours while on on OOS 9.0.11?
Click to expand...
Click to collapse
No, I rooted on 9.0.7
Sent from my ONEPLUS A6013 using Tapatalk
Koont said:
Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Click to expand...
Click to collapse
Did that... 100 times bro
Koont said:
Why don't you just download Magisk.zip again. Boot back to TWRP and flash
Click to expand...
Click to collapse
I just can't find any zip file in twrp! That's the issue.
sssarg said:
Updating removes root, so you have to do it all over again. It's what has to be done with A/B partitions (unless flashing full update from twrp or going the uninstall/restore images magisk-flash to other slot route).
Click to expand...
Click to collapse
You mean like unlock bootloader again? And then twrp and magisk?
swahmad76 said:
You mean like unlock bootloader again? And then twrp and magisk?
Click to expand...
Click to collapse
After unlocking bootloader.
Sent from my OnePlus 6T using XDA Labs
swahmad76 said:
I did that in the first place. As i said i had root on the previous version. But after update. I just couldn't find magisk file in twrp recovery mode to flash it for root.
Click to expand...
Click to collapse
Are you serious right now? Your can't find it either because your haven't downloaded it or haven't looked in the right directory for the zip. Download magisk boot into TWRP choose install navigate to the directory the zip is stored in then choose it and swipe to flash. And FYI anything you download normally goes to the Download folder.
Use one of the rooting tools it will do all for you, more simple.
9.0.11 don't prevent any method of rooting, it's in your side that something is wrong
Striatum_bdr said:
Use one of the rooting tools it will do all for you, more simple.
9.0.11 don't prevent any method of rooting, it's in your side that something is wrong
Click to expand...
Click to collapse
Which tool specifically?
Man, stop, I don't know, try them all

Root for RMX1931 Realme UI Android 10

fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Files
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
use vbmeta from this post
Magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
hi, any idea to fix fingerprint?
[email protected] said:
hi, any idea to fix fingerprint?
Click to expand...
Click to collapse
We need to wait for Realme to release a fix, just like what happened on color os when fingerprint wasn't working
On C.27 Bootloader Unlock and Root, Fingerprinter works
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
minoccio said:
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
Click to expand...
Click to collapse
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
deviantor said:
Instal stock recovery like you did to install custom recovery.
Uninstall Magisk with the .zip from their site. Github here
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
So basically if I'm on c27 already, it's okay to use the same root method?
adsubzero said:
So basically if I'm on c27 already, it's okay to use the same root method?
Click to expand...
Click to collapse
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
deviantor said:
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
Click to expand...
Click to collapse
I tried several thins to install Magisk succesfully with no luck.
I received my Global x2 Pro this thursday and i successfully unlocked the bootloader and flashed twrp recovery. But when I flask the magisk 20.4 zip and reboot my device, i get an error saying that my boot / recovery partition is corrupt. I have to install C27 again from twrp and it boots up.
Can anybody help me how to install Magisk succesfully? It's driving me nuts. Also, i cant download the vbmeta.img from the OP. So i tried to extract the vbmeta.img from the c27 image to flash, but also no lucck
Edit: Finally having it working with the Orangefox recovery with the vbmeta.img. I thought that the link in OneDrive wasnt working, but it was my home networks which was blocking OneDrive. Problem solved!
deviantor said:
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
It's possible if someone makes a flashable zip, though I dont know of that can be done for every phone. Otherwise you need a stock recovery to install the OTA.
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
Like @adsubzero said. Unless you have a custom ozip file to flash on TWRP, you need to have stock recovery to install a standard ozip.
ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Click to expand...
Click to collapse
for recovery mean recovery ka option ckick krna hai..vbmeta krty huay
In the backup options I don't see system, only system image. Does anyone else have this issue?

oneplus 6t stuck when i try to flash twrp after msm

so, i had my op 6t bricked and in a bootloop to fastboot
i managed to recover my data through twrp, but couldnt get lineage to run again, so i used the msm tool to downgrade to android 9 oos
now when i try to install a custom recovery i the phone freezes in this "the bootloader is unlocked warning"-screen
no idea why i cant boot into a custom recovery, with a unlocked oem
my plan is to get it back to run lineage os with twrp recovery
can u maybe help me?
I wasn't able to boot into twrp since a11. Had to install from magisk in booted oos using twrp installer. Not sure why it wouldn't work if you downgraded but maybe not using the correct twrp? Sounds like things are messed up. I would start from scratch and get a clean oos on both slots. If you can't boot into twrp then root with magisk and install directly from magisk manager with the installer.
So I am on 11.1.2.2, how do I get twrp installed on this. I cannot get twrp to boot past the logo. I have been trying to Flash HAVOC but have been stuck
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Brettroth said:
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Click to expand...
Click to collapse
Which magisk? latest or canary
Gytole said:
Which magisk? latest or canary
Click to expand...
Click to collapse
I use the latest
and are we talking 3.6.0_9? orr...
Gytole said:
and are we talking 3.6.0_9? orr...
Click to expand...
Click to collapse
Yeah that's the newest. Older ones work but that one has a lot of good changes
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
You need to flash a magisk modded boot in fastboot from your oos. Someone has a post somewhere in here hosting them I'll try to get a link for you.
so fastboot flash boot_a and b like usual for the patched boot image and then once in android just open magisk, then install the latest twrp from there? I think that's what put me in crash dump mode before
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
Are you on 11.2.1.1?
Brettroth said:
Are you on 11.2.1.1?
Click to expand...
Click to collapse
11.1.2.2 I believe?
Gytole said:
11.1.2.2 I believe?
Click to expand...
Click to collapse
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Brettroth said:
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Click to expand...
Click to collapse
Done. Now I boot into android, open magisk, and install the recovery?
Gytole said:
Done. Now I boot into android, open magisk, and install the recovery?
Click to expand...
Click to collapse
Yessir
Brettroth said:
Yessir
Click to expand...
Click to collapse
Work out for ya?
Wow. Alright. You all need to remember this. Msm only flashes to slot a. NOT slot b. So, if you were previously in A10 or A11 and flash msm OOS 9, there will be issues unless you local update the same android version to slot b. You can't have 2 different android version on your slots unless you're using dualboot mod. Like on 8 pro, crashdump happens when twrp is installed if both slots aren't using the same android version

Categories

Resources