Hello I have a moto edge I had havoc on there and TWRP but I don't even really know what happened but I ended up bricking well not really bricked I can get in yo fastboot but the computer doesn't recognize the device I've switched cords computers tried every driver I can find I even went as far as to make my own edl cable to try to get it to edl more which one of the times playing with the edl cable i got it to say unknown device but haven't been able to since then if i boot to recovery it boot loops and same with just trying to boot I'm at a loss of what to try to do test points? To force edl? Please help
no need for EDL mode if you can still access fastboot. you can just install the drivers.
in fastboot mode format cache partition, that will fix TWRP boot-loop.
How to do that tho ?it doesn't recognize my device at all but it recognizes any other device I plug in
in device manager find the device with yellow triangle exclamation mark
Yeah no it's not there and when I can get it to make the noise it's from my home made edl Cable it says device descriptor error or something like that I'll look to see what it comes up as but I've installed drivers of uninstalled all the drivers I've got Qualcomm drivers I've got Motorola drivers I've got I've done all that or else I would have had it solved already I don't know what's going on with it and that's why I was asking about the edl test points because the computer won't read it whatsoever now it won't even get into fastboot but it won't get into edl neither I'm lost
try in linux lsusb (no virtual machine)
I had tried on Ubuntu with no luck it doesn't do anything at all now unless I edl Cable it and it says unknown USB device device descriptor request failed
does not sound like Ubuntu error message.
No that error is from windows I do not have access to my Ubuntu atm
Related
I can't seem to get the fastboot usb drivers to install....i tried:
a) downloaded the asus android usb drivers but can't install manually because they won't do it on x64?!
b) installed asus pc sync (should install drivers also right?)
now i'm in fastboot usb download and when i connect the cable, it says USB device not recognized.
what can be done?
installed the SDK and now i see the device recognized in ADB, but i can't get it to be recognized in fastboot mode ???!!!!!! same error about unrecognized device...
// EDIT: WELL ****ING HELL, it was the USB port!!! I tried 3 of them (front panel) and same result
Switched to a backpanel port and it flashed TWRP straight away....
**** this, pls close thread.
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
I wanted to change my ROM from a xiaomi.eu ROM to Lineage OS 15.1 https://forum.xda-developers.com/mi-...-aqua-t3667638.
I had already rooted my phone and installed TWRP. I rebooted to TWRP and wiped cache, dalvik cache, data and system.
After that I installed the 8.5.1.0 firmware, that was done successfully. After that I tried to flash lineage-15.1-20180202-UNOFFICIAL-libra.zip in TWRP but I got an error message at an early stage. Eventually I switched off my phone through the menu of TWRP.
This was the last time I've seen my phone alive because no matter what I do, it doesn't respond at all.
I've tried to flash it through XiaoMiFlash, but my computer (nor my Macbook) doens't recognize my phone when I connect it through a USB cable
What to do guys?
Any possibilities that you've fully-drained your battery? Try to left your device charging on standard wall charger for at least 2 hours.
If it still bricked, you might wanna dissassemble the phone and disconnect the battery from the board and start flashing MiUi fastboot rom vie EDL mode.
kopter36 said:
Any possibilities that you've fully-drained your battery? Try to left your device charging on standard wall charger for at least 2 hours.
If it still bricked, you might wanna dissassemble the phone and disconnect the battery from the board and start flashing MiUi fastboot rom vie EDL mode.
Click to expand...
Click to collapse
I've never had any problems with the battery. And when I entered TWRP I saw the battery was 80%. But I'll try to charge my phone for at least 2 hours, just in case.
In order to perform flashing MIUI Fastboot via EDL mode, the computer should recognize the phone when it is connected through USB cable, right? If so, that's not the case with my phone. My computer is saying that an unknown device is connected to it. Do you think this will be different when I remove the battery?
MastaBlasta070 said:
My computer is saying that an unknown device is connected to it.
Click to expand...
Click to collapse
Perhaps the driver is missing? The next step will depend on the registered USB device ID, so please quote it. My Mi4C in emergency download mode displays the following:
Linux, command lsusb:
Code:
Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
or Windows, in Device Manager as Ports (COM & LPT) / Qualcomm HS-USB QDLoader 9008 (COM5):
Code:
USB\VID_05C6&PID_9008
You should see one of these: 9008, 9006, 0002, 0001 or similar.
MastaBlasta070 said:
I've never had any problems with the battery. And when I entered TWRP I saw the battery was 80%. But I'll try to charge my phone for at least 2 hours, just in case.
In order to perform flashing MIUI Fastboot via EDL mode, the computer should recognize the phone when it is connected through USB cable, right? If so, that's not the case with my phone. My computer is saying that an unknown device is connected to it. Do you think this will be different when I remove the battery?
Click to expand...
Click to collapse
Unknown device probably indicated missing driver for the QCom EDL mode as @k23m mentioned above. Try to install the driver first. If you are on Windows 8 and above, you might need to disable driver signature enforcement first.
If all going nicely, MiFlash should recognize your device based on COM port and not device id.
I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?
I have tried just about everything i can think of to make the phone be detected in fastboot, but nothing is working. The phone is detected through adb, but when i boot into fastboot and run fastboot devices, no devices are found. Device manager aslo says a code 28 error on the drivers for the device in fastboot, and i have looked all over for fastboot drivers and cannot find any. Im really stumped atm.
sucks you never got an answer to this having the same issue
Had this issue and disabling driver verification on my windows 11 laptop solved this. Hope this helps