Develop Bugs

G3 Fastboot brick, No Download mode...

I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???

draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"

Now, can you use fastboot command ? Like fastboot flash recovery "withyourrecovery.img"
Click to expand...
Click to collapse
Yes i can use fastboot commands also tried to write recover, laf, aboot img files. I dont have original img files of 20A but tried with 20H recovery and custom recovery img (TWRP) but no change. There was no problem or error while writing images with fastboot commands...

i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution

ghadeer.m96 said:
i have the same problem
it also says
? fastboot
still couldn't find a solution
please let me know if u find a solution
Click to expand...
Click to collapse
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )

th0was said:
Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
I can't erase recovery because i have this error ( remote failed to erase partition )
Click to expand...
Click to collapse
i can't do any command successfully
like when i do a flash command
it finishes sending successfully but then it gets stuck at writing ...
and it never finishes writing
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
draqkin said:
I have D855 32GB, installed Lollipop D85520A on it. (official polland rom as i learned) it has rooted but no recovery. so i tried to install TWRP but my phone is stucked in Fastboot mode. Can't enter download mode , when i try fastboot screen appearing again. i can use fastboot commands and tried to remove and reflash aboot, boot ang laf.img files. there is no error all is ok but no change... When i try to list my fastboot devices it says
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
? fastboot
but in device manager page i can see recognised as Android Bootloader Interface.
Also i cannot find 32GB 20A official kdz or img files so i tried 20H istead .
So how can i fix this problem???
Click to expand...
Click to collapse
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader

Can you erase recovery ? or not ? ( with command : fastboot erase recovery )
Click to expand...
Click to collapse
Yes i can erase and rewrite recovery and others with no error.
btw do u have an unlocked bootloader ?
mine is locked
i think this is why we're facing this problem .. cuz of locked bootloader
Click to expand...
Click to collapse
I don't know about my bootloader because i have bought my phone from someone else. It was rooted, used 3 days and tried to install twrp than *kaboom*. Stuck fastboot....

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

Reboot loop and can't get download mode and recovery mode ? (M9)

My m9 is rebooting when I plugged charge . I'm trying to flashing but I just enter fastboot . Can't get download mode and recovery mode. I used adb.
adb reboot bootloader
error: device '(null)' not found
----
fastboot devices
HT59FSV01842 fastboot
Please help!

If you cannot get to download mode the device is dead.

[Q] Vivo Y53 Bootloader Unlock | Fastboot Only | EDL not WORKING

Hello all,
A blessed day to all and many thanks to those who will answer.
The phone is on a bootloop and I can enter bootloader mode via Volume Down+Power. Tapping recovery doesnt work.
fastboot devices is OK. It shows the device.
EDL method doesnt work. The COM PORT wont show up.
fastboot bbk unlock_vivo doesnt work FAILED: (remote: unclock fail.)
fastboot vivo_bsp unlock_vivo. Nothing happens except shows the help text.
fastboot oem unlock doesnt work FAILED: (remote: unknown command or device is locked)
Is there anyway to flash a binary file just like in ASUS phones?
How can I unlock my bootloader?
Thanks in advance.

how to disable verity mode by fastboot?

this is my Z2 force,XT1789-3 4+64GB,and i replaced RAM chip ,now is 6+64GB. bootloader unlocked now.
but when I try to start the phone ,its can go into Fastboot mode only.its said Fail_through from normal boot mode.
fastboot official ROM failed,bootloader.img and GPT.bin cannot to flash.other files are flash all ok but no use to do.
I tried some methods by fastboot version26.0.0 ,but not work:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot oem disable_dm_verity
anyone can help me ?

today ,i tried blankflash_from_7.1NDX26.183-15_17.
then Found that BL model changed from MBM3.00-nash-sprint to MBM3.00-nash-verzion.
and can't enter blankflash mode anymore.The following methods have failed：
fastboot oem blankflash
fastboot oem -edl
fastboot reboot-edl
Does anyone know how Z2F enters the blankflash mode hardware switch or point？

OLDWhite said:
today ,i tried blankflash_from_7.1NDX26.183-15_17.
then Found that BL model changed from MBM3.00-nash-sprint to MBM3.00-nash-verzion.
and can't enter blankflash mode anymore.The following methods have failed：
fastboot oem blankflash
fastboot oem -edl
fastboot reboot-edl
Does anyone know how Z2F enters the blankflash mode hardware switch or point？
Click to expand...
Click to collapse
See if the information in this thread helps you.