I want to share this to make everyone know how I port it to our device so I shouldn't share it to just one or two people.
It is based on this proxuser thread, credit goes to him. I just make it details and make it work for our device.
We will make MIUIv4 framework to run on top of CM9/AOSP base. So we should prepare CM9 base and MIUIv4 to port. You can use any MIUIv4 to port but you can try by choosing the one which similar hardware with our device.
- Prepare extracted CM9 base rom in folder A, and extracted MIUIv4 rom in folder B. Copy file framework.jar, framework-res.apk and services.jar at /system/framework from CM9 folder save them in folder C. After here, we will port from folder B to folder A.
- Remove folder /system/framework and /system/app in folder A and replace them from folder B.
- Remove /system/app/nfc.apk, since our device don't have this feature.
- Copy all *.db and *.td at /system/etc from B to A.
- replace media folder in /system/media at folder B to folder A.
- copy content-types.properties file to /system/lib from B to A.
- copy miui-framework.xml at etc/permission
- copy /system/xbin/invoke-as and /system/xbin/su from folder B to A
- copy /system/lib/liblbesecs.so from folder B to A
- add this lines to updater-script file in folder B:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
- change values from build.prop
ro.build.version.incremental=2.x.x (version number of MIUIv4)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
Test the new port:
Now pack folder B to zip files and sign it and flash it using CWM. You should prepare the other working rom to get back to previous rom .
Use adb logcat to debug, and see the result. If it doesn't shown anything, then we should replace libandroid_runtime.so from MIUIv4, but not in my case, I kept it from CM9.
Our device is based on Qualcomm so with our new CM9 theme engine will affected, it will got hung on boot with unresolved at android/content/res/AssetManager. Just break the logcat when it shown some lines with "died" things and scroll up, you'll find it.
So here is the next step which will take more time. You should able to decompile and recompile jar/apk files, Google it for that, it's very easy to do that. We'll go for smaling and baksmaling here. And for comparing, use an application such as winmerge for windows or Meld for linux.
Remember that we have some files in folder C from CM9 and we'll use that as source for smaling steps.
- find /smali/android/content/res/assetManager.smali from framework.jar on Miuiv4 and compare it with the same file from CM9 one, replace all missing lines.
- copy missing method in /smali/android/hardware/Camera.smali
- copy missing method in /smali/android/os/Power.smali, method SetUnstableMemoryState the important one.
- copy /smali/android/server/BluetoothA2dpService*.smali
- copy /smali/android/content/res/PackageRedirectionMap*.smali
- copy /smali/org/codeaurora/Performance.smali
- copy smali/android/media/MediaRecorder*.smali
- copy /smali/android/view/GLES20Canvas*.smali
- copy /smali/android/net/wifi/WifiNative.smali
- copy /smali/android/graphics/paint*.smali
I found them by watching logcat, fixing one by one error on each boot, so now you can save much time by using this guide.
If still stuck, I look for some lines like this:
E/dalvikvm( 234): ERROR: couldn't find native method
E/dalvikvm( 234): Requested: Lxxxxxxx/xxxxxxx/xxxxxxxx;.yyyyyyyyyyyyyZ)I
E/JNIHelp ( 234): RegisterNatives failed for 'xxxxxxx/xxxxxxx/xxxxxxxx', aborting
F/libc ( 234): Fatal signal zzzzzz at 0xdeadbaad (code=1)
Then the problem is in xxxxxxx/xxxxxxx/xxxxxxxx.smali file, try to fix it first by adding missing lines in it if possible or copy xxxxxxx/xxxxxxx/xxxxxxxx*.smali if there is so many different lines.
You should see the MIUIv4 lockscreen if you done fixing all those problem.
After this we can fixing anothers, like 2G/3G data and headset.
To fix headset, it's in WiredServiceObserver.smali in framework-res.apk, find the path string which contain "h2w" word with "headset_sensor" word, remember just paths string, no else. It should be 3 words to replace.
Now to fix 2G/3G data,
replace RIL*.smali and copy LGEQualcommRIL*.smali at path
/smali/com/android/internal/telephony ín framework.jar.
You also need to patch PhoneFactory.smali to construct your class instead of RIL:
find "RIL" word (there will be 2 entries) and replace them to "LGEQualcommRIL".
Fuih..... That what I've learned of porting MIUIv4 guys...
Soon will be born more porters... Great!!!
Happy porting...!!!!
CacingKalung said:
I want to share this to make everyone of you know how I port it to our device so I shouldn't share it to just one or two people.
It is based on this proxuser thread, credit goes to him. I just make it details and make it work for our device.
We will make MIUIv4 framework to run on top of CM9/AOSP base. So we should prepare CM9 base and MIUIv4 to port. You can use any MIUIv4 to port but you can try by choosing the one which similar hardware with our device.
- Prepare extracted CM9 base rom in folder A, and extracted MIUIv4 rom in folder B. Copy file framework.jar, framework-res.apk and services.jar at /system/framework from CM9 folder save them in folder C. After here, we will port from folder B to folder A.
- Remove folder /system/framework and /system/app in folder A and replace them from folder B.
- Remove /system/app/nfc.apk, since our device don't have this feature.
- Copy all *.db and *.td at /system/etc from B to A.
- replace media folder in /system/media at folder B to folder A.
- copy content-types.properties file to /system/lib from B to A.
- copy miui-framework.xml at etc/permission
- copy /system/xbin/invoke-as and /system/xbin/su from folder B to A
- copy /system/lib/liblbesecs.so from folder B to A
- add this lines to updater-script file in folder B:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
- change values from build.prop
ro.build.version.incremental=2.x.x (version number of MIUIv4)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
Test the new port:
Now pack folder B to zip files and sign it and flash it using CWM. You should prepare the other working rom to get back to previous rom .
Use adb logcat to debug, and see the result. If it doesn't shown anything, then we should replace libandroid_runtime.so from MIUIv4, but not in my case, I kept it from CM9.
Our device is based on Qualcomm so with our new CM9 theme engine will affected, it will got hung on boot with unresolved at android/content/res/AssetManager. Just break the logcat when it shown some lines with "died" things and scroll up, you'll find it.
So here is the next step which will take more time. You should able to decompile and recompile jar/apk files, Google it for that, it's very easy to do that. We'll go for smaling and baksmaling here. And for comparing, use an application such as winmerge for windows or Meld for linux.
Remember that we have some files in folder C from CM9 and we'll use that as source for smaling steps.
- find /smali/android/content/res/assetManager.smali from framework.jar on Miuiv4 and compare it with the same file from CM9 one, replace all missing lines.
- copy missing method in /smali/android/hardware/Camera.smali
- copy missing method in /smali/android/os/Power.smali, method SetUnstableMemoryState the important one.
- copy /smali/android/server/BluetoothA2dpService*.smali
- copy /smali/android/content/res/PackageRedirectionMap*.smali
- copy /smali/org/codeaurora/Performance.smali
- copy smali/android/media/MediaRecorder*.smali
- copy /smali/android/view/GLES20Canvas*.smali
- copy /smali/android/net/wifi/WifiNative.smali
- copy /smali/android/graphics/paint*.smali
I found them by watching logcat, fixing one by one error on each boot, so now you can skip much time by using this guide.
If still stuck, I look for some lines like this:
E/dalvikvm( 234): ERROR: couldn't find native method
E/dalvikvm( 234): Requested: Lxxxxxxx/xxxxxxx/xxxxxxxx;.yyyyyyyyyyyyyZ)I
E/JNIHelp ( 234): RegisterNatives failed for 'xxxxxxx/xxxxxxx/xxxxxxxx', aborting
F/libc ( 234): Fatal signal zzzzzz at 0xdeadbaad (code=1)
Then the problem is in xxxxxxx/xxxxxxx/xxxxxxxx.smali file, try to fix it first by adding missing lines in it if possible or copy xxxxxxx/xxxxxxx/xxxxxxxx*.smali if there is to many different.
You should see the MIUIv4 lockscreen if you done fixing all those problem.
After this we can fixing anothers, like 2G/3G data and headset.
To fix headset, it's in WiredServiceObserver.smali in framework-res.apk, find the path with contain "h2w" word with "headset_sensor" word, remember just paths string, no else. It should be 3 words to replace.
Now to fix 2G/3G data,
replace RIL*.smali and copy LGEQualcommRIL*.smali at path
/smali/com/android/internal/telephony ín framework.jar.
You also need to patch PhoneFactory.smali to construct your class instead of RIL:
find "RIL" word (there will be 2 entries) and replace them to "LGEQualcommRIL".
Fuih..... That what I've learned of porting MIUIv4 guys...
Soon will be born more porters... Great!!!
Happy porting...!!!!
Click to expand...
Click to collapse
owh yeah so I just forget change the ril.smail on the framework..try again..thanks my sifu...
any plan for jelly bean port??
Sent from my FIH-FB0 using xda
2.6.15 and 2.6.22 boot loop
comdevx said:
2.6.15 and 2.6.22 boot loop
Click to expand...
Click to collapse
if you get boot loop,now you almost get the miui working and please follow this step
So here is the next step which will take more time. You should able to decompile and recompile jar/apk files, Google it for that, it's very easy to do that. We'll go for smaling and baksmaling here. And for comparing, use an application such as winmerge for windows or Meld for linux.
Remember that we have some files in folder C from CM9 and we'll use that as source for smaling steps.
- find /smali/android/content/res/assetManager.smali from framework.jar on Miuiv4 and compare it with the same file from CM9 one, replace all missing lines.
- copy missing method in /smali/android/hardware/Camera.smali
- copy missing method in /smali/android/os/Power.smali, method SetUnstableMemoryState the important one.
- copy /smali/android/server/BluetoothA2dpService*.smali
- copy /smali/android/content/res/PackageRedirectionMap*.smali
- copy /smali/org/codeaurora/Performance.smali
- copy smali/android/media/MediaRecorder*.smali
- copy /smali/android/view/GLES20Canvas*.smali
- copy /smali/android/net/wifi/WifiNative.smali
- copy /smali/android/graphics/paint*.smali
---------- Post added at 06:20 AM ---------- Previous post was at 06:17 AM ----------
abenagiel said:
any plan for jelly bean port??
Sent from my FIH-FB0 using xda
Click to expand...
Click to collapse
i think for driver rom jelly bean not still support for driver qulcomm(adreno) and need new baseband...
comdevx said:
2.6.15 and 2.6.22 boot loop
Click to expand...
Click to collapse
Read carefully my guide and if ypu still stuck at boot, look at logcat and look at deadbad fatal error and again... follow above guide at deadbaad error.
Sent from my bike using Tapatalk
CacingKalung said:
So here is the next step which will take more time. You should able to decompile and recompile jar/apk files, Google it for that, it's very easy to do that. We'll go for smaling and baksmaling here. And for comparing, use an application such as winmerge for windows or Meld for linux.
Remember that we have some files in folder C from CM9 and we'll use that as source for smaling steps.
- find /smali/android/content/res/assetManager.smali from framework.jar on Miuiv4 and compare it with the same file from CM9 one, replace all missing lines.
- copy missing method in /smali/android/hardware/Camera.smali
- copy missing method in /smali/android/os/Power.smali, method SetUnstableMemoryState the important one.
- copy /smali/android/server/BluetoothA2dpService*.smali
- copy /smali/android/content/res/PackageRedirectionMap*.smali
- copy /smali/org/codeaurora/Performance.smali
- copy smali/android/media/MediaRecorder*.smali
- copy /smali/android/view/GLES20Canvas*.smali
- copy /smali/android/net/wifi/WifiNative.smali
- copy /smali/android/graphics/paint*.smali
I found them by watching logcat, fixing one by one error on each boot, so now you can save much time by using this guide.
If still stuck, I look for some lines like this:
E/dalvikvm( 234): ERROR: couldn't find native method
E/dalvikvm( 234): Requested: Lxxxxxxx/xxxxxxx/xxxxxxxx;.yyyyyyyyyyyyyZ)I
E/JNIHelp ( 234): RegisterNatives failed for 'xxxxxxx/xxxxxxx/xxxxxxxx', aborting
F/libc ( 234): Fatal signal zzzzzz at 0xdeadbaad (code=1)
Then the problem is in xxxxxxx/xxxxxxx/xxxxxxxx.smali file, try to fix it first by adding missing lines in it if possible or copy xxxxxxx/xxxxxxx/xxxxxxxx*.smali if there is so many different lines.
You should see the MIUIv4 lockscreen if you done fixing all those problem.
After this we can fixing anothers, like 2G/3G data and headset.
To fix headset, it's in WiredServiceObserver.smali in framework-res.apk, find the path string which contain "h2w" word with "headset_sensor" word, remember just paths string, no else. It should be 3 words to replace.
Now to fix 2G/3G data,
replace RIL*.smali and copy LGEQualcommRIL*.smali at path
/smali/com/android/internal/telephony ín framework.jar.
You also need to patch PhoneFactory.smali to construct your class instead of RIL:
find "RIL" word (there will be 2 entries) and replace them to "LGEQualcommRIL".
Fuih..... That what I've learned of porting MIUIv4 guys...
Soon will be born more porters... Great!!!
Happy porting...!!!!
Click to expand...
Click to collapse
Hey bro replace text from d smali files to cm9 files and repack cm9 jar or miui jar??
a2441918 said:
Hey bro replace text from d smali files to cm9 files and repack cm9 jar or miui jar??
Click to expand...
Click to collapse
from cm9 to miui. repack miui jar.
CacingKalung said:
from cm9 to miui. repack miui jar.
Click to expand...
Click to collapse
bro in cm9 base assetmanager.smali its given like this
invoke-direct {v0}, Ljava/lang/Object;-><init>()V
but in miui, assetmanager.smali is given like
invoke-direct/range {v0 .. v0}, Ljava/lang/Object;-><init>()V
So replace only the missing lines or also correct these lines??
and bro in cm9 bluetootha2dpservice$1.smali the line is
move-result-object v5
.line 113
.local v5, action:Ljava/lang/String;
const-string v28, "android.bluetooth.adapter.action.STATE_CHANGED"
but in miui bluetootha2dpservice$1.smali
.line 72
invoke-virtual {p2}, Landroid/content/Intent;->getAction()Ljava/lang/String;
what to do bro??
for asset manager, just missing lines, no need to correct others.
For bluetootha2dp, replace smali files.
Sent from my bike using Tapatalk 2
Hey mate, nice guide, seems that partially matches porting of TouchWiz I'm doing right now, some errors are similiar. Will keep track on this while porting.
mesaj said:
Hey mate, nice guide, seems that partially matches porting of TouchWiz I'm doing right now, some errors are similiar. Will keep track on this while porting.
Click to expand...
Click to collapse
Good... hope you can share your work with us so we can taste it
Sent from my bike using Tapatalk 2
CacingKalung said:
Good... hope you can share your work with us so we can taste it
Sent from my bike using Tapatalk 2
Click to expand...
Click to collapse
Unfortunatelly, I can't as I'm porting to Samsung Galaxy S2 from S3 May just share some experiences during process.
There's a lot of work with resizing & need first to boot it, that I'm currently working on.
I've got a request on this guide, just to add some more bbcode formatting.
Thanks for all this, hope It'll be helpful.
mesaj said:
Unfortunatelly, I can't as I'm porting to Samsung Galaxy S2 from S3 May just share some experiences during process.
There's a lot of work with resizing & need first to boot it, that I'm currently working on.
I've got a request on this guide, just to add some more bbcode formatting.
Thanks for all this, hope It'll be helpful.
Click to expand...
Click to collapse
No problem... good luck.
Sent from my bike using Tapatalk 2
@cacingkalung
hye mate I need you help this is framework MIUI.US the latest..can you decomplie this framework.jar because I can't get decomplie this file and get error when decomplie and complied using window,can you only help me replaced the RIL.smail and LEG.smail to get mobile data working 2g/3g...
thanks..hope you will help me
elol said:
hye mate I need you help this is framework MIUI.US the latest..can you decomplie this framework.jar because I can't get decomplie this file and get error when decomplie and complied using window,can you only help me replaced the RIL.smail and LEG.smail to get mobile data working 2g/3g...
thanks..hope you will help me
Click to expand...
Click to collapse
@Elol, Yes, I also faced problems when decompiling MIUI.us framework.jar using windows.
Related
I'm trying to edit framework-res.apk so I can theme my rom. Are these the correct steps?
pull framework-res.apk from my phone
decompile the apk
make the changes
rebuild the apk
sign
zipalign
push apk back to device
I'm not too sure on this method as after I pushed back my modified apk, I get a load of force close errors
Any advice would be welcome
don't sign and don't zipalign and all are fine
I tried without sign and zipalign but the rom wouldnt boot. If I sign, I get force close errors
Does the rom need to be deoxed?
How is your process to decompile and recompile what tools do you use
vibez said:
I tried without sign and zipalign but the rom wouldnt boot. If I sign, I get force close errors
Does the rom need to be deoxed?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Is this an ODEXed ROM or a deOXEDed ROM? You can't mix and match. If you're not ODEXing any APKs after you've modified them then you need to make sure all APKs are deOXEDed.
setenza01 said:
How is your process to decompile and recompile what tools do you use
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I use apk manager to decompile and rebuild
Benjamin Dobell said:
Is this an ODEXed ROM or a deOXEDed ROM? You can't mix and match. If you're not ODEXing any APKs after you've modified them then you need to make sure all APKs are deOXEDed.
Click to expand...
Click to collapse
It is a stock rom but there is no framework-res.odex does that mean it doesn't need deodexing even though there are odex files for every other apk in my system folder?
maybe this little monster is some help to you:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
FadeFx said:
maybe this little monster is some help to you:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
Click to expand...
Click to collapse
Nice app but this theme also needs .xml changes which this app doesnt support
ok, i put him a note in his thread about the xml changing issue, we will see what hes answer will be...
edit:
also this software could do the trick: http://android.modaco.com/content/t-mobile-pulse-pulse-modaco-com/302404/ande-android-design-editor/
I've been playing around a little more today and it seems the issue is that no tool can rebuild the xml files correctly, they seem to be compressed/encoded.
Has anyone been able to edit an xml file in framework-res.apk and have the phone read it properly?
vibez said:
I've been playing around a little more today and it seems the issue is that no tool can rebuild the xml files correctly, they seem to be compressed/encoded.
Has anyone been able to edit an xml file in framework-res.apk and have the phone read it properly?
Click to expand...
Click to collapse
Refer to my signature. Apk manager.
Edit : just read ur op.
Never sign the system apk's. Simply keep the original signatures intact and after recompiling them, re-include them.
So here are the rules u must follow :
If u've modified the manifest.xml, u must stop core, push the apk, start core or push the apk while in recovery.
If u've modified anything else, a simple push / reboot will do the trick.
Note, u cannot flash a modified system apk the first time (as in on a clean boot), u must flash the original rom, let it build the dex's and then flash ur modified apk.
Daneshm90 said:
Refer to my signature. Apk manager.
Edit : just read ur op.
Never sign the system apk's. Simply keep the original signatures intact and after recompiling them, re-include them.
Click to expand...
Click to collapse
Hi, I am already using apk manager but the xml files it creates do not seem to work.
To prove this, I have done a test. See the attached xml files,
original_stat_sys_battery.xml was extracted from the original framework-res.apk
I then used apk manager to decompile and then recompile the same apk without making any changes.
recompiled_stat_sys_battery.xml is this recompiled file
I then opened up both files and they look different to me
vibez said:
Hi, I am already using apk manager but the xml files it creates do not seem to work.
To prove this, I have done a test. See the attached xml files,
original_stat_sys_battery.xml was extracted from the original framework-res.apk
I then used apk manager to decompile and then recompile the same apk without making any changes.
recompiled_stat_sys_battery.xml is this recompiled file
I then opened up both files and they look different to me
Click to expand...
Click to collapse
That shouldn't concern u. Apktool's method of rebuilding the apk/arsc file is slightly different than how android originally builds an apk. What should concern u is if the apk simply works. Now when u decompile the apk, can u check the log to see if it reports of any missing resources, if it doesn't ur fine. So decompile the apk, make ur changes, recompile the apk, move the original meta-inf folder into ur new apk and push it to ur phone following the guidelines in my previous post. if it causes problems, post ur log and i'll take a look.
Ok this time I have added meta-inf to the new apk, pushed it to my phone and the phone hangs on boot.
Here is my log
--------------------------------------------------------------------------
|08/08/2010 -- 18:36:30.87|
--------------------------------------------------------------------------
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the path specified.
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
'adb' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged.apk
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged-signed.apk
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged-unsigned.apk
The system cannot find the file specified.
I: Loading resource table...
I: Decoding resources...
I: Copying assets and libs...
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'keyguard_password_attempts_count_pin_code' has no default translation in C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\other\..\out\res; found: fr ko
I: Building apk file...
Click to expand...
Click to collapse
Oh lol i meant the log of ur phone.
Use adb logcat
lol ok, at which point should I run logcat - after the hang or as soon as I switch the phone on?
vibez said:
lol ok, at which point should I run logcat - after the hang or as soon as I switch the phone on?
Click to expand...
Click to collapse
When u switch phone On.
Ok here you are
vibez said:
Ok here you are
Click to expand...
Click to collapse
Heres ur culprit
Code:
java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for AndroidManifest.xml
Now seems u modified the androidmanifest.xml ? If u didn't then heres my recommendation, copy over the original androidmanifest.xml from the original apk.
Hi,
i'am searching for a guide how to manipulate correctly the framework-res.apk.
All ways i have tested fails.
I would modify some symbols in Notification bar (battery 1%) but all Time the my Phone run into bootloop or all Application Crashes after Startup.
I've tryed Apk Manager 4.9 / and Manualy with apktool.
Help plz .....
what i did :
1-extract apk (i use 7zip/WinRAR)
2-edit/replace image file(s)
3-repack with zero compression level ('store' level)
4-sign the apk
5-replace file using apk or create flashable recovery zip.
regards.
signing the framework-res.apk will not work.. will make the device go into bootloop
what you need is extract the framework-res.apk using apktool and edit the things you want and then compile it again using apktool .... now open the original framework-res.apk and replace the file resources.arsc with the edited compiled one..
this way you will retain the signature of the original framework-res.apk
PapaDocta said:
signing the framework-res.apk will not work.. will make the device go into bootloop
what you need is extract the framework-res.apk using apktool and edit the things you want and then compile it again using apktool .... now open the original framework-res.apk and replace the file resources.arsc with the edited compiled one..
this way you will retain the signature of the original framework-res.apk
Click to expand...
Click to collapse
But when i add some new Files and Edit some XML the Sign will be Corrupted ?
no it won't...
You need to do two copies.. the original file and the moded one...
1. make a backup of the original file
2. extract the original file using apktool
3. edit and modify anything you like
4. compile the edited file
5. rename the compiled file to framework-res.zip and take the modified resources.arsc
6. using winrar or 7zip open (to view not extract) the backed up framework-res.apk
7. place the moded resources.arsc into the backed up framework-res.apk
by doing this you retain the original signature of the backed up file and not breaking it..
Thx, will test it ;-)
kowalski99 said:
But when i add some new Files and Edit some XML the Sign will be Corrupted ?
Click to expand...
Click to collapse
Android system, signs system apk's on boot, you shouldnt sign them
Sent from my Desire HD using Tapatalk
My signed apk just work well.
AFAIK, we only cant re-sign htc's apk.
PapaDocta said:
signing the framework-res.apk will not work.. will make the device go into bootloop
what you need is extract the framework-res.apk using apktool and edit the things you want and then compile it again using apktool .... now open the original framework-res.apk and replace the file resources.arsc with the edited compiled one..
this way you will retain the signature of the original framework-res.apk
Click to expand...
Click to collapse
The right approach always depends, what you want to change. There is no need to decompile, if you only change a few standard png. If you change xml in values folder like color, styles or arrays, you can certainly not delete resources.arsc - resources have nothing to do with the signature anyway. So if you want to play safe, you should insert the original Meta-Inf (signature) and Android Manifest after compile. It is also recommended to zipalign the final apk in order to reduce RAM usage.
thanks he_stheone64 for the clarification.. i reached that conclusion based on my own research on the net and yeah i used to change the XML files to add language support and that the only way that worked with me..
And be sure to have a working and up-to-date sdk before trying to use apktool...
First, using a old sdk release i got a partially working result (few graphics bugs and strange reboots), then with a badly updated sdk on top off the old i got apktool making many errors. Finally, re-installing the last sdk from start i got apktool and my resulting apk working correctly.
Does anyone know how to enable USB Mass Storage on our phones under CM10.1? I've searched around and found this thread. But since I'm not familiar with changing build.prop I don't dare to do it myself. There are some CWM .zip files around to enable it, but they are on other phone's forums and I'm sure they just replace/change the build.prop so it's definitely not a good idea to flash those on a different phone than the ones they were intended for....
Long story short, does anyone know how to enable it on ours?
TIA!
Update on the process:
I was able to edit the build.prop according to the instructions, but that alone doesn't seem to do anything.
So I decided to try the next step, but where it tells me to do the changes below I wasn't sure what to do.
Thom75 said:
in framework-res.apk/res/xml/storage_list.xml
where oryginal line look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
after change look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:allowMassStorage="true" android:maxFileSize="4096" />
Click to expand...
Click to collapse
I was able to find the framework-res.apk file, copied to my computer and tried to open it with an XML editor... looked too complicated so I left it alone.
Does anyone know how to mess with that?
Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you
Sivvis said:
Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you
Click to expand...
Click to collapse
Thank you very much for your help! I didn't know apk files were just a compressed library of other files.
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
I attached the file below:
Apoena said:
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
Click to expand...
Click to collapse
Well, how about decompiling the .apk file with APK Tools instead of just opening it with WinRar? :laugh:
Yes, now I get a clean, editable, decompiled xml file.
I'll try editing both when I get home tonight and will post the results.
I guess this is a problem because of the emulated layout. There is a trick with setprop sys.usb.storage.config mass_storage but it does not work.
Keep me informed if you find something valuable (i'm on original CM10.1, latest nightly 0423 actualy).
Ok, here's the update from last night:
I started over since I flashed the nightly, which is good so I restarted with a clean slate.
- Edited build.prop - OK
- Copied framework-res.apk to my computer
- Decompiled framework-res.apk
- Edited storage_list.xml
- Recompiled framework-res.apk with new storage_list.xml
- Copied framework-res.apk back to my phone
- Deleted original framework-res.apk
- ...... instant restart & bootloop before I could paste the new framework-res.apk in its place
No big deal, just restored a nandroid backup I made before messing with anything and I'm back in business.
Apparently you can't mess with the framework-res.apk while your phone is on (with the OS running)... so now I need to research the right way to push/pull these files from ADB while on CWM recovery. I appreciate if someone could point me in the right direction since I'll be busy at work today.
To be honest, my gut feeling tells me that this is not going to work anyway. But look at what I learned so far... two days ago I wouldn't even think of compiling/decompiling anything... this is what XDA is all about, right?
Imho, the framework_res.apk and various tricks are all enabling or disabling a sys.usb.storage.config key. I'm not understanding nor finding informations about CM10.1 emulated layout, and if there are any reasons to forbid mass storage (because, yes, it seems it is disabled because it is not compatible).
This is something i have hard time with. On Android, you have tons of improvement for rom or kernel XY, but generally undocumented. If you apply this 'per device', the information is very fragmented and difficult to grab.
I was looking for a simple brief on base MTD partitions layout for LG P880, it seems the only way to have this is to dig KDZ files. Perhaps a Wiki would help the wannabe contributers like me to start ?
Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????
Nooby305 said:
Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????
Click to expand...
Click to collapse
Flash the latest nightly. MTP is working and you cab transfer files that way.
Sent from my tree using a ladder
effectively, if you are flashing for USM, you should stay on LG stock.
I know that the topic got a little old but I'd like to refresh it since more people (e.g. Ubuntu users) could be interested in enabling Mass Storage.
What I've done is:
1) pulled /system/framework/framework-res.apk
2) decompiled it with APKtool
3) added
Code:
android:allowMassStorage="true"
in storage_list.xml
4) builded a new apk
then I've rebooted my phone into recovery and (@Apoena you may be interested in it - there is a possibility to access /system through adb connected with phone in recovery mode) pushed the new framework-res.apk. I've also changed the entry in build.prop to
Code:
persist.sys.usb.config=mass_storage,adb
Everything seemed fine until I've tried to reboot the phone: instead of CM boot logo I got a black screen. Anybody has an idea what went wrong (maybe something during recompilation of the apk)?
And of course sorry for any language mistakes, I'm not a native speaker
Hi, it seems some dear users have problems with Miui V5 framework and miui's applications decompiling proccess.
let's begin!
for this job, Im editing the APK Multitool, and all credits will goes to his developer. [raziel23x]
original thread
what's new on this?
changed the aapt to miui compatible, added miui frameworks to default list, added additional frameworks, also you can pull back the files from the phone via adb command.
i wrote it before, original thread
-------------------------------------------------------------------------------------------------------------------------------------------------------------
for version 11.0.1.2 and older!
Download the Attached file.
extract it.
copy these files
Code:
framework-res.apk
framework-miui-res.apk
twframework-res.apk
MiuiSystemUI.apk
from Miui Rom into other folder.
run, Setup.bat script.
Select option 2:
Code:
*
* 2. Installing Framework-Res
* This Will install one of the Framwork-Res Files for 1.x/2.x/3.x/4.x
* This Feature also will install any of the other Dependencies needed
* In order to use this feature make sure to drop all of the needed files
* into the other Folder or else this script will not find them *
*
in next window, install these frameworks by entering related numbers. install it as this order and sequence
Code:
Install framework-res.apk
Install twframework-res.apk
Install Additional Frameworks
Install framework-miui-res.apk
Install MiuiSystemUI.apk
after installing, enter the "9" to get back to main screen.
run setup by entering "3".
Code:
3. Setup Directories
This will setup the appropate directories needed by Apk Multi-Tools
(This script only needs to be ran for first time users do not use if your
Just updating from previous Version
now new folders will create on main folder of this apk multi tool.
Framework's Description
- 1 = framework-res.apk
- 2 = twframework-res.apk
- 3 = additional frameworks
- 4 = additional frameworks
- 5 = additional frameworks
- 6 = framework-miui-res.apk
- 127 = SystemUI.apk
Version 1.11.0.3 XIAOMI Phones.
1- Download Version 1.0.11.3 [[XIAOMI]MIUI_V5_APKMULTITOOL_1.0.11.3.zip] and extract it.
2- Copy MiuiSystemUI.apk, framework-res.apk and framework-miui-res.apk from your rom or phone into other folder.
3- Run Setup.bat file, choose option 2 and then select option 1 for automatically installing all frameworks.
or you can install frameworks manually
Code:
2. Install framework-res.apk
3. Install dummy frameworks
4. Install framework-miui-res.apk
4- from main menu, run option 3
Code:
3. Setup Directories
This will setup the appropate directories needed by Apk Multi-Tools
(This script only needs to be ran for first time users do not use if your
Just updating from previous Version)
best regards.
How to Edit framework-miui-res.apk?
copy framework-miui-res.apk into "place-apk-here-for-modding" folder, run "Script.bat" file.
choose your project , by entering the " 24 Set current project" [24].
the select your project with related number.
decompile apk.
Code:
9 Decompile apk
when the framework-miui-res.apk get decompiled, goto project folder and on the framework-miui-res.apk , open the "apktool.yml" file via notepadd++.
you will see like this one:
Code:
version: 1.5.2
apkFileName: framework-miui-res.apk
isFrameworkApk: true
usesFramework:
ids:
- 1
sdkInfo:
minSdkVersion: '16'
targetSdkVersion: '16'
packageInfo:
cur_package: miui
orig_package: miui
compressionType: true
add additional frameworks , just like below one
Code:
version: 1.5.2
apkFileName: framework-miui-res.apk
isFrameworkApk: true
usesFramework:
ids:
- 1
- 2
- 3
- 4
- 5
sdkInfo:
minSdkVersion: '16'
targetSdkVersion: '16'
packageInfo:
cur_package: miui
orig_package: miui
compressionType: true
save the file.
now go and edit this file, at final you can compile it.
for compile you can use "11 Compile System APK files" option.
if you have any problem, please upload the "APK-Multi-Tool.log" file and tell your problem.
Changelog:
version 1.0.11.1 initial release
version 1.0.11.2 , fixed framework installing.
Version 1.0.11.3 , specially for XIAOMI phones and updated apktool to version 1.5.3 snapshot.
+ fixed and removed some scripts
+ all in one framework installer [ option 1]
+ added miui JB frameworks [ ID 2 ~ ID5]
M_J_Nazari said:
if you have any problem, please upload the "APK-Multi-Tool.log" file and tell your problem.
Click to expand...
Click to collapse
Thank you Nazari!
I dont know if this script is only meant to work with SGS III files...
I followed your instructions using MI-2 files (without twframework-res.apk of course).
And after de-compiling the apk I can't compile it back.
I'm getting:
error occurred, please check the log (option 21)
Click to expand...
Click to collapse
Btw I notice that inside the apktool.yml
I got
compressiontype: false
Click to expand...
Click to collapse
This is my log:
--------------------------------------------------------------------------
|Sun 06/02/2013 -- 17:55:49.16|
--------------------------------------------------------------------------
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)
I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: C:\Users\Sagi\apktool\framework\1.apk
I: Loaded.
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Done.
I: Copying assets and libs...
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.err.CantFindFrameworkResException
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:358)
at brut.androlib.Androlib.buildResources(Androlib.java:283)
at brut.androlib.Androlib.build(Androlib.java:206)
at brut.androlib.Androlib.build(Androlib.java:176)
at brut.apktool.Main.cmdBuild(Main.java:228)
at brut.apktool.Main.main(Main.java:79)
Caused by: brut.androlib.err.CantFindFrameworkResException
at brut.androlib.res.AndrolibResources.getFrameworkApk(AndrolibResources.java:544)
at brut.androlib.Androlib.parseUsesFramework(Androlib.java:508)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:336)
... 5 more
Click to expand...
Click to collapse
I'm guessing it is because of the 'twframework-res.apk' which i dont have...(MI-2 not Samsung).
SagiMedina said:
Thank you Nazari!
I dont know if this script is only meant to work with SGS III files...
I followed your instructions using MI-2 files (without twframework-res.apk of course).
And after de-compiling the apk I can't compile it back.
I'm getting:
Btw I notice that inside the apktool.yml
I got
This is my log:
I'm guessing it is because of the 'twframework-res.apk' which i dont have...(MI-2 not Samsung).
Click to expand...
Click to collapse
W: Could not find sources
so, don't change the "apktool.yml" file and then compile it. see the result. maybe your phone doesn't boot!!
oh,,, i forget to add framework 5 to package, download it and copy to "C:\Users\Sagi\apktool\framework\" folder. i will update the package as soon.
or you can use new package, i added new description and new fixed version.
M_J_Nazari said:
W: Could not find sources
so, don't change the "apktool.yml" file and then compile it. see the result. maybe your phone doesn't boot!!
oh,,, i forget to add framework 5 to package, download it and copy to "C:\Users\Sagi\apktool\framework\" folder. i will update the package as soon.
or you can use new package, i added new description and new fixed version.
Click to expand...
Click to collapse
After I used the new package I succeed to compile it back but the phone doesn't boot.
In apktool.yml I add only
-1
-3
-4
-5
-2 and -6 gave me errors.
I noticed that the new apk size is smaller then the original.
Sent from my MI 2
SagiMedina said:
After I used the new package I succeed to compile it back but the phone doesn't boot.
In apktool.yml I add only
-1
-3
-4
-5
-2 and -6 gave me errors.
I noticed that the new apk size is smaller then the original.
Sent from my MI 2
Click to expand...
Click to collapse
do a search into framework folder, if there is another apk file, i think you need to install this framework. i don't know about the xiaomi phones like mi2 or another.
and, are you sure that you did all steps perfectly?
could you please tell us what did you exactly for compiling process? i mean after entering option "11".
M_J_Nazari said:
and, are you sure that you did all steps perfectly?
could you please tell us what did you exactly for compiling process? i mean after entering option "11".
Click to expand...
Click to collapse
I followed the steps as you wrote except with the twframework, then I edit the apktool.yml
But instead of adding:
-1 to -6
I only add
-1, -3,-4,-5
I edit the style following your guide,
Then I compiled back by entering option 11, copied the 'unsignedframework-miui-res.apk' to my phone and renamed it to 'framework-miui-res.apk' and past it in system/framework. The phone rebooted but got stuck after the bootanimation.
Sent from my MI 2
SagiMedina said:
I followed the steps as you wrote except with the twframework, then I edit the apktool.yml
But instead of adding:
-1 to -6
I only add
-1, -3,-4,-5
I edit the style following your guide,
Then I compiled back by entering option 11, copied the 'unsignedframework-miui-res.apk' to my phone and renamed it to 'framework-miui-res.apk' and past it in system/framework. The phone rebooted but got stuck after the bootanimation.
Sent from my MI 2
Click to expand...
Click to collapse
what's about the keep folder?
M_J_Nazari said:
what's about the keep folder?
Click to expand...
Click to collapse
What is the keep folder?
Sent from my MI 2
SagiMedina said:
What is the keep folder?
Sent from my MI 2
Click to expand...
Click to collapse
ok, i think it is need to know how to work with apk multi tool.
1- decompie
2- edit your framework
3- enter option 11 to compile
4- programs will ask you about the modification , just like this:
Code:
Building Apk
Aside from the signatures, would you like to copy
over any additional files that you didn't modify
from the original apk in order to ensure least
# of errors (y/n)
Type input:
5- enter " y ' and then press enter.
6- wait for programs, to show you this message
Code:
Everything is Ok
Files: x
Size: xxxxx
Compressed: xxxxx
In the APK Multi-Tools folder u'll find
a keep folder. Within it, delete
everything you have modified and leave
files that you haven't. IF you have modified
any xml, then delete resources.arsc from that
folder as well. Once done then press enter
on this script.
Press any key to continue . . .
7- don't touch anything, minimize Apk Multitool program window ,
8-Go back to the main folder of apk multi tool , you will find the "keep" folder.
goto keep folder and delete thisfile "resources.arsc"
9- get back to Apk Multitool program and hit any key to create a new framework-miui-res.apk file with this name
"unsignedframework-miui-res.apk" file.
10- rename it and copy to your phone, do a permission
you can do it via root Explorer
or terminal command
Code:
chmod 0644 /system/framework/framewok-miui-res.apk
or adb commnad
Code:
adb shell chmod 0644 /system/framework/framewok-miui-res.apk
M_J_Nazari said:
...
Click to expand...
Click to collapse
Still no luck Nazari, did everything like you said...
I cant get pass the boot animation once i replace the framework,
why is the new apk is smaller? is it normal?
SagiMedina said:
Still no luck Nazari, did everything like you said...
I cant get pass the boot animation once i replace the framework,
why is the new apk is smaller? is it normal?
Click to expand...
Click to collapse
its normal, you can select compression level by hitting option "21".
but upload your framework-miui-res.apk here to check it and i will make changes to that.
M_J_Nazari said:
its normal, you can select compression level by hitting option "21".
but upload your framework-miui-res.apk here to check it and i will make changes to that.
Click to expand...
Click to collapse
Thanks Nazari!!!
SagiMedina said:
Thanks Nazari!!!
Click to expand...
Click to collapse
it seems xiaomi uses different framework and aapt version, you need to ask them.
M_J_Nazari said:
it seems xiaomi uses different framework and aapt version, you need to ask them.
Click to expand...
Click to collapse
If ill get these different framework and aapt version, I only need to replace them with the those in the 'other' folder?
Guys, you don't have a clue what that other frameworks are for, do you? You can't miss nr 1 or 6 or 2 framework in apktool.yml because that will never work! Apktool.yml is fine and should look like in the first post.
I think your main issue is that you don't know frameworks IDs?
This:
Code:
1. Install framework-miui-res.apk
2. Install framework-res.apk
3. Install twframework-res.apk
6. Install MiuiSystemUI.apk
7. Install Additional Frameworks
Is wrong!
How to tell what ID framework has?
Run this command:
Code:
apktool if framework-miui-res.apk
You will get:
Code:
I: Framework installed to: /home/acid/apktool/framework/6.apk
So framework-miui-res.apk is ID = 6.
Try to install regular framework-res.apk. You will get ID = 1.
To complete the gap between ID1 and ID6 you have to install proper frameworks. AND MiuiSystemUi is NOT a framework! Thats nonsense!
ID is 127 which is out of range.
You have to install framework files that have proper ID from 1 to 6.
ID1:
framework-res.apk
ID2:
frameworks from producer base. So this is twframework-res for Samsung devices, com.htc.resources.apk for HTC, SemcGenericUxpRes.apk for Sony... etc. That doesnt really matter. ID2 frameworks are used when you recompile stock apps like Samsung TW apps or HTC apps (HTCAlbum, Music etc). If you just want to recompile framework-miui-res and boot rom then you can use any ID2 framework or just a dummy file.
ID3:
This is com.htc.dummyskin.apk. Just search for it. You can find it in HTC One roms (One X and One S). Search in MIUI roms for that devices (but with stock HTC based MIUI!). Or grab the file from micode.
ID4:
This is framework-htc-res.apk. Again. search for it. Also HTC roms should have this or grab dummy framework from micode.
ID5:
From micode.
ID6:
framework-miui-res.apk
Dummy frameworks from MiCode:
https://github.com/MiCode/patchrom_build/tree/jellybean/res
You can use 3-5.apk to fill the gap. But still I advice you to use proper ID2 frameworks in case you would like to compile stock apps.
And for last install frameworks in order:
Code:
apktool if framework-res.apk
apktool if twframework-res.apk (or htc or dummy)
apktool if 3.apk
apktool if 4.apk
apktool if 5.apk
apktool if framework-miui-res.apk
That should allow you to boot the rom. Also make sure you have miui aapt and apktool 1.5.3.
thanks a lot @ Accidd for very good explanation.
i worte it for samsung devices, and it seems its fine. this script will install frameworks automatically.
but for other devices i will update the application again, so if we want to compile Xiaomi frameworks , we need to use dummy framework for ID number 2?
It doesn't matter which device you do. You always have to install all frameworks.
Wysłane z MI-2
M_J_Nazari said:
i will update the application again,
Click to expand...
Click to collapse
Thanks Nazari!
And thank you Acid for clearing things!
Sent from my MI 2
Version 1.0.11.3 added to first post to compile Xiaomi phones frameworks.
[Tutorial]How To Swap Internal & External StorageThis Swap Mod is based on This Thread
So Thanks and Credit should be Kyrie1965
I think this mod will be compatible with all stock rom and stock based custom rom (I already tested on Stock ROM, Revelation HD, and some people already used at Warrior ROM). This mod compatible with XT, XTX and XV
....and maybe with another Xperia 2012 Phone lines
ATTENTION:
I'm not responsible with any problems of your phone/sdcard, or any effect that could be happen.
Please make CWM Backup before do any mod.
And it's would be better if you make backup of your sdcard or internal storage first.
Wtih this mod, System will work as default, SDCard0 will still be Internal Storage, SDCard1 will still be real SD-card or Ext_Card. But after flash this mod, you can move installed apk to SDCard1 or External Storage through Titanium Backup.
You can look all your storage under /mnt folder by any File Explorer for Rooted Device from Playstore.
Here we go......
WHAT WE NEED?
Deodexed ROM
Apktool 4.2.2 : How to Decompile/Compile/Sign Apk/Jar from Rizal Lovins, see this thread
Winrar
Windows File Explorer or Total Commander
Environment.smali, download here
HOW TO
STEP 1 - PREPARATION
Follow instruction from Rizal Lovins thread, prepare any files needed (Android SDK, Apktools and Notepad++) and installed them all
Pull out your framework.jar files from /system/framework folder and copy to PC (Apktool folder)
STEP 2 - FRAMEWORK EDITING
Extract framework.jar
Goto extracted framework.jar folder and copy classes.dex file to root Apktool folder. You may renamed classes.dex
Extracting classes.dex
Open readme.txt and copy this line : java -jar baksmali-1.3.3.jar -o classout/ classes.dex
At Apktool root folder, press SHIFT + RIGHT MOUSE BUTTON and "Open Command Window Here"
Paste at Command Window and ENTER
Goto Extracted Classes.dex folder
Copy attached environment.smali to \android\os folder
Repacking classes.dex file
Open readme.txt and copy this line : java -Xmx512M -jar smali-1.3.3.jar classout/ -o new-classes.dex
Here a repacked new classes.dex file
Push new-classes.dex into framework
Open framework.jar with Winrar
Copy new-classes.dex file into framework
Delete original classes.dex file and rename new-classes.dex file to classes.dex
STEP 3 - FINISHING
Copy edited framework.jar into /system phone folder
Set permission rw-r--r--
Move to /system/framework
Restart to CWM, wipe cache and wipe dalvik
RESULT :
Thanks To :
Rizal Lovins for this thread
Kyrie1965 for this thread
Great People at http://forum.xda-developers.com/
Reserved 1
Reserved 2
I'm sorry for asking, but why should we swap INternal and sdcard? because heavy app's data files are stored in sdcard while Xperia V's internal memory is lower than its sdcard (1.97vs 3.65 Gb) so...? Can you get this straight for me?
Thanks in advance
Dis mod help phone with lower internal.... Like V has lower internal memory, swapping external memory to Internal memory gives tha internal memory more space... Yur SD Card will be seen as internal memory!!!
sent from tsubasa using XDA 4 app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Thanks for dis mod buddy.... Will try ot it out on when am on PC!!!
sent from tsubasa using XDA 4 app
works like a charm buddy.....
but i notice dat all my files in SDCard1/Android re also present in SDCard0/Android
is dat how it works?
What do I do to extract the classes.dex? I get error with 7zip and winrar
Can you help me modify my files? : D
Rojikaft said:
What do I do to extract the classes.dex? I get error with 7zip and winrar
Can you help me modify my files? : D
Click to expand...
Click to collapse
using dis tool buddy.... http://forum.xda-developers.com/showthread.php?t=2195680
but if yhu like, yhu can post yur framework.jar, i ll help!
This and thank you!
Rojikaft said:
This and thank you!
Click to expand...
Click to collapse
rename & give it a shot brov... dnt forget to fix permission!
http://www20.zippyshare.com/v/98517129/file.html
whalesplaho said:
rename & give it a shot brov... dnt forget to fix permission!
http://www20.zippyshare.com/v/98517129/file.html
Click to expand...
Click to collapse
Thank you! works fine!
Rojikaft said:
Thank you! works fine!
Click to expand...
Click to collapse
enjoy mate...... my pleasure!!! :highfive:
is there any workaround for 4.3 framework.jar?
Still sort it, totaly different framework.jar on JB 4.3
Important
thunder888 said:
Still sort it, totaly different framework.jar on JB 4.3
Click to expand...
Click to collapse
Please Let Us Know When U Can Do The Swap MOD For JB 4.3 >> Cause I'm Not Going To Update To JB 4.3 Unless The Swap MOD Work With It
Thanks Bro
me too havent update...... dnt think tha script one will work too!
sirkay said:
is there any workaround for 4.3 framework.jar?
Click to expand...
Click to collapse
Did anyone find a way to do this on 4.3? Am also reluctant to upgrade until its possible.
thunder888 said:
Still sort it, totaly different framework.jar on JB 4.3
Click to expand...
Click to collapse
Is the only thing you changed in framework.jar 'sdcard0' to 'sdcard1' and 'EXTERNAL_STORAGE' to 'EXTERNAL_STORAGE_DUMB'?
The only lines in Environment.smali that could need changing are: (EDIT: changing EXTERNAL_STORAGE in environment.smali results in bootloop)
Code:
.field private static final ENV_EXTERNAL_STORAGE:Ljava/lang/String; = "EXTERNAL_STORAGE"
.............
const-string v1, "EXTERNAL_STORAGE"
and inside Environment$UserEnvironment.smali (Edit: changing these make no difference!!)
Code:
const-string v7, "EXTERNAL_STORAGE undefined; falling back to default"
invoke-static {v6, v7}, Landroid/util/Log;->w(Ljava/lang/String;Ljava/lang/String;)I
.line 128
const-string v3, "/storage/sdcard0"
would changing this in theory work? I haven't installed the rom yet as want to know there is a possibility to swap storage first.
I don't want to move the entire 10GB of sdcard0 into internal memory. What do I need to modify in this process to end up with about 3GB of internal storage and the rest as sdcard0?