Database Info

[Q] Recompiling framework-res.apk problem

Hello,
Was following http://forum.xda-developers.com/showthread.php?t=1109962&page=8# to try and get SIP support on an SG SII running 4.0.3 LPQ [Polish] build.
I had to use another method to decompile and recompile my framework-res.apk due to a bug in apktool. That works well and it recompiles. I followed the instructions in the thread above to the letter, including removing info from the keep folder and eventually get a signed APK.
I copy the APK to my device, restart and suddenly I get loads of force close errors before it eventually restarts. This loops. At the moment I'm copying it in via ES File Explorer or manual 'cp' command in Terminal Emulator.
Please can anyone give some insight into what I'm doing wrong?
Thanks

I don't know what the cause is actually, but here is how I edit framework-res.apk.
If i want to make changes to the code, I extract classes.dex from the package and decompile it with baksmali
"java -jar baksmali-1.3.2.jar -o dexout/ classes.dex "
then i make the changes to the code and i recompile it
"java -Xmx512M -jar smali-1.3.2.jar dexout/"
Then i rename the out.dex file to classes.dex and add it to the framework-res.apk package
And if you need to add/change images just drag n drop the files inside the apk
Hope that helps you

very very sorry wrong post

Try pushing the apk to your phone in recovery mode, with the system partition mounted. Changing framework-res.apk while the phone's running can cause all kinds of odd bugs.
Sent from my U20i using xda premium

Have you updated your SDK tools? I thought that with rev.17 they fixed the bugs with re-compiling. If not, the easiest way I fixed it was to de-compile, then search and open all the plurals.xml files in notepad++, then at the end of almost all the files there will be a line of code that has two(2) %'s in the same line. That's what kicks up the error. all you have to do is add a second % to the last one. Using notepad++ makes this really easy, just use find and replace: FIND- %d</item> REPLACE- %%d</item>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To this:
Then I re-compile. I then go to framework-res/build/apk/ and pull out the resources.arsc and any other files I edit(res\values\bools.xml, in your case) and copy them back into the original framework-res.apk, that way I don't have to mess with any signatures or anything else. reboot to recovery, mount system, adb push framework-res.apk, adb reboot.
p.s. This is the only way I have been able to edit, build, and flash framework-res.apk in ICS without problems like fc's and other things. I hope this helps a little bit. and all I use is
Code:
apktool d framework-res.apk
and
Code:
apktool b framework-res newframework.apk
but with this method it always works.

Interesting. I'll bear that in mind but I wouldn't have thought that would cause any bugs. The syntax is technically correct, it's just a little odd.
Sometimes this code makes no sense..lol
Sent from my U20i using xda premium

Ticklefish said:
Interesting. I'll bear that in mind but I wouldn't have thought that would cause any bugs. The syntax is technically correct, it's just a little odd.
Sometimes this code makes no sense..lol
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Yeah a guess it was a "feature" they add in aapt for ICS, but like I said I think they fixed it in rev 17, but I haven't confirmed this yet.
Sent from my Ice Creamed 3D

Ah, that could be right. I'm not on ICS yet. Guess I need to pay more attention when I do!
Sent from my U20i using xda premium

[GUIDE][GB] Change path thickness of Pattern Lockscreen to ICS style

Guide to changing path thickness of Pattern Lockscreen to ICS style​
I wandered places searching this off. I found some traces in direction of my destiny but none of them worked fully correctly
So, as stated, I searched a lot for this mod and came face to face with failures and smali errors. So, I had to figure it out myself some modification to do in it to make it work.
Note: IT is not COMPLETELY my mod but I have done modifications in it to make it work. This is based on a guide for Froyo outside of XDA.
Pre-Requisites:
1. PC with Java JDK or JRE
2. Deodexed ROM
3. 7-Zip
4. classes.dex decompiling tool
5. Notepad++
6. Patience
7. Carefulness for editing smali files
Let's Start
1. First we would have to decompile classes.dex inside framework.jar
For that, you can use my Tool ROM Tool v2
First using 7zip, Right click on your framework.jar and open it as archive and drag and drop classes.dex in input folder of the tool
(Note: If you don't have classes.dex in framework.jar [only META-INF and preloaded-classes.dex], then your framework isn't deodexed)
Now, open Script.bat and choose 1 (Decompile classes.dex)
2. Now, we will make the changes. Go to decompiled folder and go to \classout\com\android\internal\widget and open LockPatternView.smali in Notepad++
Search for mDiameterFactor:F [Ctrl+F]​
See the code above it.
It should be like this:-
Code:
const[COLOR="Red"]/high16[/COLOR] v2, 0x3f00
If it is, then you will have to remove red part /high16
Because it will not allow the change of code we will be doing which will have a different hexadecimal value which will not be supported till this code is in effect
Now, it will look like this:-
Code:
const v2, 0x[COLOR="Red"]3f00[/COLOR]
Now, we will change the thickness value 3f00 to 3dcccccd
Final code will look like this
Code:
const v2, 0x3dcccccd
Save it
I am attaching final and before smali for comparison below.
View attachment Smali.zip
(Note: If you don't have /high16, it's good , then just just change the value and save)
3. Go to Script.bat again and choose 2 (Recompile classes.dex) and after it's done, you will get classes.dex
Drop it in framework.jar
4. Push framewotk.jar in /system/framework
Eg:
Copy it in platform-tools folder of android SDK and type following with pressing Enter after each command
Code:
adb remount
adb push framework.jar /system/framework/
adb shell chmod 644 /system/framework/framework.jar
adb shell killall system_server
Last command will Hot Reboot your phone to apply changes. It is fast and better than rebooting phone.
5. Enjoy
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before
After
Credits​
A member from other forum to answer a question to other member of that forum
Google for letting me search somethings
Samsung Galaxy Ace s5830i members for supporting me so much

RESERVED

Very nice, made here and was show!

thank

[FIX]adbd cannot run in production builds[With pictures]

Ever been using adb and tried to "adb root" but come up with the error "adbd cannot run in production builds"?
Sine i cant find any guide this guide is aimed directly at you! this is how i fixed it! and its actually really easy
NOTE: this will be a tool in the future, it will be for windows and linux.
Explanitory Tutorial
Step 1. Decompile the kernel (not gonna go into detail)
Step 2. In the root of the decompiled files find default.prop
Step 3. Open it with a text editor(in windows use notepad++)
Step 4. Change This Line
Code:
ro.debuggable=0
To this
Code:
ro.debuggable=1
Step 5. Save it, recompile and flash! DONE
Picture Tutorial
Step 1. Decompile the kernel (not gonna go into detail)
Step 2. In the root of the decompiled files find default.prop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3. Open it with a text editor(in windows use notepad++)
Step 4. Change this line
To this
Step 5. Save it, recompile and flash! DONE

sorry for bumping this thread that no one took care about but
THANK YOU SO MUCH

pls help me
i edited my phone build .prop usibg app in phone as it was rooted
it is htc desire626
so i edited api level and now no app is wworking except few
error boxing telling this app has stopped working comes
so i am able to pull build .prop file from phone edited it but cant push it back due to read only system
adb root is not working as it was yours
can you tell me how to decompile kerrnel
or any way i can get my phone fixed:crying: pls

usmanzafar306 said:
pls help me
i edited my phone build .prop usibg app in phone as it was rooted
it is htc desire626
so i edited api level and now no app is wworking except few
error boxing telling this app has stopped working comes
so i am able to pull build .prop file from phone edited it but cant push it back due to read only system
adb root is not working as it was yours
can you tell me how to decompile kerrnel
or any way i can get my phone fixed:crying: pls
Click to expand...
Click to collapse
I also come to this problem, how did you fix that ?

.

lebigmac said:
Okay so I set ro.debuggable = 1
And now the adb root command works but now I get this error when doing adb remount afterwards:
Code:
Not running as root. Try "adb root" first.
Even after adding all of this to the default.prop, the same error persists:
Code:
#unsecure
androidboot.selinux=permissive
drm.service.enabled=false
keyguard.no_require_sim=true
persist.adb.notify=0
persist.android.strictmode=0
persist.cne.feature=0
persist.security.ams.enforcing=0
persist.selinux.enforcing=0
persist.service.adb.enable=1
persist.sys.root_access=1
persist.sys.strict_op_enable=false
persist.sys.strictmode.disable=1
persist.sys.usb.config=mtp,acm,adb
ro.adb.qemud=0
ro.adb.secure=0
ro.allow.mock.location=1
ro.build.selinux=0
ro.build.selinux.enforce=0
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
ro.config.kap_default_on=false
ro.config.knox=0
ro.config.rkp=false
ro.config.sec_storage=0
ro.config.tima=0
ro.config.timaversion=0
ro.debuggable=1
ro.kernel.qemu=0
ro.sec.fle.encryption=false
ro.secure=0
ro.securestorage.knox=false
ro.securestorage.support=false
ro.security.mdpp.ux=Disabled
ro.setupwizard.enable_bypass=1
ro.setupwizard.enterprise_mode=0
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.storage_manager.enabled=false
ro.tether.denied=false
security.mdpp=None
security.mdpp.result=None
security.perf_harden=0
service.adb.root=1
Click to expand...
Click to collapse
hi again sir
i think i am every where
do you fixed adb root cannot run as production build ?

[Info] Difference of Odex and Deodex Files

Some people don't know about an Odex or a Deodex Files. I'm gonna explain it to you in the most understandable way :highfive:
Almost all of the Rom here are deodex because it is easier to theme or modify the .apk file because odex files are hard to modify.
These .odex files are also in the same directory as the .jar or .apk file which is located at /system
What is an Odex File?​
In system applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. The odexed file structure works well as an optimization tool. Since these .odex files contain preliminary load information about each system app, the OS knows what to expect when it’s booting up, and consequently, it loads apps faster.
On the other hand, it makes the applications difficult to modify/theme 'coz a part of the coding has already been extracted to another location before execution.
For example, in a system app there is:
Phone.apk ===> next to it will be ===> Phone.odex
the Phone.odex has some part of the codes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is a Deodex File?​
It’s the process to take all the packages out from .odex file and reassemble them all together in classes.dex file which is kept inside the APK file in other word it will combine the .odex file to the .apk file and will become a classes.dex. By doing this, it can eliminate/remove the worry to modify the APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
Example on the same system app:
Phone.apk ===> will no longer have a Phone.odex instead it will be bought inside the Phone.apk as ===> classes.dex
Advantages and Disadvantages​
Odex files can build Dalvik Caches faster on the first boot and execution of an app will be faster..
but harder to theme unlike
Deodex files can be modified easier than odex files but building Dalviks and executions will have a slight difference in .odex
Credits
to this Thread
and Google Images :laugh:
You
ME

[GUIDE] Adding Extra Details in About Phone in Settings.apk [NOOB-FRIENDLY]

Hi guyz,
Today I want to share something about settings.apk mod….
Its about adding small details in about phone section…
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: I have not copied it... Actually I was playing with some codes and got success. I don’t know if there is any guide about this… There is guides about this, but those are hard for newbies because those are complex and there is some work in strings.xml... But in my guide there are no work of that .... I think this is the easiest way.....
So lets start…
Requirments
Apktool, Java Runtime
NotePad++, 7zip
Knowledge about decompiling, recompiling
A little respect (must)
And your Settings.apk & framework-res.apk
Step 1..
Decompile your Settings.apk
Step 2..
Go to res > xml
Open device_info_settings.xml
Now Copy This Code
Code:
<Preference android:title=" TITLE " android:summary=" SUMMARY " style="?android:preferenceInformationStyle" />
And paste it before </PreferenceScreen>
See the Image… I have added 2 lines… And You can write there anything……
Step 3..
Now Recompile your settings
Step 4..
Open decompiled Settings folder then go to build/apk, there u will find AndroidManifest.xml file…
Now open original Settings.apk using 7zip then copy the META-INF folder and AndroidManifest.xml file…
paste both the files in build/apk folder, if asked to replace, click yes..
now go to a folder in settings folder named dist, there u will find Settings.apk which u compiled.....
now delete it. We never use the first Settings.apk that we compile, because we need to add the META-INF and AndroidManifest.xml files for signing purposes.
Once you have deleted the 1st compiled Settings.apk, return to the command prompt and again compile the Settings using this code
Code:
apktool b Settings
After it is compiled go to dist folder there u will find new and fresh compiled Settings.apk which u can use it…
Step 5..
Using Root Explorer push it into system/app folder and set permissions to rw-r-r-
That's it!
Credit goes to YOU if you get success :fingers-crossed:

Nice tut sir