How to install magisk in any lineage os(the easiest way) - Nokia 6.1 (2018) Guides, News, & Discussion

The most easiest way to install magisk in lineage os is to use the stock recovery.
Lots of guides are not showing this,they simply say to install a custom recovery and then flash the magisk.
So for absolute beginners,go to stock recovery,click on apply update and then update from adb,have your pc with you and your phone connected to it via a adb connection and then send the file over adb.Done magisk is installed on your phone.

varun94 said:
The most easiest way to install magisk in lineage os is to use the stock recovery.
Lots of guides are not showing this,they simply say to install a custom recovery and then flash the magisk.
So for absolute beginners,go to stock recovery,click on apply update and then update from adb,have your pc with you and your phone connected to it via a adb connection and then send the file over adb.Done magisk is installed on your phone.
Click to expand...
Click to collapse
From what I've read Android 11 does things differently. Stock recovery I would try if it I can get a matching month/year Security Patch file for boot recovery.

Related

Updating to 9.0.2 on a rooted device

Will there be any incompatibility issues with magisk and xposed?
No problem with rooted device on updating, althought you will get unrooted once you update with OTA.
Also, there is no xposed for Pie.
Not yet faced any issues. After OTA update done don't reboot the device. just come to Magisk manager -> install -> select install after OTA option and reboot so that you won't lose root.
Ok, I will stay on oreo for now then. Does Pie run better than Oreo on stock?
Should've read this **** before updating to Pie.
Currently in a bootloop after going from oreo to Pie :'(
What is the latest version of Oreo I should be able to get to with Xposed on OP6?
I faced some issues. After updating to 9.0.2 TWRP and Magisc were gone. So had to reroot and reinstall TWRP via fastboot.
Yes.. this will ALWAYS happen. if you want to keep root when doing OTA you have to do this after install is done, but before reboot!
open magisk app
press downloads
search for TWRP A/B
Install that module ( :::::...:.:..:...::::O NOT REBOOT:::::...:.:..:...::::
Go to main screen of magisk again
press install
press install to inactive slot (after ota)
NOW you can reboot and all will be kept.
If you do it from TWRP (like i prefer, since its just faster)
Flash full rom
flash Twrp (blu_spark latest)
reboot to twrp
flash magisk (latest)
done.
flashing roms will ALWAYS override recovery and boot partition
If I understand you precisely, you say, that this is a question of OTa roms. I am not very keen for OTA. Would TWRP and Magisk stay when flashing a non-OTA rom? If yes, are there non-OTAs of OOS?
No what I ment was using the update function from within android.
You will ALWAYS override recovery and Magisk. Follow the steps above when you flash..
Always like this from twrp
Flash Rom
Flash Recovery
Reboot to twrp
Flash magisk
And u be good...
OK thanks. I did wrongly to accept the automatic update instead of downloading the zip and install it via TWRP.

Losing TWRP and Magisk after update

I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?

Pie 9 for HTC U11 is out but can't install it - Root -

but I can't install it because my phone is rooted with Magisk and when I install the update TWRP takes over and won't install the Android 9 update. It does something automatically for some time but when it reboots I still have Android 8.
Can I find the Installation file in .zip format and install it manually through TWRP ?
Are there any other ideas ? I tried this Magisk Uninstall - Restore Images and downloaded the Android 9 though the system update without rebooting but when I went back to the Magisk Manager I could not find the install button to continue with the process. I have the latest Magisk and latest TWRP.
stelios_class said:
but I can't install it because my phone is rooted with Magisk and when I install the update TWRP takes over and won't install the Android 9 update. It does something automatically for some time but when it reboots I still have Android 8.
Can I find the Installation file in .zip format and install it manually through TWRP ?
Are there any other ideas ? I tried this Magisk Uninstall - Restore Images and downloaded the Android 9 though the system update without rebooting but when I went back to the Magisk Manager I could not find the install button to continue with the process. I have the latest Magisk and latest TWRP.
Click to expand...
Click to collapse
You just need "Stock Recovery"
I Have bad eng
Your answer is HERE
ALiARies said:
You just need "Stock Recovery"
I Have bad eng
Your answer is HERE
Click to expand...
Click to collapse
Download the Android 8 ruu for your device and rename the zip the usual way.
Put zip on scarf and boot to download mode. It will see the stock firmware and update

[SOLVED] OTA with ROOT...

I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)

Is it possible to pre-root a TWRP image prior to flashing it?

Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Rooting Android OS is adding an user with elevated rights ( comparable to adminstrator in Windows OS ) to it, nothing else.
TWRP recovery does not require a phone's Android is rooted.
lnrdx said:
Hello. I'm trying to flash a TWRP custom recovery on a SM-A305G (Galaxy A30). While reading the official A30's post on the TWRP website, in order to properly flash the custom recovery, they recommend me to first root my device with Magisk (which I understand how to) but THEN flashing a pre-rooted TWRP image for my device. How could this be done?
Related link: https://twrp.me/samsung/samsunggalaxya30.html
Thanks in advance to who could answer this question. Internet hero.
Click to expand...
Click to collapse
That just isn't how it is done, we don't root TWRP, we root the phone's OS. There isn't anything to "root" in or about TWRP because TWRP has the power to modify a device without needing root.
It isn't required, but, it is possible to root a device and then use an app such as Rashr, Flashify or TWRP Manager along with root permissions to flash a TWRP img or even use a Terminal Emulator app with root permissions to install TWRP via dd commands. It doesn't "have" to be done this way, it's just an alternative way to achieve root and flash TWRP on devices that are capable of doing it this way, in this order, not all devices can do it this way.
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
woheller69 said:
I want to have Magisk AND TWRP.
I rooted the phone with Magisk and had Magisk running.
Then installed TWRP app and flashed TWRP with root permission.
Now TWRP is installed but Magisk is gone again.
How can I have BOTH?
Click to expand...
Click to collapse
Flash the Magisk.zip via TWRP just to be sure binaries are installed, then wipe cache and dalvik cache in TWRP then boot into system and install the Magisk Manager app(if it dosen't get installed when you flash the Magisk.zip).
Unfortunately not working.
I installed Magisk via Odin wirh a Magisk-patched stock rom ( Galaxy A10). WORKED
Then installed TWRP via Odin and got TWRP and Magisk working by immediately booting into recovery after flashing.
But then I installed the CrDroid custom rom via TWRP and now Magisk is gone.
[ROM][ARM][OFFICIAL] crDroid 8.x for Galaxy A10 [Android 12]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com

Categories

Resources