I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Ok, so if you can see your phone through adb, then you are definitely on the right track. Unfortunately, I'm not really familiar with OS X anymore so I'm not quite sure how to do it. Just sit tight for now until someone who does use a Mac, or has more of a clue then I do can help you out.
But seriously, don't pull your hair out. It won't stay on your head forever ya know...
Edit: oops, just saw this is JI6 (Froyo) not JF6, so I can't help you, but here is a general overview:
from terminal inside Android sdk main directory:
tools/adb devices -> list all devices connected that ADB can see
tools/adb shell -> gets a normal user shell on your phone
tools/adb reboot recovery -> reboots into recovery mode, suitable for update.zip root method
--------------------------------
Place the root update.zip on internal sdcard.
from terminal inside Android sdk directory:
tools/adb reboot recovery
Select the update software option, and you will be done.
laxwillsch said:
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Click to expand...
Click to collapse
Start simple:
If you open a terminal on the mac, and go to your android SDK tools folder; what happens when you type ADB shell?
Or if you type any of the ADB push commands?
You need to give more detail around what you are seeing for us to help you.
Ok so if I am in terminal and i type in my /android-sdk-mac_x86/tools nothing happens and it just says /android-sdk-mac_x86/tools is a directory. But if I type the same but with /tools/abd it opens the abd command lines, like how to write code. Then when I try to "adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin"
it says "-bash: adb: command not found"
however when I type laxwillsch$ /android-sdk-mac_x86/tools/adb shell
it does give me the drop down $
but when I then try to write the next line of code "chmod 0755 rageagainstthecage-arm5.bin"
it says "chmod: rageagainstthecage-arm5.bin: No such file or directory"
I am stumped I am beginning to think i need to buy a pc as I am very interested in android development and want to learn more, but it seems all the tutorials are run assuming you are on a PC
EDIT** I have downloaded the android SDK started pack, and the 2.2 root pack and they are all in my /android-sdk-mac_x86/tools folder that is directly on my Macintosh HD for simplicity
Do you know how to change directories (cd command)?
The problem is that you are trying to work in one directory, but all your tools are in another.
So change directories to the tools directory:
cd /android-sdk-mac_x86/tools/
now run your adb commands - you may have to type ./adb to tell your mac to look in the current directory for the adb command (that is what ./ means "start here")
Also, try to understand what is happening so you can more easily troubleshoot: chmod is a command to change permissions, and you are running it on the phone. If you can't push the file to the phone, then you can change it's permisssions. I guess you never got rageagainstthecage on the phone, so there is no way to chmod it.
If you can't do this on a mac, a PC is not easier. I use both, and like both, but you need to learn basic commands first - they apply to the mac terminal and the windows cmd prompt.
Getting root means moving in and out of the phone - adb shell - puts you in a terminal on the phone. So you really need to understand cd (change directory); pwd (present working directory - shows you where you are); cp (copy); and know your current path - what the ./ does.
I hope this helps, not trying to sound condescending - maybe practice a linux terminal tutorial would help
Thanks so much, I am at school right now and cant test out all that but you are really helping me understand all this! I will post tonight and let you know how it goes. again thank you
ok so i dont have my usb cable with me but I was playing around with the commands that you suggested and ureka! i finally got to a point where it says "h70-33-65-19:tools laxwillsch$" thats a first! and when i type pwd it shows "/android-sdk-mac_x86/tools" so that means I am working out of the right directory right? and from here I enable usb debugging connect my phone then just copy and paste the codes from the thread correct?
yes, it sounds like you are on the right track. But take it nice and slow when you follow the steps. It is very important that the commands are entered exactly as you see them.
Also, one step tells you to wait for something to run and kick you out of ADB - wait just like it says - takes about 45 seconds but feels like forever.
If you are in the tools directory - just by typing "adb" no quotes will give you whole page of adb commands - if you get a "command not found", then you need to add the ./ and make it ./adb
Hope this helps and again, read the commands step by step a couple times first so you understand what is happening.
In a nutsell, you push the rage file;
change its permissions, run it;
get kicked out of ADB and then open a new ADB shell;
you are now root;
remount the system partition to give you write access when it reboots;
reboot;
push over some files;
change permissions on files you pushed;
reboot;
Some things to know - SU is a command for gaining root access; when you use SU your prompt changes (in adb shell) from $ to #
If you are succesful you should see the SuperUser app listed in your apps.
Done and Done just rooted successfully couldnt have done it without you! thanks so much
Related
I am trying to learn how to use ADB, so I can find the cause of a problem I am having on every 2.xx Rom I have tried, and I have tried them all!
So take a look at the screen shot, and you can see it finds my phone. For some reason thats as far as I have gotten, been screwing with it for 2 days but alas I have to ask!
Thanks for any help you can be!
Roman
OK, at a quick glance....
Instead of just typing "logcat", try "adb logcat". I think you'll have better luck.
Still looking through the rest, will edit in a few minutes.
EDIT 1: Don't actually put the "#" or the "$" on your command line. Those are prompts that the shell presents to you, not something you're supposed to type.
EDIT 2: Add the sdk\tools directory to your path. It will make your life much easier. You can get away with just doing a "cd" to that directory, but in the long run things will be much easier if you just put it in your path.
EDIT 3: "Operation not permitted"????? That command should have worked. Have you rooted your phone yet?
do adb "insert command here" logcat push pull install etc...
Cool thanks for the help subliminalurge, I think I got it now!
Now to start my bluetooth headphones with 1.5 and grab a log, then load up 2.1 and grab a log and see what the HELL is wrong!
Thanks again!
One last question, is it possible to save a whole string from CMD!
Also how do you do a dalvik wipe?
These are the 2 commands I have! Not sure if either one work or not!
DALVIK WIPE:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
adb reboot recovery
adb shell mount /data
adb shell rm -r /data/dalvik-cache
I havent used adb since rooting my g1, since the release of the flashrec method.
Heres my noob question
Can terminal emulator do the same things as adb?
The only thing id ever use adb for is to push/pull, and i just use root explorer for that.
Jesus, youd think i became a senior just by spamming...
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
mrinehart93 said:
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
Click to expand...
Click to collapse
Lol i see what you mean.
You need adb to theme, dont you?
Windows man, through and through
(oh the irony, of being such an android patron...)
ok... i am a little confused to what "adb" is and how to get "su" (superuser) via a Terminal app that i downloaded for my phone.
I type "su" and and I get "su: not found" same with "adb"
what am i not understanding?
trying to follow http://forum.xda-developers.com/showthread.php?t=797397 but the commands are not working..
i am a little new to my captivate here, so help me out. I install 2.2 and i would like to root it..
thanks in advance, and forgive my ignorance.
ADB is the Android Debug Bridge. You can read what it is here Android Debug Bridge
To use this you must first install the Android Software Development Kit found here Download the Android SDK
Read up a bit on those and search the forums to find more help. Good luck.
I was / am in the same boat.
I spent 4 hours last night getting it figured out, I sure wish I could find an Android for dummies book.
Anyway, here is what cha do....
once you dowload the adb package unzip it to the root of your c drive, you may want to rename it to some thing shorter, I just called it android.
next download the root package from the root thread here and unzip the files and copy or cut them into the tools folder of the ADB folder you placed on the root of C:
navigate to the tools folder and copy adb.exe and adbwinapi.dll to the system32 directory in windows, you will need to reboot. This will allow you to use the windows cmd line.
now I am on window 7 64 so I ran the commond line as administrator to be safe. to do this click start all prograns accessorires right click cmd and select run as admin.
change directory to the tools folder, for me "cd c:\android\tools"
Connect phone be sure usb debugging is on in the phone, (settings, application, development. it will install drivers. (I manually installed the samsung 64 bit drivers I had downloaded from samsung)
from the command promt type adb devices and hope fully it will see your phone and return with the serial number and them you are good to go with following the instructions to root from there.
I hope this helps...
Cappy
the information on how to use this is really not in one place, I spent 4 hours last night searching all over to figure it out, just so I would not ask and be belittled because there is NOT good information.
I have even been searching for any books I can find on Android so I can understand how this system works, but have found no good ones yet.
I need a nice Android for dummies type thing.
I spent an hour just to figure out it still won't run right unless you change directory to the tools folder where everything is at. ( it's been like 15 years since I messed with dos).
Some where in the wiki or bibles or all the other how toos being posted we really need better information on how to use the tools and what they are.
Cheers
Jeff
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=android+for+dummies
WOOT looks like they have one now...
Quick Tip: Once you get the Android SDK installed, you can add the location of the Tools directory to the Windows path variable and be able to call the programs from anywhere on your computer.
Masacrk said:
Cappy
the information on how to use this is really not in one place, I spent 4 hours last night searching all over to figure it out, just so I would not ask and be belittled because there is NOT good information.
Click to expand...
Click to collapse
Sorry you feel I was trying to belittle you. I was trying to be helpful by pointing you to the proper information. You know the old saying, "You'll never learn by letting others do it for you."
Sent from my SAMSUNG-SGH-I897 using XDA App
it's all good man I did not mean you.
I was taught along time ago that there are no dumb questions but it don't seem to hold true around here I have noticed.
Quess the new generation are not as patient or willing to help as mine was.
Ha ha ha. Guess I should have picked a better screen name.
Sent from my SAMSUNG-SGH-I897 using XDA App
ugg.. I dont get it.. I finaly got it to connect to the phone, but even in windows when i type in SU I get invalid command..
uggg..
i dont get it.. please help!
go to this thread
http://forum.xda-developers.com/showthread.php?t=797397
at the bottom of the first post you will see a link to Captivate2.2rootpack.zip.
http://forum.xda-developers.com/attachment.php?attachmentid=411708&d=1285997559
download , unzip, copy contents to the tools folder of the sdk package.
Also this thread was a help,
http://forum.xda-developers.com/showthread.php?t=502010
Cheers
Jeff
Masacrk said:
go to this thread
http://forum.xda-developers.com/showthread.php?t=797397
at the bottom of the first post you will see a link to Captivate2.2rootpack.zip.
http://forum.xda-developers.com/attachment.php?attachmentid=411708&d=1285997559
download , unzip, copy contents to the tools folder of the sdk package.
Also this thread was a help,
http://forum.xda-developers.com/showthread.php?t=502010
Cheers
Jeff
Click to expand...
Click to collapse
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
eatonjb said:
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
Click to expand...
Click to collapse
OK. took me a little while to figure this out, too. Not sure of your level of knowledge of the terminal. If I over-simplified please forgive me.
"Extract RootPack zip file" Did you do this? I think you did from you post. Make sure you've copied the files to your "tools" subfolder in the android sdk folder.
Click the start button, click run, type "cmd", press enter.
When that window opens type "cd.." and press Enter. Keep typing "cd.." and pressing Enter until the only thing you see at the prompt is "c:\"
Now navigate to the Tools folder where ever it is you put the android sdk.
I put mine at "c:\android_sdk" so I would type "cd c:\android_sdk\tools"
Plug your phone into your computer.
Go to home screen>menu>settings>applications>development and select "USB debugging".
At the command prompt type "adb devices" and your phone should return a value (the serial number).
If that works you should be able to follow the directions below.
It's been mention that you should be able to copy the commands from the web page and right click the terminal window and select "Paste". Makes everything faster, easier and more accurate. One other thing to mention: after you perform these steps and you want to do something else through adb where you're instructed to type "su" you'll need to open the SuperUser application on your phone and press "approve" after typing "su".
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb shell
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
reboot
eatonjb said:
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
Click to expand...
Click to collapse
those arent even commands. just random words you put into the terminal....
follow the instructions exactly like PersonOfKnownOrigin has posted. it works
I too was having trouble, turns out the files were extracted and were in a sub folder in the Tools folder so I copied and pasted them directly into the tools folder one by one, that worked great for me. Also, I find it easier to open command shell and use the Android Tools by holding the shift key and right clicking on the Tools folder and choose open command window here. I hope this helps.
I have a stupid path becaue my laptop messed up when I first got it and I haven't been able to fix it because DOS is difficult to me. It works fine but I am too lazy to type such a long path and if you are off at all it dosen't work.
just copy and paste the commands so you don't get them wrong, worked for me. The command is su then hit enter then enter the next command line and hit enter, works like a charm.
ok, I got it.. I misinturpted that the first line (the 3 commands in one line) was a command that I was supposed to run..
it was not..
dohh.. thanks guys for all the help... i felt kinda dumb, but now I think I am kinda smrt. I mean Smart!! (Simpsons Humor)
thanks again for the paitence.
Eaton
not sure if anyone has seen this but i found it posted in another forum dated june 8 (retail launch date) and no one has commented. i dont know enough to try this out my self but looks promising.
Galaxy Tab Rooting Instructions - ADB Method
These instructions provided me with a permanent root workaround when SuperOneClick, run within Windows 7, repeatedly hung "waiting for device". SuperOneClick elegantly automates the ADB method, but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
The procedure below uses components from SuperOneClick but runs the ADB server and commands from within Linux. In this environment the ADB command "adb devices" correctly reports the attached Galaxy Tab, and other ADB commands work correctly as well. To obtain the needed SuperOneClick components, download SuperOneClickv1.9.1.zip to Linux and unzip it there. The SuperOneClick.exe (which is a Windows executable) will be ignored, but other files (see below) will be pushed to the Galaxy Tab during the rooting process.
I'm indebted to authors at http://pastebin.com/i234U96k and http://rootingdroid.com/ for the hack below. Note that there is a modification to require no dependence on a "cp" command at the ADB shell prompt. For some reason "cp" is missing in /system/bin on my Galaxy Tab.
As always, attempt using this procedure at your own risk. Be specifically aware that you may not be able to "unroot" your Galaxy Tab after using this procedure--ever! This procedure doesn't back anything up from the unrooted device, so if "unrooting" it requires restoring something from such a backup, I'm (and you're) stuck with a permanently rooted device. This condition may interfere with your receiving certain updates or downloading DRM content in the future.
1) Download and install TitaniumBackup and SuperUser onto your Galaxy Tab from the Android Market. Note that SuperUser may not be necessary since there are sources for this app below. I'm including it at this step because I had previously installed it prior to the steps below.
2) Download and unzip SuperOneClickv1.9.1 into some Linux folder of your choice. You can get it at http://shortfuse.org/?page_id=2 near the bottom of the page.
3) Install Android SDK for Linux x86 into your home directory on your Linux box. You can get it at http://developer.and.../sdk/index.html The ADB server will be located in ~/android-sdk-linux_x86/platform-tools.
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
Note that there is an alternative source for Superuser.apk and su at http://www.rootingdroid.com at the "Download" link in Step 2.
5) Enter the Linux directory containing the ADB server with the command
cd ~/android-sdk-linux_x86/platform-tools
6) Plug in the Galaxy Tab to the computer, with USB debugging turned on.
7) Test ADB recognition of the Galaxy Tab with the command
./adb devices
You should see messages indicating the ADB server is starting, and then a message similar to
List of devices attached
100020497aab device
If no device is listed, begin investigating by ensuring that USB debugging is turned on. In my experience, when the "adb devices" command is entered from within Windows 7, no device is listed. Again, I think this is related to the "waiting for device" hang when SuperOneClick is run in Windows 7.
8) Push psneuter to the Galaxy Tab with the command
./adb push psneuter /data/local/tmp
9) Make psneuter executable with the command
./adb shell chmod 777 /data/local/tmp/psneuter
10) Run the psneuter exploit with the command
./adb shell /data/local/tmp/psneuter
The message "property service neutered." should appear indicating success.
11) Test for successful rooting with the command
./adb shell
The # prompt should result.
12) Remount the /system volume rw (by default it's ro), so that files can be pushed to /system, with the command
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
13) Return to the Linux computer command line with the command
exit
14) Push Superuser.apk, su and busybox to the /system volume with the commands
./adb push Superuser.apk /system/app/Superuser.apk
./adb push su /system/bin/su
./adb push busybox /system/bin/busybox
15) Make su executable with the command
chmod 4755 /system/bin/su
16) Remount the /system volume as ro with the command
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
17) Verify that su works with the command
su
You should see the # prompt; type the command
exit
and you should see the # prompt again.
18) Power the Tab down and then power it back up. Run TitaniumBackup, which will ask for root privileges that (hopefully) will be granted. It's a good idea to backup your Galaxy Tab before using your new root privileges!
i take no credit for this. all credit to feral urchin for which ever device this works for retail or I/0 but something tells me its for retail because I/o has had an easier way to root for a while..
I am running windows vista ultimate. Should I try this and see if I have the same bug that has been reported for Windows 7?
I have a new Tab 10.1 Retail picked up today.
give it a try let us know the results please
dsh897 said:
but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
Click to expand...
Click to collapse
This might work. I am running Vista Ultimate x64 and my adb does recognize my retail Tab 10.1. See image below.
Now when I execute the command on step 10 I receive this error. . .
"Failed to set prot mask <Inappropriate ioctl for device>"
Suggestions?
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
dsh897 said:
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
Click to expand...
Click to collapse
Yes I copied all those files to the correct directory. Only on my windows machine the it is /android-sdk/platform-tools/
I am a firefighter in the Charlotte, NC area. Just got off tour this morning.
Google searching that error as I type. I'll let you know the progress.
dsh897 said:
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
Click to expand...
Click to collapse
I would like a backup image to odin if needed as well. How do I do this. I have a slight idea but i don't know the directories to pull?
i just disconnected my odin during dump im screwed at the mobile phone and computer! dunno how to get out
trying both volume rockers now. days downloading and flashing android box
just hold the power button for 10 seconds or just goto recovery mode and select reboot
that should get you back to honeycomb.
yea i got it with the power up then the recovery mode thx
How did you get adb to dump. i am running all sorts of commands and nothing works. some help would be greatly appreciated.
i was using odin3 to dump but it doesnt seem to be working correctly i think because its still locked. my next step is to flash the I/0 bootloader / system but im nervous now after it not correctly dumping (failure to write) it just creates a dummy file.
I am at work i will have to play with at home more. and have more resources
I am at an standstill as well. I don't know much more then what I have done thus far. I admittedly know nothing about Linux user privileges so I was never a help to begin with. The image below speaks for itself.
have you been able to flash anything with odin? i think if we can flash the stock i/o bootloader were set
Nope. Dont you think thats a little balzy without a retail dump to fall back on? Although, i could just exchange the device with best buy if something happens...
Sent from my GT-P7510 using XDA Premium App
haha why i havent done it yet. i cant see to get adb to recognize my tablet anymore i was making progress until now
is this method working ok to root a new retail SGT 10.1? thanks
i tried it and this what i got
"Failed to set prot mask (Inappropriate ioctl for device)"
any suggestions, thanks
neonflx said:
is this method working ok to root a new retail SGT 10.1? thanks
Click to expand...
Click to collapse
Nope. I am stuck. He is stuck. We are stuck.
any other methods to root a retail SGT, i took my XOOM back to Cotsco already
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.
ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
[COLOR=Black]SETX PATH "%PATH%;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\platform-tools;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\android-sdk-windows\tools" -m[/COLOR]
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. However, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped​
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
Reserved
Reserved Once More
Last One
Reserve the guide
install full rom
how to install a full rom from adb?
Pretty sure it's impossible. Sorry.
Sent from my E15i using XDA Premium App
Perfect Guide to use ADB Commands..
It is very clear and perfect guide to use ADB commands.. I tested this all and works fine..
You can use apks to do logcats from the phone too, I use catlog.
About Broadcom being open sourced made me laugh hahaha.
open source broadcomm, i see what you did there .
Updated OP
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Android-fany said:
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Click to expand...
Click to collapse
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
iamareebjamal said:
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
Click to expand...
Click to collapse
I already reinstalled it like 5 times. Still doesn't work.
Android-fany said:
I already reinstalled it like 5 times. Still doesn't work.
Click to expand...
Click to collapse
Which Windows?
Which ROM?
iamareebjamal said:
Which Windows?
Which ROM?
Click to expand...
Click to collapse
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Android-fany said:
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Click to expand...
Click to collapse
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
AW: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
iamareebjamal said:
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
Click to expand...
Click to collapse
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Android-fany said:
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Click to expand...
Click to collapse
Very strange
Download My Phone Explorer and check if its working!!
Its just 2mb-6mb