Hi, i tried to downgrade from official 8.0 to nougat, i flashed the ota zip but ost hangs on "checking device status" at ~5%, also fastboot doesnt recognise the phone. So i believe that it must be some problem with the drivers, if anyone can has them it would be very helpful.
Thanks.
I'm having the same problem, did you fix yours?
Try to download PDANet on your computer, or search by MTK USB DRIVERS! I think the problem is that Windows don't recognize android debug bridge itself, you need to give it a hand.
Related
Hello.
I recently tried to root my phone with the S3 Mini Toolkit. I have the GT-I8190 international version.
It said that I needed to Install the device drivers first (which is the v1.5.18.0).
So I did it as instructed in the command prompt. When it finished installing the driver, and I plugged my device as instructed, suddenly came an error message "Samsung Hardware ID is missing error", and my Mini became unrecognized all of a sudden. I couldn't access my device storage.
There was an error message too popped up in my device saying that It cannot find a driver in my PC for my device.
I tried to install KIES afterward, hoping that it can solve the problem. Thing is, it didn't. My device was still not recognized, and KIES couldn't recognize it either (Connecting.....for, like forever).
I then tried to Google the problem, and came by a forum, saying that it was the 1.5 USB Drivers that caused the problem (but the case being talked in the forum is for Galaxy S3). Said that my PC need to uninstall the 1.5 drivers, uninstall KIES, deactivate the automatic device installation by Windows, and install the 1.4 version.
Well, what I can find in the internet is the 1.3 USB Drivers, so I tried the instructions, and installed the version 1.3 USB Drivers, and my PC recognized my device again, and able to access the storage.
(also, the 1.3 drivers made Odin unable to recognize my phone too in download mode).
Does anybody here have ever experienced the same problem as mine? Or did I do something wrong?
I managed to root my Mini, being not recognized by the PC (but registered at the toolkit) in the whole process, and then did the whole uninstalling and re-install the USB drivers so that I can access my storage again.
Because it's rather a painful process if in the future I want to use the toolkit again with the newest drivers.
Note:
- before rooting, I did the latest OTA update.
My current device info is
Android version 4.1.2
Baseband version I8190DXAMA2
Build vnumber JZO54K.I8190DXAMA2
Region Indonesia
Thank you very much
Bumped. Can anybody gives me some enlightenment about this issue? Thanks
So i am using the latest stable global rom and have updated windows 10 on both my computers and both won't recognize the phone as a device in fastboot. Had already used it in the past. The phone has usb debbuging activated and the phone recognises the device when not in fastboot.
Any ideas how to fix this? Or anyway to install TWRP without fastboot?
are you sure you have properly installed fastboot driver ?
Happened to me also... What I did was I used old fastboot drivers... The new 2016 drivers won't recognise in fastboot...
Connect your phone in fastboot...
In device manager manually update it to old drivers
can you upload that Old driver?
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.
this is my frist time doing this. I follow step by step guide. I even look for solution online and still dont work. I dont know whats wrong. I want to unlock bootloader to install LOS 17.1.
im using windows 10. device not detected in fastboot.
I SURRENDER. I need help. T_T
thank you !
HELP...i tried installing flashtool driver and adb 1.4.3 still dont work
do you think I need original sony cable to be recognized?
ADB / FastBoot drivers are not all you need to access your phone via USB: you must also have the OEM specific "Android USB Driver" installed on your computer.
More here: https://www.getdroidtips.com/download-latest-sony-usb-drivers/
You mean OEM driver is, my device driver (viskan,Xperia sp driver)in picture 2.everytime I manually installed it (device can't start code error 10.)
pictures 3 and 4 show that I successfully installed the oem Sao sony adb driver and still device is not detected in fastboot mode?
I even tried it on windows 7 ultimate same problem.maybe I'm missing something?
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..