Related
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
A couple of days ago I flashed Eclipse v2.0, wanting to change my phone up a bit I had been on shift3r for a few weeks. Anyways, just now I was trying to copy some modules into my /system/lib/modules to overclock my device and was having issues copying within my phone. So I tried to use an adb shell to do so, but I keep getting the output of the device being offline, this is what I'm getting:
-NV57H:~$ adb devices
List of devices attached
0A3BAF200C014015 offline
And I have done a search, where some people were having trouble using certain cords, mainly with Samsung devices, and switched cords with success. This does not apply in this situation as I have used adb many times with the cord I'm using, and also I did try to switch cords anyways. Also the only other thing I saw was a situation involving driver installation and re-installation creating problems. As I am on Lubuntu, and not Windows, this does not apply to the situation because I have neither installed or re-installed drivers. My adb is setup properly because I have been using this computer for a couple weeks now and it was working previously. Any ideas on anything that could have happened? or maybe I should switch ROMs?
additionally: on my file manager, in the address bar for my device when it is plugged up, it is seeming odd to me, this is now what the address is showing for my device's sdcard:
gphoto2://[usb:002,007]/
I think I might have messed something up on my Bionic. If you read the first post I was saying how I tried adb on the same computer I've been using, AFTER flashing Liberty. Well I've gotten rid of Liberty and went back to SHIFT3R to try to fix the problem, and my problem is still looming. I have tried on Lubuntu and Windows, and my girlfriend's Incredible 2 works on both of the OS's with the same cables I'm using as well. I remember the other day when I was flashing Liberty, I had to mount my USB while in recovery to move the file onto my SDCARD because it had vanished once I tried looking for it to flash it. I remember when I tried to eject my phone from my computer (lubuntu), it said that it was busy and could not unmount the phone, after the file transfer screen went away as well. And then I waited a few minutes and tried again, it said the same thing, but I unplugged the cable anyways and unmounted USB in recovery. The file flashed fine so I know it was not still transferring the zip file. If anyone knows what I may have done or what I may be able to do to fix this let me know. I just wanted to update the thread with my most recent trials and errors in fixing it. Thanks to anyone who can guide me. I have never had issues with adb before.
O man i really hope someone can help us with this issue.
I have the same problem..
I am trying to use the path saver, and it keeps telling me device offline.
RSD lite won't even recognize it.
HELP!!!
Me too
I had the same problem... I wanted to upgrade the radio on my Bionic to the .901 load... I could not get adb to see my device.
Using Windows 7 64 bit (Ultimate).
RSD Lite would not recognize device either.
Decided "Screw it", I'll just go back to my nandroid backup... which didn't work either.... soooo... here I am.... stuck.
Off to google I went... I don't know which of these fixed it, but it is working now... here is what I did.
Found a thread that stated "run your commands from the 'C:\platform-tools' directory... so I took all of the files from the "Bionic Path Saver 1" and copied and pasted them into this directory.
Secondly, instead of just double clicking the upgrade batch file (runmebbb.bat) like I was before, I opened a DOS command shell -IN ADMINISTRATOR MODE- and ran the batch file from there.
It immediately kicked off and I was off and running.
For those of you that don't know what I am talking about, I was upgrading... using instructions from this thread:
http://forum.xda-developers.com/showthread.php?t=1433783
I hope this helps... it bugged the crap out of me... but the feeling of relief certainly makes up for it.
Well the thing is it doesn't work on windows or Linux with my bionic. I've tried various Android devices that I own and all of them work on both of my operating systems except for my bionic
Sent from my DROID BIONIC using Tapatalk
Same issu
I just installed Eclipse 2.2 on my Bionic and now i am getting the same issue. Has anyone found an answer or a fix for this? Also, does the .902 patch have anything to do with it? Any help is greatly appreciated.
Once i had this problem the only way i fixed this was by using RSDLite to flash a FXZ. Changing ROMs didnt work, nothing worked but that. It wont affect RSD reading the phone in AP Fastboot mode. Just make sure you install moto drivers and have the newest version of RSD Lite. That worked for me, now I have my adb back
Sent from my Transformer TF101 using xda premium
Are you using Safestrap recovery? If so I think that may be the issue.
Try downloading "ADB Over Wifi" from the market.
Then "adb connect iport"
The widget should show you ip/port when you activate it.
Bionic 2.2 Eclipse adb device offline
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
s.wyckoff1 said:
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
Click to expand...
Click to collapse
First of all, it automatically adds 5555 into your address so instead use
Adb connect 10.0.2.2 or whatever your ip is. And as far as not showing your device with a USB cord, try various other cables. I have over ten cables and maybe two work with my bionic. I urge you to use as many as possible before my next recommendation. This problem screwed with me for a couple months and finally i booted into fastboot mode and FXZd my phone. I booted my phone up after that and adb worked perfect. I don't know what causes this.
Sent from my DROID BIONIC using xda premium
Eventually I discovered why adb wasn't working. Apparently there was no adb daemon running. I came across this in a different thread awhile back. Once I copied it to my phone's /sbin/ directory (there was a link to the file in this post http://forum.xda-developers.com/showthread.php?t=974824) and ran adbd from a terminal I could use logcat. However it was removed everytime the phone cycles power so only a temporary fix. I was considering trying another rom instead of eclipse 2.2. It was also buggy in that when I tried to do an adb install it broke terminated the daemon.
If you're using linux I always do "sudo adb start-server"
Sent from my DROID BIONIC using Tapatalk 2
[ROOT][ICS] Root Droid ICS 4.0.4
Tested for me on ICS 4.0.4 no erros...
Credit to Rick#2 for this great post and Exploit
Credit to miloj for this new technique
Only Run the script and wait end process
Remenber this method has been fully tested and i succeeded
[REQUIREMENTS]
Check if your USB computer connection is "Mass Storage".
It shouldn't be. Change it to "media device".
Check if your configuration of android is set to "debug mode".
[AUTOMATIC]
1. Download exploits or scripts
2. Unpack files on any folder
3. Install USB drivers
4. Connect your phone with USB cable
5. Check if your configuration of android is set to "debug mode".
6. Check your Usb connection and change to "media device"
7. Run the exploit in the bottom of the page
[SCRIPT] Fully tested and only run in prompt and wait process
http://www.mediafire.com/download.php?p1dks81hu3dtiw7
http://www.4shared.com/rar/iqgref86/ROOT.html
Didn't look at the script, but from OP it sounds like an exploit to get root on ICS. Assuming that: You do realize that the Inc doesn't have (nor is likely to get) official ICS? Not trying to sound mean, but this post is kind of useless to us since virtually all custom ROMs have root. Or was this meant for a different phone other than the HTC Incredible, and you posted this in the wrong section?
And if this isn't the case, can you be a little more clear as to what this does?
taking a quick look at the script, I'm assuming its a root exploit method for the D4
in rootscript.bat
"@title D4 ICS 4.04 Root"
So I downloaded and installed the Motorola drivers from there website... Motorola Device Manager
Unfortunately when I plug in the D3 to my computer and windows goes to install the appropriate drivers, the USB mass storage install fails. The other two, can't recall the names right now, are successful. I have tried while with and without enabling mass storage on the device
Any tricks to get it to stick? The D3 isn't showing up in windows device manager except for as a adb composition device
Sent from my Galaxy Nexus using xda premium
I've tried with and without USB debugging as well, with the phone in all of the optional modes. Several drivers install just fine except MTP USB device. Phones storage will not display nor will the memory card
Sent from my Galaxy Nexus using xda premium
you could try just installing the drivers, links in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my XT862 using xda premium
I'd much prefer to have the drivers without the Motorola software.
I will give it a go when I return home and can get the gf to let me try again
Thanks for the link
Sent from my Galaxy Nexus using xda premium
I went through your links and saw that you have Motorola_end_user_something drivers version 5.4.
I tried the 64 bit variant from the zip because I have a 64bit windows 7 laptop. Installs all drivers except the mtp USB mass storage
Thanks for the link, however, I saw a video someone showed using the "latest" being version 5.5
I can't find em for the life of me, any further assistance is greatly appreciated
I can't run motofail successfully following directions to the letter and watching a video.
I'm no noon to android, just Motorola devices and its being a pain in the arse!
Sent from my Galaxy Nexus using xda premium
I rebooted computer and phone and came back and all is good in the android world again. thanks for the file and the help!
great, rebooting is often a forgotten step
Same issue- but Nothing works!
sd_shadow said:
you could try just installing the drivers, links in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs....
Click to expand...
Click to collapse
Hi, SD_Shadow!
I have the same problem. I have been looking everywhere on this site's forums for a solution, and I tried every single technique from your "Installing Drivers and Drivers Errors" section that you suggested. My computer (Windows Vista) will not connect with my Droid 3 (2.3.4).
When I plug in my Droid 3 with the USB, the only way anything will pop up on my cpu, is when I go into DLNA & choose "Share Media".
-Then a window will pop up stating "Found New Hardware" "Windows needs to install driver software for your Motorola Phone".
-I click on "Locate and install driver software (recommended)".
-Then it shows "Driver Software Installation" "Installing Device Driver Software" for a few seconds & another window pops up:
-"Found New Hardware- Motorola Phone" "Insert the disc that came with your Motorola Phone"
-I am forced to choose the option "I don't have the disc. Show me other options"
-Which leads me to the next window that says "Windows couldn't find the driver for your device" & offers two options to click:
-"Check for a Solution" and "Browse my computer for driver software (advanced)"
1. I have already went through both of these options and still no luck.
2. I have tried all your recommended techniques in your Sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... (P.S. when I had attempted the last option in the "Installing Drivers and Drivers Errors" section with the .rar file, I extracted the file using 7zip, which I already had on my cpu)
3. I have tried uninstalling & reinstalling the Motorola Device Manager (all it does is search for a new update & nothing else)
4. I have also tried rebooting my computer which has not helped this situation either
If there is anything any of you OP's can come up with for me, I'd greatly appreciate it! I tried to include as much detail as possible on here so hopefully it will make it easier to find a solution. My intentions once my phone is connected to my cpu like it should be, is to root my phone using Motofail. As you can see, I cannot accomplish the root until my cpu recognizes my device! :crying:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Still no luck!
sd_shadow said:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Click to expand...
Click to collapse
Hello!
Thanks for getting back with me. I did exactly what you suggested, & still nothing.
After clicking "Browse my computer for driver software (advanced)"
The next window stated "Windows was unable to install your Motorola Phone"
Also, the first time, when I posted on here & said I tried both of the options:
"Check for a Solution" and "Browse my computer for driver software (advanced)"
When I chose the 2nd option, I had already chosen C:\Program Files\Common Files\Motorola Shared\Mobile Drivers but this was my result that time too. I went ahead with the process in your response, but I got the same result.
Any other ideas?
Thanks again!
how is the droid 3 listed in device manager?
sd_shadow said:
how is the droid 3 listed in device manager?
Click to expand...
Click to collapse
When going through "Device Manager":
Start>Control Panel>Hardware and Sound>Device Manager
My device is listed as "Motorola Phone"
What seems weird to me, though, is when going through "Connect to":
Start>Connect to>View Network Computers and Devices
My device is listed as "Droid 3"
This may be irrelevant, or it may be helpful, but since I had noticed the difference, I thought I'd mention it.
on the phone's top bar/notification bar, it should have a usb icon
if you pull the top bar down should see 4 options
pc mode
windows media sync
usb mass storage
charge only
which one is selected?
sd_shadow said:
on the phone's top bar/notification bar, it should have a usb icon
if you pull the top bar down should see 4 options
pc mode
windows media sync
usb mass storage
charge only
which one is selected?
Click to expand...
Click to collapse
I had someone that looked for this option, & they couldn't find it. The only way we could get anything to pop up on the cpu when plugging in my phone with the USB, was when I turned on "Share Media" in the DLNA.
When I just simply plug my phone into the cpu with the USB, it only charges & does not give any options otherwise. Nothing pops up on my phone or the cpu when doing this. It would've been so simple if my phone gave the options you listed!
Jamie840 said:
I had someone that looked for this option, & they couldn't find it. The only way we could get anything to pop up on the cpu when plugging in my phone with the USB, was when I turned on "Share Media" in the DLNA.
When I just simply plug my phone into the cpu with the USB, it only charges & does not give any options otherwise. Nothing pops up on my phone or the cpu when doing this. It would've been so simple if my phone gave the options you listed!
Click to expand...
Click to collapse
even if drivers are not installed, phone should show a usb connection.
Is Share Media" in the DLNA. still on? if so turn off
and delete Droid 3 device driver in device manager
other things to try
different usb port rear ports are often better than front
different usb data cable
different pc
sd_shadow said:
even if drivers are not installed, phone should show a usb connection.
Is Share Media" in the DLNA. still on? if so turn off
and delete Droid 3 device driver in device manager
Click to expand...
Click to collapse
I know, it's strange. Like I said, it only shows that it's charging when connected to the cpu with the USB. It does not show anything like you had described during USB connection.
I turned off "Share Media" in the DLNA & deleted Droid 3 in Device Manager, before, when you had suggested:
sd_shadow said:
try
connect droid 3 to pc, open device manager (start>control panel>Hardware and sound)
find the droid 3 select uninstall and check delete the driver for this device
disconnect droid 3, then reconnect, then use the Browse my computer for driver software option
find the moto diver folder should have placed it in C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
Click to expand...
Click to collapse
& to the second half of your response...
sd_shadow said:
other things to try
different usb port rear ports are often better than front
different usb data cable
different pc
Click to expand...
Click to collapse
I was using the USB ports in the front, so I will try the ones in the back.
If this doesn't work, I will then see if I have another USB cable, and try that.
If those don't work, I will see if I can use someone else's cpu.
Also, I'll let you know how it goes- just in case anyone ever has the same issue- since these forums have been so helpful to me with different things. Thanks again for your time!
ok copied moto drivers from my Vista laptop, and uploaded to http://d-h.st/6VJ
same directions as before
download<unzip to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
open device manager>select droid 3>update driver
Browse my computer>browse Computer>local disc C>program files>\Common Files\Motorola Shared\Mobile Drivers\Drivers
but if phone is not showing usb connection, don't think it will work.
probably should delete old C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers folder, before moving new files
---------- Post added at 11:38 PM ---------- Previous post was at 10:55 PM ----------
not sure what happened, but the first copy of moto drivers for Vista was incomplete
reuploaded http://d-h.st/6VJ
I have tried, what I think, is everything to root my droid bionic. It was rooted before, but then I got an update middle of last year and lost root and have been unable to re-root. I gave up several months ago, then along came ICS. I could NOT download this update no matter what I did. Even support couldn't help. They want me to go back to factory reset. Well I don't want to do that until I can save my apps/data in Titatium, but without root--no way, so I'm back again to try to root, backup, unroot, reset, download ICS and root again, but I first have to root.
My info:
Windows 7 64bit
I have "Mot composite ADB Interface"
Android 2.3.4
System 5.9.905.XT875
Build 5.5.1_84_DBN-74
Yes, I have debugging on
Yes, I have "unknown sources" checked
Yes, I'm in charge only mode
What I have tried:
motorolaoneclickroot
droidbionicrootnew
motofail_windows
oneclickroot will start and even reboot my phone several times but after it's all finished and says my phone should be rooted, it's not. I still can't access Titanium, but I can access BusyBox and superuser. "Root Checker" states it's NOT rooted.
bionicrootnew--nothing really, it quickly goes to..."All done, run Bionic Recovery from App Draw
Press any key to continue..."
My phone never even rebooted
When I "press any key" the program stops
motofail--I get " 'adb' is not recognized as an internal or external command, operable program or batch file" over and over again. After about a dozen of these I get "[*] Cleaning up..."
then back to the "adb" response again for several lines then
"[*] Rebooting..." but it doesn't reboot, then onto the "adb" response again until it comes to "[*] Exploit complete![*] Press and key to exit."
Then it says, "Press any key to continue..." which I do, and it exits and still no root.
What suggestions do you have?
Razr's edge - more specifically,, use the House of BIONIC tool by SamuriHL.
Let me look up the URL and I'll post it here.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD