Related
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop.
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
Download the deodex rom flash it, then flash no_verity , then format data.
Mastajeff said:
Download the deodex rom flash it, then flash no_verity , then format data.
Click to expand...
Click to collapse
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Decrypt data.
As a general statement : Almost all TWRP bootloops are due to users not backing up their data, and then formatting data.
Hardware encryption is not supported.
Decrypt your data, flash a ROM, and if that ROM doesn't have SuperSU, flash SuperSU.
Go flash my v5 MOD ROM.
Decrypt your data! 95% of TWRP loop cases are due to data not being decrypted, or some other step the user failed to follow.
Good luck.
---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
This is because you went to Advanced Wipe, and formatted /system.
Make sure you are on the latest TWRP, make sure you're data is decrypted, and then go flash my v5 MOD ROM.
For those that are still having troubles. My guide works: forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
Mastajeff said:
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
It's been determined that it does this when it finds an update in the fota and or misc folders. The phone downloads updates even when you tell it not to. It just doesn't install them without your permission.
Easy to get out of with the volume down and power button reset procedure which then deletes the files automatically or you can delete the files in twrp to fix it.
Poda_jj said:
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
Click to expand...
Click to collapse
All the bootloops for the V20 so far are all due to modifications and rooting. There are some roms that work for everyone but just refuses to work on my phone and will just bootloop. I doubt that the cause of the software bootloop is fully known. I've followed directions 100% on working romss and it would bootloop but installed a different version of the same rom and it worked. None of the bootloop "fixes" did anything for me. Fortunately, the rom that I installed is still awesome and works great.
LS997 BTW
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
bond32 said:
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
Click to expand...
Click to collapse
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
dangercl0se said:
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
Click to expand...
Click to collapse
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Team DevDigitel said:
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Click to expand...
Click to collapse
Thanks. I suppose deleting those folders isn't possible without root access?
bond32 said:
Thanks. I suppose deleting those folders isn't possible without root access?
Click to expand...
Click to collapse
yeah MISC and FOTA are protected as read only for the user without root.
Mrsana said:
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
Click to expand...
Click to collapse
Thank you, This Worked for me.
bond32 said:
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
Click to expand...
Click to collapse
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
dangercl0se said:
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
Click to expand...
Click to collapse
Did you try the above where you delete the misc and fota folders?
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.
Anyone know how to root if I'm already on 9.5.6?
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.
The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk
larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions
OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you
With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk
skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi
Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.
I used previous Oneplus devices like 5t and 6t. And did root and used for almost 2 years. And I loved that feel.
Recently I brought op7pro 12gb variant.
After one day, I thought to root and install Havoc OS.
So, I followed root method for op7pro. After fastboot boot <image>
I wiped all the partitions like, system, vendor, data, internal etc...,
After the reboot. I am unable to boot my phone.
Not even I can go to fastboot to install stock ROM. Anyhelp?
I made mistake by wiping system partition.
Anyhelp how to recover ?
aswathsaru said:
I made mistake by wiping system partition.
Anyhelp how to recover ?
Click to expand...
Click to collapse
Then you have to use msm tool to recover and it locks your bootloader.
---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------
https://androidfilehost.com/?fid=6006931924117884115
Download this file
Follow this thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I tried the steps. But unable to detect in the msmtool.
Tried several times
Fixed
Thanks Folks, I tried global Recovery via MSMtool but not sure why it doesnt worked.
Then Tried with European rom and then it worked.
Hello all,
I tried updating to OOS10 using the method listed elsewhere in the forums; install the OTA without rebooting, install the TWRP recovery script in magisk, install magisk to inactive slot, reboot. I then ran into a black screen where all I could do was reboot/turn off the phone. So I rebooted into TWRP and tried getting rid of Swift installer/magisk just in case they were causing problems. That seems to have pretty much bricked my device, so I'm in the process now of reinstalling OOS from scratch.
I'm able to get into TWRP, but it's unable to mount /data. I have a ton of Titanium backups/SMS backups on my internal storage which I'd really like to get pulled off before going any farther. Is there any hope?
Thanks!
Try install new twrp version unofficial q
---------- Post added at 09:59 AM ---------- Previous post was at 09:25 AM ----------
Install latest unofficial twrp
Purplezigar said:
Hello all,
I tried updating to OOS10 using the method listed elsewhere in the forums; install the OTA without rebooting, install the TWRP recovery script in magisk, install magisk to inactive slot, reboot. I then ran into a black screen where all I could do was reboot/turn off the phone. So I rebooted into TWRP and tried getting rid of Swift installer/magisk just in case they were causing problems. That seems to have pretty much bricked my device, so I'm in the process now of reinstalling OOS from scratch.
I'm able to get into TWRP, but it's unable to mount /data. I have a ton of Titanium backups/SMS backups on my internal storage which I'd really like to get pulled off before going any farther. Is there any hope?
Thanks!
Click to expand...
Click to collapse
I'm not sure if this can helps you but take a look before you flashing the stock rom
https://www.wondershare.com/android...36.1875208451.1572365092-140189568.1572365092
I have no idea how, but somehow I fixed it. I ended up using fastboot to switch the active slot, the booted into the new Q TWRP, flashed the OTA update from one of the other forum posts, then flashed Magisk and I was able to boot. I had to reflash TWRP and Magisk again after getting booted up, but after that everything was good again. Very weird.
Nice... I think it's time to get a backup your data and save it for example to your pc,or in external disk ...
Hi,
I have a rather odd problem:
My phone simply does not boot when Magisk is installed
Installed Magisk 20.0 on Stock 10.0.1-GM21BA a while ago and everything was fine.
Today it won't boot any more (stuck on the warning that my bootloader is unlocked, then bounces to fastboot)
As soon as I uninstall Magisk from TWRP it boots again
Then I Install Magisk 20.1 from TWRP, it does not boot.
Then I uninstall Magisk 20.1 from TWRP, it boots again
Then I flash the pre-patched boot image from here and it does not boot again
Then I flash the stock boot image from here and it boots again
I also tried installing Magisk without dm-verity (only forceencrypt), still not booting beyond unlock warning and fastboot
Does someone know what is going on with my phone
Can I root it without Magisk?
Thank you for any help
Try TWRP 70
Maybe you're on twrp v71... Try reverting to the older v70
had same problem.i reflashed stock and locked bootloader back to offical, andriod 10 lets twrp work but not masgik. i even used magisk manager to patch file and flashed that file to have no more root
NateDev said:
Try TWRP 70
Click to expand...
Click to collapse
santiagoruel13 said:
Maybe you're on twrp v71... Try reverting to the older v70
Click to expand...
Click to collapse
Thanks for the ideas, did not fix it unfortunately
Guess I will stay without Magisk for now
do you have any modules hanging out?
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
you could try that.
Hmm.
Try this with twrp v70
1. Boot to twrp
2. Flash the full a10.0.1 rom
3. Flash twrp v70
4. Reboot to twrp
5. Flash magisk v20.
Reboot
Thats what i do if something is wrong.. i always reflash a rom..
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Re flashing a rom also saved my friend's phone..after flashing boot.img for rooting purposes..he always boot without a wifi. So we dirty flash a rom.first . Then using that same rom that we flashed.. we extrscted its boot.img then patched it with magisk. Then re flashed.. then boom.. its working now..
Reflashing the full a10.0.1 rom.solved the issue..
---------- Post added at 07:24 AM ---------- Previous post was at 07:22 AM ----------
My idea here is that
Flash the rom..
Then using the rom that you just flashed..
Get its boot.img.. then patch it then flash it again.. it will now boot. I havent tried directly flashing a patched boot.img without reflashing the rom first..
I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system
coolguy001 said:
I met the same problem this morning. Did the following thing to let phone boot with magisk.
1. install magisk 74
2. install Magisk-uninstaller-20200110.zip
3. reboot magisk
4. install magisk-v20.3.zip
5. boot system
Click to expand...
Click to collapse
do you mean in step 1, Magisk Manager v7.4.0
Did anyone figure out how to fix this issue? I have tmobile and after updating to 9.5.5 and installing magisk it works until I reboot again and then it hangs and goes to fastboot. I try to narrow down the problem and it happens after I install adaway maybe after I choose system less. Or after installing YouTubevanced. Idk what I'm doing
Did anyone find a fix to this ? I'm having the exact same issue.
Flashing magisk 20.4 gives a bootloop. Uninstalling via TWRP allows me to boot to system. No overlays no modules etc,everything uninstalled but still cant boot with magisk. Have I missed something? The only solution I can find is factory reset and begin again, which I can do but as a last resort.