Related
Hello.
I cooked a rom with some changes and my question is... How can I try it? I know there's a metod to emulate roms, but I want to check if the update.zip is signed correctly, so what I want is to emulate recovery or fastboot, but I can't.
Somebody knows how to do it?
Thanks.
realjumy said:
Hello.
I cooked a rom with some changes and my question is... How can I try it? I know there's a metod to emulate roms, but I want to check if the update.zip is signed correctly, so what I want is to emulate recovery or fastboot, but I can't.
Somebody knows how to do it?
Thanks.
Click to expand...
Click to collapse
should be moved to Q&A
but i have the same questions i went through everything emulator related on the android site and through the command line help functions and i got as for as creating a sysdir image and i got stuck where you do the kernel image .....
I only found this:
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
But I can't enter in bootloader or fastboot with [Home Key], [Back Key], o [Menu Key] While it's loading.
what SDK are you using (HUGE DEAL)
if your using the latest SDK have you precompiled your AVD profile (android virtual device) see http://developer.android.com/guide/developing/tools/avd.html#creating
if you have compiled your AVD and pointed your emulator at the correct AVD profile
http://developer.android.com/guide/developing/tools/emulator.html
if your booting an actual update.zip youll have to flash do a NAND dump of the phone and copy your NAND files to your pc and boot those through your emulator to ensure it runs correctly
(i only say this because i dont know if its possible to enter recovery mode straight from the emulator)
you place your system.img and your AVD stuff in the same folder
9. Copy the above file (referring to system.img{which would be the dump of your /system folder in a img format} to the location of the enhanced.avd directory ('C:\Documents and Settings\<user>\.android\enhanced.avd' on Windows XP, and 'C:\Users\<user>\.android\enhanced.avd' on Windows Vista).
10. You're ready! Type 'emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
Click to expand...
Click to collapse
::::EDIT:::::
if you did have success making an AVD or know where i can find some premade profiles for the HTC Magic/Dream lmk
:::EDIT2::::
i just gotta finish downloading my JDK and i can get it to boot
does anyone know how to compile a system.img from just my /system folder or in essence can the /system folder just be booted without having to compile it into system.img format?
Zarboz said:
does anyone know how to compile a system.img from just my /system folder or in essence can the /system folder just be booted without having to compile it into system.img format?
Click to expand...
Click to collapse
I may be dead wrong, but you can extract a .img file to the system folder contents by unyaffs-ing it, so I assume you could do the reverse...maybe.
bcrook said:
I may be dead wrong, but you can extract a .img file to the system folder contents by unyaffs-ing it, so I assume you could do the reverse...maybe.
Click to expand...
Click to collapse
im not super linux familiar... im learning as i go and reading everything i can about it
thanks for the info :thumbsup:
so you mean
su
mkyaffs /system
or
su
mkyaffs /block/devblock/mmc0blk (i think thats system idk for sure right now tho)
just checked the unyaffs google code page... says it only supports unyaffs right now not making system.img's.....
but theres links for a mkyaffs so maybe thatll do it
---checking google site sdk site for info on compiling system.imgs maybe theres a tool included---
NOPE NOTHING!
umm
i have an idea for you man
boot into your environment and then adb shell in and just try it because the whole image that you booted to should be read write
once you boot into your emulator load a sd card file with the mksdcard commands
http://developer.android.com/guide/developing/tools/othertools.html#mksdcard
then your gunna get your adb and
adb push cyanogen1.4recovery.img /sdcard
adb shell
$ su
# flash_image recovery /sdcard/cyanogen1.4recovery.img
#reboot recovery
and see if itll do it that way if it boots into recovery with the custom recovery.img sweet action your good to go grab your ADB window and
adb push (your custom rom).zip /sdcard
adb shell
#reboot recovery
then select choose update.zip to flash and choose your custom rom and in theory it should flash it to your Readwrite system.img........
someone anyone correct me if im wrong cuz im gunna have to try this when i get home
THIS IS ALL IN THEORY I HAVE NOT TESTED NOR DO I KNOW IF THIS WILL WORK JUST AN IDEA FOR YA
Zarboz said:
im not super linux familiar... im learning as i go and reading everything i can about it
thanks for the info :thumbsup:
so you mean
su
mkyaffs /system
or
su
mkyaffs /block/devblock/mmc0blk (i think thats system idk for sure right now tho)
just checked the unyaffs google code page... says it only supports unyaffs right now not making system.img's.....
but theres links for a mkyaffs so maybe thatll do it
---checking google site sdk site for info on compiling system.imgs maybe theres a tool included---
NOPE NOTHING!
umm
i have an idea for you man
boot into your environment and then adb shell in and just try it because the whole image that you booted to should be read write
once you boot into your emulator load a sd card file with the mksdcard commands
http://developer.android.com/guide/developing/tools/othertools.html#mksdcard
then your gunna get your adb and
adb push cyanogen1.4recovery.img /sdcard
adb shell
$ su
# flash_image recovery /sdcard/cyanogen1.4recovery.img
#reboot recovery
and see if itll do it that way if it boots into recovery with the custom recovery.img sweet action your good to go grab your ADB window and
adb push (your custom rom).zip /sdcard
adb shell
#reboot recovery
then select choose update.zip to flash and choose your custom rom and in theory it should flash it to your Readwrite system.img........
someone anyone correct me if im wrong cuz im gunna have to try this when i get home
THIS IS ALL IN THEORY I HAVE NOT TESTED NOR DO I KNOW IF THIS WILL WORK JUST AN IDEA FOR YA
Click to expand...
Click to collapse
I tried before, but emulator freezes when I try to reboot it. I think can install Cyanogenmod and the CMUpdater and use my own update.zip to do the update, but I think it will not work.
realjumy said:
I tried before, but emulator freezes when I try to reboot it. I think can install Cyanogenmod and the CMUpdater and use my own update.zip to do the update, but I think it will not work.
Click to expand...
Click to collapse
it doesnt work you have to nandroid the update.zip
i was up till like 4 am last night trying to compile a tattoo build and i kept getting stuck on flash at my update script where it CHMOD CHOWN system:xbin
toooo tired to care to mess with it anymore...
tried everything to get the emulator to boot my custom rom but no go
tried doing it like
emulator -sysdir c:\c\herosysimage\ -avd hero
and like
emulator -system C:\c\herosysimage\system.img -avd hero
no boot
also tried putting system.img in the avd folder
I am on fresh 1.1 but i dont like the clear lockscreen. Is there a way i can change it??
yes try looking
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Thank You thedudejdog it worked perferct
You can take the HtcLockscreen.apk out of the /system/app dir of any ROM you like to get that rom's lockscreen going.
thedudejdog said:
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Click to expand...
Click to collapse
am a newly rooted hero owner. read/re-read/followed the steps to do it on this forum and am grateful to those who lent their knowledge/expertise.
want to have the original hero lockscreen and downloaded this HtcLockScreen.apk file.
i searched online to see if i could find instructions to push this but can't seem to figure it out.
i've done the following:
- copied HtcLockScreen.apk to the root of my sd card.
- opened a command prompt
- got to "C:\android-sdk-windows\tools>"
from here am i supposed to type:
- "adb shell"
- "su"
'cause i think to push this is the command, right:
- "push /sdcard/HtcLockScreen.apk /system/app/"?
help please!
thank you.
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
I thought I saw on here a little while back that showed you how to remove just the image from the lockscreen so all you have is the grey bar. Does anyone know where that is because I thought that that was kinda cool.
thedudejdog said:
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
Click to expand...
Click to collapse
thank you! it worked...
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
iamareebjamal said:
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:-
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. 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:
SETX PATH "%PATH%;[COLOR="Indigo"]SDK_Install_Path[/COLOR]\platform-tools;[COLOR="Indigo"]SDK_Install_Path[/COLOR]\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
(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. 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
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
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
Click to expand...
Click to collapse
This should help the new members in appealing their problems in a deeper and better way.
Originally posted by iamareebjamal
Original thread here.
I bought a Moto G(XT1031) last week. I rooted it, and before removing any system apps, created a backup in TWRP of the system and boot partitions.
Now, I have the 8GB model(couldn't find a 16GB one cheap enough) and so I would like to create a .img of the system and boot partitions. I still have the TWRP backup, however I want to remove it from my phone as it's eating up almost a GB of precious space.
I've seen some assorted stuff on how to pull .img files from the phone, but I' m not sure which ones will work with mine. Any help would be appreciated!
You could use: adb pull /sdcard/TWRP c:/MotoG_Backup/TWRP
Now you can delete that folder from phone.
Then if you want to restore TWRP Backup: adb push c:/MotoG_Backup/TWRP /sdcard/TWRP/
Alternatively:
ADB Dumping Methods: *ROOT REQUIRED*
You need to grant the SuperSU permission popup that will appear on your phone.
System:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img"
adb pull /sdcard/system.img
lost101 said:
You could use: adb pull /sdcard/TWRP c:/MotoG_Backup/TWRP
Now you can delete that folder from phone.
Then if you want to restore TWRP Backup: adb push c:/MotoG_Backup/TWRP /sdcard/TWRP/
Alternatively:
ADB Dumping Methods: *ROOT REQUIRED*
You need to grant the SuperSU permission popup that will appear on your phone.
System:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img"
adb pull /sdcard/system.img
Click to expand...
Click to collapse
Why, thank you sir! I was unaware that you can push files to your device while in the recovery! That is why I wanted a system image file.
Thanks again!