Is there any in existence? I mean roman's tweaks settings, for adding battery percentage and crt animations for our phone.
Sent from my DoubleShot Lite using Tapatalk
masterkamon842 said:
Is there any in existence? I mean roman's tweaks settings, for adding battery percentage and crt animations for our phone.
Sent from my DoubleShot Lite using Tapatalk
Click to expand...
Click to collapse
have you tried hitting up Blue, since he is the keeper of the ROM that roman started? otherwise, how about pulling the tweaks.apk out of a Bulletproof ROM and putting it into /system/app of your current ROM? i'm not sure if it's that simple or not, but could be worth a try.
yogi2010 said:
have you tried hitting up Blue, since he is the keeper of the ROM that roman started? otherwise, how about pulling the tweaks.apk out of a Bulletproof ROM and putting it into /system/app of your current ROM? i'm not sure if it's that simple or not, but could be worth a try.
Click to expand...
Click to collapse
I tried pushing it to system but it wasn't that easy... Didnt work for me. Ill see if I can get blue's attention. I'll keep this thread posted for future reference.
Sent from my DoubleShot Lite using Tapatalk
masterkamon842 said:
I tried pushing it to system but it wasn't that easy... Didnt work for me. Ill see if I can get blue's attention. I'll keep this thread posted for future reference.
Sent from my DoubleShot Lite using Tapatalk
Click to expand...
Click to collapse
What you can do is use Root Explorer to move it to /system/app while the phone is on, then set the permissions (long press on it, permissions is in the menu that pops up - scroll down) to look like the permissions of every other file in the /app folder.
Edit: to quote myself from explaining how to do it before:
Stop all apps that require market licensure to work, halt the market processes, delete the old vending.apk. Then you have to delete the market data directory at /data/data/com.android.vending and find the dalvik-cache file that belongs to the market ( [email protected]@[email protected] ) and delete that too.
Then you rename the new market .apk file to Vending.apk and use root explorer to copy it into your /system/app directory. Once there, you long-press on the Vending.apk file and select 'permissions' from the menu that pops up.
Change the permissions to read/write for owner, read for group, read for others, and nothing for the bottom 3 check boxes. Now it reads rw-r--r-- like all the other apps in the /system/app directory.
Then you reboot your phone and it should work, but you should clear the whole dalvik-cache in recovery, and you should clear cache in recovery too, so all the dependencies on the market get rebuilt the right way.
Click to expand...
Click to collapse
Then, reboot the phone, and see how much of the app works.
You should be able to get it installed that way, but if not my thread on Replacing the Google Market would be a good place to start learning how to make your own flashable zip file.
Just replace the market with whatever app you can't push to /system/app normally and you should be good.
Some third party apps don't run well or at all from the /system/app partition, they just expect to be in /data/app ... but some will. The one you're playing with works fine from in the /system/app directory.
Might want to look into this thread by Romanbb: Extended Quick Settings as well.
Romanbb's awesome tweaks are worth the work - I couldn't imagine using the device without them now, and am definitely looking at playing with it some. The one thing i'm struck by as a user more then anything else, i'd like to be able to change the order of the quick settings in the actual pull-down menu.
I want flashlight first, full settings second, then i'll figure out the rest of the order as I go, but both volume settings go dead bottom with me.
I haven't had the time to sit down and do it, but that's the next ability i'm interested in acquiring with regards to that. I can't wait to get my phone back so I can start making some progress again.
Meantime, i'll be in and out and others floating around here I know can steer you right if you need it - you lose nothing 'cept time for trying (you did do backups before you started playing around, right?).
Hi, I made Tweak.zip (i extracted tweak.apk from booletproof 1.1) for flash it by CWM, but don't works fine.
After flashed, the app is in /system/app with 0644 permissions, but with no visible changes, where was i wrong?
Can you help me? In attach my file.
antonaq said:
Hi, I made Tweak.zip (i extracted tweak.apk from booletproof 1.1) for flash it by CWM, but don't works fine.
After flashed, the app is in /system/app with 0644 permissions, but with no visible changes, where was i wrong?
Can you help me? In attach my file.
Click to expand...
Click to collapse
The tweaks need coded into the ROM, It's not as simple as just installing the apk, I would think some SystemUI smali needs edited also for any tweaks to Rosie, the Rosie.apk smali files will need an edit, so it knows what to change otherwise your just looking at the possibilities of the tweaks app.
I just did a Rosie remap for my Sense 2.1+3.0 Speedy ROM, and even though the option had always been in MikTweaks I had decompile tweaks to activate the remap option for my ROM ( by default It's turned off for Sense 2.1 ROMS ). Then I had to decompile Rosie and make the smali change. Then compile and resign both apps and i was good.
Sent from my myTouch_4G_Slide using Tapatalk 2
If you are really needing those tweaks, you can use the kitchen to apply most of them.
Compile? Decompile? More difficult for me then... I abadone the idea to realize Tweaks.zip.
Sorry.
Inviato dal mio Bulletproof_Doubleshot con Tapatalk 2
Related
OK, second try, (please ignore all posts up to number 17)
Here are some Swype Layouts that i collected over the past few feeks, most of them are not done by me but it is hard for me to give the right people credits cause most of the Swype threads were deleted. So please let me know if you'll find "your" png's here.
QWERTZ AND QWERTY Keyboards are modified. Currently there is no Swype Beta version out there for QWERTZ, but maybe in the future (or someone has a "modified" version already).
Compatible with all Roms and all WVGA (800x480) Swype Versions!
What you need:
- Metamorph (root, busybox...)
Instructions:
- go to data/app/ and search for com.swype.android.inputmethod.apk (or ...inputmethod-1.apk ...inputmethod-2.apk)
- move the file to system/app/ (MOVE! not Copy)
- be sure the file is called exactly com.swype.android.inputmethod.apk .. if there is a -1.apk or -2.apk rename it!
- reboot your phone! check if swype is still working properly
- copy the desired layout (the complete zip file attached, do not unzip!) to /sdcard/AndroidThemes
- open Metamorph and click Unzip/Extract new theme
- choose the desired theme
- klick Apply all
- REBOOT!
- choose swype as input method again (long click in empty input field -> input method -> swype)
- should be done now
Please report back if this works for you, this is my first Morph.
If you do not want to move your apk from data/app to system/app you might use Daneshm90 great script which pulls the swype.apk from the phone, copies the keyboard files in it, signs it and pushes it back. To get the right Keyboard files please extract them from my Morph themes (they are located in assets/keyboards) and copy them into the images folder of the script. The script backups your Swype settings and dictionary!
You can find his Script here .
Thanks Daneshm90 for the script and his kind help and Formel-LMS for his private message support!
original Style if you want to undo the changes.
Im confused, how is metamorph capable of modifying apps in /data/app ??? Those apks require resigning which metamorph doesnt do.
blah you are right, works for me cause i signed the swype apk for myself...
so cut/paste to system/app should be fine?
Thanks for the hint.. my first morph obv.
Well yea but u gotta then provide the apk which the forum frowns upon
Heres an alternative i created for another swype themer.
Link
sorry, had a "typo" in my reply. wrote data instead of system first.
what about cut/paste from data/app to system/app and then morph. Might that work?
edit: wow, awesome script!
so can i just replace your png with mine and upload the modified script? downside is that people are loosing their dictionary and have to start from "swype-scratch"
watercool said:
sorry, had a "typo" in my reply. wrote data instead of system first.
what about cut/paste from data/app to system/app and then morph. Might that work?
Click to expand...
Click to collapse
Yes, that should theoretically work. So this is wht would need to happen:
User with swype already installed will have to backup that apk.
Uninstall swype
Push to /system/app/
Then apply ur morph
Restart phone.
Or u cud use my script where all it does is :
Pulls the apk from ur phone
Extracts it
Replaces the images with urs
Repacks it
Signs it
Uninstalls swype from ur phone
Installs this modded one
watercool said:
sorry, had a "typo" in my reply. wrote data instead of system first.
what about cut/paste from data/app to system/app and then morph. Might that work?
edit: wow, awesome script!
so can i just replace your png with mine and upload the modified script? downside is that people are loosing their dictionary and have to start from "swype-scratch"
Click to expand...
Click to collapse
Hmm k. Didnt realize that. That should be an easy fix just gotta backup the /data/data folder for swype. K while im modifying the script, want me to change anything else ? such as more folders than assets ???
Daneshm90 said:
Yes, that should theoretically work. So this is wht would need to happen:
User with swype already installed will have to backup that apk.
Uninstall swype
Push to /system/app/
Then apply ur morph
Restart phone.
Click to expand...
Click to collapse
thanks for your help!
i just moved my com.swype.android.inputmethod.apk from data/app to system/app and it still works? Is this cause i have my "special" version or is an uninstall really necessary? -> edit: puh, ok.. now it is gone lol... move does not really work lol
edit: no, just assets is fine!
watercool said:
thanks for your help!
i just moved my com.swype.android.inputmethod.apk from data/app to system/app and it still works? Is this cause i have my "special" version or is an uninstall really necessary?
Click to expand...
Click to collapse
Hmm try restarting and see if it causes any issues, if it doesnt then try applying a morph and see if that causes any issues. If both dont then i guess ur fine
issues here lol, swype is gone hehe. trying to reinstall... confused right now a bit hehe
ok had to reinstall after moving from data to system.
can you adopt your script and implement my files (or i can do the copy/paste work for myself..)
here are my files (or morphs for system/app instead of data app)
watercool said:
ok had to reinstall after moving from data to system.
can you adopt your script and implement my files (or i can do the copy/paste work for myself..)
here are my files (or morphs for system/app instead of data app)
Click to expand...
Click to collapse
That'll be generic, so once i just change something in my script and upload it, u just gotta place one of ur themes png's inside the pics folder and run the script.
great thanks, please let me know as soon as you are done.
thanks again for your kind help.
K so im done the script. It now backs up swype data and restores after. One thing though, it seems as though the filename convention is different for the pngs inside assets/keyboards. Im using swype 1.56.30.7625.t100 and when i replace ur pngs inside that folder it still shows default. Is it version dependent ?
Any way, heres the script. The script version u downloaded, notice in the pics folder the filenames are:
SwypeRef_LS_Blue_HVGA.png
SwypeRef_LS_Blue_Shifted_HVGA.png
SwypeRef_LS_Editing_HVGA.png
SwypeRef_LS_Editing_Jump_HVGA.png
SwypeRef_LS_Editing_Jump_Select_HVGA.png
SwypeRef_LS_Editing_Select_HVGA.png
SwypeRef_LS_Numeric_HVGA.png
SwypeRef_LS_Standard_CapsLock_wBlue_HVGA.png
SwypeRef_LS_Standard_Shifted_wBlue_HVGA.png
SwypeRef_LS_Standard_wBlue_HVGA.png
SwypeRef_PT_Blue_HVGA.png
SwypeRef_PT_Blue_Shifted_HVGA.png
SwypeRef_PT_Editing_HVGA.png
SwypeRef_PT_Editing_Jump_HVGA.png
SwypeRef_PT_Editing_Jump_Select_HVGA.png
SwypeRef_PT_Editing_Select_HVGA.png
SwypeRef_PT_Numeric_HVGA.png
SwypeRef_PT_Standard_CapsLock_wBlue_HVGA.png
SwypeRef_PT_Standard_Shifted_wBlue_HVGA.png
SwypeRef_PT_Standard_wBlue_HVGA.png
Those seemed to work for my swype. Once again it could be version specific.
Link
Thanks, i will try this later!
No not version depended, but you're using HVGA and my files are for WVGA
Moving from data/app/ to system/app/ works now, i forgot to reboot to check it.
I followed the steps as outlined in the first post. After that swype was gone...reinstalled it via android commander...et voila: swype is back with the HTC theme (that I wanted to try out).
Thanks for the theme!!
Confused
Hey thanks for the info. I was wondering, does the swype apk have to be a "working" one? I tried may apks and all of them were out of beta. I also tried your steps and they didn't work for me. I'm just a little confused, sorry for the dumb questions.
is this for the newest version of swype? 1.60.36.8214?
I was able to change the system and framework directories from R/O to R/W and add circular battery png's to the framework-res.apk and push to the phone, screen shot is attached..
It might not be the progress to get complete root, but atleast we can mod the look of it and it stay after power down.
Wow. I need to get rid of the preinstalled swype so I can install the one with speech mic on it
And this mod holds after a restart?
Sent from my HTC Glacier using XDA App
Yea, so far rebooted 2 times and still holding.
Sent from my HTC Glacier using XDA App
Good news.
good find bro... def something to look into nice to have other ideas to build on
Mr Bill Florida said:
Yea, so far rebooted 2 times and still holding.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
...with fastboot OFF?
Fastboot is off, used root explorer to change attributes and pushed with adb.
Sent from my HTC Glacier using XDA App
Ok so newb question here... I've tried to mod framework-res.apk numerous times on my n1 and adb never works right, won't push or doesn't exist, or just bootloops... Any chance you could do a step by step write up on how you got the battery .pngs To work? I was just using uot kitchen before and now without full root I can't use it... I know its a pain but this is a mod I did constantly to every rom I ran. Ie: phone on? Resign apk? Commands in adb? Thanks ;-)
Yes! instructions would be awesome!
Instructions and someone else is what it will take before I believe this. Since it is not even deodexed as well as the battery icon in the picture looks blurry (to me anyways) and doesn't look native.
I pulled the framework-res.apk from system/framework
opened it within winrar and moved the battery png's to res/drawable-mdpi
it asked to update after move and click ok
went into root manager and remount /system as r/w
pushed framework-res.apk to /system/framework
that is the exact steps I followed as I did with when I had my mytough3g as well
I still can't wrap my head around this. How do these changes persist beyond a reboot if the system partition cannot be written to??
I thought this was the single biggest issue blocking progress in developing for both this device and the G2. So, it would appear that Root Explorer can re-write anything in the system partition by simply changing from r/o to r/w?
I don't get it.
NICE NICE, and nice Applanet ^_^
so this does work. Only thing i did was mount system in clockwork recovery then push framework-res.apk to /system/framework as far percentages go, there are only .pngs for 0,10,20,40,60,80 and 100 percent so i would assume the .xml needs redone. But cool to be able to do this!
I haven't seen this around, so I went ahead and made this for myself, and I decided to share it with anyone who wants it...
I hate the Recent Apps section of the Notification Bar Dropdown... so I removed it.
I wanted the Recent Apps to be removed without having to flash a complete ROM or use some theme.
1. Flash the attached file in CW Recovery
2. Clear Cache and Dalvik Cache
3. Reboot
4. Profit (It will remove the recent apps section)
There are no side-effects that I have noticed.
It was made from the SystemUI.apk from the stock US 2.3.4 Build, and should work on any 2.3.4 build for the Sensation.
There are no other changes in this from stock 2.3.4 besides removing the Recent Apps.
It will work alongside the Battery Mods I made with no issues... One mod does not affect the other.
Let me know if you have any issues.
As always, I'm not responsible if your phone breaks beyond repair and you lose all your data.
Thanks to j4n87 for the smali change required.
Work for me on EagleBlood rom.
It would be helpful.
NoRecents - installed with tiwili - take it, work it, leave it
Hi,
thanks for this mod. As always all actual modifications in existing SystemUI.apk are changed by this installation.
I took both of your modified files in my tiwili-installation method. So all other existing files in SystemUI.apk will rest in peace.
I publish it here because it´s your work, your files; It took 5 minutes for me, that´s nothing to be proud of...
Greets
idephili
So pretty much this needs root?
Sent from my HTC Sensation 4G using XDA App
thevietmonk said:
So pretty much this needs root?
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Absolutely. You can't push SystemUI.apk to the apps directory without root.
Thanks for this...finally I can remove it...just a small issue...where I am, there is no 4g network yet...however it is now showing 4g icon on the notification bar, anyway I can change it to 3g icon?
Sent from my HTC Sensation Z710e using xda premium
This will also remove the extended quick settings I had installed, flashed the EQS again though, no prob just thought I'd let ya know
Edit: Flashing EQS again, makes the recent apps come back..
ARHD 3.1.1
bigg8k said:
This will also remove the extended quick settings I had installed, flashed the EQS again though, no prob just thought I'd let ya know
Edit: Flashing EQS again, makes the recent apps come back..
ARHD 3.1.1
Click to expand...
Click to collapse
That's because both mods modify the same system file. You can only choose one or the other unless the EQS Dec decides to put this in his mod.
sorry.
No worries, thanks for the effort anyways
This does not work on 3.5 SENSE but thank you for your work
EQS-Mod + Recent App
Hey
What do i do if i want the Recent App, with EQS-Mod ?
thanks...... I'll try this app
If any of you want to do it youself.....
1.Pull Systemui.apk from system/app
2.Decompile SystemUI.apk
3.navigate to com/android/systemui/statusbar
3.open up StatusBarFlag.smali using notepad or notepad++ (recommended)
4.Around line 89 (using notepad++) you should see this:
Code:
sput-boolean v0, Lcom/android/systemui/statusbar/StatusBarFlag;->HTC_RECENT_APP:Z
5. Change v0 to v2.
6. Recompile Systemui.apk and push via adb to system/app or copy to system/app using root explorer.
**NOTE**If using root explorer make sure to set permissions as Owner = Read/Write Group = Read Others = Read. A reboot will be required after pasting SystemUI.apk before you can change persmissions.
7. Reboot and your done!
same outcome for me with p3d had to reflash to get extended settings
I tried this but it appears to remove the entire header bar. That is, there was no pull down bar at all pushing it and rebooting. Any suggestions?
mfrost66 said:
I tried this but it appears to remove the entire header bar. That is, there was no pull down bar at all pushing it and rebooting. Any suggestions?
Click to expand...
Click to collapse
Sounds like you have decompiled SystemUI.apk incorrectly and then not signed it before pushing it. What method did you use for decompiling the APK?
I'm having some trouble with decompiling the SystemUI.apk. I get a bunch of "Invalid config flags detected" error when I try to load the com.htc.resources.apk framework; when I try to recompile I get a handful of other errors (related I'd imagine) and it doesn't recompile. Googled around a bit, found similar problems but no answers - any advice?
jimhart3000 said:
I'm having some trouble with decompiling the SystemUI.apk. I get a bunch of "Invalid config flags detected" error when I try to load the com.htc.resources.apk framework; when I try to recompile I get a handful of other errors (related I'd imagine) and it doesn't recompile. Googled around a bit, found similar problems but no answers - any advice?
Click to expand...
Click to collapse
How are you decompiling the apk...??
Didn't work. Edited what was suppose to be edited and the recent apps still show up....
i know there are hunderds of threads about this, but none of them helped me and niether of them describes my situation.
i had to change some values in bools.xml in framework-res.apk of a deodexed cm7.2 rom. so, i decompiled and recompiled using apktool and tried the folowing things (in all cases i remembered to chmod to 664):
- pushed the compiled file without signing. Boot loops.
- wiped dalvik cache. still boot loops.
- signed the compiled file. IT BOOTED! but all system apps fc. And i see a blank status bar. clearing dalvik cache doesnt help.
- copied the compiled resources.asec to original apk with winrar. NO FCs this time. still a blank status bar. Rotating the phone freezes the system instantly. but even if you dont rotate, system soon freezes, within 30 secs. logcat shows repeating messages of "cpu may be pegged. trying again". (no i havent overclocked).
how do u guys mod the frameworkres successfully?
Well, I don't know exactly what the problem you're having is since it may depend on the type of mod you're doing but..
I decompile framework-res.apk with apktool, make my changes and recompile. Then I use 7zip to copy the res folder from the new apk to the old one (just open both and drag across). Next, I extract resources.arsc from the new apk and add it to the old one, making sure to use 'store' compression. If resources.arsc is compressed at all, it causes problems.
So the original framework-res.apk now has a new res folder and resources.arsc at the right compression ratios. If you sign the new apk file, you have to make sure all the other system apps are signed the same way and it's just more trouble than it's worth.
Then I reboot into recovery, mount the system and push straight to the framework folder. I used to do this while the phone was running normally but I'd get all kinds of odd bugs if I made any change to anything other than a drawable. I'd get strange FC's, I'd lose wifi connection, all kinds of things.
And that's about it. As long as the changes I'm making don't stop the phone from working properly anyway, the above works perfectly every time.
Sent from my U20i using xda premium
arnab321 said:
(in all cases i remembered to chmod to 664):
Click to expand...
Click to collapse
Did you made a typo, or did you really have set the permissions to 664?
Its 644.
brainmaster said:
Did you made a typo, or did you really have set the permissions to 664?
Its 644.
Click to expand...
Click to collapse
that was actually a typo, and once i also accidentally made a typo on adb, but it still boots fine. i dont think giving extra permissions will screw things up.
the problem "cpu may be pegged" is rom/kernel related, because it is still there after a fresh install... sometimes it happens, sometimes not.
but i dunno anything about the blank status bar... i was trying to set "has_soft_keys" to true, to use tablet tweaks on my phone, does that cause a blank statusbar? anyone else got the same problem?
Wait, why are you using framework-res.apk for that? I think you need to change local.prop in /data to do this.
Have you actually got the line "has_soft_keys" already in the bools.xml?
Ticklefish said:
Wait, why are you using framework-res.apk for that? I think you need to change local.prop in /data to do this.
Have you actually got the line "has_soft_keys" already in the bools.xml?
Click to expand...
Click to collapse
yes it had that line, and setting it to true does bring the softkeys stuff in tablet tweaks menu. But the status bar always stays empty, nothing on it.
what needs to be changed in local.prop? There's nothing related to softkeys there on my phone.
umm, my ROM had the center clock mod on status bar, is that an issue?
Sent from my LG-P500
edit:
yes it was due to the center clock. tried anoher rom and i got the softkeys just by modding the bools.xml
First of all never sign system apps.
try using apk manager(I know it uses apk tool to do these operations) so try to set compression level to zero and heap size to 512.
I think above solutions should solve your problem but revert if u face any problem.
Sent from my Micromax_A70 using Tapatalk
Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
This method should work on all Android devices.
------------------------------------------------------------------------------------------------------------
First of all, what is odex? Something you should know about classes.dex.
Odex stands for Optimized dex. I'm not gonna explain a lot because I'm not sure if I'm right. First of all, in typical apk files, when you open it with WinRAR or something like that, you can find a file called "classes.dex"(this type of apk is deodexed). This file is the key. It contains the core codes of the apk. However the other type of apk comes with an *.odex file and doesn't have classes.dex inside the apk file. This is odexed apk. There are 2 types of ROMs here, odexed and deodexed. Odexed ROMs' classes.dex are already out of the apk files, while deodexed ROMs' classes.dex are still in the apks. When Android executes an apk, it has to extract the classes.dex out and execute it. So when you flash an deodexed ROM, the first boot takes a long long time since the Android system needs to extract all the classes.dex into dalvik-cache(it shows "Optimizing apks" on the screen for 4.0 ROMs, shows boot animation on screen for 2.3 or below ROMs). However for the odexed ROMs, because the classes.dex are already out there, the system just grabs them and use them, without wasting time and storage space extracting classes.dex out.
Why odex framework?
It can boost your device a little by odexing your framework. Your phone can run more efficiently. Although it's a complicated process, but trust me, it's worth it.
What is so special about odexing framework files? What's the difference?
Odexing an app is very easy, and I believe everyone knows how to do it. But odexing framework is really annoying. Why? Because apps and more like stand-alone things, they are not a part of system. You delete it, nothing bad happens, your phone still boots, you just get endless FC if you delete the wrong one, or missing status bar, that's all. But framework files you cannot mess around. They are parts of the system. They have to match the system's codes precisely, without any error, even the order of files(keep this in mind, very important). So for every ROM, the framework initialize codes are different(same RUU or other ROM based ROMs count as its base ROM), and you must modify the odexing binary to make it odex for you properly, or you can sit and watch the beautiful bootloop.
What's the relationship between odexing apps and odexing framework?
Simple, but important. If you odexed apps, you cannot touch the framework. Framework always goes in the first place. If you wanna odex both, you must odex framework first. Or... "The Tragedy of App and Framework"...
So what do we have to keep in mind before we start?
Keep your mind clear, prepare a bag of ice in case you feel dizzy with the codes, and MAKE ENOUGH SPACE FOR FRAMEWORK ODEXING. I would prefer you remove a few useless apks in /system/app first to make more room in system partition. Failing odexing may brick your device forever! Nah just kidding it will only cause you to bootloop. No big deal. Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
What tools do you need?
Notepad++ and a magical rar that contains all you need to success.
Let's get started.
------------------------------------------------------------------------------------------------------------
1. Use your file manager to find init.rc at the very root directory of your phone and copy it to SDCard for later code editing, or you simply adb pull it out and skip the coping step. (If you know how to compile boot.img it is even easier, just unpack boot in Android Kitchen, look for line "export BOOTClassPATH". I'm not gonna introduce that method since most people can't. Silly me, didn't I just intoduced that? XD)
2. Connect USB, set mode as disk drive so you can access your SDCard. Copy init.rc into your computer. Open it with notepad, and find where it says "export BOOTClassPATH", create a new file and copy line "export BOOTClassPATH" into the new file. For example:
Code:
export BOOTCLASSPATH/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
3. Open dexopter in the rar you downloaded with Notepad++. Find the lines that show the similar contents to the things after "export BOOTClassPATH". It is Line 21 to Line 35 on my laptop. Edit them according to the things you just copied out of init.rc. For example, if the first file is "X.jar", then you will have to edit the line into "dexopt-wrapper/system/framework/X.jar /system/framework/X.odex". Then repeat until you finish with all the files that are listed in the long list you copied out of init.rc. File order DOES MATTER. Use the bag of ice I told you to prepare eariler to make you sober if you feel dizzy with the codes. The lines may be more or less after you edited them, doesn't matter.
4. Copy "dexopter" and "dexopt-wrapper" into /system/bin and set the correct permissions. Make sure they have enough permission to change your system files. Restart your phone.
5. Go to CMD and lead it to where adb.exe is(included in the rar). Type these in order:
Code:
adb shell
su
cd system/framework
dexopter fr
Then the codes will run crazy in your cmd window... The odex process has begun!
6. If the odex process completed without error, you are half way there! Well it doesn't mean you have to stare at your screen during the process. It's about time we figure it out! The phone will automatically reboot once it's finished. If it doesn't and you are sure all are done, reboot manually.
7. If you can't boot properly, go back and check everything carefully. If you can, then open your file manager and copy the entire framework directory into your SDCard. You can still adb pull and skip the next coping step.
8. Mount SDCard. Go into framework directory on your computer. Open every file that has an odex file with it, delete the classes.dex inside. WinRAR is okay. The files may seem ridiculously small after you delete the classes.dex, but don't worry since classes.dex are already pulled out and turned into odex files.
9. Copy the whole framework folder into the folder where adb is at. Use adb to push all the files back into /system/framework.
Code:
adb root
adb remount
adb push framework /system/framework
adb shell
su
chmod /system/framework xxx (xxx is a permission code, depends on your ROM. They should be the same as the old deodexed framework files. Use Google to find out how to use the permission codes.)
10. After all the files are pushed in, reboot your phone.
11. If it still boots into the system, congratulations! You've successfully odexed your framework! If it doesn't, then go back and read everything carefully. The most common error occurs when you are editing the dexopter code. You will have to redo everything again.
Done! Everything is ready to go!
You can directly grab the files you've odexed and put it in your custom ROM(must be the same base), just don't forget the odex files.
------------------------------------------------------------------------------------------------------------
Okay, hmm, what to say now? Still, I would be glad if you donated me, but if you don't it's okay, just reply and hit thanks .
Oh almost forgot, the magical rar: http://d-h.st/tYi
------------------------------------------------------------------------------------------------------------
Big thanks to Scott, see him in #3. He explained why some files aren't odexed and provided a easier method(but they all get you dizzy )
Big thanks to JSLEnterprises, see him in #4. He provided a newer busybox for Scott's method.
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
BreatheHT said:
Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
Click to expand...
Click to collapse
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
If anyone finds this to be too much work... dont worry... it only unpacks the classes.dex once. It will only need to unpack a dex if original file has changed (changed entries need to propogate). That's why all the consecutive boots are back to a 'normal' span of time.
re-odexing your roms IS recommended if either A) you're anal-retentive/have OCD or B) propogation ("Android is Upgrading...") happens every time you reboot your device (it happens sometimes)
If you're going to use the tool scrosler linked to, replace the busybox binary with the one inside the attatched zip (this is busybox 1.20.1). The one that come with the tool is pretty dated.
:good:
Update: Busybox 1.20.2 has been released (though not compiled for android use yet)
Great stuff guys.
scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
hehe yep I know the adb pull command, I thought about it and I didn't put it in...
theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You confused bro?
Thanks. Even though I won't ever be doing this, it's good to know what's going on.
This is awesome. Thanks so much for this. I wanted to know how to odex and deodex roms.
Sent from my HTC One XL using xda app-developers app
scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..
SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yep Android Kitchen can do it.
Hopefully this will help to see more odex ROMs
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Most official ROMs are odexed.
BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Nah carrier doesn't matter.
SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions
BreatheHT said:
hehe yep I know the adb pull command, I thought about it and I didn't put it in...
Click to expand...
Click to collapse
Yeah, I like to do it better that way. Dont have to move my hands from the keyboard and mouse. Makes you more efficient :good:
BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
I think all?
superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Carrier is irrelevant. Most people dont know how to work with ODEX files so they go with de-odex. Its mroe challanging but provides a better experience.
techlogik said:
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..
Click to expand...
Click to collapse
No he is asking to go the other way from odex to de-odex.
BreatheHT said:
Yep Android Kitchen can do it.
Click to expand...
Click to collapse
JSLEnterprises said:
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, I love that script. I was the one that sent him the mnt point file for the HOX :highfive:
I am going to talk to him about bringing in "official" support for the Asus TF300T. I got the boot.img fiugred out this morning! Woot. **** is about to get real with the Asus!
superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
its a good final touch when cook done with smali tweaks.
another benefit is sorta kang-protection