Related
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Not the way you are doing it. I boot to TWRP, without installing it and have TWRP install the full zip.
Hm I'll try this. Used to the boot patching.
xringo said:
Hm I'll try this. Used to the boot patching.
Click to expand...
Click to collapse
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
lorax70 said:
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
Click to expand...
Click to collapse
You can give link file magisk for use on android 9.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Fwiw. I've been using this magisk version for dp3-5, but there are newer versions, but 16.4 works for me...
https://thedroidarena.com/download-magisk-16-4-beta/
I may try a newer version at some point, but I'm in no rush.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Got this from the Flash kernel thread. It works fine on Pie :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Make sure your using 16.7 you have to change in setting to beta. Same thing happened to me trying to use 16.0
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Airpil said:
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Don't wipe your phone! Just flash the new boot.img from the image file (not OTA file) and you will be able to go back to your Android system and disable the pin. After disable the pin, boot into TWRP and flash the Magisk from here https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Hope this helps!
madmuthertrucker said:
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
Click to expand...
Click to collapse
Use magisk uninstall first and this should solve the issue.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Brakiss said:
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Click to expand...
Click to collapse
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Badger50 said:
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Click to expand...
Click to collapse
Where did you see this? I have pattern and would like to keep it.
Brakiss said:
Where did you see this? I have pattern and would like to keep it.
Click to expand...
Click to collapse
One of the other threads. Here's the twrp version though. https://dl.twrp.me/taimen/
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
pr1vate piles said:
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
Click to expand...
Click to collapse
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Your not wrong there. Tried it as you suggested, same thing, hanging at the G logo page with the bar animation under it. Had to run the uninstaller to get back into my phone. Very odd
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
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Files
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
use vbmeta from this post
Magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
hi, any idea to fix fingerprint?
[email protected] said:
hi, any idea to fix fingerprint?
Click to expand...
Click to collapse
We need to wait for Realme to release a fix, just like what happened on color os when fingerprint wasn't working
On C.27 Bootloader Unlock and Root, Fingerprinter works
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
minoccio said:
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
Click to expand...
Click to collapse
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
deviantor said:
Instal stock recovery like you did to install custom recovery.
Uninstall Magisk with the .zip from their site. Github here
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
So basically if I'm on c27 already, it's okay to use the same root method?
adsubzero said:
So basically if I'm on c27 already, it's okay to use the same root method?
Click to expand...
Click to collapse
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
deviantor said:
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
Click to expand...
Click to collapse
I tried several thins to install Magisk succesfully with no luck.
I received my Global x2 Pro this thursday and i successfully unlocked the bootloader and flashed twrp recovery. But when I flask the magisk 20.4 zip and reboot my device, i get an error saying that my boot / recovery partition is corrupt. I have to install C27 again from twrp and it boots up.
Can anybody help me how to install Magisk succesfully? It's driving me nuts. Also, i cant download the vbmeta.img from the OP. So i tried to extract the vbmeta.img from the c27 image to flash, but also no lucck
Edit: Finally having it working with the Orangefox recovery with the vbmeta.img. I thought that the link in OneDrive wasnt working, but it was my home networks which was blocking OneDrive. Problem solved!
deviantor said:
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
It's possible if someone makes a flashable zip, though I dont know of that can be done for every phone. Otherwise you need a stock recovery to install the OTA.
minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
Like @adsubzero said. Unless you have a custom ozip file to flash on TWRP, you need to have stock recovery to install a standard ozip.
ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Click to expand...
Click to collapse
for recovery mean recovery ka option ckick krna hai..vbmeta krty huay
In the backup options I don't see system, only system image. Does anyone else have this issue?
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.
so, i had my op 6t bricked and in a bootloop to fastboot
i managed to recover my data through twrp, but couldnt get lineage to run again, so i used the msm tool to downgrade to android 9 oos
now when i try to install a custom recovery i the phone freezes in this "the bootloader is unlocked warning"-screen
no idea why i cant boot into a custom recovery, with a unlocked oem
my plan is to get it back to run lineage os with twrp recovery
can u maybe help me?
I wasn't able to boot into twrp since a11. Had to install from magisk in booted oos using twrp installer. Not sure why it wouldn't work if you downgraded but maybe not using the correct twrp? Sounds like things are messed up. I would start from scratch and get a clean oos on both slots. If you can't boot into twrp then root with magisk and install directly from magisk manager with the installer.
So I am on 11.1.2.2, how do I get twrp installed on this. I cannot get twrp to boot past the logo. I have been trying to Flash HAVOC but have been stuck
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Brettroth said:
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Click to expand...
Click to collapse
Which magisk? latest or canary
Gytole said:
Which magisk? latest or canary
Click to expand...
Click to collapse
I use the latest
and are we talking 3.6.0_9? orr...
Gytole said:
and are we talking 3.6.0_9? orr...
Click to expand...
Click to collapse
Yeah that's the newest. Older ones work but that one has a lot of good changes
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
You need to flash a magisk modded boot in fastboot from your oos. Someone has a post somewhere in here hosting them I'll try to get a link for you.
so fastboot flash boot_a and b like usual for the patched boot image and then once in android just open magisk, then install the latest twrp from there? I think that's what put me in crash dump mode before
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
Are you on 11.2.1.1?
Brettroth said:
Are you on 11.2.1.1?
Click to expand...
Click to collapse
11.1.2.2 I believe?
Gytole said:
11.1.2.2 I believe?
Click to expand...
Click to collapse
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Brettroth said:
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Click to expand...
Click to collapse
Done. Now I boot into android, open magisk, and install the recovery?
Gytole said:
Done. Now I boot into android, open magisk, and install the recovery?
Click to expand...
Click to collapse
Yessir
Brettroth said:
Yessir
Click to expand...
Click to collapse
Work out for ya?
Wow. Alright. You all need to remember this. Msm only flashes to slot a. NOT slot b. So, if you were previously in A10 or A11 and flash msm OOS 9, there will be issues unless you local update the same android version to slot b. You can't have 2 different android version on your slots unless you're using dualboot mod. Like on 8 pro, crashdump happens when twrp is installed if both slots aren't using the same android version