Database Info

Testers needed for sense roms

I have a port of a sense rom from the Sensation, and I need some testers. I don't have the phone with me right now so I can't test it out .. Please do this only if you know what you're doing. I am not to be held responsible for anything that may happen to your device. Please only developers. Also developers I advise you to check any thing I may have messed up starting with the updater-script. If you have the time please help me fix it. AND BE AWARE Only Developers as this is sort of a blind build, Don't even know if it boots. If you are interested here is the link: CLICK ME It's sort of a big build. Please check all the necessary system files before you flash.

Oooooh!! Sense.!! curious to what you ported.. link to op.?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
---------- Post added at 03:47 AM ---------- Previous post was at 03:47 AM ----------
Also I'd like to test.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

theprogram1 said:
I have a port of a sense rom from the Sensation, and I need some testers. I don't have the phone with me right now so I can't test it out .. Please do this only if you know what you're doing. I am not to be held responsible for anything that may happen to your device. Please only developers. Also developers I advise you to check any thing I may have messed up starting with the updater-script. If you have the time please help me fix it. AND BE AWARE Only Developers as this is sort of a blind build, Don't even know if it boots. If you are interested here is the link: CLICK ME It's sort of a big build. Please check all the necessary system files before you flash.
Click to expand...
Click to collapse
Not to sound dheadish but sense will never run on this phone end of story sorry
1st and most important reason is the kernel WE(as in the blaze community) don't have (not trying to piss anyone off and talk down about anyone I LOVE ALL OUR DEVS "NO HOMO") a true kernel Developer the things that u would have to change u would basically have to build the kernel from scratch... Your talking about going from HTC to Samsung there is just to many differences
2nd Sense won't run on or phone because of the Pure size and weight of it Sense roms r like 500+mb ours r 130mb to 300mb
3rd ud have to repartition the whole phone to get THAT" PORT" to even come close to booting
4th Your not gonna find anyone willing to put the work into making it happen for no payoff
5 if u want sense buy an HTC phone
Sorry bro
Edited
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

We are about to find out as I am backing up phone to prep for flash. I will post results later :silly:

phoenix98 said:
We are about to find out as I am backing up phone to prep for flash. I will post results later :silly:
Click to expand...
Click to collapse
Good luck ur asking for problems bro
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

phoenix98 said:
We are about to find out as I am backing up phone to prep for flash. I will post results later :silly:
Click to expand...
Click to collapse
True story, watching him do it right now

phoenix98 said:
We are about to find out as I am backing up phone to prep for flash. I will post results later :silly:
Click to expand...
Click to collapse
Didn't accept flash (surprise). Not speaking bad of dev for the port attempt as I willingly attempted to flash. It let me set up the phone (HTC style) but after a reboot, it went to the stock tmobile splash screen and stuck there. Phone is still operational and I am doing Odin to stock as we speak. So, at least this didnt kill the phone

phoenix98 said:
We are about to find out as I am backing up phone to prep for flash. I will post results later :silly:
Click to expand...
Click to collapse
phoenix98 said:
Didn't accept flash (surprise). Not speaking bad of dev for the port attempt as I willingly attempted to flash. It let me set up the phone (HTC style) but after a reboot, it went to the stock tmobile splash screen and stuck there. Phone is still operational and I am doing Odin to stock as we speak. So, at least this didnt kill the phone
Click to expand...
Click to collapse
And here I was, looking forward to the smoke clouds.

Thetenthdr said:
And here I was, looking forward to the smoke clouds.
Click to expand...
Click to collapse
Thats not cool man....jerk

In all seriousness though, it would be cool to see this working.

Thetenthdr said:
In all seriousness though, it would be cool to see this working.
Click to expand...
Click to collapse
Listen I looked at the zip and it's a custom rom (viperRom) for a sensation and it is for a CDMA network also so it'll never work for our phone guys and not to be a d-ck but program isn't a Dev or he wouldn't of posted this
Sorry don't get ur hopes up people never gonna happen
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
phoenix98 said:
Didn't accept flash (surprise). Not speaking bad of dev for the port attempt as I willingly attempted to flash. It let me set up the phone (HTC style) but after a reboot, it went to the stock tmobile splash screen and stuck there. Phone is still operational and I am doing Odin to stock as we speak. So, at least this didnt kill the phone
Click to expand...
Click to collapse
U don't have to odin stock just wipe system data cache and dalvik and restore backup
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
phoenix98 said:
Didn't accept flash (surprise). Not speaking bad of dev for the port attempt as I willingly attempted to flash. It let me set up the phone (HTC style) but after a reboot, it went to the stock tmobile splash screen and stuck there. Phone is still operational and I am doing Odin to stock as we speak. So, at least this didnt kill the phone
Click to expand...
Click to collapse
So Phoenix ur saying it booted to Google setup screen or how far did u get
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

johnb380 said:
Listen I looked at the zip and it's a custom rom (viperRom) for a sensation and it is for a CDMA network also so it'll never work for our phone guys and not to be a d-ck but program isn't a Dev or he wouldn't of posted this
Sorry don't get ur hopes up people never gonna happen
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
U don't have to odin stock just wipe system data cache and dalvik and restore backup
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
So Phoenix ur saying it booted to Google setup screen or how far did u get
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
Click to expand...
Click to collapse
CWMR wouldnt restore my backup for some reason (MD5 failure?) So, didnt have a choice. No biggie, doesnt bother me any.
2 seconds after I flashed, it went into a viper splash screen then into some weird set up that was in a transparent teal background with a bunch of setup prompts that were all HTC setup questions (CPU speed, theme, what apps I didnt want installed, ect). After that, I rebooted and it loaded like stock and got stuck on the tmobile splash screen and that was the end of this adventure. No offense, but your comments about this whole thing sound a little hostile. I had a pretty good idea that this wouldnt work, Im not THAT retarded :cyclops: Its been a long week at work, its Friday night, and I have nothing better to do than to mess with the Blaze. I'm fully aware what any flashing of anything may do to the phone. Its all good. I know you're just lookin out bro. Not many on here care enough to throw out the warnings. :good:

I should flash it to my S3 and see what happens...

phoenix98 said:
CWMR wouldnt restore my backup for some reason (MD5 failure?) So, didnt have a choice. No biggie, doesnt bother me any.
2 seconds after I flashed, it went into a viper splash screen then into some weird set up that was in a transparent teal background with a bunch of setup prompts that were all HTC setup questions (CPU speed, theme, what apps I didnt want installed, ect). After that, I rebooted and it loaded like stock and got stuck on the tmobile splash screen and that was the end of this adventure. No offense, but your comments about this whole thing sound a little hostile. I had a pretty good idea that this wouldnt work, Im not THAT retarded :cyclops: Its been a long week at work, its Friday night, and I have nothing better to do than to mess with the Blaze. I'm fully aware what any flashing of anything may do to the phone. Its all good. I know you're just lookin out bro. Not many on here care enough to throw out the warnings. :good:
Click to expand...
Click to collapse
Ya ur right I did sound hostile sorry EVERYONE but I don't want people to mess their stuff up but that's kinda awesome it booted but we Def need more info into what was done to this zip and what phone it was meant to be ported to but if it booted at all is kinda a big deal but I'm Def not a Dev and don't know it all i just followed someone else's failed journey to bring sense to a Sammy phone once upon a time and didn't want anyone getting excited I was trying to lower expectations for all the Newbs
Sorry again
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

johnb380 said:
Ya ur right I did sound hostile sorry EVERYONE but I don't want people to mess their stuff up but that's kinda awesome it booted but we Def need more info into what was done to this zip and what phone it was meant to be ported to but if it booted at all is kinda a big deal but I'm Def not a Dev and don't know it all i just followed someone else's failed journey to bring sense to a Sammy phone once upon a time and didn't want anyone getting excited I was trying to lower expectations for all the Newbs
Sorry again
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
Click to expand...
Click to collapse
Like I said, It's all good bro! But, in all reality, it didn't really boot after setup. It went to the stock T-Mobile loading splash screen and the blue bar went all the way across and stopped from there. I dunno, to me, thats not a boot, or successful one if that. But, I agree. The fact that it didnt brick and kind of took the flash, means that there may be hope after all for a Sense ROM. But, like you, Im not a dev either. Hopefully someone that is will eventually get to cookin :good:

Thanks for all the reply guys. As I said please be careful and you guys were and this is just a beginning as soon as I get some help and get my phone back I will do what ever it takes to fix this rom. Thanks for the replies and as I said in many other threads i'm a rookie.

Hopefully you get it going
Sent from my SGS3 running AeonFluxx v4

cm 10, the handset will not send sound

cm10.
Restart during a call, the handset will not send sound.

l666666z said:
cm10.
Restart during a call, the handset will not send sound.
Click to expand...
Click to collapse
Did u try wiping cache and dalvik cache in recovery then reboot
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

johnb380 said:
Did u try wiping cache and dalvik cache in recovery then reboot
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
Click to expand...
Click to collapse
yes,wipe twice

is the problem momentary or every time you call?
Sent from my SGH-T769 using xda app-developers app

skullreapper66 said:
is the problem momentary or every time you call?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
every time

[Q] Nandroid Backup to Update.zip??

I don't know if this has been covered or anywere within the forums ( HOPE NOT ...so i maybe could be there first to question it ) but if it has then damn anyways ive searched the forum after forum from diff sites other then and also xda to find the puzzling question ..........IS IT POSSIBLE TO MAKE A NANDROID BACKUP INTO AN UPDATE.ZIP without corrupting the backup files and having recovery state MD5 Mismatch etc that way they stay intact an a smaller compression size if at all possible please reply with a thread ( if this is already been pointed out ) if not please reply with an answer i would appreciate it thank you very much

soldier1184 said:
I don't know if this has been covered or anywere within the forums ( HOPE NOT ...so i maybe could be there first to question it ) but if it has then damn anyways ive searched the forum after forum from diff sites other then and also xda to find the puzzling question ..........IS IT POSSIBLE TO MAKE A NANDROID BACKUP INTO AN UPDATE.ZIP without corrupting the backup files and having recovery state MD5 Mismatch etc that way they stay intact an a smaller compression size if at all possible please reply with a thread ( if this is already been pointed out ) if not please reply with an answer i would appreciate it thank you very much
Click to expand...
Click to collapse
I'm not sure if u mean what I think u mean but u can always do a backup in image zip format it cuts the size down a lot and is an option in Official Cwm 6.0.1.4. In backup menu then I believe to restore you just wipe and flash the zip
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -

Apollo any answers
johnb380 said:
I'm not sure if u mean what I think u mean but u can always do a backup in image zip format it cuts the size down a lot and is an option in Official Cwm 6.0.1.4. In backup menu then I believe to restore you just wipe and flash the zip
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -If I've helped you the THANX button is - - - - - - - - - - - - - only 2 clicks away! - - - - - - - - - -
Click to expand...
Click to collapse
thanks an yes i see the button you have an answer as to why none of the roms c my music from the int. or ext. sdcard cause i reflashed an did a nandroid of the stock ics none root and it sees my music and plays it fine but for some reason the roms that i have in stockpile on my laptop no longer want to play nice

Closed per op's request.

unable to update firmware ota in samsung galaxy s duos

the error that i'm getting is "access to the software update service is provided to the users in which they request it.please try later"
i'm currently posted to a place where i don't have an access to laptop hence kies.
i hv already tried clearing cache n data for google services framework but it doesn't worked
so plz help

That's some weird error that Samsung usually puts out to its devices.
May be that means you will have to wait for some more time for the OTA update to reach you.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE! A ONE TIME OPPORTUNITY TO MAKE OR BREAK!

Lifehacker7 said:
That's some weird error that Samsung usually puts out to its devices.
May be that means you will have to wait for some more time for the OTA update to reach you.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE! A ONE TIME OPPORTUNITY TO MAKE OR BREAK!
Click to expand...
Click to collapse
so will i get notification for the update or i'll have to check it manually each day?
is there a way to get the update sooner?

sidc91 said:
so will i get notification for the update or i'll have to check it manually each day?
is there a way to get the update sooner?
Click to expand...
Click to collapse
What update are ya seeking?
Is it gonna be OTA or kies only?
Keep checking often.
It will notify you if there is an update but it might not be real time.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE! A ONE TIME OPPORTUNITY TO MAKE OR BREAK!

Lifehacker7 said:
What update are ya seeking?
Is it gonna be OTA or kies only?
Keep checking often.
It will notify you if there is an update but it might not be real time.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE! A ONE TIME OPPORTUNITY TO MAKE OR BREAK!
Click to expand...
Click to collapse
it is an ota as well as a kies update i have read about the update at sammobile.com. it's a crucial update since it has fixes to many problems that my phone has so i'm desperate to get an update as soon as possible but i won't have access to laptop or pc till may

[Guide][Cross-Porting][MT6580] Android Lollipop 5.1 Roms

Guide to Cross-port lollipop roms for Mediatek MT6580 chipset​
This guide is intended for advanced and experienced porters only, if you are a noob you may stuck at some part.
I made this guide because too many people were asking for it.
As usual, you do everything at your own risk!
Using this Guide, you will be able to cross port lollipop 5.1 roms from chipset MT6582 and MT6592 with kernel 3.10.72
You can even port MT6580 roms with this method, which bootloops when using normal porting!​
Some Notices:
- Huawei roms comes in update.app format, you must extract it first.
- Huawei roms has a separate file called cust.img or custom.img, you have to unpack this too and move the files to the right places in system
- Replacing libcameraserivces.so and libcameracilent.so are known to cause bootloop
- Replacing lib/drm folder , libdrmmtkutil.so and libdrmmtkwhitelist.so are figured out to cause bootloop or problem in displaying/playing all media; like photos, videos, music.
- Some roms might bootloop even after applying this method, you have to take a logcat and try to fix it.
Now let's start:
1- Download the port rom, and unpack system.img using SuperR's Kitchen (This is the only fully working kitchen I know)
By using this kitchen you will be able to unpack the system.img and generate the updater-script, but you will still need a full META-INF folder.
If you can't generate Updater-script or don't know how, please stop here, or you will have bugs and FCs in your ported rom.
2- After unpacking the system.img, go to /system search for all files with name mt6582/92 and delete them.
- Open build.prop using Notepad++
- Replace all MT6582 or MT6592 to MT6580
- Check this line for on screen buttons: qemu.hw.mainkeys , (To disable or enable it)
- Check this line for screen resolution: ro.sf.lcd_density
3- Go to system/app and delete MTKThermalManager
you can replace this from your stock rom.
4- Go to system/bin and add or replace the following:
- 6620_launcher
- 6620_wmt_concurrency
- 6620_wmt_lpbk
- aee
- aee_archive
- aee_core_forwarder
- aee_dumpstate
- akmd8963
- akmd8976
- akmd09911
- ami304d
- acti_service
- atcid
- audicmdservice_acti
- bmm050d
- ccci_fsd
- ccci_mdinit
- geomagneticd
- gsm0710muxd
- gsm0710muxdmd2
- guiext-server
- lsm303md
- mc6420d
- md_ctrl
- mdlogger
- memsicd
- memsicd3416x
- mtk_agpsd
- mtkbt
- MtkCodecService
- muxreport
- nvram_agent_binder
- nvram_daemon
- permission_check
- ppl_agent
- pq
- s62xd
- spm_loader
- terservice
- thermal
- thermal_manager
- thermald
- tiny_mkswap
- tiny_swapoff
- tiny_swapon
- wifi2agps
- wmt_loader
5- Go to system/etc and add or replace the following:
- firmware
- fmr
- mddb
- radvd
- wifi
- audio_device.xml
- audio_effects.conf
- audio_policy.conf
- custom.conf
- mtk_omx_core.cfg
- mtklog-config.prop
- throttle.sh
6- Go to system/lib and add or replace the following:
- egl
- hw
- lib3a.so
- libaal.so
- libadpcm.so
- libaed.so
- libAGifEncoder.so
- libatciserv_jni.so
- libaudiocompensationfilter.so
- libaudiocomponentengine.so
- libaudiocustparam.so
- libaudiodcrflt.so
- libaudiomtkdcremoval.so
- libaudiosetting.so
- libbessound_hd_mtk.so
- libblisrc32.so
- libblisrc.so
- libbluetooth_mtk.so
- libbluetooth_relayer.so
- libbluetoothdrv.so
- libbluetoothem_mtk.so
- libBnMtkCodec.so
- libbwc.so
* Note: You will probably need all camera libs to get camera working, but do not replace libcameraservices.so and libcameraclient.so , these two libs are known to cause bootloop!
- libcamalgo.so
- libcamdrv.so
- libcameracustom.so
- Replace other camera libs when needed
- libccci_util.so
- libcurl.so
- libcustom_nvram.so
- libcvsd_mtk.so
- libdirect-coredump.so
- libdpframework.so
- libdrmframework.so
- libextmap.so
- libextmap_jni.so
- libextsimap.so
- libextsimap_jni.so
- libextsys.so
- libextsys_jni.so
- libexttestmode.so
- libfeatureio.so
- libfm* (means all files with name libfm - not important)
- libGdmaScalerPipe.so
- libged.so
- libgpu_aux.so
- libgralloc_extra.so
- libgraphite2.so
- libgui_ext.so
- libh264dec_customize.so
- libh264dec_sd.ca7.so
- libh264dec_xa.ca7.so
- libh264dec_xb.ca7.so
- libh264enc_sa.ca7.so
- libhwm.so
- libimageio.so
- libimageio_FrmB.so
- libimageio_plat_drv.so
- libimageio_plat_drv_FrmB.so
- libion.so
- lbion_mtk.so
- libJpgDecPipe.so
- libJpgEncPipe.so
- libm4u.so
- libMali.so
- libmatv_cust.so
- libmediatek_exceptionlog.so
- libmhalImageCodec.so
- libmmprofile.so
- libmmprofile_jni.so
- libmmsdkservice.feature.so
- libmmsdkservice.so
- libmnl.so
- libmp4dec_sa.ca7.so
- libmp4dec_sb.ca7.so
- libmp4enc_xa.ca7.so
- libmpo.so
- libmpodecoder.so
- libmpoencoder.so
- libmpojni.so
- libmsbc_mtk.so
- libmtb.so
- libmtcloader.so
- libmtk_drvb.so
- libmtk_mali_user.so
- libmtk_mmutils.so
- libmtkjpeg.so
- libMtkOmx* (Means all the files with name LibMtkOmx)
- libmtkplayer.so
- libmtklimiter.so
- libmtkshifter.so
- libnativecheck-jni.so
- libnvram.so
- libnvram_daemon_callback.so
- libnvram_platform.so
- libnvram_sec.so
- libnvramagentclient.so
- libpalsecurity.so
- libpalwlan_mtk.so
- libperfservice.so
- libperfservicenative.so
- libpq_cust.so
- libpq_prot.so
- libsensorservice.so
- libsbccodec.so
- libshowlogo.so
- libspeech_enh_lib.so
- libssladp.so
- libstagefright_amrnb_common.so
- libstagefright_avc_common.so
- libstagefright_enc_common.so
- libstagefright_omx.so
- libstagefright_soft_gsmdec.so
- libstagefrighthw.so
- libsuspend.so
- libSwJpgCodec.so
- libterservice.so
- libtinycompress.so
- libtinyxml.so
- libtouchfilter.so
- libui_ext.so
- libvc1dec_sa.ca7.so
- libvcodec_oal.so
- libvcodec_utility.so
- libvcodecdrv.so
- libvp8dec_sa.ca7.so
- libvp8dec_xa.ca7.so
- libvp9dec_sa.ca7.so
- libwifitest.so
Note: replace ril files in lib and bin folders only when you have FCs or a problem.
7- Go to system/vendor and replace the following:
- lib
8- Go to system/xbin and replace the following:
- BGW
- mnld
9- Boot.img part:
- Use SuperR's kitchen or Carliv image kitchen or any other boot.img tool to unpack the kernel
- Copy from port ramdisk to stock ramdisk:
init.environ.rc (very important)
init.rc
- Compare those files and add extra lines:
init.project.rc
init.mt65xx.rc
defualt.prop
Then repack stock boot.img
10- Zip the rom now and flash it.
This guide is based on Nonta method and my experience​
I won't be able to write this guide without Nonta helping me during my porting Journey xD
Credits:
Nonta72

Holy moly! This port worked! It's beautiful. I ported ToXperia MOD from MT6592, Infinix HOT NOTE PRO (Kernel 3.10.72+, Android 5.1) to my Infinix HOT 3 (Kernel 3.10.72+, Android 5.1, MT6580). I can't thank you enough!

Raibatsu said:
Holy moly! This port worked! It's beautiful. I ported ToXperia MOD from MT6592, Infinix HOT NOTE PRO (Kernel 3.10.72+, Android 5.1) to my Infinix HOT 3 (Kernel 3.10.72+, Android 5.1, MT6580). I can't thank you enough!
Click to expand...
Click to collapse
Congratulations bro ?

Thank you Mr.Ahmed Rahmy! this is what i'm searching for.
Mysteryagr said:
Guide to Cross-port lollipop roms for Mediatek MT6580 chipset​
This guide is intended for advanced and experienced porters only, if you are a noob you may stuck at some part.
I made this guide because too many people were asking for it.
As usual, you do everything at your own risk!
Using this Guide, you will be able to cross port lollipop 5.1 roms from chipset MT6582 and MT6592 with kernel 3.10.72
You can even port MT6580 roms with this method, which bootloops when using normal porting!​
Some Notices:
- Huawei roms comes in update.app format, you must extract it first.
- Huawei roms has a separate file called cust.img or custom.img, you have to unpack this too and move the files to the right places in system
- Replacing libcameraserivces.so and libcameracilent.so are known to cause bootloop
- Replacing lib/drm folder , libdrmmtkutil.so and libdrmmtkwhitelist.so are figured out to cause bootloop or problem in displaying/playing all media; like photos, videos, music.
- Some roms might bootloop even after applying this method, you have to take a logcat and try to fix it.
Now let's start:
1- Download the port rom, and unpack system.img using SuperR's Kitchen (This is the only fully working kitchen I know)
By using this kitchen you will be able to unpack the system.img and generate the updater-script, but you will still need a full META-INF folder.
If you can't generate Updater-script or don't know how, please stop here, or you will have bugs and FCs in your ported rom.
2- After unpacking the system.img, go to /system search for all files with name mt6582/92 and delete them.
- Open build.prop using Notepad++
- Replace all MT6582 or MT6592 to MT6580
- Check this line for on screen buttons: qemu.hw.mainkeys , (To disable or enable it)
- Check this line for screen resolution: ro.sf.lcd_density
3- Go to system/app and delete MTKThermalManager
you can replace this from your stock rom.
4- Go to system/bin and add or replace the following:
- 6620_launcher
- 6620_wmt_concurrency
- 6620_wmt_lpbk
- aee
- aee_archive
- aee_core_forwarder
- aee_dumpstate
- akmd8963
- akmd8976
- akmd09911
- ami304d
- acti_service
- atcid
- audicmdservice_acti
- bmm050d
- ccci_fsd
- ccci_mdinit
- geomagneticd
- gsm0710muxd
- gsm0710muxdmd2
- guiext-server
- lsm303md
- mc6420d
- md_ctrl
- mdlogger
- memsicd
- memsicd3416x
- mtk_agpsd
- mtkbt
- MtkCodecService
- muxreport
- nvram_agent_binder
- nvram_daemon
- permission_check
- ppl_agent
- pq
- s62xd
- spm_loader
- terservice
- thermal
- thermal_manager
- thermald
- tiny_mkswap
- tiny_swapoff
- tiny_swapon
- wifi2agps
- wmt_loader
5- Go to system/etc and add or replace the following:
- firmware
- fmr
- mddb
- radvd
- wifi
- audio_device.xml
- audio_effects.conf
- audio_policy.conf
- custom.conf
- mtk_omx_core.cfg
- mtklog-config.prop
- throttle.sh
6- Go to system/lib and add or replace the following:
- egl
- hw
- lib3a.so
- libaal.so
- libadpcm.so
- libaed.so
- libAGifEncoder.so
- libatciserv_jni.so
- libaudiocompensationfilter.so
- libaudiocomponentengine.so
- libaudiocustparam.so
- libaudiodcrflt.so
- libaudiomtkdcremoval.so
- libaudiosetting.so
- libbessound_hd_mtk.so
- libblisrc32.so
- libblisrc.so
- libbluetooth_mtk.so
- libbluetooth_relayer.so
- libbluetoothdrv.so
- libbluetoothem_mtk.so
- libBnMtkCodec.so
- libbwc.so
* Note: You will probably need all camera libs to get camera working, but do not replace libcameraservices.so and libcameraclient.so , these two libs are known to cause bootloop!
- libcamalgo.so
- libcamdrv.so
- libcameracustom.so
- Replace other camera libs when needed
- libccci_util.so
- libcurl.so
- libcustom_nvram.so
- libcvsd_mtk.so
- libdirect-coredump.so
- libdpframework.so
- libdrmframework.so
- libextmap.so
- libextmap_jni.so
- libextsimap.so
- libextsimap_jni.so
- libextsys.so
- libextsys_jni.so
- libexttestmode.so
- libfeatureio.so
- libfm* (means all files with name libfm - not important)
- libGdmaScalerPipe.so
- libged.so
- libgpu_aux.so
- libgralloc_extra.so
- libgraphite2.so
- libgui_ext.so
- libh264dec_customize.so
- libh264dec_sd.ca7.so
- libh264dec_xa.ca7.so
- libh264dec_xb.ca7.so
- libh264enc_sa.ca7.so
- libhwm.so
- libimageio.so
- libimageio_FrmB.so
- libimageio_plat_drv.so
- libimageio_plat_drv_FrmB.so
- libion.so
- lbion_mtk.so
- libJpgDecPipe.so
- libJpgEncPipe.so
- libm4u.so
- libMali.so
- libmatv_cust.so
- libmediatek_exceptionlog.so
- libmhalImageCodec.so
- libmmprofile.so
- libmmprofile_jni.so
- libmmsdkservice.feature.so
- libmmsdkservice.so
- libmnl.so
- libmp4dec_sa.ca7.so
- libmp4dec_sb.ca7.so
- libmp4enc_xa.ca7.so
- libmpo.so
- libmpodecoder.so
- libmpoencoder.so
- libmpojni.so
- libmsbc_mtk.so
- libmtb.so
- libmtcloader.so
- libmtk_drvb.so
- libmtk_mali_user.so
- libmtk_mmutils.so
- libmtkjpeg.so
- libMtkOmx* (Means all the files with name LibMtkOmx)
- libmtkplayer.so
- libmtklimiter.so
- libmtkshifter.so
- libnativecheck-jni.so
- libnvram.so
- libnvram_daemon_callback.so
- libnvram_platform.so
- libnvram_sec.so
- libnvramagentclient.so
- libpalsecurity.so
- libpalwlan_mtk.so
- libperfservice.so
- libperfservicenative.so
- libpq_cust.so
- libpq_prot.so
- libsensorservice.so
- libsbccodec.so
- libshowlogo.so
- libspeech_enh_lib.so
- libssladp.so
- libstagefright_amrnb_common.so
- libstagefright_avc_common.so
- libstagefright_enc_common.so
- libstagefright_omx.so
- libstagefright_soft_gsmdec.so
- libstagefrighthw.so
- libsuspend.so
- libSwJpgCodec.so
- libterservice.so
- libtinycompress.so
- libtinyxml.so
- libtouchfilter.so
- libui_ext.so
- libvc1dec_sa.ca7.so
- libvcodec_oal.so
- libvcodec_utility.so
- libvcodecdrv.so
- libvp8dec_sa.ca7.so
- libvp8dec_xa.ca7.so
- libvp9dec_sa.ca7.so
- libwifitest.so
Note: replace ril files in lib and bin folders only when you have FCs or a problem.
7- Go to system/vendor and replace the following:
- lib
8- Go to system/xbin and replace the following:
- BGW
- mnld
9- Boot.img part:
- Use SuperR's kitchen or Carliv image kitchen or any other boot.img tool to unpack the kernel
- Copy from port ramdisk to stock ramdisk:
init.environ.rc (very important)
init.rc
- Compare those files and add extra lines:
init.project.rc
init.mt65xx.rc
defualt.prop
Then repack stock boot.img
10- Zip the rom now and flash it.
This guide is based on Nonta method and my experience​
I won't be able to write this guide without Nonta helping me during my porting Journey xD
Credits:
Nonta72
Click to expand...
Click to collapse