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.
I have rooted my phone, installed AdBlock hosts file, and changed the stupid S7 emojis to stock Nougat emojis. now, is there any way I can remove root and replace the kernel back with the original stock kernel, without wiping my phone? so basically I want unrooted just with the mods I made to /system. haven't seen this mentioned anywhere..
xVermicide said:
I have rooted my phone, installed AdBlock hosts file, and changed the stupid S7 emojis to stock Nougat emojis. now, is there any way I can remove root and replace the kernel back with the original stock kernel, without wiping my phone? so basically I want unrooted just with the mods I made to /system. haven't seen this mentioned anywhere..
Click to expand...
Click to collapse
You could... but it wouldn't boot because the bootloader and kernel would detect a customized system partition.
xVermicide said:
I have rooted my phone, installed AdBlock hosts file, and changed the stupid S7 emojis to stock Nougat emojis. now, is there any way I can remove root and replace the kernel back with the original stock kernel, without wiping my phone? so basically I want unrooted just with the mods I made to /system. haven't seen this mentioned anywhere..
Click to expand...
Click to collapse
You can always try. Worst off you have to reflash the system partition as well. I went back to stock system and kernel without wiping the device and everything is working except Samsung Pay, but I think that's because I pin encrypted the boot (which I guess has no plans to support).
To flash just the kernel download your current release from one of the dev mirrors and extract the tar. Re-tar just the kernel (and the system if you want to revert both) and flash in the AP slot. Just as a safety measure, I would enable the "OEM Unlock" in Developer options, but that might not do anything for us.
I am looking to gain root on my new G5 Plus that I just purchased today. I was able to unlock the bootloader. I am looking to try to avoid modifying anything in /system (something that TWRP does by default if I'm not mistaken) and would like to gain root access.
I am unable to do this in TWRP because it is not able to read the internal storage.
I am not able to do this through Magisk because I am not able to find the default boot.img file for patching.
Does anyone have any suggestions?
download the stock rom, and get boot.img file from it.
I got this to work by booting into TWRP, leaving the system read-only, and then flashing Magisk followed by Elemental X 2.02.
Also I used ADB sideload since the internal storage will not mount without formatting the data in TWRP.
Taking OTAs should be super easy by just reflashing the stock boot image.
I'm following the topjohnwu's guide on how to update with Magisk but I do not find it clear enough. Are these the steps I need to take in order to not-brick and update my phone with the Feb update.
1. Uninstall Magisk by "restore images" option.
2. Install OTA
3. Reboot to reinstall Magisk on second slot
Magisk is NOT installed on the second partition! And I prefer not to flash back the original image just to do that. My system should be read only and I do not have twrp, I never had, I updated my Google services framework from apkmirror and I got the update, now how do I apply it without soft bricking?
Update
Step 2 failed, "installation problem". Wtf do I do in order not to lose Magisk or data?
Edit
I've uninstalled Magisk but haven't restarted, hoping to get a solution where I keep my sh*t since that's what the guide said...
Edit 2
I'm reading the other thread but I'm having trouble finding a single useful information there, quote one if you find it, it might be my autism that I don't see a solution in that three pages long thread. Tell me I need to MiFlash this sh*t so I calmly jump through my window instead of wasting the whole night on making it work, then wasting another day on backing my sh*t up.
Edit 3
Fully uninstalled Magisk by instructions of an indian guide. BOOTLOOP.
Note to self, stop following southern asian guides.
Downloaded ROM and MiFlash, flashed flash_all_except_storage.bat.
Shook for 4 minutes until "success" mark, successful reboot.
Edit 4:
follow the regular magisk flash guide https://forum.xda-developers.com/mi-a1/help/how-to-root-mi-a1-february-ota-update-t3757934
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
_mysiak_ said:
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
Click to expand...
Click to collapse
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
A14DWIN said:
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
Click to expand...
Click to collapse
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Dang I really need that command.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Don't bother trying to find it, it exists, I'll make a dedicated thread at some point, thanks for the answer, BusyBox seems logical.
The correct way to install Magisk? I just flash Ranjit's patched img from the official thread on Magisk root, that should be the correct way.
I just use lucky to patch cirtain apps, so that shouldn't be a problem
Right now, I'm giving Magisk root perm to Greenify, Lucky Patcher and Unified Hosts. Also both Greenify and the Unified hosts adblock have their own modules in magisk.
Hopefully I still haven't touched my system partition.
I encountered the error as well after trying the Pixel OTA method. To flash the update successfully, I flashed stock January system and boot img via fastboot and it updated properly after. Then I just patched the stock Feb boot img and went back to fastboot. Once there, i did the fastboot boot command with the patched Feb boot.img so I got root back after updating.
Sent from my Xiaomi Mi A1 using XDA Labs
HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks
cant you flash the ota in twrp and then reflash magisk if needed?
robgee789 said:
cant you flash the ota in twrp and then reflash magisk if needed?
Click to expand...
Click to collapse
Yes, I can do that.
I Know the procedure to flash full zip file via TWRP. Via this toturial: youtube.com/watch?v=oUUzxYHV_ac&t=1s&index=11&list=WL
But i want to know if it is secure to flash, because i used these two applications.
Is there a way to temporarily root my 6p, like kingo root? This is my mother's phone and I don't want root access permanently; I need to edit build.prop. I'm hoping to fix a call quality issue and revert back to non-root, and receive the final OTA updates. I've tried every method I could find, expect disabling noise canceling through build.prop. Thank you for the help
I'm not aware of a temporary root solution for the 6P.
Alternatively, you could flash TWRP via fastboot, reboot to recovery, pull the file via adb, edit, push it back via adb (make sure permissions are correct), reboot to bootloader, and flash stock recovery.
ske1555 said:
Is there a way to temporarily root my 6p, like kingo root? This is my mother's phone and I don't want root access permanently; I need to edit build.prop. I'm hoping to fix a call quality issue and revert back to non-root, and receive the final OTA updates. I've tried every method I could find, expect disabling noise canceling through build.prop. Thank you for the help
Click to expand...
Click to collapse
You could flash TWRP, back up boot.img then flash magisk. After you finish just flash the boot.img then your unrooted. If you want to go back to stock recovery put a copy on your phone and flash it in TWRP. I'm sure theres other ways but this is what I would do.