Database Info

Please help me. I am trying to install Lineage OS onto my Motorola One Vision

Hello, I have followed these instructions: https://forum.xda-developers.com/one-vision/development/recovery-official-twrp-motorola-one-t4144933 and now I am unsure what to do. This has successfully loaded TWRP onto my device and has given me root permissions. But I wish to install Lineage 17.1 and I really don't know what to do.
I have tried clicking install zip and flashing the correct Lineage zip from: https://forum.xda-developers.com/one-vision/development/rom-lineageos-17-1-t4158527 but I receive the error 255.
It says:
Code:
Flashing A/B zip to inactive slot: A
Updater process ended with ERROR: 255
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file 'etc'
How can I do this?
Thank you.

1.move to phone lasted version lineage os upload on sd card
https://images.stricted.net/lineageos/kane/lineage-17.1-20210127-UNOFFICIAL-kane.zip
2.flash boot in phone example c:\adb\fastboot flash boot boot.img
3.reboot in recovery
4.select option apply update
5.select option from sd card
6.flash it
7.reboot to bootloader
8.flash twrp recovery
9.flash opengapps and magisk
10.enjoy

link for boot.img https://drive.google.com/drive/folders/1N-mqas3cCqBoj4UTdBT0BsXf3GltBwan?usp=sharing

How to flash TWRP onto both Slot A and Slot B? - Can't find a straight answer.

Hello, my goal is to flash TWRP onto both Slot A and Slot B.
I've flashed TWRP into Slot A, while Slot B is flashed with LineageOS recovery, currently.
I'm pretty sure I then flashed the OS/ROM with TWRP into Slot A but afterward I had a warning that read, "No OS Installed" - I thought it was a fluke, I rebooted System and it went back to TWRP with Slot A active.
I manually switched to Slot B and rebooted System and LineageOS loaded. Rebooted into recovery and discovered Slot B is still using LineageOS recovery.
From there, in the recovery interface, there's no option to manually change back to Slot A. Rebooted into fastboot and connected phone to PC and ran command:
fastboot set_active other
This switched back to Slot A
I rebooted the device which loaded TWRP on Slot A.
At this point what do I need to do to install TWRP onto Slot B and flash LineageOS onto Slot A and Slot B?
I assume through TWRP on Slot A - I can flash TWRP onto Slot B. Then manually change to Slot B - reboot into recovery and verify TWRP is installed on Slot B?
Doing this of course, will break (assumption again) the LineageOS installation and will have to re-install LineageOS.
Once verified, flash LineageOS onto both Slot A and Slot B.
I feel like I missed something but honestly I'm using multiple guides and I feel I'm going to end up breaking something since not all guides align well.
I know this is a noob question, so I apologize, but I am trying to follow guides, none of which are instructing from A-Z the processes to achieve this goal. I have no issues following instructions, if I did, I'd have broken linux boxes, including a linux server.
I'm willing to start from scratch if I have to, I just want to get it right once and for all.

This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.

azoller1 said:
This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.
Click to expand...
Click to collapse
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?

Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.

Fumetsu_Guritto said:
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?
Click to expand...
Click to collapse
I am not sure where you are seeing Advanced > Install recovery ramdisk in twrp. You should never have to used the advanced menu in twrp, unless for very specific reasons.
Ok, lets assume you are running the latest stock OOS.
1. First, you unlock the bootloader and can now use fastboot.
2. Reboot to bootloader
3. At this point you flash the twrp.img file to both recovery slots like i mentioned in my other post.
4. At this point you have twrp forever until something else overwrites the recovery partitions (flashing rom, flashing other custom recovery, etc).
5. Now, you need to factory reset, go to reboot then switch to the inactive slot, dont reboot, go back to install, then flash the rom zip file.
6. After flashing the rom zip file, flash the twrp installer zip file to overwrite the rom recovery.img so you can retain twrp.
7. Then you can reboot system and you will boot to the other slot where the rom was just flashed and everything should be ok.
Since twrp for the 8T is still not fully stable, but works very well, I dont think its good to flash .imgs directly in twrp, im sure it works but I usually just flash compatible zip files in twrp and use fastboot manually to flash a specific img if desired.
For magisk, the dev states in the instructions that flashing in twrp is not recommended (for the 8t in this case) and is better to boot the patched img from fastboot then go into magisk and direct install. Flashing using fastboot should work 100% of the time without issues. I have always just flashed the patched boot.img directly in fastboot and reboot with no issues.
However, if you prefer to flash in twrp, you must reboot back into recovery (reboot then press recovery) after flashing the rom and the twrp installer, so your device is updated to the other slot where the rom was flashed. Now you can flash magisk and it will flash to the correct boot.img slot.

Fumetsu_Guritto said:
Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.
Click to expand...
Click to collapse
A magisk patched img is a boot.img unpacked and magisk is then injected and repacked. The size is 96mb.

Magisk & Lineage = No wifi

Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?

Ork_77 said:
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Click to expand...
Click to collapse
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?

Droidriven said:
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Click to expand...
Click to collapse
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.

Ork_77 said:
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Click to expand...
Click to collapse
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com

...

Droidriven said:
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
Yes...this is exatcly what I did.
Method 2.

Ork_77 said:
Yes...this is exatcly what I did.
Method 2.
Click to expand...
Click to collapse
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.

Droidriven said:
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Click to expand...
Click to collapse
Hi Droidriven, thank you for your answers. Perhaps, synthesizing my steps too much, I gave the impression of not being particularly capable in computer science (you even tell me to press "enter" after commands ...). Well, let's say it's not my case.
All steps are performed correctly.
all steps end without errors.
No matter what I do, in the end Magisk appears as n / a, I don't have root, and the data connection doesn't work. Small addition about the latter aspect: when rebooting the wifi connection works for a variable time between 10 and 20 seconds, after which the network appears as without internet (or intranet) but the phone remains connected.
At the reboot, history repeats itself
Restoring the original boot everything returns to normal.

Fastboot runs instead of TWRP | Fastboot loop

After unlocking the bootloader, I flashed TWRP according to these instructions, and everything worked:
fastboot flash recovery recovery.img
To keep TWRP on, you need to go to Advanced > Sing boot and in the window that appears, slide the blue slider to the right, after which the smartphone will reboot.
Then I followed these firmware instructions:
1. Make a backup of personal data (memory will be formatted)!
2. After unlocking boot and installing TWRP.
3. Make vipes in TWRP: "Adwanced Wipe" - Dalvik/ART Cache, Data, Cache, System - all except Internal Storage! Then go to TWRP, you can't get out of it yet!
4. In the menu "Mount" should be set only one mark "Data" - Connect to the computer - In "Note9/Internal Storage" on the computer to throw RADIO-m1923-... and install it - "Wipe Cache/Dalvik".
5. Make vipes in TWRP: "Format Data" - go to the main in TWRP (in "Mount" should be marked "Data").
6. In "Note9/Internal Storage" drop the firmware itself MK100.0-m1923-... - in the menu item "Install" look for files on the path: "/data/media/0" (to get to the memory root press "Install Image" - "Up A Level" - "Install Zip") - install - "Wipe Cache/Dalvik", reboot into the system!
At the last point in TWRP there was an error saying that the image was not installed, and I was asked if I wanted to boot with the system not installed, and I said yes
After that, no matter what I do or exactly how I try to enter recovery, I always boot into Fastboot
SOLVED
I solved this problem by reflashing to the stock recovery with dump, and reflashed to the stock firmware with stock recovery
The firmware was working and then I flashed the TWRP back and the custom firmware
Then it turned out that twrp has a format button which I didn't notice and the new firmware didn't run because of that

Reflash Stock ROM.

xXx yYy said:
Reflash Stock ROM.
Click to expand...
Click to collapse
How can I do that? Twrp won't boot

xXx yYy said:
Reflash Stock ROM.
Click to expand...
Click to collapse
I tried this with the stock firmware and the command:
fastboot update update.zip
But it seems the stock flyme firmware does not contain this file and is not recognized by fastboot:
archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt

No root Magisk 25.2 patch recovery in TWRP for Galaxy

Hi,
I finally got Palladium GSI installed (Android 11)! I rooted my Pixel in the past with Magisk 25.2. Now on my Samsung Galaxy A50 that I installed Palladium, I cannot get root. Here are the steps I did.
RAMDISK=NO in Magisk.
(1) Download Magisk 25.2
(2) extract recovery.img from TWRP 3.6 (that I installed originally)
(3) Open Magisk->Install with recovery mode checked ->NEXT -> select and patch a file -> pick recovery.img -> "let's go"
(4) copy the Magisk patched image to my SD Card
(5) boot into TWRP
(6) Install->Image-> pick the Magisk patched (recovery) image -> select 'recovery' partition -> 'swipe to confirm flash'
(7) reboot to recovery once flashed
(8) open Magisk app, no root
what did I do wrong?
I also tried installing Magisk in TWRP by renaming the extension to 'zip' and flashing, rebooting into recovery... I saw that as another method - didn't work either
I'm soo close trying the two methods above I saw in other XDA forum posts. Did I miss a critical step?

Installation
The Magic Mask for Android
topjohnwu.github.io
^ do I need to do the vbmeta steps too? Unsure how I would do that in TWRP though...

vbmeta is afaik patched from maigisk, but you can download vbmeta.img.empty pack it into tar archive and flash from Odin3 as it might still required for twrp in case magisk doesn't work.