Situation:
Everything is formatted and wiped. There is no OS/ RedWolf is there now. I press any key, either Volume plus/ volume down with power key or anything, I can only go into fastboot mode. That's it.
Now, I installed Minmal ADB and Fastboot, drivers, and everything, so that I can flash RedWolf again.
The thing is:
My Xiomi Redmi Note 5 Pro is connected to HP Win 10 using USB cable. Minimal ADB and Fastboot command prompt is opened. I entered "fastboot devices" command. Nothing is showing. So I restarted the phone. So it detected again. I immediately enterd the same command again. Deviced is showing. "c6165464". I again entered the same command. Now. ???????? fastboot is showing. and third time onwords empty showing.
So it is getting disconnted automatically. What should I do?
I am facing same problem with my realme 5 pro device. Is their any solution of it . Why it is shown?????? Fastboot and next time I put command then it shows no. And then if I put sma command or any other it gets disconnected . What should I do now?
Maybe you got a faulty cable or a faulty USB. Either try with a different cable or a different computer.
Fytdyh said:
Maybe you got a faulty cable or a faulty USB. Either try with a different cable or a different computer.
Click to expand...
Click to collapse
I tried 4-5 cables but still it remains same
Have you tried removing the drivers, restart the computer and adding them again?
Fytdyh said:
Have you tried removing the drivers, restart the computer and adding them again?
Click to expand...
Click to collapse
I also tried this many times.
Also checked from all ports but nothing works
TRYX30 said:
I also tried this many times.
Also checked from all ports but nothing works
Click to expand...
Click to collapse
Have you tried flashing stock using miflash?
Fytdyh said:
Have you tried flashing stock using miflash?
Click to expand...
Click to collapse
But I think this tool is worked on mi devices not on reealme
TRYX30 said:
But I think this tool is worked on mi devices not on reealme
Click to expand...
Click to collapse
Yeah, my bad. The original poster had a redmi. Well with the official realme tool.
Fytdyh said:
Yeah, my bad. The original poster had a redmi. Well with the official realme tool.
Click to expand...
Click to collapse
I found out what was the problem and I fixed it and now it's working fine. There is some problem with amd ryzen processers. To fix that problem I downloaded amd ryzen usb controller fix then my pc detecting my phone. BTW thnx for ur time.
TRYX30 said:
I found out what was the problem and I fixed it and now it's working fine. There is some problem with amd ryzen processers. To fix that problem I downloaded amd ryzen usb controller fix then my pc detecting my phone. BTW thnx for ur time.
Click to expand...
Click to collapse
Could you post a detailed solution for anyone who will stumble across this thread?
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
TRYX30 said:
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
Click to expand...
Click to collapse
You are my god
TRYX30 said:
if anyone has amd ryzen then you could also face this problem. then you should download the attach file. then just extract it and then you will see the extracted file and then run it as adminstrator and then restart you pc. You will see that problem is solved.
Click to expand...
Click to collapse
Brother please help me.When I am entering into fastboot mode the device is getting disconnected. I even installed the usb controller fix but its not working. Plzz help . I am using ryzen 5 5600h processor
Vivek2580_maxxy said:
I had also tried many solutions when i faced this problem but only this one which i mentioned above works for me.
Click to expand...
Click to collapse
Related
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.
today i accidently wiped my nexus 5 OS.Butnow i cant restore stockrom as adb and fastboot not showing.My pc not installing drivers and otg is not mounted in twrp .anyone help
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Jo_Jo_2000 said:
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Click to expand...
Click to collapse
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
jude_ferolous said:
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
Click to expand...
Click to collapse
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Jo_Jo_2000 said:
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Click to expand...
Click to collapse
I have tried but still tht google logo
jude_ferolous said:
I have tried but still tht google logo
Click to expand...
Click to collapse
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
Kk will try and thanks
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
jude_ferolous said:
Kk will try and thanks
Click to expand...
Click to collapse
I have also tried in windows 7 &windows 10 but no luck still showing unknown device (device descriptor failed).Whether my device hardbricked and can i go back to factory version without any luck in adb connectivity and no otg help someone...
As I mentioned I my pc can't seem to detect my phone at all..it just goes into charging mode as soon as I connect..no adb no MTP or anything.
But my other phone connects just fine.
Things I've tried but failed,
Turning on adb debugging
Setting default usb configuration to MTP
Installing OnePlus drivers in pc
Adb and fastboot drivers along with qfil and miflash tool installed.
Pls guys help me figure this out.
I'm using latest oxygen os 11.1.1.1
Did you boot into other modes and tried to connect? recovery, fastboot etc.
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
Havnt tried this..I'll get back to u soon...my bootloader is locked btw
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot
Click to expand...
Click to collapse
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
I've tried bro but doesn't detect there either
i.Desygner said:
I've tried bro but doesn't detect there either
Click to expand...
Click to collapse
If it's stock then i'm thinking hw issue but keep trying things.
Try this:
Fastboot Not Recognized
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so...
forum.xda-developers.com
And maybe another computer just in case.
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
i.Desygner said:
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
Click to expand...
Click to collapse
Could be but keep in mind it has several pins so even if the data is broken or iffy you could always use it as a charging cable.
Either way use it as backup since it's less reliable
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP
I unbricked my OP8t following this guide and decided that just a working phone is not enough for me (yes i so... stubborn)
I flash rom via twrp and got errors: "can't find system_root partition" and "can't find vendor partition".
i flash new twrp via sideload and reboot phone(DON'T DO IT!)
Now my pc can't see phone, but phone can charging.
I don't think anyone can help me... but it's worth a try
Hi, follow this giude: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
gcsuri said:
Hi, follow this giude: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Hi, i can't start Qualcomm EDL mode, device does not connect to pc
so it doesn't work for me
Hi,
disconnect and turn off the phone. Start the msm tool and begin the process. Then Push VOL+and VOL- while you connect the phone to the PC. The upload process must be started. (I needed to use USB2 interface to work)
best regards,
gcsuri said:
Hi,
disconnect and turn off the phone. Start the msm tool and begin the process. Then Push VOL+and VOL- while you connect the phone to the PC. The upload process must be started. (I needed to use USB2 interface to work)
best regards,
Click to expand...
Click to collapse
computer still does not see the phone, i tried usb 2.0 and 3.0
qwerty960 said:
computer still does not see the phone, i tried usb 2.0 and 3.0
Click to expand...
Click to collapse
can you boot linux and use edl package? It works for me. Be very carefull, do not touch the persist and persist_bkp partition. It breaks your mobile forever.
i
gcsuri said:
can you boot linux and use edl package? It works for me. Be very carefull, do not touch the persist and persist_bkp partition. It breaks your mobile forever.
Click to expand...
Click to collapse
Hi, ubuntu can't see my device too
i think it's die
When your is not recognize in edl mode maybe you don't have installed the Qualcomm driver
qwerty960 said:
Hi, ubuntu can't see my device too
i think it's die
Click to expand...
Click to collapse
try the following: turn off the phone. Type a command to a shell in linux: journalctl -f
Then connect to phone to the PC while you press vol+andvol- .
What's happening?
gcsuri said:
What's happening?
Click to expand...
Click to collapse
absolutely nothing
qwerty960 said:
absolutely nothing
Click to expand...
Click to collapse
Are you using the 1+ cable?
Have your mobile charged a bit?
gcsuri said:
Are you using the 1+ cable?
Have your mobile charged a bit?
Click to expand...
Click to collapse
I use cable from OP nord 2, usb 2.0 port
I dont know, but it was charging for about ten hours on original 65wt charge
I've found that at times getting MSM to work can be difficult. But I've always been able to, somehow, get it working.
There have also been occasions when I've had to reinstall the Qualcomm driver.
I don't have any specific suggestions for your, but I just wanted to share the notes I've made/collected regarding the tool (attached). They might give you some ideas of things to try.
Note: my PC is running Windows 11 and I'm using the original OP cable.