Strange Problem On Bootloader/Fastboot

[aasiaasi]

Hello Everyone,

I Have A Strange Problem When I Press Power+Down Button Then Device Goes To Bootloader/Fastboot And Mi Bunny Appears, But After 3-5 Seconds Mobile Device Automatically Switch Off Without Connecting The Cable Or Doing Anything.

Note That, I Have A Latest Build V11.0.9.0.QDLMIXM Installed Without Rooting And Device Working Properly. Since I Just Want To Root The Device And Bootloader Is Unlocked. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode.

Thanks In Advance !!!

Thanks,
MUHAMMAD Asif Qasim

 

[a1291762]

Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)

 

[aasiaasi]

Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)

Thankyou For Prompt Response.
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.

In Addition To That, I Can Use ADB Commands & Shows My Mobile Connectivity When I Use.

Thanks,
MUHAMMAD Asif Qasim

 

[a1291762]

I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.

I run this on my PC and it waits for a device.

$ fastboot getvar current-slot
< waiting for any device >

3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).

If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?

 

[aasiaasi]

I run this on my PC and it waits for a device.

$ fastboot getvar current-slot
< waiting for any device >

3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).

If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?

Thank You Dear. Yes I Can Use The Command On ADB When Mobile Is Switched On Here Is The Example Snapshot.
The Problem Is That When I Boot To Bootloader It Doesn't Stay On Bootloader And Shutdowns Automatically With In 3-5 Seconds. As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.

 

[a1291762]

As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.

I don't know exactly what the bootloader does while in fastboot mode, but I'm going to guess it draws the rabbit and then gets ready to talk to the PC. And something fails and it dies.

If it's working normally, that's something... But it's going to stop you from unlocking the bootloader.

I have no idea how to fix. Maybe EDL with the test points? There are 2 aboot partitions (apparently hold fastboot).

# ls -l aboot*
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_b -> /dev/block/mmcblk0p32

 

[Mewwo2]

I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.

 

[aasiaasi]

I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.

Thankyou Mewwo2,
Could You Please Check Your Device ? Without Connecting The Cable , That Your Device Automatically Switched Off In Few Seconds Or Not. Please Let Me Know So I Can Figure Out Or Take A Clue For Fixation.

Secondly I Have Windows 8 And Drivers Are Properly Installed. If The Drivers Have Issue The Adb Command Doesn't Work And Doesn't Shows My Mobile (Note That I am Taking About When Mobile Isn't on Bootloader Mode)

Thanks In Advance...

 

[Mewwo2]

Can you type another adb command like 'fastboot oem device-info' and see the output.

 

[minicm94123]

it's not a problem.

Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.

You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.

 

[aasiaasi]

it's not a problem.

Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.

You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.

Thankyou For Your Support. I Will Check & Respond Accordingly.