I currently use a HTC HD Mini (Photon) running the SCREAM ROM by Ling Gan. It has a few bugs for most of which there is either a workaround or fix but there is the one problem which has remained unsolved: the default wallpaper on everything BUT the home and lockscreens cannot be changed. It is of a tree in a meadow under a blue sky and when rotated to landscape changes to some smiling chinese lady in the "settings" submenu. Doesn't hamper use much but it is quite annoying.
I have tried a number of solutions some of which resulted in my having to reflash and others did nothing. I post this here because I think it is a CM7 issue. The ROM developers have so far been unable to post a solution within the thread and I am aware that a fix for similar problems on CM9 ROMs exists using ADB to edit framework-res.apk. I felt it was time the problem was tackled by the wider XDA fam. Used google translate to look on the chinese site where the ROM is native to (mobile-kon) but found no help as well. Any help would be greatly appreciated.
i think ur problem lays in the framework-res.apk it contains the look of the rom and the transition effects
you can mod apk with the apkmanager tool for ur computer in the frameworkresapk you should find the images u want to change replace them witch a black picture or something like that
if never done this befoure exept from changing some transition effects and i had a couple of errors among this
the easier way seems to search for the rom on another page cus the images ure stating are not standart in the cm7
SOLVED!
jiffer1991 said:
i think ur problem lays in the framework-res.apk it contains the look of the rom and the transition effects
you can mod apk with the apkmanager tool for ur computer in the frameworkresapk you should find the images u want to change replace them witch a black picture or something like that
if never done this befoure exept from changing some transition effects and i had a couple of errors among this
the easier way seems to search for the rom on another page cus the images ure stating are not standart in the cm7
Click to expand...
Click to collapse
Many thanks!
I started off looking through the "res" folder in framwork-res.apk using Root Explorer to identify the images for the wallpaper. They were
Res/drawable-land-mdpi/screen-background-dark-transparent.png
And
Res/drawable-mdpi/screen-background-dark-transparent.png
I then created a copy of framework-res.apk on my SD card and copied it onto my pc. I created new wallpapers to replace the ones I just mentioned, one in portrait, the other in landscape. They were 320x480 and 480x320 respectively. Using 7zip on the pc, I placed them in the corresponding folders (/drawable-mdpi for protrait and /drawable-land-mdpi for landscape).
I copied framework-res.apk back to my sdcard and then fired up terminal emulator to run the following commands
su
sys -rw
busybox cp /sdcard/framework-res.apk /system/framework
sys -rw
You might get error messages from running apps after this but ignore them and reboot. The idea is to replace the framework-res.apk in system/framework with the one you just edited.
After the reboot, you should have your newly created wallpaper showing up in settings in both landscape and portrait modes.
Please hit "thanks" for both jiffer1991 and I if this was helpful. Big ups to jiffer1991for pushing me in the right direction.
Hi,
i did something wrong.
So my Phone didn´t run.
He show me the Bootsceen and the Animation.
But the he will run again and again and again.
Can i handle my Phone via USB so i can restore the framework.resp.apk on my System? Or i have to reinstall Android again?
I have no backup and i don´t want to erase my system settings.
Thanks
Felix
obstgarten said:
Hi,
i did something wrong.
So my Phone didn´t run.
He show me the Bootsceen and the Animation.
But the he will run again and again and again.
Can i handle my Phone via USB so i can restore the framework.resp.apk on my System? Or i have to reinstall Android again?
I have no backup and i don´t want to erase my system settings.
Thanks
Felix
Click to expand...
Click to collapse
hm u got stuck in a bootloop thats what i meant when i mentioned errors =)
you could make a zip with the old framework res apk or reflash the cm rom
if u dont whipe data/cash ure setting will be safed
read some tutorials how to mod the framework res apk
I have an .zip file on the sd card.
Can i copy it to the Android system somehow?
Felix
P.S. can i zip the framework and remove the ".zip" to ".apk"?
It is most likely that the zip file you have is the ROM image from which you flashed in the first place. Changing the extension to apk is NOT what you want to do. I suggest you create a backup in CWM of you present configuration and after reflashing, you can then do a partial restore of your user data. But its like Jiffer1991 said, read up on CWM, theres an exhaustive guide on xda somewhere.
Thanks,
i installed my modified cm rom without wipe caches data or something.
And now i have my old datas back, with the new Background.
Related
Hey everyone, I have successfully made a few ROMS for myself (using the DSIXDA HTC Android ROM kitchen v 1.00). I am making a ROM for the HTC Evo.
I know how to do most of it, I have managed so far:
To add my own ringtones
To add my own notification sounds
To set the default ringtone, notification, and change the default wallpaper
Add a theme to my ROM
But there is a few questions I have. I have Googled, looked around on here, and done what I can to find the answers but I am so far unsuccessful.
My first question: Ok, I know that the default wallpapers reside in the system/customize/resource directory. I have attempted to replace the wallpaper (and small preview) wallpapers with my own custom ones. I tried using Paint.net for Windows to resize to the same dimensions as the default wallpaper. For example, to replace htc_wallpaper_01.jpg, I edited a 960x800 wallpaper to have the same size and name (everything the same) and changed htc_wallpaper_small_01 with a matching 80x60 smaller version of the new graphic. I have found sometimes it works, but if I do a few using the method mentioned above, the ROM fails to load up. Can someone help and explain why?
Question 2: I am trying to place the removed apps automatically on the SD Card. I made a "sdcard" folder in the root directory of my ROM. I tried editing the update.zip to include copy_dir PACKAGE:sdcard /sdcard and when I do a check for errors I get none, yet when I try and install the ROM it gives me the "E:syntax error in update script" meaning I am not doing it right. I tried doing it the same way Fresh did it and it also threw me the same error.
So can anyone please tell me how to do this? I know I am close with both and I have tried dissecting other ROMS to see how they did it but I cannot figure it out.
First question:
It could be many possibilities. Maybe not enough room on system, file names not matching, etc...
Try each png on seperate flashes to find the culprit.
*The best way to find out for sure is to use "adb logcat" on boot. This tells you all your errors the OS has.*
Second question:
Im not understanding what your trying to do?
Root of a rom is /
sdcard is mounted to a folder on /
If you want to store the apk on sdcard then,
the proper code to install in /sdcard from update.zip:
Code:
copy_dir PACKAGE:sdcard SDCARD:
If this is not what your asking please explain to me what your asking.
RichieDaze said:
First question:
It could be many possibilities. Maybe not enough room on system, file names not matching, etc...
Try each png on seperate flashes to find the culprit.
*The best way to find out for sure is to use "adb logcat" on boot. This tells you all your errors the OS has.*
Second question:
Im not understanding what your trying to do?
Root of a rom is /
sdcard is mounted to a folder on /
If you want to store the apk on sdcard then,
the proper code to install in /sdcard from update.zip:
Code:
copy_dir PACKAGE:sdcard SDCARD:
If this is not what your asking please explain to me what your asking.
Click to expand...
Click to collapse
Thank you RichieDaze for the response.
You mentioned png., but all the ROMS I have seen have the wallpaper in .jpg format. I was just wondering if there was a certain size they have to be (I mimic the exact size of the default ones).
I think I got this part worked out by doing exactly that, installing 1 at a time until I find the culprit.
For question 2: Thanks to using the DSIXDA kitchen, I cannot use updater.script, which seems to be the way ROM makers like Calkulin, Hero_over, and other have used to set their removed apps to automatically copy on to the SD card when you install the ROM.
I have to use update.script instead, and when I try and do it using that I run into an error.
What I am trying to is remove the usual bloat from the ROM, but copy the removed apps so that users can have the option of installing them if they use any of them.
You are answering my question and are on the right track to helping me. I will try to add that (the way you wrote it out) and see what happens to my update.script.
Thank you very much for your help, greatly appreciated and please let me know if there is some other way to do this if you are aware of any or if someone is using update.script instead of updater.script.
There is a font on another rom that I like, how would I get that installed onto my Eris? I have the file from the other rom.
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
bftb0 said:
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
Click to expand...
Click to collapse
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
johnny quest said:
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
Click to expand...
Click to collapse
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
bftb0 said:
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
Click to expand...
Click to collapse
Ok, thanks I will give it a try.
johnny quest said:
Ok, thanks I will give it a try.
Click to expand...
Click to collapse
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
johnny quest said:
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
Click to expand...
Click to collapse
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
bftb0 said:
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
Click to expand...
Click to collapse
Thank you so much, I've been living on backups and restores. believe me I've learned my lesson. I will give this a try.
Your method worked great with the Root Manager. I bought it on the market. Ok, my biggest problem now is that my font is microscopic small. I don't know why. But I can't see the letters of which folder I'm in to take that font out.
I need a favor: can you post up screenshots or the number of folders to scroll down to get to the system/fonts/droidsans.tff
I can't see it, really its that small its the universal acc font.
Never mind I got it. Took a lot of squinting but I got it. Thanks.
Is anyone working on a custom theme or have any info available? I think we desperately need one, to at least clear up the issue with white text on white background in some apps.
I don't know anything about theming, but I read in a post that there might be something in /system/framework/framework-res.apk. At least that is a starting point. Maybe someone can post more info to get us going.
im running froyo on emmc all i did was pull framework change the icons to ones i like and push it back i can shoot you a copy and some directions if you would like?
fyi if your still on the nook stock or just rooted framework these can not be changed in this manner.... i tryed
misfit343 said:
fyi if your still on the nook stock or just rooted framework these can not be changed in this manner.... i tryed
Click to expand...
Click to collapse
Yeah, I'm on 2.1 with the 1.1.0 Pre-rootered ROM. I guess we'll need a custom ROM for themes?
Not positive what it would take to theme the barns and noble ui.... tryed without any sucess. I think its just a little too much over my head. Thats why i jumped at having an internal 2.2 on here
Sent from my Nook Color (zoom2) using Tapatalk
I'm working on a Froyo theme right now. Not sure if there's a way to theme the B&N framework though. I have a really good link that explains how to theme and will post it in a bit.
I will say, it is definitely time consuming.
EDIT:
Here is the link. The How-To is a little vague, but the tools are what's most important.
My method of editing:
- is to pull the /system/framework/framework-res.apk using APK Manager
- extract the apk
- decompile the apk so you can edit it
- Use Photoshop or GIMP to edit the images you want to change
- Save (in PS, I use Save For Web), making sure you save without meta data
If the image is going to be a stretched image:
- Go to the Tools folder in the Android SDK folder and launch the draw9patch.bat script
- Drag your newly edited image into the draw9patch program. This will create a 1px border around your image
- Click the left mouse button and draw a black line along the portions of the image you want to be stretched. If you mess up, right click (Macs: ctrl+click) to erase if needed
- Save the image
- The images are located under the res/drawable-mdpi folder so save back to that folder and overwrite the old files (make back-ups of course)
- Going back to the APK Manager program, select option 11 to compile the apk. Select Y and then Y again.
- The script will stop mid-way and tell you what to do. Follow those directions
- Using ADB, mount the Nook's /system ('adb shell mount -o remount,rw /dev/block/mmcblk0p1 /system')
- Back to APK Manager, select option 8 to push the package to the Nook
- Using ADB, type 'adb reboot'
With any luck, the Nook will reboot without problems.
An additional tip:
When you compile the apk, you have to delete the files you edited. If you go through and edit files and then compile the apk, instead of having to go back through and delete all those you've already deleted before, pull a fresh, new copy of the framework-res.apk before continuing on to your next edits. It will keep your list of files to delete from growing out of control.
http://forum.xda-developers.com/showthread.php?t=916814
sent from my rooted Captivate using the XDA App
I've seen it asked quite a few times now, so I thought I would share how I've been creating my own themes for the Nook. This is a quick and dirty guide as I've almost got it down to a science for quick, keyboard shortcut, theming.
Things you'll need
Photoshop or The Gimp for editing files
Android SDK so you can push and pull files to/from the Nook.
draw9patch app in the Android SDK /tools folder for creating 9.png files
APK Manager (http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1)
Notepad++ or some other text editor for editing XML files. After using Notepad++ on this, I'd highly recommend it though
An attention span
Some restraint
This is a rather good guide that helped me get started. My only complaint is that it is almost to complicated and includes more information than what is needed for a basic theme.
http://forum.xda-developers.com/showthread.php?t=916814
Getting Started:
Download the Android SDK and get it installed.
Download APK Manager
ADB pull /system/framework/framework-res.apk
Make a copy of the framework-res.apk files as a back-up in case you need to revert
Copy the framework-res.apk file to the /place-apk-here-for-modding folder under the APK Manager folder
Launch the APK Manager Script.bat file
Type in 22 to select the default project
Type in the number next to framework-res.apk in the list to select it as your project
Select 1 to extract the files
Select 9 to decompile (this is what makes the XML files readable)
Go to the /projects/framework-res/res folder under the APK Manager folder to view all the files from the theme
Images are located in the /drawable-mdpi folder. XML files are located throughout, but the files specific to layout are under the /layout folder. To change global settings, such as color codes and strings, edit the XML files under the /values folder.
Creating custom PNG files: If you are using Photoshop, use the Save For Web feature when saving. Save the image as PNG-24. Select None under the Matte option. Select None under Metadata.
A word on 9.png files: 9.png files are files that can be stretched by the OS. There is a 1 pixel border all the way around the image. In that 1 pixel border, you'll notice solid black lines here and there. The black pixels indicate which portions of the image are to be stretched. You can add this border and the black pixels in Gimp or Photoshop, or you can open the file the draw9patch app under the Android SDK /tools folder. The draw9patch app will actually display how the image will look when stretched as you add the black pixels around the border, so it can come in handy and it's what I prefer to use. You can open and edit .9.png files in draw9patch and edit the border even after you save the file.
Once you have all your files edited, recompile the APK package with APK Manager
Option 11
y
y
It will tell you to delete the files under the /keep folder that you have edited. Delete any images and XML files, from the /keep folder, you edited under the /projects folder. If you edited XML files, delete the /keep/res/resources.arsc file as well
Press any key to continue and let the script finish
In a separate command line window, mount your Nook's /system folder (adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system)
back in APK Manager, select 8
/system/framework/framework-res.apk
Reboot your Nook
Boot Loop: If you messed something up and are stuck in a boot loop, most of the time you can still mount your Nook, push the original framework-res.apk to it and reboot. Or, you can use an unedited version of the CWM flashable zip file from the link below.
NOTE: it is not smart to push your framework-res.apk file to the Nook. I've learned the hard way that you can only do this about 10 times before you run out of memory and can no longer boot your Nook until you reflash Froyo again.
I'd recommend only a few flashes on a bare bones copy of Froyo until you feel comfortable with working on the framework theme. After that, I'm attaching a base, flashable zip for you to use in CWM so you can flash the theme instead of pushing. This will prevent you from getting stuck in a boot loop (unless you do something wrong yourself).
To add your framework-res.apk file to the zip, just open the zip and replace the /system/framework/framework-res.apk file (I'd recommend 7zip).
A Few Goodies
I'm including all of the PSD files I use to edit and create themes. If you want to create your own, custom theme, these will get you started. The only downside to these PSD files is that they are at the MDPI scale. If you want to create an HDPI theme, you'll need to increase the sizes.
Link to PSD files for creating your own theme, plus the flashable CWM zip file:
http://jjis.me/android-theme-templates
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
PMDColeslaw said:
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
Click to expand...
Click to collapse
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
wretchedlocket said:
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
Click to expand...
Click to collapse
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment updater-script.zip
PMDColeslaw said:
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment 546902
Click to expand...
Click to collapse
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
PMDColeslaw said:
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. I had too many things to do with the family yesterday.
If you haven't got this working yet, I'd suggest trying to start with removing just the /system/app/Vendind.apk file via the updater-script. If it works, then go back in and add each additional line until you run into problems again. At that point, you'll know what your problem is.
Since everything else (framework-res.apk, services.jar, etc.) gets replaced successfully, leave those lines alone. I'd just start with the basics of replacing the Vending.apk first and then work your way back up from there.
The stock battery icon on Galaxy wifi 5.0 is not very inspiring and it doesn't tell you the battery level. It is quite easy to replace them on other phones with Clockwork Recovery. You just need to go to UOT kitchen http://uot.dakra.lt/kitchen/ , pick the icons you like and it will give you a flashable zip file.
Without Clockwork Recovery on Galaxy wifi, it can still be done but with a bit more manual operations.
Prerequisites:
1. A rooted device.
2. Clockworkmod Recovery (optional).
Step 1:
Use Titanium backup (pro version needed) to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. For example converting Flash player and google map to user app free up enough space for me.
Step 2:
Backup the following apk files from your stock rom. You can do that by using some file manager like File Expert. These files will be needed by UOT kitchen
/system/app/SystemUI.apk
/system/framework/framework-res.apk
/system/framework/twframework-res.apk
Step 3:
Go to UOT kitchen http://uot.dakra.lt/kitchen/ and cook your custom UI. Make sure you read their how-to here first http://uot.dakra.lt/how_to/
Step 4a: (follow this if you have Clockworkmod Recovery)
Copy the zip produced by UOT kitchen to your internal SD card. Reboot to CWM Recovery and flash the zip file using the option "Install zip from sd card". Then reboot and you are done.
Step 4b: (follow this if you don't have Clockworkmod Recovery)
Extract the 3 modified apk files from the zip package produced by UOT kitchen and put them into a convenient location on your sdcard, say /sdcard/
Step 5:
The system directory is by default read only. You need to remount it as r/w. I do that through adb shell
Code:
su
mount -o rw,remount /dev/block/mmcblk0p13 /system
Step 6:
Copy your new apk files into /system directory
Code:
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/framework-res.apk /system/framework/
cp /sdcard/twframework-res.apk /system/framework/
Step 7:
Restart your device. The /system directory should remounted as read only and the new UI will take effect.
Disclaimer:
Certainly there are risked involved and I did corrupted my rom on several occasions when trying this out. So make sure you have a functional ROM around before you give this a try.
thanks for the tips.
hey I wanna ask you about is it can fully modification from http://uot.dakra.lt/kitchen/
I mean don't just modify battery icon but every option that site provide.
thanks in advance.
" Step 1:
Use Titanium backup to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. The flash. For example converting Flash player and google map to user app free up enough space for me."
How do you do that with titanium backup? Do you have to get pro?
aillez said:
thanks for the tips.
hey I wanna ask you about is it can fully modification from http://uot.dakra.lt/kitchen/
I mean don't just modify battery icon but every option that site provide.
thanks in advance.
Click to expand...
Click to collapse
I have only experimented with icons so far. Other mod may be possible because UOT kitchen does support gingerbread. Since this device is new, we need some brave soul to try that out
iJimaniac said:
" Step 1:
Use Titanium backup to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. The flash. For example converting Flash player and google map to user app free up enough space for me."
How do you do that with titanium backup? Do you have to get pro?
Click to expand...
Click to collapse
Yes, you will need the pro version. If you have the pro version, long press an app will give you the option to do the conversion.
Well, while deleting apps with TI, I decided to get rid of "phone", figuring I didn't need it, but it turns out Google voice needs it! Trying to "restore", but just hangs forever. If someone could give me the "com.sec.android.app.dialertab.apk" located in /system/app/ I would really appreciate it!
EDIT; I just reinstalled voice from market, seemed to fix it, I wouldn't advise removing phone from the apps though!
can you make the display of battery accurate to 1%?thank you!
First make it accurate to 5%, then work on 1%
I think the accuracy of the battery level is deeper down in the system, may be in the kernel?
If you try different types of battery widget on Galaxy Player, they all have very bad accuracy.
I want to edit the framework-res.apk manually, instead of using the kitchen. Do the files need to be deoxed? Would flashing a framework-res compiled with apk manager brick the device?
nice guide!
I've used UOT Kitchen to get ICS transitions, change icons, battery, fonts, and customize the status bar and they all work on my galaxy player 4.0 US.
what are those different icons you have on your notifications like the wifi icon and what launcher is that ADW?
azoller1 said:
what are those different icons you have on your notifications like the wifi icon and what launcher is that ADW?
Click to expand...
Click to collapse
I am using the "Color pack V8 animated" icon set on UOT kitchen. The launcher is GO Launcher.
Stale_bread said:
I want to edit the framework-res.apk manually, instead of using the kitchen. Do the files need to be deoxed? Would flashing a framework-res compiled with apk manager brick the device?
Click to expand...
Click to collapse
There is still an odex file in the system directory. I suppose it is not deoxed but UOT kitchen doesn't seem to bother with that file. I guess it is because these apk files don't contain any executable code.
from OP
Disclaimer:
Certainly there are risked involved and I did corrupted my rom on several occasions when trying this out. So make sure you have a functional ROM around before you give this a try.
Click to expand...
Click to collapse
Two things, if you please:
When you say "corrupted my rom", you can't boot your device but you can still go to dl mode, correct?
"functional ROM" is the fw/md5 file we usually flash via odin/heimdall?
I'd like to try this out (& then some...) but, in the absence of a custom recovery, I don't wanna have to go through the lengths of "resurrecting" my sgp. TIA!
maxq1 said:
from OP
Two things, if you please:
When you say "corrupted my rom", you can't boot your device but you can still go to dl mode, correct?
"functional ROM" is the fw/md5 file we usually flash via odin/heimdall?
I'd like to try this out (& then some...) but, in the absence of a custom recovery, I don't wanna have to go through the lengths of "resurrecting" my sgp. TIA!
Click to expand...
Click to collapse
In my case, it couldn't boot beyond the samsung start up screen, but I can still boot into download mode. Since we are only modifying a file within the file system, it is very unlikely that it will destroy the download mode.
If you can get to download mode, you can flash one of the firmwares you found in this forum using odin. You need to be sure you have the correct firmware for your device though, because there are so many variant of Galaxy Player. What is the version of your device?
nvm that (i was thinking on the same lines too though) but thanks anyway! appreciate it.
thanks to your guide, was able to change my fonts and added that flying in pop up animation as well. for these two, however, i don't think we need the kitchen though and for that matter, we don't need to modify systemui & twframework.
for fonts (you could use font changer apps, but i hate doing so for such things), take any you fancy from anywhere here in xda (WARNING: only extract the downloaded file to your device/pc) then rename (case sensitive) font files accordingly: Clockopia.ttf, DroidSans.ttf, DroidSans-Bold.ttf. copy these to sd & push to /system/fonts/ using similar cp command/s from OP.
for pop up animation, you could follow this guide. no need to sign after replacing files in /res/anim. copy modded framework-res.apk to sd then push to device via same commands in OP.
btw, wouldn't issuing "reboot" within adb shell be more convenient & safer after changing system files while booted to android? it's what i did instead of rebooting via power button, as you'll most likely see an FC fiesta after replacing these files.
maxq1 said:
nvm that (i was thinking on the same lines too though) but thanks anyway! appreciate it.
thanks to your guide, was able to change my fonts and added that flying in pop up animation as well. for these two, however, i don't think we need the kitchen though and for that matter, we don't need to modify systemui & twframework.
for fonts (you could use font changer apps, but i hate doing so for such things), take any you fancy from anywhere here in xda (WARNING: only extract the downloaded file to your device/pc) then rename (case sensitive) font files accordingly: Clockopia.ttf, DroidSans.ttf, DroidSans-Bold.ttf. copy these to sd & push to /system/fonts/ using similar cp command/s from OP.
for pop up animation, you could follow this guide. no need to sign after replacing files in /res/anim. copy modded framework-res.apk to sd then push to device via same commands in OP.
btw, wouldn't issuing "reboot" within adb shell be more convenient & safer after changing system files while booted to android? it's what i did instead of rebooting via power button, as you'll most likely see an FC fiesta after replacing these files.
Click to expand...
Click to collapse
Theses are good suggestions, will definitely give them a try.
As for changing system fonts, I like to use the Font Installer app on the market
https://market.android.com/details?id=com.canvs2321.font_installer&hl=en The nice thing is I can preview the fonts before changing them.
As for the reboot, actually I did try using the reboot command once but it toasted my rom on that occasion. That's why I didn't mention the method in the guide. May be I should give that another try next time.
Hopefully, we will get CWM soon then it will be much easier to flash these mods.
WT Ho said:
I think the accuracy of the battery level is deeper down in the system, may be in the kernel?
If you try different types of battery widget on Galaxy Player, they all have very bad accuracy.
Click to expand...
Click to collapse
Kernel battery driver is very simplistic and only has 5% increments in the numbers it returns.
On my list to look at once I finish CWM - no guarantees.
thhhhhhhhhhhhhhanxx