Related
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(
MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs
I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.
Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
I was able to directly install Magisk 17.1 from Magisk itself without issues.
SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop
MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?
Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..
Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine
Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now
I updated my device to the last pie version (10.0.0.3); a former version of Magisk was completely uninstalled before. Then I did a backup of my boot.img via TWRP I booted temporarily. But when I patched this boot.img via Magisk Manager 18.0 and installed and booted the patched_boot.img it ended in a bootloop; only the screen with "android one" was visible and then it stopped. When I flashed back the boot.img and booted again everything worked fine again. A strange fact is that the boot.img has 64 MB, but the patched_boot.img only 16 MB. Any help would be greatly appreciated!
Keep stock boot.img installed, boot into TWRP, install Magisk from TWRP, reboot.
_mysiak_ said:
Keep stock boot.img installed, boot into TWRP, install Magisk from TWRP, reboot.
Click to expand...
Click to collapse
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
ForTheOne said:
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
Click to expand...
Click to collapse
I was afraid this would happen so I didn't try it. I think the Magisk patching routine is somewhat faulty on our device - see the massive difference in size of the boot images I mentioned.
zapper19 said:
I updated my device to the last pie version (10.0.0.3); a former version of Magisk was completely uninstalled before. Then I did a backup of my boot.img via TWRP I booted temporarily. But when I patched this boot.img via Magisk Manager 18.0 and installed and booted the patched_boot.img it ended in a bootloop; only the screen with "android one" was visible and then it stopped. When I flashed back the boot.img and booted again everything worked fine again. A strange fact is that the boot.img has 64 MB, but the patched_boot.img only 16 MB. Any help would be greatly appreciated!
Click to expand...
Click to collapse
The size difference is normal, compressed boot image is 16MB while not compressed is 64
If you zip a 64 MB boot image, it will be 16 mb
zapper19 said:
I was afraid this would happen so I didn't try it. I think the Magisk patching routine is somewhat faulty on our device - see the massive difference in size of the boot images I mentioned.
Click to expand...
Click to collapse
I have rooted via the same method. I didn't face any problem. The size difference is also normal.
ForTheOne said:
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
Click to expand...
Click to collapse
How did you uninstall the previous Magisk version? I guess that incompatible Magisk module is the culprit here. Do the full uninstall with Magisk uninstaller in TWRP and install it again.
_mysiak_ said:
How did you uninstall the previous Magisk version? I guess that incompatible Magisk module is the culprit here. Do the full uninstall with Magisk uninstaller in TWRP and install it again.
Click to expand...
Click to collapse
Thanks, this worked perfectly. These are the steps which worked for me:
Flashed the uninstaller.zip from this page --https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rebooted and installed Magisk Manager apk
Patched the stock boot image via Magisk app using "Patch boot Image"
Flashed the patched boot image via fastboot
Success!! Phone is rooted.
Let me know if you face any issues by this method @zapper19
ForTheOne said:
Thanks, this worked perfectly. These are the steps which worked for me:
Flashed the uninstaller.zip from this page --https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rebooted and installed Magisk Manager apk
Patched the stock boot image via Magisk app using "Patch boot Image"
Flashed the patched boot image via fastboot
Success!! Phone is rooted.
Let me know if you face any issues by this method @zapper19
Click to expand...
Click to collapse
Worked like a charm - thank you! :laugh: Strange: I uninstalled Magisk via the Magisk Manager before I updated to Pie, but maybe there were some relics that prevented the new patched image from booting.
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Use magisk uninstaller in twrp. Then flash magisk 19.4 canary.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
yes i always follow these steps, 3.2.3 twrp
MoHed said:
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Click to expand...
Click to collapse
I did as you suggested and had the same issue stuck at oneplus circles. I then tried to flash 18.1 it made me boot back into the system but root not working just magisk manager with just 2 options, in the menu side, settings magisk and settings.
Then I would try to start from scratch.
Means wipe everything, flash full OOS and then magisk.
@Shady282
Have you got it fixed? I am in the same situation and its frustrating that I am still unable to get root.
Tried flash magisk 19.4 canary no success. Still stuck in bootloop.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
a4abbas said:
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
Click to expand...
Click to collapse
Hmm sorry, do 't remember.
I guess it was the latest Twrp at that time, I switched to op7 non-root for a while now...
the 6t was derooted and given to my s.o.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Have you found any solutions to it yet? Please advice
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.
tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.
socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary
Anyone have the screen record enabled in power menu and how ?
khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop
monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )
hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?
V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.
Hey guys,
Just having a big bloody problem installing magisk on LOS 18.1.
Whenever I do the device will get hot, reception will be gone, system ui will keep crashing, device will operate on fullbright then eventually after about 2-5 mins qualcomm crashdumps to mdm_force_reset.
And even with all that happening Magisk still doesn't appear to have been installed
I have tried:
Factory reset
Magisk canary
patching boot image
reflashing rom
flashing via the (wip) twrp
flashing via sideload
All resulting in the same situation.
I have attached a full logcat dump below, device will continue to work properly with stock boot image and with stock or non stock kernal. This works on OOS just not LOS. During installation no errors occure for magisk so this has me stumped.
hmm not sure if this logs uploading on xda so heres a drive link
log.txt
drive.google.com
Have to ask, you're trying to patch and boot from the LOS boot image, right?
Try with different, non-canary Magisk too. I never used canary and it always worked for me.
daviddosa said:
Have to ask, you're trying to patch and boot from the LOS boot image, right?
Try with different, non-canary Magisk too. I never used canary and it always worked for me.
Click to expand...
Click to collapse
Yeah correct, Pulled directly off my device (also the flashing via twrp of the magisk zip has the same outcome so it can't be boot image related :^) )
Yeah tried both canary and mainline 23.0, no dice but thx for checking.
darkjake said:
Yeah correct, Pulled directly off my device (also the flashing via twrp of the magisk zip has the same outcome so it can't be boot image related :^) )
Yeah tried both canary and mainline 23.0, no dice but thx for checking.
Click to expand...
Click to collapse
What if you extract it from the payload.bin?
Patch that boot.img, boot from it(don't flash), then use Magisk to install it directly, but not on the inactive slot.
daviddosa said:
What if you extract it from the payload.bin?
Patch that boot.img, boot from it(don't flash), then use Magisk to install it directly, but not on the inactive slot.
Click to expand...
Click to collapse
Booting from it has the same result :/ cannot use Magsik to install it directly either ( since the manager still claims it isn't installed)
Magisk log just in case
magisk.log
drive.google.com