Is it possible to use Magisk with this root method on the s7?
Nope
Ok, another question. According to the root guide, the root enabled boot image is what causes the lag. Therefore after root, why can't we Odin flash just the official bootloader? Does root require it's own boot image to function?
bart77 said:
Ok, another question. According to the root guide, the root enabled boot image is what causes the lag. Therefore after root, why can't we Odin flash just the official bootloader? Does root require it's own boot image to function?
Click to expand...
Click to collapse
Yes or you will get verity errors.
OK, can you explain verity error? What if I customize my rom to my liking, unroot then flash just stock boot image. In my case I don't need root if I can enable vzw Hotspot, call recording and disable some bloat all the while preventing lag.
More or less the best of both.
bart77 said:
OK, can you explain verity error? What if I customize my rom to my liking, unroot then flash just stock boot image. In my case I don't need root if I can enable vzw Hotspot, call recording and disable some bloat all the while preventing lag.
More or less the best of both.
Click to expand...
Click to collapse
Any changes to system and boom no booting stock kernel
Related
I've been reading a lot of threads with a number of different ways to upgrade to MM on a rooted phone. Anywhere from restoring back to stock to take the OTA to flashing one of the files in this thread http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am currently running LP 5.1.1 unlocked BL, rooted, xposed installed.
Couldn't I just unroot, flash stock recovery and the system img and accept the OTA? DO I have to return to full stock? Also is systemless root the only way to root after you take the OTA?
Sorry be there is so much information going around I just want to make sense of the update process.
AndKacz said:
I've been reading a lot of threads with a number of different ways to upgrade to MM on a rooted phone. Anywhere from restoring back to stock to take the OTA to flashing one of the files in this thread http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am currently running LP 5.1.1 unlocked BL, rooted, xposed installed.
Couldn't I just unroot, flash stock recovery and the system img and accept the OTA? DO I have to return to full stock? Also is systemless root the only way to root after you take the OTA?
Sorry be there is so much information going around I just want to make sense of the update process.
Click to expand...
Click to collapse
You can probably just flash stock recovery and system.img and accept the OTA.
Systemless root isn't the ONLY way to achieve root on MM, but using the traditional (/system) root method requires a modified kernel to set SELINUX to permissive. For now, it looks like systemless is the way to go.
Good Luck.
samwathegreat said:
You can probably just flash stock recovery and system.img and accept the OTA.
Systemless root isn't the ONLY way to achieve root on MM, but using the traditional (/system) root method requires a modified kernel to set SELINUX to permissive. For now, it looks like systemless is the way to go.
Good Luck.
Click to expand...
Click to collapse
Is there an advantage of systemless root over the traditional? And I am guessimg since I have SuperSu installed I will still need to do a complete restore to stock.
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
I ever read how root and unroot with magisk, but it must download and reflashing stock rom to unroot it.
Is there a more simple way to unroot MI A1?
As simple as choose menu > unroot
I really want root my phone, but only after I found simple way to unroot it again.
Thanks
mrtbb said:
I ever read how root and unroot with magisk, but it must download and reflashing stock rom to unroot it.
Is there a more simple way to unroot MI A1?
As simple as choose menu > unroot
I really want root my phone, but only after I found simple way to unroot it again.
Thanks
Click to expand...
Click to collapse
Why? At the very least you will need to uninstall via a flashable ZIP, but this will still mean the dm-verity is probably disabled and the bootloader is unlocked. Any half decent app which detects root will also detect these, and without MagiskHide they will be even more easily detected.
I thought there is a option to un-root phone in Magisk manager with restoring stock boot image.
CosmicDan said:
Why? At the very least you will need to uninstall via a flashable ZIP, but this will still mean the dm-verity is probably disabled and the bootloader is unlocked. Any half decent app which detects root will also detect these, and without MagiskHide they will be even more easily detected.
Click to expand...
Click to collapse
I think I just too lazy too reflashing, beside bricked risk.
TrueMS said:
I thought there is a option to un-root phone in Magisk manager with restoring stock boot image.
Click to expand...
Click to collapse
Yes this option used to update OTA too, but I dont know if it is really restoring stock and unroot or not
----
I think I will root my phone with magisk and hoped not need to unroot again
Hey everyone,
I tried installing magisk 16.0
firstly i did ,
unlocked bootloader,
then installed twrp recovery 3.2.1
booted the phone installed magisk manager,
then again in twrp recovery
i tried flashing the magisk 16.0,the magisk gets flashed but the phone does not boot up to system,
i dont get what mistake i am doing,
i want to use the 'CAMERA2 API' on my moto g4 plus,
and nothing else
But they say you need to root for that,
so i am trying
Please help me with this...
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
thorin0815 said:
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
Click to expand...
Click to collapse
Thankyou I'll try this also..
echo92 said:
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
Click to expand...
Click to collapse
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
PushkarajK said:
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
Click to expand...
Click to collapse
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
echo92 said:
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
Click to expand...
Click to collapse
Yes got it ,thankyou for the help:good:
I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike
resarfekim said:
I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike
Click to expand...
Click to collapse
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.
madbat99 said:
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.
Click to expand...
Click to collapse
I suspected as much, thanks for confirming.