MT6592 CM 12.1 PORTING GUIDE
Lots of people asked me how i ported cm 12.1 from @fire855's compiled rom for kingzone k1 Turbo
First of all huge thanks to @fire855 and other Dev who helped him for bringing cm 12.1 on mt6592
Give support to him via pressing thanks or Donate , here is it's Link : http://forum.xda-developers.com/and...od-12-kingzone-k1-turbo-t3119908#post61000671
Requirements :
1. Stock Rom KK
2. Working Good Custom Recovery
3. Good Porter and Mind
Lets Start This Short Guide :
1. Download Latest Cm 12.1 from above link
2. Extract in a new folder
3. Use this tool LInk : http://forum.xda-developers.com/android/development/tool-convert-folder-to-ext4-format-t3099237
unpack .dat file and copy extracted system folder in new folder as stated in step 2.
4. Using @michfood's tool (link : http://forum.xda-developers.com/showthread.php?t=2036528)
change Kernel and Do necessary changes acc. to your stock's ramdisk
5. Copy new boot.img that created in step 4 and replace in new folder as stated in step 2.
6. From stock kk rom ...........extract libaudio.primary.default.so (system/lib) and modem.img (system/etc/firmware) nd replace in cm 12.1 's rom ................ in the same location
7. Delete meta-inf folder of cm 12.1's rom and extract this (link : https://www.sendspace.com/file/vnf0gi)
8. Open meta-inf's updater-script in notepad++ and change mountpoint of system acc. to your's phone
9. Pack the folder as in zip format and flash via recovery
( meta-inf, install ,system, boot.img, file context these files must there in zip )
10. Voila Rom booted .............if not comment
If Rom Booted ..............Follow this steps :
1. Download this apk (link : http://forum.xda-developers.com/showthread.php?t=2524485)
2. Go to Settings>developer>enable root and install apk from step 1
3. Open app and Set as permissive ,reboot Your device
4. Voila your wifi,bluetooth etc will start working, even Dual Sim
5. If you faced basedband unknown that mean restore your imei
6. For Home Key Bug , Edit generic.kl and mtk-kpd.kl (system/user/keylayout)
7. For Storage Bug, Edit Framework-res.apk and set sdcard1 as primary and edit boot's ramdisk MT6592.rc, fstab
8. For Other Bugs, Let Me Know
Notice : Always give thanks and link of @fire855's Rom Link
Credits : everyone (who's name i added in this guide and there's tools )
@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...
contactwajeeh said:
@[email protected]. . . . but mic is not working . . . .
Click to expand...
Click to collapse
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic
G-GFFD said:
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic
Click to expand...
Click to collapse
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.
What necessary changes i must do in ramdisk?help
contactwajeeh said:
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.
Click to expand...
Click to collapse
currently mic problem is there ....wait for fixes
contactwajeeh said:
@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...
Click to expand...
Click to collapse
edit keylayout's genric.kl etc
mirrr46 said:
What necessary changes i must do in ramdisk?help
Click to expand...
Click to collapse
like some some extra lines der in urs .
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: No such file or directory
m_file:s0 failed: Operation not supported on transport endpoint
Error flashing Zip : Failed
Updating partition details...
Click to expand...
Click to collapse
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
1. don't touch kernel header....change only kernel
2. u should try other recovery like philz
3. delete lost and found folder if present
4. use my meta-inf only....just change mountpoint of system........it seems u need good recovery with lp supported or philz recovery :fingers-crossed:
Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?
mirrr46 said:
Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?
Click to expand...
Click to collapse
1. camera icon in launcher is issue (for mt6592)
2. for storage...fixes r from mt6592.rc in this file read proper sysmlink and do changes acc. to it ,decompile framework-res.apk....set sdcard1 as primary ,fstab changes also needed
Enforcing to Permissive
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?
Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
ADev_28 said:
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?
Click to expand...
Click to collapse
/system/bin/setenforce 0
From any root terminal.
Thanks,
1. But i did port for mtk6582 (camera unfortunelty has stop)
chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12
[email protected] said:
1.
Click to expand...
Click to collapse
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app
lopestom said:
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
congo
Traace said:
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12
Click to expand...
Click to collapse
mirrr46 said:
1. But i did port for mtk6582 (camera unfortunelty has stop)
Click to expand...
Click to collapse
seems storage bug...u need to fix storage .............check guide and comments
chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
i don't think so....again try and don't touch ramdisk
[email protected] said:
congo
seems storage bug...u need to fix storage .............check guide and comments
i don't think so....again try and don't touch ramdisk
Click to expand...
Click to collapse
How to solve storage bug??
Device booted.Not able to mount/access storage. ??
Related
Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes
Hello Viewers! I am Rohan Taneja, here with completely re-written guide to Port MTK65xx Roms.
I had left MTK development since a year and I finally got another MTK device to carry with it again.
{
"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"
}
So, Many Of You May be MTK Device User than you are at right place to fill your device with many awesome roms!
Note: Android ONE devices (MT6582 SoC) use Google's device tree, meaning they differ on everything with all the other MediaTek devices (even the ones with the same SoC , MT6582), as per @superdragonpt told us
Requirements:
A MTK powered device
USB Cable
Usable Brains :cyclops:
Knowledge about Flashing & Taking Logs :angel:
Stock Firmware (from manufacturer) & Port Firmware (matching specification of your device)
Custom Recovery installed on device
Porting Tips
Choose Custom ROM from a device matching same resolution to reduce App Size related bugs
This Guide Applies to
MT6577 to MT6577, vice-versa
MT6589 to MT6589, vice-versa
MT6572 to MT6572, vice-versa
MT6582 to MT6582, vice-versa
Note: Try it at your own risk, and don't complaint any developer or XDA if any mishap takes place. :good:
TUTORIAL:Starting with the tutorial, I request you to follow every single step written below to prevent any kind of problem in flashing and causing bootloop. I also dare you to take a nandroid backup of your current rom you are using.
Get. Set. Go.
Step 1 : Patching System Folder for the port patch.First of all make a folder named "Port_Patch" and setup all the folder as shown in the images below.
Now, in Port_Patch make system folder in which make folders, "bin" "etc" "lib" "usr" "vendor" "xbin" (without ")
In folder "bin" copy pq & vold from your stock rom
In folder "etc" copy "bluetooth" "firmware" "wifi" "apns-conf.xml" "vold.fstab" "vold.fstab.nand"
In folder "lib" copy files as shown in the image
In folder "usr" copy usr/keylayout/Generic.kl
In folder "vendor" all the files
In folder "xbin" copy "libmnlp_mt662x" (x - '0' or '8') from stock
System has been patched, copy this /system to patch the /system of port ROM.
Step 2: Patching the boot.img of the port rom.This is bit tricky but can be done easily.
So, first of download this little tool, to unpack & repack your boot.img - MTKbootimg.zip - tested on Windows 7 & above platform
Extract the Tool and you will get two folders named "stock" & "port"
Copy boot.img's respectively from stock rom in "stock" folder & from port rom to "port"
Unpack both boot.img repectively and they may look like this.
From stock copy "kernel" to port folder and just replace it.
Now, repack it, new file named "boot-new.img" will be generated.
Copy "boot-new.img" to port Rom Folder.
Delete existing "boot.img" and rename "boot-new.img" to "boot.img"
Now, your boot.img is patched, proceed to last step.
Step 3: Modifying updater-script to install ROM accordingly.
So, it's the last step before flashing the rom. Now lets fix it.
First, you have to know your device mount points, that can be tracked using MTKDroid Tool or check them in stock rom updater-script.
I have my flashable stock rom so I will get mount points from it.
As show in the image, my stock updater have different mount point for system & data while port have different.
Now, replace "mmcblk0pX" (X - no. for the mount) from stock to port as designated for the partition.
Now Save the updater-script.
Finally, the ROM is ready to flashed.
Step 4: Compressing & Flashing the ROM.
Now, the rom is ready to be packed and flashed.
Simply get to the main directory with META-INF, system, boot.img, etc files.
Select all the files and compress them to zip. Select the compression ratio as you want.
After compressing copy the ROM into root of sdcard
Enter Custom Recovery, wipe data & Cache
Flash the ROM.zip wait till it completes.
Wait till it boots, or else take log using ADB logcat. (Hint: If LED light blinks, the rom is booting)
FOR Fixes Proceed to next post and find out the way to tackle and fix the bugs.
Fixing ROM issues
Finally Ported a Custom ROM. Now, time to kill out some bugs.
Its all about making the build stable for personal as well as others to use it.
Leave the files if not there in your System
Let's get started:
Bootloop? :crying:
Replace following files(from stock to port):
Code:
[LIST]
[*]libandroid_runtime.so
[*]libandroid_servers.so
[*]libmedia_jni.so
[*]libsync.so
[*]If possible try modifying framework.jar "\smali\com\android\server" (copy from stock)
[/LIST]
Camera Not Working?
Replace following files(from stock to port):
Code:
[HIDE][LIST]
[*]lib3a.so
[*]liba3m.so
[*]libacdk.so
[*]libaudioflinger.so
[*]libc.so
[*]libcam.camadapter.so
[*]libcam.campipe.so
[*]libcam.camshot.so
[*]libcam.client.so
[*]libcam.paramsmgr.so
[*]libcam.utils.so
[*]libcam_camera_exif.so
[*]libcamalgo.so
[*]libcamdrv.so
[*]libcamera_client.so
[*]libcamera_jni_eglfence.so
[*]libcamera_metadata.so
[*]libcameracustom.so
[*]libcameraservice.so
[*]libgn_camera_feature.so
[*]libexif
[*]libfeatureio.so
[*]libfrsdk.so
[*]libft.so
[*]libgcomm_jni.so
[*]libgoggles_clientvision.so
[*]libgui.so
[*]libimageio.so
[*]libja3m.so
[*]libjni_mosaic.so
[/LIST]
Thanks To [I]Shikar A[/I][/HIDE]
[B]Init.rc Fix:[/B]
[HIDE]Init.rc(present in the ramdisk of boot.img), find for code #Camera in stock boot.img. Copy it and replace from stock init.rc and replace in the port init.rc
[IMG]http://s27.postimg.org/4ucj34cwj/initrc_cam.png[/IMG][/HIDE]
Wlan not working properly?
Code:
Check wlan.chip in stock like:
[HIDE][IMG]http://s30.postimg.org/myaya0sxt/Untitled.png[/IMG]
fmradio.driver.chip=x (if mt6620 then x=1, if mt6628 then x=3)
Change the above codes accordingly in updater-script
Replace the version in port from the one in stock[/HIDE]
(Replace from stock to port)
libbluetooth_mtk.so
libbluetoothem_mtk.so
GPS, unstable or not working?
(Replace from stock to port)
Code:
xbin/libmnlp
Media Player problem?
(Replace from stock to port)
Code:
libdpframework.so
libcodecvdrv.so
Sensors not working properly?
(Replace from stock to port)
Code:
libsensorservice.so
SD Card not working or mounting?
Code:
In the framework-res.apk of your port, replace /res/xml/storage_list.xml from stock one.
USB not mounting your device?
Code:
Unpack your boot.img replace init.usb.rc from ramdisk by stock boot.img init.usb.rc
This tutorial worked for porting MIUI, Baidu, Vibe UI, LeWa OS, AOSP based rom from different device to my MT6589 of same hardware.
Credits:
Special Thanks to @yuweng (for starting his main MTK porting thread and his great works)
XDA-Developers being one of the best place for Android Development
Other Developers for helping in fixing most the issues.
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
iel0000 said:
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
Click to expand...
Click to collapse
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
A N D Y said:
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
Click to expand...
Click to collapse
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
iel0000 said:
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
Click to expand...
Click to collapse
Don't Worry Try The one in the Ported Rom!
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
xjammetx said:
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
Click to expand...
Click to collapse
what boot.img did you use? stock from cherry mobile?
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
iel0000 said:
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
Click to expand...
Click to collapse
Those Files You Can't Find In port just leave that!
A N D Y said:
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
Click to expand...
Click to collapse
can i use stock boot.img from my phone?or do i have to modify it?
Very nice thread, for beginners that want to learn
tried porting miui v5 base on jb 4.1.2
always stock on boot animation
iel0000 said:
can i use stock boot.img from my phone?or do i have to modify it?
Click to expand...
Click to collapse
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Yep. Dont worry, ill upload it sometime.
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
how to use the tool?
How to from STOCK
iel0000 said:
how to use the tool?
Click to expand...
Click to collapse
Do you know procedure to Port a STOCK ROM(SP Flash tool format not a CWM) of X device to Y device?
Both are mostly same in specifications except the resolution.
I read in some threads that we can not port a rom from a device which has different resolution ?
Thanks in Advance
iel0000 said:
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
Click to expand...
Click to collapse
what phone do you have btw?
yo kumpare!
@chrmhoffmann compiled first ever CyanogenMod for his Wiko Stairway which is a MT6589 device and made it possible for other MT6589 users to taste CM. Since then many are porting it to their MT6589 device and many are requesting to make a port for their device. So, I have made a guide here to make it easier for them to port themselves. You should give proper credits to respected developers and hit thanks before posting on XDA.
NOTE:I have made a list of already ported CM roms in #2 post below , if your device is not listed there download any of the ported CM rom and follow this guide to port it to your device
This is the guide to port CM 10.2/11 for all MT6589 devices.Read carefully and follow each step correctly otherwise CM won't boot
Tools Required:
1) Archive Manger (winrar,winzip,7zip)
2) boot.img Unpack Repack Tools
http://forum.xda-developers.com/showthread.php?t=1587411(For Linux)
http://forum.xda-developers.com/showthread.php?t=2036528(For Windows)
NOTE:
For CM 11 the same proceedure is followed but the stock boot.img must be having kernel with binder.c patched and SELinux enabled (This feature can be bypassed but binder.c patch is must otherwise CM 11 won't boot)
Guide:
1) First get your stock rom and download any ported CM 10.2/11 rom from #2 post below
2) Get boot.img from your phone(stock rom) and boot.img from downloaded CM-ROM.zip
3) Unpack both of them to get ramdisk and kernel of both.
4) Repack CM's ramdisk and stock kernel (your phone's) to get a new boot.img
5) Extract system folder from your phone(stock rom) and system folder from downloaded CM-ROM.zip
6) Copy and replace these files from stock to CM,
=> /lib/modules/ -> all files
=> /framework/ -> CustomProperties.jar
mediatek-common.jar
mediatek-framework.jar
mediatek-op.jar
secondary-framework.jar
=> Also all the files mentioned in the below link ( A great thanks to Kashifmin for providing this )
https://github.com/kashifmin/android_device_micromax_a116/blob/master/proprietary-files.txt
7) Now take the modified CM system folder and the new boot.img and make a zip archive with normal deflate compression ( are default in 7zip)
8) Open the newly created zip archive and downloaded CM-rom.zip .Now drag and drop the META-INF and file_contexts from downloaded CM-rom.zip to newly created zip archive.
9) Now flash the new zip using recovery (CWM/TWRP)
10) Enjoy !!
CREDITS:
@michfood for his Boot unpack/repack utils for WINDOWS.
@bgcngm for his Boot unpack/repack scripts for LINUX.
@kashifmin for his proprietary-files.txt
@kashifminfor guiding me.
@chrmhoffmann For bringing the first ever CM10.2 for an MT6589 device.
@XpLoDWilD
@Dr-Shadow
OmniROM project.
Available CM port builds for MT6589
CM 10.2 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2467400
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2673367
XOLO Q700/Q700i -> http://forum.xda-developers.com/showthread.php?t=2675963
LAVA 458Q / XOLO Q600 / CROSS A88 -> http://forum.xda-developers.com/and...-cross-a88-t2814034/post54103404#post54103404
CUBOT GT99 / Cherry Apollo / XYZ X1 -> http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
CM 11 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2676086
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2676896
ACER liquid e2 v370 -> http://forum.xda-developers.com/showthread.php?t=2766290
MMX Canvas Magnus (A117) -> http://forum.xda-developers.com/canvas-magnus/development/rom-cyanogenmod-11-canvas-magnus-a117-t2790957
MMX Canvas 2+ (A110Q) / Fly IQ450 -> http://forum.xda-developers.com/mic...-2-cyanogenmod-11-port-canvas-2-plus-t2750867
MMX Canvas Turbo (A250) -> http://forum.xda-developers.com/canvas-turbo/development/rom-cyanogenmod-11-canvas-turbo-t2780905
If CM for any MT6589 device is missing here , PM me. I will add here.
i try but always stuck on boot splash, no boot up.. pleash help thanks
Uhm.... I guess I can't port cm10.2 over stock jb4.2.1 rom, right?
I ask because I first looked for cm10.1 to port, but to my surprise, I didn't find any cm10.1 builds for any mt6589 on google.
@polfrank you can port CM 10.2 using stock 4.2.1 rom. First you have to download any CM 10.2 Rom from above and follow guide to port. You can even port above CM 11 Roms if you have a working kernel source for your device
Sent from my iris458Q using XDA mobile app
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Hmm, I'm stuck on my brand's splash screen too. I don't get to see the boot animation, and as you mention I get errors during both unpacking and repacking. But it said that the file was copied though.... I 'll search for another way to upack and repack on Google and come back.
Edit: pfff, seems like the only way to do it on windows was the one you provided...
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
4shreyas said:
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I chose the CM10.2 from Wiko Stairway.
Yes, I'm now setting a Virtual Machine with Linux 14. And I'll try the unpack scripts from there. Let's see...
UPDATE:
OK, i ended up doing a clean install of ubuntu.
I upacked both images SUCCESS.
I repacked using stock kernel.img and CM ramdisk folder, SUCCESS.
I Install boot.img through CWMrecovery, it now gets past boot logo(Cubot white screen) but I think that before it would enter bootanimation the screen becomes a weird mass of colours, as if the screen was broken. It lasts for 1 second, then it restarts.
ps. I can successfully go to recovery with power+volUP If i like..
Any ideas?
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
4shreyas said:
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think I used wrong kernel.img. I repacked, will flash soon and come back to report.
EDIT: Are you sure that I have to use the META-INF folder from the CM rom? It gives me status 7 error.... (I also used the META-INF from a rom for my device, unfortunatelly it uses aroma, but it seems to install properly..)
EDIT2: I think that now I repacked the correct components of boot.img. It seems to get past the Cubot white splash screen, but after this, I get a black screen, but I can see that the screen is on, I can see the backlight. [I will try again with the CM META-INF-->still fails]
ps. Seems like I have to learn how to get a logcat if I wanna make use of your help... I'll be back in some hours.
----------------------------------------------------------------------
To sum up:
I have packed the new boot.img and replaced the needed files in the rom.
1) With the CM's META-INF folder I can't install, status 7 error.
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "stairway || getprop("ro.build.product") == "stairway"
E: Error in /sdcard/experiment/cm102last.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
2) With the stock rom's META-INF it seems to install propperly.
After reboot from recovery it goes to a black screen and stays there. I tried to logcat (adb logcat -v long > port.txt) but it just says:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb logcat -v long > port.txt
- waiting for device -
Click to expand...
Click to collapse
If i write adb devices it says :
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
0123456789ABCDEF offline
Click to expand...
Click to collapse
When I am on recovery I get:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
CWM-ZTE-V967S recovery
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------
CONCLUSION: I managed to install the new boot.img and rom but it stops on a black screen, right after it passes from the white logo screen. And now, I need your ideas...
ps. I repeated the porting process from the beginning to make sure that I didn't make any mistakes... again, the same result.
--------------------------------------------------------------------------------------------------------------
NEW UPDATE: IT BOOTED!! but how....? Here it is........
I just replaced the boot.img from the wiko stairway flashable zip with the boot.img I created with repacking my phone's kernel and CM's ramdisk.
SO, I just changed the boot.img !!!! Testing.......
-------------------------------------------------------------------------------------------------------------
Testing results: buggy mobile network and sound not working. I guess this is why all those files are needed to be copied. I think I ll start copying..... But I wonder...what did I do wrong earlier while copying,,,?
You will get status 7 error because it is a security feature which doesn't allow to flash one device's ROM to other. You have to edit using any text editor and remove first line in the update-script found in meta-inf/com/Google/android/
Also don't use other rom's meta-inf as they have different symbolic links which may not boot the device.
Your phone's modules will be different from wiko's. That's why you got buggy audio and network. Replace all the mentioned files.
sent from my iris458Q using XDA mobile app
Okay, after some hours of trial and error I copied all the porting files provided in the op, except 2:
-libjpeg.so - When I port this from stock, Cm boots, but cannot show images, every single image, including the bootanimation is black.
-libmedia.so - When I port this from stock, Cm stays in the bootanimation forever. (No bootloop, just bootanimation forever)
-------------------------------------------------------------------------------------------------------------------------------------
The "extra" bugs that I have are:
1. No sound from the speaker (but yes in the headphone).
2. Weak signal. I don't know if this is normal. It has 1 bar and sometimes it has 0 and says no service. Also, the name of the tile in the QuickSettings is 20201 (weird...). I also get a message when the rom boots and it says: "Restricted Access changed. Data service is blocked." This appears sometimes at random too.
3. USB storage doesn't work through Android.... ( I don't know if this is normal too). When I plug it on PC it just charges. (Note: I now see that other devices have this problem too. I found a partial workaround in the MMX Canvas HD cm10.2 section)
PS. Would logcat help in any of these problems?
--------------------------------------------------------------------------------------------------------------------------------
I moved on, and took some adb logcats.
1. I took the audio.txt as follows: started logcat, pressed play on the apollo widget, pressed pause, stopped logcat
2. I took the signal.txt as follows: started logcat (while on Airplane mode), disable Airplane mode (from quickSettings tiles), enable mobile data, disable mobile data, enable Airplane mode, stop logcat
I'll look at logs meanwhile I never had problem with signal, speaker audio and images. To get USB storage working add these lines to build.prop and reboot
persist.sys.usb.config=mass_storage,adb
persist.sys.usb.config=mtp,adb
For signal issue , did u replace your modem.IMG in CM ROM ?
For image issue try those 2 files from wiko ROM.
Edit:
Try to freshly port CM once again as given in guide with some changes in meta-inf and build.prop as I gave. If you still have problems then report here.
I couldn't debug audio log but in signal log > network is disconnected as data is enabled and even it's saying messaging settings are false. There may be issue with modem.img
sent from my iris458Q using XDA mobile app
Thanks for the USB storage tip. At least the internal SD can be seen now by the computer.
Images are OK now with the lib of CM.
For signal issue I copied modem.IMG from stock into the CM rom, and still having problems.
Btw, I just created a new thread for my device, I hope this is not a problem.
http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
Cheers !! I'll add your device in the ported list. As I said previously all necessary files should be replaced in CM to be bug free except major BT,camera,hwcomposer,FM,GPS,2nd Sim bugs.
Also USB storage is buggy now as SD card is unmounted in mass storage mode but not mounted on PC and when disconnected from PC it doesn't get mounted and you have to reboot to get it working on android. Also mtp mode sometimes doesn't work
sent from my iris458Q using XDA mobile app
Nice!
The only file missing is /lib/libmedia.so and I 'm starting to think that this may be the cause of the sound bug. But when I copy it from the stock rom, I get boot problems...
Anyway, thanks for your help, and sorry that I messed up/spammed your thread. I think the most important part of the job is done..! Good job!
EDIT: I think I sort of fixed the mobile network issue. I used a modem.img from another version of stock rom and it seems to work. However I still get the error "Restricted Access changed. Data service is blocked." But I have full signal and 3G! It's something!
Restricted access notification occurs if you enable or disable data and turn on/off airplane mode and phone and it is not a issue I think. It may be cyanogenMod's security message or something.
Also try libmedia.so from other
Stock rom which you said above.
sent from my iris458Q using XDA mobile app
thanks for repley
4shreyas said:
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Hello @limam27
@Iimam27 said:
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Click to expand...
Click to collapse
You can't patch binder.c from boot.IMG. You must be having kernel source for your device and you must patch binder.c in kernel. If you don't have kernel source then its almost impossible to get KitKat. See if your device clones have kernel source for their device. Else look for almost similar specs device with same processor. My device has mt6589m but no source from vendor. I used similar mt6589m device's source to build kernel. Now CM 11 is booting but no display due to different GPU config. So it's really hard if you don't have source. Try with CM 10.2 first .
EDIT- Previously I have told why you get status 7 error. So read whole thread before posting here. Good luck
Sent from my iris458Q using XDA Premium 4 mobile app
Infocus M810/T/U thread. (Also wth interesting things for m812 holders.)
Infocus m810 thread on facebook
Note:
All roms on this page are remade to use with Infocus m810 so don't flash on m812. MULTILANGUAGE
Bootloader unlock (m812/m812):
Custom recovery (m810/m812):
SUT flashable images (SUT Factory tool 3.0.8):
SUT 3.1.4 cracked.
Video tutorial SUT flashing on Android 6
ROMS M812(A/I) VN2/PHX:
Android 5.0.2 m812 OFFICAL sut. (Suitable for m810 too) to be used with SUT
cm13 for m812(a) http://forum.xda-developers.com/showpost.php?p=68355126&postcount=1110
ROMS M810(T/I/U):VNA
25/07/16 CM13 beta 2 (release) http://forum.xda-developers.com/showpost.php?p=67901403&postcount=1074
20/03/16 Android 6 custom ROM (ported from m812 ver 617A firmware)
23/02/16 Android 6 custom ROM (ported from m812 ver 6130 firmware)
27/12/15 Android 5.1.1 (internal version 511C(D updated)) (port from m812 ver 511C firmware)
Official Android Kitkat 4.4.2 (VNA-1640-0-00WW-A02)
Older roms
Older ROMs are designed for recovery installation and need some knowledge:
Before the installing of thiose ROMs you must be common with Adb/fastboot driver and installation. working fastboot.exe and adb.exe here
Im the author of this work. So feel free to ask and report.
All you install from here is on your responsibility.
m810.ROM Android 5.0.2: (October 2015) MULTILANGUAGE.
This ROM is full upgrade, so its able to install over Android 4.4.2 ROMS.
How tot install: Russian installation site
1. Put the zip file to sdcard.
2. Connect phone by USB cable. Press and hold volume down+power buttons
(10s), when phone restarts, release power button after vibrating and keep
holding volume down button until FASTBOOT message appear on screen.
3. Download boot recovery https://yadi.sk/d/v_LrtBVdk8pAj and place in fastboot/adb
folder
4. Run in cmd: fastboot boot tw101_recovery_repack_by_titovich.img
5. When recovery booted, Choose firmware UPDATE502_M810_v1.zip and
install.
In the end you should get this error: apply parsed perms lsetfilecon from
/cache to u_object_r:cache_file:s0 failed operation not supported on transport
endpoint set_metadta: some changes failed.
Ignore it. Its issue of recovery.
6 Besides, ROOT and Xposed for 5.0.X framework preinstall can be copied to
sdacard and installed same time after rom installed from boot recovery.
7. Hold power button 10 sec and reboot.
Enjoy.
5.0.2 DOWNLOAD
m810.ROM Android 5.1.1A 08/10/15 The beta version of Lollipop
5.1.1A
ROM from official 511A m812.
Same install instructions as above
Main changes
-Wifi reception better;
-GPS;
-Added buttons config, e-compass, g-sensor calibrations to display menu .
5.1.1 DOWNLOAD.
XPOSED for 5.1.1 . ROOT
Note Xposed from version 5.0 and 5.1 are different!
To flash via SUT:
ODEXED ROM Android 5.1.1B 11/15 The beta version of Lollipop
5.1.1B from official m812 511B update ROM. |For SUT installer. With
unbricking feature.
- ROM designed for odexed files so it contains resized partition for system
(by titovich). means one you install the partition table will remain - 2.5gb for
system. original system parttion is less 2gb. You will be able to install all
m810 roms but I noticed you.
-not for XPLOSED framework. The ROM is full odexed. So don't try Xposed it
will fail;
-minor changes from my side diff to previous ROM;
-fixes from Infocus to battery life.
bugs: haptics not working for hard buttons (to be fixed)
To be installed via SUT utility SUT 3.0.8: DOWNLOAD
-install SUT (drivers will be installed with SUT);
-download zip with nb0 image. Unzip.
-open nb0 image file in SUT.
-Check "Normal Download" and "Erase data".
-Download ignore warning messages.
-Flash will complete in less than 1 min.
5.1.1B for SUT DOWNLOAD LINK2
EOL
Tweaks and enchantments :
M810 service manual
http://forum.xda-developers.com/showpost.php?p=68520451&postcount=1123
Edit boot logo m81X
http://forum.xda-developers.com/showpost.php?p=68956713&postcount=1163
Other party hears the noise durine the phone call
build.prop file
persist.audio.fluence.voicecall=false
Secret codes:
*#*#4636#*#*, *#*#653837#*#*, *#*#76278#*#* Settings.
Note, never tap "USA Band", otherwise you will need to reflash modem part or firmware to make phone back to work.
*#*#873#*#* Upload service
*#*#225#*#* Calendar
*#*#2324636#*#* , *#*#232#*#*, *#*#23273#*#* ,*#*#233#*#*, *#*#231#*#*, *#*#2324678#*#* CDA
*#*#278#*#* CPUDaemon
*#*#324#*#* DebugCfg
*#*#368#*#* Device manager
*#*#3721#*#*, *#*#6721#*#*, *#*#372#*#*, *#*#672#*#*, *#*#4867#*#* High Temperature Monitor
*#*#744#*#*, *#*#628#*#* Mobile Assistant
*#*#787#*#* PackageUsageTool
*#*#227#*#* Pandora Box
*#*#272#*#* Permission Control
*#*#33546#*#* Permission Detection
*#*#793#*#*, *#*#795795#*#* Power Detective
*#*#795#*#* power Monitor
*#*#277#*#*, *#*#3277#*#* Stability Monitor
*#*#28274663#*#* TeleService
Themes pack for 511B/C:
http://forum.xda-developers.com/showpost.php?p=64725810&postcount=429
Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Noise fix. When party on other side is claiming on noise above your voice.
This is typical issue of dual mic QUALCOMM devices on 5+ Androids. Edit built.prop
persist.audio.fluence.voicecall=true change to false
Enable DIAG port for QXDM (QPST). Rooted.
adb shell
su
setprop persist.sys.usb.config diag,serial,mass_storage,adb
Increase speaker volume
http://forum.xda-developers.com/showpost.php?p=64566136&postcount=330
Sound volume mod working on m810
https://www.youtube.com/watch?feature=player_embedded&v=DOo7sT_JIs8
IMEI, Serial number, MEID, MAC, BT changer. Service tool (m810/m812) DANGEROUS!!!
https://drive.google.com/open?id=0B3Wy4Ok3qGszcmZlMDFCbGdwUjQ
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
will Infocus m810 get android 5.1???
there is an ota update for m812 to android 5.1 but i am unable to find the file.
My phone its on the way.Im interesting this thread
sknipas said:
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
Click to expand...
Click to collapse
Yes, its Multilanguage.
2g-3g-4g work
sknipas said:
there is an ota update for m812 to android 5.1 but i am unable to find the file.
Click to expand...
Click to collapse
If you find it, pls share, it can be used for further development.
@ heineken78
Thanks for coming here at XDA
I am daily following your good works at 4PDA and I am actually with Titovich's 5.02 rooted and i feel more than satisfied.
I take the opportunity to send you my grateful Thanks.
I will install the new update and let comment as well. I hope and wish the system repartitioning will not give any issue ( I don't like playing with root partition!!).
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
good work bro. looking for rom based on 5.1 . following this thread
lolo9393 said:
@ heineken78
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
Click to expand...
Click to collapse
Stock reserved place in m810 for system partition is ~1,6 gb. Making firmware less, won't bring any changes, unless repartitioning it to lets say 1,1 gb. This operation needs lot of system knowledge from people who will install it.. And profit of changes will be only 500 mb? is nothing.
m812 has partition of 3 gb, that's huge, but suitable for oxdexed roms.
repartition means- you need to change start sectors of emmc in order to set sizes of system, cache. Everything before those partitions remain the same.
Ok, tweak as promised
http://forum.xda-developers.com/showpost.php?p=63576292&postcount=2
Wow,wonderful news... i will test it,downloading...
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
@ heineken78
I've just finished the new Rom install. I followed instructions and had no issue . Rebooted via recovery and installed my stuffs.
-Wifi reception is the same as before and always weaker than my other phones. (minus 8 db)
-GPS IS NOT GETTING ANY FIX. 25 SAT in view and no one fixed.
-New Rom is a HUGE bit of improvement and feel more pleasant and very fast.
-DISPLAY is vibrant and very well set. Automatic mode is perfect also at night reading. good
- Battery leak in stand by is impressively low. less 1% full night. very good
THANKS TO THE TEAM BUILDING FOR THIS REALIZATION.
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
[email protected] said:
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
Click to expand...
Click to collapse
Indonesian/Deutch/ENGLISH/Espanol/Filipino/FRENCH/Portugues/VIET/Russian/chinese/ and 2 symbolic i can't know ....sorry may be Hebreu,
lolo9393 said:
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
Click to expand...
Click to collapse
Yes Im trying that.
But for now, "adb reboot ftm" to reboot in ftm mode and enable qualcomm diag driver.
Then change nv's as written here and here. Uz mztool to calculate right entry's.
@heineken78
Thanks dude!
Its an official or unofficial translated ROM?
Im just ask the reason of hope, maybe put into some more languages too.
Im get this phone yesterday, it looks really great, but enter the recovery and fastboot mode its terrible.
Do you know TWRP or CWM recovery for this phone?
ilhi, i tried to disable backlight with .rar file you attached and it does work but i
heineken78 said:
TWEAKS:
1. Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Click to expand...
Click to collapse
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
a1dahiya said:
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
Click to expand...
Click to collapse
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
what should i do please help me
heineken78 said:
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
Click to expand...
Click to collapse
What should I do, please help me out
---------- Post added at 08:46 AM ---------- Previous post was at 08:38 AM ----------
a1dahiya said:
What should I do, please help me out
Click to expand...
Click to collapse
What drivers to change or any other change of value .....?
I'm on stock lollipop 5.0.2 rooted
I also tried to replace the patched file with original which I copied before replacing but nothing helped
ALL IN ONE PORTING GUIDE
by @kuberrocks96
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
INDEX:
GUIDE FOR MTK
MTK BUG FIXING
RECOVERY PORTING
QUALCOMM BUG FIXING
Update:-
Code:
*Updated Bug Fix Guide for MTK
*Added SNAPDRAGON Bug fix guide.
*Guide to port TWRP also updated.
*Improved the thread.
*Added more fixes.
*Qualcomm porting guide added.
This is for all those users who want to port roms and use them in their devices.
But , before porting any rom,here are some of the main things you should keep in mind.
1)Base Rom :-
What is a Base Rom?
Code:
Base Rom is reffered to the Stock rom or the Default Rom of your device or sometimes the rom from which you will take base files(libs,apns,modem etc).
2)Port Rom
What is a Port Rom?
Code:
Port Rom is the rom which you will port for your device.
like if you are working a rom of another device having similar specifications and porting it for your device then it is called PORT ROM.
3)Kernel
What is a Kernel?
Code:
The kernel is a computer program that is the core of a computer's operating system, with complete control over everything in the system.
the central or most important part of something
In easy words kernel acts as the middle man between the Software and the Hardware
When porting a rom , you should check the Kernel version of the Port Rom and the Base Rom
They both should be similar,
like you can port from :
3.18.xx to 3.18.xx only
3.10.xx to 3.10.xx only
BUGS IN THE BASE ROM OR IN THE PORT ROM.
Yes , our Base Rom and the Port roms may contain bugs,
Those bugs will exist in our final Ported Rom also so , fixing those is not possible - Its always recommended to use a Stable or near to Stable Roms but hi, Custom Roms are made for pleasure only and these roms can't take place of stock roms.
Many users don't like Stock Rom (i.e Default Rom) so , they look for a Custom Rom.
Now let's talk about the main topic for which YOU ARE HERE!
PORTING A ROM!
In this Guide, i will tell one of the most easy way to BOOT UP THE ROM.
So, lets begin,
This guide will focus on MT6735/MT6753 porting.
Device i used is Coolpad Note 3 Lite
CPU:MT6735
But, it will work mostly on all MT675X SoCs , this can also be useful for MT67XX series but , My main focus is on MT675X
Without any delay let's talk about how you should port a ROM and what should be your focus at
YOU SHOULD FOCUS ON BOOTING THE ROM INSTEAD OF BUG FIXING AND DOING OTHER THINGS.
WHEN YOU PORT A ROM CHANGE FILES WISELY
DONT JUST COPY PASTE
PORTING A ROM CAN GET TOUGH ACCORDING TO THE ROM, LIKE PORTING AN AOSP BUILD CAN BE EASY BUT PORTING A MIUI BUILD IS CONSIDERED ONE OF THE MOST TOUGHED AND IRRITATING THING.
RESPECT THE EFFORTS BY THE PREVIOUS DEV.
CREDITS, WHEN YOU PORT A ROM THAT ROM WAS MADE BY SOMEONE , PORTED BY SOMEONE or BUG FIXED BY SOMEONE - SO BY ANY MEANS IF YOU KNOW THE SOURCE AND THE DEV OR TEAM WHOSE BUILD YOU ARE PORTING PLEASE GIVE CREDIT.
THANKS.
NOW , FINALLY. LET'S TALK ABOUT THE PORTING GUIDE WHICH YOU ALL ARE WAITING FOR.
What you guys need:-
Code:
1)Base Rom
2)Port Rom
3)Any good Notepad
4)Any Boot.img repack or unpack tool
5)Brain
Now , if you have all the above mentioned things , Lets proceed.
BOOT.IMG :-
BOOT.IMG contains all the magic , it has the KERNEL inside which is one of the main thing.
Porting from Same CPU & GPU:-
NOTE:- When you are porting from a Similar device having same chipset like porting from:-
MT6753 TO MT6753
MT6735 TO MT6735
Use this method (95% times working ):-
System/lib & lib64 :-
Code:
libaudiocomponentengine.so
libaudiocustparam.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libcustom_nvram.so
System/etc :-
Code:
/Firmware folder
/apnconfig
/spnconfig
/agps_profile_conf2
/media_codecs.xml
BLACK SCREEN AFTER LOGO???
REPLACE THIS LIB:- libcam.paramsmgr
To Fix Camera ( sometimes bootloop so try one by one ) :-
from System/lib & lib64 replace all libs starting like this:-
Code:
libcamera.mt6735 (mt6735 is according to my CPU )
libcameracustom.lib etc
libcamalgo.lib
Unpack Boot.img of both Base & Port Rom
Code:
replace kernel
and init.mt6735.rc ( not recommended always)
and Fstab.mt6735
System/Lib(/64)/HW*
Done , Now zip em and flash.
90% Rom will boot with BUGS! ( NO ROM IS THERE WITHOUT BUGS, LOL)
==>READ BUG FIX METHOD ALSO{Later in this Guide}<==
For Cross Porting Like:-
MT6752 etc to MT6753/MT6735
DO REMEMBER TO CHANGE :-
Code:
System/xbin/mnld
System/mddb
System/etc/firmware
System/etc/Apnconf
System/etc/spnconf
In lib(/64)/HW :- add files accordingly to your CPU or rename them.
BLACK SCREEN AFTER LOGO :-
Code:
libcam.paramsmgr
BOOT.IMG PORTING:-
UNPACK both Base Rom and Port Rom Boot.img
In PORT ROM BOOT.IMG:-
Code:
replace the boot.img-kernel
and in ramdisk folder add these files from Base Boot.img to Port Boot.img
Code:
fstab.mt6735
init.mt6735.rc
init.mt6735.usb.rc
Note:- Name may differ a little according to your CPU
REPACK THE BOOT IMAGE
NOTE:- If u get WIFI AND BLUETOOTH NOT SWITCHING ON OR BATTERY PERCENTAGE THEN REPLACE
Code:
init.project.rc
Done , You have succesfully ported Boot.img
Now , Lets focus on BUG FIXING
Bug Fixing isnt easy as it seems.
Replacing any wrong file or not supported file can easily give you bootloops.
It depends from ROM to ROM.
BUG FIXING[MTK]
Let's Begin.
If any lib missing in Base leave that - DONT WORRY
NOTE:- CHANGE LIB FILES FROM BOTH lib & lib64 folders
If you face "This rom is for Coolpad Note 3 Lite and your device is "K4Note"
To remove this delete the assertlines in Updater-script
ALWAYS CHANGE DPI IN BUILD.PROP ACCORDING TO YOUR STOCK ROM
Bootloop when porting
Code:
*libandroid_runtime.so
*libandroid_servers.so
*libmedia_jni.so
*Repack boot.image (properly)
RadioFM
Code:
\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(/64)\libfmcust.so
/system/lib(/64)/libfmjni.so
Sensors
Code:
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so ( acc. To device)
/system/etc/firmware (folder)
/system/bin/servicemanager
/system/bin/sensorservice
System/bin/msensord
system/etc/permissions/:-
android.hardware.sensor.xxxxx.xml
FIX Offline charging:-
Code:
In Boot.img -> sbin/healthd
System/Lib(/64):-
Showlogo
System/bin:-
Kpoc_charger
Bluetooth\Wifi not turning On\Off(old)
Code:
\system\lib\module\mtk_stp_wmt
Wifi
Code:
/system/etc/wifi (folder)
/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/lib(/64)/libhardwarelegacy.so
Hotspot:-
Code:
/system/bin/netd
*follow Wifi fix also*
Camera
Code:
firstly try one by one:
\system\lib(/64)\libcameracustom.so
\system\lib(/64)\libcameraservice.so
System/lib(/64)/camalgo
/system/etc/media_profiles.xml
/system/lib(/64)/libcamera.so
/system/lib(/64)/liboemcamera.so
\system\lib(/64)\hw\camera.default.so
\system\lib(/64)\libcamera_client.so
\system\lib(/64)\libcamer aprofile.so
\system\lib(/64)\libmhal.so
\system\lib(/64)\libmhalcontent.s o
\system\lib(/64)\libmhaldrv.so
\system\lib(/64)\libmhalmdp.so
\system\lib(/64)\libmhalpipe.so
\system\lib(/64)\libmhalscenario.so
\system\lib(/64)\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
Other cam files if any
*try one by one*
CamCoder/HwDecoder
Code:
\system\lib\libOmx*.so
system/etc/media_codecs
[SIZE="3"][B]Green/pink Camera / video lagging[/B][/SIZE]
system/lib(/64)/libdpframework.so
SD card/Memory
Code:
mt67**.fstab in boot.img
/system/bin/vold
/System/bin/pq
System/bin/sdcard
WhatsApp Media Fix:-
Code:
from System/bin/ replace these files:-
Media
mediaserver
netd
service
servicemanager
surfaceflinger
GPS
Code:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen(Haptic)
Code:
/system/usr
/system/usr\keylayout\Generic.kl ->fix HomeKey
NFC ( experimental)
Code:
System/etc/: Nfc files
System/etc/permissions/ nfc files
System/lib/libnfc****** ( all starting from nfc )
Sim1/2 (RIL)
((Trustbin.bin flash it accordingly to LP or MM etc of stock rom))
Code:
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
Try these aswell if ( you may suffer Bootloop )
/System/bin/mtkrild
/System/bin/mtkrildm1
/system/bin/stmd
EXPERIMENTAL FIX for ril:-
Code:
System/ Lib(/64)/ :-
Nvram
Nvram_sec
Nvram_platform
Nvrammagentclient
System/bin:-
Gsm***
System/etc/trustzone
Lib(/64):-
Libril
Libc2k***
Librilmtk
Audio/Sound:-
Code:
\system\lib\libaudio* .so
system/lib(/64)/libaudiocustomparam
system/lib(/64)/libaudiopolicymanager
system/lib(/64)/libaudiopolicyservice
system/etc/audio_effects
system/etc/audio_policy
System/lib(/64)/soundfx
Sometimes if Sound isn't working fully :::::
Code:
System/lib(/64)/hw/audioxxxxxxxxx (audio files)
Bluetooth:-
Code:
system/etc/bluetooth
System/etc/permissions/android.hardware.bluetooth.xml
/system/bin/uim*
/system/bin/bluetooth*
/system/lib(/64)/libbluetooth_mtk.so
/system/lib(/64)/libbluetoothem_mtk.so
Ads
Code:
/system/etc/hosts ->replace with new files or use tweak.
=====>>ADVANCE BUG FIXING:-
Volte Fixing
( Will only work if your Base Rom , Port Rom and Kernel supports VOLTE )
Code:
Boot.img:-
Zimage ( kernel - volte supported )
init.volte.rc
==THIS SHOULD NORMALLY FIX but if it doesn't try :- ==
Code:
System Folder:-
bin/volte_stack
bin/volte_imcb
bin/volte_ua
lib(/64)/volte_imsm
build.prop(Not always required):-
ro.mtk_volte_support=1
persist.mtk.volte.enable=1
FingerPrint:-
[Try one by one][If any file missing leave it]
Usual way to fix :-
Code:
System/etc/permissions/android.hardware.fingerprint.xml
System/lib(/64)/libgatekeeper.so
System/lib(/64)/hw/gatekeeper.mt6735.so
System/(/64)/libmcgatekeeper.so
System/lib(/64)/hw/fingerprint.default.so ( can break FP in some devices)
Advanced ( if usual doesn't work ):-
Code:
System/bin/:-
fingerprintd
Gx_fpd
tee_deamon
Lib64/lib:- ( if any missing leave that)
Fpclient
Fpalgorithm
Fphal
FPservice
IF ROM DOESNT BOOT TAKE LOG ( From ADB)
adb shell logcat > log.txt
and check what is causing issue
REFERENCE LINKS :-
Carliv Image Kitchen :-
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
Cross Port and Porting Guides:-
https://forum.xda-developers.com/k3-note/development/guide-porting-64bit-mtk-roms-cross-t3310605
Unpack and Repack without PC guide:-
https://youtu.be/qTe9XofT5VE
Meta-INF Info:-
http://www.mtkroms.com/2015/06/make-stock-rom-mtk-easy.html?m=1
Meta-Inf generator:- ( Not tested try but its worth a look)
https://forum.xda-developers.com/showthread.php?t=1221003
Sample Recovery flashable zip:-
https://forum.xda-developers.com/android/development/sample-custom-recovery-zip-t3552916
Assert Failed ?check this:-
http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
BUG FIXING FOR SNAPDRAGON
Compare the PORT FILES FROM BASE FILES:
Code:
uneventd.qcom.rc ( will fix sensor )
uneventd.rc
Copy and replace the following files from Base (ROM-PORTING/BASE) to Port (ROM-PORTING/PORT) to solve the given issues:
No sound bug:
Code:
system/lib/hw/
audio.primary.msm****.so
audio.primary.default.so
system/lib64/hw/
audio.primary.msm****.so
audio.primary.default.so
Sound working in speaker but not working through headphones or vice-versa:
Code:
system/etc/
mixer_paths.xml (you can also try patching it with the base)
[B]Distorted Outgoing Sound during Phone call or [/B]Partial Sound:
system/etc/acdbdata/MTP/
MTP_***.acdb (all files)
Home or any other button not working:
Code:
system/usr/keylayout/
goodix.kl
gpio-keys.kl (important)
Generik.kl
Video hw encoding/decoding not working:
Code:
system/etc/firmware/
venus.*** (all files starting with ‘venus’)
Sensors not working:
Code:
system/lib/hw/sensors.msm****.so (or sensors.lsm6db0.so)
system/lib64/hw/sensors.msm****.so (or sensors.lsm6db0.so)
system/lib/libsensorservice.so
system/lib64/libsensorservice.so
Led notification not working:
Code:
system/lib/hw/lights.msm****.so
system/lib64/hw/lights.msm****.so
Vibration not working:
Code:
system/lib/libhardware_legacy.so
system/lib64/libhardware_legacy.so
FM not working:
Code:
system/lib/qcomfm_jni.so
system/lib64/qcomfm_jni.so
Wifi not working:
Code:
system/lib/modules/wlan.ko
[Note: In MIUI, wlan.ko is renamed as pronto_wlan.ko and is also kept in system/lib/modules/pronto/ folder, so you have to replace in both the places.]
In some phones you may not find wlan.ko file. In that case you may try replacing these files
Code:
system/lib/libwcnss_qmi.so
system/lib64/libwcnss_qmi.so
For slow WiFi network and other WiFi related issues replace these files:
Code:
system/etc/wifi/ -- all files
system/etc/firmware/wlan/ -- all files
Camera and flash not working:
Code:
system/vendor/lib/ :-
libactuator_***.so (all files starting with ‘libactuator’)
libchromatix_***.so (all files starting with ‘libchromatix’)
libmmcamera_***.so (all files starting with ‘libmmcamera’)
system/lib/:-
libmm-qcamera.so
libmmcamera_interface.co
system/lib/hw/
camera.msm****.so
[Note: If such files are also available in your BASE/system/vendor/lib64/ then you have to copy those files also to their respective place in PORT]
GUIDE TO PORT RECOVERY
PORT TWRP RECOVERY
Things You are Required ::-
Code:
1.Android Image Kitchen
2.Notepad++
3.Base Recovery
4.TWRP to Port
5.Brain
First of All , You Guys need to unpack Recovery.img i.e both Stock Recovery or TWRP Recovery.
After this :-
You need to Copy these files from your Stock Recovery to the TWRP Recovery ( which you want to port ) :-
Lets Divide Step by Step ::--
*REPLACE FROM STOCK TO PORT*
STEP1:
Inside Ramdisk Folder ::::::
Code:
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
STEP2:
Now replace your Kernel usually named as zimage-kernel
STEP3
Inside Ramdisk Folder(boot.img):::::::
Code:
1.fstab
2.ueventd.rc
3.ueventd.goldfish.rc.
STEP4
INSIDE RAMDISK/ETC
Code:
recovery.fstab
STEP5
Open Default.prop
and Compare it with stock Default.prop or your Build.prop ( add values from build.prop )
=============>>>>>>>
DONE!!!!! EVERYTHING IS IN PLACE
NOW REPACK IT AND FLASH.
YOU HAVE PORTED A RECOVERY....
WARNING: Do not replace any file unnecessarily, because it may give rise to new bugs in place of solving it. Always be specific!
Now Mostly its the end of the Guide / Tutorial / G.K on porting or whatever you call it.
Once again , i (Kuber Sharma) hope you guys succesfully learn porting and making roms soon.
You guys have my Best Wishes.
Thank You.
I couldn't have done this without the help of :-
Amit Kumar (A.M.T)
Sam Grande (A.M.T)
Special Thanks to @sandeep.sethi
Special Thanks to @Yousef Algadri
Special thanks to @mohancm
You can find me here:-
@kubersharma
Want to buy me a coffee or wanna donate me for my cause!!
https://paypal.me/kubersharma
DO HIT THANKS BUTTON IF YOU LIKE MY GUIDE
THANK YOU
not lib64 files?
http://cloud.tapatalk.com/s/58a1efb476118/IMG_20170213_183928.jpg
Odesláno z mého VFD 700 pomocí Tapatalk
Great work, Really appreciated!
Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
Adreno306™ said:
not lib64 files?
http://cloud.tapatalk.com/s/58a1efb476118/IMG_20170213_183928.jpg
Odesláno z mého VFD 700 pomocí Tapatalk
Click to expand...
Click to collapse
I think op have missed while typing, both lib and lib64 should be considered.
Reserved...
Thank you
mohancm said:
Great work, Really appreciated!
Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
I think op have missed while typing, both lib and lib64 should be considered.
Click to expand...
Click to collapse
Couldn't have done without your support.
Thanks
Awesome work
Great job man.. Awesome and best guide for 64 bit devices.. Great thing... Expecting more guides.. ?
Is there a method for fixing the NFC to?o
Adreno306™ said:
Is there a method for fixing the NFC to?o
Click to expand...
Click to collapse
Follow sensor fix and replace libnfcxxxx in lib folder
kuberrocks96 said:
Follow sensor fix and replace libnfcxxxx in lib folder
Click to expand...
Click to collapse
nfc service has stopped working
Odesláno z mého VFD 700 pomocí Tapatalk
Adreno306™ said:
nfc service has stopped working
Odesláno z mého VFD 700 pomocí Tapatalk
Click to expand...
Click to collapse
Take a log
trying to port for teclast t98 4g mt8752
I've trying to port following a lot of guide ever bootloop only one time boot but no touchscreen
what i'm wondering my stock rom is kitkat so with a 32bit kernel ,i think, can i mix it with 64bit rom?
in my stock rom there isn't lib64 directory so what can I do to follow your guide?
thanx
Sorry to post it here as i thought probably you could help me but this method should also work for 32 bit roms .. Right?? I was porting a lollipop nexus look rom to my lenovo tab.It boots to the android is optimising screen and finishing bootbthen goes into a soft reboot. Can you help me with that? And please do confirm whether this method would work for 32 bit rom.
Hello!
I have a problem with the port I made for the Redmi Pro (MTK6797T). The ROM is booting and working quite well but the problem comes when i try to use my headphones.
The ROM recognises the headphones, when i plug them the headphones icon appears and the buttons are working to stop-play a song, however the sound comes out of the headphones and the speaker at the same time.
Any idea to solve this?
thanks A LOT for bugfixing guide portion... i was searching for that for a long time
@kuberrocks96
Camera gets crashed whenever I try to take HDR ......what is needed to fix this?
hi bro, Thanks for the guide, just like crossposting from a mt6753 to a mt6735? Or similar?
Now I would like to leave a solution for the nvram problem that has already happened to me several times
1.- edit the build.prop looking for gemini lines, in my case being a single sim would have to be disabled this function and any other line related to the sim ... if in your case you have 2 sim as you have to activate The gemini function and specify that it is dual sim looking for this line in the build.prop "persist.radio.multisim.config = ss" (for single sim) and change it to "= dsds" for dual sim
2.-In the libraries you have to change this
Libnvram.so
Libnvramagentclient.so
Libnvram_platform.so
Libnvram_sec.so
Libfeatureio.so
Libfeatureiodrv.so
Libhardware_legacy.so
Libcustom_nvram.so
3.- also have to change the firmware and mddb folders
And finally in the boot.img it is necessary to replace in ramdisk these files
Fstab.mt6735.rc
Init.mt6735.rc
Init.mt6735.usb.rc
And added a fourth file
Init.modem.rc
With that you should have running the imei and remove the nvram error in the configurations of the wifi
Greetings from Mexico and apologies for my English, but I'm using google translator
i couldnt fix modem problem even with firmware nor mddb nor modem file in boot image. w/o sim inside baseband imei works but w sim inside its showing no baseband no imei no service.
mt6752 to mt6752. base is c5 e5553 single sim port is k3 note dual sim.
wifi bluetooth sound works, didnt try camera fix
Please can you help solve the BLU R1HD camera MT6735 in Nougat from this ROM: https://forum.xda-developers.com/r1-hd/development/cm14-1-r1hd-t3518202
Yes , it will
YuZaGa said:
Sorry to post it here as i thought probably you could help me but this method should also work for 32 bit roms .. Right?? I was porting a lollipop nexus look rom to my lenovo tab.It boots to the android is optimising screen and finishing bootbthen goes into a soft reboot. Can you help me with that? And please do confirm whether this method would work for 32 bit rom.
Click to expand...
Click to collapse
Check wht files you replaced.
While booting the rom just don't replace all files.
Kernel ( and other boot.img part)
Firmware
Apn & spn
Amd sometimes mddb is enough
Hi , thanks
2909luboy said:
hi bro, Thanks for the guide, just like crossposting from a mt6753 to a mt6735? Or similar?
Now I would like to leave a solution for the nvram problem that has already happened to me several times
1.- edit the build.prop looking for gemini lines, in my case being a single sim would have to be disabled this function and any other line related to the sim ... if in your case you have 2 sim as you have to activate The gemini function and specify that it is dual sim looking for this line in the build.prop "persist.radio.multisim.config = ss" (for single sim) and change it to "= dsds" for dual sim
2.-In the libraries you have to change this
Libnvram.so
Libnvramagentclient.so
Libnvram_platform.so
Libnvram_sec.so
Libfeatureio.so
Libfeatureiodrv.so
Libhardware_legacy.so
Libcustom_nvram.so
3.- also have to change the firmware and mddb folders
And finally in the boot.img it is necessary to replace in ramdisk these files
Fstab.mt6735.rc
Init.mt6735.rc
Init.mt6735.usb.rc
And added a fourth file
Init.modem.rc
With that you should have running the imei and remove the nvram error in the configurations of the wifi
Greetings from Mexico and apologies for my English, but I'm using google translator
Click to expand...
Click to collapse
Yes , no worries we all are humans and language shouldn't be a bearer.
And yeah , thanks for your little guide.
Cheers