I need original media_profiles.xml @ 4.1.2 - Xperia SP General

Help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

it's yours now :laugh: unzip it.

Related

[GUIDE]How to port manufacturer ROM (Sense/Touchwizz...) [UPDATED For KITKAT]

How to port manufacturer ROM​​
As many people ask me how i’m porting ROMs to my Nexus S i share my method in this thread.
This method works for the Nexus but should also work on a lot of devices. The list of files that I would write in this thread is not exhaustive.
Please for all improvements, send me a MP. I’m french and it’s possible for me to misspellings
This thread is in constant progress thanks to your feedback.
Do not use this guide to port rom based on CM / AOSP roms. Please use this guide to port Sense / TouchWizz / Motoblur etc ... If you want to port based on AOSP roms there are others guide on XDA.
This method is not perfect, much work will then be necessary to fix all the bugs, and nothing says that this method is functional rather than every time ....​
I. What you need
Ubuntu and dsixda's Android Kitchen. Please refer to this link
Notepad++
Winrar
A brain =)
NB : Before you start porting a ROM you need to know several things. Over the phone you want to port the rom will have a hardware close to your, more porting will be simple and functional.
Example : Same screen resolution, processor of the same type (ARM6, ARM7, etc ....)
PORT is the ROM you want to port and BASE is the ROM developed for your device (AOSP/CM)
II. Let’s go !
1. Create new folder where you want and name it « Rom_port_for_yourdevice »
2. Download AOSP/CM developed for you device with the same android version which the rom you want to port
3. Download the rom you want to PORT
4. Extract each zip ROM in separate folder in « Rom_port_for_yourdevice »
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Now it will appears two folders. Open both.
In PORT folder delete META-INF folder and copy/paste the META-INF folder of BASE in PORT folder.
6. Open system folder in PORT rom and delete vendor folder
7. Now in PORT folder open lib folder and delete these folders :
modules
hw
egl
8. Now go in BASE folder and select (if exists) these folders :
addon.d
bin
etc
customize
framework
lib
vendor
xbin
Now copy these in system folder of PORT but do not replace anything ! (If forgot « ETC » folder on screenshot)
 
9. Open bin folder in BASE and PORT folders. Copy and replace these files from BASE to PORT :
adb
brcm_patchram_plus
hostap
hostapd
init.vsnet
linker
logcat
logwrapper
radiooptions
rild
rmt_storage
vold
wpa_cli
wpa_supplicant
glgps
10. Now in BASE and PORT system folder open etc folder and copy and replace (if exist) these files/folders from BASE to PORT :
Bluetooth
Dhcpcd
Firmware
gps
init.d
permissions
ppp
pppd
security
ssh
terminfo
updatecmds
wifi
audio_effects.conf
audio_policy.conf
dbus.conf
gps.conf
init.*.sh
media_codecs.xml
media_profiles.xml
nfcee_access.xml
secomxregistry
vold.conf
vold.fstab
wrs_omxil_components.list
11. Now copy usr folder from BASE to PORT and replaces all files
12. Open lib folder in BASE and PORT folders. Copy and replace these files from BASE to PORT :
liblog.so
libsecril-client
libreference-ril.so
libril.so
libs3cjpeg.so
libaudioflinger.so (if port does not boot, use from PORT rom)
libaudioutils.so
libtinyalsa.so
libpn544_fw.so
libSEC_OMX_Core.so
libOMX.SEC.***.Decoder.so
For HTC devices:
libhardware_legacy.so
libhtc_ril.so
libhtc_ril_switch.so
For LGE devices:
lge-ril.so
More commonly:
Add all the lib files with "ril" in their name
13. Open framework folder in BASE and PORT folders. In both folder rename framework-res.apk to framework-res.apk.zip and open the two files with Winrar.
In both files go to /res/xml/ and replace storage_list.xml of PORT framework-res.apk with the one of BASE.
Now close Winrar and rename framework-res.apk.zip in framework-res.apk in both folders.
14. Very important: By the way, there are some proprietary binaries missing from the guide (just depending on the device, as it's impossible to include all), so what I recommend is if your device has official cm, go to github.com/themuppets, pick the repo corresponding to your manufacturer and branch corresponding to your android version and download it and copy the files in your device's folder to the ROM you are porting. Lib to lib, bin to bin, etc. You may also need to look at the Mk files in the cm device source for your device to see what is built from source that you'll need such as libs and bins. For example, if it has Product_packages += \libwifi \
You would need to copy libwifi from cm. [/QUOTE]
Source: http://forum.xda-developers.com/showpost.php?p=41294434&postcount=23
15. Now open build.prop of PORT rom and replace these lines with BASE build.prop :
Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
ro.product.cpu.abi=
ro.product.cpu.abi2=
ro.product.manufacturer=
ro.wifi.channels=
ro.board.platform=
ro.build.product=
ro.build.characteristics=
rild.libpath=
rild.libargs=
wifi.interface=
16. Reboot to Ubuntu.
Steps for android 4.3 and older
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
Save and recompile kernel
Use CM/AOSP modified kernel in your rom.
Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom.
17. Now ZIP your PORT rom folder and flash it.
Please don't forget to use LOGCAT to debug the rom..... And to thanks or/and donate to me .....
Thanks !
​GalaxyUser
Here, I give you some tips and may help you to fix issues..​
Files to fix ...
You can try to replace some of these files (if exists) to fix ...
NFC
/system/app/Nfc.apk
/system/lib/libnfc*.so
/system/bin/pcscd
Radio FM
/system/bin/fmradio
Sensors
/system/bin/akmd*
/system/lib/libsensors.so
Bluetooth
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
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*
RIL
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Camera
Copy libcamera*.so from base to port rom
If rom does not boot after that, replace file one by one and see which file is the problem.
If you port on HTC Devices, try these:​Fix Network auto select
Decompile framework-res.apk
Go to this folder \framework-res\res\values
Open bools.xml
Change <bool name="skip_restoring_network_selection">true</bool>
To Change <bool name="skip_restoring_network_selection">false</bool>
Fix graphichal issues
Decompile framework.jar
Change these files with your CM base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
so there is hope that i can port xperia t jb rom to galaxy s3 using cm10 rom for galaxy s3
zeyadhan said:
so there is hope that i can port xperia t jb rom to galaxy s3 using cm10 rom for galaxy s3
Click to expand...
Click to collapse
Use CM10 and not CM10.1 to have the same version.
Try it i hope it will work
thank you for reply i saw your threads you ported lot of roms do you think it will boot
but sadly i use windows 7 so there is no way to decombile the kernel
zeyadhan said:
thank you for reply i saw your threads you ported lot of roms do you think it will boot
but sadly i use windows 7 so there is no way to decombile the kernel
Click to expand...
Click to collapse
I don't know if it will boot, when i do a port i never know if it will boot ^^
Read this: http://forum.xda-developers.com/showthread.php?t=633246
You could use kitchen in windows but it's not optimal i think.
i guess that the only way is install the Ubuntu and decombile kernel and make changes then combile it and copy the kernel to phone and back to windows (need a lot of time)
rom stuck at bootanimation maybe i do something wrong
zeyadhan said:
rom stuck at bootanimation maybe i do something wrong
Click to expand...
Click to collapse
Do a logcat and post pastbin link
Sent from my XT890 using xda app-developers app
Thanks for good tip!
Dear Galaxy_User,
i just port GT-I9100 rom for Nexus S, i am on Boot Animation and nothing working after that ..
http://pastebin.com/YBWDU1L4 here is the link for logcat .. kindly help me out
Regards,
Assassinoid
assassinoid said:
Dear Galaxy_User,
i just port GT-I9100 rom for Nexus S, i am on Boot Animation and nothing working after that ..
http://pastebin.com/YBWDU1L4 here is the link for logcat .. kindly help me out
Regards,
Assassinoid
Click to expand...
Click to collapse
Hi,
Your logcat is very weird
Try libaudioflinger.so to use from PORT
looks not bad
sent from my security handy talkie
talk free , no pay®
Nothing worked .. I just quit
Sent from my Nexus S using xda premium
assassinoid said:
Nothing worked .. I just quit
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Do you have correctly edited the kernel ?
You need to use CM kernel for Nexus S and to modify it with the BOOTCLASSPATH of Galaxy S Kernel.
Send me the boot.img of Nexus S and the boot.img of Galaxy S i will check that
GalaxyUser said:
Do you have correctly edited the kernel ?
You need to use CM kernel for Nexus S and to modify it with the BOOTCLASSPATH of Galaxy S Kernel.
Send me the boot.img of Nexus S and the boot.img of Galaxy S i will check that
Click to expand...
Click to collapse
OK I'll do that
Sent from my Nexus S using xda premium
Nice, the first actual tutorial on this instead of "just replace all apps/framework and media folder" which is a load of bull****,
Good job
Will this guide work if you want to port LG Stock ROM to another LG device? Like you ported O4X to Optimus Black.. I can use this guide to port O4X stock ROM to O2X?
Also, when porting stock ROM, I will need CM10 as base ROM or I must use same android version as the ROM I am porting?
Thanks.
natalya said:
Will this guide work if you want to port LG Stock ROM to another LG device? Like you ported O4X to Optimus Black.. I can use this guide to port O4X stock ROM to O2X?
Click to expand...
Click to collapse
I did it for Optimus Black, try it for O2X
natalya said:
Also, when porting stock ROM, I will need CM10 as base ROM or I must use same android version as the ROM I am porting?
Thanks.
Click to expand...
Click to collapse
You can use any rom with the same android version
GalaxyUser said:
I did it for Optimus Black, try it for O2X
You can use any rom with the same android version
Click to expand...
Click to collapse
Okay, can you please link me to the one you used as port (the O4X ROM) and do you recommend me to use that one as port or shall I use the one you already ported for Optimus Black as port?
PS: Is it easy to change bootclasspath?

rom porter patch beta 1

after too many test i finally made a patch for porting ics stock roms from arc/s (and maybe other xperia 2011 devices) to pur lovely xperia play
it will install all the things that you need for fully working rom on xperia play and deletes the cybershot camera(because it not working on our device)
installation guide:
there are 2 ways for installing
1-if the rom has armo installer
2-if it doesnt have armo installer
if it has armo installer its very easy to use this
here is the instruction
1-open rom zip and ics rom porter.zip files with winrar
2-find the device section in rom zip file
3-drag all the files inside system folder in the ics rom porter.zip to lt28i(xperia arc) folder of rom zip
4-now simply flash the rom zip ans choose xperia arc as your device and everything will be fine
if the rom doesnt have armo installer
do the same thing as i said for the the roms with armo installer but instead of draging the files to lt28i folder drag them to system folder
bugs:
1-no touchpad. i need help for this part.
2-flashable.zip is broken. i need help for this one too
3-build.prob will be replaced with xperia z v5 by markphyton so you wont see the original tweaks after the port
4-some of the roms will give bootloop because they have more space than our system partition. if some one can repartiton a kernel with more system storage it will be great
to do list:
1-making an armo zip with all build.prob form popular roms and the requested roms
2-adding touchpad fix
tested on(working):
1-anzumi : by myself
2-4.1.b.1.13(arc version by jader) : by myself
tested on(not working):
xperia ray 4.1.b.1.13 (touchscreen had some problems)
download link:
http://d-h.st/eJv
thanks to:
1-markphyton : i have taken my files from his rom
2-all the developers of xperia arc :for making roms(that gived me the idea of this patch)
3- xda: all of us know why
4-dev host : i use it for uploading my files
5-xperia play users : for not giving up
reserved
please help me for fixing the bugs
i will start working on gb and jb patch as soon as i get time
waiting for reports now
that all i can do now
if you want to help for completing this patch i need help for these things
1- someone with good knowledge in making armo installer and update.zip files
2-someone for helping me in making build.prob files of requested roms
3-(the moost ipmortant) helping me for fixing touchpads
Smokerman is good in porting roms, you should ask him for touchpad fix
I have basic knowledge of aroma installer and build.prop editing, if i can, i'll help
touchpads
@smokerman
can you help me for fixing the touchpads?
i will release an update soon
things that i changed:
1-fixed the flashable zip
2-im using 4.0.4 ics build.prob instead of xperia z rom by markphyton
jb patch is being tested now
for now i only get bootloops
but im trying to solve the problem
i aslo wanted to make an gb patch but i saw that we will get a little problem in gamepad after porting gb roms from arc
(always open game pad. you cant use touchscreen for gaming anymore in ported gb roms.)
pedyvirus said:
@smokerman
can you help me for fixing the touchpads?
Click to expand...
Click to collapse
i can help for sure..what is the rom? send me the link..i will look into it on the weekend.
well im making a patch for all of the roms
i need to know the way so i can support all the roms that xperia play users want
do you use farenheith's patch for fixing the touchpad in stock based roms?
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
pedyvirus said:
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
Click to expand...
Click to collapse
is it possible to port ics stock rom of arc to our device(xperia miro) (2012) ?????
a help would be appreciated!!! and i know @pedyvirus you can help me

Lastest Z1C 4.4.4 firmware (14.4.A.0.157) deodexed

Hy guys, I've deodexed the latest 14.4.A.0.157 firmware and made a flashable zip for the new 4.4.4 Firmware (using kamome tool).
based on 14.4.A.0.157 Generic uploaded by @Jozinek (download)
note : This is not a whole rom, only a deodex mod to use with stock 4.4.4 Firmware
Why I made it ?
I would try Z3 app but I needed deodexed firmware, so I decided to deodex it
What you need ?
- 4.4.4 firmware 14.4.A.0.157 (link above)
- root access (sony patched kernel so you may follow this to get root and dont forget to thanks @Jamal_RS)
- a recovery installed
- flashable deodex zip from :
* Google Drive (uploading), sorry I have some troubles to upload on my drive...
* Dropbox
* htcfanboys thanks to @sinosuke
* androidfilehost thanks to @sinosuke
for .108 version :
What you need ?
- 4.4.4 firmware .108 (second edition) from august 28 (download)
- root access
- a recovery installed
- flashable deodex zip from Google Drive - Dropbox
Instructions :
- Copy flashable zip to you SD CARD
- Enter Recovery
do not format /system or anything else otherwise you'll need to flash stock rom
- Flash deodexed 4.4.X YYY Z1C.zip file
- Reboot
- Enjoy deodexed firmware and feel free to install mods
Thanks dude... i need this... for same reason... try a new app from Z3...
Thanks boro
hey guys,
i just installed this, but now i am getting an OTA update (a small one) but i dont know how to install it as it tells me verification failed.
how can i install that OTA? or can I ask you for a favor on incorperating it into your zip please
solidd_swa said:
hey guys,
i just installed this, but now i am getting an OTA update (a small one) but i dont know how to install it as it tells me verification failed.
how can i install that OTA? or can I ask you for a favor on incorperating it into your zip please
Click to expand...
Click to collapse
Lock your bootloader again and it will works
Thanks --- solved my problem after accidentally flashing a deodex systemui, by the way do we have to zipalign after this? got any TUT how to do it or a script to zipalign every boot. Thanks!
themes never change...only the wallpaper....
waxiboy said:
themes never change...only the wallpaper....
Click to expand...
Click to collapse
For me themes are working fine
What's the different of first and second edition on .108?
Will this unlock bootloader!??
TheEndHK said:
What's the different of first and second edition on .108?
Click to expand...
Click to collapse
This second edition brings mainly security enhancement fixes :
-Android 4.4.4 including the latest enhancements and security updates from Google
-Updated and improved camera experience
-Improvements when using Google voice, Contacts, Music streaming and Google+
-The latest versions of our Sony apps for you to enjoy
-All of our latest bug fixes, optimisations & improvements
zike47222 said:
Will this unlock bootloader!??
Click to expand...
Click to collapse
No this will not unlock your bootloader
Hello Tonio78r i have a question, where I can download the firmware you mention? You never mention where to download :silly:
Mrchidongas said:
Hello Tonio78r i have a question, where I can download the firmware you mention? You never mention where to download :silly:
Click to expand...
Click to collapse
Indeed I forgot, here you go
added to OP
Thanks man
i have the stock version on my z1c, i want flash that mod in this thread -->http://forum.xda-developers.com/showthread.php?t=2730097 it's necessary an deodexed rom,so i think that i can install your version but..when there will be other Ota upgrade o other stock version, what i have to do? i have to wait that somebody will do an new deodexed version on last stock firmware?
thanks a lot
Axospirit said:
i have the stock version on my z1c, i want flash that mod in this thread -->http://forum.xda-developers.com/showthread.php?t=2730097 it's necessary an deodexed rom,so i think that i can install your version but..when there will be other Ota upgrade o other stock version, what i have to do? i have to wait that somebody will do an new deodexed version on last stock firmware?
thanks a lot
Click to expand...
Click to collapse
If you want your mods to work well (most of the time) it needs a deodexed rom, so you will need to wait until somebody make it. Be sure I'll make it as soon I can .
BTW this is just a mod so you will need to update your stock rom before flashing deodex mod
Hope I will help you
Tonio78r said:
If you want your mods to work well (most of the time) it needs a deodexed rom, so you will need to wait until somebody make it. Be sure I'll make it as soon I can .
BTW this is just a mod so you will need to update your stock rom before flashing deodex mod
Hope I will help you
Click to expand...
Click to collapse
Thanks for your response!
Which recovery have you used? I have tried the dualrecovery, but after flashing the zip it goes into bootloop.
baseman said:
Which recovery have you used? I have tried the dualrecovery, but after flashing the zip it goes into bootloop.
Click to expand...
Click to collapse
I used TWRP (included in dual recovery). Are you sure you've used the latest .108 firmware ?
You may try to download and flash latest sony 108 from here
BTW I'll make deodex for firmware 14.4.A.0.157 very soon, but I'll not be able to test it because my Z1C is in repair...
Tonio78r said:
I used TWRP (included in dual recovery). Are you sure you've used the latest .108 firmware ?
You may try to download and flash latest sony 108 from here
BTW I'll make deodex for firmware 14.4.A.0.157 very soon, but I'll not be able to test it because my Z1C is in repair...
Click to expand...
Click to collapse
Thank you very much! I'm waiting
Sent from my D5503

How to make kernel by myseflt?

Guys,
I am a newbie, and want to make my kernel by myself for N910C.
I was build my kernel successful, and got my zImage.
But i have problem when i recompile zImage into boot.img follow this tips:
http://forum.xda-developers.com/showthread.php?t=1877807
but it not work.
what was i missing?
anyone can help me to make it work?
Sorry for my bad English.

[GUIDE] PORTING 64BIT MTK ROMs (CROSS PORT Too)

Hi All,
This Guide is For Lenovo K3 Note Other devices can use it but some files may vary.
Here is a quick guide for getting the basics of the rom working.
Display, sound ,GSM (3g) and Wifi .
I used this for CyanogenMOD based ROMS and MIUI and it worked for me.
If anyone finds additional items or wants to complete this guide please feel free to add it in here.
Please remember, i am posting this so that people will try things and usually when they do, they end up finding something better and awesome than not trying.
I use this from stock and make it a zip file so it makes easy porting by just dragging the system folder with stock files to the rom to be ported and replace.
NOTE: ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else.
FOR CROSS PORT
SO THE FILES NEEDED TO REPLACE FROM STOCK TO PORT:
BIN FOLDER:
Code:
afm_server
akmd09911
applysig
audiocmdservice_atci
climax
custom_sn
encfs
factory
factory_reset.sh
fusermount
gzip_static
ipod
kpoc_charger
mtkbt
nvram_proximity
seeder
updater
vold
IF YOU THINK SOME FILES ARE ABSENT, DONT WORRY JUST SKIP THEM
NOW MODEM FILES:
Code:
take the whole [COLOR="Red"]firmware[/COLOR] folder from system/etc/
take the whole [COLOR="Red"]mddb[/COLOR] folder from system/etc/
NOW THE MAIN THING OF K3 Note (Audio)
Code:
take the whole folder [COLOR="Red"]tfa98xx[/COLOR] from system/etc/
NOW LIBS Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libbypass.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcam_hwutils.so
libcam_platform.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libipod.so
libJpgDecPipe.so
libJpgEncPipe.so
liblocSDK5c.so
liblocSDK_2_5OEM.so
libm4u.so
libMA3-wavesfx-Coretex_A9.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnetworklocation.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libshowlogo.so
libtfa9897_interface.so
libvc1dec_sa.ca7.so
libvcodecdrv.so
libvcodec_oal.so
libvcodec_utility.so
libweibosdkcore.so
mtk-ril.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
mtk-rilmd2.so [COLOR="Red"]<= IF U GET BOOT LOOP TRY WITHOUT REPLACING THIS FILE[/COLOR]
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\egl.cfg
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\bluetooth.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
soundfx\libmaxxeffect-cembedded.so
NOW LIB64 Folder:
Code:
lib3a.so
libacdk.so
libbluetoothdrv.so
libbluetooth_mtk.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.jni.lomohaljni.so
libcam.metadata.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.sensorlistener.so
libcam.utils.so
libcam1_utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libcamera_client_mtk.so
libcamera_metadata.so
libcam_hwutils.so
libcam_mmp.so
libcam_platform.so
libcam_utils.so
libcustom_nvram.so
libdpframework.so
libfeatureio.so
libfeatureiodrv.so
libhardware_legacy.so
libimageio.so
libimageio_plat_drv.so
libJpgDecPipe.so
libJpgEncPipe.so
libm4u.so
libmhalImageCodec.so
libMiraVision_jni.so
libmtkjpeg.so
libmtk_drvb.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libtfa9897_interface.so
libvcodecdrv.so
libvcodec_utility.so
And this subfolder with these libs:
Code:
drm\libfwdlockengine.so
egl\libGLES_mali.so
hw\audio.primary.mt6752.so
hw\audio_policy.default.so
hw\camera.mt6752.so
hw\gps.default.so
hw\gralloc.mt6752.so
hw\hwcomposer.mt6752.so
hw\lenovopower.default.so
hw\lights.default.so
hw\mmsdk.default.so
hw\sensors.mt6752.so
soundfx\libdownmix.so
NOW VENDOR FOLDER:
Code:
system\vendor\etc\audio_effects.conf
system\vendor\etc\default.mps
FOR DIFFERENT CHIPSET (i.e. 6795 to 6752)
Proceed as above THEN
open build.prop
EDIT THESE LINES
Code:
ro.mediatek.platform=[COLOR="Red"]MT6795[/COLOR] to [COLOR="Red"]MT6752[/COLOR]
mediatek.wlan.chip=[COLOR="Red"]MT6630[/COLOR]to [COLOR="Red"]CONSYS_MT6752[/COLOR]
mediatek.wlan.module.postfix=[COLOR="Red"]_mt6630[/COLOR]to [COLOR="Red"]_consys_mt6752[/COLOR]
And Now Boot.img
Unpack both stock and port boots from CarlivImageKitchen Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now
In port boot.img
replace the boot.img-kernel
and in ramdisk folder add these files:
fstab.mt6752
init.mt6752.rc
init.mt6752.usb.rc
AND DELETE THOSE with mt6795 and mt6595 words.
REPACK THE KERNEL
MAKE THE FLASHABLE ZIP
AND FLASH THE ROM
If u get WIFI AND BLUETOOTH NOT SWITCHING ON OR BATTERY PERCENTAGE WRONG THEN REPLACE init.project.rc
FOR SAME CHIPSET PORTING
Just replace
Code:
etc/firmware
etc/mddb
and from lib and lib64 hw folder replace all libs named like this camera.mt6752.so
and replace audio_policy.default.so from both hw folder
from lib and lib64
replace
Code:
libcameracustom.so
libaudiocomponentengine.so
libaudiocustparam.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libcustom_nvram.so
UPDATE :
TIP:To BOOT a rom with minimal replacements
Replace the boot.img files as usual
in system:
ETC FOLDER
etc/firmware
etc/mddb (not needed tho)
etc/tfa**(if your device uses)
LIB & LIB64
lib/libjni_pq.so
lib/libmtk_drvb.so
lib/libtfa****.so
lib64/libjni_pq.so
lib64/libmtk_drvb.so
lib64/libtfa****.so
HW folder
All the 67xx files if crossporting
VIOLA UR A PORTER
Can you add some image :3
Syaoran Lord said:
Can you add some image :3
Click to expand...
Click to collapse
i can add but image of what should i add
Porting to Ulefone be touch 2
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance
Ufoner said:
Hi! Nice tutorial. Will this method work with Ulefone be touch 2? I want to port Aerom v5 from elephone p7000 to Ulefone be touch 2. My kernel version is 3.10.61 and port rom kernel is 3.10.91 so I have to port kernel? Thanks in advance
Click to expand...
Click to collapse
yes it will work
no need to do anything about kernel u just proceed as the guide says
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
Ufoner said:
Thank you so much! And one more question please. Some guy try to port CM12.1 for BT2 and volume down button stopped working and screen is laggy. Installing stock ROM not solve that problem. Can happend this when i port android 5.0 or 5.1? Sorry for my bad English. Thanks in Advance.
Click to expand...
Click to collapse
try taking logcat while pressing the vol down key
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
jordandroid64 said:
Hello, I don't undestand that : ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else. please someone could explain for me ?
Click to expand...
Click to collapse
You need to delete file "recovery-from-boot.p" from system folder of your stock ROM and of port :good:
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
I ended again with black screen when porting cm12.1 from redmi note 2 Is it caused by another size of ram Because my device has 3gb ram and redmi note 2 has 2gb.
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
jordandroid64 said:
thanks but it's an img on my port rom and I don't find this file... and same on my stcok rom (androium) but there are files name recovery i need to delete all of them ?
Click to expand...
Click to collapse
You need to extract system.img with ext4unpacker and then make it folder with ext2explore. You dont need recovery so delete it
I have already extract the img but with ext2explore only that will be good also?
thanks for your answer
edit: edit : on the port rom at the last when i search recovery that whow me that :
http://www.hostingpics.net/viewer.php?id=839697recovery.jpg
Help me with bootloop please
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day
Ufoner said:
Hi sandeep.sethi!
Today i port your aicp 5.1.1 from k3 note to be touch 2(stock rom is android 5.0.1) and i got bootloop . I edited mount points and replaced all files as your guide says.
Do i need to port kernel or anything else when my device has 3gb ram and k3 note has 2gb ram All specs are same except the ram size.
Stock rom is 5.0.1, but alex1112 port cm12.1(5.1.1) to be touch 2, so do i need to port kernel from alex1112 cm12.1 or from my stock rom to AICP?
Is this guide for same android version ex. 50.1 to 5.0.1?
Thanks in advance and have a good day
Click to expand...
Click to collapse
then try using his kernel in the boot.img with my roms' ramdisk
Thanks but i have problem
sandeep.sethi said:
then try using his kernel in the boot.img with my roms' ramdisk
Click to expand...
Click to collapse
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
Ufoner said:
Thank you it worked, but when device start after bootanimation it show aicp is upgrading optimizing app starting apps ..... and then it restart and then again starting apps... and reboot. Please help. Thank you so much for your support.
Click to expand...
Click to collapse
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk
sandeep.sethi said:
what files did u replace from lib/hw and lib64/hw
or try taking cm12 of ur phone as base
Sent from my Lenovo K3 Note using Tapatalk
Click to expand...
Click to collapse
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:
Help with porting
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00
AnStu00 said:
Hello! Thanks for this awesome tutorial!
But now i need some help with porting a ROM
I am porting your BlissPOP rom from Lenovo K3 Note to my Elephone P7000 device!
when i install it with TWRP i get stuck in a bootloop
Can you please help me with this problem, i have followed the tutorial exactly as i should!¨
What should i do?
please help!
//AnStu00
Click to expand...
Click to collapse
I got bootloop too and sandeep.sethi told me how to fix it!
1. You need to change mount points in updater-script
2.Extract blisspop´s rom boot.img and extract boot.img from Elephone CM12.1 http://www.needrom.com/download/elephone-p7000-cyanogenmod-12-1/ and then copy blisspop rom ramdisk and copy it to cm12.1 boot.img and then repack it
Ufoner said:
I replaced all files except in lib and lib64 lenovopower.default.so and in drm i don´t replaced drm\libfwdlockengine.so because my stock rom don´t have these files. I tried this method to fix stuck in starting apps... http://www.mtkroms.com/2016/01/bugless-lollipop-exodus-for-mt6592.html and it not worked I searched that some people say the problem is in system apps and i need to replace them, is it true? Thanks, today i will try to port rom again with cm12.1 files If you help me and rom will boot i will donate to you bro :good:
Click to expand...
Click to collapse
okay try porting again and this tym in ramdisk replace factory rc files
Sent from my Lenovo K3 Note using Tapatalk

Categories

Resources