After rooting using toast I am stuck at the recovery portion.
I am running Windows 7 64bit
Text in red are my questions.
RECOVERY INSTRUCTIONS:
- Extract the evorecovery.zip to your desktop
- plug your phone into a usb port on your desktop
- In a shell: <----Where is shell?
Code:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
Code:
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin <---I did this part and nothing happened the cmd prompt came and went quick.
- in a shell do:
Code:
For Linux ~~> ./recovery-linux.sh
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard. <---How do I wipe? I am so lost here.
Any help to make this easier because I am seeing some Linux lingo and I dont know what to ignore and how to go about this with Windows. Thanks for any help.
First. What version? 1.47? Or below?
Swyped from my Evo 4G
I was on Version 1.47, then I did simple root and went to 1.17? I wanted to make sure I root correctly with NAND. So I was re-rooting Toasts way. Now I am on version 1.32. Here is a screenshot.
To get the shell just go to a command prompt. CD to your /tools folder and type "adb shell"
robtrevino said:
To get the shell just go to a command prompt. CD to your /tools folder and type "adb shell"
Click to expand...
Click to collapse
Thats not helping. I dont know how to CD? CD is for linux? I am on Windows.
How do I do the evo recovery? Please explain in simple terms.
Step by step would help.
Im guessing I need to install adb on the computer? But the links on the how to have 404 error.
EDIT:
Found the links for the sdk install. ITs updating and installing , I hope thats what is needed.
got it from here----> http://developer.android.com/sdk/index.html
bump...
Really need some help. I would appreciate it very much. I dont want to go forward without doing this evo recovery.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Acer>cd c:\adnroid-sdk-windows\tools
The system cannot find the path specified.
C:\Users\Acer>c:\adnroid-sdk-windows\tools
The system cannot find the path specified.
C:\Users\Acer>cd c:\adnroid-sdk-windows\tools
The system cannot find the path specified.
anything I am doing wrong?
The files are in the C drive no idea whats wrong
You can use the sdk, or you can install sync drivers by plugging your phone into your computer and choosing the sync option. Install the program when it asks you and you will have the adb installed!
Then you can simply open command prompt and go step by step. BTW cd is a msdos command also to change directory (get it cd ) but if you go the sync route you won't need to worry about cd as it will set the path variable for you.
Anyway, after you install the sync, make sure to switch your phone back to charge only
I plugged my phone in and chose HTC sync, after connected I dont see anything asking me to install. I did install HTC sync on my computer already is thats what you mean?
Yes. Do me a favor, open command prompt and type adb and hit enter. Does it spit out a bunch of stuff or does it say command not found?
I'm new to all this as well and have yet to root mine(still learning everything) but there is a video from youtube that might help you but since I'm a new user it won't let me post outside links.
So, hit up youtube and search EVO 4G Root Walkthrough Part 2 of 2 by aboredguy52.
elegantai said:
Yes. Do me a favor, open command prompt and type adb and hit enter. Does it spit out a bunch of stuff or does it say command not found?
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Acer>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Acer>
if you want to help me walkthrough can we use a chat client?
let me know if thats ok.
churchwin88 said:
I'm new to all this as well and have yet to root mine(still learning everything) but there is a video from youtube that might help you but since I'm a new user it won't let me post outside links.
So, hit up youtube and search EVO 4G Root Walkthrough Part 2 of 2 by aboredguy52.
Click to expand...
Click to collapse
That is a good walkthrough but im stuck at adb-windows reboot recovery
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Acer>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Acer>
C:\Users\Acer>C:\Users\Acer\Desktop\EVO-recovery
'C:\Users\Acer\Desktop\EVO-recovery' is not recognized as an internal or externa
l command,
operable program or batch file.
C:\Users\Acer>cd
C:\Users\Acer
C:\Users\Acer>cd desktop
C:\Users\Acer\Desktop>cd evo-recovery
C:\Users\Acer\Desktop\EVO-recovery>adb-windows reboot recovery
'adb-windows' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Acer\Desktop\EVO-recovery>
It's easier for me to work it out here. But you are close, so let's just do this the hard way
You said you downloaded the sdk? So make sure its extracted. Then you want to go into that folder, find another folder called tools. Go into that folder and verify that you have a file called adb.
If so, let's set your path. Right click on any file inside of tools, click properties, and select the path or location and copy it. you should have copied the path to that folder. Then go to control panel, system, advanced system settings, then you should see a button called environmental variables. Click on that, then in the lower half of the screen scroll through the list and find the line that says PATH. Highlight it and select edit. Inside this dialog you will go to the end of the line, make sure there is a semicolon, and paste what you copied earlier and end it with a semicolon. Then apply or ok through all the dialog,s, open new command prompt as admin and do adb again.
elegantai said:
It's easier for me to work it out here. But you are close, so let's just do this the hard way
You said you downloaded the sdk? So make sure its extracted. Then you want to go into that folder, find another folder called tools. Go into that folder and verify that you have a file called adb.
If so, let's set your path. Right click on any file inside of tools, click properties, and select the path or location and copy it. you should have copied the path to that folder. Then go to control panel, system, advanced system settings, then you should see a button called environmental variables. Click on that, then in the lower half of the screen scroll through the list and find the line that says PATH. Highlight it and select edit. Inside this dialog you will go to the end of the line, make sure there is a semicolon, and paste what you copied earlier and end it with a semicolon. Then apply or ok through all the dialog,s, open new command prompt as admin and do adb again.
Click to expand...
Click to collapse
OK!!!! that worked! this is what I have.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\Windows\system32>
-------------------------------------------------
just so you know this is the name of the directory... C:\android-sdk\tools
Let me know the next step!
First of all
You were on the right track. I noticed that you typed cd c:\adndroid-sdk-windows\tools. This is misspelled and probably why your computer couldn't find the directory. If you put the android-sdk-windows file folder in the root of your C drive then you should be able to go into a command prompt and type cd c:\android-sdk-windows\tools . Then type "adb shell" (without quotation marks) and you should be in an adb shell where you can deliver commands directly to your phone based upon adb code. I am a new user here so I'm not able to post links but copy and past the link into your browser and put http before it. Here's the very helpful link with a recovery guide from Toast: forum.xda-developers.com/showthread.php?t=701835
If the file is named android-sdk then open a command prompt and type cd c:\android-sdk\tools hit enter then type adb shell.
Sorry lost track of what your question was!
You should be able to follow your guide now. Check out the wiki link at the top of this forum. Use the cache links since the Wilk is down. Anywho, from your first post, shell is the command prompt. So when it says open shell it means open your command prompt. The adb commands should all work.
Your question as to what wiping is, that is a feature of your recovery when you get to that part. Normally you use all the wipe options for data/cache/dalvik. This just cleans stuff out when you flash a new Rom so that you don't get any weird errors.
Let's pretend you're running Mac OS X or Linux. You might have your adb and fastboot files in a directory such as:
Code:
~/Android/
Which means to execute the command you have to
Code:
cd ~/Android/
then execute
Code:
./adb
You must be thinking, "There has to be a similar way!" Well, there is!
Code:
sudo cp ~/Android/adb /usr/bin
followed by
Code:
sudo cp ~/Android/fastboot /usr/bin
Now, all you have to do, no matter what you're present location in your file system is to simply type whichever command you want. This will probably speed up using the commands and make your time in terminal a little easier.
It is much more efficient to add the ~Android dir to PATH.
If you ever update your android sdk you'd have to copy the files again.
so better:
Code:
export PATH=~/Android:$PATH
if you want it persistent just change your ~/.profile file (depending on your distribution)
same would work in Windows, there you have to set PATH in the system settings.
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
1. Download terminal emulator,android vnc and arm version of backtrack.
2. Extract the content of img file and transfer it in to memory of android devices.
3. Install BusyBox and start it.
4. Open terminal emulator. use "cd" command to get in backtrack directory where extracted content is saved on memory card of device. In this case command is
cd /sdcard/BT5
5. Type "sh bootbt" and we will be in Backtrack.
commend
su
cd/sdcard/bt5
sh bootbt
startvnc
download from torrent
BackTrack 5 ARM Edition Quick Start
This image has been developed and tested on the you yureka. Your mileage may vary on other devices.
As this image runs in a chroot, you will need to have your device rooted. There are numerous tutorials on the subject online and are not included here.
***Rooting your device will potentially void its warranty and we are not in any way resposible if you brick your device while rooting it.***
### IMPORTANT POINTS ###
1. Since the image runs in a chroot, there is no root password set.
2. There are 2 scripts under /usr/bin/ 'startvnc' and 'stopvnc' that are set to start with the Xoom's default resolution.
3. The current vnc password is set to 'toortoor' and can be changed by running 'vncpasswd'
4. This image is a work in progress and suggestions/tips from the community are always welcome.
### GETTING STARTED ###
1. Once you have downloaded the ARM BT package, save the files in a convenient location. The steps below assume they are in the platform-tools folder of the Android SDK.
2. Go to your platform-tools directory and proceed to make a directory on the device to store BT5:
./adb shell
mkdir /sdcard/BT5
exit
3. Copy over the busybox install files:
./adb push busybox /sdcard/
./adb push installbusybox.sh /sdcard
4. Install busybox on the device:
./adb shell
cd /sdcard/
sh installbusybox.sh
exit
5. Transfer the required BT5 files to the device:
./adb push fsrw /sdcard/BT5/
./adb push mountonly /sdcard/BT5/
./adb push bootbt /sdcard/BT5/
./adb push bt5.img.gz /sdcard/BT5/
./adb push unionfs /sdcard/BT5/
6. Uncompress the image and start BT5:
./adb shell
su
cd /sdcard/BT5
gunzip bt5.img.gz
sh bootbt
If all goes well, you'll be in the BT5 chroot:
# sh bootbt
net.ipv4.ip_forward = 1
[email protected]:/# ls /pentest/
backdoors database exploits passwords scanners stressing voip
cisco enumeration forensics python sniffers tunneling web
[email protected]:/#