Develop Bugs

[Q] PB31IMG Not Progressing....

Was gifted a Dinc that was stuck on boot screen, reset did nothing.
DL'd the GB PB31IMG.zip (from Doug's site), ran in HBOOT .... Update is now stuck on step 2, updating the radio.
It reads like this:
Parsing...[SD ZIP]
[1] BOOTLOADER - FAIL-PU
[2} RADIO_VZ - Updating
The progress bar on the right hand side looks to be 95% full, but nothing has changed in, oh, maybe 30 mins.
Don't want to power down quite yet and risk junking it. Maybe should have tried the Froyo stock image??

Tried the Froyo image... same result, except it passed boot loader.
Could HW issues prevent radio updating?
Sent from my ThunderBolt using Tapatalk 2

What I'm looking at.... another 30 min in. May try some older stock images.
Sent from my ThunderBolt using Tapatalk 2

Each time you power down the device during a critical update like this you have a chance of bricking. I hate to say you may have gotten a defective phone.

Yeah it's looking that way. I'm curious as to just what is defective though. It's a freebie so I'm not torn over it. I'll keep playing and see if something works.
Sent from my cm_tenderloin using xda app-developers app

Have you tried a newer ruu that will update hboot? Then you could unlock your bootloader flash a recovery, do a full wipe, and try to flash a rom. Or unlock,fastboot flash misc partition, and try to downgrade to froyo again (hopefully the radio takes), then flash recovery and then the s-off patch. However the radio not updating dosent seem like a good sign.

I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.

manhatton said:
I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.
Click to expand...
Click to collapse
You need at least 1.02 for the identifier token stuff to work. You should be able to flash just the HBOOT through the bootloader with the PB31IMG.zip from dinc.does-it.net (the link in cmlusco's sig).

Just attempted that and may have found the problem, although I have no clue what it means. On my way to flashing the HBOOT here's where it failed:
c:\Android>fastboot oem rebootRUU
...
(bootloader) msm_nand_erase: failed, block 4091, status 0xC001A0
(bootloader) [ERR] Bad block found: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_erase: failed, block 4092, status 0xC001A0
(bootloader) [ERR] Bad block found: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_erase: failed, block 4093, status 0xC001A0
(bootloader) [ERR] Bad block found: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_erase: failed, block 4094, status 0xC001A0
(bootloader) [ERR] Bad block found: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_erase: failed, block 4095, status 0xC001A0
(bootloader) [ERR] Bad block found: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261824): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261824
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261888): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261888
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261952): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261952
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262016): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262016
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262080): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262080
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) [ERR] <Error>partition_write::Too many bad blocks(out of ran
(bootloader) ge)
OKAY [ 0.275s]
finished. total time: 0.277s
After that it shutoff. Any clue what this indicates?

Now, I don't what this is.... Tried rebooting into RUU again and had a different result:
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6A800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 45
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6B000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 46
......40 some odd iterations of this later.....
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 86
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 87
There was more, but wouldn't show in the window. It also did not shutoff this time, however the command prompt is hung and I cannot navigate the menu with the rocker. ODD

Did you try to flash the bootloader or the ruu? You can only flash a seperate bootloader if you are s-off.

I tried running the RUU executable from the htcdev site first, when that didn't communicate with the phone I tried the 'oem rebootRUU' command to try and flash the 1.07 HBOOT from there. I was thinking of trying to use the 'flash bootloader' command, but figured it wouldn't work s-on.

To use the ruu exe the phone must be booted. And as i said before you cant flash an hboot only update unless you are s-off. You need to flash this http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot. Place the file on your sdcard in no folders, named eaxctly PB31IMG.zip. Boot to hboot. It should automaticly find the file and prompt you to press vol up to install. Or you can do the fastboot oem rebootRUU way.

Right, right, right....
The thread was started because flashing the stock image PB31IMG wasn't working, a subsequent step was attempting oem rebootRUU which failed, and I acknowledged the s-on problem.
I'll try the stock image you provided to see if it takes.

Ugggh, this phone....
Well, that image progressed a little further than the first two. Passed bootloader, then...
1 RADIO_VZ - FAIL-PU
2 BOOT - OK
3 RECOVERY - OK
4 SYSTEM - Updating....
Stuck like this for 15 minutes. Seeings how the HBOOT was successfully updated to 1.07, I'm sorely tempted to pull the batt and try to unlock now. Guess I can't make it worse! Here it goes....

Correction. I made it worse. No booting of any sort now.

Not even hboot? Did the rest of the ruu complete or did you stop it?

Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2

More likely the batttery pull did it. Sadly we won't know. I hope that you can figure out something.
Sent from my Galaxy Nexus using Tapatalk 2

manhatton said:
Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
It was radio 2.15.10.12.20 and it can be flashed over it self without issue, i have done it several times my self. The md5 is just the file url with .md5 on the end ( http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.md5 ).
All files on dinc.does-it.net have an md5.

Pixel XL bricked, bootloader locked and recovery doesn't work.

Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Useful logs:
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:352693081633543
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012901-1702171013
(bootloader) version-bootloader:8996-012001-1704121145
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT7370201155
(bootloader) kernel:lk
(bootloader) product:marlin
all:
finished. total time: 2.243s
./flash-all.sh (8.0.0-stock-opr3.170623.007):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32268 KB)...
OKAY [ 1.076s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.175s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'radio_a' (57272 KB)...
OKAY [ 1.952s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.050s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.150s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device
failed to extract 'vendor.img': I/O Error
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
error: file_write: write: No space left on device
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is '8996-012001-1704121145'.
Update requires '8996-012001-1706221457'.
finished. total time: 0.300s
./flash-all.sh (7.1.2-stock-njh47d):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32380 KB)...
OKAY [ 1.088s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.187s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.247s
target reported max download size of 536870912 bytes
sending 'radio_a' (57240 KB)...
OKAY [ 1.924s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (26001 KB)...
OKAY [ 0.951s]
writing 'boot_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.401s

zades9 said:
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Click to expand...
Click to collapse
I assume that you have tried fastboot boot with the correct twrp image?

I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".

mikefnz said:
I assume that you have tried fastboot boot with the correct twrp image?
Click to expand...
Click to collapse
I get this log:
Code:
[cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.001s

Pain-N-Panic said:
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
Click to expand...
Click to collapse
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.

zades9 said:
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20

mikefnz said:
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
Click to expand...
Click to collapse
I can't enable Bootloader Unlocking from the developer settings because the device is bricked.

@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.

Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?

comat0se said:
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
Click to expand...
Click to collapse
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

tdct12 said:
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Click to expand...
Click to collapse
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!

Bryanx86 said:
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Click to expand...
Click to collapse
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/

zades9 said:
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.

zades9 said:
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
Click to expand...
Click to collapse
I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope

Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as
~$ fastboot --version
fastboot version -4022467
I would also give the November image a try.

Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!

Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b

dictionary said:
Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
Click to expand...
Click to collapse
Code:
C:\Users\cristian>fastboot --set-active=_b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.076s
C:\Users\cristian>fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.292s
I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer

Bootloop fix for Nexus 7 2013 when flashing doesn't help

This practical solution I wanted to share here after i couldn't find a solution online is for Nexus 7 devices that can boot into Fastboot. If your device can't boot into fast boot anymore try this solution by K23m from here. And if your device have instead a faulty eMMC that might need replacement or else check here instead.
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop two days ago. I used twrp recovery to wipe it all, refresh lineage os or stock ota, yet i couldn't get past the boot loop. Ill spill the beans early here, It fixed and it needed me to zero out all the free space of the eMMC. as soon as i did that i got back to a 100% reliability and fast speeds like the first time i bought it.
But first was how to boot into a working android image to download and run the zeroing utility. The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz" you can google it but ill provide this mirror link just in case it disappears.
I believe that my problem was that i had little space left and it got corrupted in some way maybe because of bad Trim process. in any case the following old factory image is small and have the highest (only?) chance to boot once and allow to reset the empty space values int he eMMC.
I started by following the process under fast boot:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15j.zip
Try booting 4 times if it doesn't work add this step before:
Download the great restore script and files from "[TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)" here at XDA and download the "Nexus7_2013_KTU84P_Restore.zip WIFI Flo" if you're like me or the other corresponding image for your Nexus 7 version.
First copy the files of the razor-jss15j-factory from the compressed archive inside the same folder as the restore archive and
Run these fast boot commands from within:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash recovery twrp-3.2.1-0-flo.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot -w
fastboot -w update image-razor-jss15j.zip
fastboot flash boot boot.img
fastboot reboot
Try booting 4 times with at least one switched off period of 20mn in between till you boot in. ( it is random and its not guaranteed it will work for you like i did for me)
I know some command are redundant and might make you think its stupid to do so but believe me when i say i spent 2 days non stop trying everything i can short of opening the device to heat gun the eMMC chip
These are the last steps i took to finally boot in and i repeated the process as i tried the first time to flash newer images in the hope they will boot too but to no avail.
Now that you booted in the old android version first go to the App Store and download a free zeroing app like" Secure Eraser " by Giuseppe Romano from the app store. after you run it twice, you can reinstall lineage os or your favourite stock version and be relieved.
I hope this amateurish post help you not discard too early your beloved Nexus 7 tablet. its only worth for me is manga reading and youtube sometimes, and for that its a wonder.

jackkill said:
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop... The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz"
Click to expand...
Click to collapse
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers

k23m said:
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers
Click to expand...
Click to collapse
Thank you k23m,
Ill add the Fresh persist solution link for those who can’t boot into Fastboot
and the link to the Hardware Nand bricks fix too
As for my experience, I did try google’s recovery firmware and steps, however it proved ineffective. At some point even the recovery partition stopped working and forced me to only use Fastboot afterward. As i looked everywhere on how to fix the stuck boot and tried the proposed software solutions with no avail, i decided to share my practical experience of what worked for me, in hope it helps someone else facing the same problem.
my Nexus 7 device is already around 4 years old and it was a discounted demo unit form a retail store, It is a fact that the amount of read write have already reached a high level that must have wore the Nand quite a bit already. However, as the secure eraser method solved the problem, I don’t believe that doing so once in the 4 years span is much of a risk in comparison. My device was on post Stock Android 4.3 most of the time and was on Lineage OS Android 7 since last year, Trim clearly failed to perform. And many sources online believe that the way Google implemented Trim isn’t complete and think that the decreasing device performance on android devices must be linked to it.
I am convinced that the problem was software, related to Trim somehow, and as the Land chip i own is a Toshiba, it can be ruled out from the known faulty Nand brand some Nexus 7 have. Moreover, no error message was displayed when performing Fastboot operations. everything was executed with success all the time.
Cheers

jackkill said:
However, as the secure eraser method solved the problem...
Click to expand...
Click to collapse
Many things happened during the repair session and I'd not credit "secure eraser" for the speed improvement.
The "secure eraser" app does not require root (to run fstrim) nor trigger TRIM ever! It just fills up empty storage space. Read the reviews - slow, horrible , inefficient. Let me propose an alternative - boot TWRP and run/install my TRIM script - it will optimize the storage space in seconds, without excessive NAND wear out - see the attachments. Run it whenever you feel that Google's TRIM algo is deficient and it's time for manual override...
:highfive:

About to give up on old Nexus 7 2013 (last ditch)
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years. The last months, I pretty only used it for podcasts via the PocketCast (best Podcast app and runs on both the major mobile OS's.)
Anyways, it had been getting caught in these bootloops off and on. The last time it successfully booted was on Sunday (4/29). That session lasted until this past Sunday until it decided to reboot on its on and hasn't been usable since.
I tried the ADB tools on a Windows 10 but the only way Windows would talk to the device was when I set it to Recovery mode with the "Install from ADB". I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.
I should add that I never installed any custom ROMs ,TWRP, or what have you. In fact, I never really paid much attention to the Android Development scene at all until the past couple of days.
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out. I got my money's from it though.
If anyone has any advice on other things to try, I'd be all ears. I'm probably going to move on try my hand with one of the Odroids.

Burgin said:
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years......
Anyways, it had been getting caught in these bootloops off and on........
I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.........
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out.
Click to expand...
Click to collapse
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Please post the output of the following commands:
turn off the Nexus
connect it to your PC
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache​
Next...
go to your folder with fastboot.exe and adb.exe
download twrp-3.2.1-0-flo.img to the folder
also unzip and copy the attached "twrp-log.bat" to the folder
in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
when TWRP is up and running (may ask for ADB driver) and you see the menu, double-click on twrp-log.bat
Note, the above steps must be done withn 3 minutes to ensure complete dmesg log
then you will find a new file twrp.txt in the folder
zip up twrp.txt and attach it to your next post
Actually, as a new XDA user you may not be able to attach files or post links, so upload twrp.txt to http://pastebin.com and post only the subpage part, eg. from https://pastebin.com/9cat4t4X7 post only this 9cat4t4X7
Cheers :good:

First, thank you for the quick reply
Moving on. My problem is I can't get anything from the fastboot command. It just says "Waiting for device".
I assume that my USB drivers are totally wrong and I need to start all over in that regard.
When I read from this page, "developer.android.com/studio/run/oem-usb#InstallingDriver", I gather that there are actually two drivers to install, one for the Google USB driver and another specifically for the Nexus 7. Am I reading this correctly? What is this second driver?
(Oh and I did manage to find what I think to be a better quality USB cable.)
k23m said:
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Cheers :good:
Click to expand...
Click to collapse

Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
fastboot getvar all
Code:
(bootloader) version-bootloader: FLO-04.08
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 07d98df8
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: locked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.043s
fastboot oem gpt-info
Code:
(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB
(bootloader) partition[4].name = persist
(bootloader) partition[4].first_lba = 524288
(bootloader) partition[4].last_lba = 554287
(bootloader) partition[4].size 15000 KB
(bootloader) partition[5].name = m9kefs1
(bootloader) partition[5].first_lba = 655360
(bootloader) partition[5].last_lba = 656919
(bootloader) partition[5].size 780 KB
(bootloader) partition[6].name = m9kefs2
(bootloader) partition[6].first_lba = 656920
(bootloader) partition[6].last_lba = 658479
(bootloader) partition[6].size 780 KB
(bootloader) partition[7].name = m9kefs3
(bootloader) partition[7].first_lba = 786432
(bootloader) partition[7].last_lba = 787991
(bootloader) partition[7].size 780 KB
(bootloader) partition[8].name = fsg
(bootloader) partition[8].first_lba = 787992
(bootloader) partition[8].last_lba = 794135
(bootloader) partition[8].size 3072 KB
(bootloader) partition[9].name = sbl1
(bootloader) partition[9].first_lba = 917504
(bootloader) partition[9].last_lba = 920503
(bootloader) partition[9].size 1500 KB
(bootloader) partition[10].name = sbl2
(bootloader) partition[10].first_lba = 920504
(bootloader) partition[10].last_lba = 923503
(bootloader) partition[10].size 1500 KB
(bootloader) partition[11].name = sbl3
(bootloader) partition[11].first_lba = 923504
(bootloader) partition[11].last_lba = 927599
(bootloader) partition[11].size 2048 KB
(bootloader) partition[12].name = aboot
(bootloader) partition[12].first_lba = 927600
(bootloader) partition[12].last_lba = 937839
(bootloader) partition[12].size 5120 KB
(bootloader) partition[13].name = rpm
(bootloader) partition[13].first_lba = 937840
(bootloader) partition[13].last_lba = 938863
(bootloader) partition[13].size 512 KB
(bootloader) partition[14].name = boot
(bootloader) partition[14].first_lba = 1048576
(bootloader) partition[14].last_lba = 1081343
(bootloader) partition[14].size 16384 KB
(bootloader) partition[15].name = tz
(bootloader) partition[15].first_lba = 1179648
(bootloader) partition[15].last_lba = 1180671
(bootloader) partition[15].size 512 KB
(bootloader) partition[16].name = pad
(bootloader) partition[16].first_lba = 1180672
(bootloader) partition[16].last_lba = 1180673
(bootloader) partition[16].size 1 KB
(bootloader) partition[17].name = sbl2b
(bootloader) partition[17].first_lba = 1180674
(bootloader) partition[17].last_lba = 1183673
(bootloader) partition[17].size 1500 KB
(bootloader) partition[18].name = sbl3b
(bootloader) partition[18].first_lba = 1183674
(bootloader) partition[18].last_lba = 1187769
(bootloader) partition[18].size 2048 KB
(bootloader) partition[19].name = abootb
(bootloader) partition[19].first_lba = 1187770
(bootloader) partition[19].last_lba = 1198009
(bootloader) partition[19].size 5120 KB
(bootloader) partition[20].name = rpmb
(bootloader) partition[20].first_lba = 1198010
(bootloader) partition[20].last_lba = 1199033
(bootloader) partition[20].size 512 KB
(bootloader) partition[21].name = tzb
(bootloader) partition[21].first_lba = 1199034
(bootloader) partition[21].last_lba = 1200057
(bootloader) partition[21].size 512 KB
(bootloader) partition[22].name = system
(bootloader) partition[22].first_lba = 1310720
(bootloader) partition[22].last_lba = 3031039
(bootloader) partition[22].size 860160 KB
(bootloader) partition[23].name = cache
(bootloader) partition[23].first_lba = 3031040
(bootloader) partition[23].last_lba = 4177919
(bootloader) partition[23].size 573440 KB
(bootloader) partition[24].name = misc
(bootloader) partition[24].first_lba = 4194304
(bootloader) partition[24].last_lba = 4196351
(bootloader) partition[24].size 1024 KB
(bootloader) partition[25].name = recovery
(bootloader) partition[25].first_lba = 4325376
(bootloader) partition[25].last_lba = 4345855
(bootloader) partition[25].size 10240 KB
(bootloader) partition[26].name = DDR
(bootloader) partition[26].first_lba = 4456448
(bootloader) partition[26].last_lba = 4456463
(bootloader) partition[26].size 8 KB
(bootloader) partition[27].name = ssd
(bootloader) partition[27].first_lba = 4456464
(bootloader) partition[27].last_lba = 4456479
(bootloader) partition[27].size 8 KB
(bootloader) partition[28].name = m9kefsc
(bootloader) partition[28].first_lba = 4456480
(bootloader) partition[28].last_lba = 4456481
(bootloader) partition[28].size 1 KB
(bootloader) partition[29].name = metadata
(bootloader) partition[29].first_lba = 4587520
(bootloader) partition[29].last_lba = 4587583
(bootloader) partition[29].size 32 KB
(bootloader) partition[30].name = userdata
(bootloader) partition[30].first_lba = 4718592
(bootloader) partition[30].last_lba = 61079518
(bootloader) partition[30].size 28180463 KB
(bootloader) partition[31].name =
(bootloader) partition[31].first_lba = 0
(bootloader) partition[31].last_lba = 0
(bootloader) partition[31].size 0 KB
(bootloader) partition[32].name =
(bootloader) partition[32].first_lba = 0
(bootloader) partition[32].last_lba = 0
(bootloader) partition[32].size 0 KB
(bootloader) partition[33].name =
(bootloader) partition[33].first_lba = 0
(bootloader) partition[33].last_lba = 0
(bootloader) partition[33].size 0 KB
(bootloader) partition[34].name =
(bootloader) partition[34].first_lba = 0
(bootloader) partition[34].last_lba = 0
(bootloader) partition[34].size 0 KB
(bootloader) partition[35].name =
(bootloader) partition[35].first_lba = 0
(bootloader) partition[35].last_lba = 0
(bootloader) partition[35].size 0 KB
(bootloader) partition[36].name =
(bootloader) partition[36].first_lba = 0
(bootloader) partition[36].last_lba = 0
(bootloader) partition[36].size 0 KB
(bootloader) partition[37].name =
(bootloader) partition[37].first_lba = 0
(bootloader) partition[37].last_lba = 0
(bootloader) partition[37].size 0 KB
OKAY [ 0.289s]
finished. total time: 0.290s
fastboot format cache
Code:
fastboot format cache
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 143360 4k blocks and 35840 inodes
Filesystem UUID: 582c2894-53a4-11e8-8bf9-f98baf2837a1
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.510s]
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.522s
---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.

Burgin said:
Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
.....
fastboot format cache
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
....
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.
Click to expand...
Click to collapse
Thank you. It looks like you had to unlock it before running TWRP. I see some errors which should go away after you flash the latest factory image from fastboot. Then before you boot the fresh system, please make sure it is still connected to USB3 or a 2 Amp charger. If or when Android is up and running start an app like StabilityTest or some other heavy load benchmark tool. If there are no problems, disconnect the charger and see how it goes without it.
Your battery's stats:
Code:
<5>[ 3.908325] bq27541_get_psp voltage_now= 4040000 uV
<5>[ 3.909149] bq27541_get_capacity = 70% ret= 71
<5>[ 3.909973] bq27541_get_psp temperature= 287 (0.1¢XC)
<5>[ 3.910980] bq27541_get_psp current_now = 356 mA
<5>[ 3.911804] bq27541_get_psp charge_now (compensated) = 2235000 uAh
<5>[ 3.912811] bq27541_get_psp charge_avg (uncompensated) = 2365000 uAh
<5>[ 3.913635] bq27541_get_psp charge_full = 3161000 uAh
<5>[ 3.914611] bq27541_get_psp charge_design = 4090000 uAh
<5>[ 3.915466] bq27541_get_psp energy_now = 8067000 uWh
<5>[ 3.916442] bq27541_get_psp charge_counter = -51000 uWh
<5>[ 3.917266] bq27541_get_psp power_now = 1438000 uW
<5>[ 3.918243] bq27541_get_psp cycle count = 600
There is a huge drop of "charge_full" and very high "cycle count". I'd say the battery is definitely finished. I bet there are no problems or bootloops when it is connected to a good external power source via a short USB cable.
:highfive:

k23m said:
....
[*]in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
....
Cheers :good:
Click to expand...
Click to collapse
I am a newbie to using TWRP and this is the first time I have attempted to try a Custom ROM for my Nexus 7 2013 (flo).
The above command saved me. I was able to go into TWRP, Wipe, Advanced Wipe, and perform a Wipe of everything except the internal storage.
I then did the adb flash recovery <latest TWRP.img> and now I get the most welcome sight of the TWRP GUI.
Many many thanks.

No slot to boot / error booting boot.img

I have the Pixel 3 xl Unlocked from google.
I was in the Android 10 Q beta and wanted to leave. The Opt-out Android beta site was not working.
I went to flash the newest public release myself off googles firmware website.
I have flashed many android phone from android 6 and up including this pixel 3 xl I am having issues with.
I have had such a hard time the last 4 days getting it to boot I completely wiped my computer and reinstalled a fresh new windows 10 pro.
I re downloaded every. Android Studios , all the SDK files, adb and fastboot, Android 9.0, 9.1, Q beta.
I put everything in the correct location or at least the same place I had everything before where it all worked.
everytime I Flash-all I get the same message / error.
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5343672
(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 msadp_b
(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 cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.328s]
finished. total time: 0.422s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 0.320s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_b
OKAY [ 0.405s]
finished. total time: 0.725s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b1c1-0.1-5343672
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A8Y0FQ0H
--------------------------------------------
checking product...
OKAY [ 0.063s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.344s
Press any key to exit...

try this https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849

That guide was perfect! Thank you!! My pixel 3 xl was up and running in about 15mins or so. The green tea I got to drink at the end was tasty too.

Bricked device, Any chance of recovery?

Ok so a quick insight into what happened first I was trying to manually upgrade my phone (XT1955-4) via fastboot to Android 10 since I never received the update about half way through the flash the phone slipped and disconnected from the cable.
I've tried forcing a reboot, (power button held for 10 secs) nothing shows on screen, no vibrating what so ever, I've tried booting into fastboot (power button and volume down button) still nothing on screen, no vibrating.
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753 I've tried this but all I get is the following.
lsusb (It's detected)
Code:
Bus 001 Device 036: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Terminal output
Code:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
FAILED: qb_flash_singleimage()->device_open()->error opening device
qboot_log.txt
Code:
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
[ 0.000]
[ 0.000] qboot version 3.40
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "/dev/ttyUSB0",
[ 0.000] flags = "0x60",
[ 0.000] addr = "0x5CE6C0D8",
[ 0.000] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1/1-1:1.0/ttyUSB0",
[ 0.000] api.bnr = "0x123E560",
[ 0.000] }
[ 0.000]
[ 0.000]
[ 0.000] Backup & Restore {
[ 0.000] num_entries = 0,
[ 0.000] restoring = "false",
[ 0.000] backup_error = "not started",
[ 0.000] restore_error = "not started",
[ 0.000] }
[ 0.000]
qboot detects the device is EDL
Code:
/dev/ttyUSB0 "QCOM emergency download"
UPDATE 1:
After a little tinkering I managed to get some readout but still no life in the device.
Code:
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.003] ...cpu.id = 186 (0xba)
[ 0.003] ...cpu.sn = 3056566883 (0xb62f8263)
[ 0.003] Opening singleimage
[ 0.004] Loading package
[ 0.010] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.314] Handling things over to programmer
[ 0.314] Identifying CPU version
[ 0.322] Waiting for firehose to get ready
Is there anything else I can do as I do believe it's out of warranty.

roadkill42 said:
Try this have couple more
Click to expand...
Click to collapse
Hi Roadkill yes I tried that blankflash earlier this morning and it did work I managed to get back to the bootloader and flash a stock rom but now I'm unable to downgrade the bootloader to reinstall Stock Pie via LMSA (Lenovo's repair tool doesn't recognise the device after trying to update to Android 10) is there anyway to downgrade the bootloader on moto G devices, my old phone was a Nexus 5 which never gave me the amount of problems the Moto G's are doing.
I am now unable to boot into any "special" mode due to flashing firmware from lolinet and there's no bootable A/B slot on the device if that helps.

BioT3rm said:
half way through the flash the phone slipped and disconnected from the cable.
Click to expand...
Click to collapse
That's not a problem and won't cause any problems.
Each single flash command runs like this:
1. sending the image to the RAM of your device
(that's the reason why using sparse image parts for large files)
2. only after the file has been completely transferred, fastboot will start writing it to the partition out of your RAM
As you can see in your output when flashing a firmware via fastboot, every command states sending... and writing.... It's not possible to interrupt the flashing process by disconnecting the USB cable. If it happens that you disconnect your device, then connect it again and go ahead with the next command.

WoKoschekk said:
That's not a problem and won't cause any problems.
Each single flash command runs like this:
1. sending the image to the RAM of your device
(that's the reason why using sparse image parts for large files)
2. only after the file has been completely transferred, fastboot will start writing it to the partition out of your RAM
As you can see in your output when flashing a firmware via fastboot, every command states sending... and writing.... It's not possible to interrupt the flashing process by disconnecting the USB cable. If it happens that you disconnect your device, then connect it again and go ahead with the next command.
Click to expand...
Click to collapse
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.

BioT3rm said:
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.
Click to expand...
Click to collapse
Which country? I need to know the software channel for your firmware. XT1955-4 seems to be the whole planet...
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
Here are versions for Android 10 available:
https://mirrors.lolinet.com/firmware/moto/ocean/official/

BioT3rm said:
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.
Click to expand...
Click to collapse
That bad key is cause of unlocked bootloader

Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200524
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: removed for security reasons
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 63822FB600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: removed for security reasons
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 07-26-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 25 3: 9:22 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: <not found> <-- This is another issue
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200524
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200524
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200524
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No <-- This is supposed to say Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P0FB
Ok so I think I found the problem @roadkill42 & @WoKoschekk it looks like something went extremely wrong during the flash maybe I was on slot b ?
finally relocked the bootloader fully back to stock, booted the phone up and no sim card is detected, no signal bars are showing and the phone is literally wifi only.
Also another weird thing is that the IMEI is shown in fastboot but not in the sim card menu ?!?
@WoKoschekk My country is England, I've never had a phone do this to me before.

BioT3rm said:
Ok so I think I found the problem @roadkill42 & @WoKoschekk it looks like something went extremely wrong during the flash maybe I was on slot b ?
finally relocked the bootloader fully back to stock, booted the phone up and no sim card is detected, no signal bars are showing and the phone is literally wifi only.
Also another weird thing is that the IMEI is shown in fastboot but not in the sim card menu ?!?
@WoKoschekk My country is England, I've never had a phone do this to me before.
Click to expand...
Click to collapse
It doesn't matter which slot was active while the ROM has been flashed. First of all you flash the gpt.bin (partition table) which will set the active slot to _a.
The downgrade from A10 to 9 is responsible for your mobile network issue. You should unlock your bootloader again and flash the complete firmware a second time.

roadkill42 said:
That bad key is cause of unlocked bootloader
Click to expand...
Click to collapse
WoKoschekk said:
Which country? I need to know the software channel for your firmware. XT1955-4 seems to be the whole planet...
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
Here are versions for Android 10 available:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Click to expand...
Click to collapse
WoKoschekk said:
It doesn't matter which slot was active while the ROM has been flashed. First of all you flash the gpt.bin (partition table) which will set the active slot to _a.
The downgrade from A10 to 9 is responsible for your mobile network issue. You should unlock your bootloader again and flash the complete firmware a second time.
Click to expand...
Click to collapse
Should I unlock - reflash - relock or just unlock - reflash ?
Code:
#!/bin/bash
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem lock
fastboot reboot
That should be enough to completely reflash and lock the device ?

BioT3rm said:
Should I unlock - reflash - relock or just unlock - reflash ?
Click to expand...
Click to collapse
You should have a running system without any errors before locking the bootloader. There is no need to hurry with that. Make sure everything is working.

WoKoschekk said:
You should have a running system without any errors before locking the bootloader. There is no need to hurry with that. Make sure everything is working.
Click to expand...
Click to collapse
Booted and went through device setup still the same issue no network
Screenshot:
https://ibb.co/30zWYyR

Final update
Managed to get networking back by flashing the following rom
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm going to test the device and then relock it later hopefully this is now a solved issue @WoKoschekk @roadkill42 thank you to the both of you during these harrowing times

BioT3rm said:
Ok so a quick insight into what happened first I was trying to manually upgrade my phone (XT1955-4) via fastboot to Android 10 since I never received the update about half way through the flash the phone slipped and disconnected from the cable.
I've tried forcing a reboot, (power button held for 10 secs) nothing shows on screen, no vibrating what so ever, I've tried booting into fastboot (power button and volume down button) still nothing on screen, no vibrating.
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753 I've tried this but all I get is the following.
lsusb (It's detected)
Terminal output
qboot_log.txt
qboot detects the device is EDL
UPDATE 1:
After a little tinkering I managed to get some readout but still no life in the device.
Is there anything else I can do as I do believe it's out of warranty.
Click to expand...
Click to collapse
I have something that might work .was u just flashing certain files not the modem if I were doing that I have something that might get u back to bootloader

Try this have couple more