Develop Bugs

[AS990] Custom Recovery and Keep Stock

Hey guys, I have been working on this for a while an I think I finally have the answer as to keep stock AS990 and have a custom recovery.
Please note I will not be responsible for bricked devices. If you don't understand something do some research before you start.
Lets get started.
To get roms to install, I had to use the whole guide found here then install a custom rom, create a TWRP backup, take the backup off the internal sd card then once I finished the steps below I put the backup back onto my internal sdcard and used TWRP. Now some of you may be asking "Why the heck did he do that for?". Well when I went to install a ROM, I could not mount the system partition so therefore I used this work around because I had made a backup before I found out the method below. If anyone has a fix for this please be sure to comment.
Download and extract the files here
First off you will need to be on Stock AS990 and rooted. If you have not done this please follow the guide located here to do that.
If you are on a rom that cannot be rooted, follow this guide and use the files found in the restore bullet point to downgrade then root. Backing up your build.prop should not be necessary in this case since you are doing a downgrade.
After you have done this, root and use flashify to install ls990 TWRP.
Reboot your device into recovery.
If all goes well, You should now be stuck in fastboot mode.
Flash the following files found in the folder you downloaded earlier.
Open the folder you extracted the files to earlier, hold shift, right click in a section of the folder where no files are then select "open command window here".
Type the following commands into the CMD window.
fastboot flash aboot aboot.bin
fastboot flash boot boot.bin
fastboot flash dbi dbi.bin
fastboot flash factory factory.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rct rct.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash tz tz.bin
Pull the battery and turn back on and the rom should now boot back into your stock system.
Again use flashify to install ls990 TWRP.
Make a recovery of your current rom.
Flash the rom you backed up.
For me I have figured out how to get mms, data texting and calling on a custom rom with my carrier (Carolina West Wireless).
I installed Google Hangouts then used shortcut master lite to find the apn settings in hangouts which are not the same as using other methods.
If I left out anything please let me know thanks.
Well that's all for now.
Not sure who all to give credit to but this is a compilation of my work as well as all the guys who made the post above.
You may be able to use this method to root as well but have not tired that yet.

Attempting to root and install a custom ROM (DU), where am I going wrong?

Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!

I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.

HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.

thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.

If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app

HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone

Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.

thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play

berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:

Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.

Help, possibly bricked phone

Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.

Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip

EFS backup

Hello there,
Guys, give me some hints how to do a EFS backup on my MZP. There are no such option in TWRP, I've tried some apps but with no success as well.
Thank you.
Sent from my VTR-L29 using Tapatalk

pocko said:
Hello there,
Guys, give me some hints how to do a EFS backup on my MZP. There are no such option in TWRP, I've tried some apps but with no success as well.
Thank you.
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
As far as I know it is not possible at this time. Best to hope it is added into a future release for us on TWRP. It is normally the first thing I do on TWRP and I was just as shocked to not see on it as well.

pocko said:
Hello there,
Guys, give me some hints how to do a EFS backup on my MZP. There are no such option in TWRP, I've tried some apps but with no success as well.
Thank you.
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
i am relatively new to the moto z but i think you can use the Chinese TWRP and backup the EFS, i didn't see it available on the non-chinese TWRP. You can do a search on here to find a link.

1)Flash TWRP recovery(Official & latest).
2) Backup--> nandroid Backup
3) select system checkbox.
4)Swipe to confirm.
1)using terminal from TWRP-->Advanced-->Terminal
2) type following command
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return) dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
Copy both file modemst1.bin & modemst2.bin to comp.
2)type the following in fastboot
Code:
fastboot flash modemst1 modemst1.bin fastboot flash modemst2 modemst2.bin
I found this online. I don't know if it actually works.

mysterysauce said:
1)Flash TWRP recovery(Official & latest).
2) Backup--> nandroid Backup
3) select system checkbox.
4)Swipe to confirm.
1)using terminal from TWRP-->Advanced-->Terminal
2) type following command
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return) dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
Copy both file modemst1.bin & modemst2.bin to comp.
2)type the following in fastboot
Code:
fastboot flash modemst1 modemst1.bin fastboot flash modemst2 modemst2.bin
I found this online. I don't know if it actually works.
Click to expand...
Click to collapse
That's the best way!! Chinese twrp have the EFS backup option, but if you use another twrp version (tomparr or Alberto97) you can do this... in the moto z play must work in this way (two commands):
To backup via TWRP terminal:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.emmc.win
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.emmc.win
To restore via TWRP terminal:
dd if=/sdcard/modemst1.emmc.win of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/modemst2.emmc.win of=/dev/block/bootdevice/by-name/modemst2

Thank you guys for your help.
As Chinese TWRP doesn't work on my reteu mzp, to use fastboot commands is not so bad option.
Sent from my VTR-L29 using Tapatalk

Hi, I have Tomparr TWRP version and I want to make a EFS Backup, should I flash chinese TWRP and backup from there or can I backup from tomparr TWRP terminal following those two commands put it in previus posts?

Cordobes21 said:
Hi, I have Tomparr TWRP version and I want to make a EFS Backup, should I flash chinese TWRP and backup from there or can I backup from tomparr TWRP terminal following those two commands put it in previus posts?
Click to expand...
Click to collapse
Use this version as it allows EFS backup.
https://www.androidfilehost.com/?w=files&flid=194127

Jimi Mack said:
Use this version as it allows EFS backup.
https://www.androidfilehost.com/?w=files&flid=194127
Click to expand...
Click to collapse
I'm currently with tomparr TWRP, with RR rom, so, if I understand correctly, I should install the TWRP that you provide me via fastboot, enter TWRP, make backup, shut down the device, put tomparr TWRP via fastboot and reboot into Android, and copy TWRP folder on my PC, I understand correctly????? Sorry for the troubles

Cordobes21 said:
I'm currently with tomparr TWRP, with RR rom, so, if I understand correctly, I should install the TWRP that you provide me via fastboot, enter TWRP, make backup, shut down the device, put tomparr TWRP via fastboot and reboot into Android, and copy TWRP folder on my PC, I understand correctly????? Sorry for the troubles
Click to expand...
Click to collapse
No, I sent step by step simple instruction to you. It is as simple as flashing over your existing TWRP, no need for fastboot and flipping back and forth. You are over thinking this.

Jimi Mack said:
No, I sent step by step simple instruction to you. It is as simple as flashing over your existing TWRP, no need for fastboot and flipping back and forth. You are over thinking this.
Click to expand...
Click to collapse
Thank you very much for help me :good:

How to make a backup with LineageOs recovery?

On an older phone I used TWRP recovery. That has a brilliant option to create system backups.
How to do that in the LineageOs recovery?
I want to clone one phone to another identical phone. I hope that can be done by creating a backup on phone 1 and install it from recovery on the other. Hopefully including the OS (with all the setting that take hours of fiddling about), apps and data.

Just use twrp..?

PhotonIce said:
Just use twrp..?
Click to expand...
Click to collapse
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.

carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp

carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Use twrp backup and select all the partitions. It'll back up everything.
Apps and settings are located in the data partition and other files/data is located in the internal storage partition. boot is the kernel, recovery is the recovery and system in the system image.
If you know what you're doing you could even install a fresh copy of lineage onto another phone and just restore the data and internal storage partitions, and still receive an exact copy of the phone you backup up from while using less space in the backup.

... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?

Paul_Neocube said:
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Click to expand...
Click to collapse
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.

PhotonIce said:
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
Click to expand...
Click to collapse
On my device there are two slots... A and B. Like two separate partitions that van have software installed to. When I installed my rom I first installed twrp to slot a and then my Tom to slot b which is what runs now when I power on my device. I can't install twrp to the slot my os is on as I would have issues with the os recovery that is on that slot.

Skorpion96 said:
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
Click to expand...
Click to collapse
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.

zogoibi said:
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
Click to expand...
Click to collapse
It's not. He keeps LineageOS recovery on the phone, and when he wants to use TWRP, he connects the phone to his computer via USB and runs fastboot boot twrp.img from the command line. This reboots the phone and loads TWRP into memory without flashing it to the phone.

@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?

zogoibi said:
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
Click to expand...
Click to collapse
actually i done the reverse, i have twrp installed and when i want to run lineage recovery i boot it with fastboot boot "recovery.img"

Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.

zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
You ever flashed TWRP via cmd (adb) on a pc? It's the same thing but you use fastboot flash rather than fastboot boot. When you flash twrp on phone, you put the recovery.img file in your adb folder, if I'm not mistaken. The same thing goes for booting an .img file (it goes in the adb directory/folder in your pc).

zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
The alternate recovery should remain on the computer. It can be in the same folder as adb and fastboot for easy access (it doesn't need to be there, it's just easier that way). That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.

MJPollard said:
That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
Click to expand...
Click to collapse
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.

zogoibi said:
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
Click to expand...
Click to collapse
Try fastboot boot recovery twrp.img. I don't normally do this so I might have misremembered it. If it works, I'll edit my post so that others don't get confused.

Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!

zogoibi said:
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
Click to expand...
Click to collapse
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.

agamemnonn said:
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
Click to expand...
Click to collapse
I found out that it's not possible. LOS Recovery's fastboot mode has that command disabled.