Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
balleny said:
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
Click to expand...
Click to collapse
1. Settings, system, systemupdate
2. Read the big guide
3. Same as above
4. Same as 2
5. Same as above
6. Omni is good, havoc is good... All depends on your usage, you have to try the roms and decide for yourself.
7. After each rom flash you must flash twrp, then reboot to twrp then gapps then magisk if you want to use custom roms. (A/B partitions, read that info in guide section)
8. You don't flash, you install an apk. Many people like it. Up to you if you will like it. Try, just an apk.
9. For me, they worked from first boot.
10. Probably not, Google has made improvements in security and that's why titanium stopped working on bank aps etc.
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again
itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.
irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.
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