Related
Can you use Android Q on the pixel A along with rooting?
sillyshyme said:
Can you use Android Q on the pixel A along with rooting?
Click to expand...
Click to collapse
Unfortunately, not. The pixel 3, 3a as well as the xl versions of both currently do not have magisk for Android q. The dev is working on it though. Keep your ear to the ground
Sent from my Pixel 3a using Tapatalk
Yes. The Pixel 3/3a versions use logical partitions in the Q beta. and it sounds like it's taking a major re-write to support it. I believe it is called system-as-root. The developer John Wu has been posting about it on Twitter. https://twitter.com/topjohnwu
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
12paq said:
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
Click to expand...
Click to collapse
It's pushed to the Cannery build https://twitter.com/topjohnwu/status/1144159892430659584
Magisk and TWRP all in the same day!
@pharpe wait TWRP got released?
Tiebe said:
@pharpe wait TWRP got released?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413
did any one successfully root q ?
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
Yeah, can confirm, did this earlier today!
Just a question, did you have the issue that many apps show up in the appdrawer of pixel launcher, even if they shouldnt? (like Google PDF Reader, Sd Maid unlock or sideloaded Pixel livewallpapers etc.)
I guess its because of the bootloader is unlocked (for security reasons)?! Just really weird. No other issues observed till now.
peace!
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
removed
pharpe said:
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
Click to expand...
Click to collapse
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
bejunk said:
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
Click to expand...
Click to collapse
Interesting. I never realize that. I keep all my apps organized in folders so I only go to the app drawer for things I rarely use. I just assumed everything that was installed was in there.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
c_tho said:
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
Click to expand...
Click to collapse
That is my understanding from what I have read but I have not actually done it. You would uninstall via Magisk and it restores the original boot.img that it has backed-up. Then you are back to stock to take the OTA.
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
I have a Twrp backup with the boot img patched with Magisk/Twrp boot to recovery boots GSI with magisk boot to recovery hold volume up while rebooting to recovery will boot twrp for this boot img to work u have to be on the vendor of the boot img which is also in the backup so the phone won't bootloop this vendor is modified to work with GSIs pass the magisk environmental setup and notch fix so swiping down is like swiping down on stock.... to implement notch fix go to developer settings hide display cut and choose the first hide option and your notch will be fixed...
Thanks @Spaceminer for the twrp for without this none would of been possible
please note twrp will only boot with a android 9 vendor and your GSI will only boot with magisk and twrrp with the vendor in the backup cause it matches the boot img, GSIs only boot when the vendor and boot img match
the boot img & vendor img in the backup is from Channel/Retail (PPY29. 105-160-4)
Instructions
If on android 9 stock
1. Boot to bootloader
2. fastboot - w
3. fastboot GSI of your choice
4. fastboot boot twrp.img
5. format data
6. Place the twrp folder you downloaded from the zip into your devices internal storage which will be available after u format data
7.Resize system
8.Flash gapps zip if gapps is needed
9.wipe dalvick
10. go to twrp restore boot and vendor
11. reboot to recovery and phone will boot after boot is complete install magisk manager it will do the environmental setup phone will reboot and u will have magisk.... ( if u want the best experience with magisk on this device I recommend that you use havoc cause with the lineage GSI magisk doesn't play nice but with havoc its stable also when making a backup it's boot, system image, vendor image, data if u chose system instead your backup will bootloop your device upon restoration)
Download (twrp img is in twrp folder remove it and place it in ADB folder)
https://mega.nz/file/7t03DLhL#jjS9vgrJMlDS-_-hsApyx4uJ6L8wXCN8HtjSqJrg2ds
if u wanted to do this manually to install the latest canary or stable version magisk need to patch twrp to the recovery flash phh root boot up install magisk manager give it root permissions with phh superuser from apk mirror now with elevated permissions the option patch directly will be avaliable cause u got root (it's the recommended option ?) chose recovery and leave the other 2 unchecked patch the img and reboot to recovery the phone will reboot os with magisk and u hold up while booting recovery will boot twrp after that backup that boot img in twrrp for future installation of the GSI of your choosing....
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
xcode22 said:
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
Click to expand...
Click to collapse
Everytime u flash a GSI just use the vendor and boot from the twrp folder and your android 10 GSI Will have magisk and twrp no need for data disabler zip cause my backup already has the vendor and boot patches enabled for decryption so twrp will be accessible via boot to recovery
([emoji88]Havoc GSI[emoji88])
Also have edxposed for Android 10 since the one in the repo won't work cause it needs a custom magisk with merged patches for xposed to work on android 10 this version has the patches in the edxposed so having to use a custom magisk won't be an issue cause as ya know obtaining magisk and twrrp in this device was unknown into this OP was made
([emoji88]Havoc GSI[emoji88])
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
xcode22 said:
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
Click to expand...
Click to collapse
Your on a GSI go in your system settings and activate advance boot and when u have to reboot just put reboot to recovery and you don't have to worry about manually rebooting to recovery everytime u have to reboot also no way u installed the rom to the recovery partion our device doesn't have a recovery partion the recovery lives within the boot img
([emoji88]Havoc GSI[emoji88])]
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
xcode22 said:
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
Click to expand...
Click to collapse
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
PoochyX said:
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
Click to expand...
Click to collapse
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
PoochyX on telegram dm me I walk you threw it
([emoji88]Havoc GSI[emoji88])
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
The easiest way I know of is from the stock OS using termux and root.
Code:
su
setenforce 0
mkdir /mnt/x && chmod 0755 /mnt/x
mount -o loop /dev/block/by-name/vendor_a /mnt/x
Now navigate to /mnt/x and everything from vendor will be in there. Find the file and delete it with a root explorer. Then unmount the partition and the changes will be permanent. Doing it this way gets around FEC, which is what prevents you from changing anything in vendor.
Code:
umount /mnt/x
If you need to work on the other vendor partition just change out vendor_a with vendor_b
Any recommendation about what GSI to choice for XT1952-6 variant?
mickem said:
Any recommendation about what GSI to choice for XT1952-6 variant?
Click to expand...
Click to collapse
Chaos GSI Bluetooth works without disabling audio effects (so u can use viper with bluetooth headset) it's clean stock with minimum stuff added to it and works with gravitybox then you got havoc that has the majority of stuff gravity has off the rip so it's not as minimum so more memory usage is needed and Bluetooth only works with the phh disable audio effects work around also magisk works good on both of these lineage is good also if you don't care about magisk working cause with our device magisk has issues on lineage don't know if it was fixed on a recent bulid however if lineage is your preference there is a phh root for it so u can be functional
([emoji88]Havoc GSI[emoji88])
My device is xt1952-4. I downloaded the latest firmware (PPYS29-105-160-4-8), and installed it to both slots. I am currently using Resurection Remix Pie. Is your patched boot.img and vendor compatible with the newer firmware or will I get a downgrade error?
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
[16/01/22] lineage-18.1-20220116 patched boot images
[09/01/22] lineage-18.1-20220109 patched boot images
[02/01/22] lineage-18.1-20220102 patched boot images
[26/12/21] lineage-18.1-20211226 patched boot images
[19/12/21] lineage-18.1-20211219 patched boot images
[12/12/21] lineage-18.1-20211212 patched boot images
[05/12/21] lineage-18.1-20211205 patched boot images
[28/11/21] lineage-18.1-20211128 patched boot images
[21/11/21] lineage-18.1-20211121 patched boot images
[14/11/21] lineage-18.1-20211114 patched boot images
[07/11/21] lineage-18.1-20211107 patched boot images
[31/10/21] lineage-18.1-20211031 patched boot images
Reserved
Thanks bro
intp.pisces said:
Thanks bro
Click to expand...
Click to collapse
You're Welcome , hope you found it useful.
Backstab319 said:
[31/10/21] lineage-18.1-20211031 patched boot images
Click to expand...
Click to collapse
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
sandeep_kumar said:
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
Click to expand...
Click to collapse
Hi, i would recommend installing the update from the native updater, that takes care of most of the things for you out of the box.
After you install the update keep the patched bootimage in a directory that's easily accessible on your pc. Then follow the below instructions (Make sure your device is connected via adb),
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
And you are done, once booted up you will see that magisk root status is back and all your previously installed magisk modules and xposed modules work as before the update.
Thanks
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Magisk canary removed magisk hide and the list of modules. Stick with magisk v23 stable to get magisk hide and module list.
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Backstab319 said:
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Click to expand...
Click to collapse
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
NoSauce said:
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
Click to expand...
Click to collapse
Yes, its the boot.img extracted from each of the lineageOS nightly release.
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Backstab319 said:
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Click to expand...
Click to collapse
Yes. Better to switch to Magisk 24.1 after everything gets fixed. For now V23 has no issues.
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Backstab319 said:
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
Click to expand...
Click to collapse
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
barcia99 said:
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Click to expand...
Click to collapse
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Backstab319 said:
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Click to expand...
Click to collapse
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
barcia99 said:
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
Click to expand...
Click to collapse
Oh, i had the same scenario. Tried installing 24.1 didn't work, tried rolling back to 23. But sadly rolling back from 24 to 23 caused bootloop for me as well. I ended up flashing the rom again (fresh) and then it started working.
What's the best way, to install root with magisik on an a52q device?
The manual at https://topjohnwu.github.io/Magisk/install.html seems to describe how to install root with the official Samsung OS, but not with LineageOS?
And how can I update LineageOS regularly with staying root persistent?
Thanks!
redcarholder said:
What's the best way, to install root with magisik on an a52q device?
The manual at https://topjohnwu.github.io/Magisk/install.html seems to describe how to install root with the official Samsung OS, but not with LineageOS?
And how can I update LineageOS regularly with staying root persistent?
Thanks!
Click to expand...
Click to collapse
LineageOS, at least the PHH builds, already have root built in. Just install the Magisk app.
V0latyle said:
LineageOS, at least the PHH builds, already have root built in. Just install the Magisk app.
Click to expand...
Click to collapse
When I install the Magisk app, it says:
Installed: N/A
Zygisk: No
Ramdisk: Yes
When pressing the Install button, I'm asked for selecting and patching a file.
What I'm doing wrong? I use this manual: https://wiki.lineageos.org/devices/a52q/install
Flash Magisk in TWRP. No need to rename the extension, TWRP will flash apks.