Database Develop

Can't flash my recovery to TWRP on LineageOS

Hello dear fellows,
since 2 days i try to fix a problem with my unlocked and rooted Sony Xperia Z C6603. Still not finding any solution via internet, i take my last chance and post it here.
I unlocked and rooted my C6603 2 days ago and installed via fastboot the actual Lineage Custom ROM lineage-14.1-20171027-nightly-yuga-signed.zip.
Everything worked fine.
Bootloader -> fastboot flash boot boot.img (from lineage-14.1-20171027-nightly-yuga-signed.zip) :good:
Restart into Android Recovery :good:
Install via ADB sideload lineage-14.1-20171027-nightly-yuga-signed.zip :good:
Install via ADB sideload LineageOS 14.1 ARM32 SU (for full root access) :good:
Boot into Lineage, activate dev options and enabled Android-Debugging + Root-Access -> Apps and ADB :good:
Now my problem:
The so called "Android Recovery" is rly bad, so i try to override this recovery with TWRP 3.0.2.0 (yuga) but everytime i get the following error:
Code:
fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10656 KB)...
OKAY [ 0.351s]
writing 'recovery'...
[B]FAILED (remote: Command not allowed)[/B]
finished. total time: 0.370s
Where is my fffffff problem^^ Yes my phone is unlocked and yes, it is rooted (checked it also via root app).
I cant install gapps (dont work with ADB sideload) and and i want a proper recovery for backups and stuff...
So, what is wrong with me? Maybe someone of you have a good idea and can help me, i would rly appreciate it!
Sry for my not so proper english, hope u understand my problem anyway
Phone information:
Sony Xperia Z C6603
Android 7.1.2
LineageOS 14.1-20171020-NIGHTLY-yuga
LineageOS API-Level Guava (7)
Kernel-Version 3.4.113-yuga-gd710842
Build-Number lineage-yuga-userbug 7.2.1 NJH47F f281cb28f4

Thanx for all the help^^
I figured it out what to do:
1. fastboot flash boot twrp(actualversion).zip NOT fastboot flash recovery twrp(actualversion).zip
2. reboot into TWRP recovery mode
3. check if u can mount your data folder
3.1 if not, go to wipe -> advanced wipe -> change file system to ext4
4. install via ADB the actual LineageOS (or put the actual LineageOS file on your Sony/SD)
4. install LineageOS 14.1 SU via ADB (or put the actual LineageOS 14.1 SU file on your Sony/SD) -> https://www.lineageosroms.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
6. install Open gapps -> http://opengapps.org/
7. reboot and configure LineageOS
7.1 check your developer options -> Debugging + root access for ADB and apps
8. download TWRP apk via PlayStore
8.1 give TWRP apk root access and download the actual TWRP file for yuga
9. flash this TWRP recovery via app
10. DONE
Everything works fine (for now )
Topic can be closed!

Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.

nurps said:
Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.
Click to expand...
Click to collapse
Did you manage to solve the issue? I have the exact problem. The TWRP says it flashed but recovery is still stock android.

I have C6602. Someone on reddit gave me the solution; (do note that I had to run
Code:
adb root
for
Code:
su
to work.
You have a Xperia device which deals with recovery kind of weird. Recovery is stored with the kernel, not in a standalone recovery partition. Because of this you need to flash it to a FOTAKernel partition and use a kernel that supports FOTAKernel (the LineageOS one does).
To flash TWRP, first move the recovery image to your device with the adb command
Code:
adb push twrp-3.0.2-0-yuga.img /sdcard
. Then run
Code:
adb shell
to get access to the shell. Then run
Code:
su
and accept any prompts to gain root access. Then to actually flash, run
Code:
dd if=/sdcard/twrp-3.0.2-0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse

Mi A2: Pie upgrade + Magisk upgrade = bricked

Steps on my Xiaomi Mi A2:
Started the OTA from Oreo to Pie, officially being offered via settings.
While the OTA was downloading / installing, I uninstalled Magisk 17 (“restore images”). Note that after uninstalling Magisk, I did not see an option to install it again. In fact, the Magisk app still reported Magisk as being installed.
In the meantime, the OTA showed the restart button. This I did not tap, since I want Magisk to work.
I went back into the Magisk app. So far I had ignored the popup window offering an upgrade to Magisk 18. Now I accepted it, and I selected to install Magisk to the other slot (A/B). As advertised, this was followed by an automatic reboot.
The device at first continuously reset itself, i.e. it was in a boot loop. Eventually, I think I disconnected it from power or I pressed the power button. Now the boot process would move on to the boot animation with the colored horizontal stripe. There is got stuck. I waited for perhaps half an hour, then accepted that something is broken.
What could’ve gone wrong? Any idea what to do now or how to diagnose the issue? (there is data on the device that I don’t want to lose, text messages and other stuff)
Modifications that I did later:
Code:
fastboot set_active a
fastboot reboot
This enters a boot loop. Another time, I think after disconnecting the USB cable, it went back into Fastboot mode. Weird.
And:
Code:
fastboot set_active b
fastboot reboot
This boots to the colored stripe animation mentioned in the last of the steps above. So I assume slot b is the one that was last active.
I also tried booting other images, but to no avail:
Code:
fastboot boot boot.img
Among the images that I tried booting was Xiaomi’s 9.6.16.0 Oreo image as well as the images from the 10.0.1 built that Ricardo linked to in another post.

Bootloop usually occurs when you uninstall Magisk without uninstalling modules first.
Try installing Magisk via adb sideload with TWRP.
Sent from my Mi A2 using Tapatalk

hank81 said:
Bootloop usually occurs when you uninstall Magisk without uninstalling modules first.
Click to expand...
Click to collapse
Had no modules installed. But there was something odd about the upgrade process, especially that at first I didn’t get an option to install Magisk again.
Try installing Magisk via adb sideload with TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion! Have to look into TWRP.
Anyhow, at the moment I would be happy for the phone to boot again, even without Magisk. Can install Magisk later.

feklee said:
Had no modules installed. But there was something odd about the upgrade process, especially that at first I didn’t get an option to install Magisk again.
Thanks for the suggestion! Have to look into TWRP.
Anyhow, at the moment I would be happy for the phone to boot again, even without Magisk. Can install Magisk later.
Click to expand...
Click to collapse
If you can access TWRP, I hope that you can search for the OTA firmware zip that the System Updater downloaded & you can try manually flashing that zip using TWRP. It would restore the Pie boot image which would make the device boot up.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
If you can access TWRP, I hope that you can search for the OTA firmware zip that the System Updater downloaded & you can try manually flashing that zip using TWRP.
Click to expand...
Click to collapse
OK, so I booted into TWRP 3.2.3-0:
Code:
# fastboot boot TWRP-3.2.3-jasmine-20181201.img
I played with the command line in TWRP. However, I didn’t find the zip. Cache was not mounted, and it was not possible to mount it. Then I read a little bit about A/B (Seamless) System Updates. This is a cool concept, but somehow it failed miserably here. Neither slot does boot.
Slot B:
It looks like the Android version is still Oreo:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V9.6.17.0.0DIMIFE
So I obtained the image files for that version. There is a post with links to dumps. I then tried to boot the V9.6.17.0 boot image:
Code:
fastboot boot boot.img
Again, booting hangs at the animation with the horizontal colored stripe.
SLOT A:
As mentioned before, booting that doesn’t work either: The system enters a boot loop, repeatedly reseting itself before it even gets to the horizontal colored stripe animation.
This one has Pie:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V10.0.2.0.PDIMIFJ
As above, I obtained the image files for that version, and I did:
Code:
$ fastboot set_active a
Setting current slot to 'a'...
OKAY [ 0.017s]
Finished. Total time: 0.020s
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
Boot loop!
I repeated:
Code:
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
It’s always like that: When you’re not expecting anything anymore, it works! The A2 booted into Pie.
Noteworthy:
It’s weird that explicitly selecting the slot made it not work, or maybe it required another reboot.
Magisk remained installed: After the initial boot into Pie, I rebooted the phone, and it booted into Pie again although I did not flash boot.img.
Perhaps the phone didn’t do the initial boot into Pie because Magisk was still installed.

feklee said:
OK, so I booted into TWRP 3.2.3-0:
Code:
# fastboot boot TWRP-3.2.3-jasmine-20181201.img
I played with the command line in TWRP. However, I didn’t find the zip. Cache was not mounted, and it was not possible to mount it. Then I read a little bit about A/B (Seamless) System Updates. This is a cool concept, but somehow it failed miserably here. Neither slot does boot.
Slot B:
It looks like the Android version is still Oreo:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V9.6.17.0.0DIMIFE
So I obtained the image files for that version. There is a post with links to dumps. I then tried to boot the V9.6.17.0 boot image:
Code:
fastboot boot boot.img
Again, booting hangs at the animation with the horizontal colored stripe.
SLOT A:
As mentioned before, booting that doesn’t work either: The system enters a boot loop, repeatedly reseting itself before it even gets to the horizontal colored stripe animation.
This one has Pie:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V10.0.2.0.PDIMIFJ
As above, I obtained the image files for that version, and I did:
Code:
$ fastboot set_active a
Setting current slot to 'a'...
OKAY [ 0.017s]
Finished. Total time: 0.020s
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
Boot loop!
I repeated:
Code:
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
It’s always like that: When you’re not expecting anything anymore, it works! The A2 booted into Pie.
Noteworthy:
It’s weird that explicitly selecting the slot made it not work, or maybe it required another reboot.
Magisk remained installed: After the initial boot into Pie, I rebooted the phone, and it booted into Pie again although I did not flash boot.img.
Perhaps the phone didn’t do the initial boot into Pie because Magisk was still installed.
Click to expand...
Click to collapse
Great to see you fixed your issue
Maybe your post will help somebody else
Sent from my #FlagshipKiller3T using Tapatalk

[GUIDE][GSI] Flashing GSI's with TWRP Fixes and Workarounds

Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators

Screenshots of Havoc OS gsi running on my zte axon 10:

Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor

That all is great news.....bravooo

Any issues with the havoc gsi?

blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken

noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.

Bliss 12.7 Android 10 gsi on a2020u.

rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"

Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.

i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?

honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what

Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.

cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details

ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work

In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.

miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!

miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.

Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)

sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?

Moto G7 plus TWRP installation issues/confusion

Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks

I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.

timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?

timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.

chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse

I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins