Database Develop

Fastboot Flash <remote failure>

I was on my phone and an app closed. Then it closed again when I tried to re-open it. Third time's the charm, it closed again and then google services stopped. Then my phone shut off. I wouldn't turn on, so I had to do the power button+volume down to get into the bootloader menu. I tried to boot up and was stuck with a bootloop. I downloaded a factory image and the latest android sdk.
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?

melgibson666 said:
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
Click to expand...
Click to collapse
My idea is that the bootloader is locked.

Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.

NLBeev said:
My idea is that the bootloader is locked.
Click to expand...
Click to collapse
It is not.
danarama said:
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.

melgibson666 said:
It is not.
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
Click to expand...
Click to collapse
Please screenshot the error.

melgibson666 said:
. . .Bootloader unlocked
. . .reinstalled the drivers to be sure,
. . .used the original USB cable. . .
. . .tried 3 different USB ports . . .
. . .fastboot detected the device.
Still not working.
Click to expand...
Click to collapse
The quotes from you posts gave me the impression that the hardware is OK.
Probably the drivers on your PC are also OK.
I assume the command 'fastboot devices' responded a device ID.
Other issues could be:
- the dosbox and fastboot commands on the PC are not started as administrator;
- the driver on the pc is an adb-driver and not an adb combined driver;
- the version of fastboot is obsolete;
- images flashed before were corrupt;
Possible actions:
Make sure the fastboot and also adb files including the dll's are up to date.
Check if the command 'adb devices' works.
Try to adb sideload a (stock) rom.

The strangest problem with oneplus i have seen!

Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:

onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.

Tried to flash Zuk Z2 but nothing has gone right.

Hi guys,
I am having a lot of difficulties flashing the OS I have. I have an old ZUI 1.9 and after a few years I just started getting fullscreen ads when launching aps like netflix.
My bootloader is locked, I was able to get the unlock file from the chinese lenovo website, but now the issue I have is that all the commands I try are wrong.
I am using SDK platform tools, I have adb setup installed and got the driver for my device. When I go into fastboot the computer doesn't recognise Zuk Z2 anymore.
What I did was set the driver manually to ADB bootloader in device manager. This prevents the command from returning "waiting for any device".
I have tried many commands but all the ones that have fasboot -i doesn't work.
IE: fastboot -i 0x2b4c flash unlock unlock_bootloader.img will return :"fastbook: unknown option --i"
If I can't get the bootloader to be unlocked commands like: "fastboot flash recovery twrp.img" will return :"fasboot: error: command failed". Sending goes OKAY, writing goes FAILED (remote: 'Partition flashing is not allowed').
In a last attempt to get this fix before I lose my calm I decided to register an account on the zukfans forums to ask for help. Once you register your account gets banned for spamlike behavior.
I found through an old post here that you can contact them through facebook to get that fixed, but now their pages have been deleted, and I have spent way too much time trying to flash this stupid device.
Any help is appreciated, if you need any more information don't hesitate to ask, I'll do my best to answer as this is the first time I try to flash a phone and none of the guides could help this far.
Thanks

[HELP]my xiaomi mi a2 doesn't accept almost any command through fastboot

Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....

I'm having the same problem.
basically when i am on slot b, I can't use any fastboot commands and ive also not installed twrp.
those same commands worked when i was on slot a.
now i am stuck in slot b. don't know any fix.

ZuNNN said:
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
Click to expand...
Click to collapse
Use Windows PC (preferably 7 with Intel and USB 2.0), latest platform tools and try again. I generally do not install TWRP, rather boot it (use the latest one) and carry out the tasks since I use Stock ROM.

I had that problem before.
Things that solved:
Use another usb-c cable
Run fastboot on linux
Use an usb 2.0 HUB (the ones that have 3 or 4 ports)

did u check usb debug box,and OEM as well?
and if you did all of that , did unlock bootloader?

hi guys, after the really buggy android 10 update from xiaomi i decided to install a custom rom on my device, i hadn't installed a custom rom in ages and never on an a/b device so it was new to me, i was kinda stumbling but managed to install twrp, install pixel experience rom and then switched to slot a and it booted
but now my device does not accept most fastboot commands! fastboot getvar all only works 1/3 of the time, most of the time it either fails with FAILED (remote: 'unknown command')) or FAILED (Write to device failed (Unknown error)) which boots me to the same black screen as OP. fastboot boot twrp.img always fails. the phone boots successfully but im unable to switch slots or boot to recovery when everything was working perfectly before switching slots. ive tried 2 cables with 3 usb ports on my laptop.

Redmi K20 Pro restarts to fastboot and not to system.

Hi, after flashing newest Legion OS I have a small problem. Every time I restart my phone, it enters fastboot, all I have to do is to connect my phone to PC and use "fastboot continue" then phone normally boots to system, until next restart. It's not a big deal, but sometimes I forgot about this problem and restart my phone when I don't have pc near by. I tried "fastboot oem fb_mode_clear" but all I'm getting is "FAILED (remote: unknown command)"

MorganMLG said:
Hi, after flashing newest Legion OS I have a small problem. Every time I restart my phone, it enters fastboot, all I have to do is to connect my phone to PC and use "fastboot continue" then phone normally boots to system, until next restart. It's not a big deal, but sometimes I forgot about this problem and restart my phone when I don't have pc near by. I tried "fastboot oem fb_mode_clear" but all I'm getting is "FAILED (remote: unknown command)"
Click to expand...
Click to collapse
That's a new one on me. Normally, if the phone boots into fastboot instead of system, it's because there's a problem with the ROM installation (typically it's an encryption problem with this phone). In which case you wouldn't be able to boot into system at all (if the problem is encryption then formatting data would fix it). Not come across a case, so far, where you could successfully boot into the ROM from fastboot in this scenario. Maybe it's a LegionOS issue - possibly the dev was debugging and had the ROM go into fastboot first, then forgot to remove this before releasing it.
The fastboot oem .... command allows oems to introduce their own specific commands for their phones.
As far as I'm aware fb_mode_set and fb_mode_clear are Motorola inventions, and so will only work on some Motorola phones.
I would suggest either asking in the LegionOS thread, or backup everything and try clean installing LegionOS again.

I have exactly the same problem as you after flashing newest PE （Clean flash)
Solved: flash miui 12.0.x.x based on android 10 before flashing custom rom.