Related
For Droid 2's on Gingerbread, click link below to find info to Root your phone
http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
One Click Root Version for Linux and Works for Mac, too!
This is still a work in progress! Gonna call it 3.3 (I went through 3 previous versions). It takes the 2.2.1 version and adds a user interface. Nice, easy, clean. In order to run this script, you need to chmod (change permission) of the .sh file, and then execute it.
Download the file here: http://kimete.com/droid/beta/dorootv3.sh
It is good for both Linux and Mac. All you have to do is execute it and the script will download all the appropriate files for you!
How to run this in Ubuntu/Linux
How-to video here: http://www.youtube.com/watch?v=gvlB3e_UE8I
Note: General idea. You no longer need to update android-sdk, though.
1. Download the file.
2. Right-click the file, choose properties, choose the permission tab, and check executing file as program, close window
3. Double-click the file, choose Run in Terminal, and it'll start.
4. Choose 1 for install and root. Choose 2 for root process only. Only good if you've rooted using this method before, or you need to reroot your phone. Choose 3 to unroot. Choose 4 for credits/donation information. Choose 5 to exit. Choosing other numbers...
How-to for Mac
How-to video here: http://www.youtube.com/watch?v=d7s8dtfYyHI
Note: General idea. You no longer need to download and install android-sdk anymore.
1. Download dorootv3.sh. Best to put it on your desktop.
2. Open a terminal. Go to the magnifying glass and type in terminal, and then select it.
3. Next, you need to change permissions. Type in the terminal chmod 0755 followed with a single space. Then drag the dorootv3.sh into terminal.
You should see something like this chmod 0755 /user/(file path)/dorootv3.sh. Press enter.
4. Now run your file by dragging the file into the terminal again and pressing enter!
5. Now choose and option...
New version of rooting for Linux and Mac! Version 2.2.1!
Linux 2.2.1: http://www.kimete.com/droid/beta/DoRootLinux_221.zip
Mac 2.2.1: http://www.kimete.com/droid/beta/DoRootMac_221.zip
General Instructions:
1. Extract the files.
2. Change the permissions on the doroot.sh file
3. Run doroot.sh file.
Instructions for Linux and Mac
1. Extract the respective files to somewhere accessible. Your home directory or desktop is idea. The file comes in a .zip file. Just open it up and drag and drop the DoRootMac or DoRootLinux folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the folder in terminal.
example: [cd /DoRootMac or cd /DoRootLinux]
4. enter [chmod 0755 doroot.sh] then run it [./doroot.sh]
5. Let it run.
6. That's it, you are done.
One Click Root for Windows
Here's the Windows version. Facelessuser pushed this through and worked his magic. Give it a try. Very exciting stuff. I haven't used it yet, but according to him, it should work!
Download here, Ver. 2.1.4:
http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
Instruction for Windows:
How-to video here: http://www.youtube.com/watch?v=B7RGVikpQ8o
1. Extract the folder from the DORoot zip file to your desktop. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom righ, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot.bat
5. Let it run.
6. That's it, you are done.
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Many thanks to facelessuser for working his magic!
====
====
How-to Videos
Video of the Rooting Process for D2 and DX by [email protected]
For Windows/Mac/Linux
http://www.youtube.com/watch?v=u5l3MDomDSc
Video of the Rooting Process for D2 and DX by DarkOnion
For Windows
New: http://www.youtube.com/watch?v=B7RGVikpQ8o
Old: http://www.youtube.com/watch?v=gzlg9a-H42w
How to use the ADBDL.sh file by DarkOnion
For Mac and Linux
http://www.youtube.com/watch?v=9cHpGXfEudM
=====
=====
Frequently Asked Questions
Why does my anti-virus tell me that the files contain Trojan's?
The files are exploits and hack your phone. Don't worry, they are clean. However, to be safe, do not download from any other source than the ones linked in this post.
I've gotten countless hate mail and comments on Youtube users about rageagainstthecage-arm5.bin being detected as a trojan. It is an EXPLOIT. If you are scared that the files I hosted are going to give your computer a virus. Look else where, like Z4Root, though, my understanding is that Z4Root also uses rage.
http://forum.xda-developers.com/showthread.php?t=853704
What is do these files/programs/scripts do?
These scripts will root your Droid 2 or Droid X phone with the least amount of user input as possible.
Why should we use this method and not another method?
All the methods are based off the same process/procedure. If you feel like doing MORE work, we can't stop you. The reason why we wrote all these scripts is to expedite the process, make the procedure easier, and to reduce human input which reduces the chance of human error.
Is there anything I need to know in order to successfully root my phone?
Yes. READ THE DIRECTIONS. Read the directions first. A lot of people make errors because they don't read the directions. I've also provided links to my video and another video which outlines the root process. Both are only a few minutes long.
Root failed! What do I do?
Run the script again! Most people succeed on the first or second try. Usually the rest by the third try.
Do I have to install Android SDK and update it?
It depends. The new Linux/Mac version does not require you to. The windows one, we are still working on.
Does this work on other phones?
I can't answer that. I know it works for Droid 2 and Droid X.
Wait a minute, this isn't really one-click! What's the deal?
Deal with it. Don't like it, try the 25+ step process.
When I open up the Superuser app, I get a blank screen.
That is NORMAL. Superuser lists the processes/applications that you've allowed superuser access to. If you haven't allowed anything, then it will be blank.
How do I test if I have root or not?
Try downloading an app like Wireless Tether (published by Google), and running it.
What USB connection mode do I set my phone to?
PC Mode or Charge Only. Choose the one that comes up with USB Debugging.
I am not very good with computers. Is this something I can do?
Oh yes! The key to success is following the directions.
How do I update Android SDK?
On Windows, you just need to double click the SDK Manager.exe. On Linux/Mac, you need to go into terminal, navigate to the tools folder in the android sdk folder, and run this command ./android update sdk. More information can be found in the SDK Readme text file. On Windows, double-click and run the SDK Manager.
I am getting stuck at the "daemon not found/daemon is starting" part. What do I do?
You need to fumble with the settings on your phone. You don't need to close the terminal. Change between PC Mode and Charge Only mode until it starts to continue. If that still doesn't work, also try disabling then enabling USB debugging for each mode.
=====
=====
Reporting an Error or a Problem
You can report errors right here in this thread. Make sure you give us as much information as possible. List what operating system you are on, what phone you have, at what part of the script you had errors, and anything else you may have tried or done. The more information you provide us, the better we understand situations. Posting up pics or logs of the terminal is extremely helpful.
=====
=====
Change log for 1-2-3 Root
Version 0.0 - 25+ step tutorial on how to root D2 on Windows and Mac
Version 1.0 - Initial scripts to streamline processes and reduce user error in Ver. 0.0.
Version 2.0 - Streamline of multiple scripts into 1 script. Minimal commands. Minimal work. With error checking and reporting.
Version 2.1 - addressed issue where remnants of a previous root would not allow root to complete
Version 2.1.1 -
-Cleanup code.
-Address issue where I thought I was killing a hanging rage, but I wasn't (It was a syntax thing)
-Fix for ERROR6 or ERROR5 (this was drastically different than what I did in windows. I wasn't returning exactly a string in format I thought when doing the check, so I had to do some ridiculous stuff to process it.)
-Better error resolution. (more error checking)
-Refined unroot.
-Reboot if you had files from a previous root
-Now the script will automagically download needed root files if they are not in your folder. (If you are behind a proxy, make sure your mac or linux has curl or wget configured for proxies respectively)
-Longer wait before remount (I had it not remount because it was busy once)
Version 2.1.2 -
Linux and Mac
Contains everything windows 2.1.1
Unroots non bootstrapped phones too
All
Contains option to unroot
Version 2.1.3 - Added dounroot.bat
Vesion 2.1.4 -
-Fix bug where people were getting a false ERROR5 because they already had Superuser.apk
-Hide killing of busybox before unroot
Version 2.1.4 - Files are standalone. No need to download Android SDK anymore.
Version 2.2.0 -
-adb included, no SDK needed
-abort if cannot find adb
-remove alternate busybox at /system/xbin and /system/bin when unrooting
-remove alternate busybox at /system/xbin when rooting and installing busybox at /system/bin
-No more hang in exploit...I hope
-Clean up code
Version 2.2.1 - minor revision to code (curl related)
DarkOnion's DoRootv3
Version 3.0 - set-up menu's, added error checking, will detect which OS you are on
Version 3.1 - fixed issues with ADB SDK User interfaces
Version 3.2 - adapted to DoRoot 2.2.1
Version 3.3 - edited code for easier understanding and modifications
=====
=====
References:
Original procedure produced by Sebastian Krahmer
http://forum.xda-developers.com/showpost.php?p=7838000&postcount=1
Tutorial/How-to Root Droid 2 on Windows by DarkOnion
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
Tutorial/How-to Root Droid 2 on Linux/Mac by DarkOnion
http://forum.xda-developers.com/showpost.php?p=8103311&postcount=340
====
====
Appreciate my work and/or help, feel free to send donations my way! Poor college student here who just got a speeding ticket! Doh!
This is outdated information and should be used as a reference only! All updated versions have moved to POST #1.
Hi all. Made it to the front page of XDA Developers.
http://www.xda-developers.com/android/easy-rooting-method-for-droid-2/
I just want to make sure credit is given where due. First of all, the original procedure was produced Sebastian Krahmer. From there I wrote an indepth tutorial to root the Droid 2. I took a vague instruction set and help it grown into something that the average person could understand. Understanding the need to simplify the process, I decided to write scripts to further streamline the process. What started out as a 3 part script that involved 8 or 9 commands eventually became a two part script that involved 3 or 4 commands. I have no programming background, by the way. Having trouble getting the process down into one part, facelessuser volunteered to take my work, and put a bunch of neat things into it to get it to work as one thing with error checking! So, with that said, I'd like to thank everyone that had a part in the project, especially facelessuser for his dark magic arts that made the script run, matt4542 for constantly testing my various scripts, and everyone who directly or indirectly ran the scripts!
We are moving forward!
===
Hi all.
We (me), facelessuser, and a few others are working furiously to get an easy one step program out for you guys. In the mean-time, I have a pretty safe, and clean, and easy 2 step method for Windows, Mac, and Linux. I am still cleaning stuff up, but for the most part, it all runs well.
What you need:
Android-SDK for your operating system which can be found here:
http://developer.android.com/sdk/index.html
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
And the files/scripts/programs to root for your OS:
Want to try the one step process, go down to post #2!
Windows [1.0]: http://www.kimete.com/droid/DORootforD2Windows.zip
Mac/Linux [1.0]: http://www.kimete.com/droid/DORootforD2Linux.zip
Instruction for Windows:
GO DOWN TO POST #2 AND DOWNLOAD THE ONE STEP
1. Extract and Update Android SDK package to your computer. The file comes in a zip file. Just open it up and drag and drop the android-sdk-windows folder to your C drive. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom right, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot1.bat
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to DOS, enter or double click doroot2.bat
8. That's it, you are done.
Instruction for Linux and Mac:
GO DOWN TO POST #2 AND DOWNLOAD THE 1-STEP!
1. Extract and Update Android SDK package to your computer. The file comes in a .tar.gz file. Just open it up and drag and drop the android-sdk-linux folder to your home directory or desktop. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the tools folder of your android-sdk
[cd /android-sdk-linux_x86/tools]
4. enter [chmod 0755 doroot1.sh] then run it [./doroot1.sh]
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthe cage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to command prompt, [./doroot2.sh]
8. That's it, you are done.
Enjoy my works? Want to show your gratitude? Just want to help a poor college student out, donate via PayPal to: [email protected]. All donations are greatly appreciated. Money will be spent on escorts, food, adult beverages, higher education and its bs fees, paying off my phone, and the wonderful speeding ticket I got this week!
Hey Thanks alot for writing this! I just tried it out and ran until completion.
A few things I found.
In the dos prompt, part2 the program asks user to input a few commands. Commands 2 and 3 should end in .sh. The program dosent mention this.
Thanks again
Typo in the 3rd step. You forgot to add '.sh'.
lockdownx1x said:
Typo in the 3rd step. You forgot to add '.sh'.
Click to expand...
Click to collapse
Doh. Good catch y'all. I will take care of that now!
Problem
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
The " ./ " before doroot.sh tells linux to look in the current directory for the file to run. Make sure you in the tools directory of the sdk and that the script is there as well.
Sent from my DROID2 using XDA App
Yep i definitaly made sure of that but same error. It doesnt matter though i have rooted my droid 2 through the manual proccess
NiteSite said:
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
Click to expand...
Click to collapse
Did you do cd data/local/tmp in adb shell before doing the chmod and ./doroot2.sh?
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
NiteSite said:
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Weird. I am going to send you a PM. Hit me up on Google Talk.
-Kevin
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
mjones1052 said:
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
Click to expand...
Click to collapse
I am working on it. Hahaha. I don't have any programming background. So I am learning on the fly, but progress is being made.
Though, I have to say that the process is much much much easier than what it originally began as. So... moving in the right direction.
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Kenny Strife said:
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Click to expand...
Click to collapse
Just follow the instructions. Launch the doroot1.bat file. The .bat file will launch you into ADB shell. chmod the doroot2.sh file, then run it. adb shell again. chmod the doroot3.sh file and run that. Hope that helps. I am on google talk if you need help.
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
please help!
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
chrismouro said:
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
Click to expand...
Click to collapse
You are okay. Superuser lists the program you've allowed superuser access to. You haven't given any apps access, therefore blank!
Kenny Strife said:
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
Click to expand...
Click to collapse
Kenny, did you get this resolved? I am experiencing the same issue.
I'm getting kicked the ./doroot2.sh: not found as well. Anyone get past this point?
Hi after reading through the post on GitHub on how to simply root your shield I have a few questions that the tutorial doesn't make clear:
1)There are a ton of files at the top and not sure what to do with them...
2) There is a bit where it explains "On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz"
But it doesn't say that after you open the directory what you do with it?
Do you keep the window open and that's fine?
Do you type in it's location into command prompt before you type in: fastboot boot zImage_dtb ramfs.img.gz?
Just a bit confused as to what all the files are and where I put them and how they have to be utilised etc
Just need clarification for peace of mind
wanted to post the link but forum won't let me yet
Root explanation
Hi here is the main walkthrough from github but as I said there are a few plot holes for people who are new.
If your SHIELD is already unlocked, you can skip this section.
SHIELD ships with an unlockable bootloader. The bootloader is locked by default, which prevents anyone (including yourself) from booting custom OSes and changing system partitions to potentially obtain extra privileges. This is a significant security feature: in the event that your device gets stolen, an attacker will not be able to retrieve your personal data or use your device if your lock screen has a password set.
By unlocking the bootloader, you allow anyone with physical access to your SHIELD to boot custom images and flash system partitions. This opens the way for an attacker to access your personal information or physically damage your device. For this reason, unlocking the bootloader will erase all your personal data like a factory reset does (so a potential thief cannot get it) and will also void your warranty.
If you know you really, really want to take these risks, here is how you unlock SHIELD's bootloader.
Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable.
On your computer, enter the following command:
fastboot oem unlock
This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting SHIELD
Now your bootloader is unlocked, but you still don't have root access. For this, we need to install SuperSU, and we will do so by booting a custom Linux image that will do this for us.
Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
Connect your SHIELD to your computer using a USB cable
On your computer, navigate into the directory containing this file and enter the following command:
fastboot boot zImage_dtb ramfs.img.gz
The kernel and ramdisk will be downloaded and started. You will see 4 penguins on your screen, and the message ROOTING SHIELD will appear. Shortly after, your device will reboot. Congratulations, you are rooted!
For some unknown reason USB debugging in Developer options might become unchecked after rooting. You will need to re-check it if you want to use ADB.
It is safe to perform the rooting operation as many times as you want (e.g. after an OTA). Your user data will not be erased by rooting itself, it is the act of unlocking the bootloader that does.
Is there anyone who can add a little to this to make it more simple for a noob like me?
I understand there is a file set that is at the top of the page and I downloaded the files which include zImage_dtb ramfs.img.gz
but don't know how to utilise them etc
There are no videos on youtube of how to do it and if anyone can add just a few more steps so that I know where I'm going with this (don't want to brick my system).
I just want controller support installed like Tincore or gamekeyboard so I can unlock the potential of the games library on GooglePlay.
Thanks for reading.
you copy those two files "zImage_dtb" & "ramfs.img.gz" to the same directory your adb and fastboot executeables are (same directory you issued the oem unlock command from)
then navigate to the same directory you did the oem unlock from via command line then issue the command "fastboot boot zImage_dtb ramfs.img.gz"
it's pretty simple but I can run you through a simple example of what I did
1)download android sdk
2)copy platform tools folder to a directory on c drive (exp c:\tools\ )
3)copy the 2 files above to the same folder along with cwm recovery(optional)
4)boot shield into fastboot mode (home+back+power)
5)navigate to the folder with adb, fastboot, and the above files in it.
Code:
cd c:\tools
6)detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection
7)issue oem unlock command and follow the onscreen prompts
Code:
fastboot oem unlock
8)restart device, after a full boot cycle(wipes data), power back into fastboot
9)issue the "rooting image" command, device with automatically reboot
Code:
fastboot boot zImage_dtb ramfs.img.gz
*10) optionally reboot back into fastboot and install cwm recovery
Code:
fastboot flash recovery recovery.img
pretty simple
thanks for fast reply.
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
If your confused by my instructions you need to wait for a "one click" installer, sorry.
gogul1 said:
Ok so I have Two different versions of Android SDK (32 bit and 64 bit) which one do I use?
"copy platform tools to a directory on C drive (exp C:\TOOLS\)"
What are platform tools?
"copy the two files above to the same folder along with cwm recovery"
What two files? do you mean the zImage_dtb and ramfs.img.gz? Do they go into the C:\TOOLS\ folder?
"navigate to the folder with adb, fastboot, and the above files in it"
What do you mean by navigate? Do you simply mean open the folder or do I use a program to do this?
"Detect if fastboot driver is installed with "fastboot devices" if result, then continue, if no result, then check if correct driver and check connection"
What's fastboot devices? What does result and no result mean? What does Check driver and check connection mean? how dod I do that?
I'm confused by all the lingo, what applications I should be using and when exactly do I start using command lines etc
Thanks for help so far been great but I need step by step instructions eg
open folder, copy and paste file1 and file 2 to this folder
open application X
click import file 1 and file 2
type XXXXXX\root\cdrive into command
press enter
see?
I do not know what some of the words mean and how to do some of the stuff the tutorial says. It's jargon and I have all these files, in all these folders with no idea how to do this from start to finish.
Appreciate the help so far but you are dealing with a novice. I know the work won't take long but I need all the relevant info, in one list, with consistent language to ensure I do everything as it should be done.
Bless you sir and...
Good luck
Click to expand...
Click to collapse
Step by step instructions like that would take quite a long time to write. Its basically assumed that navigate is a straight forward instruction, namely, open My Computer, click C:\, click something else, etc etc. 32 bit vs 64 bit, again, you should know what your computer is running and use the correct one respectively.
The reason they dont issue novice instructions is for 1 reason only. People who such as yourself claim to not understand the "jargon" are also those who are more likely to make a mistake when rooting. This can lead to a completely bricked device, ie one that will no longer turn on and load up android, totally dead device. As far as the manufacturer is concerned, a bricked device unless bricked by one of their own updates on a non rooted shield installed correctly, is not covered by warranty. This leads said novice to accuse the tutorial writer of having something wrong in the tutorial when in reality they have clicked the wrong thing etc.
Either way, end result: dead device.
Rooting is not aimed at the novice. It is aimed at the advanced user.
Thank you
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Sorry for being so abrupt, it wasn't my intension, you are trying to learn. I will not give a step by step which I feel would be the best, yet potentially more dangerous option for you though.
The parts written in the "code" blocks are what you copy and paste into the command line. When I say navigate I mean by changing directory via command line. You can copy files with a graphical file manager as it's quicker but navigate could also mean graphically.
Google search how to tell if you are running 32 or 64 bit windows, there are better guides and videos than I would be able to describe in a few lines. I was assuming you had already unlocked your bootloader as it is required before root, I covered it as point of reference only.
Platform tools is a folder in the SDK, if you install the SDK you will see that folder where you install it.
Fastboot is the utility also in the SDK that you run from command line that's in the code blocks I posted. If you run the command it will either give a result saying a device is detected or it won't show anything (no result) and you have an issue. If you have a driver issue then that's a whole other problem with a specific forum topic for, but I also assumed you unlocked your bootloader which would require you have fastboot and driver issue resolved.
Main cause of my snappiness is it says the requirement (first line of what you quoted) is unlocked bootloader and you are asking questions about rooting (step two after unlocking bootloader) didn't realize you were stuck in step 0, trying to figure out where to start.
gogul1 said:
I understand that and appreciate the explanation. I can work my laptop and I know that my laptop is 32bit or 64bit but it did not say at any point that it was referring to my computer. It just said download the 32 or 64 bit version. Well I have to make sure what they are talking about before I go and try to root my device as I like clarification on everything I do so that I get it right (and don't brick it). At the moment the explanations are all over the place, some info here, another bit there and was hoping somebody could link it all for me and make sense of the order in which I would do things. I have installed graphic cards in my laptop, put custom firmware on to ipods, psp's, computer etc but this is my first foray into android territory and would like to get it right. I am trying to follow a video tutorial but my computer's reaction to driver updates for the ADB/Fastboot drivers is telling me my drivers are up to date and I'm not getting the error message his is. This means I'm not sure where to go as the situation is diffferent s He is trying to get motochopper working for shield so it will root the device and hoped it would do the same for me.
Hopefully some clarification will come sooner rather than later but won't venture fourth until I'm absolutely sure of what needs to be done.
Again, thanks for the help it is appreciated.:laugh:
Click to expand...
Click to collapse
Download 64 bit software for 64 bit windows and 32 bit on 32 bit windows. Only notable exceptions are where a guide explicitly says to get 32 bit for some particular reason (in my case the only time I have come across this is MSI afterburners screen recording facilities only functioning on a 32 bit program for some reason, no 64 bit version) or if you are running 32 bit windows and physically cannot run 64 bit software even though a guide says "use 64 bit java etc etc".
rather interested in installing a graphics card in a laptop seeming as laptops use graphics cards that are soldered down to the motherboard not on a seperate removable card in all with very few (but existant) exceptions.... I think asus, dell and someone else did offer them at one point, its actually what the MXM connector was invented for (but its used for a few other things now instead).
Anyway. Its always good to have clarification. I think the post above me gives a few starting points and as always: google is your friend (so are bing and yahoo, but they are those friends where once you leave your job or school or whatever you probably wont ever see again).
boot achieved
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So I restarted everything and the device is now showing up in the Andriod Device driver list.
I am using minimal adb and Fastboot application. It opens the command menu
I type in
adb reboot bootloader and I get the reply "error:device not found"
any ideas?
Sigh!
gogul1 said:
I boot loaded the Shield through dab and boot loader.
Shield restarted once I chose to unlock the shield. I lost all my stuff (as expected) and it restarted. The drivers then reinstalled on my laptop.
I restarted my laptop and the shield again and tried to reinstall the drivers that were made for the ADB but sadly I get this message now...
"Windows has determined that your driver software is up to date MTP USB DEVICE"
So the shield is now showing up in my computer manager under Portable Devices and not under the Android Devices like it did when I installed the custom drivers the first time.
Will this be an issue when I come to root?
Sigh!
Click to expand...
Click to collapse
the MTP driver is for plugging the shield in and viewing the file system. If the device isn't under android devices in device manager then you may need to reinstall the ADB drivers or just double check that the ADB can see the device (it may).
Open a command prompt. type "cd [path to the android sdk]\platform-tools"
Then type "adb devices".
It should list all the android devices it can make a debug connection to. If the Shield is in that list your good, otherwise don't proceed any further until you can rectify that.
The other solution is that you dont need ADB drivers on a linux system for some reason. Don't ask why. I havent a clue. But that would necessitate installing linux.
And something that is useful for finding the adb on the command line again in future for windows. You don't want to "cd" into the correct folder every time (the command line equivalent of opening folders). Sometimes you just want to be able to open the command prompt, type "adb devices" and it to just work. That's doable by altering your system PATH variable.
Open my computer. Right click > Properties, should open the System window.
Left side there should be a button saying "Advanced system settings".
It will open the "System Properties" window to the "Advanced" tab (if it isnt on that tab just switch).
Bottom of the window should be a button saying "Environment Variables...". Click it.
Now the window that appears will be split in 2. User variables and System variables. There is a PATH entry in both, it is best that you only change 1. If you are the only user or you only want your user to be able to access the adb, you can change the User variable. Otherwise you can change the system variable for the adb to work on all users. For me I had to add python to my path once but I wanted to do this for all users so I changed the system one, the PSP SDK I installed however altered the User variable by default. Make your choice and find the variable "PATH" in either one.
Click Edit. A window will appear with Variable name and Variable Value. At this point what I recommend doing is copying the entire contents of value into a notepad file and saving them as a backup. Then cancel and go back into it.
Code:
C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Lua\5.1;C:\Program Files (x86)\Lua\5.1\clibs;C:\Python27;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
That is my Path variable.If you look the path variable is mostly a series of filepaths (or other variables too) which are seperated with ";". When you type a command such as "adb" into a command prompt what windows does is searches the current command prompt directory for a file it can execute which is called "adb" (it ignores extensions unless explicitly given one), if it doesnt find it in the current directory it searches each folder in the system path variable for the same executable (it ignores sub directories, it will only search the folders above on my system). So if we want to be able to type adb from any folder, we need the folder the adb is in to be added to the system path variable.
Simply add this to the end of it
Code:
;[whatever the path to the adb folder on your system is]
It will be whatever you had to add after "cd" to get to the adb earlier (must not leave out the C:\Users etc etc if its stored in your documents, cd will let you get away with ignoring that, the variable requires the FULL filepath).
Save the variable. Open a command prompt. Type adb, should work. If not, QUICKLY RESTORE THE BACKUP BEFORE WORKING OUT WHAT WENT WRONG. Should be safe with the broken variable to be fair, but you don't want to risk anything. If you dont think your going to use the adb often then simply dont bother updating the path variable rather than taking the (minimal) risk.
Wow my path variable is beginning to get a bit long now I only manually added python and lua to it. The rest will be the default entries and the SQL server stuff appears to be from installing visual studio. Yours probably wont match.
hehe you're going to hit me in a minute...
message deleted as I was being a moron....
ok I should be entirely clear as you guys are trying to help
ok I should be entirely clear as you guys are trying to help me so it's best i let you know what I have done up until this point.
Ok so I boot loader my shield.
I downloaded minimal ADB and Fastboot. I also downloaded the drivers you recommended in the forum.
I installed the drivers:
My shield showed up in the computer Manage list as a Portable device.
I chose to install the new drivers, it asked if I still wanted to go ahead as the drivers could not be verified and I said yes.
The drivers installed and the Shield changed from being in the portable list to showing up as an Android device.
Success I believe.
I then opened ADB BOOTLOADER and booted my Shield Manually.
I then typed in the relevant prompts in the command and a list of options showed up on the shield.
It showed my device number in the command prompt which was the one on my shield screen.
I then command the unlock function and the shield offered me the option to lock or unlock.
I chose Unlock and it then rebooted.
When it restarted, my computer reinstalled the device drivers and my shield had reset to factory settings (as it should).
I then looked in the Computer Manage list and my Shield had reverted back to being in the Portable Devices list.
I restarted both again and the Shield then showed up under Android Devices like it did when I installed the custom drivers the first time.
But the name of the device is Nvidia Shield - not Nvidia Shield ADB like in the tutorial video... not sure it that helps.
I enabled USB Debugging,
put the Superuser.apk and Su bin file into the minimal AADB and Bootloader folder.
I then put the Thor-insecure-boot.img in the Minimal ADB and Bootloader folder too.
I started up the command prompt from the minimal ADB and Bootloader.
I then saw this
C:\Program files <X86>\Minimal ADB and Fastboot>
I then typed in adb reboot boot loader and pressed enter
I got
error: device not found
So I decided to take the above advice and opened a command prompt
I typed in cd C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools
and pressed enter:
It repeated what I typed and I then put in adb devices.
It then came back with:
List of Devices attached
but nothing was listed....
doh!
Progress!
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
Do I have to choose one of these in order for it to begin the thor img command?
C:\tools\adt-bundle-windows-x86_64-20130729\sdk\platform-tools Just incase you didnt get it earlier. That would be the path required for the variable change above. Just whack a ; on the end of the existing variable and throw that new path on the end and done.
But yes, adb devices not listing shield is not a good thing. Try reinstalling the ADB driver for the shield manually (you cant do it via device manager etc).
cool
I'm past that and now <waiting for device> problem to rectify. Am looking online now but there isn't much on there so far...
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far
picture
ok so here is a pic of my devices list fastboot is there
before boot
This is the devices it can see before I put the shield in boot mode
devices seen after shielf in boot mode
the are the devices seen after I put the Shield in boot mode. It can't see any devices
waiting for devices
This is the screen on the shield in boot mode. The CMD screen says "Waiting for Devices"
** Version 4.7 Updated October 2016 - Supports Android 4.0-7.0 **
SUMMARY:
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
UPDATE: This tool was last updated on October 12th 2016. and confirmed working on Android 4.0-7.0 using WhatsApp version v2.16.304 (latest available).
IMPORTANT: If you wish to extract media files or WhatsApp databases from Google Drive backups then you need: WhatsApp Google Drive Extractor instead.
TUTORIAL:
BRANCH UPDATES:
v4.0 - Fixed issues with Android API 14-17 (4.0-4.2 Jelly Bean).
v4.1 - Added support for Android API 23 (6.0-6.0.1 Marshmallow).
v4.2 - Added support for specifying adb backup passwords.
v4.3 - Added PowerShell version as optional alternative to bat version.
v4.4 - Changed primary mirror for legacy apk.
v4.5 - Fixed issue pushing cipher key to emulated storage.
v4.6 - Updated primary mirror for legacy apk (again).
v4.7 - Added new sanity checks and support for Android API 24 (7.0 Nougat).
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Java - If not installed: Download Java
ADB (Android Debug Bridge) Drivers
USB Debugging* must be enabled on the target device. Settings -> Developer Options -> (Debugging) USB debugging
Android device with Android 4.0 or higher. I.E. Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow or Nougat.
*= If you cannot find Developer Options then please go to: Settings -> About phone/device and tap the Build number multiple times.
INSTRUCTIONS:
Extract WhatsApp-Key-DB-Extractor-master.zip maintaining the directory structure.
Click on WhatsAppKeyDBExtract.bat (Windows) or WhatsAppKeyDBExtract.sh (Mac OS X / Linux).
Connect your device via USB, unlock your screen and wait for Full backup to appear.
Enter your backup password or leave blank (if none set) and tap on Back up my data.
Confirm backup password in your command console and then check the "extracted" folder.
TROUBLESHOOTING:
If you have never used USB Debugging before, you may also need to verify the fingerprint.
If you have set a default backup password in your Android settings, then this MUST be the
backup password that you provide when prompted to backup your data. Else it WILL fail!
Linux and Mac OS X users may need to set the script permissions as executable. Depending on the
adb permissions, you may also need to sudo ./WhatsAppKeyDBExtract.sh from your command console.
If you're having issues with WhatsAppKeyDBExtract.bat then right click WhatsAppKeyDBExtract.ps1
and select Run with PowerShell. You may have to enter "y" at first run for script execution policy.
If you get an error saying "AES encryption not allowed" then you need to update your Oracle Java
Cryptography Extension (JCE) to Unlimited Strength Jurisdiction Policy Files.
DOWNLOAD: WhatsApp-Key-DB-Extractor-master.zip
AUTHOR: TripCode
THANKS: dragomerlin for Android Backup Extractor and Abinash Bishoyi for being cool.
alternatives
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
droopyar said:
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
Click to expand...
Click to collapse
The only way to access private application files (such as a WhatsApp's cipher key) without root is the ADB method. You can backup some files on the device without a PC (APK's etc...), but there is currently no way to access private files and folders. All the "My Big Fat Backup" style apps and tools will either require root or ADB. Eclipse also utilizes ADB. Basically, device side backups of application data require root. There are no other alternatives to this. If there was, then Android would be too infeasible and insecure as a viable operating system. Physical access translates into only two solutions. 1.) The ability to root and 2.) The ability to utilize ADB (Eclipse, Bats, Exe's doing nothing more than calling a simple command line). Of course if you are aware of a 3rd method (disregarding the user interface) and is not based on root or ADB then please feel free to share.
Thanks for this tool!
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Thanks!!
Mia
PS I got JDK installed and still not working
MiaNet said:
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Click to expand...
Click to collapse
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
still showing this message attached
TripCode said:
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
Click to expand...
Click to collapse
Still showing the attached message
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Many thanks! I'll test when home and let you know.
Just to let know, the path command do not fix the prior version with Java check as I first thought this might be the problem.
Thanks!
Mia
Could even be use with ADB from phone to phone? without using the pc? Or I must install the app on the phone and do it offline?
I have find my way! Re-installed Java, manually clicked on java.exe stored in Java folder in Program files (or Program files (x86) ) I've clicked on Javacpl as well and enabled all options, not sure if this is necessary though.
I've then rerun the program without Java check (the Java check one is bugging now) and was able to do the back up.
Thanks!!
Best regards,
Melanie
Cannot tap button
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Permission denied
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Error
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
I, too am showing the same error.
Curwens said:
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Click to expand...
Click to collapse
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
kharloz_jc said:
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Click to expand...
Click to collapse
cardinalaa said:
I, too am showing the same error.
Click to expand...
Click to collapse
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
TripCode said:
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Click to expand...
Click to collapse
Hi, I am receiving the "Cannot find the path specified" error. I have tried both changing the script and also the other method, in environment variables. I am curious if this has anything to do with the fact that its an ATT phone (since no one can even root it yet)? No other apps can access my phone, either. I have USB debugging enabled and all prerequisite programs installed. Tried on 2 computers, win7 and win 8.1
I wonder if i it is an error on my part..?
TripCode said:
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
Click to expand...
Click to collapse
I have reviewed the "Extract" folder and there was the key. I have managed to decrypt it.
Thanks for the help and the tool!
PD: sorry for my bad English, I use translator is haha.
Nothing happens
Hi, first, thanks for this iniciative. A lot of people would apreciate this
I think I did everything as u said, but when I open the WhatsAppKeyExtract,bat and then conect my phone in debuggin mode to PC, nothing happens. Ive waited for 10 minutes and.. nothing happens. Keep showing the initial message: "Please connect your Android device..." and in my phone nothing happens too. Just show a messagem at the upper tab saying: "USB debbugin conected".
Theres any kind of setting to do futher in the debbug options?
Thanks
Update: I had do install de universal adb driver for my phone, and now it starts the download, but now im having problem with java... the messagem says "'java' isnt a recognizable command". I tried all solutions in this post and nothing.. I need heeeelp!
Solution to path problem
Is working perfect. For someone else that can happen the same thing as me. I have to fix something (i am spanish) about:
java is not recognized as an internal or external command, operable program or batch file
Here is the solution:
java .com/en/download/help/path.xml
Or here:
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer
6. Make Sure to add a semicolon after the word bin in the path to seperate it from the other important paths
7. If this doesnt work then you may have to reinstall Java and Try Again
Setting Path on Windows
For Windows XP:
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
tzuyang said:
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
Click to expand...
Click to collapse
Have seen this error before (not related to bat file). You may need to revert to an earlier Java version.
There are servel cmds which we can use
But I post only top 10 cmds to help that ones who need
###############
If I make a mistake so please reply with your suggestions
And if you want a cmd in the list .submit your reply with cmd and features ( full detail as you know.).
########cmds###########
For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands. That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.
The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time. The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.
Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!
1. The adb devices command
The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK. Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.
Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!
Now that we have everything set up, let's look at a few more commands.
2. The adb push command
If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.
I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.
3. The adb pull command
If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.
In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.
5. The adb reboot-bootloader and adb reboot recovery commands
Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.
Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.
6. The fastboot devices command
When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating. That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.
7. The fastboot oem unlock command
The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness. Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.
Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device
8. The adb shell command
The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS.
The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.
9. The adb install command
While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.
And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.
10. The adb logcat command
The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.
To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.
You also have to specify the cmds properly.
Hope it help you .
Like my work hit thanks button.
$$$$$$$$$$$$$$$$$$$$$$$$
Any suggestions most welcome.
$$$$$$$$$$$$$$$$$$$$$$$$$
How to Reset Your Forgotten Windows Password
Forgetting your password is never any fun, but luckily there's a really easy way to reset the password. All you need is a copy of the windows installation disk and one simple command line trick.
Resetting Your Forgotten Windows Password
Boot off the Windows disk and select the “Repair your computer” option from the lower left-hand corner.
Follow through until you get to the option to open the Command Prompt, which you'll want to select.
First you'll want to type in the following command to backup the original sticky keys file:
Copy c:\windows\system32\sethc.exe c:\
Then you'll copy the command prompt executable (cmd.exe) over top of the sticky keys executable:
Copy c:\windows\system32\cmd.exe c:\windows\system32\sethc.exe
Now you can reboot the PC.
Resetting the Password
Once you get to the login screen, hit the Shift key 5 times, and you'll see an administrator mode command prompt.
Now to reset the password—just type the following command, replacing the username and password with the combination you want:
Net user Admin MyNewPassword
That's all there is to it. Now you can login.
Of course, you'll probably want to put the original sethc.exe file back, which you can do by rebooting into the installation CD, opening the command prompt, and copying the c:\sethc.exe file back to c:\windows \system32\sethc.exe.
Source
This should be the source of the above trick:
howtogeek.com/96630/how-to-reset-your-forgotten-windows-password-the-easy-way/
Please don't copy and paste stuff from the interwebz and post it here as your own.
Thread closed.