314 replies to this topic

[kombat]

Need to turn on USB debugging

Ooof. Thanks. My brain wasn't registering that I needed to enable it AFTER installing ICS.

[stupidchicken03]

so im having issues.

I downloaded the .211 update
downloaded both the 1.6 and 1.7 utility
checked all with md5 check sum (all was good)

put the update on the root of my SD card
booted into AP FB
opened the 1.7 utility
booted up and when it said "press any key to continue" i pressed enter and the screen closed.
I added to the system path like it says to in the OP (pic attached)

so i then tried to boot up 1.7 and again when it tells me to press any key, it just closes.

I tried using the 1.6 utility and it too just closes after "press any key"

Thats as far as ive gotten
Any ideas?

Attached Files

•  PATH.JPG   133.29KB   12 downloads

[stupidchicken03]

Use WinRAR to extract the zip file.

Sent from my DROID SPYDER using Tapatalk 2

This is how i have it on my SD card. If i try to unzip it, it would be multiple files

And I havnt even gotten to that point because I cant get the utility to work past "press any key to continue"

Attached Files

•  zip.JPG   59.56KB   7 downloads

[stupidchicken03]

Sent from my DROID SPYDER using Tapatalk 2

Let me rephrase. Extract the Utility.

I extracted both utilities. Ran each .bat file and each utility will open fine. But when I "press any key to continue" on the launch screens, both utilities will just close

Attached Files

•  utility.JPG   77.17KB   4 downloads

[Rgaskill123]

I feel kinda noobish, I cant figure out the problem here, Whenever i load up 1.7 and run option 1 it always gets to system.img and preinstall.img and it wont load them?

[stupidchicken03]

so you can see i can get this far... but then it doesnt matter if i hit "enter", "space bar", or anything else... the utility window just closes

this is in 1.7 and 1.6 utility

even tried right click > run as admin
still will just close after "press any key to continue"

Attached Files

•  1.7utility.JPG   105.49KB   8 downloads

[stupidchicken03]

Ok so i took a video of my opening the utility and pressing any key to continue.. a screen flashed real quick and then closes..

so i went frame by frame and this is what it pops up with for a fraction of a second before closing.

\Droid was unexpected at this time.

Any ideas???

Attached Files

•  unex.jpg   33.15KB   23 downloads

[badheadache1]

I have error assert failed com.gameloft something or other.

[G8orDroid]

Ok so i took a video of my opening the utility and pressing any key to continue.. a screen flashed real quick and then closes..

so i went frame by frame and this is what it pops up with for a fraction of a second before closing.





Any ideas???

Just taking a stab here since I haven't read back to all of your previous posts, but you might try extracting (or moving) the utility and all it's subfolder to the a folder on the root of your C; drive (ie. C:\DRU17). I'm thinking you may have some characters in your path that are giving the script a hard time.
Can't hurt to try.

[MkVsTheWorld]

I had an issue rooting my Razr this morning. I have the xt912 Maxx and the Droid Razr Utility wouldn't recognize my phone at all. I uninstalled all Motorola drivers and programs off of my computer, rebooted my PC and my phone, then ensured USB debugging was selected, that I mounted the phone as a MTP phone, and that I used a USB port in the back of the computer. After I plugged the phone in, I let it sit until Windows installed all drivers for the phone. There was some networking communications controller driver that had to be installed that took a long time to install. After that finished, the Droid Razr Utility root feature worked. That might help other people having similar issues.

[stupidchicken03]

Just taking a stab here since I haven't read back to all of your previous posts, but you might try extracting (or moving) the utility and all it's subfolder to the a folder on the root of your C; drive (ie. C:\DRU17). I'm thinking you may have some characters in your path that are giving the script a hard time.
Can't hurt to try.

tried that and either that (or the multiple reboots to the PC) worked lol.

applying the update now

[stupidchicken03]

ICS has been up and running

havnt played with it much. reinstalling all my apks and 6000+ txt messages haha

[biz_diddy]

Alright fellas....I need a little bit of assistance. This is what I've done so far and where I'm having an issue:

• I rooted my device using v1.6 of your utility for GB (I was on v1.81) successfully
• Installed VooDoo OTA Rootkeeper, created a SU backup successfully
• Installed ICS v.211 via OTA. Install was fine
• Attempted to restore root via Rootkeeper. It says it succeeded, but I do not have root. Refreshing within rootkeeper does not show root. None of my root apps have root access.
• Superuser.apk is still installed and "su" is still located within /system/bin. busybox is located within /system/xbin
• I uninstalled Motorola v5.2 of the x64 drivers (previously had a Bionic)
• I Installed the included driver for my system (x64 - I'm running Windows 7) in the Drivers of the zip you've provided
• Go to Settings > Developer Options > Enable USB Debugging
• Plugged in USB and in the notification/pulldown menu. Choose the USB Mode as MTP.
• Run option 3 on the 1.7 Utility "Ice Cream Sandwich 4.0.4 Root"
• It says "Waiting for device" and the utility never finds my phone.
• Rebooted my device/laptop numerous times to no avail. It still hangs at "Waiting for device"

Any ideas? Thanks in advance for the help guys....not sure else what to do.

[Memnoch73]

Alright fellas....I need a little bit of assistance. This is what I've done so far and where I'm having an issue:

• I rooted my device using v1.6 of your utility for GB (I was on v1.81) successfully
• Installed VooDoo OTA Rootkeeper, created a SU backup successfully
• Installed ICS v.211 via OTA. Install was fine
• Attempted to restore root via Rootkeeper. It says it succeeded, but I do not have root. Refreshing within rootkeeper does not show root. None of my root apps have root access.
• Superuser.apk is still installed and "su" is still located within /system/bin. busybox is located within /system/xbin
• I uninstalled Motorola v5.2 of the x64 drivers (previously had a Bionic)
• I Installed the included driver for my system (x64 - I'm running Windows 7) in the Drivers of the zip you've provided
• Go to Settings > Developer Options > Enable USB Debugging
• Plugged in USB and in the notification/pulldown menu. Choose the USB Mode as MTP.
• Run option 3 on the 1.7 Utility "Ice Cream Sandwich 4.0.4 Root"
• It says "Waiting for device" and the utility never finds my phone.
• Rebooted my device/laptop numerous times to no avail. It still hangs at "Waiting for device"

Any ideas? Thanks in advance for the help guys....not sure else what to do.

Double check usb debugging. That's usually what wait for device means

[biz_diddy]

Double check usb debugging. That's usually what wait for device means

I've even toggled it a few times...but still no dice.

[mattlgroff]

How to fix the device not found (if the phone is being your problem, and I mean that you have USB Debugging and MTP and/or Camera mode set and drivers installed still not found):

• Boot into AP Fastboot Mode
• Choose Option 8 to flash 4.0.3 Boot.img
• Boot into android normally.
• Choose Option 4 to root 4.0.3 and root it.
• Boot into AP Fastboot mode
• Choose Option 9 to flash 4.0.3 Boot.img

If this still does not work, try another usb port, usb cable, or computer. If even those do not work, then you are out of luck. The linux utility requires no driver installs and might be a better choice for your situation if this does not work.

[biz_diddy]

Well come to find out that the ADB Interface DOES not show up within the Device Manager whenever the Razr is connected to my Windows based machine. This interface does show up for my previous moto devices (Bionic, Droid X) just fine as soon as they are attached using the same cable/same USB port. I now know its NOT the drivers or the USB port/cable. It seems as if even though USB debugging is set to be enabled, it seems as if it not actually on. When I toggle USB debugging, Windows recognizes a change as it does make an audible tone and the MotoCast nonsense pops up....so I'm kind of at a loss.

ADB shell for my previous devices generate a response, while the Razr just gives a "device not found" error. Anyone have any suggestions based on that info?

[Mr.Rzr]

got a question for you all. took the official ota today but made sure i had voodoo and did a backup root. installed the ota fine and rooted and all is good. now trying to install bootstrap from the utility and seems like it just gets hung up and doesnt do anything. any ideas. usb debugging is on too