Database Develop

ICS upgrade - boot loop - can't fix - bricked?

I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.

jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.

tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.

jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes

jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers

Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​

jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.

tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***

jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.

Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app

tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks

jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.

tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all

tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake

Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app

Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files​
Any ideas anyone?

What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app

Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted

Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.

jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.

[Q] HELP - Bricked HTC One m7 (m7ul)

Hi,
I am after some help trying to get my HTC One back up and running.
I unlocked the bootloader using the htcdev website and installed cyanogen mod.
This was working fine for quite some time, until I recently wanted to download an app that was only available on stock phones.
I tried editing the /system/build.prop file to change the version to fool the app store but that didn't work.
Then when I restored my backup build.prop, I think I got the permissions wrong or something and the phone rebooted and went into a boot loop.
Then I followed a guide to get twrp on the device which worked.
Then I followed another guide attempting the restore the device to stock using the commands
Code:
fastboot oem lock
and
Code:
fastboot oem rebootRUU
.
Now the phone is stuck in a boot loop. All I can do is hold down power and volume down to get to HBOOT and Fastboot. If I try and load recovery it reboots to the same menu.
What else can I try, or do I now have a new paperweight?
Thanks for any suggestions.
- gatamous

Also,
I have tried flashing the stock recovery but I get signature errors.
Code:
C:\Android\android-sdk-windows-r24.0.2\platform-tools>fastboot flash recovery recovery_2.24.980.2.img
target reported max download size of 1443966976 bytes
sending 'recovery' (8752 KB)...
OKAY [ 1.140s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.846s

OK,
Never mind.
I was unable to unlock my bootloader because I was typing fastboot flash unlock token Unlock_code.bin instead of unlocktoken being one word.
One I fixed that the twrp recovery started again.
Once I opened that the phone apeared on my PC as a storage device.
I copied a cyanogen mode zip to that directory then installed it via twrp.
Now I have cyanogenmod working again.
Yay - no longer a brick.
I guess I am out of luck with reverting it to stock if the RUU I need is not available for my carrier - is that right?
If so I'll stay on cyanogen mod and not worry about reverting to stock.
Next time I guess I'll take one of these nandroid backups while the phone is still stock. Hindsight.
- gatamous

[Q] Fastboot flash error - FAILED (remote: unknown command)

Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.

same here

Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825

neverdies said:
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP

jmang98 said:
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
Click to expand...
Click to collapse
what steps have you done so far?
ie: unlock/root/flash recovery?

itsJohnuno said:
what steps have you done so far?
ie: unlock/root/flash recovery?
Click to expand...
Click to collapse
Same problem....

Did anyone who was having this problem end up finding a fix?

This is a problem I have too, need a fix.

Still need a solution. Is this due to lollipop? Cuz back then I was able to unlock the bootloader. LG L90 D415

BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
D405_v20a_patched_aboot??
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
EDIT:
Did you flash D405_v20a_patched_aboot if not, you need to flash D405_v20a_patched_aboot

i also have same poblem d415

me too...same problem D415 tmobile version

Does anyone with this problem have an lg d-415 and android with root? Because I think these commands in a terminal emulator or in an adb shell will fix fastboot:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Or if that doesn't work try this >> https://forum.xda-developers.com/lg...ick-hard-bricked-l90-variants-t3173429/page24
I think this problem is caused by people not unlocking the bootloader.

Same error on LG D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.

aixhinnn said:
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
Click to expand...
Click to collapse
How did you enable fastboot, what commands did you run?

0000.0000.00 said:
How did you enable fastboot, what commands did you run?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.

aixhinnn said:
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
Click to expand...
Click to collapse
Did you try volume down+ power to factory reset and see if that fixes it?

im having this problem too, but on an lg v10 tmobile

17mm said:
im having this problem too, but on an lg v10 tmobile
Click to expand...
Click to collapse
This problem is strange and I'm not sure if it has a solution.

0000.0000.00 said:
This problem is strange and I'm not sure if it has a solution.
Click to expand...
Click to collapse
what i did was get lg bridge and mobile support, let if flash the most current update then used this method to root on the latest 30c update https://forum.xda-developers.com/tm...901-nougat-t3773942/post76711778#post76711778
twrp flashed fine, magisk installed flawlessly, now rooted on latest official update with all kinds of goodies to play with :good:
oh and with magisk you pass safetynet aswell so all good.

Request OEM unlock Huawei P10

Hi all,
I have an incorrect firmware installed for my P10 and lots of things are not working (oreo 8.0). I want to re-flash or rollback to other firmwares but problem is I can't get into TWRP anymore. flashing it doesn't work and although I see in fastboot Phone Unlocked and FRP unlock i have the idea it has to do with the OEM unlock not working properly. It's also not available in the developer options. What;s exactly the link to huawei's page where you can request your phone unlock ID ?
Thanks

Whats not working ?
What is it saying when flashing something through fastboot ?

virusdunil said:
Whats not working ?
What is it saying when flashing something through fastboot ?
Click to expand...
Click to collapse
When I go into the bootloader and want to flash TWRP I get following message:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16494 KB)...
OKAY [ 0.552s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.566s

What is the ADB command youre using ?

virusdunil said:
What is the ADB command youre using ?
Click to expand...
Click to collapse
fastboot flash recovery_ramdisk twrporeo.img
and my twrp oreo name is twrporeo.img

Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img

virusdunil said:
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
Click to expand...
Click to collapse
Same problem...:
C:\Android>fastboot flash ramdisk twrporeo.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16494 KB)...
OKAY [ 0.532s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s

i did a mistake...its really recovery_ramdisk
Look Here...
TWRP

virusdunil said:
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
Click to expand...
Click to collapse
I already tried that but no success. Did a factory reset and now the bootloader is locked again. How can I unlock the bootloader again?
Thanks

1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?

virusdunil said:
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
Click to expand...
Click to collapse
First of all, I've tried to update from Nougat to Orea via Blackballs method in this thread https://forum.xda-developers.com/p10-plus/development/oreo-update-thread-l29c432-t3729907 with the firmware mentioned there
What is not working:
I've managed to do the first part (oreo install), but:
- SImcard has 'No service
- Can't flash TWRP
- Bootloader / phone locked in Fastboot
- I can't remember how I unlocked the P10 last year (I have a P10 L09-VTR, rebranded to L29-VTR and now 'working' on a VKY P10 plus rom)

Question Help installing LineageOS on Pixel 5a5g (Can't unlock)

Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?

Did you remove your screenlock and Google account before flashing?

Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue

From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)