Database Users

[Q] Vega stuck?

Situation:
Advent Vega running r6 Modaco ROM by Paul
Ubuntu 10.10 desktop PC in case it's needed
Tried to activate the USB Host Mode, as I wanted to plug a USB stick
It had been done before flawlessly.
The device came to a black screen with a prompt: "Starting Fastboot USB download protocol".
The device is unresponsive. Powering off the device and turning it on again brings only the same black screen with the prompt.
I've read somewhere that it's not bricked, but I certainly can't bring it to work. Has anyone encountered this issue?

Re-flash original rom from recovery. Power off and fully charge. Then hold down the back button for 2 sec then power for 2 sec then back for 2 sec. You also need to install the recovery drivers from the advent website. Not sure how that goes with ubuntu. Good Luck

First of all, thanks for your help.
Sigh. I've tried putting the device in Recovery mode (with a timer to count the seconds for every press) and the same Fastboot screen appears.
The lsusb command doesn't return any changes after plugging the Vega either, so I can say the computer is blind to the device. I have another Android device which is recognized flawlessly.

It took me a few attempts to get my device into recovery. Just keep trying with the device plugged in to your pc, eventually i got a unknown device in hardware manager. I then had to install the recovery drivers to get the device to show up.
I dont use ubuntu so cant tell you if its any different.

Oh,, it is. Nobody programs drivers for Linux, and Advent is no exception. I guess I can try and... compile the Windows ones?
For what it's worth my device is not recognised no matter where I plug it, so adb is out of the question.

Using a windows pc would be the easiest. Advent only likes windows for the time being. Sorry i cant help any further, i am not a Linux user.

Then I'll try tomorrow in college. Thanks for your help!
...Forgot to ask: Has anyone had the issue I'm reporting and successfully solved it after flashing?

I've never heard of a Fastboot prompt before, however, as far as I know, getting in to recovery should always be possible.
1) Get the screen on (doesn't matter what is on it).
2) Make sure it is unplugged.
3) Hold power for ~7 seconds until the screen turns off.
4) Plug it in and wait for the charge light.
5) Plug in the USB cable.
6) Hold back.
7) While holding back, press power for 1 to 2 seconds and release (keep holding back)
8) Within 2 seconds you should hear the PC's found USB noise (the screen will not turn on)
9) Once you hear the PC's USB connect noise, you can release back, install the nVidia driver (not ADB driver) and run the FW updater.
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.

rpmccormick said:
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.
Click to expand...
Click to collapse
I *think* I got that prompt because my device was already in USB host when I intended to toggle USB host. However, it's kind of disheartening to hear that the issue is new...
Shall I post a picture of the prompt?

Here is a (regrettably very poor, I'm no photographic whiz and the college lightning conditions are horrible) picture of the Fastboot prompt I receive.
{
"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've tried to enter Recovery mode today in one of college's computers (Windows XP). The device was recognized as "Nvidia ANdroid Fastboot device" after executing the recovery mode operation successfully. I was prompted to install the drivers, which I did, I was warned that they were unsigned, but on executing the Advent updater I had the following output:
Pressing Enter leads to the console closing and no changes have been done on the device: I'm not told that the image has been installed or anything, the Fastboot screen is still there, and powering on and off does bring me to the same than before.

Hi - I'm now in the same situation with the Fastboot error and no recovery no matter what I try.
Have you been able to boot to recovery / flash your Vega or is it still sitting with the error message ?

I'm going to try again today (Free day, no college )

A re flash will sort it out. I done it 5 times in the past 2 days to test CWM. Just count 2 seconds back button, 2 seconds back and power and 2 seconds back button alone again and it will be in recovery. I do it every time first time. It's just a matter of getting used to it. Then plug the vega in and it will recognise it, you will see by starting the original 1.08 firmware again, the vega screen is blank, no back-light.

I couldn't do it yesterday, but it worked today. I am now on stock 08 and I'm very happy. Thanks for all the help!

[Q] Help! Lenovo yoga 2 tab 1050L broke

My yoga 2 1050L broke while I tried to flash it with:
"Rooted_YT2_10_prc_call-blankphone-user-YT2-1050LC_USR_S000018_1409241649_WW21_CN"
It was flashing well untile 88% "unknown commend"
now I'm getting "EFI BOOT FAIL HARD DRIVE" and it's keep opening the bios,
and I can't even flash it with the 1050L stock rom

??????????????

MohamedStar said:
??????????????
Click to expand...
Click to collapse
1. power off the tablet if it's on (long press pwr btn until shuts off)
2. press and hold Vol+ & Vol- keys, while keeping them pressed press shortly(2-3 sec) PwrOn btn to start tablet, keep Vol keys pressed until the screen says: starting fastboot.. after you can release them (this fastboot mode is different in regards to the standard one as it is started directly from BIOS, disregarding what you have/or not have on your hard drive, so it's good for unbricking), the screen will remain unchanged to the starting fastboot message, but that's ok, the bios is waiting commands already
3. flash your stock ROM as usual (use flash.xml file) using Intel Flash Tool
for root use the much more simpler(generic and safe) method described here http://forum.xda-developers.com/showpost.php?p=62815888&postcount=698

Please Help!!!!!!
ionioni said:
1. power off the tablet if it's on (long press pwr btn until shuts off)
2. press and hold Vol+ & Vol- keys, while keeping them pressed press shortly(2-3 sec) PwrOn btn to start tablet, keep Vol keys pressed until the screen says: starting fastboot.. after you can release them (this fastboot mode is different in regards to the standard one as it is started directly from BIOS, disregarding what you have/or not have on your hard drive, so it's good for unbricking), the screen will remain unchanged to the starting fastboot message, but that's ok, the bios is waiting commands already
3. flash your stock ROM as usual (use flash.xml file) using Intel Flash Tool
for root use the much more simpler(generic and safe) method described here http://forum.xda-developers.com/showpost.php?p=62815888&postcount=698
Click to expand...
Click to collapse
sorry to say but the following didn't work for me still stuck in bios and Flash Tool keeps saying
05/26/16 00:07:14.679 INFO : Port 0/10: Rebooting BaytrailD13EBC1E in Provisonning OS (current state = DNX_STATUS)
05/26/16 00:07:14.679 INFO : Port 0/10: Cannot Reboot android device, status is DNX_STATUS
so now what need to fix this device!! PLEASE HELP!! ;-(

TechTanium said:
sorry to say but the following didn't work for me still stuck in bios and Flash Tool keeps saying
05/26/16 00:07:14.679 INFO : Port 0/10: Rebooting BaytrailD13EBC1E in Provisonning OS (current state = DNX_STATUS)
05/26/16 00:07:14.679 INFO : Port 0/10: Cannot Reboot android device, status is DNX_STATUS
so now what need to fix this device!! PLEASE HELP!! ;-(
Click to expand...
Click to collapse
Try this
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Don't unplug the USB, every time u unplug the USB you must update the driver again
I don't know if this'll work for you I'm not developer but you can try.

ok tryed to follow that tortorial but when I get to devece manager step I get this for my tablet on fastboot + usb conected !!
Screen shot
{
"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"
}
PLEASE HELP NEED MY TAB TO WORK!! ;-((
MohamedStar said:
Try this
Don't unplug the USB, every time u unplug the USB you must update the driver again
I don't know if this'll work for you I'm not developer but you can try.
Click to expand...
Click to collapse
---------- Post added at 12:40 AM ---------- Previous post was at 12:33 AM ----------
ok tryed to follow that tortorial but when I get to devece manager step I get this for my tablet on fastboot + usb conected !!
Screen shot Gyazo Screen shot number 7d530b85044c23739eab9a4df4c2d826
PLEASE HELP NEED MY TAB TO WORK!! ;-((
MohamedStar said:
Try this
Don't unplug the USB, every time u unplug the USB you must update the driver again
I don't know if this'll work for you I'm not developer but you can try.
Click to expand...
Click to collapse

TechTanium said:
ok tryed to follow that tortorial but when I get to devece manager step I get this for my tablet on fastboot + usb conected !!
Screen shot
PLEASE HELP NEED MY TAB TO WORK!! ;-((
---------- Post added at 12:40 AM ---------- Previous post was at 12:33 AM ----------
ok tryed to follow that tortorial but when I get to devece manager step I get this for my tablet on fastboot + usb conected !!
Screen shot Gyazo Screen shot number 7d530b85044c23739eab9a4df4c2d826
PLEASE HELP NEED MY TAB TO WORK!! ;-((
Click to expand...
Click to collapse
If u able to go throw fastboot then try to flash kitkat bios from this and (just follow the instructor):
http://forum.xda-developers.com/attachment.php?attachmentid=3783701&stc=1&d=1465980824
after that just flash any kitkat rom, good luck.

MohamedStar said:
If u able to go throw fastboot then try to flash kitkat bios from this and (just follow the instructor):
http://forum.xda-developers.com/attachment.php?attachmentid=3783701&stc=1&d=1465980824
after that just flash any kitkat rom, good luck.
Click to expand...
Click to collapse
Dear MohamedStar
Thanks a lot for attaching the link above, you saved me from an boot failure efi hard drive issue. Thanks a gain

samehhakim said:
Dear MohamedStar
Thanks a lot for attaching the link above, you saved me from an boot failure efi hard drive issue. Thanks a gain
Click to expand...
Click to collapse
I'm glad it helped :good:

Thank you so much man for the replys Really
MohamedStar said:
If u able to go throw fastboot then try to flash kitkat bios from this and (just follow the instructor):
http://forum.xda-developers.com/attachment.php?attachmentid=3783701&stc=1&d=1465980824
after that just flash any kitkat rom, good luck.
Click to expand...
Click to collapse
I did the following and theoretically it should work perfectly but it still comes up with this https://gyazo.com/33d795031aeda6a8710af55da541651f
I don't understand ??? phone flash tool says it is in DNX mode this says its not!!???

QuietLife said:
If u able to go throw fastboot then try to flash kitkat bios from this and (just follow the instructor):
http://forum.xda-developers.com/attachment.php?attachmentid=3783701&stc=1&d=1465980824
after that just flash any kitkat rom, good luck.
Click to expand...
Click to collapse
i plugged my lenovo yoga tab 2 1050L in fastboot starting, then select 'c' to continue in the tool, but the program is stucked in "Sending files for booting in fastboot mode" and while waiting the screen in my tablet just shut down and nothing happened. Intel Flash Tool just turn on the device but can't detect it.

Repair HuaweiP8Lite

Hello. It can be fixed by yourself?
I had a cell phone connected to a PC for charging only mode. I picked him out of a MicroSD card, reboot and start-up steps.
There was a version of ALE L21C432B551 Singles
Thank you for your help
{
"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"
}

You deleted boot image *facepalm*
Download update.app and unpack it with huawei extractor then use adb command
Fastboot flash boot boot.img
Sent from my Che2-L11 using XDA-Developers mobile app

MarcoPLs said:
You deleted boot image *facepalm*
Download update.app and unpack it with huawei extractor then use adb command
Fastboot flash boot boot.img
Sent from my Che2-L11 using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you me a better description of the process how? I have downloaded ALE L21C432B551.rar size of about 1.60GB

extract update.app from the zip then huawei extractor tool , excrat the boot.img from that update.app then flash it in fast boot mod via the command above
Note: the firmware version on your phone should be B551 too juste like the rom you downloaded

AmINoS007 said:
extract update.app from the zip then huawei extractor tool , excrat the boot.img from that update.app then flash it in fast boot mod via the command above
Note: the firmware version on your phone should be B551 too juste like the rom you downloaded
Click to expand...
Click to collapse
All this mama but I can not connect the phone
What combination of buttons should be used ?
error: device not found

plug it into the laptop and push power button and vol- button together
Drivers need to be installed
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
In case all this does not work
Plug the phone into the laptop and push power button and vol+ and vol- button at the same time , the phone will download and flash rom automaticly from pc but it can take time it depends on your network speed

AmINoS007 said:
plug it into the laptop and push power button and vol- button together
Drivers need to be installed
Click to expand...
Click to collapse
I am still fits on the TV screen, which I above shows. Niejak the lends can not get the PC to at least react to connect mobile

i didn't really understand but to restart the phone keep pushing power button for arround 10 secondes

AmINoS007 said:
i didn't really understand but to restart the phone keep pushing power button for arround 10 secondes
Click to expand...
Click to collapse
Phone can not be switched off. While pressing the power button only restarts. Let him recharge. Yesterday I managed to get to the menu VOL + VOL - and VOL -. Today it is not. I do not know why. Let him recharge and try later.

ok i get it
Good luck

AmINoS007 said:
ok i get it
Good luck
Click to expand...
Click to collapse
Aki driver needs to be installed ?

there is no driver zip as I know , to install drivers you need to connect the phone to pc via Hisuite tool

AmINoS007 said:
there is no driver zip as I know , to install drivers you need to connect the phone to pc via Hisuite tool
Click to expand...
Click to collapse
Just use only this one command?
Fastboot flash boot boot.img

since you only have boot.img problem, yes , just this command

AmINoS007 said:
since you only have boot.img problem, yes , just this command
Click to expand...
Click to collapse
It is possible that after 2 hours charging battery still is not charged? When you disconnect the USB cable so I got to FlashModu and try to turn it on so I immediately shows the logo of charging and the LED flashes twice, steam green

Try this:
Plug in your USB Cable into your computer but NOT to your phone.
Then press and hold Volume Down and plug in your USB Cable into the phone while Holding Volume Down

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?

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.