Database Users

Can't unlock bootloader....what am I missing

I'm going nuts here. I use a mac, have had the 6p since preorder (well...since they shipped it) and I haven't had a need for unlocking or rooting (first phone ever to leave it stock) but I've got a few glitches and what not and wanted to flash the newest update released today rather than wait for OTA. Figured a complete wipe can't hurt. unfortunately the fastboot flashing unlock command isn't working. Developer options enabled, OEM unlock tab enabled...usb debugging enabled.....but when I enter ./fastboot flashing unlock this is what I get in terminal (yes mac requires the ./ before any command)
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

Perhaps you have an outdated version? Just a wild guess here but usually if an option is invalid, that's the case.
Sent from my Nexus 6P using Tapatalk

Yep - as @funnel71 said - outdated version.
I unlocked the bootloader on my shiny new 6p yesterday, and initially I got exactly the same result initially. I were doing it on my ubuntu desktop (14.04) at work which has adb installed from packages, which was working perfectly fine with other devices. I manually installed the latest android sdk - and in no time at all I had unlocked and rooted goodness

As others have said, your fastboot package is outdated. You need to install the Android SDK and make sure the platform-tools package is updated.

Thanks. I was thinking that. But it's been so long since I've done that... I got read up again lol
Sent from my Nexus 6P using XDA-Developers mobile app

Updated the SDK. Thanks everyone. It's unlocked now. I knew I was missing something.

Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt

318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
What is the exact command you're issuing?

318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?

./flash-all.sh is what type in and it gives me the error above.
When I tried to flash just the bootloader first I used
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Sent from my Nexus 6P using XDA-Developers mobile app

nathanchance said:
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?
Click to expand...
Click to collapse
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.

318sugarhill said:
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.
Click to expand...
Click to collapse
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.

nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
agree, very hit or miss, personally I flash each file manually. just the best results this way. I also agree that a outdated version of fastboot/you're gonna have a bad time.

nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.

318sugarhill said:
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Click to expand...
Click to collapse
Did you ever use the following command?
Code:
fastboot erase bootloader

DJBhardwaj said:
Did you ever use the following command?
Code:
fastboot erase bootloader
Click to expand...
Click to collapse
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.

318sugarhill said:
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.
Click to expand...
Click to collapse
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.

DJBhardwaj said:
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.
Click to expand...
Click to collapse
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.

318sugarhill said:
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.
Click to expand...
Click to collapse
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img

DJBhardwaj said:
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img
Click to expand...
Click to collapse
yes.....just with a ./ in front. I've shorted the name of the booloader to bootloader.img just to keep the typing down.....but I've tried with the original name too. It's not angler.....it's ......
Holy F..........!!!!!!!!! I downloaded the factory image for the 5X.....it's friggin bullhead! AHHHHHHHHH
Facepalm.

Problem installing TWRP on ALE-L21 after last Stock ROM Update

Hey guys,
I can't install TWRP anymore on my unlocked "P8 lite" after the last Stock ROM Update. I've done the installation many times before without problems using Minimal ADB and fastboot and even the Universal Fastboot and ADB tool. When I try to flash I get no failed command, but nothing happens on my phone. I've tried with the newest grace .img (for "P8") and with an older .img that I've used in the past successfully. Commands "adb devices" and "adb reboot bootloader" work fine.
Any solution?
thx
CMD commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 2.625s

CANNOT FLASH TWRP FAILED (remote: 'Command not allowed')

Hello all i have unlocked my bootloader and i booted into the bootloader fastboot & rescue mode
fastboot flash recovery twrp.img
C:\Users\USER\Desktop\platform-tools>fastboot flash recovery_ramdisk recovery.img
Sending 'recovery_ramdisk' (24434 KB) OKAY [ 0.655s]
Writing 'recovery_ramdisk' OKAY [ 0.612s]
Finished. Total time: 1.294s
C:\Users\USER\Desktop\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 3.085s]
booting FAILED (remote: 'Command not allowed')
Finished. Total time: 5.215s
BOOTLOADER IS UNLOCKED!
I tried flashing using
fastboot flash recovery.img and it still did not work AT ALL it says command not allowed and no unlocking it again does not work!

Redicat said:
Hello all i have unlocked my bootloader and i booted into the bootloader fastboot & rescue mode
fastboot flash recovery twrp.img
C:\Users\USER\Desktop\platform-tools>fastboot flash recovery_ramdisk recovery.img
Sending 'recovery_ramdisk' (24434 KB) OKAY [ 0.655s]
Writing 'recovery_ramdisk' OKAY [ 0.612s]
Finished. Total time: 1.294s
C:\Users\USER\Desktop\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 3.085s]
booting FAILED (remote: 'Command not allowed')
Finished. Total time: 5.215s
BOOTLOADER IS UNLOCKED!
I tried flashing using
fastboot flash recovery.img and it still did not work AT ALL it says command not allowed and no unlocking it again does not work!
Click to expand...
Click to collapse
You need to re unlock the bootloader. I had the same issue. In fastboot mode says bootloader unlocked but it seems that is not. When i tried to install stock B638 through dload folder it seems to "relock the bootloader"

Oneplus 6T McLaren complete brick

I have had the OP6T for about 1.5 years now and immediately installed TWRP after the purchase. I have never changed or updated the software (Android 9.0). Now I recently experienced some small bugs and wanted to perform a factory reset via TWRP. This one just did not allow it and I got an error message. Backing up was also not possible because of a mount error. The internal partition was still available. Yesterday I downloaded the official and stable update to Android 10 via the Oneplus site. This was the next step to solve the problems.
Step-by-step plan:
1. Boot to TWRP and flash new rom.
2. Install TWRP again to overwrite system recovery.
3. Reboot to recovery again and reinstall Magisk.
4. Reboot device.
All problems started at step 1. When flashing the full zip I got an 'Error code 1'. My TWRP turned out not to be up to date. I immediately updated TWRP and rebooted it. At that moment TWRP reported that there was no OS installed. No disaster, I could still overwrite everything and install Android 10 I thought. Again an 'Error code 1'. Then I wiped the system partition via TWRP. After this the error code stayed. When I restarting TWRP, TWRP suddenly disappeared as well. Now I have the default menu of an empty Oneplus device which only allows me to go to fastboot/ADB. In tried to reinstall TWRP trought fastboot/ADB but it failed. Below the error code from the command prompt:
PS C:\Users\yoeri\Downloads\img> fastboot devices
1b6ccb35 fastboot
PS C:\Users\yoeri\Downloads\img>
PS C:\Users\yoeri\Downloads\img> fastboot boot twrp.img
downloading "boot.img"...
OKAY [ 0.699s]
...booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.724s
The MSM tool (hard-brick tool) does not work either. My device doesn't show up but it can still boot up to nowhere. Fastboot/ADB is the only way to connect the device but doesn't work. I suspect that there were errors in the disk partitions from the beginning. Does anyone have any idea how I can fix my OP6T?

Generally wiping system is a bad idea on these devices. Generally once I've had problem in fastboot, I've had to use the fastboot ROM to fix the device. Either reload the problem "partition" or the whole ROM, doesn't matter.
Since you have fastboot, the MSM tool is never what I jump since it locks the bootloader. MSM Tool is always my last resort. Key combinations are (from another post I did recently):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Just to make sure you do know that when you using the MSM tool, you won't be in Fastboot correct? There is a driver as well for this.
Once you get this up and running, make sure you are using an up to date TWRP from here.

OhioYJ said:
Generally wiping system is a bad idea on these devices. Generally once I've had problem in fastboot, I've had to use the fastboot ROM to fix the device. Either reload the problem "partition" or the whole ROM, doesn't matter.
Since you have fastboot, the MSM tool is never what I jump since it locks the bootloader. MSM Tool is always my last resort. Key combinations are (from another post I did recently):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Just to make sure you do know that when you using the MSM tool, you won't be in Fastboot correct? There is a driver as well for this.
Once you get this up and running, make sure you are using an up to date TWRP from here.
Click to expand...
Click to collapse
I can only enter fastboot mode. Download mode doesn't show up with that button combination. Is there no way to recover it with fastboot mode?

yoeri058 said:
I can only enter fastboot mode. Download mode doesn't show up with that button combination. Is there no way to recover it with fastboot mode?
Click to expand...
Click to collapse
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.

OhioYJ said:
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.
Click to expand...
Click to collapse
I followed the article but it doesn't work for me. I receive this error codes:
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot devices
1b6ccb35 fastboot
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot boot flash-all.bat
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.030s
Click to expand...
Click to collapse
These are the logs from the manual try which also didn't change anything:
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot boot flash-all-partitions.bat
cannot load 'flash-all-partitions.bat': No such file or directory
PS C:\Users\yoeri\Downloads\10.3.2-OnePlus6TOxygen_34_OTA_044_all_2002220041_110bb9052a994b6f-FASTBOOT> fastboot flash aop_a aop.img
>> fastboot flash aop_b aop.img
>> fastboot flash bluetooth_a bluetooth.img
>> fastboot flash bluetooth_b bluetooth.img
>> fastboot flash boot_a boot.img
>> fastboot flash boot_b boot.img
>> fastboot flash dsp_a dsp.img
>> fastboot flash dsp_b dsp.img
>> fastboot flash dtbo_a dtbo.img
>> fastboot flash dtbo_b dtbo.img
>> fastboot flash fw_4j1ed_a fw_4j1ed.img
>> fastboot flash fw_4j1ed_b fw_4j1ed.img
>> fastboot flash fw_4u1ea_a fw_4u1ea.img
>> fastboot flash fw_4u1ea_b fw_4u1ea.img
>> fastboot flash modem_a modem.img
>> fastboot flash modem_b modem.img
>> fastboot flash oem_stanvbk oem_stanvbk.img
>> fastboot flash qupfw_a qupfw.img
>> fastboot flash qupfw_b qupfw.img
>> fastboot flash storsec_a storsec.img
>> fastboot flash storsec_b storsec.img
>> fastboot flash system_a system.img
>> fastboot flash system_b system.img
>> fastboot flash vbmeta_a vbmeta.img
>> fastboot flash vbmeta_b vbmeta.img
>> fastboot flash vendor_a vendor.img
>> fastboot flash vendor_b vendor.img
>> fastboot flash LOGO_a LOGO.img
>> fastboot flash LOGO_b LOGO.img
target reported max download size of 536870912 bytes
sending 'aop_a' (180 KB)...
OKAY [ 0.011s]
writing 'aop_a'...
OKAY [ 0.029s]
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'aop_b' (180 KB)...
OKAY [ 0.027s]
writing 'aop_b'...
OKAY [ 0.035s]
finished. total time: 0.102s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (748 KB)...
OKAY [ 0.026s]
writing 'bluetooth_a'...
OKAY [ 0.021s]
finished. total time: 0.071s
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (748 KB)...
OKAY [ 0.024s]
writing 'bluetooth_b'...
OKAY [ 0.024s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.421s]
writing 'boot_a'...
OKAY [ 0.311s]
finished. total time: 1.735s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.423s]
writing 'boot_b'...
OKAY [ 0.311s]
finished. total time: 1.737s
target reported max download size of 536870912 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 0.713s]
writing 'dsp_a'...
OKAY [ 0.324s]
finished. total time: 1.039s
target reported max download size of 536870912 bytes
sending 'dsp_b' (32768 KB)...
OKAY [ 0.715s]
writing 'dsp_b'...
OKAY [ 0.344s]
finished. total time: 1.062s
target reported max download size of 536870912 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.189s]
writing 'dtbo_a'...
OKAY [ 0.072s]
finished. total time: 0.264s
target reported max download size of 536870912 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.191s]
writing 'dtbo_b'...
OKAY [ 0.080s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_a' (344 KB)...
OKAY [ 0.020s]
writing 'fw_4j1ed_a'...
OKAY [ 0.027s]
finished. total time: 0.073s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_b' (344 KB)...
OKAY [ 0.028s]
writing 'fw_4j1ed_b'...
OKAY [ 0.032s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_a' (344 KB)...
OKAY [ 0.020s]
writing 'fw_4u1ea_a'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4u1ea_b'...
OKAY [ 0.036s]
finished. total time: 0.099s
target reported max download size of 536870912 bytes
sending 'modem_a' (118228 KB)...
OKAY [ 2.596s]
writing 'modem_a'...
OKAY [ 0.683s]
finished. total time: 3.282s
target reported max download size of 536870912 bytes
sending 'modem_b' (118228 KB)...
OKAY [ 2.596s]
writing 'modem_b'...
OKAY [ 0.523s]
finished. total time: 3.123s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (432 KB)...
OKAY [ 0.031s]
writing 'oem_stanvbk'...
OKAY [ 0.038s]
finished. total time: 0.102s
target reported max download size of 536870912 bytes
sending 'qupfw_a' (64 KB)...
OKAY [ 0.005s]
writing 'qupfw_a'...
OKAY [ 0.025s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
sending 'qupfw_b' (64 KB)...
OKAY [ 0.008s]
writing 'qupfw_b'...
OKAY [ 0.025s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'storsec_a' (24 KB)...
OKAY [ 0.012s]
writing 'storsec_a'...
OKAY [ 0.028s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'storsec_b' (24 KB)...
OKAY [ 0.008s]
writing 'storsec_b'...
OKAY [ 0.032s]
finished. total time: 0.072s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system_b'...
OKAY [ 0.033s]
sending sparse 'system_b' (498465 KB)...
OKAY [ 11.469s]
writing 'system_b'...
OKAY [ 0.002s]
sending sparse 'system_b' (515995 KB)...
OKAY [ 17.766s]
writing 'system_b'...
OKAY [ 0.002s]
sending sparse 'system_b' (504323 KB)...
OKAY [ 17.175s]
writing 'system_b'...
OKAY [ 0.003s]
sending sparse 'system_b' (524294 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 47.659s
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (8 KB)...
OKAY [ 0.012s]
writing 'vbmeta_a'...
OKAY [ 0.041s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.009s]
writing 'vbmeta_b'...
OKAY [ 0.047s]
finished. total time: 0.070s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (513884 KB)...
OKAY [ 12.133s]
writing 'vendor_a'...
OKAY [ 0.003s]
sending sparse 'vendor_a' (315106 KB)...
OKAY [ 14.075s]
writing 'vendor_a'...
OKAY [ 0.002s]
finished. total time: 26.218s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
target reported max download size of 536870912 bytes
sending 'LOGO_a' (3204 KB)...
OKAY [ 0.082s]
writing 'LOGO_a'...
OKAY [ 0.014s]
finished. total time: 0.099s
target reported max download size of 536870912 bytes
sending 'LOGO_b' (3204 KB)...
OKAY [ 0.084s]
writing 'LOGO_b'...
OKAY [ 0.025s]
finished. total time: 0.113s
Click to expand...
Click to collapse
I am sure that I have al drivers correctly installed. Do you know which MSM-tool is should use? Last OS was Android 9 but now there is nothing installed.

OhioYJ said:
Nothing will show up on the screen while in download. MSMTool will recognize it though if the drivers are properly installed.
If fastboot works, I always use that before the MSMTool. MSMTool is always and always should be the last resort, as it relocks the bootloader.
You can flash ROMs from Fastboot, that's how I normally recover my phone when I've messed it up, and typically what I do in this situation: Stock Fastboot ROMs for OnePlus 6T Thread
I made a script* that has all that stuff in it that so I can flash everything I need from a single command (I use Linux all this stuff just goes in a .sh file, Windows would be a little different):
Code:
sudo fastboot flash aop_a aop.img
sudo fastboot flash aop_b aop.img
sudo fastboot flash bluetooth_a bluetooth.img
sudo fastboot flash bluetooth_b bluetooth.img
sudo fastboot flash boot_a boot.img
sudo fastboot flash boot_b boot.img
sudo fastboot flash dsp_a dsp.img
sudo fastboot flash dsp_b dsp.img
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot flash fw_4j1ed_a fw_4j1ed.img
sudo fastboot flash fw_4j1ed_b fw_4j1ed.img
sudo fastboot flash fw_4u1ea_a fw_4u1ea.img
sudo fastboot flash fw_4u1ea_b fw_4u1ea.img
sudo fastboot flash modem_a modem.img
sudo fastboot flash modem_b modem.img
sudo fastboot flash oem_stanvbk oem_stanvbk.img
sudo fastboot flash qupfw_a qupfw.img
sudo fastboot flash qupfw_b qupfw.img
sudo fastboot flash storsec_a storsec.img
sudo fastboot flash storsec_b storsec.img
sudo fastboot flash system_a system.img
sudo fastboot flash system_b system.img
sudo fastboot flash vbmeta_a vbmeta.img
sudo fastboot flash vbmeta_b vbmeta.img
sudo fastboot flash vendor_a vendor.img
sudo fastboot flash vendor_b vendor.img
sudo fastboot flash LOGO_a LOGO.img
sudo fastboot flash LOGO_b LOGO.img
*I just took all that information from the thread, definitely give all the credit to mauronofrio for taking the time to develop TWRP for our device and others, and put these things together for us. Mainly just pointing out, which so did he I believe you don't need type all that stuff in one by one.
Click to expand...
Click to collapse
I fixed it using Mauronofrio all-in-one tool. I am now running Android 10. Thanks for pointing me in the right direction!

yoeri058 said:
I am sure that I have al drivers correctly installed. Do you know which MSM-tool is should use? Last OS was Android 9 but now there is nothing installed.
Click to expand...
Click to collapse
On the MSMTool it won't matter what version, pick one and run it.
Since you were on Android 9 you may actually want to try using an Android 9 fastboot ROM.

adt-3: fastboot get_unlock_ability 0

Hi All,
I am trying to flash Android TV 13 beta 4 ~ to the developer tools adt-3. After flash ... the adt-3 keep reboot. And cna't load the bootloader and OS. when I try to flash the device again ... adt-3 said that FAILED (remote: 'locked device').
I would like to know how to unlock adt-3 !?
ToTo

./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.049s]
Finished. Total time: 0.050s
sudo ./flash-all.sh
[sudo] password for toto:
error: no devices/emulators found
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'data' FAILED (remote: 'locked device')
fastboot: error: Command failed
Sending 'bootloader' (1591 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
--------------------------------------------
Bootloader Version...: 01.01.220621.133524
Baseband Version.....: N/A
Serial Number........: ACHE0000xxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.015s]
Checking 'version-bootloader' OKAY [ 0.014s]
extracting boot.img (16 MB) to disk... took 0.031s
archive does not contain 'boot.sig'
Sending 'boot' (16384 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
OKAY [ 0.023s]
Finished. Total time: 0.023s
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.305s
Need help to unlock adt-3

fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock

Many thanks, I using adt-3. I think oem not working ... many thanks. Here is the result.
./fastboot oem 'setenv lock 10101000;save'
FAILED (remote: 'locked device')
fastboot: error: Command failed
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed

That is the command that is within flash-all.sh for build adt3_gtv-stt1.211025.001.z3-factory-91f7efe7.
It was designed specifically to fix this particular issue/bug with the adt-3.
This problem started before android 12. Read article;
[Update: Fixed] Android TV 12 preview builds for ADT-3 can't be flashed
The first builds of Android TV 12 for Google's own ADT-3 developer device are completely broken, leaving developers unable to install them.
9to5google.com

Yes, I know ... I also go through that issue when I did Android TV 12. Right now I have the issue again. When I was doing Android TV 13 beta 4. Here flash-all.sh come with Android TV 13 beta 4.
if ! [ $($(which ./fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
./adb reboot bootloader || true
if ! ./fastboot flashing unlock ; then
./fastboot oem 'setenv lock 10101000;save' || true
./fastboot reboot bootloader; sleep 3
./fastboot flashing unlock || true
fi
./fastboot erase data
./fastboot flash bootloader bootloader-adt3_gtv-01.01.220621.133524.img
./fastboot reboot bootloader; sleep 3
./fastboot -w --skip-reboot update image-adt3_gtv-trb4.220715.005.zip
./fastboot reboot bootloader; sleep 3
./fastboot flashing lock
./fastboot reboot
But this time ... it is not working

Are you sure that your fastboot version/drivers are new/good?
Within a few days I will try to update mine, in order to see if there are any issues.
Are you familiar with worldcup burn mode?
Obtain worldcup drivers and command line "update" program for your OS.
Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;
update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"
Then reboot and see if fastboot works.

./fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/platform-tools/fastboot
I just upgrade it b4 I do the Android TV 13 Beta 4.
Sorry ... I have no idea of "worldcup burn mode"

Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3

ToToHayashi said:
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
Click to expand...
Click to collapse
Did you try the update method as suggested by "Deleted member 11959327" ?
To get the tool i recommend the Khadas Git (khadas/utils) then the aml-flash-tool/ is the folder with Amlogic tools
for the update tool its in tools/linux-x86/update