[Q] Trying to port 3D framework to CM9 - LG Optimus 3D

Hi all,
I'm trying to extract System.img file of ICS v28. It's because I want try to port the 3D framework, from LG's original firmware, to CM9.
I need extract the System.img to do a "diff" between both builds and analize the diferences.
anybody knows how to extract the System.img? I have tried unyaffs and unyaffs2 but they don't work...
Thanks in advance,

internest said:
Hi all,
I'm trying to extract System.img file of ICS v28. It's because I want try to port the 3D framework, from LG's original firmware, to CM9.
I need extract the System.img to do a "diff" between both builds and analize the diferences.
anybody knows how to extract the System.img? I have tried unyaffs and unyaffs2 but they don't work...
Thanks in advance,
Click to expand...
Click to collapse
Why you Post This in Development
Anyway Here

Because port 3d Framework will be a development, isn't it? the port is not copy & paste.
If you want, you can delete this thread.
PD: thanks for you reply.

it not doable the native libs like the files in system/lib these are compiled with the build and the 3d framework is embedded into libs such as surfaceflinger if you can get CM9 to run with libsurfaceflinger from ics it might maybe work after ALOt of diff'N

It's not impossible to port Real3D, but it will be one of extremely unpleasant experience. I tried that "copy and paste" thing, while monitoring Logcat - lemme tell you, something's preventing the Real3D framework from working correctly. It's probably because of LG's DRM services. It sucks, and I gave up - not a task for the timids.
Sent from my LG Thrill 4G (PAC-man 4.1) using XDA

Related

Question about the frame-resp.apk from the X10 leak

I tried to bake my own rom, but ti didn't work. My question is, can I just push the apk. to the phone? Or is it tied to possibly to something else and will not work?
isn't the X10 based on 1.6?? I doubt it wud ever work on the 2.0, let alone the 2.1
craigacgomez said:
isn't the X10 based on 1.6?? I doubt it wud ever work on the 2.0, let alone the 2.1
Click to expand...
Click to collapse
Didn't know that. Thanks.
of course it can work. the dump needs to be ported first, u can't just push .apk's.. they run on a highly customized framework that is all tied together and inter-related much like HTC sense.
jroid said:
of course it can work. the dump needs to be ported first, u can't just push .apk's.. they run on a highly customized framework that is all tied together and inter-related much like HTC sense.
Click to expand...
Click to collapse
Which is why I asked.
but, you should be able to pull most of the .pngs out of the x10 framework and port it into a theme for 2.0/2.1...
got a link to the x10 apk?
MYxdaUSERNAME said:
but, you should be able to pull most of the .pngs out of the x10 framework and port it into a theme for 2.0/2.1...
got a link to the x10 apk?
Click to expand...
Click to collapse
I would like to get theses png too... I search for the launcher png to make my own theme.
Do you know if they are available somewhere
Download the dump here
http://forum.xda-developers.com/showthread.php?t=658063&highlight=dump
Then extract the apks and open them in any archive manager (winrar etc) and look for PNGs in the res/drawable folder. Most system wide stuff is in /system/framework/framework-res.apk
EDIT: OK, my mistake
I downloaded the sources and not the rar file
jonasl said:
Download the dump here
http://forum.xda-developers.com/showthread.php?t=658063&highlight=dump
Then extract the apks and open them in any archive manager (winrar etc) and look for PNGs in the res/drawable folder. Most system wide stuff is in /system/framework/framework-res.apk
Click to expand...
Click to collapse
Euhhh, I just downloaded 73Mb file of X10..
I think there is a mistake because once the file uncompressed I get this:
A directory: X10_Donut_100325_01
1 sub-dir: esheep_linux
1sub-dir: LINUX
1sub-dir: android
3 sub dir: external - kernel - system.
If I go under system, i get: core/mtd and there nothing but .c files
I think that was a wrong file a downloaded but I cannot find an other one.
Sorry, but I try my best ;-)
I found some apk but no launcher.apk.
Only launcher.odex and i could'nt unzip it.
For all the other applications, that's OK.
Hello, sorry to annoy you again with my questions...
1) I downloaded the framework and extract all.
I extracted all the files but:
SonyX10/system/app/Launcher.apk - CRC failed
Total errors: 1
Click to expand...
Click to collapse
OMG, i had tu unzip hundreds of files that worked pretty well and the only one I need is the only one that failed????
I'm so unlucky.
Can someone send the launcher.apk to me?
Here is the un-odexed X10 dump I have... Ready to be played with...
http://www.4shared.com/file/wA0ELkvL/X10_dump.html
Also, here is an X10 theme for CM 5.0.6 that I have been working on...
http://www.4shared.com/file/CKUM0CAj/zapmi_X10_103.html
Enjoy!
Thank you for both link that work pretty well. Thank a lot!
I found all I wanted except one thing: do you know where is the background of the "quick settings" widget?
The number one on the picture, the launcher was easy to find in the launcher.apk.
Click for full size - Uploaded with plasq's Skitch
Thank a lot.
settings.apk should be what you're lookin for.
i actually ported the statusbar to my droid a while back. didnt look too bad..
MYxdaUSERNAME said:
settings.apk should be what you're lookin for.
Click to expand...
Click to collapse
Thank a lot, that was too simple .. I feel stupid.. :-s
Good job on your theme!

Flashable theme zips?

Need to know how to make flashable zips for my rom releases without apks just framework images!
Any quidance would be of help!
Building a rom from the ground up is easier than this but i need to start making them for the build cause i have a crapload of images with no place to go thanks! just pm me or whatever! thanks
eVoKINGS said:
Need to know how to make flashable zips for my rom releases without apks just framework images!
Any quidance would be of help!
Building a rom from the ground up is easier than this but i need to start making them for the build cause i have a crapload of images with no place to go thanks! just pm me or whatever! thanks
Click to expand...
Click to collapse
If you are just using images I would say metamorph is the only option I know of that can replace files in .apk on the fly. Its not a flashable zip though.
Give this a try... this will port png's from one rom to another. you just need to pull the framwork-res.apk and resources.apk from framework from your rom and put it in the "new" folder. and put the same apk's from the theme you want to port in the "old" folder, both under the framework folder with in the "new" and "old" folders. and run the script.... there are also app folders for any themed apps that you want to port also.... same thing with those, yours in the new and the themed ones to port in the old.... Just remember, these are only png ports, you still need to do xml edits if there are any...
this is not my work, found it here on xda a very long time ago and don't remember from who but thanx to him or them......
View attachment Theme-Porter.zip

[TOOL][PORT] Autodeodexer 2.3a for the Epic 4G Froyo - Windows

Honestly, I do not know how much interest there will be in this, but throughout my own exploration and experimentation with Android and the Epic 4G I feel like sharing my finds with the community.
I kanged this tool from HERE so thanks to Daneshm90 among other people who are thanked in the tool itself. All I really did was add a few BOOTCLASSPATHS to the *APK.bat files to get it to deodex all the apks, and update smali/baksmali to version 1.2.6 (newest as of 3/25/11).
Basically this is a one click tool to deodex stock, odexed system/framework and system/app folders on a windows machine. I tested on the ACS Untouched Stock EC05 ROM and got clean runs where everything became deodexed.
Tips: I found it best to do system/framework first in one run, then leave the output in deodexed_JAR, and THEN process system/app as many of the files in the app folder have dependencies on the jars.
After processing system/framework you will have framework-res.apk and twframework-res.apk which do not need deodexing.
In early testing, I found certain files leftover after a run processed on the next run. This stopped after updating smali/baksmali. I doubt I'll be of much help if you run into problems, you are doing EVERYTHING at your own risk. I barely understand the details here, I just ported it to work on our phone, so good luck!
Deodexed 2.3a Download
Thanks for this!
Good tool for those that want stock with.a theme.
Sent From My Evo Killer!
Mind if I throw this in the EPIC 4G cookbook?
amosher13 said:
Honestly, I do not know how much interest there will be in this, but throughout my own exploration and experimentation with Android and the Epic 4G I feel like sharing my finds with the community.
I kanged this tool from HERE so thanks to Daneshm90 among other people who are thanked in the tool itself. All I really did was add a few BOOTCLASSPATHS to the *APK.bat files to get it to deodex all the apks, and update smali/baksmali to version 1.2.6 (newest as of 3/25/11).
Basically this is a one click tool to deodex stock, odexed system/framework and system/app folders on a windows machine. I tested on the ACS Untouched Stock EC05 ROM and got clean runs where everything became deodexed.
Tips: I found it best to do system/framework first in one run, then leave the output in deodexed_JAR, and THEN process system/app as many of the files in the app folder have dependencies on the jars.
After processing system/framework you will have framework-res.apk and twframework-res.apk which do not need deodexing.
In early testing, I found certain files leftover after a run processed on the next run. This stopped after updating smali/baksmali. I doubt I'll be of much help if you run into problems, you are doing EVERYTHING at your own risk. I barely understand the details here, I just ported it to work on our phone, so good luck!
Deodexed 2.3a Download
Click to expand...
Click to collapse
This is awesome...... GREAT WORK.....
Okay so this sounds interesting and all...But how does one use it??
tphillips said:
Mind if I throw this in the EPIC 4G cookbook?
Click to expand...
Click to collapse
Go right ahead!
sent from my mind to yours
youngpro83 said:
Okay so this sounds interesting and all...But how does one use it??
Click to expand...
Click to collapse
Just take an odexed frame work, put it in the folder and run deoall.bat, then repeat for app. Pretty much it, if you don't know the point then you probably don't need it, lol
sent from my mind to yours
Thanks dude
Thanks bro good work
Anyone give this a shot yet?
blazinazn said:
Anyone give this a shot yet?
Click to expand...
Click to collapse
Yea I tried using it to deodex my eco5 stock rom, and it ran clean and gave output, but the output wouldn't boot.. I ended up going a diff route which included using a tool made for another phone and doing some by hand...
Sent from my SPH-D700 using XDA App

[Q] CM 6 Theming

Hope posting this here is OK- I never get answers in Q&A...
I have made & modified themes for the SE stock 'rom' and as you know the framework-res and system apks do not need to be recompiled or signed when just exchanging images.
Is it the same for CM 6 'roms'?
I am looking into theming Wolfbreak's rom and noticed the framework-res that I'm using as a base says "signed by SignApk" when I open it in winrar.
Do I need to recompile & sign or not?
Thanks in advance!
AyDee said:
Hope posting this here is OK- I never get answers in Q&A...
I have made & modified themes for the SE stock 'rom' and as you know the framework-res and system apks do not need to be recompiled or signed when just exchanging images.
Is it the same for CM 6 'roms'?
I am looking into theming Wolfbreak's rom and noticed the framework-res that I'm using as a base says "signed by SignApk" when I open it in winrar.
Do I need to recompile & sign or not?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
You dont need to sign regardless of OS if you are only swapping images for system files. But remember to use optimized pngs and zipalign as final step to minimize resources consumption.
If you are modding any resources.arsc you need to decompile to do that and recompile and sing accordingly.
Ok, thanks- just making sure... the winrar message threw me off...
AyDee said:
Ok, thanks- just making sure... the winrar message threw me off...
Click to expand...
Click to collapse
try 7-zip.....hope seeing themes from u soon....

[HOW-TO] Port US S3 ROMs between carriers

Porting TouchWiz ROMs​
This guide is intended to help you port ROMs from AT&T, T-Mobile, and Sprint over to the Verizon S3. The guide will be split into two different parts. Porting CDMA to CDMA and porting CDMA to GSM.
Just so there's no confusion:
CDMA Carriers:
Verizon
Sprint
GSM Carriers:
AT&T
T-Mobile
REMEMBER: If you choose to port a ROM from another carrier, be sure to ask permission to post from the developer.
What you need
7zip
Notepad++ (If on Windows)
A ROM you want to port
A ROM from your carrier/device
Knowledge on how to compile and recompile .jar files (I will not cover this)
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.2) and have the same chip (e.g. MSM8960). You will be able to determine the chip type from the build.prop​
PORTING CDMA TO CDMA (i.e. SPRINT TO VERIZON)​
Download the ROM you want to port
Download a ROM from your carrier
Unzip both ROMS
In the ROM you want to port - delete /system/etc/apns-conf.xml
Replace the apns-conf.xml you just deleted with the one from the ROM for your carrier
In the ROM you want to port - delete /system/framework/GlobalConfig.jar (This .jar file contains a lot of carrier information)
Replace the GlobalConfig.jar you just deleted with the one from the ROM for your carrier
In the ROM for your carrier, locate the following lib files in system/lib and copy them over to the ROM you want to port
libreference-ril.so
libril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libsecril-client.so
If your carrier is Verizon and you're porting a Sprint ROM, delete all the apps with "Sprint" in the name including these:
SecContacts.apk
SecPhone.apk
PhoneInfo.apk
Replace SecContacts.apk and SecPhone.apk with the Verizon ones.​
In the ROM you want to port - open up /system/build.prop in Notepad++
Locate every instance of d2att, d2tmo, or d2spr and replace it with d2vzw (Use CTRL+F if you have to)
Save the build.prop after all changes are made
In system/framework/ of BOTH ROMs, decompile framework.jar and framework2.jar
In the framework.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/android/service
smali/com/android/internal/telephony
Replace them with the folders from the ROM for your carrier
In the framework2.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/com/android/internal/telephony
smali/com/google/android/mms
Replace them with the folders from the ROM for your carrier
Build all of the jar files when finished (Please note that replacing the above folders will make the ROM operational to the point where MMS will work, but you may encounter other weird superficial errors. It's just too much work to go into the specifics.)
Re-zip the ROM you want to port
Flash in recovery
PORTING CDMA TO GSM (i.e. VERIZON TO T-MOBILE & ATT / SPRINT TO T-MOBILE & ATT)​
Download the ROM you want to port
Download a ROM from your carrier
Unzip both ROMS
In the ROM you want to port - delete /system/etc/apns-conf.xml
Replace the apns-conf.xml you just deleted with the one from the ROM for your carrier
In the ROM you want to port - delete /system/framework/GlobalConfig.jar (This .jar file contains a lot of carrier information)
Replace the GlobalConfig.jar you just deleted with the one from the ROM for your carrier
In the ROM for your carrier, locate the following lib files in system/lib and copy them over to the ROM you want to port
libreference-ril.so
libril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libsecril-client.so
Delete the following apps and replace them with the ones from your carrier:
SecContacts.apk
SecPhone.apk
In the ROM you want to port - open up /system/build.prop in Notepad++
Locate every instance of d2att, d2tmo, or d2spr and replace it with d2vzw (Use CTRL+F if you have to)
Save the build.prop after all changes are made
In system/framework/ of BOTH ROMs, decompile android.policy.jar, framework.jar, framework2.jar, and services.jar
You need to go through every smali file in all of the .jars and replace all instances of "Sprint" with "Verizon" or "Verizon" with "Sprint" depending on your carrier
In the framework.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/android/service
smali/com/android/internal/telephony
Replace them with the folders from the ROM for your carrier
In the framework2.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/com/android/internal/telephony
smali/com/google/android/mms
Replace them with the folders from the ROM for your carrier
Build all of the jar files when finished (Please note that replacing the above folders will make the ROM operational to the point where MMS will work, but you may encounter other weird superficial errors. It's just too much work to go into the specifics.)
Navigate to system/framework/ in both ROMs
Open framework-res.apk from both ROMs in 7zip
In framework-res.apk in both ROMs navigate to /res/xml/
Delete eri.xml from the framework-res in the ROM you want to port
Replace the deleted eri.xml with the one from the ROM for your carrier
Save and close the modified framework-res.apk
Re-zip the ROM you want to port
Flash in recovery
Obviously this guide will not work on more difficult ports such as bringing Sense to the S3, but the end result is that we will hopefully see more ROMs in the thread.
Thanks TrevE
Porting AOSP ROMs
================================ START ================================​
What you need
7zip
Notepad++ (If on Windows)
An AOSP ROM you want to port
An AOSP ROM from your carrier/device
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.1)​
I will do the AOSP porting section with an example. Say I want to port Paranoid Android:
Download Paranoid Android (Android 4.2)
Download CM10.1 (Android 4.2)
Unzip both ROMs
In the CM 10.1 folder delete the following folders/files:
/system/framework
/system/app
/system/lib/libandroid_runtime.so
/system/media (optional)
/system/fonts (optional)
Add the following folders from the PA ROM into the CM10.1 ROM:
/system/framework
/system/app
/system/lib/libandroid_runtime.so
/system/media (only if you deleted from CM10.1)
/system/fonts (only if you deleted from CM10.1)
Only do the following if you are porting from GSM to CDMA or CDMA to GSM (i.e. Porting an AT&T ROM to Verizon)
Navigate to system/framework/ in both ROMs
Open framework-res.apk from both ROMs in 7zip
In framework-res.apk in both ROMs navigate to /res/xml/
Delete eri.xml
Replace the deleted eri.xml with the one from your base ROM
Save and close framework-res.apk
Re-zip and flash in recovery
================================ END ================================​
If the ROM does not boot up, try a different ROM. For example, if you tried to port Paranoid Android 4.2 from AT&T and it didn't work. Try Paranoid Android from T-Mobile or the Galaxy Nexus, etc.
Wicked Sensation: http://www.androidfilehost.com/?fid=9390248398092763137
This ROM is completely based on Sprint's OTA. It will work with KindaCrapMods due to the framework being about 95% similar to the Verizon version. However, the 5% difference may induce abnormal behavior such as irregular lockscreen clock readings. Also, the ROM does not include any tweaks outside of what is present in the original release.
I WILL NOT be maintaining this ROM so if you want to see updates, start a thread for it.
Great writeup pure. Truly an asset to this community
Sent from my SCH-I535 using xda premium
epicroot said:
Great writeup pure. Truly an asset to this community
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hopefully we will see more ROMs in the future.
Wicked Sensation is uploaded.
Did you happen to do a test flash? Or just edit, zip and go
Sent from my SCH-I535 using xda premium
epicroot said:
Did you happen to do a test flash? Or just edit, zip and go
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Flashed it. Booted up. I did a reboot just to test, and then reverted to my ROM to continue development lol.
PureMotive said:
Flashed it. Booted up. I did a reboot just to test, and then reverted to my ROM to continue development lol.
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda premium
Cool deal
---------- Post added at 08:12 AM ---------- Previous post was at 08:02 AM ----------
Tryd flashing.. It failed immediately.. Gonna try redownloading
Sent from my SCH-I535 using xda premium
i just tried this hoping that it would work with this PA rom from AT&T. sadly this didnt work for me. it says update aborted when i try to install it. i was coming from PA 2.52 but it has some BT issues and occasional loose of signal for me so ifigured this would work. Maybe someone would like to try this and get it to work? :angel:
epicroot said:
Sent from my SCH-I535 using xda premium
Cool deal
---------- Post added at 08:12 AM ---------- Previous post was at 08:02 AM ----------
Tryd flashing.. It failed immediately.. Gonna try redownloading
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which mirror did you use?!
Sent from my SCH-I535 using xda premium
rossida said:
i just tried this hoping that it would work with this PA rom from AT&T. sadly this didnt work for me. it says update aborted when i try to install it. i was coming from PA 2.52 but it has some BT issues and occasional loose of signal for me so ifigured this would work. Maybe someone would like to try this and get it to work? :angel:
Click to expand...
Click to collapse
It's better to build AOSP from source if you can. In any case I'll update my reserved post with a how-to for AOSP ROMs (may or may not work for you).
EDIT: AOSP guide is up
Pure did you use twrp to flash?!
Menardo said:
Pure did you use twrp to flash?!
Click to expand...
Click to collapse
Yes. I always use TWRP. If you're trying to flash the Wicked Sensation ROM - it takes a long time to boot up.
EDIT: I just saw your post. If the ROM keeps failing I may have had a bad upload. Let me know and then I can correct it orrrrr you can try your hand at porting
PureMotive said:
Porting AOSP ROMs
================================ START ================================​
What you need
7zip
Notepad++ (If on Windows)
An AOSP ROM you want to port
An AOSP ROM from your carrier/device
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.1) and have the same chip (e.g. MSM8960)​
I will do the AOSP porting section with an example. Say I want to port Paranoid Android:
Download Paranoid Android (Android 4.2)
Download CM10.1 (Android 4.2)
Unzip both ROMs
In the CM 10.1 folder delete the following folders:
/system/framework
/system/app
/system/media (optional)
/system/fonts (optional)
Add the following folders from the PA ROM into the CM10.1 ROM:
/system/framework
/system/app
/system/media (only if you deleted from CM10.1)
/system/fonts (only if you deleted from CM10.1)
Re-zip and flash in recovery
================================ END ================================​
If the ROM does not boot up, try a different ROM. For example, if you tried to port Paranoid Android 4.2 from AT&T and it didn't work. Try Paranoid Android from T-Mobile or the Galaxy Nexus, etc.
Click to expand...
Click to collapse
SO just to clear things up... if i download this and CM10.1 for verizon i just do the guide above and this should work even tho its not the same phone? The PA is coming from Google Nexus and trying to port to VZ GS3
PureMotive said:
Yes. I always use TWRP. If you're trying to flash the Wicked Sensation ROM - it takes a long time to boot up.
EDIT: I just saw your post. If the ROM keeps failing I may have had a bad upload. Let me know and then I can correct it orrrrr you can try your hand at porting
Click to expand...
Click to collapse
I just tried TWRP like 3 days ago... Have to say I'm digging it... Yea I tried to flash from the main server... Just downloaded from a mirror... About to give it another go will let you know...
rossida said:
SO just to clear things up... if i download this and CM10.1 for verizon i just do the guide above and this should work even tho its not the same phone? The PA is coming from Google Nexus and trying to port to VZ GS3
Click to expand...
Click to collapse
Yes, that's correct. However, if it does not work try porting PA from another device like one of the other US S3s.
PureMotive said:
Yes, that's correct. However, if it does not work try porting PA from another device like one of the other US S3s.
Click to expand...
Click to collapse
but the PA from other US devices are not running 4.2.1 which CM10.1 is. All PAs are running 4.1.x on US GS3. So would it not be possible to port them since they are two different JB versions?
Can this help us bring Premium Suite over to us? Want it bad
rossida said:
but the PA from other US devices are not running 4.2.1 which CM10.1 is. All PAs are running 4.1.x on US GS3. So would it not be possible to port them since they are two different JB versions?
Click to expand...
Click to collapse
You don't have to port PA from the US S3s. You can port 4.2 PA from the GNex forums if you want.
TokedUp said:
Can this help us bring Premium Suite over to us? Want it bad
Click to expand...
Click to collapse
Unfortunately not. Porting that is much more complicated than what's described in this thread. I pretty much already ported multi-window and the ink effect so doing the rest doesn't seem too far fetched.
Thinking it's a bad upload... Same immediate failed message...

Categories

Resources