Related
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
I forgot to mention that I cheated and I don't know if that was a problem. I started with crb43 and used the old exploit to downgrade to rc29 (format sd card, copy rc29 update.zip to root of card, enter bootloader mode and flash).
SharpieMarker said:
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You should be using adb for terminal commands. If you type 'adb' in the terminal you will get nothing.
Go to terminal emulator and type 'su'
if it brings up the permission screen press 'allow'
if your command line changed from '$' to '#' then you have successfully rooted.
There shouldn't be anything in superuser permissions if you haven't given any apps permissions (every app is considered a different user)
Hope this helps, but this seems like a thread that would be better suited to the Q&A or Dream topics since this is the Development section not general questions...just thought I'd mention it.
Just AIM me: Breakthecycle2
Breakthecycle2 said:
Just AIM me: Breakthecycle2
Click to expand...
Click to collapse
I can't use AIM at work. I am better reached at [email protected]
I think that worked. su brought up permissions window and when I select allow I now have root. Brilliant. Thanks very much for the assistance.
EDIT:
Oops
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
SharpieMarker said:
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
Click to expand...
Click to collapse
adb is the Android Device Bridge that allows you to interface your G1/Magic with an x86 Windows system. It is included in the Android Developer Toolkit.
You need windows and to have your G1 connected to your computer. There are a few really good threads giving step by step walkthroughs on setting it up correctly, just use the search.
ADB for Dummies
ADB for Dummies
ADB can't be used from terminal emulator on the phone...you have to use it from your windows command prompt...read up on ADB first.
I hope this post can be of use to someone. My workplace is running Lotus Notes (sigh) and IBM recently released an update to their Traveler server which supports Activesync sychronizaton of mail, contacts, calendar and directory on Android, Iphone, etc.
The only problem is AT&T blocks Sideloading. Yes a simple root can fix the issue but that is not a true solution for every Captivate for our users. I figured out a relatively easy method of getting around this limitation.
First you need the following:
Rooted Captivate (to obtain the .apk files necessary) Only needed once, I would upload the necessary files but IBM won't like that very much.
Computer with Captivate drivers and Android SDK
The Lotus Traveler setup requires two installs which makes the process more tricky than simply doing an adb install lotusinstaller.apk, so we need a few more steps.
1. On your PC download the Lotusinstaller.apk file from your traveler server and copy it to you sdk\tools folder.
2. Plug your rooted Captivate phone into you computer with debugging mode on and use adb to issue the following command "adb install lotusinstaller.apk"
3. Open the installer application on your phone and enter the required server and authentication information for your system and click next. (this will create the server setting on the phone and download the lotustraveler.apk file to your rooted phone.) I can't remember the exact location so simply do an adb shell then "su" to gain super user rights and then do a find -name LotusTraveler.apk (or *.apk and find the lotustraveler.apk)
4. copy this file to your computer. One easy way would be to adb pull LotusTraveler.apk c:\location of sdk\tools\
Now that you have both the lotusinstaller.apk and lotustraveler.apk you will not need the rooted captivate for future phone setups.
5. Now to setup a stock Captivate. Enable usb debugging
6. adb install lotusinstaller.apk
7. launch the installer and enter the appropriate settings on the phone and click next. It will attempt to download the lotustraveler.apk and then give you an error about not being able to install applications that aren't from the market. Ignore that and close the installer.
8. now issues abd install lotustraveler.apk on your pc
You're done. The installer setup the initial server settings and the lotustraveler did the rest.
To setup more phones begin from step 5 from now on
***Disclaimer***
I wrote this up simply from memory so I'm sorry if this is not 100% accurate with the commands etc.
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
thats exactly my first thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Clienterror said:
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'll try the wonder machine first. thanks for that tip.
Your suggestion won't work as stated in my walkthrough. The initial apk downloads another apk to your phone somewhere in the system directory. Once you have both apk files it's a simple "adb install lotusinstaller.apk" then "adb install Lotustraveler.apk"
wonder machine causes the issue of not being able to install the second apk file as stated in my last post. It can replace adb install after you have both apk files on your computer.
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Ziuck said:
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Click to expand...
Click to collapse
just do
find -name LotusTraveler.apk
it will show you where the apk is located
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
hockeyfamily737 said:
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
Click to expand...
Click to collapse
Just download a file manager, (es fileexplorer, or root explorer) and install it that way. or if you have adb and all the drivers you need for it.
Put the .apk in the tools folder in the SDK
and go to it in a command prompt and type adb install titaniumbackup.apk..
Or whatever you apk is named.
if you need help, dont quote this, just send me a pm for help =]
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
kyouko said:
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
davidevan said:
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
Click to expand...
Click to collapse
Yea they are. Besides, personally I'd do it the way you mentioned; either first using a filemanager (easiest imo) or via adb install
Only reason I replied was in case there was a specific reason he'd only want to use terminal emulator and not adb or a FileMan
Edit: Oh I see what I think you're referring to, the line:
Adb commands are completely different than terminal commands.
Click to expand...
Click to collapse
That was just directly copied from a post I made before something about wanting to "adb push" with TE, it had nothing to do with your response
Sent from my Android using Tapatalk
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
btw click my thanks meter ;]
its the ony thing i have left lmao! :'(
davidevan said:
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
Click to expand...
Click to collapse
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
davidevan said:
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
Click to expand...
Click to collapse
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
hockeyfamily737 said:
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
Click to expand...
Click to collapse
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
waffle_ said:
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
Click to expand...
Click to collapse
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
"
hockeyfamily737 said:
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
Click to expand...
Click to collapse
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
laie1472 said:
"
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
Sitll no good installing ADB at work, but I did get a good ADB workout at home this weekend rooting my son's Optimus......Wholy crap!!! Revert to old software, lose the lcd display, root with rage against the cage, push recovery to the phone, revert back to current version of software, lose root, and then re-root on current software with recovery already installed, what a process that was!!!! BTW.... Terminal Emulator commands worked perfect. Mistake I was making was trying to "push" from my SD card instead of "copy".
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
Trying to be charitable and cautious, I'm trying to back up my EFS folder before I go messing around and it is consistently failing. I'm using:
SGS Tools Vz 0.5.7
Busy Box Vz1.17.2
On my previous captivate this works just fine. Now I get
"could not create backup folder /sdcard/SGSToolbox/backup (date string)" and then the bluebox saying creating backup. This never goes away and to clear I have to reboot.
Any helpful hints?
I tried to download the latest and greatest SGS Tools but Google knows I have it installed and won't let me get the newest one. Haven't figure out how to get around that unless I just have to un-install my current one.
Rooted 2.2, KB2, running existz KB1 kernel.
Knowing there are no successful backups... just successful restores.
If you're willing to use your computer and can get the Android SDK and ADB going, just get into a command prompt in the ADB directory and type "adb pull /efs". That will back it up to your computer.
Or you could open a file explorer and copy the directory from there to your sd card
You could use an app called nitrality
Sent from my SGH-I897 using XDA App
Try to update your su binary, the simpliest way is use Root Explorer to backup whatever u want
Well just to be daring, I tried to install the ADB tools. Had to install the Java development software first. After I installed what I thought was the ADB suite, I can't seem to find the place to type in commands, dumb as that sounds. I may not have gotten the right package. Going to tinker with it though.
My SU is up to date.
I can see the folder with Super Manager so I guess I'll just copy with that. Interesting though I can't see anything in the /efs directory. Probably just something else I don't understand.
Still curious though as to why SGS Tools is failing... part of my nature.
Thanks to all that replied.
Make a note of where adb is installed (e.g. c:\users\person\Android-sdk-windows\platform-tools). Then hit the windows key and R, and type cmd. Once in the prompt, type CD (directory from before, no parentheses) and hit enter. From there, type your adb commands.
Ahhhh.... I get it. Was expecting something a bit more elegant. Gotta love DOS commands.
Well..there are a couple more elegant ways to do it.
Open up a new note in NotePad, just type:
Cmd
Exit
And save, but instead of a .txt file extension save it as a .bat, now drop that into your adb directoty, then just double click on that to open a prompt in that directory, so you don't have to do the cd command every time.
Or..the most elegant way is to add adb to your environmental variables so you can enter adb commands from anywhere
That's a good solution. I've got a set of files put into my C:\Users\(my username) folder called "adb", "adbr" (adb reboot), "adbrd" (adb reboot download), and "adbrr" (adb reboot recovery).
Each of these is a .bat file with a version of this text in it:
@ echo off
cd "C:\Users\(me)\Other\tools\android-sdk-windows\platform-tools"
adb reboot
That way, all I have to do is hit Win-R and type one of those file names and it does that command for me. Or, I can type cmd, then adb, and automatically be where adb is installed without cd'ing through a long file list.
My suggestion is Root Explorer. I was able to backup the EFS directory without problems also create a .tar file.
I used root explorer to do my backups, another option is the explorer inside the rom tollbox aplication its also very good
Now I have another adb question...
First off, now I'm just trying to learn and get better. I've built my bat files and I can get adb working. Thanks to those that helped with that. When I tried to pull the /efs folder it said there was no device recognized. I was in "mass storage" mode at the time.
Whenever I've seen people talk about using adb, I don't recall anything being said about if it should be in Download, debug or what. One of those assumed knowledge things.
So what do I have to do to the phone to let adb recognize it?
gnawing on the bone....
I'm also thinking of pulling a logcat or something when SGS tools fails... just to see. That's my next step.
Enable usb debugging in settings> applications> development
SGS Toolbox doesn't work with efs backups. Are there easier ways to do the backup?
Adb or root explorer.
I did both... just to say I did it and finally got adb working.