Ho there! I just stumbled upon this magisk module that, correct me if I'm wrong, lets you keep the TWRP installed after installing an OTA.
Has anyone tried it on OP Nord?
Well, at the time being is pretty useless since we don't have a functional custom recovery under Android 12
But anyway....
I'm wondering if it works on oneplus 6t also?
But without TWRP A/B retention script on Magisk anymore I'm wondering is it still possible to update without losing root,data and twrp??
Related
I have a google pixel recently rooted with Magisk and have TWRP. My system is informing me of a system update, and it says Couldn't install update. I've seen people suggesting using FlashFire to flash a factory image of the update, then install Magisk right after that. So how would i go about it? can i do just that? is it possible to update that way? can i flash both magisk and twrp after flashing the factory image? thanks in adv
https://forum.xda-developers.com/showpost.php?p=75480639&postcount=3
Try this
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2. A little less than 3 minutes at this speed.
https://photos.app.goo.gl/Ck70tezbKVvbBCjs2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this, or search for and read the appropriate posts for uninstalling Magisk and installing the correct version in order to use FlashFire under 8.1.
Since i got my oneplus 6 i've had magisk and twrp running on it, the last few times the os has updated i get a bootloop wich i've managed to get out of in the past by running magisk remover and reinstalling magisk, although i confess to stumbling my way through that and do not seem to be able to reproduce the effect this time, i'm currently running oxyOS 9.0.7, no magisk and twrp blu spark, any help would be greatly appreciated in getting magisk back on my phone without bootlooping again.
the current version i should be running is 19.3
paul0909 said:
Since i got my oneplus 6 i've had magisk and twrp running on it, the last few times the os has updated i get a bootloop wich i've managed to get out of in the past by running magisk remover and reinstalling magisk, although i confess to stumbling my way through that and do not seem to be able to reproduce the effect this time, i'm currently running oxyOS 9.0.7, no magisk and twrp blu spark, any help would be greatly appreciated in getting magisk back on my phone without bootlooping again.
the current version i should be running is 19.3
Click to expand...
Click to collapse
After updating OOS you need to re-flash TWRP (stock recovery after OOS update), then Magisk.
What Magisk modules are you using? Most likely the issue if you did what I mentioned above (unclear from your post.
Not many modules, vanced youtube, a call recorder, i honestly can't remember the others, when i get this fixed I'll tidy it up.
To be honest I only wanted magisk for YouTube vanced and installed it before I knew there was a non root option.
PS, I did flash TWRP then magisk, it's been working since I got the phone the week they came out, but the last 2 or 3 software updates have not been smooth like they used to and I get a bootloop
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
matusala said:
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
Click to expand...
Click to collapse
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Horgar said:
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Click to expand...
Click to collapse
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
matusala said:
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
Click to expand...
Click to collapse
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Horgar said:
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Click to expand...
Click to collapse
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
jackdubl said:
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
Click to expand...
Click to collapse
Magisk is systemless root maybe that's why it did that.
matusala said:
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
Click to expand...
Click to collapse
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Horgar said:
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Click to expand...
Click to collapse
Have you tried just booting twrp instead of flashing it?
jackdubl said:
Have you tried just booting twrp instead of flashing it?
Click to expand...
Click to collapse
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Horgar said:
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Click to expand...
Click to collapse
I seem to remember getting some strange messages while flashing Magisk, like it couldn't mount system or something. It was in red. It seemed bad but it also came after successfully flashing Magisk, so it said. Everything was working fine after I rebooted. All root apps working as normal.
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
jeffritz1 said:
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
Click to expand...
Click to collapse
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
junglism93 said:
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
Click to expand...
Click to collapse
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
is rooted Magisk on Android 10 or 11 with Pixel 1 possible?
jeffritz1 said:
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
Click to expand...
Click to collapse
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
YogaSlackers said:
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
Click to expand...
Click to collapse
Hey, almost a week late but hope it's still helpful. Yes I recommend the official 10 firmware with Magisk, flashed through a temporary TWRP.
I've been running this setup for months, I can use all my root apps, even Google Pay and Netflix no problem.
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Thank you so much for your suggestion, and reply. Magisk and TWRP were up to date (the latest releases); Magisk v20.1, and TWRP 3.3.1.2 ("Enchilada"). My device is a OnePlus 6 running Android 9, last updated August 1st of this year, "ONEPLUS A6003_22_190911"
I will try your suggestion and respond as soon as possible. If there is anything else you need to know, ask. I am new to the concept of forums so I've been kinda flopping around like a fish out of water. :laugh:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Hello, just wanted to update you. I am happy to report your suggestion worked. Sadly I still lost my data, but that's alright; all the important bits were already backed up. Just lost the home screen layout and some application settings. All the same, I am now successfully running my rooted device and couldn't be happier! Thanks! :laugh::good:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
Hey, I'm in a similar situation you were in and I'm stuck in a bootloop after I flashed/installed busybox from magisk repo, I wanted viper 4android as well and while installing viper it said that I'd need busybox. Soon after I install busy box from magisk I'm in this bootloop, i have access to twrp luckily and i tried deleting this busybox and viper 4android module from twrp file manager but still I'm in a boot loop, can you guide me on how you managed to get out of this bootloop?? Thanks
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
I'm also wondering if I've edited the build prop in any way with the build prop editor, will this cause a boot loop or will a full ota zip return it to normal anyway?
Thanks
Bxperiaz3 said:
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
Click to expand...
Click to collapse
the typical and safe route to take an OTA and keep your root is:
download OTA using oxygen downloader app
Use the sytem update app to install the file above using the local upgrade option. DO NOT REBOOT.
Use magisk to install the twrp a/b keeper script. DO NOT REBOOT.
Use magisk to install magisk to the inactive slot. Then reboot.
I have the gm1913 phone which is a different variant, but I'm sure that the concept is the same.
Good luck.
Thanks for the reply. Did something similar to this
What I ended up doing incase anyone else needs to know..
Disable all magisk modules and reboot
Flash full update from local storage
Don't reboot
Go to magisk and flash twrp zip
Don't reboot
Flash magisk zip to separate slot (ota option)
Now phone reboots its self
Re enable modules in Magisk
Reboot
Profit