Database Users

How to fix LG540GT

I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help

restart you pc and try fastboot again

Tryed but it didn't work,I have tryed it on another PC and without success

darac32 said:
I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help
Click to expand...
Click to collapse
bro this question was answered heaps of times..
search before posting..
Also this is supposed to be in the general section not
development..
Anyways go into clockworkmod if you can't connect to
pc and wipe everything and reflash with Recovery.

there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find

cccb010 said:
there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find
Click to expand...
Click to collapse
yeah i think i saw it as well..
forgot though..
Try the recovery, i had this problem as well!!
uninstall all drivers and reinstall them..
After that go to fastboot and type
fastboot -w
fastboot reboot

Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards

MrAndroid12 said:
Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards
Click to expand...
Click to collapse
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help

flash another recovery via fastboot

darac32 said:
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help
Click to expand...
Click to collapse
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img

jhonnyx1000 said:
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "

darac32 said:
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "
Click to expand...
Click to collapse
The 'display initialize' thing is a part of fastboot. Do the commands when you're in fastboot.
Sent from my GT540 using XDA App

er dudes remember that the blue screen and white text is only there if you use mur4ik's bootloaders and not the one you get from the kdz

If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz

Danzano said:
If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working

darac32 said:
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working
Click to expand...
Click to collapse
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .

Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium

airbus360 said:
Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium
Click to expand...
Click to collapse
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz

Danzano said:
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
I use Windows 7,but windows xp is no problem

mircea89fzr said:
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .
Click to expand...
Click to collapse
Tryed that but no response from phone,that is what makes my troubles ...
Everything rechecked twice ... but maybe somthing I miss but I don't think I did

[Q] Stuck in endless bootup logo - unable to stock flash

Hi Guys,
I'm stuck in the endless boot logo problem, I installed google drivers, I'm able to get into recovery mode.
the device manager in win7 reports a "android ADB Device" connected.
but when I issues some of the commands in this guide http://forum.xda-developers.com/showthread.php?t=1907796 (like adb devices) it doesn't show anything...
What I've to do?? Am I doing something wrong?
thanks

Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app

peneoark said:
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Already did that with no success... .

If your device is rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?

Djabolic said:
If are rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Click to expand...
Click to collapse
I'm not rooted,
when rebooting with power and vol- windows recognize the device but "adb devices" gives nothing"
If I select recovery mode the nexus disappears from windows device manager

Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.

Djabolic said:
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Click to expand...
Click to collapse
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager

lmalossi said:
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
Click to expand...
Click to collapse
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.

Djabolic said:
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Click to expand...
Click to collapse
but when if fastboot the command "adb devices" return nothing...

When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796

Djabolic said:
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I was already following your guide....
Didn't know that if I was already in fastboot mode I could issue fastboot commands even if adb devices didn't show anything...
N00b Error!! Now the thing is clearer to me
Flashed image, and the tablet appears to be working :fingers-crossed:
Thank you very much!!
Luca

[SOLVED] Z1 not showing up in Linux ADB devices

hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.

I think it´s a driver fault. Did u install them in windows?

im using linux, i dont get any rsa pop up confirmation either!

EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)

EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?

ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.

MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk

Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]

ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!

You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.

ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!

Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.

EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.

I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk

It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...

For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?

Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.

MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.

Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802

This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".

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.

The system has been destroyed please help

So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?

Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328

emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen

lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637

lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.

lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"

emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.

lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?

emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.

Try flashint stock on EDL mode.

Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!

Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.

yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.