Develop Bugs

Issues with Pixel 2XL

Hi, I rooted my Pixel 2XL a couple of weeks ago and just recently decided to remove the root and lock the bootloader. So I just locked the bootloader, which I thought would only delete all data and reset it back to normal. But instead the whole operative system got removed. When I noticed that I tried to install the factory image. But that only gave me errors...
This is what happens every times:
Code:
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
--------------------------------------------
Bootloader Version...: TMZ12a
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Press any key to exit...
And this happens a second time:
Code:
Sending 'bootloader' (55680 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Sending 'radio' (60428 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Unknown error))
getvar:serialno FAILED (Write to device failed (Unknown error))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Unknown error))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Anyone who has any idea what to do?

Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...

CyberpodS2 said:
Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...
Click to expand...
Click to collapse
Thanks for the response. I will make sure I think of that next time. Fortunately it was only the cable that needed switching for it to be able to send the files.

You did the one thing that you must not do. Good luck with unbricking.

I'm stuck - Pixel XL, Unlocked Bootloader, Soft-Bricked, Fastboot Only, No recovery

Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.

ekjean said:
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
Click to expand...
Click to collapse
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide

Homeboy76 said:
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Click to expand...
Click to collapse
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>

ekjean said:
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
Click to expand...
Click to collapse
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.

Homeboy76 said:
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Click to expand...
Click to collapse
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>

ekjean said:
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
Click to expand...
Click to collapse
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but here are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.

Homeboy76 said:
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but hear are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Click to expand...
Click to collapse
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3

ekjean said:
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
Click to expand...
Click to collapse
RIP Pixel/Pixel XL!

hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot

@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
Maybe I will! Did it stay on?

it will stay on the enough time to recover your data

@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
I'm afraid in my case this was the death blow. Let out a few buzzes when attempting to power into fastboot, flashed a red light at the top and then nothing. She was euthanized by freezer around 5PM, 3/2/20, went quietly into that good night surrounded by friends and family at home. RIP Pixel.

did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious

@mateodiaz802 said:
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
Click to expand...
Click to collapse
I wrapped 'er in plastic wrap before putting it in. So it would've been covered. Oh well, stuff happens. Funny thing, I tried it again just to see. It started vibrating and hasn't stopped. XD

i covered the holes with tape, it's more effective, also you should try booting it with "start" optino from the bootloader

[Solved] Stuck at bootloader, can't flash factory image.

Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img

fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.

fjgato said:
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.
Click to expand...
Click to collapse
Just report your thread to the moderator team designated to your area, which I am not, and have them change the thread title to what you want. Glad you figured out your problem :good::laugh:

fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
I'm having the same trouble that you did got the same stuff to pull up and everything all you did was switch out your data cable

Can´t flash anything on moto G7 Plus. pls help 🙏🙏🙏

Hi!
I recently unlocked the bootloader of my Motorola G7 Plus. I did everything right and every time I restart shows a warning about the smartphone being unlocked, and I do have the drivers of the phone updated, the adb & fastboot drivers updated and I have tried 4 different cables and 3 USB ports.
So I want to flash Lineage OS but it is showing me some errors when I try to flash the recovery.img lineage.
*It was starting to download to boot but never ended, and I mean 5 hours (25 mb), only showing (sending.....) and FAILED (remote failure)
*So i tried the methods Lineage recommends fastboot boot__a/boot_a/boot_b/boot__b. RecoveryImageName.img
None of them worked
I gave up the idea of trying by Lineage, so I tried with TWRP, didn't install as well. Sometimes just showing (sending....) and stayed there for hours, FAILED (remote failure), but with me trying new commands to fix it started to appear errors about not knowing partitions file sizes, not detecting any partitions and maximum file reached for that partition.
I did try a whole bunch of commands, ways, tutorials but couldn't figure it out.
The phone is perfectly fine, I can´t just flash it
This is my last bit of my code trying
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery recovery.img
(bootloader) max-sparse: not found
sending 'recovery' (23065 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\0\Pictures\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\0\Pictures\platform-tools>adb reboot bootloader
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (23065 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery "recovery.img"
(bootloader) max-sparse: not found
sending 'recovery' (23065 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\0\Pictures\platform-tools>fastboot --set-active=_a
Slot _a does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active=__a
Slot __a does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active='a'
Slot 'a' does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active="a"
(bootloader) slot: not found
fastboot: error: Device does not support slots
C:\Users\0\Pictures\platform-tools>fastboot --set-active="b"
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active='b'
Slot 'b' does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>mfastboot --set-active=_a
mfastboot: unrecognised option `--set-active=_a'
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>mfastboot --set-active=a
mfastboot: unrecognised option `--set-active=a'

Hi there,
flashing twrp is different for different phones
for instance, when i flashed the recovery twrp for my coolpad note 3 lite, i have to press the power key and volume up key but it didn't flash successfully.After six to seven attempts i realised i have to hold down the keys until the whole flashing is completed but the guys in the youtube did it differently and it worked.
maybe why don't you try something of that sort???

Maybe some information and assistance in your device forum Section:
Moto G7 Plus
The Moto G7 Plus is a 6.2" phone with a 1080 x 2270p display. The Snapdragon 636 is paired with 4GB of RAM and 64GB of storage. The main camera is 16MP and the selfie camera is 5MP. The battery has a 3000mAh capacity.
forum.xda-developers.com

You have good skill. You need to find proper steps. Some steps may different for different mobile. Look within forum

-.-

Development [FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices

Greetings,
I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.
PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES
This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM
Attention: this ROM only for the migration from COS Android 11 to OOS Android 11. Do not try to use it for switching to/from other version of Android. This can lead to the boot loop.
You can find ROMs maintained by @penguinus which are more universal than these and allow to switch between Android versions.
Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.
Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111". Fixed in latest firmwares.
Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.
Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved
Good luck!
Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.
DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.11 zip:
4.3 GB file on MEGA
mega.nz
boot.img OxygenOS A.11 https://mega.nz/file/RVAXCJya#SXukMoZbmWqScbSuE3iVtTEYYkYlOt8eajfV8xCIOdI
Fastboot ROM OxygenOS A.08 zip:
https://mega.nz/file/LYFElKaL#9-gO2xVEenHufecxaDSTRTUuCuJY-QlxIRRbSUtHfo8boot.img OxygenOS A.08 https://mega.nz/file/kJQyCCTS#VHy7tzjPEhDlrtZm1v1AB-lmEN4ckx5dUVlnX0YZ0gs
Fastboot ROM OxygenOS A.07 zip:
https://mega.nz/file/4JZ2XRiT#7fIk6nL0V9zkr02CcGL9tgxiVJPfJpYN1S8jA-DAxE8boot.img OxygenOS A.07 https://mega.nz/file/dZpHiAYI#eEuNHhz7nO0dCqFJrl3kK57s2PAnwr7zfa2UvBecgAE
Fastboot ROM OxygenOS A.06 zip:
https://mega.nz/file/QZQQUZqZ#3PntyL67g71AneyGKjPD5UH-gVyTxHk21MkLoTxojpA
Fastboot ROM OxygenOS A.05 zip:
https://mega.nz/file/MBgg2AjJ#98vdiFZPUCMm9gskDu5SQmic-D8jHZ3snO8pLbqrbFY
Fastboot ROM OxygenOS A.04 zip:
https://mega.nz/file/oFhjDKrI#jUajmG5fAeH1TvYS3b6EZB6Pwj5MzDpAt47fwr6gurMhttps://disk.yandex.ru/d/U8WxNFOFU4rDfA
Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Updates:
[2022-02-22] fixed installation and upgrade for some specific device state (if you have installed previous version successfully, you doesn't need re-installation).
[2022-03-01] add A.05 version of firmware.
[2022-03-11] add A.06 version of firmware.
[2022-03-20] add A.07 version of firmware.
[2022-05-23] add A.08 version of firmware.
[2022-06-06] update A.08 version of firmware (fixed issue with telegram by @penguinus).
[2022-07-20] add A.11 version of firmware (prepared by @penguinus)
[2022-10-12] add attention message about downgrading.

Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?

bonez56 said:
Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
Click to expand...
Click to collapse
It has an option to upgrade without wipe.
Please read instructions more carefully (last part of instruction about upgrade from previous version)

Thanks for posting this.

bonez56 said:
Cảm ơn vì điều này. Tôi đang chạy cái này trên MT2110 của mình (mặc dù là phiên bản A03).
Điều này có thể bị bẩn được hiển thị trên đầu cài đặt gốc hay nó sẽ xóa tất cả các cài đặt / ứng dụng của tôi?
Click to expand...
Click to collapse
Choose update.bat to update and all your data is kept intact

Thank you so much, really appreciate it

Valdem said:
Greetings,
I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.
PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES
This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM
Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.
Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111".
Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.
Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved
Good luck!
Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.
DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.04 zip:
File on MEGA
mega.nz
Яндекс
Найдётся всё
disk.yandex.ru
Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Click to expand...
Click to collapse
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?

borg79 said:
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?
Click to expand...
Click to collapse
If you talk about next OTA - then answer is YES, because you lock bootloader.
The main requirement for OTA - unmodified data on device system's partitions.
If you talk about official MSMDownload Tools. Then nothing can stop you to flash it. It is low level firmware, which can restore almost everything.

I own the chinese version with 8/256 GB. Will this rom work? I know, its the only version, thats not coming to india, but i would like to install this rom for better use.. Thanks for answering

Solved

deleted

miky03 said:
I have the mt2110 model comming from colorOs v12
i can boot to fastmode what should I do please help
Click to expand...
Click to collapse
Try to flash again. By log it looks like your phone didn't rebooted to fastbootd correctly when install script tried to do that.

miky03 said:
hi i did like you write unfortunly i get the
QUALCOMM CrashDump Mode:
dm-verity device corrupted verity_ctr
I have the mt2110 model comming from colorOs v12
i can boot to fastmode what should I do please help
D:\op9rt-oos-A04-fastboot-rom>install.bat
###################
# Formatting data #
###################
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.004s]
Writing 'userdata' OKAY [ 0.012s]
Finished. Total time: 1.630s
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 2.541s]
Writing 'metadata' OKAY [ 0.886s]
Finished. Total time: 5.592s
#######################################################################
# Oxygen OS Flasher For OnePlus 9RT by abhinavgupta371 and HELLBOY017 #
# updated by Va1d3m #
#######################################################################
#################################
# Flashing firmware into slot A #
#################################
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.013s
#################################
# Flashing bootloader img's #
#################################
Sending 'boot_a' (196608 KB) OKAY [ 5.309s]
Writing 'boot_a' OKAY [ 0.384s]
Sending 'boot_b' (196608 KB) OKAY [ 4.253s]
Writing 'boot_b' OKAY [ 0.381s]
Finished. Total time: 10.370s
Sending 'modem_a' (190060 KB) OKAY [ 5.191s]
Writing 'modem_a' OKAY [ 0.376s]
Sending 'modem_b' (190060 KB) OKAY [ 4.143s]
Writing 'modem_b' OKAY [ 0.435s]
Finished. Total time: 10.186s
Sending 'vendor_boot' (196608 KB) OKAY [ 5.316s]
Writing 'vendor_boot' OKAY [ 0.430s]
Finished. Total time: 5.767s
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.018s
##########################
# Rebooting to fastbootd #
##########################
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
#################################
# Flashing fastbootd img's #
#################################
fastboot: error: Could not check if partition abl has slot all
fastboot: error: Could not check if partition aop has slot all
fastboot: error: Could not check if partition bluetooth has slot all
fastboot: error: Could not check if partition cpucp has slot all
fastboot: error: Could not check if partition devcfg has slot all
fastboot: error: Could not check if partition dsp has slot all
fastboot: error: Could not check if partition dtbo has slot all
fastboot: error: Could not check if partition engineering_cdt has slot all
fastboot: error: Could not check if partition featenabler has slot all
fastboot: error: Could not check if partition hyp has slot all
fastboot: error: Could not check if partition imagefv has slot all
fastboot: error: Could not check if partition keymaster has slot all
fastboot: error: Could not check if partition mdtp has slot all
fastboot: error: Could not check if partition mdtpsecapp has slot all
fastboot: error: Could not check if partition multiimgoem has slot all
fastboot: error: Could not check if partition oplus_sec has slot all
fastboot: error: Could not check if partition oplusstanvbk has slot all
fastboot: error: Could not check if partition qupfw has slot all
fastboot: error: Could not check if partition qweslicstore has slot all
fastboot: error: Could not check if partition shrm has slot all
fastboot: error: Could not check if partition splash has slot all
fastboot: error: Could not check if partition tz has slot all
fastboot: error: Could not check if partition uefisecapp has slot all
fastboot: error: Could not check if partition vm-bootsys has slot all
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
###############################
# Resizing logical partitions #
###############################
Deleting 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
###############################
# Flashing logical partitions #
###############################
Sending 'vendor' (621044 KB) OKAY [ 18.220s]
Writing 'vendor' FAILED (remote: '(vendor_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 17.645s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system' (760184 KB) OKAY [ 23.335s]
Writing 'system' FAILED (remote: '(system_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 18.302s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'product' (71056 KB) OKAY [ 1.946s]
Writing 'product' FAILED (remote: '(product_a) No such partition')
fastboot: error: Command failed
Sending 'my_carrier' (340 KB) OKAY [ 0.010s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_a) No such partition')
fastboot: error: Command failed
Sending 'my_company' (340 KB) OKAY [ 0.009s]
Writing 'my_company' FAILED (remote: '(my_company_a) No such partition')
fastboot: error: Command failed
Sending 'my_engineering' (340 KB) OKAY [ 0.009s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_heytap' 1/2 (786368 KB) OKAY [ 17.396s]
Writing 'my_heytap' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'my_manifest' (720 KB) OKAY [ 0.019s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_a) No such partition')
fastboot: error: Command failed
Sending 'my_preload' (3520 KB) OKAY [ 0.097s]
Writing 'my_preload' FAILED (remote: '(my_preload_a) No such partition')
fastboot: error: Command failed
Sending 'my_product' (267700 KB) OKAY [ 7.769s]
Writing 'my_product' FAILED (remote: '(my_product_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_region' 1/2 (781680 KB) OKAY [ 17.330s]
Writing 'my_region' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_stock' 1/2 (750628 KB) OKAY [ 16.707s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
#######################
# Rebooting to system #
#######################
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
Press any key to continue . . .View attachment 5543893View attachment 5543895
Click to expand...
Click to collapse
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).

Valdem said:
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).
Click to expand...
Click to collapse
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.

miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
it is ok. fastbootd mode looks like recovery. but script should not fail with message 'fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.'

Where is bootloader drivers for OP9RT？

miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device
if no serial number is printed - there is issue with fastboot binary.
Update: It looks like you have some issue with drivers.

miky03 said:
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
Click to expand...
Click to collapse
Have you put your Window OS into "testsigning" mode before executing the batch file ?

Valdem said:
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device
if no serial number is printed - there is issue with fastboot binary.
Update: It looks like you have some issue with drivers.
Click to expand...
Click to collapse
Hi i did until 3. Then reboot to this menu in cmd waiting for any device

borg79 said:
Have you put your Window OS into "testsigning" mode before executing the batch file ?
Click to expand...
Click to collapse
Hi im running on win 7 64bit.what is testing mode?