Related
I've seen a lot of people asking how folks have changed the Windows logo to the HTC one and so on. I am one of those people!
There's a thread over in the Diamond Forum here, http://forum.xda-developers.com/showthread.php?t=437307, that discusses altering the taskbar icons.
I've had a read of that but it doesn't appear to discuss the start button. I've currently got a cab installed that gave me coloured icons on the taskbar but also the 3d MS Office style start button. I like the icons but not that start button.
Is there anyway someone could provide an idiot/noob style guide for altering that icon. I'd love to have the Vista start button on my HD (attached image) but have no idea how to go about it aside from I think it has something to with .dll files.
Can anyone explain this? Anyone? I know there would be a lot of people grateful for it! I've Googled and used the search but just cannot seem to find anything!
I've attached a mock-up of my ideal; I've got the coloured icons, just the start button to go!
I think....
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
I believe you can do it with Wisbar.
Wisbar is not free.
http://www.lakeridgesoftware.com/
sk806 said:
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
Click to expand...
Click to collapse
you had a chance at it yet? did it work?
...........
This is the thread I used to alter the Windows logo to a HTC logo among other things in this thread. It's dead easy,
1) Unsign the file using Unsigner linked to in the thread further up (on page 2 of the Unsigner thread there's a .bat file that I found gave a better idea of whether it had worked or not).
2) Open the file in Reshacker and go to Icon on the left hand side and click it to expand it. Go to number 292, click it and it will expand to show 1033. Click 1033 and it should be the start menu icon. Right click on 1033 and select Replace Resource. Select Open File With New Icon and find your new (resized) icon. Double click it and it will show a preview of new and old. Click Replace in the bottom right corner.
3) Save the newly modified file.
4) Sign the modified file using Ssigner linked to in the thread above. CHECK THE TEXT FILE IT CREATES TO MAKE SURE IT SIGNED OK. Don't forget this bit as it will mean a hard reset if you do (as I learnt).
5) If you've not installed SDKCert.cab some time in the past. download it from here, copy it to the phone and install it.
6) Copy the file to the Windows directory on the phone using Resco Explorer or Total Commander.
7) Reboot the phone.
how did you copy shellres.192.dll? it says "Acces denied" even with resco. No chance to renaming also
To get the file in the first place you need a program called ROM Extractor on the phone to get the file from ROM. There are also different varients of the ROM for different locales. There's a description in the link above.
thanks for your efforts but seems a little complicated TotalCommander did the trick, resco seems to have some security check problems
anyway, unsigner doesn't work so i'm stuck
guap said:
anyway, unsigner doesn't work so i'm stuck
Click to expand...
Click to collapse
Try the .bat file in the second page of the Unsigner thread. Copy Unsigner, the .bat file and the file you want to unlock to the same directory and double click the .bat file. Also, because the file is from ROM make sure it's not marked as Read Only when you get it to your PC before unsigning it. If it's from ROM they're usually Read Only for a start.
frostywrath said:
you had a chance at it yet? did it work?
Click to expand...
Click to collapse
Not yet. Just got back from work. I need a different job...
I will try tomorrow. I have been meaning to give this s shot for a while now, and the icon you posted is what I have been looking for.
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
guap said:
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Click to expand...
Click to collapse
True, but when I tried Unsigner on it's own it didn't give any feedback as to what it was doing (or if it did I missed it) so I changed 150+ icons only to find it hadn't been unsigned and therefore couldn't be resigned. At least with the batch file I can check it's been properly unsigned before making changes.
Does it give you any error messages when you try Unsigner?
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean me or someone else?
Prof. Yaffle said:
Does it give you any error messages when you try Unsigner?
Click to expand...
Click to collapse
that's the point: no errors from unsigner, but resourcehacker can't open my file (not valid bla bla bla)
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean this cab?
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/Colored Top Bar.cab
Don't forget you'll need to install this first:
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/1SdkCerts.cab
Hope this helps.
Prof. Yaffle said:
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
Click to expand...
Click to collapse
uhm seems reasonable
but I don't want to extract all my whole rom for a stupid dll... I extracted with total commander, isn't supposed to work this way?
Nope, certain ROM files can't be copied using normal file copy programs. I've found that they try and copy, then say the "File already exists, do you wish to replace?" and then whatever you select you're left with a 0k file with nothing in it. The ROM extractor doesn't copy the whole ROM. When you launch it you get a list of all the ROM files. Double click the one you want to extract, give it a location (\ usually for the root directory of the phone) and a name and click Extract.
Ok, I will try. But how to replace when modified? If I can't even read it, how will I replace it?
Hello!
So, some guys tested my bat-script and they reported that it works! So i create a new thread..
All you need is a java installation (i think jdk, becuase you need the jar binary) and adb! You have to edit the bat file and
set the 2 variables to the directory.
The other variables (sed, smali, baksmali, dexopt-wrapper) are in the package, so you shouldnt change it.
If anything necessary is not found, the script will not start!!
Attention: If you run the bat file, be sure your mobile is NOT IN STANDBY!! You have to be in normal mode (not recovery or sth) and the screen turned on!
So not in lockscreen/standby mode, because otherwhise SuperUser does not popup and ask for root-rights.
When you dont allow root-rights you will see a permission error during the script and this is bad (it will ask you 2-3 times for root rights).
I made this script, so everyone can look at the commands (not hiding inside an exe file which could do anything).
Here is the link: http://rapidshare.com/files/420586328/install_lockscreen.zip
Windows verion needs to be on rapidshare/filehoster, because i have put the sed binary + dll into it (you need it for windows and autopatching the .smali file)
Just download the bat script and edit it with an editor (notepad++ or jedit or just notepad) and set the ADB variable to adb.exe and JAVA_DIR to the JDK-directory (not including \bin - just the main-directory).
Tested successfully on my JM5 and some other user with JM8 and someone with JH2!
4 things todo (not for running the script, just for the future ):
1. create script for linux/mac os usage (shouldnt be so hard, but i have not so much time currently..)
2. auto-create an update.zip with the original android.policy.odex/.jar file for errors (because you cannot change this file if the phone cannot boot - su segmentation fault)
3. if /system/xbin/dd is not here or if it is missing the "conv=notrunc" option, the script should abort
4. create a version for deodexed mobiles/firmwares.
I dont have a clue, how to create an update.zip, so if anyone of you could give me a little help, i would be very happy
And i dont have a deodexed mobile, so someone should tell me the difference, so i can make a different script or the script should autodetect it.
Big thanx to Ateisti for found this solution: http://forum.xda-developers.com/showthread.php?t=779803
If you like my work you can buy me a beer (but you dont have to ): Beer via paypal
menu button fix included or not?
When someone would tell me what this is, then i can insert it in the script
Ateisti talk about it at the end of the first post of his thread
Found it
- By default, the menu button will also unlock the screen. To disable this behavior, you have to modify /res/values-hdpi-v4/bools.xml in /system/framework/framework-res.apk, and change the value of <bool name="config_disableMenuKeyInLockScreen">false</bool> to true. Can also be done by modifying code.
But, i have disabled WidgetLocker and just the AndroidLockscreen now..
I can hit so many times i want the menu button, the lockscreen will never be released..
I have JM5 (2.1). Maybe this is there different?
I will make on the weekend a linux version of the script and then i will also enable this feature..
thE_29 said:
When someone would tell me what this is, then i can insert it in the script
Click to expand...
Click to collapse
There is also a way to do this from the android.policy smali files. I did it on my UGJH2.
go into "android.policy\com\android\internal\policy\impl\LockScreen.smali"...
Do a search for "return v4" and change it to "return v6" (this should be within the method ".method private shouldEnableMenuKey()Z", closer to the ".end method" line.)
To add it to your script, have it change this at the same time as the other file you edit and bingo, no more menu button unlock....
didn't work here.
thank god you made a backup folder
JHJP8, not de-odexed.
I'm new to this and just need a tutorial on how to create custom splash screens on a Evo. If any one can show me or post a link that be great.
Download this and unzip it. (On your computer)
http://db.tt/YLmI87K
There's a how-to included in there that tells you how to use it.
Sent from my HTC EVO 4G with Tapatalk
there's also a program called nbIMG, along with the one mentioned above.
Thanx working great!!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Cammands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancments you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to resize the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will resize within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the bootloader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the bootloader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOTLOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Bootloader by holding the volume down button and pressing power. The bootloader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the bootloader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the bootloader, you have in effect reflashed the stock rom (rooted of course) back to your phone.
Allow a few mintues for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup
manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if
this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
Can't u flash these also ??
neno2323 said:
Can't u flash these also ??
Click to expand...
Click to collapse
They're "flashed" in the bootloader, as a PC36IMG with the file being respective to how you rooted. You can also "flash" them using fastboot, but that can only be done if you're on the .76 bootloader.
Hello guys,
Just thought i'd share the source code with you and a tutorial on how to modify it to work with a rom with a modified ondemand governor by default. Or if you wanna change the values altogether you will be able to do so.
Also if any other devs wanna modify it to look better or anything feel free, we are a community
Right first off your gonna need
Eclipse properly set up to work with android and OpenSense SDK (i will not go through how to do this, google is your friend for that)
The Source Code provided in this post
An APK signer
Patience because if your not experienced this could take a while
Tutorial:
First off extract the .zip somewhere on your pc
Then your gonna want to open Eclipse, go to File/New/Project.
From there expand the android folder and select "Android Project From Existing Code"
Click Here For ScreenShot
On the next screen where it says "Root Directory", point it to where you extracted the source folder to.
If you have done it correctly your screen should look like this:
Click Here For ScreenShot
Click finish and the project will be open.
From there, at the top left you will see a section saying "Package Explorer".
Underneath you will see "com.ondemand.gaming.boost.OnDemandGamingBoostActivity".
Click the arrow to open it up.
Once opened you will see a lot more options, the one we need to worry about is"src", so go ahead and open that one up.
You will see another 2 options, go ahead and open up "com.ondemand.gaming.boost".
From there you will see "OnDemandGamingBoostActivity.java", double click that and it will open in the main window.
Click Here For ScreenShot
Right the bit we are after is about halfway down, so just scroll down till you find this section of code.
Click Here For ScreenShot
From here you will see that this is where all the commands get executed.
"ShellInterface.runCommand" basically tells the app to run a command.
The top half is the values to revert back to when you disable gaming boost, this is shown by the "preference.setSummary("Gaming Boost Disabled");" at the end of the commands. (Most likely this is just the section you will be editing, but the same would apply if you was changing the optimized values)
From here its pretty much self explanatory, you edit the values to whatever you want them to revert back to after you disable gaming boost.
Make sure you edit all the values, some commands appear twice so make your you edit every instance of the value you see, a good way to check is to search for the old value when you think you have finished to see if you have missed it anywhere.
Please Note: They have to match whatever your ROM Dev uses in his ramdisk, contact him if you dont know what they are or check/modify his ramdisk yourself.
The last thing you need to edit is the file the app checks for before allowing the changes.
Above all the commands you will see "String ODGBState = SubActivities.readFile(ODGB_File + "/up_threshold", true);"
This basically means the app will check the value of "up_threshold" and if the value in the app doesn't match the value in the ramdisk the app won't work.
This is where things may get a little confusing.
The value for the checkfile for when the app is disabled is actually found in the second block of commands, where the optimized values are.
Just above the commands you will see "int iDisabled = 85;"
The "85" is the value of the up_threshold you have just modified in the previous steps, so change that to match what you tweaked it to.
Exporting the APK.
Once you have done all the editing you want to export the apk for use.
On the left hand side pane, the 3rd from the bottom in list you will see "AndroidMnifest.xml". Double Click it.
In the main windows about three quarters of the way down you will see the "exporting" tab. Click on "export an unsigned apk"
Choose a name and where you want to save the app and click save.
A pop up will come up when its saved.
From there all you need to do is sign the APK and push it to system/app, or include it in your ROM ZIP.
This may not be a 100% perfect tutorial but its worked for me, i'm still learning.
If anyone see's any errors please point them out.
Thank you.
SOURCE CODE
How to properly install framework apks and use tags
ApkTool (and therefore VTS) needs framework apks to properly de- & recompile Android resources.
Framework tags are used to differentiate between multiple sets of framework apks.
You are usually going to have one set (ie. multiple apks) per device and base/rom version.
When installing frameworks it's very important to install all frameworks from the same device/rom with the same tag.
Have a look at this tutorial to learn more about installing frameworks with VTS.
Click to expand...
Click to collapse
How to completely reset the VTS layout
VTS has a "Reset layout" button, but sometimes this can't repair all problems with a broken window layout.
To fix such persistent problems, open the settings and untick the "Save dock layout" checkbox.
Now restart VTS, the layout should be reset to the default layout.
You can enable layout saving again.
Click to expand...
Click to collapse
How to manually edit VTS settings
Since VTS 2.6.12 you can easily change these settings with the "Advanced settings" window inside VTS.
Open the settings window and click on the "Advanced" button at the bottom.
VTS stores its settings easily accessible in XML files. They are stored in a folder (normally) located here:
C:\Users\<your user>\Documents\Virtuous Ten Studio\Settings\
You can easily open and edit these settings files, just make sure VTS is closed before doing so.
Note: Some settings only exist after VTS used them for the first time.
Click to expand...
Click to collapse
VTS can't find the Java binary
Make sure to add the location of your Java.exe to your PATH variable and reboot after doing so.
VTS should be able to find your java binary now.
If it still doesn't work, you can manually specify the java path in the VTS settings.
Click to expand...
Click to collapse
Something else went wrong and I need help
Editing apks and other Android related files can be a highly complex task.
There are many possible error sources. If something goes wrong nobody can help you unless you provide some important things: (if applicable)
The VTS logs. Without these it's pretty impossible to troubleshoot problems that occured while using VTS.
Have a look at this tutorial, it explains you how to use the Log Viewer.
Make sure all checkboxes on top are checked and copy all the log text from the textbox.
When asking for help, make sure to include all the text in [CODE]<log text>[/CODE] tags.
A logcat of your device, the packagename (if applicable) and filename of the file you are working on.
If something goes wrong or doesn't work on the device you are working with, it's absolutely required to get a logcat before asking for help.
You can use the Logcat viewer of VTS to get a copy of the so called Logcat. It's the internal log of your device and usually helps revealing and solving all kinds of problems occuring on the device.
As with the VTS logs, please include the Logcat in [CODE]<logcat text>[/CODE] tags.
Your Operating System version (eg. Windows 8, Windows Vista etc)
General information:
Can you reproduce the issue?
Did you try to restart your computer/your device first?
Click to expand...
Click to collapse
Feel free to propose me any new entries for this post
Something is badly messed up..
I used VTS v2.6.12 .. Until then everything was alright.. I used to decompile framework-res.apk, framework.jar, systemui.apk..
I never got any boot loop..
I downloaded and installed the latest version and ..
Whatever projects I made in v2.6.12 .. Were not recompiling.. May be because there was an update to apktool..
I had to make all new projects.. .
SystemUI.apk of my stock ROM is ~2.5mb.. After I decompile and recompile its size is like 5mb .. Why so??
I have to do everything manually ..
It never shows any error while decompiling or compiling..
How can i figure out where the problem is??
rkharat98 said:
Something is badly messed up..
I used VTS v2.6.12 .. Until then everything was alright.. I used to decompile framework-res.apk, framework.jar, systemui.apk..
I never got any boot loop..
I downloaded and installed the latest version and ..
Whatever projects I made in v2.6.12 .. Were not recompiling.. May be because there was an update to apktool..
I had to make all new projects.. .
SystemUI.apk of my stock ROM is ~2.5mb.. After I decompile and recompile its size is like 5mb .. Why so??
I have to do everything manually ..
It never shows any error while decompiling or compiling..
How can i figure out where the problem is??
Click to expand...
Click to collapse
You made a pretty big jump in versions there, I suspect the changes in the file formats prevented a proper loading of your old files.
Sorry for that, I never expected such large version jumps.
As for the size, in its default configuration VTS builds all binaries with no compression, whereas most binaries come with some compression. You can set the compression level in the settings of the zip module yourself. In any case, the size difference does no harm, you can leave it either way.
@Diamondback, great work.
Can I compile Apk via VTS? Example: I have sources and want to compile it with my drawables,XML,values. Thanks in Advance