Tried to root, stuck at the classic *daemon started successfully*.
Uninstalled/reinstalled drivers, unknown sources and USB debug enabled.
Only solution I've seen is ppl tried other computers. I only have 1....does no one know why this happens?
The debugfs method I think its called.
Related
I need help here... I'm trying to root this thing and I don't know if I have a software problem, USB issue or phone problem.
Running Vista Hpme Edition 32 bit.
I downloaded the Samsung Drivers 1.4.6 or something and the comp said they were already installed. Now when I plug my phone in, it tries to install drivers again and hangs up on CDC Serial and MTP. It asks for a CD with driver info.
I tried deleting the USB drivers and restarting the comp to reinitialize them. I did a factory reset on the phone. Then I plugged back in and I am still at a stand still.
Since it said the drivers were already installed, I tried debugfs to root it. It just stays stuck at "Waiting for device to be detected".
How do I get these drivers to load properly so that debugfs can detect my phone?
In windows explorer, I can see the I535 and my internal and external cards... Grrrrrrrr
bionik9 said:
I need help here... I'm trying to root this thing and I don't know if I have a software problem, USB issue or phone problem.
Running Vista Hpme Edition 32 bit.
I downloaded the Samsung Drivers 1.4.6 or something and the comp said they were already installed. Now when I plug my phone in, it tries to install drivers again and hangs up on CDC Serial and MTP. It asks for a CD with driver info.
I tried deleting the USB drivers and restarting the comp to reinitialize them. I did a factory reset on the phone. Then I plugged back in and I am still at a stand still.
Since it said the drivers were already installed, I tried debugfs to root it. It just stays stuck at "Waiting for device to be detected".
How do I get these drivers to load properly so that debugfs can detect my phone?
In windows explorer, I can see the I535 and my internal and external cards... Grrrrrrrr
Click to expand...
Click to collapse
At that prompt it should also ask you to install them either way, choose yes... install the drivers then try opening up Odin and see if it can see your phone....
Your phone will have to be in download mode, and Odin should show some sort of recognition as in a COM port address in the upper left....
If that fails, follow the guide in my sig, droidstyle put together a great step by step instruction....(You can also follow the sticky about how to return your phone to Verizon in this forum that I put together, except to choose root66 and don't re-lock the bootloader)
Nevermind... I installed Kies and that seemed to remedy the issue. Thank you, though.
I recently rooted and unlocked my bootloader on my N5 and now cannot for the life of me get MTP installed on my W7 PC. Ive tried using Wugs to clear drivers and reboot and reinstall but all it does is install ADB Interface driver.
Ive also changed USB port, used my N5 USB cable, and also cleaned drivers but nothing. In occasion when looking in USB Deview it shows an MTP driver but it just wont do a thing. Ive unticked MTP and switched to camera and back. Nothing.
So, I tried my N7 and surprise, the same thing has happened. Ive installed SDK and tried updating drivers, still nothing. Ive been at it for about 7 hours all in and about to throw the phone at the wall.
Can anyone offer an advice. ive read posts and tried the suggestions there but nought. I vaguely recall a programme that will wipe any naughty bits of rogue drivers (once uninstalled) but cant remember the name of it.
In portable devices I have E/ drive.
No one out there who can help??
Im not new with using adb but using it in a virtualbox and getting all the drivers to work is becoming a pain. I can get the adb drivers to install and recognize the device, but I am having problems getting the diag drivers to work.
The phone is an HTC Incredible. I tried using the universal adb drivers which installed correctly for the most part, my problem is when the device reboots and I try to get it to be recognized from the fastboot devices command, it gets disconnected from the usb devices and then I get an error that the device is busy, and then I cant reconnect the phone through any way other than deleting the xp virtual machine and re-installing it and starting from scratch.
Any information or links explaining steps to mount the phone and install the adb and diag drivers would be greatly appreciated, thanks in advance, apologize for first newb post, will try to contribute something once I stop pulling my hair out.
Figured it out, put it in diag mode before connecting it and then set the filter and install drivers, disable port before rebooting.
I recently bought a YU YUPHORIA . When i tried to root it I was stuck at waiting for device. I checked on different forums and somehow everybody was telling about how the ADB drivers are not installed. I tried different methods . I tried to update the Android Composite ADB Interface as they had worked for a lot of other people but they didn't work with my phone. Then i tried to install ADB drivers with the help of Pdanet but the Pdanet was stuck at Trying to install Pdanet on your phone. When i write fastboot commands like fastboot -i 0x2A96 devices my device is recognised. But when i write adb devices my device doesn't show up. Please help because I really need to use this phone for app development purposes but Android Studio is also not recognising my device. I have managed to root my device but can't solve this problem of ADB not detecting my device.
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
Is their any hardware problem with my Device.?
suparv2204 said:
I recently bought a YU YUPHORIA . When i tried to root it I was stuck at waiting for device. I checked on different forums and somehow everybody was telling about how the ADB drivers are not installed. I tried different methods . I tried to update the Android Composite ADB Interface as they had worked for a lot of other people but they didn't work with my phone. Then i tried to install ADB drivers with the help of Pdanet but the Pdanet was stuck at Trying to install Pdanet on your phone. When i write fastboot commands like fastboot -i 0x2A96 devices my device is recognised. But when i write adb devices my device doesn't show up. Please help because I really need to use this phone for app development purposes but Android Studio is also not recognising my device. I have managed to root my device but can't solve this problem of ADB not detecting my device. Is their any hardware problem with my Device.
Click to expand...
Click to collapse
First, be sure you have enabled USB debugging in developer options. Also, you may have to uninstall all android drivers from your PC and then reinstall the specific drivers for your device.
Evolution_Tech said:
First, be sure you have enabled USB debugging in developer options. Also, you may have to uninstall all android drivers from your PC and then reinstall the specific drivers for your device.
Click to expand...
Click to collapse
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
suparv2204 said:
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
Click to expand...
Click to collapse
OK, try to update manually. Select update driver, then choose let me pick, then navigate to where you have the new driver.
Evolution_Tech said:
OK, try to update manually. Select update driver, then choose let me pick, then navigate to where you have the new driver.
Click to expand...
Click to collapse
I mentioned in the post I tried that . But windows shows the same message. I have tried with Google Usb drivers . I have also tried with other mobile drivers of Asus , Htc but same thing happens
Has anyone figured out a solution to this issue? I can't get my computer to recognize my device any longer.
I've tried:
Uninstalling the driver
Manually doing a generic USB hub driver
Trying to forcefully install the google driver (gives the warning it's not compatible)
Different USB cables
Different USB slots
Unrooting
OEM re-lock
Enabling/disabling developer options
No idea what else the issue could be.
ADB, fastboot, or both?
Try a different pc or roll back Windows update. I've had this issue and it turned out to be a Windows update that screwed up the communication between my phone and pc.