This is the Q&A for Infuse4G One-Click back to stock. The rules are as follows
Be respectful
if you know the answer to someones question, answer it. When people ask questions, they want answers now. A wrong answer is worse than the right answer but better than no answer.
What is Infuse4G Back-To-Stock?
This program is a Java based application which will restore your device to factory specs UCKD5 with one-click. Infuse4G Back-To-Stock uses Heimdall One-Click.
What is Heimdall One-Click
"Heimdal One-Click" is an open-source one-click package distribution tool based on "Heimdall" by Benjamin Dobell. I developed Heimdall One-Click application to make software redistributon easier for the end user and thus easier to support for the developers.
Where can I find Infuse4G Back-To-Stock
http://forum.xda-developers.com/showthread.php?t=1216790
How do i use Infuse4G Back-To-Stock?
1. Double-click the file, or right-click and open with java. (You will be prompted to install heimdall the first time.)
2. Connect the device in download mode (Remove battery. Hold VOL+, VOL- and insert battery.)
3. Click flash (In the event of any issues, reboot the computer and start at step 1.)
This does not wipe the "data partitons" or old program information. To finish up, use 4a or 4b.
4a. Wipe Data Wipe user data in recovery mode (Remove battery. Disconnect USB. Hold VOL+, VOL- and insert battery. Select "wipe data")
--or--
4b. Reformat This will wipe user data and SDCard. In dialer type: *2767*3855#
How do I put my phone in Download Mode?
1. Remove the battery
2. Connect USB cable to the computer and the device.
3. hold Volume + and Volume - while inserting the battery
Why wont Heimdall One-Click won't detect my phone? What do I do in the event of a problem?
Each of the following items can be performed out-of-order.
Reinstall heimdall by clicking Help>Install Heimdall.
Restart the One-Click program.
Restart computer and put phone back in download mode.
Windows: ensure you have heimdall drivers installed. You must select "show all devices" in Zadig (the driver installer program).
Check that you have 400 Megabytes of disk space or more.
If this is open source, where is the source?
Right here: http://code.google.com/p/heimdall-one-click/source/browse/#svn/trunk
What can I do if I found a problem and I'm sure it's not just me?
First off, when you post about a problem, it must include the log from the detail window. If you can't get the program to open, then include the console log.
post here.
post here: http://forum.xda-developers.com/showthread.php?t=1216790
Fill out this form in it's entirety: http://code.google.com/p/heimdall-one-click/issues/entry
How do I get the console log
On Linux and Mac:
Code:
java -jar /path_to/One-Click.jar
where /path_to/One-Click.jar is the location of the One-Click program.
On Windows:
Code:
C:\path_to_java.exe -jar C:\path_to\One-Click.jar
Where path_to_java.exe is the path to the java file (usually in c:\program files\java\jre\bin\java.exe) and path_to_one_click is the location of the One-Click program.
Why does it say beta?
The size is still a bit large. I woud prefer that most stock ROMs fit into a 200 megabyte package. Currently, packages take 205 megabytes. Most sites like MediaFire only allow 200 megabyte packages.
ensure you have 400 Megabytes of disk space or more.
how do i check this and if i need more space how do i do so?
^^ Windows: my computer>hover over C: drive. Linux/Mac: terminal "df"
If you have a problem, restart the phone, restart the program, try again. and if that does not work, restart the computer. It's really simple.
To free up more space on WIndows, use the disk cleanup utility. On Linux/Mac, reboot the computer to clear the temp folder.
AdamOutler said:
^^ Windows: my computer>hover over C: drive. Linux/Mac: terminal "df"
If you have a problem, restart the phone, restart the program, try again. and if that does not work, restart the computer. It's really simple.
To free up more space on WIndows, use the disk cleanup utility. On Linux/Mac, reboot the computer to clear the temp folder.
Click to expand...
Click to collapse
first off #1 problem........PHONE WONT DO ANYTHING BUT DL MODE!!!!!!!!!!!!
wont power on, ect ect ect
2. restarted program SEVERAL times....still getting same issue, stuck at setting up interface.
3. restarted computer twice, same thing!
also how would i be able to show you the detailed log of the one click if i cant save it or copy it??
space says 41.2gb free
145gb total
bignate78 said:
first off #1 problem........PHONE WONT DO ANYTHING BUT DL MODE!!!!!!!!!!!!
wont power on, ect ect ect
2. restarted program SEVERAL times....still getting same issue, stuck at setting up interface.
3. restarted computer twice, same thing!
also how would i be able to show you the detailed log of the one click if i cant save it or copy it??
Click to expand...
Click to collapse
K, don't panic. This program has everything you need built in.
In program, help>install heimdall. follow the on-screen directions.
To copy the log, click in the log press ctrl+a, ctrl+c then click on this window and ctrl+v to paste. I should make a save log buton.
AdamOutler said:
K, don't panic. This program has everything you need built in.
In program, help>install heimdall. follow the on-screen directions.
To copy the log, click in the log press ctrl+a, ctrl+c then click on this window and ctrl+v to paste. I should make a save log buton.
Click to expand...
Click to collapse
IBL+PBL true false 1 0
PIT true false 1 1
EFS false false 40 20
SBL true false 5 3
SBL2 true false 5 4
PARAM true false 20 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\param.lfs 21
KERNEL false true 30 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\zImage 6
RECOVERY false false 30 7
FACTORYFS false true 1146 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\factoryfs.rfs 22
DBDATAFS false true 536 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\dbdata.rfs 23
CACHE false true 130 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\cache.rfs 24
MODEM false true 60 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\modem.bin 11
false 0 11
bignate78 said:
IBL+PBL true false 1 0
PIT true false 1 1
EFS false false 40 20
SBL true false 5 3
SBL2 true false 5 4
PARAM true false 20 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\param.lfs 21
KERNEL false true 30 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\zImage 6
RECOVERY false false 30 7
FACTORYFS false true 1146 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\factoryfs.rfs 22
DBDATAFS false true 536 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\dbdata.rfs 23
CACHE false true 130 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\cache.rfs 24
MODEM false true 60 C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\modem.bin 11
false 0 11
Click to expand...
Click to collapse
Looks good. Everything is fine. Click flash. I need the log, not the table above the log.
Is your username really yoursorryass?
AdamOutler said:
Looks good. Everything is fine. Click flash.
Is your username really yoursorryass?
Click to expand...
Click to collapse
thats after i clicked flash!!
i can copy the bottom log, wont let me.
thats the name of the second user side of my comp.
I need the log under the table. Not the table. Please wrap it in [ code] [/code] tags.. much cleaner that way.
Is this XP? Run as administrator. Permissions cannot be elevated with a yes/no UAC prompt in XP as in Win7 or Vista.
If you can't copy the table, then the log will be in the same folder as the files in the table. log.txt
it come up with an error of file cannot be opened with the param in it
Deleting C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\ROMPACKAGECleaning up folder:C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\ROMPACKAGEStatics.setSystemInfo(): Windows Operating System: Windows
###executing: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe###arrayToString [Ljava.lang.String;@d19bc8 expanded to: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe
###executing: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe###arrayToString [Ljava.lang.String;@14a8cd1 expanded to: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe versionFound Heimdall Version: v1.3.0Infuse4G-BackToStock Stock is ready for your device.
Attempting to write C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\vcredist_x86.exeAttempting to write C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\Elevate.exeVerifying C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\\Elevate.exe . Result=trueResult=truearrayToString [Ljava.lang.String;@175d6ab expanded to: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\vcredist_x86.exe
###executing: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\vcredist_x86.exe###Response from command "C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\vcredist_x86.exe":Attempting to write C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32.zipAttempting to write C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32.zipSearching for heimdall in folder:C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\Searching C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32Searching for heimdall in folder:C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0Searching C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\Drivers
###executing: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe###Response from command "C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\heimdall.exe":
v1.3.0Installing driversDevice not connected.Ready.Attempting to write C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\Elevate.exeVerifying C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\\Elevate.exe . Result=trueResult=truearrayToString [Ljava.lang.String;@ca470 expanded to: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\Drivers\zadig.exe
###executing: C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\Drivers\zadig.exe###Response from command "C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\heimdall-win32\Heimdall Suite 1.3.0\Drivers\zadig.exe":nullnullHeimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
ERROR: Failed to open file "C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\param.lfs"
nullnullHeimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
ERROR: Failed to open file "C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\param.lfs"
Interesting... does
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHei mdallOneClickF9B9EFB8\
actually exist?
or is it
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
?
Also, please use code tags...
AdamOutler said:
Interesting... does
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHei mdallOneClickF9B9EFB8\
actually exist?
or is it
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
?
Also, please use code tags...
Click to expand...
Click to collapse
i have no idea, and i dont know what code tags are
AdamOutler said:
Interesting... does
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHei mdallOneClickF9B9EFB8\
actually exist?
or is it
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
?
Also, please use code tags...
Click to expand...
Click to collapse
in the error log it show it without the space
bignate78 said:
in the error log it show it without the space
Click to expand...
Click to collapse
ok... that's because it does not have code tags... I'm troubleshooting without data..
Please post the log like this:
"[ code]" log log log and "[ /code]
around it without the spaces or quotes in the "[/code]" tags. That makes it into a nice code block which is formatted for reading...
I need to know if the folder exists... you can use explorer or internet explorer and copy/paste this into the navigation bar:
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
or
Start>run>type cmd then in the cmd window copy and paste this:
Code:
dir C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
and see if anything comes up.
I see the same problem on my XP machine... it was not doing this before... I'll be doing a series of commits at oneclick.adamoutler.com to resolve this issue.
in the mean time.. use One-Click UnBrick http://forum.xda-developers.com/showthread.php?t=1153310
This is a different tool. it releases the bootlocks. it's not UCKD5 one-click
Alright... do not use this package under Windows XP. It will not work for now.... I'll fix it. However, it will only work on the first boot and the first boot only.
AdamOutler said:
ok... that's because it does not have code tags... I'm troubleshooting without data..
Please post the log like this:
"[ code]" log log log and "[ /code]
around it without the spaces or quotes in the "[/code]" tags. That makes it into a nice code block which is formatted for reading...
I need to know if the folder exists... you can use explorer or internet explorer and copy/paste this into the navigation bar:
Code:
C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
or
Start>run>type cmd then in the cmd window copy and paste this:
Code:
dir C:\DOCUME~1\YOURSO~1\LOCALS~1\Temp\yoursorryassHeimdallOneClickF9B9EFB8\
and see if anything comes up.
I see the same problem on my XP machine... it was not doing this before... I'll be doing a series of commits at oneclick.adamoutler.com to resolve this issue.
Click to expand...
Click to collapse
yes something came up.
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 all,
Saw there were no guides for ClockworkMod install on Mac. And people cool enough to have the DHD must also surely have Macs Or like hacking about enough to have a hackintosh. So anyways, I made a guide.
Rooting and s-off
I rooted using this thread here
http://forum.xda-developers.com/showthread.php?t=835746
You need to download visionary r12 and a terminal emulator, but its all explained there. Exact same process as for windows users.
Once you are rooted and have s-off, come back here.
ClockworkMod Recovery (Updated guide for [email protected] version)
1. Download the Android SDK for Mac from HERE
Extract it, then move the whole folder to the root of your main drive
e.g for me its full path is "/Snow/android-sdk-mac_x86"
2. Download the HTC fastboot binary from Here
Then extract it and move it to /xxxx/android-sdk-mac_x86/tools/
3. Download the clockwork.img from This thread
And copy it to the tools folder where you put fastboot
4. Connect your DHD to the computer in charge only mode.
5. Open Terminal.app
6. Type
Code:
cd /xxxx/android-sdk-mac_x86/tools/
Where xxxx is the name of your drive
And press enter.
If the drive where your sdk folder is located has a space in its name, you have to add a backslash before the second word.
e.g if your drive is called "Macintosh HD" the path will be:
/Macintosh \HD/android-sdk-mac_x86/tools
Alternatively, if you cant be asked typing into terminal, type cd, then a space, drag the tools folder to the terminal window, make sure it says the right path, then press enter.
7. Type
Code:
./adb devices
And press enter
Check your device is listed correctly y checking its serial number in settings on your phone with the serial number that comes up
8.Type
Code:
./adb reboot bootloader
And press enter
This should reboot your phone to bootloader, with green writing at the top, then fastboot USB in red.
9. Now type
Code:
./fastboot flash recovery clockwork.img
And press enter
If youve done it correctly, it will say
Code:
sending 'recovery' (4914 KB)... OKAY
writing 'recovery'... OKAY
10. Now use the volume buttons to navigate, and power button to select, and navigate to bootloader, then once that loads, to recovery.
Let it load and ClockworkMod will load.
Then click down through the whole menu 3 times until it says 'back menu button enabled"
This means the power button now is the select button.
You now have CM successfully installed, and can reboot, install new roms etc as you please!
No guarantee provided for this guide, if it breaks your device, blows up the computer, gets you sued by google or whatever, I am not responsible and you do all this at your own risk.
Any improvements to the guide, please say in the thread.
I am also working on a script/app to do it all on OS X with one click. Will hopefully be done once this 10 days of coursework and tests is over!
Happy Flashing and thanks to all the devs that made this possible!
Rory
excellent looking forward to the app!
mac OS x needs love from android! devs
Yeah!!!
Useful Guide! Thanks!!
Thanks!
I'm running Ubuntu and the commands are basically the same for Linux systems.
But Linux users will need to add a small file to let the OS see the Device correctly.
Follow step 3 "Setup your system to detect your device." in the guide below:
http://developer.android.com/guide/developing/device.html
Great guide!!!
but on Mac I ceep on getting a signature error??
What am i forgetting?
duanes said:
Great guide!!!
but on Mac I ceep on getting a signature error??
What am i forgetting?
Click to expand...
Click to collapse
Not sure mate, maybe look in the windows threads.
First thing I would suggest is redownload the recovery image.
At what point are you getting the signature error?
excellent i just did it..and my DHD is free!
nandihno said:
excellent i just did it..and my DHD is free!
Click to expand...
Click to collapse
Glad I could help. Will soon be expanding it for flashing kernels and ROMs using fastboot.
Thank you so much for this tutorial is very useful! If Mac users who believe that this method is difficult, can install BootCamp and run Windows natively. I use Windows 7 Ultimate under BootCamp to use the tools for Root, Downgrade, etc... (remember: for use the tools under Windows, runing under "Administrator mode" click right on mouse over the EXE file
Someone with a Mac to use Parallels Desktop or VMWare Fusion for root, to Downgrade, etc with the DHD?
Regards,
Linux users please go HERE (thanks to bloodychaos)Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
UPDATE: Not necessary for Windows 7 is installng adb drivers automatically after plugging the device and fastboot ones after rebooting the connected device to bootloader. To get the HTC USB Drivers on different Windows version download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
fonpacific said:
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Click to expand...
Click to collapse
Method 3:
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Good Idea!
Have put a link to this within the GUIDES section of [INDEX][22 SEP 11] ROMS/RECOVERY/ROOT/HBOOT/RADIOS/TWEAKS/GUIDES/etc
I believe that the guide would be more useful if you put in a link to a URL for the HTC Drivers and moved the advice about enabling USB Debugging to the top!
I can now point people at this guide rather than manually instruct them, Thank's you probably just saved me loads of time and aggravation!
Nice Work, Great Help
Excellent! Exactly what I needed. Thanks for showing us this.
Hi an thank you. Good guide.
I believe one important information is missing in the guide:
Before installing the HTC drivers (or HTC sync) it is necessary to temporarily disable AntiVirus software on Windows machines. If you don't do that, Windows won't recognise your phone. After the installation is finished, enable AntiVirus again.
I got this advice somewhere and it was true for me personally. I'm using Windows 7.
Sent from my HTC Desire S using XDA App
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
mimirom said:
One more comment:
This is a minor detail but I think it's worth mentioning.
If you are using the HTC Sync installation in order to get the HTC drivers only, you actually don't need to install and immediately uninstall HTC Sync itself.
The Sync installer will first install the Desired (pun fully intended ;-) drivers and the it will stop. Next it's going to ask you if you want to proceed with the installation of HTC Sync. At that point you hit cancel and you're done. No Sync, just the drivers.
Click to expand...
Click to collapse
It's very useful, Thanks!!
Doing all this the phone has to be turned off, on, or power button and volume down?
Desire S said:
Doing all this the phone has to be turned off, on, or power button and volume down?
Click to expand...
Click to collapse
You do not need a phone for this guide It is setup for PC
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
bonesy said:
Just a tip, if you put the Adb and fastboot files in C:/windows/system32 (32bit) or in C/windows/sysWOW64 (64bit) you can just use them from any command prompt window
Click to expand...
Click to collapse
This is exactly the purpose of point 4 of the guide (global path setup)
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
bonesy said:
Just trying to give another idea mate, I used to set up all the SDK and make a global path but now just drop them in those folders when i reinstal indows
Click to expand...
Click to collapse
Agree, added to the first post.
Sent from my Desire S using Tapatalk
Instructions for Linux users???
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
On my Linux system I have installed Java and the whole Android SDK and the set the path of course. If you are a Linux user you should know how to do this. Also there are guides for other devices that are basically the same
amidabuddha said:
Similar guides can be found on other devices subforums around but I can see that a lot of new users in our forum are not familiar with the setup and use of this commands.
All the instructions and installation files can be found on the Android Developers webpage, but for basic commands it is not necessary to download the whole SDK (which requires the JDK as well) to follow installation and the resources download process.
*Important: to use the adb/fastboot commands you have to enable USB Debugging in your phone Settings -> Applications -> Development menu*
To have working adb and fastboot system wide for basic commands just follow the steps below:
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system).
*According to post #5 in this thread in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync. Thanks @mimirom*
Download the zip archive (Mirror @MediaFire) or the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
Adding to the System Path globally to use the command without browsing to the containing folder
Method 1 (via GUI):
Go to My Computer icon -> right click and select Properties.
On the left side of the opened screen select Advanced system settings.
(Or Start -> Search -> type sysdm.cpl -> Enter, browse to the Advanced tab)
Look down on the opened menu and select Environment Variables.
In the lower half are listed the System Variables.
Scroll to find "Path" variable, select it and click Edit...
On the Edit window in the Variable value field go to the end of the line (do not delete it!) and add without any intervals (spaces):
Code:
;C:\android-tools
do not forget the semicolon symbol (;)!
Click Ok 3 times.
Method 2 (via Command prompt):
Go to Start and in the Search box type cmd, right click and Run as Administrator
Type
Code:
setx path /m "%PATH%;C:\android-tools"
and hit Enter. Close the cmd window
Method 3:
To check is it working properly open Command Prompt (Start -> Search -> type cmd -> Enter) and type adb
If everything is configured properly this should list you the Android Debug Bridge version and the available commands.
*HINT*: To use adb or fastboot with files in the Command prompt you have to navigate to the folder containing the file first (using the cd command) e.g. "D:\Downloads\Android" and then to execute the command.
Example:
Start -> type cmd in the Search box, then Enter. You will see
C:\Users\with blinking cursor
If your file is on another drive like the example type "d:" (without the quotes), or other drive letter to go to the relevant drive. Skip this if the file is on C: drive. Then type:
cd D:\Downloads\Android to go to the "D:\Downloads\Android" folder. If your path contains spaces (intervals) type it in quotes.
The command "cd.." brings you one folder back
Click to expand...
Click to collapse
Nice work mate
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
jamsh said:
Instructions for Linux users???
Click to expand...
Click to collapse
OP edited - there is a link to a guide for Linux users
fonpacific said:
Thanks a lot for the guide, dude!
By the way, I noticed that it doesn't work for me (windows 7 professional) unless i end the path of adb with "\", for example: ;C:\android-tools\ and not ;C:\android-tools as in your guide.
Hope it helps!
Click to expand...
Click to collapse
Thank you for the remark, I hope it will help the users with the same problem
Hey Guys, I need help!
after an installation of adb all I get is error:device not found
i entered a code adb shell and hit enter, than i entered
dmesg | grep mmc0, since you cannot put two lines of code at once (I'm a rookie)..
where did I put it wrong?
I can get to recovery of my device, but I get error like:
/I]E:Can't open /cache/recovery/command
I made revolutionary S-OFF..
Thanx for a help!
Rocks
You have to enable USB debugging in the settings.
And while in recovery it should work too
Sent from my HTC Desire S
** 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.
With a lot of work scrounging around, I've found all the pieces that fit making a jail-broken OS boot-ready Surface RT. As of Now like 5 or 6 years after it's release, there still doesn't seem to be a OS prepared to run on the Surface RT, but maybe if this thread gets enough popularity someone can get an android OS (Possibly derived from an Asus TF502T) Or a debian style Linux build for it. Credit to @ShapeShifter499 for secure boot unlock, @mamaich for Hard drive repartition instructions, @Screeny for original Downgrade instructions, and @netham45 for jailbreak tool and I have posted links to other threads that will also help once 8.1 is downgraded and jailbroken. Here are all files shared and ready for you:
https://drive.google.com/drive/folders/12VilYYz-gF82qzzs6qOkUXoaKz2us8J9?usp=sharing
And Here goes the instructions for the boot-ready Surface RT
1. Create Recovery usb stick (search for recovery drive in control panel, not the file recovery(you might want that too though))
2. Download Surface RT 8.0 Recovery (Took me forever to find, microsoft has removed it from it's site, i have included)
3. Unzip and Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image) to the root of your 8.1 recovery USB stick
4. Reboot into Recovery with the 8.1 recovery stick.
5. Open Command Prompt
6. Use DiskPart to clean the whole Disk (I had to use the override command)
7. While in Disk part use the following commands- (Minus the rem parts)
convert gpt
rem === 1. Windows RE tools partition ===========
create partition primary size=350
format quick fs=ntfs label="WinRE"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="T"
gpt attributes=0x8000000000000001
rem === 2. System partition =====================
create partition efi size=200
rem *** NOTE: For 4KB-per-sector drives, change this value to 260
format quick fs=fat32 label="System"
assign letter="S"
rem === 3. Microsoft Reserved (MSR) partition ===
create partition msr size=128
rem === 4. Windows partition ====================
rem == a. Create Windows partition ===========
create partition primary
rem == b. Create space for recovery image ====
shrink minimum=3600
rem == c. Prepare the Windows partition ======
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 5. Recovery image partition =============
create partition primary
format quick fs=ntfs label="Recovery Image"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="R"
gpt attributes=0x8000000000000001
exit
8. While in Command Prompt do the following
Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
(Make sure to include spaces in the proper places and replace U with your Recovery Drive letter, can be found with Diskpart command 'list vol')
bootrec /fixboot
9. Restart, login and disable automatic updates
10. Disable Bitlocker with administative command prompt with the following
manage-bde -unlock C: -RecoveryPassword YOUR-BITLOCKER-RECOVERY-KEY-HERE (Find your bitlocker code it has changed)
manage-bde -off C:
11. get the secureboot file and run the cmd file as admin. (use volume keys and windows button to select accept when the time comes)
12. After reboot (If stuck in bitlocker bootloop use recovery cmd to do #10) run administrative cmd and use- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
13. Use RT_jailbreak in administrative mode to run unsigned apps
14. Use SignTool to Sign any apps you want to continue to run
(optional)
15. use @VNNGYN development tool to continue updates and remove infected updates
I am Soon to test whether i can update directly from final state at #14 to windows 8.1 using the update file and development tool given without ruining anything noticable (Probably safer to run through all updates naturally but I'm impatient), will update with details as soon as I am successful.
---Update---- Microsoft seems to force going through the whole update process so no direct updating to 8.1------
Hopefully people can get the ball rolling with some other OS working fully on this tablet unlike windows 10 iot flop.
Development tool: https://forum.xda-developers.com/wi...ent/windows-8-1-rt-jailbreak-exploit-t3226835
Hacked Desktop Apps: https://forum.xda-developers.com/showthread.php?t=2092348
Compiling guide: https://forum.xda-developers.com/showthread.php?t=2096820
One Desktop app store: https://forum.xda-developers.com/showthread.php?t=2559750
Another Desktop app store: https://forum.xda-developers.com/showthread.php?t=2546221
I apologize if there's anything I missed, these are the same steps I took and where I'm at, once an OS development becomes available I will update a reserved comment.
Create recovery USB stick with attached file “windows 8.0” in the main article, then connect the USB stick into your surface and boot it holding the following keys (Volume Down + Power). Your surface now will boot into recovery from your USB stick and continue troubleshooting and refresh your surface with a new system deleting your files (chose the quick method). After you finish your surface will startup normally with Windows RT 8.0.
You can proceed from number 10. In the main article. Good luck
Reserved
Just as a clarification, this will only work for the original Surface RT. This will not work with the Surface 2
I want to clarify, I DID NOT CREATE THE UNLOCK. I just dug around and recused the needed files for the unlock. Many of them were dead links and lead nowhere. I found them scattered on forum postings, threads, and https://archive.org/ If I had to create this unlock from scratch it would take decades I'd think as currently I don't have the knowledge required for this sort of hacking.
Hi
After the step 8, why restart while then /EFI is always empty ?
I bootloop after doing bootrec /fixboot
and have to start all over again, anything to suggest here?
will Surface RT 8.0 North America restore a Vivotab?
<snip>..... Here are all files shared and ready for you:
drive google com/drive/folders/12VilYYz-gF82qzzs6qOkUXoaKz2us8J9?usp=sharing
.[/QUOTE said:
Is that the w8 rt restore image I can use to repair my asus vivotab w8 rt?
Click to expand...
Click to collapse
Can't get past step 8, Surface RT won't boot properly.
Have tried for 4KB-per-sector drives and won't work either way. Any suggestions?
Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
There is no space between imagefile and letter usb. Follow as below.
Dism /apply-image /imagefile:U:\Install.Wim /index:1 /ApplyDir:W:\
Change U with your own USB Stick drive letter.
well first of one, thanks a lot for your effort , i couldnt pass after the step 8 , as all the previous guys, i tried with this tutorial and the original one, more easy only with one partition (ntfs), i think that the steps are corrects but the problem is that the efi partition is empty an if you try to put the efi zip that is on google drive this efi doesnt work, i hope some one could explain with more details because the surface tablet is a very good one and the possibility to install another sw is required because microsoft sw in the store is very limited and discontinued.
Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond
XDA-00 said:
Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond
Click to expand...
Click to collapse
No, physical keyboard isn´t need
falsate said:
No, physical keyboard isn´t need
Click to expand...
Click to collapse
Thank you.
Deleted
@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.
XDA-00 said:
@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.
Click to expand...
Click to collapse
Here are some pics
XDA-00 said:
@Thedarkwolf123
Please add these steps to your guide after step 8 :-
Copying the EFIESP.zip files into the system (EFI) partition
Use bootrec /fixboot and then bootrec /rebuildbcd
EXIT and reboot.
Click to expand...
Click to collapse
how to copy efiesp under cmd
XDA-00 said:
Here are some pics
Click to expand...
Click to collapse
Hey would you mind writing out how you got it to work?
I followed the instructions and added your steps after step 8 but I still keep hitting a bootloop Everytime.
dont put a space after imagefile.. on step 8 on an rt U is drive D
the command line is wrong .the correct way is at the bottom command line .
But.. even when that finishes and the last step is bootrec /fixboot then exit then shut down it still wont boot and this doesnt work
and i doubt anyone has got it to work using these steps as evident in step 8 which is wrong and corrected by me.
its wrong not this
Dism /apply-image /imagefile: U:\Install.Wim /index:1 /ApplyDir:W:\
but this
Dism /apply-image /imagefile:U:\Install.Wim /index:1 /ApplyDir:W:\
XDA-00 said:
Hi, I have a Surface RT but its detachable keyboard is broken. Do I need the physical keyboard in this tutorial?
Pls respond
Click to expand...
Click to collapse
there is an onscreen keyboard but this fix is not working . also step 8 is wrong and everyone gets stuck there . see my post for the correct command line . dont put a space after imagefile:U:\ see they show this with a space after the first : imagefile: U:\ which wont work . no space between :U:\ but even after 100 percent and fixboot it still wont boot .just keeps showing surface then looping