twrp corrupted or something - Sony Xperia ZR

for some reason, i'm able to flash any custom rom i want, but any other file, it gives me error everytime, like gapps, xospapps, supersu, etc. i'm not so sure if the twr is corrupted or i installed one that is not compatible with my phone, but that shouldn't be the case i think, because like i said, i can install custom roms without a problem, edit: i forgot to mention, i'm unable to install gapps, x86, x64, arm, arm64

bump, i really need help on this, i swear i've spent over 4 entire days trying to solve this crap, unlocking/locking bootloader, supersu, rootking, etc. fastboot drivers, adb, everything, still no clue what is going on, i can't install gapps, i can't go on with the rom i installed, is freaking useless as it is, i can't even flash (overwrite) the current twrp because i need to flash with it or adb, and none are working, but just for now, i need to know, why i can't install any gapps

I SOLVED IT !!! first of all, if you having the same issue as me, DO NOT EVER INSTALL AN UPDATED VERSION OF TWRP, ok, so the way i made it, it was downgrading my rom/kernel in order to root my phone, cause it was literally impossible, kingroot, supersu, emma, flashtool, nothing worked, so once i downgrade my rom, i installed an older version of twrp, and then i root my phone, which it was possible due to having a less secured version of the kernel, and that's it, i could install gapps, flash roms, etc.

Related

Unable to install Magisk on my Z3C

For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Kesymos said:
For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Click to expand...
Click to collapse
Have you tried with a different stock kernel, (maybe Elite)? Not sure what the problem is. I've never had trouble with Magisk, but now that I think about it, I don't think I ever tried to flash it on straight stock rom, (I prefer phh anyway in general).
Another thought I had is, if Magisk has a problem with elf format, maybe use Rashr to make a kernel backup image, then flash the backup, (I really don't know anything about this stuff, just shooting in the dark...).

Help with Treble ROMs

I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!

Install TWRP, Root, LineageOS and Immensity Kernel from Stock?

Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?

Can't Unlock Device or Cannot Install OpenGapps

Here are somethings I struggled with unlocking the bootloader, installing a custom ROM and the apps.
If you are trying to unlock your bootloader with the Mi Unlock Tool and it seems to randomly fail, make sure you are not using a Ryzen processor. It fails everytime. Use an intel based machine if you can.
Ryzen processors also make it impossible to use fastboot correctly. I could not install or boot into TWRP. Once again, use an intel based machine.
One thing I could not get working after unlocking my phone is flash TWRP to the recovery. It never worked. It said it worked in the Fastboot CLI but it didn't. I could boot to the TWRP image and do everything I needed to from there. Anyone know why this is?
I also could not install Opengapps after installing the OS. They just would not show up at all.
I made sure to install Magisk after OpenGapps and everything seemed to work fine but the launcher kept crashing. I found that it must have the items installed in this order:
OS, Magisk, OpenGapps
Now everything is working and stable. I'm not sure as to why this works (or doesn't in my attempts) but it does. I have read a lot of scattered forums on this issue and the best I can come up with is the correct partitions are not mounted/unmounted when OpenGapps is installed but doing Magisk first mounts and unmounts the correct partitions.
Does anyone know the actual answer to this?
TL;DR
Don't use Mi Unlock or ADB/Fastboot on Ryzen, use intel.
Install OS, Magisk, OpenGapps on TWRP, in that order.

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

Categories

Resources