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.
Apparently, some firmwares seem to disable "adb" service on the Galaxy S.
So in case you run into this problem (adb unable to see the device) what you will need is to modify /default.prop on the SGS.
Here is what I had originally:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
To enable ADB on SGS
1. Run on the device: setprop persist.service.adb.enable 1 to temporarily switch it on.
2. pull /default.props with adb and modify the "ro.secure=0" and "persist.service.adb.enable=1"
2. mount -o remount,rw rootfs /
3. push modified default.props back to /
It's what I'd need, but the guide it's not quite clear to me:
1. Run on the device, means on terminal emulator?
2. How to pull? And please, specify better what to change...
I assume the rest of commands must be issue on the device via terminal emulator...
Let me know and thanx so much!
details
In more detail:
1. Root your device (see FAQ sticky post)
2. Install shell emulator on the device
3. In shell emulator, enable ADB (not sure if you need to run "su" before that):
setprop persist.service.adb.enable 1
4. Now, you should be able to connect to the device with ADB (temporarily). If not, make sure your udev rules (for Linux: /etc/udev/rules.d/51-android.rules) are smth like:
SUBSYSTEM=="usb|usb_device", ATTRS{idVendor}=="04e8", MODE="0666"
5. To make the change permanent:
adb pull /default.props .
(this will copy default props to local directory)
6. Modify the two properties as follows:
ro.secure=0
persist.service.adb.enable=1
7. Re-mount the root filesystem on the device in read-write mode (requires "su" before that):
mount -o remount,rw rootfs /
8. Now overwrite the /default.props on the device with modified one:
adb push default.props /default.props
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/show...88&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
Mirror(s):
http://www.bild-ton.net/Tattoo.rar
http://www.megaupload.com/?d=CI9AW83F
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/suAlso make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
i hope someone try this i don't have time
I couldn't reply to the [ROOT][EG30/31] Automated root of your existing stock ROM (w/o ODIN or ROM Flash)
post in the dev forums because I'm a noob, so I figured I'd post it here.
The OP's Mac instructions were a bit vague for noobs like me, but I figured it out, hope it helps others.
1. Download the eg30auto.zip listed in step 1 of the original post. Unzip it.
2. Follow step 2 in the original post for hooking up your phone
3. Download the platform tools here and unzip
4. Copy the adb file from the platform tools folder, to your eg30auto folder
5. Open a Terminal, cd to the eg30auto folder
6. Use these commands to open an adb shell, copy the needed files:
./adb shell
./adb push copy2tmp /data/local/tmp/
./adb push copy2sd /sdcard/
Click to expand...
Click to collapse
7. Run the exploit (do not type the $ symbols)
$ cd /data/local/tmp
$ /system/bin/sh install-zerg.sh
Click to expand...
Click to collapse
8. The previous step will take a few minutes. Assuming it is successful, it will kick you out of "adb shell". Restart "adb shell"
./adb shell
Click to expand...
Click to collapse
9. Your adb shell should now have the # prompt indicating temporary root. Proceed to install persistent root and cleanup the temp rooting files, followed by rebooting the phone (do not type the # symbols)
# cd /sdcard/000root
# /system/bin/sh install-root.sh
# /system/bin/sh install-cleanup.sh
# reboot
Click to expand...
Click to collapse
If you get an error during the install, consult the original post. Otherwise, you should be rooted now! Mad props to the hardworking devs that blessed us with this early christmas gift!
Hello,
I would like to start an app installed on a non rooted fire tv (generic solution, and as an example for xbmc) by adb. I found some examples, which all don't work... (I am able to start the adb shell and launch other commands...)
eg:
Code:
am start -a android.intent.action.MAIN -n org.xbmc.xbmc/android.app.NativeActivity
returns
Code:
Error type 3
Error: Activity class {org.xbmc.xbmc/android.app.NativeActivity} does not exist
.
Is this not possible on non rooted fire tv's?
Or do I just use a wrong syntax?
I am working on some remote conrtrol options, so launchers are not a solution for me.
Thanks for support.
adb shell am start -n org.xbmc.xbmc/.Splash
Kramar111 said:
adb shell am start -n org.xbmc.xbmc/.Splash
Click to expand...
Click to collapse
Works, thanks a lot!
Is there any way to get this for other apps out of the system?
eg: if I want to start netflix the same way, can I get the parameters from anywhre in the system or is "google my friend""?
with aapt (part of Android SDK):
run
Code:
aapt dump badging name.apk
and search line "launchable-activity"
or in GNU/Linux run
Code:
./aapt dump badging name.apk | grep "launchable-activity"
Kramar111 said:
with aapt (part of Android SDK):
run
Code:
aapt dump badging name.apk
and search line "launchable-activity"
or in GNU/Linux run
Code:
./aapt dump badging name.apk | grep "launchable-activity"
Click to expand...
Click to collapse
adb shell am start -n ir.hamgam.mobile/.Splash
for doesn't work plz help me