Related
Hey guys, so this script de-odexe's a rom's apks and jar's.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming. This is crzyruski script updated with jesus freke's latest smali/baksmali update ver 1.2.3
It incorporates detecting the bootclasspath of the odex instead of the user specifying it. For non standard odex however a specific bootclass path must be defined. For example:
According to Jr33 for rosie deodexing u have to add class paths com.htc.framework.jar. Thank him for the new Sense bootclasspaths
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
*New Menu added
*Ability to specify custom bootclasspath (eg for sense ui)
*Added a java check at the beginning
*Added 1.2.3 smali/baksmali with froyo support(thank jf ofcourse )
*Modified it so if an error is encountered during deodexing, it leaves that file behind so once done you know what files encountered errors
*Added Ignore Mode
*Removed zipalign
*If apk doesnt have corresponding odex, it moves it to deodexed_APK instead of user manually moving it
*Added compression level option
*You can monitor the status of ignore mode / compression level right above the main menu
DISCLAIMER:
Its a batch file so it'll only work on windows.
Convince farmatito to bring this to linux
Thanks
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
enomther said:
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
Click to expand...
Click to collapse
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Daneshm90 said:
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Click to expand...
Click to collapse
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
enomther said:
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
Click to expand...
Click to collapse
Ah sweet, something i shall incorporate in the script later on. thanx
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Joe333x said:
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Click to expand...
Click to collapse
Emm...no im 99.99% sure it doesnt help tht way. I know that odex's cause customization problems in roms....there are other factors im sure
mrandroid said:
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Click to expand...
Click to collapse
MyFaves == No Go ... it requires some other form of trickery ... I'm not sure what exactly ... as I did de-odex it and it would not work properly on test-key ROM's like CM, etc.
... So it requires more than a simple de-odex.
~enom~
does your phone need to be connected? I noticed some ADB commands in the script
Daneshm90 said:
Hey guys, so this script de-odexe's a rom's apks.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
Oh also make sure to place only apk's that have their corresponding odex's. Dont place only apk's !!!!!
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
1. Download http://www.mediafire.com/?mwownkhzm4m
2. Extract to a folder
3. Place all your rom's apk's which have odex's attached to them into that folder
4. Run deoall
5. Copy all the apk's from the deodexed folder into ur corresponding rom app folder
Thanks
Upcoming:
Seperate Framework & apps folder
De-odex framework apk's and jar's (thanx for the tip enomther )
Click to expand...
Click to collapse
So the apk after that has the DEX built in or is dexopt still needed?
wesgarner said:
So the apk after that has the DEX built in or is dexopt still needed?
Click to expand...
Click to collapse
>.<.......................
kingklick said:
>.<.......................
Click to expand...
Click to collapse
Hey I am just double checking
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
---edit---
shoot me for not reading.
Daneshm90 said:
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
Click to expand...
Click to collapse
jubeh said:
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
Click to expand...
Click to collapse
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
enomther said:
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
Click to expand...
Click to collapse
I did it with the tattoo build, but upon boot I would get all sorts of fc's, but I think that was due more to a bad, hasty port than the deodexing. It was also a long time ago when the tool first came out, dont know if there's been newer revisions, so I'll try it again on that funky tattoo rom.
K guys one problem i found after doing multiple apk's is that i need to give the listening dex command a bit delay so its ready for baksmali. I was doing it right after which it misses for some conversions. I'll upload with delay between the two commands. Hmm framework i gotta give a shot :/ Sounds interesting ...
Solid script! Should make deodexing A LOT easier
Ok so i uploaded with delay between, seems to work fine, tested a LOT of times
thanks for this! can't wait for frameworks to be de-odexed.
jubeh: Thanks for the info. I had no idea and have informed JF previously here: http://jf.andblogs.net/2009/11/08/smalibaksmali-v1-0/ (see comments)
hello guys
through sbfrecalc I managed to open a original ROM 2.1 of droidx
I would like to try different type apk on my milestone: blurhome, blur service, blurcalendar, blurupdater etc etc..With rootexplorer installing them, after write me "apk not installed"
is a test without success, or do I have to change any library?
any advice is welcome!
thanks
any ideas?
1. do a test-key sign of apk.
2. copy appropiate jar files associated with apk
3. copy the libs needed
4. make sure framework support the blur functionality
5. update init.rc to load the required jar files at the end.
you're up for a little challenge. My mod of Motoblur is the closest you get to using it.
Dexter_nlb said:
1. do a test-key sign of apk.
2. copy appropiate jar files associated with apk
3. copy the libs needed
4. make sure framework support the blur functionality
5. update init.rc to load the required jar files at the end.
you're up for a little challenge. My mod of Motoblur is the closest you get to using it.
Click to expand...
Click to collapse
thank's dexter!
your motoblur its base froyo, but my idea was to prove eclair, and how do I know which are the correct libraries?
at your 5 answer im not sure to understand!
thanks for the reply and thanks for your work!
For those who doesn't search a bit n bug here n there for the question "how to port roms??? like cm7 n miui?"
here is the answer :
add/replace these
/system/app:
Bluetooth.apk → To fix the bluetooth problem
Phone.apk → To fix the proximity sensor issue
Added liquid settings & GApps
/system/bin:
Since you probably use the old sensor, you need to add all the *_yamaha files.
brcm_patchram_plus → To fix the bluetooth
dhcpcd
netd → To fix the wifi hotspot (you MUST change also /lib/libhardwarelegacy.so too, else you will get a bootloop)
rild → To get the network working
servicemanager → To get the sensors working
vold → To get the vold working
/system/etc:
the entire firmware folder to get wifi and sensors working
the init.d folder to tweak the rom
the permissions folder, added missing xmls
the entire wifi folder to get the wifi working
gps.conf → To improve the GPS
hosts → To fix ads
media_profiles.xml → To fix problems with camera and camcorder
vold.conf and vold.fstab → To fix vold, if you don't change them the rom won't boot.
/system/framework:
Added com.google.android.maps.jar to fix problems with the apps which uses GMaps.
You can find there the files to tweak with smali to get some stuff working. For example, if you want to get the prox. sensor working well, you need to edit the PowerService class in services.jar.
/system/lib:
the entire egl folder
the entire hw folder
the entire modules folder
all the libOmx* .so files → To get the camcorder working
all the libaudio* .so files → To get the audio working (if you don't change them, it won't boot)
libandroid.so
libauth.so
libcamera.so and libcameraservice.so → These depends on the ROM.
libcm, libcommondefs.so, libdiag.so, libdll.so, libdsm.so, libdss.so, libeffects.so, libg*.so
libhardare_legacy.so
libloc*.so
liblog.so
libmedia.so
libmmgsdilib.so, libmmipl, libmmjpeg.so, libnfc_ndef.so, libnv.so
libms3c_yamaha.so → To fix the sensors
liboemcamera.so → To fix the camera & camcorder
liboncrpc.so, libpbmlib.so, libqmi.so, libqueue.so
libril*.so
librtp_jni.so
libsensor*.so
libspeech.so
libsqlite_jni.so
libstagefright_*.so → These are usually not required
libt99.so
libvoicesearch.so
libwebcore.so
libwms.so
libwmsts.so
/system/sd:
The placeholder file. → To get sd working
/system/usr:
the entire 'keychars' and 'keylayout' folders
/system/vendor:
The entire folder.
/system:
Edit build.prop and add/change the following strings:
ro.product.board=salsa
ro.hw_version=4
rild.libpath=/system/lib/libril-acer-1.so
Obviously you also need to change the kernel and, if needed, you must also edit the BOOTCLASSPATH in the init.rc file in the ramdisk. Please refer to other tutorials for this.
Very nice, Thanks man
sachin0701 said:
For those who doesn't search a bit n bug here n there for the question "how to port roms??? like cm7 n miui?"
here is the answer :
add/replace these
/system/app:
Bluetooth.apk → To fix the bluetooth problem
Phone.apk → To fix the proximity sensor issue
Added liquid settings & GApps
/system/bin:
Since you probably use the old sensor, you need to add all the *_yamaha files.
brcm_patchram_plus → To fix the bluetooth
dhcpcd
netd → To fix the wifi hotspot (you MUST change also /lib/libhardwarelegacy.so too, else you will get a bootloop)
rild → To get the network working
servicemanager → To get the sensors working
vold → To get the vold working
/system/etc:
the entire firmware folder to get wifi and sensors working
the init.d folder to tweak the rom
the permissions folder, added missing xmls
the entire wifi folder to get the wifi working
gps.conf → To improve the GPS
hosts → To fix ads
media_profiles.xml → To fix problems with camera and camcorder
vold.conf and vold.fstab → To fix vold, if you don't change them the rom won't boot.
/system/framework:
Added com.google.android.maps.jar to fix problems with the apps which uses GMaps.
You can find there the files to tweak with smali to get some stuff working. For example, if you want to get the prox. sensor working well, you need to edit the PowerService class in services.jar.
/system/lib:
the entire egl folder
the entire hw folder
the entire modules folder
all the libOmx* .so files → To get the camcorder working
all the libaudio* .so files → To get the audio working (if you don't change them, it won't boot)
libandroid.so
libauth.so
libcamera.so and libcameraservice.so → These depends on the ROM.
libcm, libcommondefs.so, libdiag.so, libdll.so, libdsm.so, libdss.so, libeffects.so, libg*.so
libhardare_legacy.so
libloc*.so
liblog.so
libmedia.so
libmmgsdilib.so, libmmipl, libmmjpeg.so, libnfc_ndef.so, libnv.so
libms3c_yamaha.so → To fix the sensors
liboemcamera.so → To fix the camera & camcorder
liboncrpc.so, libpbmlib.so, libqmi.so, libqueue.so
libril*.so
librtp_jni.so
libsensor*.so
libspeech.so
libsqlite_jni.so
libstagefright_*.so → These are usually not required
libt99.so
libvoicesearch.so
libwebcore.so
libwms.so
libwmsts.so
/system/sd:
The placeholder file. → To get sd working
/system/usr:
the entire 'keychars' and 'keylayout' folders
/system/vendor:
The entire folder.
/system:
Edit build.prop and add/change the following strings:
ro.product.board=salsa
ro.hw_version=4
rild.libpath=/system/lib/libril-acer-1.so
Obviously you also need to change the kernel and, if needed, you must also edit the BOOTCLASSPATH in the init.rc file in the ramdisk. Please refer to other tutorials for this.
Click to expand...
Click to collapse
nothing to unlock the wifi?
i posted this 7 months ago
and lol u copied it - 'rild.libpath=/system/lib/libril-acer-1.so'
I am sure this guide will not make the phone boot
Sent from MIUI V5 on GT-I9003
Never needed this
Yeah sakindia is right he posted this way back in june
Sent from my GT-I9003 using XDA App
bro sakindia i searched xda for porting roms but cudn't find any 1and this i ddn't copied u its from combined resources out of xda!!!!!
i dont knew abt this sorry bro!!!!
sakindia123 said:
i posted this 7 months ago
and lol u copied it - 'rild.libpath=/system/lib/libril-acer-1.so'
Click to expand...
Click to collapse
if u think i will delete this post so chilax!!!
gm007 said:
I am sure this guide will not make the phone boot
Sent from MIUI V5 on GT-I9003
Click to expand...
Click to collapse
bro than wud u help me correct this post plz???
Hello, Sachin.. I will try out your guide.
But I have one suggestion: make it more newbie friendly. Currently seems like people who already know how to port a ROM would understand this, but those that don't (the people who most need a guide) will have to try this blind. Can you make is so its like a guide for an absolute newbie?
inciongd said:
Hello, Sachin.. I will try out your guide.
But I have one suggestion: make it more newbie friendly. Currently seems like people who already know how to port a ROM would understand this, but those that don't (the people who most need a guide) will have to try this blind. Can you make is so its like a guide for an absolute newbie?
Click to expand...
Click to collapse
take the rom you want to port n take a stable rom for the same device....
extract both roms....now replace all above files of a stable rom from the rom u want to port!!! after replacing/adding reapack it n u r done......
wen u extract rom u will find a file system.rfs extract it...than u will be able to find the files listed above!!!!!
sachin0701 said:
take the rom you want to port n take a stable rom for the same device....
extract both roms....now replace all above files of a stable rom from the rom u want to port!!! after replacing/adding reapack it n u r done......
wen u extract rom u will find a file system.rfs extract it...than u will be able to find the files listed above!!!!!
Click to expand...
Click to collapse
Sry for the noob question but if its jut extract and repack then how come the devs are having problem making the camera work
Sent from my GT-I9003 using XDA App
devilhell007 said:
Sry for the noob question but if its jut extract and repack then how come the devs are having problem making the camera work
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Video, audio Codec and lib files I believe.
Cheers
Sent from my i9003 powered by Cyanogenmod 7
I really want to this tutorial
Sent from my Droid using Tapatalk 2 Beta-4
Useful guide.
Sent from my GT-I9003 using xda premium
Hi all -
I'm using a GSM Galaxy Nexus with stock Android 4.1.1, and I'm trying to reduce the dim level, which kills my eyes at night. This is determined by a value "config_screenBrightnessDim" found in framework-res.apk. (In the source tree, it is found at frameworks/base/core/res/res/values/config.xml.)
I tried using apktool to decompile/recompile the stock framework-res.apk, but it doesn't seem to work with Jelly Jean. So, I instead attempted to replace the stock framework-res.apk with one I compiled from AOSP. When I do this, I get stuck at the boot animation. I assume this has something to do with the fact that my AOSP framework-res.apk is signed with a different certificate than the stock one. However, I also noticed that my AOSP file was ~10MB, while the stock one is only ~9.8MB, so there could be some other issue.
Any help with this would be greatly appreciated. Thanks!
(PS: Another modification I made was successful: I replaced the stock audio.primary.tuna.so with one I built from AOSP with a higher maximum volume. So, I think I am at least replacing the files correctly!)
Don't sign the framework file. Leave it unsigned and just move the cert from the stock framework. Also I would be interested in your audio boost file if you wouldn't mind sharing.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the advice –*I'll try it out. I'll "unsign" my framework-res.apk by removing all the META-INF files in it. If it doesn't work, do you know a way to find the logs from the failed boot? Also, is there anything I should do (wipe cache, etc) after copying over the new framework-res.apk?
I've attached a zip containing three versions of the library audio.primary.tuna.so, found at /system/lib/hw/audio.primary.tuna.so: orig, loud, and aosp. "orig" was pulled from my phone with stock 4.1.1, "aosp" was built from aosp (the command you need is "make audio.primary.tuna"), and "loud" was made from aosp with the "device/samsung/tuna/audio/audio_hw.c" file altered to change the volume. Enjoy!
Geo411m said:
Don't sign the framework file. Leave it unsigned and just move the cert from the stock framework. Also I would be interested in your audio boost file if you wouldn't mind sharing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This worked! Thanks so much!
Great! Glad it worked for you. Also thanks for the Audio file.
How do you build just framework-res.apk from AOSP?
I've followed a tutorial and built the whole system, but I don't know where fraemwork-res.apk is built from in the source or how to only build it.
Edit:
figured out to build specific packages:
make (package name)
...omg
If you figure out how to use a framework-res.apk built from AOSP to replace one on the stock rom, let me know. I never did get that method to work.
michaelmotes said:
How do you build just framework-res.apk from AOSP?
I've followed a tutorial and built the whole system, but I don't know where fraemwork-res.apk is built from in the source or how to only build it.
Edit:
figured out to build specific packages:
make (package name)
...omg
Click to expand...
Click to collapse
There are some (most) things that you can modify in framework-res.apk and just copy over the old META-INF.
There are some things (like AndroidManifest.xml) that you can not modify and use the old META-INF.
The most radical solution is to resign your entire system with a new signature.
If the particular APK (not FW-R) does not use a sharedid, you might get away with just signing that.
(The above observations might be different on different versions Android.)
To the point!
When you found a bug when porting a ROMs, you can try to fix using this methods!
Just replace it from Stock ROM to your Custom ROMs.
~~For MTK~~
Bootloop when porting
*libandroid_runtime.so
*libandroid_servers.so
*libmedia_jni.so
*Repack boot.image
RadioFM
\system\bin\fmradio
\system\etc\firmware\mt6620_patch_e3_hdr.bin
\system\etc\firmware\mt6620_patch_e6_hdr.bin
\system\etc\firmware\WMT.CFG
\system\lib\modules\mtk_fm_drv.ko
\system\lib\libfmcust.so
Sensors
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware (folder)
/system/bin/servicemanager
Bluetooth\Wifi not turning On\Off
\system\lib\module\mtk_stp_wmt
Bluetooth
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
/system/lib/libbluetooth_mtk.so
/system/lib/libbluetoothem_mtk.so
Wifi
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd -> Fix wifi hotspot
/system/lib/libhardwarelegacy.so -> Fix wifi /system/lib/modules/mtk_stp_wmt.ko/system/lib/modules/mtk_wmt_wifi.ko
/system/etc/wifi (folder)
/system/etc/firmware (folder)
Camera
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so\system\lib\libmhalcontent.so
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so ->fix camcoder
SD card/Memory
/system/bin/vold
\system\etc\vold.fstab -> edit file for swap internal and external
\system\etc\vold.fstab.nand
GPS
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen(Haptic)
/system/usr
/system/usr\keylayout\Generic.kl ->fix HomeKey
Sim1/2 (RIL)
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound
\system\lib\libaudio* .so
Ads
/system/etc/hosts ->replace with new files or use tweak.
~~SNAPDRAGON QUALCOMM~~
BUGS SIGNAL
Change all file berextensi librilxxx.so in system/lib with file from stock rom.
If doesn't appear, check imei *#06#
BUGS SENSOR
Change file sensorservice in system/bin with file from stock rom
Chamge file libsensorservice.so in system/lib with file from stock rom
Change file sensor.default.so in system/lib/hw with file from stock rom
BUGS CAMERA
Change all file extensi mm-qcameraxxx in system/bin with file from stock rom
Change file v4I2-qcamera-app in system/bin with file from stock rom
Change file camera.msm7627a.so in system/lib/hw with file from stock rom
Change file libcamera_client.so and libcameraservice.so in system/lib with file from stock rom
Change all file libmmcameraxxx.so in system/lib with file from stock rom
Change all libs started with *cam* in lib and lib64
Change all libs started with *omx* in system/vendor
BUGS FINGERPRINT (FPC/GOODIX)
Change gx_fpd in bin folder from stock to port
Change hwservicemanager in bin folder from stock to port
Change android.hardware.fingerprint.xml in etc folder from stock to port
Change libcom_fingerprints_service.so from lib and lib64 from stock to port
Change fingerprint.default.so and fingerprint.msmxxxx.so in hw folder in lib and lib64 from stock to port
Change name started in *fp* in vendor from stock to port
BUGS WIFI
Change file wpa_supplicant im system/bin with file from stock rom
Change folder firmware and wifi in system/etc with file from stock rom
Change file wifitest_recv.sh and wifitest_send.sh in system/etc with file from stock rom
Change file libwpa_client.so in system/lib with file from stock rom
Change file cfg80211.ko in system/lib/modules with file from stock rom
Change folder ath6kl in system/lib/modules with file from stock rom
Change file in folder wifi in system with file from stock rom
BUGS GPU
Change all file in folder egl in system/lib with file from stock rom
BUGS USB
Change file vfold.fstab in system/etc with file from stock rom
NB: still bug? Repack boot.img and see the ramdisk files.
BUGS VIDEO
Change all file berextensi libchromaticxxx.so in system/lib with file from stock rom.
Thanks in advance!
Give like if you like it!
i ported a rom.. its just fyn.. but settings is crashing.. when ever i open settings its crashing nd also play store no opening showing connection problem.. retry... help me with this!
Try fix permissions ,,
if the fix wifi tethering how
D2Y aka E said:
if the fix wifi tethering how
Click to expand...
Click to collapse
I need to know what the Chipset of your device? Is MTK or something else?
Thanks ,, [emoji4]
Jawaad_S said:
I need to know what the Chipset of your device? Is MTK or something else?
Thanks ,, [emoji4]
Click to expand...
Click to collapse
Qualcom bro...
Use the Qualcomm methods ,,
If its doesn't work, you can use the MTK methods ,,
Thanks
Any idea with FC errors when installing third party app in ported MIUI v4.
Maybe that apps is not compatiblelity for MIUI v4 ,,
my port brigthness not working,recent app not shown. then after i lockscreen it wont open.. i port s5 KK mt6582
Sent from my YP-G70 using XDA Free mobile app
Ported a rom successful from mobile with the exactly same specifications with mine, unfortunatelly the power key does not trigger screen lock and unlock, what to replace to make it work? Plus when the phone goes to deep sleep it takes ten to twenty seconds to come back on when power key pressed, please advise thanks.
sarry86 said:
Ported a rom successful from mobile with the exactly same specifications with mine, unfortunatelly the power key does not trigger screen lock and unlock, what to replace to make it work? Plus when the phone goes to deep sleep it takes ten to twenty seconds to come back on when power key pressed, please advise thanks.
Click to expand...
Click to collapse
The importantly for fixing is in system/lib. Theres so many bug when first time porting a ROM's and lib is the first to solve that bugs. Trying to replace the lib files from Stock ROM to your PORT ROM but not all. Just replace it one by one. If it makes your phone bootloop, the lib files is not compatibility with your PORT ROM's. And especially don't forget to backup the lib files before replace it from your Stock ROM.
Hope it helps
lildhiel08 said:
my port brigthness not working,recent app not shown. then after i lockscreen it wont open.. i port s5 KK mt6582
Sent from my YP-G70 using XDA Free mobile app
Click to expand...
Click to collapse
Its about the lib files bro ,,
I ported CM10 for my mtk6592 and there's just one error, when I put a number in dialer app and click on call, it says "searching for networks" and it remains there. However sometime it calls. And it can receive calls from other phones.
Copied all the SIM1/SIM2 files from base to port and the firmware folder and everything but its just not working.
And no apns are being displayed in settings.
3g turns on and displays "3G" on statusbar but net doesn't work.
Have copied apns_config but still doesn't work
Do you have any clue how to fix?
parasthakur37 said:
I ported CM10 for my mtk6592 and there's just one error, when I put a number in dialer app and click on call, it says "searching for networks" and it remains there. However sometime it calls. And it can receive calls from other phones.
Copied all the SIM1/SIM2 files from base to port and the firmware folder and everything but its just not working.
And no apns are being displayed in settings.
3g turns on and displays "3G" on statusbar but net doesn't work.
Have copied apns_config but still doesn't work
Do you have any clue how to fix?
Click to expand...
Click to collapse
In system/framework, you can replace telephony-common.jar and telephony bla la. And in the system/lib replace all file with the name of "ril" and in system/bin replace it too the file "ril" to your Port ROM from Stock ROM.
Hope it helps
Jawaad_S said:
The importantly for fixing is in system/lib. Theres so many bug when first time porting a ROM's and lib is the first to solve that bugs. Trying to replace the lib files from Stock ROM to your PORT ROM but not all. Just replace it one by one. If it makes your phone bootloop, the lib files is not compatibility with your PORT ROM's. And especially don't forget to backup the lib files before replace it from your Stock ROM.
Hope it helps
Click to expand...
Click to collapse
Hats off to the devs, this porting stuff is a pain in the a**, porting ain't easy. Thanks will try libs one by one to see if i can fix it
led light blinging always
Please how do I fix led light always on after notification is cleared the light will still be on ........... (The home key , back key and settings key all having light always) will be happy if I can fix that)
What to do when we get
android.process.media has stopped...???
sarry86 said:
Hats off to the devs, this porting stuff is a pain in the a**, porting ain't easy. Thanks will try libs one by one to see if i can fix it
Click to expand...
Click to collapse
Good luck
Akorstayblessed said:
Please how do I fix led light always on after notification is cleared the light will still be on ........... (The home key , back key and settings key all having light always) will be happy if I can fix that)
Click to expand...
Click to collapse
I'm so sorry. I can't fix the bug like that. You can tell the Dev because i've never found a bug like that.
Hope it helps
saurabh1234 said:
What to do when we get
android.process.media has stopped...???
Click to expand...
Click to collapse
Check the system/framework files.
i have ported a rom it had storage 0.0b so i changed vold from system/bin and i got a bug with usb pc connection (MTP,PTP,Charging mode) but usb debugging works
Device Micromax A092(Snapdragon MSM8212)
ROM ported LAVA iris 406q(MSM 8610)