Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.
vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?
Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.
Related
I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?
Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info
Ty for now I'll wait
same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great
Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks
On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16
Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.
Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...
Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
TWRP INSTALLER FOR REDMI 8
I want to share my tool for installing TWRP for Redmi 8.Tested on MIUI 11 Global 11.0.10.0 (PCNMIXM). Always take a backup of your data before doing this modifications. I'm not responsible if something went wrong and do it at your own risk!!!
About this tool:
Includes Official TWRP for Redmi 8
Includes ADB and Fastboot
Easy to Use
Files:
TWRP Installer for Redmi 8 - https://androidfilehost.com/?fid=8889791610682873743
Magisk Zip - https://magisk.me/zip/
How to Install TWRP & Root:
Unlock the Bootloader.
Connect your phone with USB cable and put the Magisk zip file to your internal or SD Card
Turn off your device and reboot into fastboot by pressing Vol down and Power button
Extract the TWRP installer zip file
Open TWRP_Installer.bat
Press Enter to proceed
Then press any key to install the TWRP and wait to finish
Press any key again , it will automatically boot into TWRP
Go to Install
Find the Magisk Zip File then flash
Reboot and your done
Congratss!!! You successfully install TWRP and Root your Redmi 8
Notes:
You need to Flash the Magisk after you install the TWRP. So that it will not back to stock recovery and the TWRP is now your permanent recovery.
You can also change the TWRP that I use on this tool. Go to the installer folder and delete the recovery.img then paste the recovery that you want and rename it to "recovery.img"
Credits:
XDA
Xiaomi Redmi 8 Developers
TWRP
Google
THANK YOU FOR USING MY TOOL!!! HAVE A NICE DAY AND GODBLESS
I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?
GreenGremlim said:
I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?
Click to expand...
Click to collapse
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app
MattPRZ said:
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app
Click to expand...
Click to collapse
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.
GreenGremlim said:
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.
Click to expand...
Click to collapse
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
When I first install the magisk , I wait couple minutes and then the magisk manager appears
MattPRZ said:
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
Click to expand...
Click to collapse
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed
GreenGremlim said:
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed
Click to expand...
Click to collapse
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.
MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
GreenGremlim said:
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.
Click to expand...
Click to collapse
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.
GreenGremlim said:
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.
Click to expand...
Click to collapse
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version
MattPRZ said:
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version
Click to expand...
Click to collapse
Installed latest magisk manager, it shows magisk not instaled.
GreenGremlim said:
Installed latest magisk manager, it shows magisk not instaled.
Click to expand...
Click to collapse
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
Ok will try that, thanks.
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
GreenGremlim said:
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.
Click to expand...
Click to collapse
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?
GreenGremlim said:
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?
Click to expand...
Click to collapse
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global
MattPRZ said:
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global
Click to expand...
Click to collapse
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.
GreenGremlim said:
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.
Click to expand...
Click to collapse
Try other magisk version
MattPRZ said:
Try other magisk version
Click to expand...
Click to collapse
Any particular version in mind?
GreenGremlim said:
Any particular version in mind?
Click to expand...
Click to collapse
Try the lower versions like 20.3 , 20.2 and others
Would I just download the old zip file from johnwu github and install it on Magisk manager?
qman66 said:
Would I just download the old zip file from johnwu github and install it on Magisk manager?
Click to expand...
Click to collapse
That depends. If you are on Android 11, 20.4 won't work. You'll need to use 21.2. If you are on Android 10, you can flash the old zip in TWRP.
Lughnasadh said:
That depends. If you are on Android 11, 20.4 won't work. You'll need to use 21.2. If you are on Android 10, you can flash the old zip in TWRP.
Click to expand...
Click to collapse
I'm on 10. Don't have twrp. Couldn't get that set up. It can't be done through the manager?
qman66 said:
I'm on 10. Don't have twrp. Couldn't get that set up. It can't be done through the manager?
Click to expand...
Click to collapse
I don't exactly remember, but I don't think there is an option in Manager to flash a zip, only to download a zip, patch a boot image or direct install.
EDIT: You can also try to find the json for 20.4 on Github and then set a custom channel using that and then do a direct install.
qman66 said:
I'm on 10. Don't have twrp. Couldn't get that set up. It can't be done through the manager?
Click to expand...
Click to collapse
On Android10 and without TWRP, I downgraded to 20.4 via custom update!!
Watch this video:
It is not very friendly video, but it works.
My phone is galaxy s9 ,Android 9
Which method is suitable to downgrade magisk ?
I need the url for v20.4
Thx
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Problem solved. The hidden magisk just renamed it to magisk...
What?
Renaming magisk solves problem?
Did u mean rename apk file
My problem is magisk not detecting rooted boot.img or recovery.img that i ve flashed to my device
Wait, what.. I thought I replied to another post. Sorry
MasterGmind said:
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Click to expand...
Click to collapse
Which magisk version?
Selvam_2568 said:
Which magisk version?
Click to expand...
Click to collapse
Here is the solution...(It will work for all magisk versions)
1.Uninstall magisk manager.
2.Reboot to twrp recovery. Then Advanced > File manager > /data/adb/
3.Delete the "adb" folder which present inside the /data.
4.Restore stock boot.img
5.Now flash magisk via recovery...it will work now.