I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
I'd be interested in knowing as well...
Sent from my DROID RAZR using xda app-developers app
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
seanzol said:
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
Click to expand...
Click to collapse
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
jeff_roey said:
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
Click to expand...
Click to collapse
Hi!
Take a look on others users problems they faced in eternityproject easyrootics.
You may face problems with other devices drivers like htc sync, kies, motocast... disable those and check you got adb working by typing
Code:
adb devices
I your root folder from windows terminal.
cheers
did you make sure you have the correct drivers installed? Not just plugging it in to USB and windows says drivers are installed.. that's not it. You have to make sure you install the correct 32 or 64 bit drivers (included in "Matt's Utility). Extract them, and double click to run the installation. Then try Matt's utility again.
I have only used M's U, not the other methods on both a 32 bit computer, and a 64 bit puter and haven't had any problems whatsoever. Good luck.
Edit: Just thought of this as I was re-reading the thread, try a different USB port. Some of my other USB stuff only works in the port it was installed in. Also, I'm sure you know, but to find out if you're 32 or 64 bit, go to "start" right click on "my computer", then properties. Install the drivers that are included in the extracted Matt's Utility 1.7 folder. Make sure USB debugging is enabled, USB mass storage on your phone. It'll re-boot 3-4 times during the rooting process.
jeff_roey said:
I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
Click to expand...
Click to collapse
Did you unzip Matt's utility into a new folder?
Go to my thread op and read the instructions
Cheers
Sent from my XT910 using xda premium
I had the same issue when I side loaded. Drivers were updated and all was well. Try plugging the phone in in charge only mode. I was complicating the process by trying to do it in fastboot. I was informed to just plug it in, hit 3 and let Matt's utility do it's thing. And it did.
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
newowner said:
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
Click to expand...
Click to collapse
Setting my USB mode to connect as a camera (PTP) did it!
I had the Moto Drivers from Matt's Utility 1.7 already installed (driver ver 5.7.0) and based on advice from other posts in this string, I went ahead and uninstalled them and reinstalled them just to be safe. Root attempts after doing that using the methods I discussed in my OP still were unsuccessful.
After seeing newowner's post, I went ahead and chose camera mode for the USB Computer Connection (settings -> storage -> press the menu key and choose Camera (PTP) and windows installed additional devices: USB Composite Device, DROID RAZR, and Mot Composite ADB Interface. I'm guessing the ADB Interface on was the one I was missing before.
Okay, I'm rooted and I'm heading back through this string with my bag O'Thanks to all of you.
Glad to assist.
Thanks for following up with your progress.
ICS is a little different!
nothing worked for me...tried camera mode tried media mode, tried different computers and reinstalling and uninstalling....bah.
I ended up doing a factory reset and everything was fine after. Boo...couldn't TB it beforehand though..
Related
anyone have a 64-bit adb driver for the slide
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
fermunky said:
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
Click to expand...
Click to collapse
it took a few days after nexus release to get a proper driver so im thinking we will be waiting a day or 2.
I used the 64bit driver for the Dream and my Vista64 had no trouble connecting to my Slide in ADB.
Thanks Fordude on Android Fourums!!!
1. Used USBDeview to uninstall all of the HTC drivers/ports
2. Unplugged HTC from PC
3. Installed PDANet software for Android (free).
4. When prompted, plugged in slide
5. After successful report of drivers being installed and program, accessed adb just fine!
Click to expand...
Click to collapse
Worked great for me on win7/64. SDK and Android Browser both work, still need root though
Also tried to use Apps2sd update zip, needs to be signed for this phone if anyone would be willing.
apps2sd--http://paulw.hardmilk.com/downloads/r1-a2sd-desire-dalvik-fresh-signed.zip
and the instructions for ADB were found here
http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
I'll have to give this a try. I remember using PDANet a while back and it worked, so probably will work again. Thanks
awesome i got it working now thanks
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
chrisinaz said:
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
Click to expand...
Click to collapse
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
the HTC Sync update for the phone was released for the phone. it should contain the necessary and appropriate drivers.
fermunky said:
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
Click to expand...
Click to collapse
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
poetik517 said:
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
Click to expand...
Click to collapse
Got it. For some reason Chrome had me Cached outside of the US, so it wasn't showing up for me.
For everyone's reference, make sure your selected country is US or just go here:
http://www.htc.com/us/support
chrisinaz said:
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
Click to expand...
Click to collapse
You'll want to remove the driver again via USBDeview. THEN make sure Charge only is selected, reinstall PDANet, and then plug in phone. If it still doesn't work, you are doing something wrong, trust me.
I just got a Motorola Droid RAZR and have been scouring these forums as well as other websites and they all seem, to me at least, that there is no kit to root a RAZR on 2.3.6
I have downloaded DooMLoRD_v2_ROOT-zergRush-busybox-su as well as MotoFail and it is just not working. I am using Windows 7 64-bit and the first issue that I run into is that it will not recognize my device when I plug it in. Now you may be saying, well go to Motorola's site and download the v5.4 drivers you idiot, well I am one step ahead of you, I did. Still not being recognized. Tried manually installing the drivers and telling me it is not being recognized.
If any of you out here now of a way to have the RAZR recognized by my computer and root this device, I would gladly donate to the cause.
Maybe you could try this.
When you plug your device in. On the Razr itself. Pull down the notifications menu and tap on USB Connection. Make sure it's not on "Charge Only".
I don't have that option in my notifications menu. I have selected "Allow installation of unknown sources" as well as enabled USB debugging within the application setting menu and still it will only charge the device.
Gotta ask...........you do have the 64bit drivers, right? And your logged into the PC as an admin?
Yep. I am the admin. of the computer and I am trying to install the 64-bit drivers as well. I just don't understand what I am doing wrong.
Thinking of maybe testing on a new user profile and seeing if that changes anything, if it does, then I can narrow it down to being a user issue, but I am sure I will run into the same problems on a new user account.
Can you check Device Manager and see if you have the "yellow triangle" showing for MTP USB Device?
I did check the USB drivers list and there was one where it had the yellow triangle. I tried right-clicking on it and uninstalling it then re-installing, still same issue, not being recognized.
Ok, try this. Go back to device manager again. Locate the MTP USB Device that's showing the yellow triangle. Right click and choose select update driver. Select 'browse my computer for drivers' and then choose "Let me pick drivers to install". You will get two options; select the USB controllers and click OK.
See if that helps. And make sure your phone IS NOT connected to the PC while doing this.
I think the problem may be that Doomlords hack doesnt work on 2.3.6 no matter which version of the exploit you try. It happend to me with my Australian Optus Razr when I tried to run the exploit after the OTA update and it kept failing. I have since been able to get root but theres a few things I had to do which I'll list now:
1. Install the Android SDK.
2. Install the Moto drivers.
3. Install RSDlite 5.6.
4. Find a stock 2.3.5 ROM to flash to your RAZR then do it using RSDlite.
5. Run Doomlords exploit and you should now have root.
This worked for me after alot of f***ing around but now Im running a stock rom (SPDREM_U_01.6.5.1-167_SPU-15-M2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml) and it works brilliantly.
Hope this helps.
Alright, give me about an hour to get it all downloaded. Using Barnacle WiFi tether right now on my Incredible to download everything necessary. If all goes well, someone will be getting a donation from me as this is causing me a lot of stress and I just want CyanogenMod 7 on this phone.
I recently bought the Motorola Droid RAZR and when I powered up the phone, I received a notification to update to System Version 6.16.211.XT912.Verizon.en.US
I agreed and the phone updated. I notice that I am now on Android 4.0.4.
I am trying to root the phone, but when I connect it to my PC, There is no Motorola ADB driver installed. All my drivers are up to date and I have tried this on multiple computers but to no avail. I also have the Android SDK installed.
What I have noticed is that when I connect my phone with USB debugging checked, the USB Networking driver is installed. Typically its the ADB driver that's installed but not in this case, so when I type in ADB devices my phone is not listed.
Anyone else have this problem? Any help would be much appreciated. Please let me know if you need any information and I'll be happy to provide it.
Thank you.
Same here...
I'm seeing the same thing. I've tried all combinations of settings on the phone, PC, Mac, Motocast Drivers, etc. No luck.
New Driver?
I noticed some new Windows drivers were released today on Motorola's dev site. I'm on my Mac today, so I can't give it a try myself.
This forum is blocking me from posting URLs (t00 n00b). developerdotmotoroladotcomslashtoolsslashusb_drivers
No luck...
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Fix Found
greatguitartist said:
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Click to expand...
Click to collapse
So after all my attempts at installing the ADB Interface failed, I performed the following steps (although a little grudgingly... lol)
1. a factory reset on my phone (currently on ICS 4.0.4).
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
After this, I turned on USB Debugging and connected the phone to my PC and voila! it worked. Even though the USB option was set as Mass Storage, It still installed the ADB Drivers. I set the USB Option to MTP and was able to successfully root my phone using the utility.
Hope this helps.
FYI - If you'd like to take a backup of your text messages then you can get the SMS BackupRestore app from the play store
greatguitartist said:
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
Click to expand...
Click to collapse
I think this is what got it working for you. Windows sometimes won't install USB device drivers if it thinks it's already been attempted.
This is a HUGE problem that I spent the last 12 hours researching how to fix. Instead of typing an essay on how to fix it, I made a blog post that outlines how to fix this problem. The blog post is here: Fix Adb Droid Razr Problems.
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
ultimate_reconx said:
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Did you have the Android drivers installed previously? I'm assuming that you're trying to install the drivers for the first time on that your computer and that you have USB Debugging enabled. I'll also be assuming you disabled driver verification, which can be a problem in some computers.
First you need to boot your phone normally, and plug it into the computer. Press Win+R to open the "Run" dialog and run "devmgmt.msc," which is the Device Manager. Look up the "Unknown Device" that is your phone and double click it. Click on the Event tab and check the Hardware ID in the drop-down box. It should look something like this (sorry mine is Android Composite ADB Interface because I've installed it already, but that's what it should look like in the end):
Now you have to make a new section in the driver inf. It should be in the google adt bundle and in the extras\google directory. The file name is android_winusb.inf. In the picture below my tablet is the iDeaUSA CT702. You need to add one of these sections in both the x86 and x64 section if you have a 64 bit computer. If not, just put it in the x86 section. The %USB stuff needs to match that in the Device Manager Hardware ID.
Now you should have a device called Android Composite ADB Interface or anything like that is fine.
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
ultimate_reconx said:
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you don't know where the driver is, then download a new one. I've uploaded the official Google USB driver to mediafire here: Mediafire - usb_driver.zip
You need to modify this driver, then when asked to select the inf file for driver installation choose the android_winusb.inf inside. After installation your phone should be recognized. Please tell me if there's any uncertainties you have.
Have you tried connecting the device with usb dev mode disabled? I know its strange but I've a few devices that use different drivers if the usb dev mode is enabled. I've also devices where I need to enable usb mass storage setting every time (settings menu or slide down notification). Also it never hurts to try a new cable, usb wires do tend to wear out and are very cheaply manufactured so they break inside with the slightest tug of the wire. I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
ultimate_reconx said:
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Cha1n5aW said:
I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
Click to expand...
Click to collapse
Good point. If you don't have developer mode usb debugging enabled, then there will be no "unknown device" as shown above in the device manager. Be more detailed about "no luck" please.
Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.