Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend
ElectroYume said:
Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend
Click to expand...
Click to collapse
Sounds like the fastboot drivers are missing. I'm sure you can find the drivers if you google it or just download the mi flash tool and install the drivers from there. Test the type c as well maybe the cable has the problem (try to use the official one), test it from a different usb, or an other PC or laptop if you have any.
I had similar issues before using mi flash tool, I tried on my other laptop and was working fine.
Thank you for your advice, it was due to drivers, but now im struggling with some very weird problem, i managed to flash twrp, and installed havoc (later tried lineage) succesfully, but when i boot the phone, it boots into fastboot instead of android for some reason, i tried installing the rom several times, everytime succesfully, deleted dalvik cache and so on.. Its just booting to fastboot for some reason.
Related
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...
Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app
Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.
Hi,
You're on Windows? If yes which version?
Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.
Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4
Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.
I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~
ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop
Hello!
So, I am simply an indian with all the developer-things. Checked lots of the topics here, tried everything I found and nothing. Error after error. Let's jump to the problem:
- HTC ONE M7
- hboot - 1. 61
- windows 8.1 Pro x64mBit
- USB 3.0
Installed all kind of drivers I found, but nothing works when it is in fastboot mode. The phone shows that it is connected to the PC, but in the settings the PC recognise it as "Android 1.0" and nothing more. Not a folder, or some kind of connection.
Tried different computer, different cable, different USB-port and nothing. I don't know what more can I do, just to root my phone.
Thank you for your time!
a1gara said:
Hello!
So, I am simply an indian with all the developer-things. Checked lots of the topics here, tried everything I found and nothing. Error after error. Let's jump to the problem:
- HTC ONE M7
- hboot - 1. 61
- windows 8.1 Pro x64mBit
- USB 3.0
Installed all kind of drivers I found, but nothing works when it is in fastboot mode. The phone shows that it is connected to the PC, but in the settings the PC recognise it as "Android 1.0" and nothing more. Not a folder, or some kind of connection.
Tried different computer, different cable, different USB-port and nothing. I don't know what more can I do, just to root my phone.
Thank you for your time!
Click to expand...
Click to collapse
Would help to know what error you are getting exactly
Better to use USB 2.0 ports only
Install the right drivers from HTC. Version 4.17 here: http://htcusbdriver.com/download/htc-usb-driver-v4-17-0-001
When your phone is booted in fastboot mode, you'll not see any folder from your phone and that is normal. You'll be able to use fastboot commands only.
alray said:
Would help to know what error you are getting exactly
Better to use USB 2.0 ports only
Install the right drivers from HTC. Version 4.17 here: x
When your phone is booted in fastboot mode, you'll not see any folder from your phone and that is normal. You'll be able to use fastboot commands only.
Click to expand...
Click to collapse
Okay. So...I had a success, using windows 7 with USB 2.0.
Unblocked the bootloader and started to root. But when I finally got to the "Team Win Recovery Project v 2.5.0.0", there was the next surprise. Unable to mount internal storage & unable to mount data. Now what? I couldn't find the superuser zip file and couldn't finish the root. There are underwater-rocks everywhere...
a1gara said:
Okay. So...I had a success, using windows 7 with USB 2.0.
Unblocked the bootloader and started to root. But when I finally got to the "Team Win Recovery Project v 2.5.0.0", there was the next surprise. Unable to mount internal storage & unable to mount data. Now what? I couldn't find the superuser zip file and couldn't finish the root. There are underwater-rocks everywhere...
Click to expand...
Click to collapse
Twrp 2.5 is outdated, use the latest version, same for supersu.
Sent from my HTC One using XDA Labs
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.