Database Develop

Changing fonts on a rooted phone

Hi,
I need help updating the fonts on my rooted Incredible. The way I understand it, all that needs to be done is to replace the font(s) in /system/fonts with something else. Easier said than done...
I opened an SU shell via "adb shell", and then tried to remount the /system in "rw" mode, I also updated the permissions for the font files so that I can override them. So good so far...
But when I try to copy or replace the files, I run into all kinds of problems:
* First of all, the rooted phone doesn't have "cp" so I can't do the usual copy operations like a regular *nix machine (did I miss something during the root process).
* Then I saw examples of using the "cat" command to replace the old files, but that resulted in "write: No space left on device" error, which I think has to do with how the memory image is loaded/packed??
* Then I saw examples of using the "dd" command, to copy the new files over the old files. This went further, since I can see the new timestamp when using "ls -l /system/fonts". However, when I reboot the phone, the old fonts show back again.
* I also saw an example in another thread titled "Hebrew support" in this forum (sorry, don't know how to cross-post URLs), but I didn't know how to follow the instructions there.
I would really appreciate it if someone can help me out.
- how can I update the system image? (do I really need a signed ZIP file?)
- is it too late for me to add "cp" to my rooted phone?
- the 10 minutes rooting video had us copy the "busybox" file to the sdcard, but it didn't say what to do with it. can I use it as a replacement for "cp"? (do I have to go back to "adb recovery"?)

You can only modify /system while in clockwork recovery after you're rooted and have run the unrevoked recovery flash tool

Yea, you have to push them to the phone in clockwork recovery.
you can put them in your tools folder where adb is located or put them on your SDcard and push them from there.
I attached the fonts I used. I used these on my Moto Droid I used to have and now they are on my dInc. This font is not as bold as the stock font and a little smaller. This font i believe is the "Droid" font. It looks pretty nice, see my screenshot and look under icons and at the clock and then compare to your phone.
Here is the commands you would do at command prompt, not from ADB shell.
For these commands to work, you have to place the fonts in your tools folder where ADB is.
Code:
adb push Clockopia.ttf /system/fonts/
adb push DroidSans.ttf /system/fonts/
adb push DroidSans-Bold.ttf /system/fonts/
adb push DroidSansFallback.ttf /system/fonts/
adb push DroidSansMono.ttf /system/fonts/
adb push DroidSerif-Bold.ttf /system/fonts/
adb push DroidSerif-BoldItalic.ttf /system/fonts/
adb push DroidSerif-Italic.ttf /system/fonts/
adb push DroidSerif-Regular.ttf /system/fonts/
you might be able to try this command
adb push *.ttf /system/fonts/
Im not sure if that would work or not, maybe someone else could confirm.

Thank a lot for the reply...
So is this the correct thread that I should follow now: "Unrevoked team: Recovery reflash tool (updated!)" to install the "clockwork recovery"? I am assuming this will allow the phone to start recovery with adbd running, so that I can connect to it from my PC while in recovery. Correct?
It took me forever to get the adbd running in recovery as part of rooting my phone, and I am not sure that I can replicate these steps again (at least not easily). I was this close to copying the font files while in "adb recovery" mode, but then I chickened out, because I didn't want to risk the rooting process by doing something that doesn't match the root instructions.

yes, as long as you have actually gained root and have the superuser/busybox properly installed. just follow that thread and you'll have new fonts in no time, and I can assure you that it will work because I changed mine too.

If using clockword recovery, dont forget to mount system.

Put them all in a folder named fonts. Put the folder in tools. Boot into recovery, mount system. Then: adb push fonts /system/fonts. Unmount system then reboot.
Sent from my ADR6300 using XDA App

TNS201 said:
Yea, you have to push them to the phone in clockwork recovery.
you can put them in your tools folder where adb is located or put them on your SDcard and push them from there.
I attached the fonts I used. I used these on my Moto Droid I used to have and now they are on my dInc. This font is not as bold as the stock font and a little smaller. This font i believe is the "Droid" font. It looks pretty nice, see my screenshot and look under icons and at the clock and then compare to your phone.
Here is the commands you would do at command prompt, not from ADB shell.
For these commands to work, you have to place the fonts in your tools folder where ADB is.
Code:
adb push Clockopia.ttf /system/fonts/
adb push DroidSans.ttf /system/fonts/
adb push DroidSans-Bold.ttf /system/fonts/
adb push DroidSansFallback.ttf /system/fonts/
adb push DroidSansMono.ttf /system/fonts/
adb push DroidSerif-Bold.ttf /system/fonts/
adb push DroidSerif-BoldItalic.ttf /system/fonts/
adb push DroidSerif-Italic.ttf /system/fonts/
adb push DroidSerif-Regular.ttf /system/fonts/
you might be able to try this command
adb push *.ttf /system/fonts/
Im not sure if that would work or not, maybe someone else could confirm.
Click to expand...
Click to collapse
Where can I get/download these font files?
EDIT im a retard and didnt see the .zip sorry

so where can i go to download other font types?

Perhaps this is an obvious questions to some... Can I use any TTF font? I have a font I created that is my own handwriting. This would be pretty cool to have available in my Phone... It is a standard TTF font.
Possible? I tried to search but didn't see anything specifically mentioned if a font has to be a specific type or if I can use anything.
Thanks!

compnird said:
Perhaps this is an obvious questions to some... Can I use any TTF font? I have a font I created that is my own handwriting. This would be pretty cool to have available in my Phone... It is a standard TTF font.
Possible? I tried to search but didn't see anything specifically mentioned if a font has to be a specific type or if I can use anything.
Thanks!
Click to expand...
Click to collapse
it should work fine, you just need to rename the file to DroidSans.ttf and DroidSans-Bold.ttf and replace the ones that are in /system/fonts

Thanks for the help seanhassars and TNS201: I am using the ClockworksMod recovery, and I was able to update the fonts (using the "update from ZIP" option).
I can see Arabic letters, but unfortunately, they don't look correct (they are disjoined, when they actually should be connected together). Now I am looking around for patched libwebcore.so to fix this issue, and thanks to nandroid backup, I can experiment with changing the libraries as much as I can.

shamidude can you please let me know which fonts you used? I am desperately needing to install arabic on my phone and could use the help. If possible could you upload the proper ones? Also which libwebcore.so did you use?
I tried to install Arabic fonts from another website but my phone froze on the splash screen and wouldn't boot. Please let me know what works for you, especially if you get the reshaper working.
edit- also if you could post general instructions of what you did to push the fonts onto the phone, how you mounted/dismounted, etc would be good

I don't think that was supposed to be an update.zip he just zipped the fonts he's using for easier access, you still have to push them manually.

[MOD] Stock lockscreen

Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are. EDIT: Unzip the file then push the one inside of the zip.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
If you want to go back to your old lockscreen download the enable_glass_lock.zip, unzip it, and push the enable_glass_lock to /data/local
If your signature is different it will get stuck on the samsung, you can then restore your backup.
and if you want it then run these instructions:
You need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.

You are the ****ing man!

How well does this work with the alarm silencing and incoming calls? Thanks!!!
EDIT: Never mind...testing it out.

wasupwithuman said:
Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
Click to expand...
Click to collapse
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!

taypotts said:
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!
Click to expand...
Click to collapse
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.

wasupwithuman said:
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.
Click to expand...
Click to collapse
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?

taypotts said:
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?
Click to expand...
Click to collapse
yep, unzip first...

Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.

frostman89 said:
Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.
Click to expand...
Click to collapse
Your more then welcome to use it, but It does not give an option. So you would have to create a seperate theme for people who would just want the stock lockscreen.

I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App

tiger4life said:
I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App
Click to expand...
Click to collapse
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.

hey man, i'm new to all this i've done all that u said, but what is the command to pull the android.policy.odex from the phone? I think i'm putting the wrong directory in the command because I keep getting "remote object '......android.policy.odex' does not exist" thanks for this, btw i really dislike that puzzle piece unlock bs.
nevermind, I wasn't in cwm when doing it the first time. Thanks again.

I like this, can't wait to try it.

wasupwithuman said:
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.
Click to expand...
Click to collapse
That did the trick. Thanks for the help!

Sweet, put that file in the xultimate and deodex'ed and got it working.. Thanks

Followed step by step from adb, and got stuck with the Samsung screen.

DUNC4N said:
Followed step by step from adb, and got stuck with the Samsung screen.
Click to expand...
Click to collapse
hmm... you used the file i attached and did eveything in adb? try again, i'd like to help more, but if you did everything step by idk...
You did it in cwm recovery right?

Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App

DUNC4N said:
Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
not sure about the silent slide....i don't use this lockscreen. i just made it for you guys... and yes follow the last two steps exactly how i have them.

Silent mode is functional.

How: can I mod the stock phone.app?

Ok, I must have posted this question somewhere but I would like to know the answer cause no one has answered it. "how do I get the stock phone app to modify?. How would I get it and put it back into my phone? please I would like to know.
38 views and no response?

the .png files for the phone are actually in the contacts.apk.
Are you asking how to modify the apk, or just specifically where are the phone images?

To copy the app from your phone just do: adb pull /system/app/Phone.apk
That will put a copy of the file in your "tools" directory in the android sdk folder
Then when you want to put it back on you should be able to overwrite it with: adb push /system/app/Phone.apk
What exactly are you planning on doing with this file?

Thank you. I want to create my own images to make it look different then the stock colors.

There are 2 apks that contain dialers, one is the Contacts.apk as stated bfore that brings up the phone when the phone icon is pressed the second is in the Phone.apk appears once a call is placed, and the persons picture appears of the person you are calling.

I don't know how to do a adb pull. can you explain?

johnny quest said:
I don't know how to do a adb pull. can you explain?
Click to expand...
Click to collapse
In terminal or command prompt, navigate to the tools directory in the android SDK and run the following commands:
Code:
adb remount
adb pull /system/app/Phone.apk
That will dump the file in you tools directory.
If you are having trouble with this, let me know what operating system you are using and if you have the android SDK installed.

synesthete said:
In terminal or command prompt, navigate to the tools directory in the android SDK and run the following commands:
Code:
adb remount
adb pull /system/app/Phone.apk
That will dump the file in you tools directory.
If you are having trouble with this, let me know what operating system you are using and if you have the android SDK installed.
Click to expand...
Click to collapse
This is confusing. I didn't think it would be so hard. I do UI's for iphone and ipod touch and this is way different. There are so many different things. Its discouraging in some ways. Sorry. I would love to create an app but of course its different. So, I stick to creating themes.
I would love to take a ROM and mod it myself or even modifying Launcher pro but it has that 9.pngs which makes it hard.
Ok, I have the Eris 2.1 rooted with Tenzo Rcmix2.0 installed. I have the SDK installed but don't know what to do with it. I appreciate you taking the time to help me out. I really want to create and mod lots of apps.

this is what I've done to a phone app I downloaded from the market:
-I created my images through Photoshop and saved them to a folder with its correct name used.
-I opened draw9patch and saved the images with the correct name again to a folder.
-I named the folder drawable-hdpi that belongs in the Res folder
-took the files and folder and created a zip out of it.
-opened the AvaboxV2 and signed it.
-loaded to my phone and changed the name to the correct name and installed it
but it keeps saying application not install, I just don't get it. What step did I messed up on?
Anybody? anybody?...............................

This is what you need to do:
1. Open Contacts.apk in 7-zip
2. Copy the images over top of the original images in drawable, drawable-mdpi, and drawable-mdpi-finger (notice I didn't say anything about hdpi)
3. Close the archive.
4. Copy it back onto the device with:
Code:
adb remount
adb push Contacts.apk /system/app
Your phone may not appreciate you pushing Contacts.apk while it is running, so it may become unstable at this point. I would recommend restarting.

icbeer said:
This is what you need to do:
1. Open Contacts.apk in 7-zip
2. Copy the images over top of the original images in drawable, drawable-mdpi, and drawable-mdpi-finger (notice I didn't say anything about hdpi)
3. Close the archive.
4. Copy it back onto the device with:
Code:
adb remount
adb push Contacts.apk /system/app
Your phone may not appreciate you pushing Contacts.apk while it is running, so it may become unstable at this point. I would recommend restarting.
Click to expand...
Click to collapse
thank you but I'm trying to understand what you mean by push ADB. is that the one in the sdk folder? if so, I open it and it just flashes for a few seconds then closes.

ADB is a command line program that allows you to debug and move/edit files on your phone. You need to run those commands from a command prompt (should be a link in the Accessories folder on the Start menu if you can't right-click on the sdk folder and open one). Navigate to the tools folder, then run the remount and push commands like icbeer said to get your modified .apk on your phone:
Code:
C:\users\brtnbrdr> cd c:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb remount
C:\android-sdk-windows\tools> adb push Contacts.apk /system/app

How to push files via adb?

Can someone please point me to a place that explains how to push files via adb? I have Android SDK installed and I know how to do a screen shot using Dalvik Debug Monitor using the ddms.bat file. But other than that, I don't know what I am doing. lol Also, I am not rooted.
I know it can't be that difficult, any help is appreciated! Thanks!

Holy crap, apparently I pushed a new bootanimation via adb and really had no idea what I was doing. lol
So I guess my question is different now.
First, I put the bootanimation.zip file in the platform-tools folder.
Then I launched a CMD prompt and then I went into my Android/Android-SDK\platform-tools\
then I typed in "adb push bootanimation.zip /data/local" and I wasn't even sure it did anything.
So my question now is what made it push the bootanimation file to my xoom? Did it have something to do with the file being in the platform-tools folder, along with the adb.exe file?

I don't really get the question... It pushed the file to the Xoom because you told it to. A better question might be why it did not push the file during your previous attempts, but I cannot answer that without knowing what you tried. Anyways, I just wanted to chime in that since you are already familiar with DDMS, right under the screenshot option is a file explorer that you can use to push files.
edit: actually, I think it may not be possible to push to subfolders in /data using ddms since it cannot see them

sangreal06 said:
I don't really get the question... It pushed the file to the Xoom because you told it to. A better question might be why it did not push the file during your previous attempts, but I cannot answer that without knowing what you tried. Anyways, I just wanted to chime in that since you are already familiar with DDMS, right under the screenshot option is a file explorer that you can use to push files.
edit: actually, I think it may not be possible to push to subfolders in /data using ddms since it cannot see them
Click to expand...
Click to collapse
Yea, I didn't do it in ddms because I did not see the local folder. I did it through the CMD prompt. But my question is how does it know where to push the files by just typing "adb push bootanimation.zip /data/local"? No where in that does it say push it to the xoom. When using adb, does it automatically try to push the file to whatever Android is plugged up? How does it know where and what to push it on? That was my question.

Best place I've found to start is http://developer.android.com/guide/developing/tools/adb.html which gives an overview along with some good details on some of the subcommands. Beyond that, use your favorite search engine.
To answer your question more directly, though, if only one Android device is connected, ADB can figure out how to talk with it. With two or more you'll need to specify the device (which you can get from "adb devices").
HTH

short/y said:
Best place I've found to start is http://developer.android.com/guide/developing/tools/adb.html which gives an overview along with some good details on some of the subcommands. Beyond that, use your favorite search engine.
To answer your question more directly, though, if only one Android device is connected, ADB can figure out how to talk with it. With two or more you'll need to specify the device (which you can get from "adb devices").
HTH
Click to expand...
Click to collapse
Ahh.. cool. I did google it to see what came up and learned a little but nothing ever explained how adb knew what or where to push the file.
But just knowing that it does know, then the rest is pretty easy to figure out. I can follow and type commands well... even though I might not know what they do (which is scary, huh?). lol
Edit: Thanks for the link also.

I got this from XDA somewhere so credit to them:
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish

[Q] [AOKP] Cannot access root files to install boot animation

So, I've rooted my captivate and have installed build 32 of aokp.
I'm trying to install a custom boot animation. However i cannot access /system/media from my computer and when i try to copy and paste the .zip from the sdcard, file manager won't let me. /data/local does not exist.
I should mention i'm running blue infinium.
Any help? I'm pretty sure i'm being stupid but i've tried everything i can think of and read a bunch of threads.
Thanks in advance,
JSP

jsb_front said:
So, I've rooted my captivate and have installed build 32 of aokp.
I'm trying to install a custom boot animation. However i cannot access /system/media from my computer and when i try to copy and paste the .zip from the sdcard, file manager won't let me. /data/local does not exist.
I should mention i'm running blue infinium.
Any help? I'm pretty sure i'm being stupid but i've tried everything i can think of and read a bunch of threads.
Thanks in advance,
JSP
Click to expand...
Click to collapse
Unless I'm mistaken, you actually want to put your boot animation in /system/media.
And if you have ADB installed, you can just reboot to recovery, hook up the USB cable, put your bootanimation.zip into the /platform-tools folder where ADB resides, and issue this command:
adb push bootanimation.zip /system/media/bootanimation.zip
If you don't have ADB, you'll need to get a root-level file manager (ES File Explorer, Root Explorer, etc) to move the file.

Noob mode activated:
I'm assuming ADB is an app, and the code i'm supposed to enter is entered on the phone through a terminal program?
Otherwise thanks, makes sense. Anyway to access /system files through windows explorer?
Thanks again
*EDIT* Also, thats what i've been trying to do with the file manager. But when the file is selected/cut/copied, i cannot access the root files. I have tried several different root file systems.

jsb_front said:
Noob mode activated:
I'm assuming ADB is an app, and the code i'm supposed to enter is entered on the phone through a terminal program?
Otherwise thanks, makes sense. Anyway to access /system files through windows explorer?
Thanks again
Click to expand...
Click to collapse
ADB is on the computer, you run it in terminal or command prompt. There isn't a way to access /system through windows explorer
Sent from my CM9 ICS i897 Captivate

korockinout13 said:
ADB is on the computer, you run it in terminal or command prompt. There isn't a way to access /system through windows explorer
Sent from my CM9 ICS i897 Captivate
Click to expand...
Click to collapse
Alright, thank you. Also, does terminal=cmd? I understand terminal can be on the phone, but i always thought, on windows anyway, that terminal is synonymous with command prompt.
Thank you all for the help

jsb_front said:
Noob mode activated:
I'm assuming ADB is an app, and the code i'm supposed to enter is entered on the phone through a terminal program?
Otherwise thanks, makes sense. Anyway to access /system files through windows explorer?
Thanks again
*EDIT* Also, thats what i've been trying to do with the file manager. But when the file is selected/cut/copied, i cannot access the root files. I have tried several different root file systems.
Click to expand...
Click to collapse
ADB is Android Debug Bridge - it's part of the Android SDK that you have to download and install from Google. It's a pretty handy tool to have.
As korockinout13 pointed out, no dice with the Windows Explorer seeing the root files, and terminal does equal cmd/command prompt.
With the explorer app on your phone, you'll have to look around and find a setting that will tell Android to mount your /system folder as read-write. I believe in Root Explorer there's a button near the top that switches read-only and read-write.

Looked around on explorer and couldn't find the setting. Root explorer costs 4$ and I've tried a couple others. All giving me the read only memory error. I'll just have to wait till I get home to do it over adb. Thanks for all the help.

root access wont let you "see" your root folders when you mount your phone as SD card.
adb is one of many options.
copy to sdcard, then use a root level manager to move
wait!! there was this on the portal today.... Quick ADB Pusher.. adb file pusher GUI
http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/

Got it to work with Ghost Commander. There's an option to remount files as ro/rw.
Works great. Thanks for your help!

That bootanimation is screwed up - it's not zip, files are stored. It took me a while to figure it out.