Related
Hi,
i have recently bought an HTC desire Z (G2) device, and downloaded a 163MB .zip rom. what do i have to do to install it??
i searched every where and could not find an answer!!
thanks
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Razorless said:
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Click to expand...
Click to collapse
Flash the ROM via recovery. I realize that's vague but you need clockworkmod recovery and to do that you need to have s-off. And to get s-off is a whole new thing all together because you need perm root
To root it, s-off it and rom flash it, you have to be willing to accept the consequences if you don't read enough and if you make a mistake!
And, that's the key, read everything and keep reading until it makes sense to you. Then follow the instructions to the "T" make sure you know your builds and then it's a leap off faith.......if you don't understand something, ask a question or two. There is all the info that you need right in the threads. Good luck and don't be in a hurry . Happy New Year.
thanks all, i really appreciate your fast response.
actually i just want to enable arabic support on my htc desire z, and i downloaded the arabic files from
http://ardoid.com/?p=189
and installed visionary and done the perm root with su permissions and get a # after typing su in terminal
i copied the zip files to the sd, rebooted and selected recovery, then applied update.zip, the phone rebooted but without any success of arabizing.
my kernel is 2.6.32.21-gd2764ed older according to wiki
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
my question is, do i need to s off to get the files installed? do i have to remove visionary as a second step with removing rooting?
the status is that my phone has permaroot, and what i understood is that i am a step away from s off using gfree, i downloaded the file to my mac, and copied to the sd card.
i have super user
su
#
i have understood adb, and terminal, and copied the script but resulted with errors, script used
cd /data/local
chmod 777 gfree
./gfree
sync
error result on phone after chmod 777 gfree
unable to chmod gfree:no such file or directory
#
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
again, i would appreciate your efforts, since this thread is closed;
http://forum.xda-developers.com/showthread.php?t=857390&page=15
Microzift said:
i have understood adb, and terminal, and copied the script but resulted with errors, script used
Click to expand...
Click to collapse
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Microzift said:
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
Click to expand...
Click to collapse
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
ianmcquinn said:
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
Click to expand...
Click to collapse
thanks for your reply, i checked the thread and more questions!
actually i am confused, i do the steps without getting the point of it, i installed astro, visionary 14, terminal emulator on phone, and adb on mac.
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
its also not easy to understand astro, can it copy files from sd to internal memory?
do i have to drag adb to terminal every time for adb to run?
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
please let me know if i have misunderstood anything or if i am on the wrong track to s off.
i apologize for the long questions,
thanks again
Microzift said:
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
Click to expand...
Click to collapse
ADB stands for Android Debug Bridge. It allows you to do a number of functions to your phone from your computer. The most common commands are push and pull (copies files on your computer to/from your phone) and shell (starts a shell terminal on your phone---basically the exact same as running the Terminal app on your phone, only you can type all of your commands on your computer instead). It also allows you to do things like install APKs stored on your computer directly to your phone and viewing log files.
Microzift said:
its also not easy to understand astro, can it copy files from sd to internal memory?
Click to expand...
Click to collapse
Astro is simply a file manager for your phone. It allows you to do basic file management (copy, move, delete, create new directories, etc.). Some directories are read-only by default however (rooting the phone will allow you to, among other things, mount these directories as read-write---once rooted, Root Explorer is a popular file manager like Astro that will allow you to manipulate these directories).
Microzift said:
do i have to drag adb to terminal every time for adb to run?
Click to expand...
Click to collapse
No, this is not ADB should be used (it is a command line tool). Check out the various guides on setting up/using ADB.
Microzift said:
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
Click to expand...
Click to collapse
See my next post for instructions on rooting without using ADB.
Permanent Root without using ADB
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
ianmcquinn said:
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
Click to expand...
Click to collapse
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Microzift said:
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Click to expand...
Click to collapse
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
steviewevie said:
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
Click to expand...
Click to collapse
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Microzift said:
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Click to expand...
Click to collapse
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
steviewevie said:
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
Click to expand...
Click to collapse
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Microzift said:
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
Click to expand...
Click to collapse
Do not keep them in separate folders on the SD card. The files need to be on the root of the SD card in order for the commands I gave you to work.
Microzift said:
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Click to expand...
Click to collapse
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
steviewevie said:
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
Click to expand...
Click to collapse
i have disconnected the usb from my pc, and still get the same message.
this is my understanding; mount sd on pc; means i can access the sd as a hard disk via the phones usb cable on my mac desktop.
unmounting; means i gain access of the sd on my phone only?
i found an option on phone, unmount sd card, should i do this every time i use terminal? i think this is for to unplug the sd card from the phone.
how can i get the sd mounted on my phone? i can see the same files via astro on my phone.
i still receive /sdcard
thanks guys, i just rebooted
my desire z is S OFF now.
and installed the recovery
thanks for all of your efforts
These instructions are not solely my own and are adapted from miloj’s Windows based instructions found here:
http://developer.android.com/sdk/installing.html
Thank you miloj for the instructions!
This guide is intended to help noobs with rooting their TF300T device with a Mac. I am probably a half step above noob, so please don’t expect perfection.
Read this these instructions straight through, maybe even a couple of times before you begin to make sure you fully understand what you are doing.
I am not responsible for any bricked devices, malfunctions, etc. and most likely will not be able to problem solve much for you. Hopefully, the real geniuses here on XDA will jump in should you need extra help.
First off, make sure you have Android SDK and ADB installed. Follow these instructions skipping the Eclipse installation step (unless you plan on developing apps and such):
http://developer.android.com/sdk/installing.html
Save these files wherever makes sense to you and once done open up the folder containing adb in file explorer and leave open. This should be in the SDK>platform-tools folder.
Now for miloj’s instructions with some Mac specific extras and for sake of ease:
Download the debugfs and su binary files provided by miloj first from here:
http://db.tt/FBUNeVmo
Again, save these files where it makes sense to you and then open up the containing folder in file explorer and leave open.
Make sure “usb debugging” is turned on on your Asus TF300T by going to Settings>Developer options and check the USB debugging options.
Make sure you device is plugged into your Mac via usb cable. Now find out if our Mac recognizes your device.
Open up terminal from your utilities.
Organize your Terminal and folder containing adb on your workspace so you can easily access both. Click, hold, and drag the adp icon and drop it into the Terminal window. This will allow you to you immediately move into the adb command without having to type in the complete destination. Your line should end with “…/adb” now type in the command devices and hit return/enter.
NOTE – from here on out assume after every command you hit “return” or “enter”
It will look something like this:
Code:
…adb devices
the response should read:
List of devices attached
{serial number} devices
If nothing is listed, then you either didn’t activate USB debugging or your adb isn’t up to date, start again from the top.
If it showed your device, then lets move forward.
Now we have to push over the debugfs file and the su file (superuser). Make sure you can see Terminal and both open file explorer windows listed above all visible on your workspace.
Again, click, hold, drag the adb into Terminal and then complete the following commands by typing the command (in this case “push”) in between adb and the proper file and then typing in the location you want it pushed to on the device: (*note: dragging and dropping the “debugfs”file where it says “debugfs” – your file destination path name will be shown, not just debugfs)
Code:
adb push debugfs /data/local/
In the command above you would drag into Terminal the adb file then type push, drag in the debugfs file then type in “/data/local/” all with spaces in between. Every time you read in a “Code” section “adb” you are going to follow this procedure with the adb icon/file. Now, rinse and repeat moving forward.
Then this command (dragging and dropping the “su”file where it says “su” – your file destination path name will be shown, not just su)
Code:
adb push su /data/local/
now you have debugfs and su on your device.
You now have to have Terminal take control and run commands in your device by using this command:
Code:
adb shell
once in you will have a line starting with a “$” and you type in the following commands to gain root access: (type them exactly as written)
Code:
cd /data/local/
mv tmp tmp.back
ln -s /dev/block/mmcblk0p1 tmp
exit
The “exit” takes you back into your Mac, now reboot your device through adb:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN!
Now get back into the device:
Code:
adb shell
Continue with the following commands after the “$” symbol:
Code:
cd /data/local
toolbox chmod 755 /data/local/debugfs
/data/local/debugfs -w /data/local/tmp
Now you’re going to run the debugfs files. Make sure you are writing these all in EXACTLY as written. All lines preceeded by “debugfs:” you will type in the following:
Code:
cd xbin
rm su
write /data/local/su su
set_inode_field su mode 0106755
set_inode_field su uid 0
set_inode_field su gid 0
quit
Now, back in to lines starting with “$” and run these:
Code:
rm /data/local/tmp
mv /data/local/tmp.back /data/local/tmp
exit
Now reboot:
Code:
adb reboot
WAIT UNTIL THE TF300T HAS BOOTED UP AGAIN
You are rooted! Congratulations!
Let’s double check and do some clean up:
Code:
adb shell
From the line “$” type these commands for double check:
Code:
/system/xbin/su
Now the line is a hash tag “#” and type
Code:
id
The Terminal response should read something like this:
id=0 (root) gid=0 (root) … and so forth
Clean up:
Code:
rm /data/local/su
rm /data/local/debugfs
Done with Terminal.
Now, open up the Play store and download the Superuser app immediately. Once it is installed, open the app and go into the settings. Under the heading “GENERAL” Tap the “Su binary v…” to check for updates and update the app.
You are now rooted, you have Superuser control.
Let me know how this works for you!!!
Credits: wolf849 for exploit, and miloj for commands.
Good stuf, just wait firsts feedbacks about this process :good:
Inserted in the Index for TF 300t
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
ngocdao said:
Guess i'm the only person who either owns a Mac here or has tried this but...
First time Terminal user and first time ASUS owner. Was a bit iffy doing it. Read through the TF300 board for weeks and was scared as sh#t to mess with this but...
it works!! Thank you so much. :good:
Click to expand...
Click to collapse
I'm glad it was easy for you! I am not a pro Terminal user by any stretch of the imagination! I am a first time ASUS owner as well, and have only rooted 2 phones and worked on rooting another (the phone ended up being software updated via Verizon to the point of unrootable that I could find or figure out). I am a Mac user and do not have easy access to a Windows PC and figured there were plenty of other Mac users noob to rooting. Apparently, that lists is you and me!!!
Thanks for the feedback, though! Congrats on your root!!
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
dirator said:
...too dificult for me,
Thanks.
Enviado desde mi ASUS Transformer Pad TF300T usando Tapatalk 2
Click to expand...
Click to collapse
It sounds intimidating, I know, trust me when I say this is rather easy! The first time I rooted my phone I was quite worried! I read the instructions a few times and took my time though and it was really quite easy! Read the instructions a few times and you'll be alright. If you start to have trouble come back here or to this thread http://forum.xda-developers.com/showthread.php?t=1704209 and ask for answers.
not working as expected
Sorry to bother you with noob's problems.
I think I unlocked my TF300T ww Jelly Bean 4.2.1 allright.
I moved debugfs and su and other files to /data/local/ through bluetooth 'cause I wasn't able to do it in any other way.
The process worked fine up to here:
mv tmp tmp.back
Then I got this message:
[email protected]:/data/local $ mv tmp tmp.back
failed on 'tmp' - Permission denied
also, when pressing Power + Vol Down and then Vol Up to choose RCK it just dies (lying android with red triangle)
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 reooting and rebooting in recovery ode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
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
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
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. Howeve, 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
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
Forgot next ones, will write later
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
My Uncle: For gifting me this Phone
My Teachers: For teaching me English(I would not be here without them)
You: For future Thanks
Till now, thats it, will add some more things later
If any problem, I will add it too
Suggestion? They are welcome
Doesn't it belong to General section???
great work, now i know how to make a logcat. hehehehe. tnx a lot.
Ganesh A said:
Doesn't it belong to General section???
Click to expand...
Click to collapse
Well if you say so
I will request a mod to move it
But I have seen several threads (even stickies) that are guides just about logcat
And my guide features it all
Well I will not argue and request a mod if you insist
Keep it in this section
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 reooting and rebooting in recovery ode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
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
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
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. Howeve, 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
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 system /system/
Miscellanous commands:-
su: Initiates root request
du: Shows files, folders and size
date: Shows todays date
surfaceflinger: Shows your bootanimation (Tested on GB)
grep: Used to search through text files
chmod: Sets permission to files
sh: Initiates shell mode
echo: Displays the text you wrote with the command. Analogous to PRINT command on QBasic
Forgot next ones, will write later
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
My Uncle: For gifting me this Phone
My Teachers: For teaching me English(I would not be here without them)
You: For future Thanks
Till now, thats it, will add some more things later
If any problem, I will add it too
Suggestion? They are welcome
Nice thread , every thing is very clearly stated.
Thx, Nice guide.
I suggest to change the 'remount' command in:
mount -o remount,rw /system
As the effect is the same and it works universally (at least, should)
Sent from my GT-5660 using xda app-developers app
ItachiSama said:
I suggest to change the 'remount' command in:
mount -o remount,rw /system
As the effect is the same and it works universally (at least, should)
Sent from my GT-5660 using xda app-developers app
Click to expand...
Click to collapse
I use the command you mentioned every time. Thanks for reminding. I can't remember why I wrote that command there!
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 reooting and rebooting in recovery ode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
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.)
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:
SETX PATH "%PATH%;SDK_Install_Path\platform-tools;SDK_Install_Path\android-sdk-windows\tools" -m
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
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. Howeve, 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
Forgot next ones, will write later
All credits go to
iamareebjamal
For writing this up.