Database Develop

Trying to flash twrp after flashing stock N rom

Trying to flash TWRP post android N flash and I get this:
sudo /usr/bin/fastboot flash recovery twrp-3.0.2-0-grouper.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (9502 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.148s]
finished. total time: 0.476s
sudo fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13921 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.707s
Not even sure what the error means: (bootloader) has-slot:recovery: not found
I mean, I know what it means, but... how do I fix it since I can't flash the recovery partition now?

NeCr0mStR said:
Trying to flash TWRP post android N flash and I get this:
sudo /usr/bin/fastboot flash recovery twrp-3.0.2-0-grouper.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (9502 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.148s]
finished. total time: 0.476s
sudo fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13921 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.707s
Not even sure what the error means: (bootloader) has-slot:recovery: not found
I mean, I know what it means, but... how do I fix it since I can't flash the recovery partition now?
Click to expand...
Click to collapse
did you unlock your bootloader first?

simms22 said:
did you unlock your bootloader first?
Click to expand...
Click to collapse
Already set to OEM unlocked because it was unlocked before, did the flash again and get this:
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.145s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.471s]
finished. total time: 0.616s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 4.207s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.534s]
finished. total time: 5.741s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22Q3ZV
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.304s]
writing 'boot'...
OKAY [ 0.140s]
sending 'recovery' (13921 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 0.191s]
sending sparse 'system' 1/3 (508909 KB)...
OKAY [ 19.620s]
writing 'system' 1/3...
OKAY [ 7.191s]
sending sparse 'system' 2/3 (524036 KB)...
OKAY [ 19.858s]
writing 'system' 2/3...
OKAY [ 7.148s]
sending sparse 'system' 3/3 (443892 KB)...
OKAY [ 17.295s]
writing 'system' 3/3...
OKAY [ 5.945s]
erasing 'userdata'...
OKAY [ 1.557s]
sending 'userdata' (139061 KB)...
OKAY [ 4.977s]
writing 'userdata'...
OKAY [ 2.552s]
erasing 'cache'...
OKAY [ 0.037s]
sending 'cache' (6248 KB)...
OKAY [ 0.229s]
writing 'cache'...
OKAY [ 0.115s]
rebooting...
finished. total time: 87.805s
You can see that several thins show that they can't be flashed. I have never seen this before and there is nothing I can find with the Googles.

NeCr0mStR said:
Already set to OEM unlocked because it was unlocked before, did the flash again and get this:
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.145s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.471s]
finished. total time: 0.616s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 4.207s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.534s]
finished. total time: 5.741s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
wiping cache...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22Q3ZV
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.304s]
writing 'boot'...
OKAY [ 0.140s]
sending 'recovery' (13921 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 0.191s]
sending sparse 'system' 1/3 (508909 KB)...
OKAY [ 19.620s]
writing 'system' 1/3...
OKAY [ 7.191s]
sending sparse 'system' 2/3 (524036 KB)...
OKAY [ 19.858s]
writing 'system' 2/3...
OKAY [ 7.148s]
sending sparse 'system' 3/3 (443892 KB)...
OKAY [ 17.295s]
writing 'system' 3/3...
OKAY [ 5.945s]
erasing 'userdata'...
OKAY [ 1.557s]
sending 'userdata' (139061 KB)...
OKAY [ 4.977s]
writing 'userdata'...
OKAY [ 2.552s]
erasing 'cache'...
OKAY [ 0.037s]
sending 'cache' (6248 KB)...
OKAY [ 0.229s]
writing 'cache'...
OKAY [ 0.115s]
rebooting...
finished. total time: 87.805s
You can see that several thins show that they can't be flashed. I have never seen this before and there is nothing I can find with the Googles.
Click to expand...
Click to collapse
first try using fastboot flash recovery recovery.img
secondly, try using the flashify app to flash your recovery instead of using code.

No root, so it looks like no flashify.
I tried both fast boot with stock recovery.img and tried flashing Android M to see if I could go back.
At this point I can't get bootloader to change or install recovery partition.
Any help with the issue would be great, tried all the basics already but this seems to be beyond me as to why the recovery partition is no longer flashable.

When I flashed the 7.0 image I got that same error "(bootloader) has-slot:xxxxx: not found" for each image file I flashed with the corresponding image file name in the error message but everything still flashed successfully. I don't think that that error is a fatal error, or at least it wasn't in my case.

alryder said:
When I flashed the 7.0 image I got that same error "(bootloader) has-slot:xxxxx: not found" for each image file I flashed with the corresponding image file name in the error message but everything still flashed successfully. I don't think that that error is a fatal error, or at least it wasn't in my case.
Click to expand...
Click to collapse
Yeah, I think I have to agree here. I did get TWRP flashed, I think my copy was corrupt and I pulled a good copy and flashed it and now I am solid, if only my backups weren't at work
Thanks for the helps people.

NeCr0mStR said:
Yeah, I think I have to agree here. I did get TWRP flashed, I think my copy was corrupt and I pulled a good copy and flashed it and now I am solid, if only my backups weren't at work
Thanks for the helps people.
Click to expand...
Click to collapse
Glad you got it sorted out!

I will admit, I was a bit panicked and started to come to grips with the fact that I may need to just have stock on it... but nope, back to not so stock I go.

Its because of latest adb and fastboot, if u r flashing from computer. Use an old version of adb and fatboot, and u won't see these (boot loader) slot count not found, etc... Anyways flashing would be success

NeCr0mStR said:
I will admit, I was a bit panicked and started to come to grips with the fact that I may need to just have stock on it... but nope, back to not so stock I go.
Click to expand...
Click to collapse
Your first posts states that you were trying to flash twrp-3.0.2-0-grouper.img
Grouper is Nexus 7 (2012). That might have been the problem. Nexus 6 code name is Shamu.

How could I recovery my Nexus 6

Hi,
I was trying to update my Nexus 6 to Android Nougat(nbd90z) today, the system image failed to be flashed. And then I locked the device by mistake. Then I became unable to flash any images.
If I tried to flash any image, it failed and the message is below.
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
If I tried to unlock the device, it failed and the message is below.
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
And because the system image failed to flash, so I can't boot the device to check the 'Allow OEM Unlock'.
Is there any way to recovery my device? Thanks very much for the help.

Below is the text from the command terminal where I tried.
<pre>
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.528s]
finished. total time: 0.657s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.609s]
finished. total time: 5.226s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.161s]
sending 'recovery' (13921 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.208s]
sending sparse 'system' (508909 KB)...
OKAY [ 16.031s]
writing 'system'...
OKAY [ 7.247s]
sending sparse 'system' (524036 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 28.751s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
^C
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition confirmed!
(bootloader) Phone is locked successfully!
OKAY [ 24.319s]
finished. total time: 24.319s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.288s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ geany flash-base.sh
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot reboot
rebooting...
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot flash radio radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ cd /home/zhiming/Project/Nexus/Images/shamu-mob31e/
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ls
bootloader-shamu-moto-apq8084-71.18.img flash-all.bat flash-all.sh flash-base.sh image-shamu-mob31e.zip radio-shamu-d4.01-9625-05.34+fsg-9625-02.111.img
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.327s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.332s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-71.21'.
Update requires 'moto-apq8084-71.18'.
finished. total time: 2.498s
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ cd /home/zhiming/Project/Nexus/Images/shamu-nbd90z/
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.135s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.113s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$
</pre>

ZhimingWU said:
Is there any way to recovery my device? Thanks very much for the help.
Click to expand...
Click to collapse
Flash an OTA image. They're intended to be flashed even on locked systems.

Strephon Alkhalikoi said:
Flash an OTA image. They're intended to be flashed even on locked systems.
Click to expand...
Click to collapse
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.

Strephon Alkhalikoi, thank you very much. I got my device recovered.
I followed the instructions at https://developers.google.com/android/nexus/ota, except replacing Step 3 by below steps to boot into recovery mode.
a. Hold Volume Down key and press Power key to enter fastboot mode.
b. Press Volume Down key to navigate to "Recovery mode" and press Power key.

ZhimingWU said:
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.
Click to expand...
Click to collapse
Do you have recovery installed?
If yes and hopefully TWRP which is best option, just go to recovery, mount phone, transfer OTA image, factory reset, and flash it.
Also, if upgrading from 6.x.x to 7.0.0 you must flash the Nougat bootloader img. which in order to do it, i recommand using Nexus toolkit which you could access only via phone being on.
So what i do recommand is the next thing:
download 6.x.x ota and install it.
boot into phone, unlock developer options and usb debugging, also check the "oem unlocking".
plug the phone to the pc while using an adb program like nexus tookit, unlock bootloader.
then download the Nougat bootloader img, and radio img (not a must). into the pc, and flash it via nexus root toolkit once again.
After your'e done flashing, all you have to do is go to recovery mode and flash the Nougat rom.
And before all that, make sure you have the latest TWRK recovery.

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.

Android 12.1 Custom Rom [Pixel Experience] or any Treble-Enabled Device Development A/AB ROMS on Nord n100

Hello all nord n100 owners. thanks to @bentalebnordine I've found how to Install Pixel experience android 12 on you're device.
Here are the steps below :
1-first backup your phone
2-unlock your bootloader by : fastboot oem unlock
Click to expand...
Click to collapse
3- download and extract the Nord n100 SDK rar file here :
https://drive.google.com/file/d/11zzlWYwxoDcNr8HrjeL4NTZNyxfrugd7/view?usp=drivesdk
Click to expand...
Click to collapse
4-then download the [GSI][UNOFFICIAL][12] Pixel Experience arm64-ab-slim :
PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img.xz
Click to expand...
Click to collapse
5- extract the PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img and put the file in Nord n100 SDK folder
{note that you can put any GSI treble-enabled rom on the SDK folder of your choice, but the extracted image file shouldn't be bigger than 2.7 GB}
** there are plenty other GSI Treble-Enabled ROMS over here : forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
6- open Command Prompt in Nord n100 SDK folder by holding shift button and right clicking mouse.
7- then type :
adb reboot bootloader
fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.049s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 17.266s
fastboot flash product_a product_gsi.img
Resizing 'product_a' OKAY [ 0.013s]
Sending 'product_a' (328 KB) OKAY [ 0.015s]
Writing 'product_a' OKAY [ 0.312s]
Finished. Total time: 0.396s
fastboot erase system_a
Erasing 'system_a' OKAY [ 0.665s]
Finished. Total time: 0.679s
fastboot resize-logical-partition system_a 421000000
Resizing 'system_a' OKAY [ 0.012s]
Finished. Total time: 0.015s
fastboot -w
Erasing 'userdata' OKAY [ 2.078s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.015s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 2.136s
fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
fastboot -w
Erasing 'userdata' OKAY [ 0.188s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 93872792 (45836 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 587] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 621] Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1210] Writing root inode (hot node), 13000 0 200 at of
fset 0x00077824
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013601,
00013602
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077825
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013603,
00013604
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077826
[f2fs_update_nat_root:1431] Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1628] Writing default dentry root, at offset 0
x00013600
Info: Overprovision ratio = 0.940%
Info: Overprovision segments = 431 (GC reserved = 220)
[f2fs_write_check_point_pack: 774] Writing main segments, cp at offset 0x00
000200
[f2fs_write_check_point_pack: 911] Writing Segment summary for HOT/WARM/COL
D_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 938] Writing Segment summary for HOT_NODE, at
offset 0x00000202
[f2fs_write_check_point_pack: 950] Writing Segment summary for WARM_NODE, a
t offset 0x00000203
[f2fs_write_check_point_pack: 961] Writing Segment summary for COLD_NODE, a
t offset 0x00000204
[f2fs_write_check_point_pack: 969] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 989] Writing NAT bits pages, at offset 0x0000
03fe
[f2fs_write_check_point_pack:1010] Writing cp page 1 of checkpoint pack 2,
at offset 0x00000400
[f2fs_write_check_point_pack:1029] Writing cp page 2 of checkpoint pack 2,
at offset 0x00000405
[f2fs_write_super_block:1062] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.010s]
Writing 'userdata' OKAY [ 0.002s]
Erasing 'metadata' OKAY [ 0.023s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 9.997s
fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.141s
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.040s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 10.023s
fastboot flash system PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img [or any other GSI Treble-enabled ROMS]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.012s]
Sending sparse 'system_a' 1/7 (524228 KB) OKAY [ 20.447s]
Writing 'system_a' OKAY [ 2.675s]
Sending sparse 'system_a' 2/7 (524228 KB) OKAY [ 20.208s]
Writing 'system_a' OKAY [ 2.684s]
Sending sparse 'system_a' 3/7 (524252 KB) OKAY [ 20.297s]
Writing 'system_a' OKAY [ 2.693s]
Sending sparse 'system_a' 4/7 (524248 KB) OKAY [ 20.846s]
Writing 'system_a' OKAY [ 2.745s]
Sending sparse 'system_a' 5/7 (524248 KB) OKAY [ 20.274s]
Writing 'system_a' OKAY [ 2.717s]
Sending sparse 'system_a' 6/7 (524204 KB) OKAY [ 21.480s]
Writing 'system_a' OKAY [ 2.771s]
Sending sparse 'system_a' 7/7 (461172 KB) OKAY [ 17.803s]
Writing 'system_a' OKAY [ 2.638s]
Finished. Total time: 199.508s
Click to expand...
Click to collapse
8- enjoy
[note that there might be bugs but Android 12 worth it]

Does this work for the Metro variant?? be2015/ BE82CF ?

I've tested on my BE2013, so make a backup and test.

AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
It applies to all treble enabled devices, more specifically OnePlus devices, note that OnePlus n100 is arm64 a/b device

The full rom is the best.
https://github.com/ponces/treble_build_pe/releases/download/v414-plus/PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img.xz

AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse

sdflowers32 said:
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
Click to expand...
Click to collapse
Thanks that's kind of what I was thinking even though the other poster said it did.

AesopRock127 said:
Thanks that's kind of what I was thinking even though the other poster said it did.
Click to expand...
Click to collapse
You'll find the most useful information on this device in the 4pda forum Here. It's a bit choppy but you'll find info that's pretty much the same across the board. Most useful is the info regarding removing encryption. I've flashed more than 10 different GSI's both A11 and A12 to this device. I've heard one person say they were able to do so on the Metro variant but I never seen any proof and I know I was never able to so best option is to flash the global version to the Metro variant. Also you can unlock the bootloader without a token once you're on global 10.5.5.

.

Děkuji Dlouho jsem hledal ROM pro svůj Oneplus Nord N100 (BE2013). O instalaci vlastní ROM do telefonu jsem neuvažoval, ale po výměně neoriginálního displeje se mi telefon neustále restartoval, nic nepomohlo, tak jsem nainstaloval vlastní ROM Pixel Experience a vše funguje jako předtím.
Moc děkujeme

ringtone for incoming calls are not playing even when im in settings trying to change the ringtone nothings playing but the phone vibrates on incoming calls.
And in the music players songs are playing fine!
Is there any solution for this?

Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?

Mahdi0047 said:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?
Click to expand...
Click to collapse
I tried it with `PixelExperience_Plus_arm64-ab-slim-13.0-20230104-UNOFFICIAL.img.xz` and it didn't work. It booted, but the screen got black as soon as I ended the initial configuration.

I tried Pixel Experience this weekend. Screen flickers and dims. Could be refresh problem. But phone finally got so dark it was unusable. Display would not show anything at all. But the reboot menu was fine.

I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.

Halphix said:
I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.
Click to expand...
Click to collapse
I fixed the issue. For anyone that has this issue download the msm tool and use that to unbrick which will also install android 10. Then update to android 11 which will install it into slot b. This will also wipe any data you have in slot b before this. Then just follow instructions for flashing gsi

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.