Database Develop

GrapheneOS - waiting for any device

Hello,
i tried to install GrapheneOS on my phone and it start with flashing. but then fastboot doesnt recognize my device. i tried in Windows 10 and also in Linux Mint with the same problem. Can someone help me pls?
there you can see on which step its stoped:
Code:
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.592s]
Finished. Total time: 1.201s
Rebooting into bootloader OKAY [ 0.063s]
Finished. Total time: 0.063s
Sending 'radio_a' (82692 KB) OKAY [ 2.143s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g8150-00063-200702-B-6648947
(bootloader) Flashing partition modem_a
OKAY [ 0.655s]
Finished. Total time: 3.058s
Rebooting into bootloader OKAY [ 0.039s]
Finished. Total time: 0.039s
Erasing 'avb_custom_key' OKAY [ 0.222s]
Finished. Total time: 0.340s
Sending 'avb_custom_key' (1 KB) OKAY [ 0.149s]
Writing 'avb_custom_key' OKAY [ 0.228s]
Finished. Total time: 0.558s
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.036s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00063-200702-B-6648947
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.070s]
Checking 'version-bootloader' OKAY [ 0.070s]
Checking 'version-baseband' OKAY [ 0.070s]
Setting current slot to 'a' OKAY [ 0.069s]
extracting boot.img (64 MB) to disk... took 0.282s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.720s]
Writing 'boot_a' OKAY [ 0.456s]
extracting dtbo.img (8 MB) to disk... took 0.047s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.324s]
Writing 'dtbo_a' OKAY [ 0.119s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.137s]
Writing 'vbmeta_a' OKAY [ 0.070s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.063s]
< waiting for any device >
sorry for my bad english

March 2021 Tmobile Factory Image

Did the march Tmobile factory image come out yet? I'm rooted and can't tell when an update appears. Can we flash-all the MAR 2021 factory image if it doesn't specifically say Mar 2021 Tmobile?...it does for Feb.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

trizzv said:
Did the march Tmobile factory image come out yet? I'm rooted and can't tell when an update appears. Can we flash-all the MAR 2021 factory image if it doesn't specifically say Mar 2021 Tmobile?...it does for Feb.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
Yes it has. The updates are released on the first Monday of the month, which was the 1st this month. This month's update for T-Mobile and every carrier except Virgin Mobile/UK is 11.0.0 (RQ2A.210305.006, Mar 2021)
Add a calendar reminder for every first Monday and this to your favorites to take you right to the redfin (Pixel 5) images: https://developers.google.com/android/images/#redfinimages

JimSmith94 said:
Yes it has. The updates are released on the first Monday of the month, which was the 1st this month. This month's update for T-Mobile and every carrier except Virgin Mobile/UK is 11.0.0 (RQ2A.210305.006, Mar 2021)
Add a calendar reminder for every first Monday and this to your favorites to take you right to the redfin (Pixel 5) images: https://developers.google.com/android/images/#redfinimages
Click to expand...
Click to collapse
Hello PLEASE help! just unzipped the file and removed (-w) from flash-all.bat and executed. stuck in bootloop. keeps going back to Your device is corrupt. it can't be trusted and may not work properly. Am i supposed to extract the image file too before doing flash all?

I can boot into fastboot mode

Sending 'bootloader_a' (8754 KB) OKAY [ 0.316s]
Writing 'bootloader_a' (bootloader) Flashing Pack version r3-0.3-7051238
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.449s]
Finished. Total time: 1.033s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.051s
Sending 'radio_a' (149284 KB) OKAY [ 3.540s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00069-210128-B-7108850
(bootloader) Flashing partition modem_a
OKAY [ 0.538s]
Finished. Total time: 4.345s
Rebooting into bootloader OKAY [ 0.056s]
Finished. Total time: 0.061s
--------------------------------------------
Bootloader Version...: r3-0.3-7051238
Baseband Version.....: g7250-00069-210128-B-7108850
Serial Number........: 0A261FDD4001ZG
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.066s]
Checking 'version-bootloader' OKAY [ 0.067s]
Checking 'version-baseband' OKAY [ 0.064s]
Setting current slot to 'a' OKAY [ 0.083s]
extracting boot.img (96 MB) to disk... took 0.471s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'boot_a' OKAY [ 0.306s]
extracting dtbo.img (16 MB) to disk... took 0.069s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.477s]
Writing 'dtbo_a' OKAY [ 0.112s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_a' OKAY [ 0.075s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.138s]
Writing 'vbmeta_system_a' OKAY [ 0.076s]
extracting vendor_boot.img (96 MB) to disk... took 0.291s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'vendor_boot_a' OKAY [ 0.305s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.068s]
< waiting for any device >
this is the error i get when i unzip the image into the same file

i'm trying to just factory reset (by keeping -w) in the flash-all but it is still booting me back into fastbootd right after google logo. How do i fix it?

trizzv said:
i'm trying to just factory reset (by keeping -w) in the flash-all but it is still booting me back into fastbootd right after google logo. How do i fix it?
Click to expand...
Click to collapse
while your device is in fastbootd, open "Windows Device Manager" (Right-click Windows -> Device Manager)
There, you might see your device with an exclamation mark.
Right click your device and choose update driver automatically.

STUCK IN BOOTLOOP March tmobile update

Hello PLEASE help! just unzipped the march factory image file and removed (-w) from flash-all.bat and executed. stuck in bootloop. keeps going back to Your device is corrupt. it can't be trusted and may not work properly.
Am i supposed to extract the image file too before doing flash all?
keeps going into fastboot-d after it get stucks on the GOOGLE boot up logo

I am able to get into fastboot mode

Sending 'bootloader_a' (8754 KB) OKAY [ 0.316s]
Writing 'bootloader_a' (bootloader) Flashing Pack version r3-0.3-7051238
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.449s]
Finished. Total time: 1.033s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.051s
Sending 'radio_a' (149284 KB) OKAY [ 3.540s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00069-210128-B-7108850
(bootloader) Flashing partition modem_a
OKAY [ 0.538s]
Finished. Total time: 4.345s
Rebooting into bootloader OKAY [ 0.056s]
Finished. Total time: 0.061s
--------------------------------------------
Bootloader Version...: r3-0.3-7051238
Baseband Version.....: g7250-00069-210128-B-7108850
Serial Number........: 0A261FDD4001ZG
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.066s]
Checking 'version-bootloader' OKAY [ 0.067s]
Checking 'version-baseband' OKAY [ 0.064s]
Setting current slot to 'a' OKAY [ 0.083s]
extracting boot.img (96 MB) to disk... took 0.471s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'boot_a' OKAY [ 0.306s]
extracting dtbo.img (16 MB) to disk... took 0.069s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.477s]
Writing 'dtbo_a' OKAY [ 0.112s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_a' OKAY [ 0.075s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.138s]
Writing 'vbmeta_system_a' OKAY [ 0.076s]
extracting vendor_boot.img (96 MB) to disk... took 0.291s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'vendor_boot_a' OKAY [ 0.305s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.068s]
< waiting for any device >

trizzv said:
Am i supposed to extract the image file too before doing flash all?
Click to expand...
Click to collapse
no

I'd suggest sideloading the OTA, but it seems to late for that. Maybe.........
Are you sure you edited the flash-all correctly? Maybe you took something out that you shouldn't have. It could be as simple as a space

Suddenly hang at the "booting into fastboot" message when flashing.

Hey, I've been searching all through XDA and google to find someone with the same issue, but I can't find it. Plenty of experience flashing/rooting/etc. I've had a Pixel 4XL for a while now, never had an issue with custom roms. But lately I can't get it to take ANY flashes except official OTA sideloads or the online Android Flash Tool. Anytime I try to do a normal ./flash-all.sh it will flash normally UNTIL it hits the "booting into fastboot" (fastbootd) command. Then it will bring up the fastbootd screen and do absolutely nothing no matter how many hours you let it sit there while you resent its existence. Has anyone had experience with this? I'd really appreciate the help. Here is the full read out of my terminal when I flash (I've tried zsh and bash, i've made them executable with chmod +x, and have used them both with sudo and without):
bash-3.2$ sudo -s ./flash-all.sh
Password:
Sending 'bootloader_b' (8845 KB) OKAY [ 0.330s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.4-7617419
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 0.963s
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
Sending 'radio_b' (82708 KB) OKAY [ 2.099s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00111-210817-B-7650554
(bootloader) Flashing partition modem_b
OKAY [ 0.617s]
Finished. Total time: 3.006s
Rebooting into bootloader OKAY [ 0.079s]
Finished. Total time: 0.079s
Erasing 'avb_custom_key' OKAY [ 0.220s]
Finished. Total time: 0.370s
Sending 'avb_custom_key' (1 KB) OKAY [ 0.140s]
Writing 'avb_custom_key' OKAY [ 0.231s]
Finished. Total time: 0.590s
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
--------------------------------------------
Bootloader Version...: c2f2-0.4-7617419
Baseband Version.....: g8150-00111-210817-B-7650554
Serial Number........: 9A251FFBA00481
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.070s]
Setting current slot to 'b' OKAY [ 0.079s]
extracting boot.img (64 MB) to disk... took 0.224s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.670s]
Writing 'boot_b' OKAY [ 0.431s]
extracting dtbo.img (8 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.121s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_b' OKAY [ 0.077s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_system_b' OKAY [ 0.077s]
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.070s]

I forgot to mention that I've also manually flashed a bunch of bootloaders and boot images to see if would help, but still nothing. Also twrp doesn't load when I boot a twrp img.

ashtonv59 said:
I forgot to mention that I've also manually flashed a bunch of bootloaders and boot images to see if would help, but still nothing. Also twrp doesn't load when I boot a twrp img.
Click to expand...
Click to collapse
I have nothing to offer but the obvious which is to confirm the latest binaries, new data cable (not C-C) and try a different (windows) machine you have adb/fastboot set up on. With an unlocked bootloader, flashing the untouched script/batch file should return ANY device to the OOB state.

v12xke said:
I have nothing to offer but the obvious which is to confirm the latest binaries, new data cable (not C-C) and try a different (windows) machine you have adb/fastboot set up on. With an unlocked bootloader, flashing the untouched script/batch file should return ANY device to the OOB state.
Click to expand...
Click to collapse
I actually figured it out last night. I still don't know the cause of it, but if anyone ever has this issue this is the solution.
Extract the download. Notice there is a ZIP FILE (this is important as it is the userspace data for each partition) within the extracted folder along with the bootloader, radio, flash-all, flash-base, etc. Execute the flash-all script like normal. It will hang like I described. Once fastbootd loads, hit CTRL+C so you have control of your terminal again. Type the command
Code:
fastboot update -w ZIPFILETHATIMENTIONEDEARLIER.ZIP
MAKE SURE YOU TYPE -w, otherwise the phone will hang on the Google logo screen until you turn it off. The reason the phone gives is the "no valid boot slot" message. Anyway, once you hit enter after that command, you'll see it flash each partition, then it boots the system automatically. BOOM you'll be at the setup screen in no time.
I don't know why it hangs. It seems to related to my computer or terminal. I have the newest MacBook Air. But yeah, that's the solution. Happy flashing. I hope this might help people in the future.
Peace out.

@ashtonv59
Glad you got things working. That line is already in the untouched script (and the DOS *.bat file) The -w flag is an instruction to wipe the user data partition. This flag is often removed by users to "dirty flash" or otherwise update without losing their data. For users like me who manually update every single month using the full factory image, it is always removed. Leaving the -w flag in (or using it manually on the command line is used to remedy flashing issues when all else fails and the user is willing to lose all their data.

See below reply.

v12xke said:
@ashtonv59
Glad you got things working. That line is already in the untouched script (and the DOS *.bat file) The -w flag is an instruction to wipe the user data partition. This flag is often removed by users to "dirty flash" or otherwise update without losing their data. For users like me who manually update every single month using the full factory image, it is always removed. Leaving the -w flag in (or using it manually on the command line is used to remedy flashing issues when all else fails and the user is willing to lose all their data.
Click to expand...
Click to collapse
Yeah, the problem though is the script only actually executes the first part, what would be considered flash-base.sh. Since the terminal hangs when it boots to fastbootd, it never executes the the userspace update, let alone the -w variable at the end of the script. So since you have to manually execute
Code:
fastboot update
, you also have to manually add the
Code:
-w
variable in:
Code:
fastboot update -w USERSPACEZIP.zip
, or else you still have a pretty paperweight. It's an easy thing to overlook, but it is absolutely necessary to successfully flash and have a functioning device.

Question Help Recovering Data From Device with no Display/Touch

Hi there. My Pixel 5a has a motherboard issue, and needs to be returned to Google for warranty. I am trying to recover my files from the device before I send it in, but I'm having issues. For some reason, even though I have enabled usb debugging and issued commands through this laptop before, it says adb unauthorized when I issue the command "adb devices". So I downloaded my factory image, removed the "-w" from the flash all bat file, and attempted to flash to see if that would fix issue. However, it appears that for some reason I'm missing fastboot d. Here is the screen I get when attempting to flash.
Sending 'bootloader_b' (8762 KB) OKAY [ 0.122s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b9-0.4-7758098
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 0.771s
Rebooting into bootloader OKAY [ 0.029s]
Finished. Total time: 0.056s
Sending 'radio_b' (149780 KB) OKAY [ 0.970s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_b
OKAY [ 0.782s]
Finished. Total time: 2.058s
Rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: b9-0.4-7758098
Baseband Version.....: g7250-00161-211008-B-7807492
Serial Number........: 19241JEG503250
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.061s]
Checking 'version-bootloader' OKAY [ 0.057s]
Checking 'version-baseband' OKAY [ 0.055s]
Setting current slot to 'b' OKAY [ 0.071s]
extracting boot.img (96 MB) to disk... took 0.384s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 0.623s]
Writing 'boot_b' OKAY [ 0.472s]
extracting dtbo.img (16 MB) to disk... took 0.104s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.192s]
Writing 'dtbo_b' OKAY [ 0.120s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.126s]
Writing 'vbmeta_b' OKAY [ 0.062s]
extracting vbmeta_system.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.122s]
Writing 'vbmeta_system_b' OKAY [ 0.059s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.536s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (98304 KB) OKAY [ 0.625s]
Writing 'vendor_boot_b' OKAY [ 0.469s]
extracting super_empty.img (0 MB) to disk... took 0.002s
Rebooting into fastboot OKAY [ 0.049s]
< waiting for any device >
And then it hangs there indefinately. The only way I can get out of here is by pressing the power and volume down simutaneously. Then the dialogue adds this line
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Press any key to exit...
Can anyone help me get to a point where I can recover my data? Please, and thanks in advance.

Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.

danielhatzor said:
Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.
Click to expand...
Click to collapse
Hi there, thanks for responding. Actually, yes, my bootloader is unlocked. The phone is rooted. I have enabled usb debugging in the past, but for some reason it is still unauthorized. I currently cannot even get the os to boot, but I cannot figure out why because no screen. When I try to flash the factory image, removing the "-w" so my data isn't wiped, the process hangs att the portion where it boots to fastbootd and will not go any further.
I'm going to try to boot into twrp again. I seem to remember that I tried this, but let's see.
If you have any other info or advice, it would be greatly appreciated.
Edit: I just tried to boot into twrp, and I get an error message. It is : (bootloader) boot.img missing cmdline or OS version
I have attached a picture of the command line messages. Maybe someone here can see something that would point to something that would help

Is it possible you flashed an incompatible / corrupted factory image for your phone?
https://www.reddit.com/r/LineageOS/comments/kn257b

Yeah, I just went and double checked, and then reflashed to see. I def have the July barbet image, which is for the 5a, my device. It just won't work.
Google is trying to get me to either take the device to ubreakifix, which when I try tell me that they do not do motherboard issues, or send the device to them, which I am hesitant to do because I feel they are going to wipe the device. Very frustration situation. I've always used nexus/pixel devices becuase of the readily available info on here, but this just doesn't seem to be a popular development device, and I can't seem to find a way. I know there is some command or series of commands that will fix this issue, I just can't seem to find it.
Thank you again for replying and attempting to help. Truly appreciated. Hopefully someone will stumble across this and let me know.