Database Users

I think i broke my Redmi

I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?

1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)

Danoz88 said:
1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)
Click to expand...
Click to collapse
ok new problem, i plug the deep flash cable and it says hardware malfunctioned repeatedly
this one scared me and the device cannot charge
i'm thinking about test point method but i have to wait ordered small torx driver on monday

UPDATE:
After using test point. nothing changed except the device ID number is weird
{
"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"
}

How is it displayed in fastboot mode? Deepflashcable also doesn't worked for me because I read that on the newer rom's the edl mode is blocked so no chance with dfc anymore (thanks xiaomi...). It only reboots if I tried everything (commands,dfc,file..).
I had to flash an older version first via fastboot mode. After this I was able to reboot into edl mode with 0 problems. And I never tried the test point methode, not the right tools.

cant goto recovery, cant go to fastboot, test point tested 2nd time and its work.. flash success
but the screen still blank.
if i plug my usb cable to laptop its onlt shows MTP and green led light

I Know How To Fix This...
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
---------- Post added at 04:29 AM ---------- Previous post was at 04:23 AM ----------
rs168 said:
I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?
Click to expand...
Click to collapse
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .

amangupta711 said:
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
Click to expand...
Click to collapse
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same

Try this!!!
rs168 said:
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same
Click to expand...
Click to collapse
Hold power and vol down button for 20 sec.

amangupta711 said:
Hold power and vol down button for 20 sec.
Click to expand...
Click to collapse
it has been said.. nothing

Redmi 3X Hard Bricked. No Access to Recovery and Fastboot

So, yesterday I just unlocked bootloader redmi 3x. It’s successfulnothings wrong with that. So, I start to flash my phone using MiFlash2016.08.30.0, after a few minutes the screen phone turn into black(like sleepstate), and the miflash show the flash is complete, but the progress is keptrunning(like the time elapse still counting). After waiting for 30 minutes ejectthe usb cable, and miflash kept running like I said before. And my phone can’tenter fastboot, enter recovery.
After searching any solution. I started to use method testpoint. And the devices is detected in the Device Manager also in MiFlash. Buteverytime I flash the phone at 179 second the phone always have result
“Read packet hello”
“Can not read packet hello. Mi flash try to reset status”
…
…
And the progress is stop and showed the result “cannotreceived hello packet”
I'm using
- Windows 10 Pro x64
- MiFlash 2016.08.30
And I already try to flash this rom
- land_global_images_7.9.15_20170915.0000.00_6.0_global
- land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global
- land_images_V9.5.3.0.MALCNFA_20180309.0000.00_6.0_cn_28cc4d1a97
Is there something that I missing ?, also can I get my phoneback ?
i put the log in attachment
Thank you
{
"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"
}

reynandapp1997 said:
So, yesterday I just unlocked bootloader redmi 3x. It’s successfulnothings wrong with that. So, I start to flash my phone using MiFlash2016.08.30.0, after a few minutes the screen phone turn into black(like sleepstate), and the miflash show the flash is complete, but the progress is keptrunning(like the time elapse still counting). After waiting for 30 minutes ejectthe usb cable, and miflash kept running like I said before. And my phone can’tenter fastboot, enter recovery.
After searching any solution. I started to use method testpoint. And the devices is detected in the Device Manager also in MiFlash. Buteverytime I flash the phone at 179 second the phone always have result
“Read packet hello”
“Can not read packet hello. Mi flash try to reset status”
…
…
And the progress is stop and showed the result “cannotreceived hello packet”
I'm using
- Windows 10 Pro x64
- MiFlash 2016.08.30
And I already try to flash this rom
- land_global_images_7.9.15_20170915.0000.00_6.0_global
- land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global
- land_images_V9.5.3.0.MALCNFA_20180309.0000.00_6.0_cn_28cc4d1a97
Is there something that I missing ?, also can I get my phoneback ?
i put the log in attachment
Thank you
Click to expand...
Click to collapse
Hi, Do yourself such cable from a normal USB micro usb cable:
Deep Flash USB http://en.miui.com/thread-310325-1-1.html
It is normal USB cable, but shorten together black and green lines.
Be sure you have one more unmodified normal micro usb cable.
1. Then plug in modified cable in PC usb and connect the phone.
2. push Vol+, Vol- and Power buttons together for more than 15sec, eg. 20sec.
Even the screen is dark and no activity (like your device is in power-off ) is displayed, the magic should happen.
3. Then connect normal USB cable to PC and plug the phone.
4. Download (if you don't have it) latest official ROM. And unzip it.
5. Now important : DO NOT USE MiFlash at all.
6. Find and Click right mouse button on flash_all.bat file and select 'Run as administrator'
7. Wait until device is get flashed.
Reboot it if needed.
Ask if something goes wrong.

thank you for your replied
okay i get it, i'll try this method tomorrow maybe

bro i have the same situation my phone was redmi 3s prime completely bricked i thought i lost it ,i watched many tutorial but they don't worked for me deep flash cable needs short circuiting which can cause more damange to my phone so i Don't wanna try it firstly i tried mi flash directly to flash my bricke phone but it didn't detected by my pc,
then i disabled my driver signature verification
and installed mi flash again .
after doing this when i connect the phone using mi data
cable it was detected às unknown usb device only once,
but i haven't downloaded the fastboot rom yet, so i have to pulg it out ,when i downloaded and connected it again it didn't show up , i thought might be cabel is faulty but it was good , i puted it fpr charging around 10 mins however phoen shows nothing but its charging
after few mins i connected it again to pc but it was detected as usb device which i want to be port or com
so i pull out the cable from phone hold the volume up and down and plug it in phone afyer few seconds pc detected my phone as Qualcomm hab usb hub.....
started mi flash my device is available
clicked on flash , flashing taked around 20 mins,
after 20 mins it shows success , but didn't turned on , i thouught it got worth of a shot , tried very key combination but didn't worked, puted it again for charging around 20 min , after 20 min when i pressed volume up and power key together for 30 second it vibrated and tuened on booting takes 15 mins and now my phone is back to life

reynandapp1997 said:
So, yesterday I just unlocked bootloader redmi 3x. It’s successfulnothings wrong with that. So, I start to flash my phone using MiFlash2016.08.30.0, after a few minutes the screen phone turn into black(like sleepstate), and the miflash show the flash is complete, but the progress is keptrunning(like the time elapse still counting). After waiting for 30 minutes ejectthe usb cable, and miflash kept running like I said before. And my phone can’tenter fastboot, enter recovery.
After searching any solution. I started to use method testpoint. And the devices is detected in the Device Manager also in MiFlash. Buteverytime I flash the phone at 179 second the phone always have result
“Read packet hello”
“Can not read packet hello. Mi flash try to reset status”
…
…
And the progress is stop and showed the result “cannotreceived hello packet”
I'm using
- Windows 10 Pro x64
- MiFlash 2016.08.30
And I already try to flash this rom
- land_global_images_7.9.15_20170915.0000.00_6.0_global
- land_global_images_V7.5.9.0.MALMIDE_20160805.0000.29_6.0_global
- land_images_V9.5.3.0.MALCNFA_20180309.0000.00_6.0_cn_28cc4d1a97
Is there something that I missing ?, also can I get my phoneback ?
i put the log in attachment
Thank you
Click to expand...
Click to collapse
this may sound weird
but try it if u want
open the back cover, and unscrew the top part
there u'll see a battery connector
unplug it and plug it again and you will have fastboot and edl access

Did you solve this?

EDL Mode HD1925

So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!

I always power off my phone. Then hold both volume buttons down and plug it in. MSM tool sees my phone and hit start.

which Qualcomm drivers you installed ? because my phone is not connecting with MSM tools ....

I'm having the same issues. Anyone find a fix?

Charles: said:
I'm having the same issues. Anyone find a fix?
Click to expand...
Click to collapse
I installed twrp recovery software to go into EDL mode after that all works fine and connected

Zain ul Abedin said:
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Click to expand...
Click to collapse
Which TWRP?? Did you load it via Fastboot and use Fastboot commands? Are you A11? Which Qualcomm drivers?

I basically forget that , but search about it . And install TWRP in your phone

otoyayamaguchi said:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
Click to expand...
Click to collapse
I think it's supposed to only last for a few seconds. Pull up the MSM Tool and pay attention to the "Status of Connection" field for any of the COM lines in the MSM Tool. When you connect, it should say "Connected" for one of those lines. If that happens at all, then you're good to proceed. Make sure you have TMO selected in the drop-down, click "Enum" once you plug in your device, then click Start. Try to do this quickly. Let me know if this helps.

I am having the same problem with my 7T Pro McLaren, the pc recognizes it but msm tool does not, someone has already found the way
{
"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"
}

I had the same issue. One easy fix is switching from a USB 3.0 port to USB 2.0 port. The other method that worked for me is a little more of a process.
1) Have MSM open
2) Connect phone to PC
3) Power phone off
4) Then, the moment it powers down, hold the vol +, -, & power button
5) Keep holding it. Your PC will make a sound notifying you that it's detected the phone, but you want to keep
holding the buttons until you hear it being detected for the second time.
6) Release buttons.
Hopefully that makes it stay in EDL mode for you.

I wrote on this somewhere, but you can try having the program open and placed at the right settings, then move quickly once the phone is in EDL mode. Not ideal but worked for me. Once the process begins it won't exit out of EDL mode in my experience.

hii, from most tutorial i have seen so far, the com number is show in the msm tool upon starting the program, most the two msm tools i have tried so far dont show com number... and its not detecting my phone.

Fire HD10 9th Gen Boot Loop

I have a 2019 9th gen maverick HD10, that has recently went into a boot loop.
unit is reporting OS 7.3.1.8, and it has never been rooted or moddeed in any way apart from loading google play etc with no root.
when turned on, it displays the white amazon logo for 3 secs, then reboots for ever.
I have tried to recover it by holding power and volume up/down (seems to be down for mine?) and i manage to get into android recovery, but there is no option to update from ADB any more.
i have cleared cache and did the factory reset option, but it does nothing, reboots to same loop.
when i reboot into bootloader, the unit says fastboot in the bottom corner in tiny writing.
i have installed the google adb drivers, but fastboot does not detect the tablet. windows recognises a device is attached with the chime noise. i am suspecting wrong drivers?
all i want to do is restore the original FW and make the unit usable agaion. warranty ran out 4 weeks ago.
is there a way to restore original FW with fastboot?

gazcoigne said:
I have a 2019 9th gen maverick HD10, that has recently went into a boot loop.
unit is reporting OS 7.3.1.8, and it has never been rooted or moddeed in any way apart from loading google play etc with no root.
when turned on, it displays the white amazon logo for 3 secs, then reboots for ever.
I have tried to recover it by holding power and volume up/down (seems to be down for mine?) and i manage to get into android recovery, but there is no option to update from ADB any more.
i have cleared cache and did the factory reset option, but it does nothing, reboots to same loop.
when i reboot into bootloader, the unit says fastboot in the bottom corner in tiny writing.
i have installed the google adb drivers, but fastboot does not detect the tablet. windows recognises a device is attached with the chime noise. i am suspecting wrong drivers?
all i want to do is restore the original FW and make the unit usable agaion. warranty ran out 4 weeks ago.
is there a way to restore original FW with fastboot?
Click to expand...
Click to collapse
Boot your device to Fastboot mode and run
Code:
fastboot flash update.bin
If you have a problem with ADB drivers caused by older Windows 7/8. Update your PC to Windows 10.

I am running Windows 10
I have tried several times to install adb drivers but my device still comes up in device manager as android with an exclamation mark so my system does not discover device in fastboot just hangs on waiting for device

ok after a lot of playing with driver installs, I finally managed to get the correct ADB drivers installed, and in CMD i am now able to get fastboot to show me a device id
{
"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"
}
but when i run the command above it errors out, seems i have to define the partition
any suggestions?

Download the latest firmware onto the computer from amazon. then type fastboot flash C:\Location of file you downloaded. FYI Fastboot and ADB are different..... A question, what were you doing prior to it going into a bootloop? In recovery you may have the option to install update, sorry it has been a long time since i was on stock...

Michajin said:
Download the latest firmware onto the computer from amazon. then type fastboot flash C:\Location of file you downloaded. FYI Fastboot and ADB are different..... A question, what were you doing prior to it going into a bootloop? In recovery you may have the option to install update, sorry it has been a long time since i was on stock...
Click to expand...
Click to collapse
it seems to be a failed update, it was working one night then i woke up next morning to it froze on the amazon boot logo.
i force restarted the tablet, and it went into a boot loop, logo for 2 secs, restart and repeat.
i am well aware of the difference in adb and fastboot, but they both use the same adb driver.
i have recovered many fire tablets over the years with adb, but this tablet does not have the "normal" recovery options, seems amazon devs are trying to remove root abillity from recovery
below is the only options i have when getting to recovery
youll notice there is no more revocer from adb option. only thing i can do is boot to bootloader. this is where it goes into fastboot mode and it is now responding to commands like reboot etc, but the bootloader is locked to prevent downgrading for root.
i have wiped data/factory reset and cache, with no effect.
in normal circumstances, recover from adb lets you use the OS bin file downloaded from amazon, which i have done many times.
fastboot seems to need a list of partitions and offsets to write individual portions of the firmware, which is where im getting lost.
ive read on other android forums about fastboot you need to create a bat file with the list of files and offsets etc but no idea where to start.

doing the suggested command yields this error

gazcoigne said:
doing the suggested command yields this error
View attachment 5326399
Click to expand...
Click to collapse
Sounds like you might be bricked. Do you know when it was purchased? It's a long shot, but the first few months of the release of maverick have access to the bootrom which is unlockable.

nah i have gave up on this and purchased a new 2021 model will keep an eye on ebay for a broken one that i can swap the logic board out.

How to bypass fastboot low battery warning / FAILED (remote: Warning: battery's capacity is very low)

Hello Everyone I'm writting this post to hoping that This would help many people. Because I didn't find any proper solution for this on the internet.
Scenario: Suppose you flashed wrong file or did something wrong and somehow you bricked your device in such a state where your device will only go to fastboot mode stable or unstable fastboot mode ( fastboot restarts itself after few seconds).
Means your boot/recovery all destroyed. Luckily your bootloader is unlocked. So you felt realx thinking that you can flash recovery/boot from fastboot to fix your device. Then you flashed an image through fastboot and saw an warning like " FAILED (remote: Warning: battery's capacity is very low)".
{
"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"
}
Thats when the problem begins .
It's because before device got bricked it had very low charge. And without boot or recovery image your device don't know how to charge itself. So weather if your device is in fastboot or edl 9008 don't expect it to charge itself. And by fastboot rule it won't accept any file if it has low battery.
For exactly below 3478mV any file writing is unacceptable.
I found a solution on XDA How to fix the 'Low Battery' fastboot loop . Basically it's a fastboot script which restarts bootloader in a continues loop to charge it in the mean-time of reboot to fastboot.
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
I mean no disrespect to that post, The way it was trying to do it maybe it make some sense but not much.
Because like others I have run this script for several hours for several times and got no result. I was running this script on laptop then i thought maybe laptop is not giving proper output delivery. Then I tried with my desktop back usb port but no good.
Instead for running this script so long that in those thousands reboot my device surely lost some of its lifetime early and it corrupted my internal partition which I've discoverd after fixing my device.
Ok then the next option I had was opening the backshell which I don't want. Tried customer service they denied because of unofficial device. Local shops failed also they tried to open back shell but I didn't let them.
So your'e basically doomed like me because Brands like realme doesn't provide any flash tool/flash tool credentials for free. And remote unbrick is very much costly.
Solution:
After trying many things I found an App on play store Called Bugjaeger Mobile ADB - Develop & Debug via USB OTG.
Requisitions :
1. NO Root Required
2. App itself
3. Good OTG cable
4 Proper USB cable
5. Nothing else
For stable fastboot user:
First download the app in a device which support OTG connection. plug in otg cable.
Now connect your device to other device via OTG in fastboot mode. Now press on < > This icon and type your command like you do In pc
for example "fastboot flash recovery" after recovery give a space and click on attachment icon in the top right corner then select your file. Then run the command .
Boom you have successfully ignored fastboot low battery warning. Enjoy.
For unstable fastboot users:
I have calculated that my device was restarting in every 5 secons. could be different for you.
So what I did. Before going to fastboot mode the app show some AD.
so first disable it by adding private DNS like dns.adguard.com or better turn off wifi/mobile data.
Then suppose you want to flash recovery so make copy of command 'fastboot flash recovery" this will save 2 seconds and keep your file in your root directory so it will also save time. After everything set hit flash As soon as possible.
My recovery size was 98 mb and It had only 2 seconds to push it to the device. It said " sending recovery ok- writing failed" so you better use good cable.
Means it was able to successfully sent the file but didn't got image writing status because your device got turned off. But don't worry.
sent the img file was all the things we needed. I tried it 2 times and it works.
If it is unclear please watch the video to how to use this app
Tips:
1. Never do any risky task with low battery .
Conclusion : I'm not responsible if anything goes wrong with your device. I shared it only thinking that this will save many people from hassels.
Thank you.

So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?

mike_san said:
So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?
Click to expand...
Click to collapse
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?

Bishnu840 said:
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?
Click to expand...
Click to collapse
I've to run; adb reboot recovery, then in stock recovery I can run 9008 qualcomm state and it is detected by windows.

I has the same problem, but only with recovery flashing. For other partitions flashing works correct.
I just deleted recovery:
Code:
fastboot erase recovery
Аnd the problem is gone.
Now i can flash it:
Code:
fastboot flash recovery recovery.img
Device: Oukitel k7 power.
Sorry for bad englich.