Develop Bugs

Urgent - Boot and recovery problem!

Hi to all
I have a big problem. My HTC Desire HD is now "dead". So, everything is working normally, just fine, on JellyTime, but this afternoon everything get broken. Suddenly, after the boot animation is finished, nothing happens, the screen is "black". The phone works, because when I connect USB to the computer sound. I can not get into Recovery (Home + Volume Down), can not do anything. I tried to remove the battery, but it does not help. I tried with adb, but there is "error: device not found". So I installed the drivers, asking me activate USB Debugging on the phone, and I can not access the phone.
Do you have any idea how to access recovery mode and install the new ROM?
Please help!
Thanks in advance.

just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery

JJeamy said:
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
Click to expand...
Click to collapse
I try, but I can't. :crying:

SkipperRi said:
I try, but I can't. :crying:
Click to expand...
Click to collapse
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?

JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
I finally managed this problem. I pulled off the battery over the night, and this morning I can booted into the recovery. So, I installed new ROM, all my apps, and now I performed backup to the my PC.
Thanks for help!
Regards.

Again same problem. For few hours everything seems fine, but just now my HTC has "blank" screen... Nothing to do. Again, I can't go to Recovery, nothing... What's going on with this phone?!?!

JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
How to do this? And, if I do that, will be my phone still rooted after that?

SkipperRi said:
How to do this? And, if I do that, will be my phone still rooted after that?
Click to expand...
Click to collapse
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?

JJeamy said:
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
Click to expand...
Click to collapse
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?

SkipperRi said:
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
Click to expand...
Click to collapse
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..

JJeamy said:
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
Click to expand...
Click to collapse
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!

SkipperRi said:
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
Click to expand...
Click to collapse
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC.. if not just downloading from here..
and already had installing the latest HTC driver on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)

JJeamy said:
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
Click to expand...
Click to collapse
Thank you so much! I'll go and try right now and let you know what's going on.

JJeamy said:
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
(all command w/o quote)
Click to expand...
Click to collapse
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!

SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that

lexuz said:
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
Click to expand...
Click to collapse
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...

SkipperRi said:
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
Click to expand...
Click to collapse
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum

SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom

lexuz said:
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
Click to expand...
Click to collapse
Thank you anyway...
JJeamy said:
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
Click to expand...
Click to collapse
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?

SkipperRi said:
Thank you anyway...
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
Click to expand...
Click to collapse
i'm not sure about that..until now..what i see is still software related..but i don't know what software exactly had the problem is..
can be from the recovery that you had installed the rom..or else..
to make sure what exactly is.. you must return the phone to the stock..stock bootloader, stock rom and stock recovery too..all back to the stock..with flashing stock RUU while your phone back in normal condition..
you know the forum rule is doesn't give any permission to all member for compare the rom..

<<.>>Asus Zenphone 2 z008 stuck after hard reset cannot open!>> I am out of options:(

<<.>>Asus Zenphone 2 z008 stuck after hard reset cannot open!>> I am out of options
Dear all kind developers ,
I went to the recovery mode of my asus zenpone 2 and wipe of the data from it.
After I clicked data wipe it did not continued , it was stuck for like 20 minutes and I restarted the phone .
After that every time I try to open it or go to recovery I cannot open the phone. It only shows an android logo and an error.
I can go to the boot loader menu .
I have already searched the whole internet and found I solution for it , which I have to
* Download intel driver, and some abd files
* Enable Usb debugging and switch of the phone
* Go to boot loader and switch volume up until it shows fastboot
* Connect the phone via usb and open the adb files in cmd
* Type fast boot remove cache in the cmd
And it says that the phone will be alright after the process !
BUT, I DID NOT KEEP THE USB DEBUGGING TOOL ON ALL THIS TIME !
Can anybody help me with a solution to this ! Please

When you have that error logo, press your volume button and then power button and release it immediately. I think thats how you get into recovery mode/bootloader menu. If this doesn't work, try its vice versa because its been a long time since I've gone ito recovery mode/bootloader menu.

rooter789 said:
Dear all kind developers ,
I went to the recovery mode of my asus zenpone 2 and wipe of the data from it.
After I clicked data wipe it did not continued , it was stuck for like 20 minutes and I restarted the phone .
After that every time I try to open it or go to recovery I cannot open the phone. It only shows an android logo and an error.
I can go to the boot loader menu .
I have already searched the whole internet and found I solution for it , which I have to
* Download intel driver, and some abd files
* Enable Usb debugging and switch of the phone
* Go to boot loader and switch volume up until it shows fastboot
* Connect the phone via usb and open the adb files in cmd
* Type fast boot remove cache in the cmd
And it says that the phone will be alright after the process !
BUT, I DID NOT KEEP THE USB DEBUGGING TOOL ON ALL THIS TIME !
Can anybody help me with a solution to this ! Please
Click to expand...
Click to collapse
When you get to the Android with "ERROR" underneath, hold power and press volume up. It should go to recovery. Try clearing cache again from recovery.
If that doesn't work, go and get the latest version of the rom from the ASUS site, put it on a FaAT32 formatted sd card (rename to MOFD_SUPDATE) and put in phone. Go to recovery and flash rom from sd card.
Otherwise use fastboot and download an image, pre-rooted images available in Original Android Developement, thankyou Shakalaka, and flash from fastboot with command "fastboot flash system system.img" (make sure you put the system.img file in the same directory so you don't have to go hunting).

Solution found !
I've found a solution for this problem
All you need to find is a same device which is normal or BUY a new one ! OR BEG,Borrow, or steal from a friend
Find a asus zenfone 2 from a friend and enable usb debugging
Download intel driver
Just google it
Download Abd driver installer from the link bellow
Just google it
Just enable the usb debugging mode from the phone which you found
Open the adb driver intaller and fetch the abd driver directly from the installer for your asus phone
After that, download the following adb interface
Google it like " Abd interface for asus fastboot"
Then, extract the file , hold shift and right click the folder you will see a option in cmd option
Click that and a cmd window will be opened
Turn off your phone
Hold volume up and power button
After the phone vibrates realease from power button and keep holding volume up button
Boot loader will open and press volume up until you see "continue in fastboot mode"
Keep it the mode and connect your device to pc
It will directly intstall usb driver and adb driver after that
Just go back to your pc and type "fastboot format cache" and the process will continue
You will know when the process is over from the cmd in your pc
After that reboot your phone and you will still see the error
Click power and volume up button and the recovery mode will apear
Just wipe your data and every thing is going to be ALRIGHT

Cant boot into Recovery and Download Mod (LG G4 H815)

hi.
my phone is not going into recovery and download.. i tried every thing but nothng
when going to stock recovery it shows secure boot error 1003
and when try to boot into download mode it shows secure boot error 1004 on the upper cornr of the phn...
plz help me.

I think your phone become 9008.
Look this:
http://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853

pengpengback said:
I think your phone become 9008.
Look this:
http://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Click to expand...
Click to collapse
one thing i forget to say that my phone works normally. i mean in every day driver its ok. but cant boot into download or recovery?
and i tried your link but nothng?

I got very similar problem. Phone works fine but download mode shows error 1014. But I can boot to recovery mod via adb command "adb reboot recovery". Try to setup adb drivers on ur pc & put ur phone into debugging mode. & Did u try the method mentioned by pengpengback ?

vishvesh098 said:
I got very similar problem. Phone works fine but download mode shows error 1014. But I can boot to recovery mod via adb command "adb reboot recovery". Try to setup adb drivers on ur pc & put ur phone into debugging mode. & Did u try the method mentioned by pengpengback ?
Click to expand...
Click to collapse
Yes i did. But When i bought this phn i hardrest it from recovery but for second time i cant boot into recovery and it gives me error code 1013.
Download the file, write on 16hb m card put in phn then start but phn start normally. I dont undrstand if i m missing some thng...

tanvir1987 said:
Yes i did. But When i bought this phn i hardrest it from recovery but for second time i cant boot into recovery and it gives me error code 1013.
Download the file, write on 16hb m card put in phn then start but phn start normally. I dont undrstand if i m missing some thng...
Click to expand...
Click to collapse
Then try pm experts on this forum. Hope we can get solution !

Is OEM unlock set in android settings?
.

steadfasterX said:
Is OEM unlock set in android settings?
.
Click to expand...
Click to collapse
Yes. i tried every thing which i fnd on xda. every possible solution but cant boot to recovery or download mode.

tanvir1987 said:
Yes. i tried every thing which i fnd on xda. every possible solution but cant boot to recovery or download mode.
Click to expand...
Click to collapse
key combos doesn't work?
what combo have u tried?
.

steadfasterX said:
Is OEM unlock set in android settings?
.
Click to expand...
Click to collapse
steadfasterX said:
key combos doesn't work?
what combo have u tried?
Switched off the phone, removed the betray then press and hold volume - and power up the phone. when lg logo appears i release the power button for a sec and then press hold but nothing. then i removed the betray and press and hold power and volume down keys simultaneously for 4 or 5 seconds. recovery screen appears saying loading recovery but on upper left corner it shows secure boot error code 1002. i also tried to boot into download mode by holding volume up and putting cable into phone to connect with pc but same problem with different code. error code 1013.
Click to expand...
Click to collapse

How to root TP-LINK NEFFOS Y5L ANDROID 6.1

Hi everyone. Just like in the title of my post. I've just bought a TP-LINK NEFFOS Y5L smartphone, and I started to looking information, how I can get root for this device. And I found it:
https://morfitronik.pl/android-root-smartfona-neffos-y5l-tp-link/
Sad that this site is`t online anymore, but u can find it on github or gitlab.
I've flash this recovery, and it's working fine. The next step to root was to download the zip package from the chainfire site (currently abandoned, but u may use magisk from xda) :
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest MAGISK:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
Well, I've done it. It's working, and I have root on Android 6.1.
Here it is :
View attachment recovery-neffos-y5l-tp-link-twrp.apk
u will have to change extention of file from *.apk to *.img due to xda registration of size file uploaded.
Tutorial how to do this:
https://youtu.be/SfkbkcXSa2M
And if u want to buy me a beer, that is my account number:
PL 37 1020 4317 0000 5402 0389 9689
IBAN BPKOPLPW
Thanks a lot for your support.

How did you flash that twrp recovery...:laugh:

I just flash this recovery via fastboot mode.

TuanPengarah said:
How did you flash that twrp recovery...:laugh:
Click to expand...
Click to collapse
U may also try to boot your phone in this recovery throu fastboot boot image.img

Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards

Hello. It is a very annoying thing, but also very simple to solve. If u see the broken robot when u trying to enter to recovery, u must push and hold power button and short press vol+. But if you want to go to recovery or fastboot mode, u don't have to power down your phone. Just go to cmd (or whatever) console and write:
" adb reboot recovery" to boot up you device in recovery mode or
"and reboot bootloader" to boot into fastboot mode
Seeia.

Greetings!
The custom TWRP link does not seem to work as it should be. Either that or I am missing something
Could you please re-upload the recovery file?
Thanks!
"edit: I found it"

Can someone write a tutorial please, it's the first time i try to root with TWRP and i don't understand if the bootloader method for emample is from the device or from the pc because i can enter to the official android device (Y5L ANDROID 6.0.1 ) recovery menu but when i choose to boot at bootloader the phone freeze at the logo. Thanks a lot for any help.

Calaad said:
Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards
Click to expand...
Click to collapse
1. pressing the VOL up + Power button => reached a picture of android and 3 Chinese characters (means no command !)
2. pressing again the VOL up + Power button => then you will reached recovery mode.

I had seem this polish method but I get afraid because there is no method to recovery to original rom.
I hope to see a custom rom in next days.

thanks

Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.

TieSKey said:
Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.
Click to expand...
Click to collapse
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.

sixdiceray said:
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.
Click to expand...
Click to collapse
That worked fine. Weird there's no official drivers for download.
Thx.

TieSKey said:
That worked fine. Weird there's no official drivers for download.
Thx.
Click to expand...
Click to collapse
NP and maybe there is but i didn't find any official mobile app management tool from tplink to download.

Thx!

A little offtopic but, any idea on how to enable diagnostic usb port on this device? Nothing in this guide worked so far: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059

hi
Why does not this mobile display the number of unread messages (sms)?
Why can not I choose one or two SIM cards in my message program?
Why does not the percentage of battery remaining up the screen?
Why does gps work too slowly?

I Have Successfully installed TWRP But when restart TWRP I got blank image
I have successfully install but when reboot recovery I got blank image that have don't show TWRP Logo

How to root!?
Whit out pc?

Boot loop issue: cannot get into fastboot from "no command" screen

Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.

You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.

Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .

As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...

daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:

Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.

daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!

If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears

@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

@marstonpear thanks for your help so far <3
 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .

I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot

daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes

Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!

daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho

Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .

daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.

Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...