Database Develop

Lg G3 (D855) CM13 Supersu

Hello Chainfire,
I have smartphone LG G3 32GB (D855), as custom rom I just installed the CM13. I tried to flash through recovery TWRP SuperSU-v2.62-3-20151211162651.zip, but when I restarted the device went into boot loop.
Can you tell me if I should try another version, or you have to wait ??

I have the same question
...

Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.

Chainfire said:
Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.
Click to expand...
Click to collapse
Same problem here with my ONEPLUS One... Updated to the latest CM 13.0 nightly everything was perfect. Installed SuperSU "UPDATE -SuperSU v2.46. System hang at the Android character during logon. I have reloaded the CM13.0 and Gapps, reflashed those two to restore system operation. Found SU v2.62-3 I'll hold off on flashing that SuperSU until a ".. different (easier) solution..." is available. Thanks Chainfire!!!

Happy to wait!
Sent from my LG G3 running cm 12.1

Same problem...
There are news? :crying:

Boot Error
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.

SkyDriver11 said:
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.
Click to expand...
Click to collapse
well! have you a news about this way?
ps. happy new year to everybody!!

Use SuperSU 2.52
Drago76 said:
well! have you a news about this way?
ps. happy new year to everybody!!
Click to expand...
Click to collapse
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img

SkyDriver11 said:
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img
Click to expand...
Click to collapse
I've tried to flash SuperSU 2.52 but the phone go to loop on the cm animation boot.. :crying:

CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.

gimli4711 said:
CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.
Click to expand...
Click to collapse
Everyone knows this, thanks..
the problem is that with cm13 root, some apps like Leandroid doesn't work, cause it wants only supersu.
for example, my friend with Nexus 5 cm13, has installed supersu 2.62 and he enjoys Leandroid perfectly.

nothing? :crying:

The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.

great solution!!! it's wonderful!!!
thanks!!
Inviato dal mio LG-D855 utilizzando Tapatalk

superSU 2.66 beta on lg g2 d802...
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
it worked perfectly on lg g2 d802 ...no bootloops !thanks a lot

stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:

jhtrades1 said:
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:
Click to expand...
Click to collapse
You also can manually install update from TWRP, after than reinstall xposed Framework (if have it), supersu 2.66 and last reinstall "Sharpening-Mod-3.5".. now reboot.
enjoy!
Inviato dal mio LG-D855 utilizzando Tapatalk

stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works thanks for this nice solution

stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works on my LG G3 D855! Thank you! :victory::highfive:

Bootloop - New fi Moto x4

I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!

Laugh this is just getting worse. I uninstalled Magisk and now the phone boots straight into recovery whenever I restart it. I'd flash a stock rom but I can't find one. I think I'm in trouble...

Reinstalled Magisk and it at least tries to boot up again but it just loops.

Arsenal420 said:
I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Click to expand...
Click to collapse
https://magiskroot.net/uninstall-magisk-module-twrp/
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
In summary:
Step 1: Download the flasheable zip file from the Magisk module uninstaller from the following link to the PC
Step 2: Send the zip file to the SD card of the phones or to the internal memory using MTP (most of the recovery of TWRP is compatible with this method)
Step 3: Now, touch the Install button and choose the Zip file of the uninstaller of the Magisk module that you want to update.
Step 4: After the completion of the installation. Go back to the TWRP home page.
Step 5: Tap the advanced option from the TWRP homepage. Choose the terminal option now.
Step 6: Type uninmod in the terminal box and touch the input button.
Step 7: Now, you can see the list of Modules and you have to type the Number you want to uninstall (Check the screenshot below)
Step 8: Finally, the magisk module will be completely uninstalled.

Arsenal420 said:
. Downloaded the Xposed Installed from the playstore,
Click to expand...
Click to collapse
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.

Nergal di Cuthah said:
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Click to expand...
Click to collapse
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?

Arsenal420 said:
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Click to expand...
Click to collapse
Ok good, I got scared for you a bit there, my post was not meant to be mean spirited but maybe you read it as such. As far as the bootloop i'm afraid i'll be no help.

7 Pro OB6 is out, uploaded ZIP on my google drive

https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!

Thanks, I was testing.
---------- Post added at 03:53 AM ---------- Previous post was at 03:16 AM ----------
สุรินทร์ พลโธา said:
Thanks, I was testing.
Click to expand...
Click to collapse
From testing hours than typical usage, better 0.2 overview and notifications improved. The battery cannot be dictated at this time.

I can't install from twrp, too. Same error.

=。= said:
I can't install from twrp, too. Same error.
Click to expand...
Click to collapse
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.

rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
I installed through an app system. I tested it now, it's better to use a stable battery enough to say it's saving

aNGERY said:
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Click to expand...
Click to collapse
After activating magisk modules my device is not booting. continuously booting to twrp and showing Rescueparty. i had tried magisk untinstaller but nothing happen.

rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.

I'm wondering if there is any advantage to installing the update twice, so that it's on both slots?

This Walkthrough works with me perfectly
Updating from open beta 5 to open Beta 6 successfully
Rooted 20.1 & Twrp 72 no issues
Thanks a lot

1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72

null0seven said:
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
Click to expand...
Click to collapse
This works like a charm. Just did it to install it to the other slot being slot a. I'm ocd so I like both slots flashed. Easy solution to not being able to flash it in twrp. I'm kind of curious why it won't flash in twrp though. Maybe something to do with the security patch

I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?

Account login in settings:

I was able to flash in TWRP using version -74, downloading OB6 using oxygen updater

Gordietm said:
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Click to expand...
Click to collapse
Not up at the top but yes can add in through settings.View attachment 4883201

Aporzio said:
Not up at the top but yes can add in through settings.
Click to expand...
Click to collapse
So why do I have in the main settings and others don't?

Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
Not really sure

If anybody wants official download link for OB6 Global:
https://otafsg1.h2os.com/patch/amaz...13.W.17_OTA_017_all_1911152150_5b8908ba7b.zip

ZoiraP said:
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
Click to expand...
Click to collapse
this is the first one i couldn't flash in TWRP

Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
I updated from twrp and got the same popup in my settings. Also, xXx has been affected, the debloat doesn't work properly on ob6. Hopefully things will get figured out soon.

[OXYGENOS] Android 10 Open Beta 1 for OnePlus 5

Changelog
System
• Brand new UI design brings light and fluid experience
• Updated to Android 10
Instructions
• Download the appropriate package - OnePlus 5
• Open the File Manager and move the downloaded .zip package from the Downloads folder to the root directory.
• Open Settings - System - System updates, press the cogwheel on the top right corner, choose the Local upgrade option, and select the rollback file.
Users who are still on OBT builds for 5/5T can update to this build only via update from recovery. For those, PLEASE NOTE, your entire data will be wiped.
• Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
• Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
• Wait until the installation is complete -> Reboot
Note:
• Please keep in mind that this is beta software. These builds are not as stable as our official OTAs. By installing this update, you accept the potential risks.

https://forums.oneplus.com/threads/android-10-open-beta-1-for-oneplus-5-5t.1218721/
OnePlus 5 : https://oxygenos.oneplus.net/OnePlus5Oxygen_23_OTA_063_all_2004201835_a1de28fd0bda4c8b.zip
OnePlus 5T : https://oxygenos.oneplus.net/OnePlus5TOxygen_43_OTA_063_all_2004201837_eca63aa919a1477a.zip

Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.

PhoenixNLx said:
Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.
Click to expand...
Click to collapse
I don't think so... It's better to perform a clean install

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?

PhoenixNLx said:
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?
Click to expand...
Click to collapse
I came here looking for this too. I guess I'll have to do a full backup just in case before updating.

Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!

Ssmiles said:
Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!
Click to expand...
Click to collapse
Did you dirty flash or?

yes dirty flash
kernel BluSpark OOS v193 error in TWRP
Recovery TWRP 3.3.1-x blu_spark v9.110
ctsProfil Magisk 20.4 false

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Yes it worked, for me except duo calls not working when google hotword is enabled, everything is working

duo it's desactived

I tried this method https://droidholic.com/fix-cts-profile-mismatch-errors/ but CHROME doesn't work afterwards so I uninstalled everything

I just dirty flashed it in bluspark.
Full zip install
Magisk 20.4
Clear cache
Done

@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!

shadowstep said:
@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!
Click to expand...
Click to collapse
My thread was published before the other one, but as you wish

PierreVicquery02 said:
My thread was published before the other one, but as you wish
Click to expand...
Click to collapse
The other one (official thread) was created on 25th November 2017 by Funk Wizard, when the first Open Beta was released. Ever since then, it has been used for announcing all subsequent Open Beta releases as well as gather feedback on them. Nonetheless, thanks for changing the thread title, I appreciate it!

Does any one have any idea how I can enable full screen gestures for OnePlus 5?
I flashed the open beta build and tries enabling on screen navigation buttons but it's giving me the old buttons
I tried using
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
as it used to work on OOS 9, but this has no effect on the current open beta build
Thanks in advance

The wifi is randomly dropping for me then reconnecting. That happens quite often,anyone else experiencing it? I'm full stock with locked bootloader,haven't done a factory reset though.

this beta ROM can pass safety net with magisk?

fedex_742 said:
this beta ROM can pass safety net with magisk?
Click to expand...
Click to collapse
Somebody passes, somebody not. I don't know why.

After rooting G9+ & installing an unofficial LineageOS 18.1, root was lost & need help getting it back

I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.

Have u tested lineage, is
everything working fine?

UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.

doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?

Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.

UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)

Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)

Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.

doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel

There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro

The ROM in the O.P. works.​
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).

M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!

I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know