Database Develop

Help with fastboot ubuntu

does anyone know where to get help with fastboot in ubuntu? i have tried flashing a recovery image to my Dell Streak 7, but it keeps failing. fastboot is working, and when i send the command "fastboot reboot" it works fine. however, "fastboot devices" returns "????????????". when i try to flash the recovery, i get
"sending 'recovery' (3654 KB)...
FAILED (command write failed (No such device))
finished. total time: 0.000s"
"fastboot getvar version" returns version: LG7 0.4
so i know fastboot is working, and that it has at least some communication with the tablet, but something is not quite working. any ideas?

SOLVED
i'm not sure what happened differently, but i plugged the tablet into a different USB port, and then i got a max-download-size error when flashing the recovery. i came across another post that said to use "fastboot -S 0 flash..." to resolve that error, and it worked. everything seems to be good now

Device is Corrupt and will SHUTDOWN in 30 seconds. DEAD DEVICE?=(

I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:

First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?

KonikoO said:
First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?
Click to expand...
Click to collapse
I needed to make a critical unlock, and according to instruction 1st step was to lock the bootloader.
I can access download mode only

well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.

sumitinhome said:
well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.
Click to expand...
Click to collapse
Everything is fine. Ntool helped me to install stock 8.1

Mihalsch said:
Everything is fine. Ntool helped me to install stock 8.1
Click to expand...
Click to collapse
Process please.

sumitinhome said:
Process please.
Click to expand...
Click to collapse
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.

pls help bro im having the same probelm of urs for 1 month
Mihalsch said:
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.
Click to expand...
Click to collapse
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:

gogeta blue said:
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:
Click to expand...
Click to collapse
0.036 version
Here is 8.1. Pass (techmesto.com)
https://drive.google.com/file/d/1g4rsUE2sohL9EISb0Uu5FPRlNs0D73Xl/view

Mihalsch said:
0.036 version
Here is 8.1. Pass
Click to expand...
Click to collapse
0.036 version is not found any where i can only find 0.1 pls help

gogeta blue said:
0.036 version is not found any where i can only find 0.1 pls help
Click to expand...
Click to collapse
Try this
https://fex.net/635965328106

Mihalsch said:
Try this
Click to expand...
Click to collapse
Error while flashing
RUNNING NTool 0.036
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Elapsed: 40 secs.
SELECT FIRMWARE PACKAGE
Will flash : NB1-488B-0-00WW-B04.mlf
PLEASE CONNECT POWERED OFF PHONE
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Security version : 0004
Challenge : 9AEEE713ECEF3D6448B2E0842D1C8B34EA5D12BF
Waiting for calculation process ...
recv error [10054]
FATAL ERROR: server error: No server found.
Elapsed: 0 secs.

Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me

same problem with my nokia 8 ta-1004

dugu1248 said:
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me
Click to expand...
Click to collapse
you must change your battery ,thats battery problem

Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
same device, same problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Fastboot stopped working ?

Mysteriously my fastboot stopped working?
I can adb devices works fine
Adb reboot bootloader works fine
Fastboot devices works fine
Fastboot flash boot filename I get FAILED (Write to device failed ( Invalid argument)) fastboot: error: Command failed
Stumped at this point
I'm completely stock and not rooted..
Flash_all gives same error and any other fastboot command as well :crying:
Edit: I've used the same USB to C cord I've always used BUT have tried another PC and different cords...No dice

Question 'fastboot oem unlock' failing with remote: 'unknown command'

I just got my OnePlus 10 Pro, and am trying to unlock the bootloader. I've enabled USB debugging, and enabled the option to allow the bootloader to be unlocked in the Developer Settings.
I ran `adb reboot bootloader`, then ran `fastboot devices` to confirm the phone was connected and visible.
When I try to run `fastboot oem unlock`, I get this response:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Fastboot version if necessary:
Code:
C:\Windows\system32>fastboot --version
fastboot version 33.0.2-8557947
Installed as C:\Program Files\Android Platform Tools\fastboot.exe
Thanks!

Fastboot flashing unlock

Awesome, thank you very much!

Question OnePlus 10 Pro Bootloader Unable to unlock [NE2215]

Hi,
I am trying to unlock the bootloader as it show status as "Device Lock"
When I try to use the command "fastboot oem unlock", it showed
"
...
FAILED (remote: unknown command)
finished. total time: 0.001s
I then tried "fastboot flashing unlock" but it showed this
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
Any solution to this?

fastboot flashing unlock
Make sure your platform tools are up to date as well - https://developer.android.com/studio/releases/platform-tools

Still the same. This is what I kept getting

When you type in fastboot press tab and it'll populate the actual filename.
I get this with certain setups. Same with ADB, just press tab after typing fastboot or ADB then continue with the same commands as you have..
Could just be your fastboot/ADB files.
. I've got the ones I use in my root guide in this forum, grab it and pop it in the root of C then give it another shot.
Hope you get it sorted

Jcddenton said:
Still the same. This is what I kept getting
Click to expand...
Click to collapse
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.

You go into developer options and tick oem_unlock on?

EtherealRemnant said:
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.
Click to expand...
Click to collapse
The above is what I have experienced myself.. Only ever happens with PS never CMD, not the end of the world though

Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.

Update your platform-tools. I had the same issue trying to unlock my pixel 7.

az_r2d1 said:
Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.
Click to expand...
Click to collapse
Everything you need is linked in my sig

Unlock oem from setting

ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !

az_r2d1 said:
ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !
Click to expand...
Click to collapse
In his case he is actually getting connect currently and it's visible..
As it's an unknown command then it's probably due to PowerShell,, when you type in the command, eg:
fastboot reboot
It won't see the word fastboot itself as the correct command. To fix this just click tab once and it'll populate it's actual name from the list of files in the active folder, so in actual fact the command would be
.\fastboot.exe reboot
Same thing with ADB as a command.
.\adb.exe devices
Just pressing the tab key would do the job.
Or just use CMD and navigate to the folder you'd like to be active

I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!

BeachNYC said:
I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!
Click to expand...
Click to collapse
Install platform tools, go into the directory that platform tools was installed, and run adb and fastboot thru that, i was getting same error and then went from directory platform tools was unzipped at and it worked fine...fastboot flashing unlock though

fastboot flashing unlock don't work for me!
adb is ok
fastboot reboot and fasboot devices is ok all commands
but not fastboot flashing unlock! on power shell or cmd always the same!
no error just the list
i test different cable or usb plug
i go crazy...

Damned fastboot flashing unlock passed. Don't ask me when. verified all 10 time and voilà !?
First time I like erase all my data
Just CMD like the undred before, but why this time?
I don't know really.
Though lock.