Fastboot : FAILED (remote: flash write failure) - G3 Q&A, Help & Troubleshooting

I recently bricked my phone and got stuck at fastboot. Any command i enter to erase or flash the image is failed. No download mode, no recovery. My pc detects it as "Marshall london Bootloader Interface". Help me guyz.

Related

I am stuck with fastboot mode error : failed (remote flash write failure)

I am stuck with fastboot mode error : failed (remote flash write failure)
I am using a G3 phone. Which appeared to have a IMEI of d855 but its motherboard is of 850. I tried to flash kdz for 855 on it.. but now its stuck in fastboot mode with fastboot mode error : failed (remote flash write failure) . Whatever I've tried to do.. The same error appears.. any go around this error ??.. Please any help would be appreciated.. Thank you

Stuck in bootloader –*not able to flash anything.

Hello and merry christmas.
I wanted to flash my BQ M5 with the new firmware 5.1.1 and now i'm stuck in bootloader with no way out?
To shorten it up: I did a fastboot flash sec sec.dat because i thought that this would fix things.
After a reboot-bootloader i ended up on a Fastboot-screen with a Linux Penguin in the middle. (i never had this before)
now any flash command suddenly ends in FAILED (remote: device is locked. Cannot flash images)
(flash-commands worked before with a unlocked bootloader)
but re-unlocking the bootloader with
fastboot oem unlock-go ends in FAILED (remote: oem unlock is not allowed)
(This worked before after enabling OEM-unlock in the Developer options.)
Robooting brings it directly to the penguin-bootloader with no possibility to flash anything(?) or to unlock(?)
Is it now totally bricked?
Thanks for any advice!!
AK

Cannot flash recovery

OK I have a problem. Till now:
1. Installed drivers
2. Bootloader unlocked
3. ADB enabled. PC authorised.
4. OEM unlocking permitted confirmed.
5. Command fastboot devices shows phone connected in fastboot mode.
EDIT: Solved. Experimented with different drivers on different laptop.
Now trying to send official twrp with command fastboot flash recovery recovery.img and I get error:
sending 'recovery' (18680 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
Can't seem to get a solution to this
Any help?

Bootloop after flashing eUI 5.8.19S

Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
coolcoder001 said:
Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
Click to expand...
Click to collapse
R u able to use twrp???

Failing install twrp in fastboot mode

I recently purchased redmi note 5 pro.
I'm using miui 10 Oero version, but I want to install recovery such as twrp for installing custom ROMs.
So, I searched for the process on the Internet.
I think that adb driver and fastboot driver are installed well in my PC (Window 10) .
That's because I can control my phone in adb mode.
I can find my phone in "adb devices" command and reboot it in "adb reboot bootloader" command
Also, I can find my phone by entering "fastboot devices" in fast mode, which shows the same serial number as that in adb mode.
However, I cannot flash or boot using downloaded twrp.img in fastboot mode, showing as follows.
=======================================
>fastboot boot twrp.img
downloading 'boot.img'
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
=======================================
I also used "fastboot flash recovery twrp.img" the command, but there is no response.
Could anyone tell me the solution for this problem? :crying:
You have to unlock bootloader as well

Categories

Resources