I have installed chain 3D app which made my phone bricked and after that, flashed my phone with stock ROM downloaded from internet.I didn't unlock the boot loader and my phone was unroofed.And again I want to root my phone,but while using cmd prompt from adb after installing lephone driver and PDA net ,it is not showing my device information when I type adb devices in windows 8. In windows 7, PDA net is not installing because of "driver for plug and play devices error:32",now how can I root my k3 note if it is not detecting it
Related
I HAVE A NET HTC one andi want to root but
i cant even unlock the bootloader
when i connect my device to my desktop windows 8 64bit pro
the device connects fine in normal mode it gives problem when in fastboot mode
the device in device manager shows as unrecognized device and device malfuntion type notification
it connects fine on windows 7 another pc is there a way to fix this
i have sync installed everything done but whenever i try to use cmd to unlock
it gives waiting for device please help
thanks
I have this problem in connecting my Lenovo A7000 with my laptop, whenever I connect the device to the laptop I get this error - "USB device you connected to this computer malfunctioned".
I read some other threads regarding the same error,
So far I have done these things to debug this -
1. Uninstalled USB drivers from my laptop
2. Checked for any available update for the device drivers in device manager.
3. Tried installing drivers manually using Lenovo tool.
4. Wiped data from the device to give a fresh start
5. Changed the USB cable.
6. Even tried this on other PC.
But still I haven't come across any solution yet, I want to flash some zip's in my device using the recovery, but can't install TWRP, because I can't connect with PC, so I am stuck with stock recovery
P.S - My device is rooted.
Try installing proper vcom drivers.btw a specific edition of win10 didnt detects the device.i have faced the same.
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk
You need to enable "USB debugging" in the developper options
ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working
I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything
First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?
Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...
Hi guys,
I want to unlock the bootloader to flash a new recovery image and to flash lineageos on my device.
But connection to fastboot will not be established whatever approach I follow.
Stock Android is updated to the last version through update function.
I followed instruction on lineageos.org and on Sony side for my device to unlock bootloader,
I installed XZ2 device driver,
I used several versions of adb and fastboot (old and new versions)#
I tried Windows 7 prof. 32 bit, 64 bit, Windows 10 64 bit Prof.
I tried USB 2 and USB 3.0 ports
Don't know anymore what I should do to get things done.
If my XZ2 is running in normal Android mode, I'm able to access the internal memory via file explorer as well as
adb devices and
adb reboot bootloader is working.
Result: LED is almost not on, maybe one can detect a little bit of blue color and screen ist black.
Then
fastboot devices or
fastboot print-pit
will not give any answer. :-(
Does anyone have a good idea to proceed before I just give up?
Many thanks in advance
Illo
strange.
had the same issues with Windows 10. had to disable Win10 driver signature enforcement to install the correct Fastboot drivers for the Xz2.
So if it doesn't work in Windows 7 either you seem to have a different problem.
A. Try using different cable
B. Install 15sec adb installer
C. Reinstall the driver again after "adb reboot bootloader"
i had the same issue and tried various method. The thing that did for me was A. Weird, since the working cable was a cheap bundle one..
Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-
Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!