Database Users

Fastboot, waiting for device.

Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.

ejnahuj said:
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
Click to expand...
Click to collapse
Hello
1. you need to install a ROM with fastboot the most common is europe + fastboot (KDZ) ROM.
http://www.mediafire.com/?96nu9lb6afx22a7
2. once its finished phone will reboot, then fast login into fastboot mode CAMERA + POWER
3. You are missin 1 thing, OEM usb drivers not GOOGLE usb drivers as some tutorial says, those are just for Android Developer Phones (ADP), Nexus One, and Nexus S.
LG_Android_USB_Driver_Rebuilt
http://www.mediafire.com/?pbigrb8cimmxa4d
* these drivers are for your pc to recognize your phone in fastboot mode, they are not the normal LG usb drivers
4. for install the drivers abouve follow these smll tutorials
* if using windows 7:
http://developer.android.com/sdk/win-usb.html#Win7
* if using windows XP:
http://developer.android.com/sdk/win-usb.html#WinXp
once is installed plug your phone in fastboot mode to your pc, now your pc has to recognize your phone wait until it finish installing the drivers and read it properly
5. unzip the new ROM files into C:\*SDK\tools
6. open CMD Terminal and go to C:\*SDK\tools, type:
cd C:\*SDK\tools
7. once in, type
fastboot flash recovery recovery_clockwork_3.x.x.x_swift.img"
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
*Just in case it drops you an error AdbWinApi.dll missing here is the file. place it in C:\*SDK\tools and try again
http://www.mediafire.com/?3s3z5uym2rw5r7u
Any other question PM me

fastboot "waiting for device"
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance

murthy.krishna00 said:
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
Click to expand...
Click to collapse
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App

Quinny899 said:
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Can you please clearly explain it, I couldnt get that. The prob was even though I installed the diver fastboot cannot detect the device..

Turn the phone off normally and when you'from holding down power to turn it on, also hold down camera until you get a black screen.
Sent from my GT540 using XDA App

[Q] Help with bricked Nexus 10

I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now

Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Thanks, that was pretty much what I did. The trick was to get it working in boot loader mode. I kept trying to reboot it, and in the end holding down power plus both volume up and down all at the same time for 2 beeps made it work.
Sent from my Nexus 10 using Tapatalk

nikkilocke said:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Click to expand...
Click to collapse
I have the same problem, however I can't access my Nexus 10, fastboot devices and adb devices gives back an empty line, so I can't access the N10 with fastboot or adb, to lash a ROM. Factory reset from CWM doesn't work, ˛internal card can't be accessed from CWM ("E: Can't mount /sdcard).
How can I get out of this trouble? (Solutions in forums usually involve reflashing with fastboot or formatting the external SD card. These solutions don't work here...
Any idea would be highly appreciated...
Csaba

Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk

nikkilocke said:
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
---------- Post added at 05:17 PM ---------- Previous post was at 05:00 PM ----------
ixxion said:
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
Click to expand...
Click to collapse
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba

You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app

ixxion said:
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
Click to expand...
Click to collapse
Glad you have managed to make the device visible again (it's really scary when you can't, I know from yesterday!).
Go into bootloader mode (not recovery), and follow the fastboot instructions demkantor gave earlier in the thread.
Get your factory image from https://developers.google.com/android/nexus/images#mantaray.
Get TWRP recovery from http://teamw.in/project/twrp2/128.
At least, that's how I did it.

demkantor said:
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I check md5sum?

Use this for windows
http://www.microsoft.com/en-us/download/details.aspx?id=11533
Or terminal for Linux
md5sum nameoffile.extention
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?

ixxion said:
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
Click to expand...
Click to collapse
That means you don't have twrp installed. That's the stock recovery. You can download twrp and use fastboot yo flash it or try the app twrp intaller which dies or fir you
Sent from my VS980 4G using xda app-developers app

i deleted my os

hi...
i unlocking bootloader
and i want to install factory image
but first i open recovery and i deleted every thing format system and every thing becase i want clean -_-"
so .. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot
i Didn't have this problem with my other N4
please help me -_-"

Only fastboot works when in bootloader, adb needs a custom recovery or android to work. Use fastboot to flash the images (run the install all bat file).

Marvlesz said:
Only fastboot works when in bootloader, adb needs a custom recovery or android to work. Use fastboot to flash the images (run the install all bat file).
Click to expand...
Click to collapse
i used fastboot
but it still waiting device
when i plug another n4 its work

box_zzz said:
i used fastboot
but it still waiting device
when i plug another n4 its work
Click to expand...
Click to collapse
uppppppppppppppppppppp

Connect your device to the PC in fastboot mode and type "fastboot devices". Do you get an output?
Remember that you have to run the command line from the folder where your fastboot.exe resides.
Sent from my Nexus 4 using XDA Free mobile app

box_zzz said:
hi...
i unlocking bootloader
and i want to install factory image
but first i open recovery and i deleted every thing format system and every thing becase i want clean -_-"
so .. when I plug the phone into my computer while in fastboot and try any adb commands.. I get nothing... It seems like the adb drivers aren't loading while in fastboot
i Didn't have this problem with my other N4
please help me -_-"
Click to expand...
Click to collapse
It happened to me once upon time, I've deleted EVERYTHING, only adb fastboot was working for me, so i connected my phone to my laptop and pushed system.img by wugfresh toolkit.. Try this way.. I hope it will resolve your problem.
Sent from my Nexus 4 using XDA Free mobile app

No Fastboot Option In Bootloader

I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.

It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.

RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.

RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.

JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?

RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.

teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app

RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.

JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.

RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine

RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices

He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk

Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.