Using OTA Rootkeeper, I temp unrooted, took the OTA that was just released and now I lost root. I still have the SU binary install, but when i click on it, it seems its execution is being blocked. Anyone else loose Root?
is this for your Droid DNA, or for a RAZR?
If for a RAZR, there is a thread below that will link to RAZRblade (my 'puter is not wanting to play "copy and paste" right now, don't know why....)
This is for my xt912 razr. I saw a few other folks that had the same problem but it doesnt appear to be wide spread. Im gonna RSD back to ICS and go through the motions again. Not my primary phone so i dont really care if it doesnt work... just like having root on all my phones for tethering.
The bootloader is locked which means you can't get the ics kernel back. As suggested above use the razrblade utility to root jelly bean. But at this point you may need matt's jelly bean unbrick utility
Yup, just use the RAZRBlade root, works well, even if it is weird...
Another thing you can do is edit the system's path environment variable. By doing this you can use adb from anywhere and you needn't navigate to C:\ADB (or wherever you stored it).
Do this by right-clicking on computer -> properties -> advanced system settings -> advanced -> environment variables. In system variables click 'Path' and then click edit. Add ";C:\ADB" (without quotes) to the end of the variable value.
Well it isn't working. I get the "adb is not recognized as an internal or external command" message. Been trying to research what I need to do. Have read I need to remove what is left of the old root (don't know how) and/or install adb on the computer. I bought Titanium, I wanna use it
Dumb question; do you have the latest Moto drivers installed on your computer? If so, this should work. I'm not sure why it wouldn't, unless there is some setting that's not right. Usually this goes right the first try. It has to be something that was overlooked (of course, that never happens to me....lol).
Keep trying, it has to come around for you eventually
android - adb is not recognized as internal or external command on windows - Stack Overflow1 Answer
If you go to your android-sdk/tools folder I think you'll find a message :The adb tool has moved to platform-tools/So you should also add C:/android-sdk/platform-tools to you environment path. Also after you modify the PATH variable make sure that you start a new CommandPrompt window.
If you don't see this directory in your SDK, launch the SDK and AVD Manager (execute the android tool) and install "Android SDK Platform-tools"
Please also update your PATH environment variable to include the platform-tools/ directory, so you can execute adb from any location.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.