Database Info

[RECOVERY][e2nam] TWRP 2.8.5.0 touch recovery LG MS395

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
DOWNLOAD:
TWRP Builds
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Latest Windows adb drivers required for sideload
HERE
Latest Linux adb drivers required for sideload compiled from android source
HERE
To install unzip and open terminal in root of folder
Code:
sudo cp adb fastboot /usr/bin

Installation
You must be rooted first follow the guide here
This can be flashed with several methods
1.) Flashify
Choose the name of the recovery image you want to flash
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) Fastboot (Must be enabled first)
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Run the following code to zero out laf:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
To flash recovery copy openrecovery-twrp-2.8.5.0-e2nam.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery openrecovery-twrp-2.8.5.0-e2nam.img
To boot into recovery
Code:
fastboot.exe boot openrecovery-twrp-2.8.5.0-e2nam.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push openrecovery-twrp-2.8.5.0-e2nam.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/openrecovery-twrp-2.8.5.0-e2nam.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery

Thanks for this. Will give it a try after work today. Hopefully unlocking won't give a noob like me any trouble.

I would recommend just putting the recovery on laf
Code:
fastboot flash laf recovery.img
We don't have button combo and it makes booting into recovery easier if you don't have access to the system or a PC by allowing you to boot into recovery the same way you boot into download mode.

Thank you!
Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
This works. No problems. :laugh:

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
I can't seem to get the into fastboot. I have Minimal adb and Fastboot installed, put the recovery image that folder, but my phone just reboots normal no how I tell fastboot to do it..recovery, download, etc. Don't understand this, could it be causing this "fastboot (Only works if you chose to keep fastboot mode in the linked guide) "

Unjustified Dev said:
Installation
You must be rooted first with boot loader unlocked follow the guide here
This can be flashed with several methods
1.) Flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide)
To flash recovery copy recovery.img to root of folder that contains fastboot.exe and start a command prompt
Code:
fastboot.exe flash recovery recovery.img
To boot into recovery
Code:
fastboot.exe boot recovery.img
3.) ADB shell
Copy recovery.img to root of folder that contains adb.exe and start a command prompt
Code:
adb.exe push recovery.img /sdcard/
Start ADB shell
Code:
adb.exe shell
Get root permission
Code:
su
Install the image
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
to boot into recovery
Code:
reboot recovery
Click to expand...
Click to collapse
Step 2 didn't have the adb in the code and I was copy and pasting and could get it to work. Finally figured it out. I know it's a rookie thing with me and this was the first time I used fastboot. Working now and have TWRP. Thanks!!

I was able to get TWRP on using fastboot but I don't understand this- "2.) fastboot (Only works if you chose to keep fastboot mode in the linked guide) "
Are you referring to having the recovery.img file the same location as fastbook.exe or does this mean something else?
Thanks

I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk

I am new myself and will let Unjustified explain Fastboot, although I did use that method to flash TWRP, I don't want to give you bad advice. With that said, I have Xposed Framework installed and also Gravity Box KK. Gravity box has many cool customizations and one is you can change the options you get when you reboot your phone. One the choices is reboot into recovery. Hit that and you will boot up into TWRP.
If that doesn't work for you, there is an app called Quick Boot in the play store that does the same thing as far as different choices for rebooting. Fastboot you would need to connect to you PC/Laptop and know the commands to boot into recovery, again any further details I l;eave to others that know more.
Hope this helps some.
---------- Post added at 07:20 AM ---------- Previous post was at 07:09 AM ----------
smilesintears77 said:
I'm a noobie with a question. Fortunately I was able to root and install twrp with flashfy app. Down the road if I brick my phone, how can I recover? Is there button combo on the f60 for twrp? what is fastboot?
Sent from my Z970 using Tapatalk
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2317790. You can read in that thread for more info on ADB and fastboot. This was a little easier for me then just using the commands posted above where you would execute them with CMD prompt from your PC, just make sure you are going to the root folder where the adb.exe and fastboot.exe are located. I was doing that wrong when I was trying to root at first. My choice not to use Flashify was strictly because I wanted to learn more, so please wait for others to chime in who know more then I.

Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.

bichofelix said:
Our phone has no button combo to reach recovery.
You usually would be able to use the factory reset button combo and then cancel to recovery but all I get is hardware cursor mode. If someone else has achieved these results then disregard the below message. :
If you would like to reach recovery from power off, then we will either need a modified aboot, or you can flash recovery over laf (download mode).
Code:
fastboot flash laf recovery.img
As for xposed, get g3tweaksbox from play store. It used to be a paid app but works flawlessly.
Click to expand...
Click to collapse
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.

TWRP Backup
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL

lowender62 said:
Question regarding making my first back up in TWRP. I know how to do it, just wanted input on a couple of thing so I have a good back up for if/when I mess something up. As of now, my back up I made has several apps (including system) disabled via @gatesjunior Debloater. I also have Xposed installed and Greenify and Gravity Box Modules installed.
Would I be better to put things back to stock and make a back up of the phone as it was when I bought (except root) or would a backup like I have to good enough to restore from.
Thanks again for all the help, especially on my stupid questions. LOL
Click to expand...
Click to collapse
As long as what you backup is currently usable you should be fine.
Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?

bichofelix said:
As long as what you backup is currently usable you should be fine.
Actually that did work. I was pressing vol+/-.
So to reiterate for others, to reach recovery you hold power & vol- until you see the lg logo, then release and immediately press and hold power again until factory reset comes up. Press yes then yes and bam.
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!

Unjustified Dev said:
I got to recovery once you reach factory reset I clicked yes and it went to twrp. Search Google for hard resetting F60.
Click to expand...
Click to collapse
Yes! this was what I was looking for! Thank you.
Sent from my Z970 using Tapatalk

lowender62 said:
Thanks for the info on my backup. It does work fine and is they way I like it, so I will just keep it. On the reboot to recovery I tried that and got a different screen with mode off, mode on, etc but didn't see factory reset. Highlight was Mode Off and I moved up and selected mode on. Now when I try it boots up normally. Anyway I can set it back to Mode off like it was?
Thanks for your help!!
Click to expand...
Click to collapse
Same way you get into factory reset except instead of vol- you hold both volume buttons.

bichofelix said:
Also, have you started a github for this device, yet?
Click to expand...
Click to collapse
Only for recovery our device is e2nam I won't push a full device tree until I'm booting cyanogenmod
https://github.com/Teamregular

bichofelix said:
Same way you get into factory reset except instead of vol- you hold both volume buttons.
Click to expand...
Click to collapse
Ok got it and I think it may have just been me doing something wrong. Got home from work and tried it way you described a few posts back and I booted into TWRP. It's working Thanks

Bricked Moto G (XT1072) after factory reset

Hello experts,
I already looked and tried different solutions without success…
I have a Moto G (4G) 2015 (XT1072), rooted and with custom recovery TWRP 2.8.0.1, Developer mode activated. It was working fine.
So I’ve launched a ‘Factory Reset’ from android… And something goes wrong… After the reboot, the phone hangs with the warning “unlocked bootloader screen”
I still can access to TWRP, and I noticed that the /system partition don’t exist any more!
I tried to access my phone from ADB to rewrite the system partition, but I couldn’t. I can see my phone from my computer but ADB says ‘Unauthorized device’ … don’t tell me you have to activate the “Developer mode”. Mon phone can’t boot to do this…
I also have an external SD card and the terminal from TWRP is working with root access.
What option I have to resurrect my phone? Is it dead for real?
Please advice.

gnucoder said:
Hello experts,
I already looked and tried different solutions without success…
I have a Moto G (4G) 2015 (XT1072), rooted and with custom recovery TWRP 2.8.0.1, Developer mode activated. It was working fine.
So I’ve launched a ‘Factory Reset’ from android… And something goes wrong… After the reboot, the phone hangs with the warning “unlocked bootloader screen”
I still can access to TWRP, and I noticed that the /system partition don’t exist any more!
I tried to access my phone from ADB to rewrite the system partition, but I couldn’t. I can see my phone from my computer but ADB says ‘Unauthorized device’ … don’t tell me you have to activate the “Developer mode”. Mon phone can’t boot to do this…
I also have an external SD card and the terminal from TWRP is working with root access.
What option I have to resurrect my phone? Is it dead for real?
Please advice.
Click to expand...
Click to collapse
Not dead...just flash a rom, like cyanogen or something and it will be fine. If twrp is there is can be saved

hp420 said:
Not dead...just flash a rom, like cyanogen or something and it will be fine. If twrp is there is can be saved
Click to expand...
Click to collapse
How can I do that if I have no access via ADB? Any how to?

gnucoder said:
How can I do that if I have no access via ADB? Any how to?
Click to expand...
Click to collapse
Well you should have adb access. It's possible with recovery to adb push files, so you should be able to do that. If you have a rom already stored on your phone, you can just flash that so it will at least boot. Also, you can try fastboot. Since you know you have twrp, you must have fastboot by default...flash a factory image.

Thank you for your support hp420, but unfortunately I can't fastboot neither adb I don't know what to do
Code:
evon:x azeus$ ./fastboot devices
evon:x azeus$ ./fastboot flash partition gpt.bin
< waiting for device >
evon:x azeus$ ./fastboot devices
evon:x azeus$ ./adb devices
List of devices attached
ZX1C228MGH unauthorized

gnucoder said:
Thank you for your support hp420, but unfortunately I can't fastboot neither adb I don't know what to do
Code:
evon:x azeus$ ./fastboot devices
evon:x azeus$ ./fastboot flash partition gpt.bin
< waiting for device >
evon:x azeus$ ./fastboot devices
evon:x azeus$ ./adb devices
List of devices attached
ZX1C228MGH unauthorized
Click to expand...
Click to collapse
You need to be in the bootloader to use fastboot commands

Oh man you just saved my phone Thank you very much

gnucoder said:
Oh man you just saved my phone Thank you very much
Click to expand...
Click to collapse
Welcome

Accidentaly formatted all partions

I accidentally formatted all partition and now only have a TWRP. The TWRP only shows the start screen when i go to recovery.
Adb devices show me the device detected. I did a adb push and moved the stock rom 5.1.11 and my twrp recovery to the sdcard using the command adb push. I am struck here because i cannot get to the twrp screen which gives you option to install/wipe etc.
Can somebody please guide me if there is a way to recover or install the .zip files I have copied to sdcard. Thanks in advance

You need to fastboot flash the default stock rom, and then re root/install TWRP etc etc

Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.

SachinGopal said:
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
Click to expand...
Click to collapse
You need to go to this thread... https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Download the version of OOS you want (5.1.11) and unzip the contents in to a folder and run the flash-all.bat file and let it install to all partitions. Just follow this instructions in the thread and you will be fine.

Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >

Thank you so much it worked when I tried. Grateful . Will donate the Dev for that bat script.

SachinGopal said:
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Click to expand...
Click to collapse
You need to be in fastboot mode.
Either adb reboot bootloader from inside android or from a powered off phone, hold Volume Up and power on.

problems with phone decryption

I have older device, it is htc 10.
I was using corporate MS Teams on it however at some point corporate required encryption to be done on my phone i got poop-up and trigger encryption.
Now phone consume much more power, i think because of the encryption.
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?

It can't be undone normally. Back up all critical data, factory reset.
I never encrypt any device as it will come back to bit you sooner or latter.
-Never- encrypt backup data drives or set PC bios passwords. You are the one most likely to get locked out, sometimes through no fault of your own!!!

seba.kwiat said:
...
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?
Click to expand...
Click to collapse
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off

jwoegerbauer said:
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off
Click to expand...
Click to collapse
Could u recommend any terminal app, I have tried a couple but looks like recovery command is missing on them?

Question Write to /data/... folder

I just switched to the Pixel 6a and have botched something with an app I use.
I have the app's files from the old phone, which were in /data/data/com... folder, and want to overwrite files on the new phone, with them.
I did "adb pull ..." on the old phone to get files on the computer and intended to do "adb push ..." to the new,
but I can't get it to connect to adb, in recovery mode.
The old phone had TWRP.
When I rebooted it into recovery and connected with cable to PC, "adb devices" would print:
List of devices attached
<device_ID> recovery
On the new one, when I go into recovery (stock), "adb devices" prints nothing.
When I select the sideload option, "adb devices" prints:
<device_ID> sideload
In this sideload mode, the pull, push, shell... adb commands don't work.
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?

Stock recovery isn't TWRP! You have no access to anything in your file system.

Svrmirac said:
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Click to expand...
Click to collapse
Use TWRP. Stock recovery has no adbd, only a minimal adbd with no features except a sideload option for signed update.zips

Thank you for the suggestion, @WoKoschekk, but I don't think I can do that.
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
I seem to be at an impasse, with the stock ROM/recovery.

Svrmirac said:
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
Click to expand...
Click to collapse
Yes, (un-)locking wipes all data. But that is exactly the reason why /data is inaccessible from recovery. To keep your data safe.

I don't even think TWRP is a thing for modern pixels

ctfrommn said:
I don't even think TWRP is a thing for modern pixels
Click to expand...
Click to collapse
No it isn't the closing thing you'll find to TWRP on Pixel 6A is the Lineage Recovery.
I would suggest using a tool like Titanium Backup. That allows the saving and reinstating of apps.

Booting a custom recovery requires unlocking the bootlader, which I don't want to do now.
Titanium backup requires rooting as well...
Thank you for the suggestions but I'm counting this one as lost.

You won't be able to directly write to the /data/data/com.your.packagename folder without root. The only options I can think of are
1. Using adb backup... backup your app data from your old phone and restore it to the new phone
Bash:
To backup
# adb backup -noapk com.your.packagename -f backup.adb
To restore
# adb restore backup.adb
2. If the app in question is debuggable, you can assume the application permission and access the folder
Bash:
# adb shell
bluejay:/ $ run-as com.your.packagename
bluejay:/ $ cp -r /storage/emulated/0/Download/backup/* /data/data/com.your.packagename