I have made a custom ROM, with additional API's and patches using stock ICS source - Downloaded from source.android.com.
After modifying, patching etc, I built the ROM using 'make' on my Ubuntu machine.
I followed the steps here to build the ROM: http://source.android.com/source/building.html
The output of this procedure is attached as a screenshot
(I copied the folder to windows hence the screenshot shows a windows OS)
Now I have a ROM I am asked to flash it using'fastboot flashall' per the instruction here:
http://source.android.com/source/building-devices.html
My device doesn't seem to support a Fastboot mode.
The output folder of the ROM is attached as a screenshot.
A> When I try to use CWM, it fails to flash - MD5 Mismatch:
Also I am unsure how CWM flashes and which of the folders are to be included. A CWM recovery generates:
1. boot.img
2. recovery.img
3. system.ext4.tar
4. data.ext4.tar
5. cache.ext4.tar
6. nandroid.md5
Clearly my output folder is not aligned to this format. So I'm a bit lost here.
B> Odin takes on tar file. I am not sure if simply making the folder a tar will work.
C> Heimdall doesnt support this tab I guess...
Any ideas on a solution would be appreciated.
Thanks & Regards
Indrajit
Downloaded & Installed a custom ROM zip, it worked. How can I make mine into a zip?
Most of the custom ROMs have a boot.img, system folder, data folder and meta-inf.
What is Meta-Inf?
Also If I zip my ROM (created as mentioned above) and try installing it doesnt since I dont have a Meta-Inf & I cant use the other meta-inf.
This is the ROM I installed: Worked fine except USB-PC connection didnt:
http://forum.xda-developers.com/showthread.php?t=1643736
Any ideas / suggestions would be highly useful & appreciated.
Thanks in advance.
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE
Most of us have always wanted to use custom roms but there just no custom roms for our devices so we just use different app launchers and uninstall some bloatware to make our stock rom feel good.
Rom porting makes it possible to use a custom rom on your mtk device provided in this tutorial they have the same chipset (example: mtk 6582 ported to mtk6582).
THINGS NEEDED :
1. B1 archiver / ES FILE EXPLORER
2. Root Browser.
4. A rooted device is also needed but not much important if you have CWM INSTALLED WITHOUT ROOT.
PROCEDURE :
1. Make a backup of your current rom, preferably CWM backup. You can either use MTK DROID TOOLS or ROM MANAGER...
The location of the backup will be at clockwork/backup/"date and time of the backup ". This is very important since we will need stuff from the back up and we will also use the backup to recover the phone should the ported rom give any problems.
2. At this point I presume you have already downloaded the apps needed and the custom rom you want to use which is in a zip format( this was not important but I had to bring it up cause I know zombies could be reading this.
3. Now extract the custom Rom with Root Browser. if you extracted with Root Browser then the location will be "speedsoftware/extracted/"folder with the name of the custom rom "".
4. Now open Root Browser and open the folders side by side "custom rom which will be ported at one side and other side will be used for searching for the location of the things needed for the custom rom.
5. Delete the following from the Custom rom:
Boot.img
logo.bin (You do this only when you like the Your current logo.bin)
system/vendor
system/usr
system/lib/hw
system/lib/modules
system/lib/libncurses.so
system/etc/firmware
system/etc/vold.fstab
system/etc/vold.fstab.nand
system/etc/bluetooth
6. Now that you have deleted them from the custom rom replace them. You will find the boot.img at clockworkmod/back/"folder with date and time"/boot.img. The rest of the files and folders will br located in the Root /system. Just copy and paste
7. Now at the custom Rom panel go back to where you find the "META-INF" folder,open /google/android will now long press on "updater script" and tap on open with then select text editor.
8. Check The mount & format point check something like this mmcblk0p. A number is always written after the "P" replace the number of your BASE to PORT.
9. Check multi select in B1 archiver Select ( do not archive the folder the files are in but the individual files in the folder containing the extracts)
10. Compress to ZIP file wait till the process finished. Now boot to recovery and flash your ROM
Good luck in porting Your Rom... I have used this method to port 5 roms including AROMA ROMS. and I have never ported a Rom with a pc before
MAYBE U NEED TO EXTRACT THE BOOT IMG TOO IF THIS DIDNT WORKED
DO IT AS FOLLOWS
Requirements:
-- BusyBox (cpio, gunzip and gzip is mandatory)
-- /System Write Permissions (Does not need to be a modified kernel)
-- Terminal Emulator
-- ES File Explorer (or similar)
-- Hex Editor (or use of DD)
-- Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish)
-- Open up your boot.img with the Hex Editor and look for: ANDROID!. Remove everything before it so that the ANDROID! header is the first to be read then save it over top of the boot.img. NOTE: This is only required if you are using a stock boot.img.
OR USE THIS IF U DIDNT UNDERSTOOD THIS
Hello Everyone, I’ll show you how to Unpack and Repack your Phone’s Boot.img & Tweak Karnel. Lets start.
Make a new folder named “boot edit” in cache/
image
Pull your boot.img in this folder
image
Now open ApkTool. Long press on “cache“, click on Get Access Permission.
image
Open cache folder and do same with boot edit. Give ApkTool access permission
image
Open boot edit, click on boot.img select Expack(MT65xx), press ok
image
It will unpack your boot.img.
image
Now open file manager & go to cache/boot edit/. You wil find your unpacked boot.
image
Now edit/modify the files or tweak karnel.
Again open ApkTool. Goto cache/boot edit click on ramdisk select repack-mt65xx.
image
It will repack your boot.
image
You will find an img file named new.img
image
This file is your Tweaked/edited/custom boot.img!!
Flash it via Recovery or Flashify & Enjoy..
FOR DETAILED AND STEP WISE GUIDE WITH SCREEN SHOTS SEE HERE
Mod Edit: link removed
XDA:DevDB Information
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE, ROM for all devices (see above for details)
Contributors
manhar2108, manhar2108, 2108kick
Source Code: Mod Edit: link removed
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: all
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-16
HIT THANKS IF I HELPED U
Good guide..
Especially for noobs....
Darshan601 said:
Good guide..
Especially for noobs....
Click to expand...
Click to collapse
i too am a noob so i tried and made this guide
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
manhar2108 said:
i too am a noob so i tried and made this guide
Click to expand...
Click to collapse
Yeah....Even I am a noob
gunzgunz said:
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
Click to expand...
Click to collapse
just replace all these files and use stock kernal to port them
good luck
Sir i tried your guide in porting rom. Mt6582 tp mt6582 chipset roms.. But after replacing those files you mentioned and when i flashed it to my phone, it was tuck in boot screen and keep on restarting. How am I going to fix this?
Thread closed. Pay per click links are not allowed on XDA.
Darth
Forum Moderator
Thread will be best viewed in website
Code:
[CENTER][COLOR="red"]Your warranty is now void.[/COLOR]
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 before asking help and reporting bugs.
Please read the entire OP instructions and FAQ,if any.
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.
A lot.[/CENTER]
This thread is for spreadtrum Marshmallow, lollipop and KitKat phones. I made this guide for porting especially CM/CM based ROMs. This thread is in under progress, I'll be keep adding and changing things. These lines will be removed when I think I'm done.
Requirements
A PC /Laptop /Even your android phone is enough for porting, since your not building ROM, provided that you know how to get things done
Android Image Kitchen
A ZIP archiver(winzip,7z,etc)
Notepad++/your favorite one
HEX Editor (for Android available on play store)
A working brain with basic understanding skills properly installed
An Android device with the chipset as per the title (of cource this will work on iPhone and Windows phones but sadly my kitten eaten flashing instructions , so blame my kitty:silly
A working custom recovery (if you don't have one, this thread might help you)
Aroma File Manager (this is used to skip the process of extracting system files from system.ext.win and system.new.dat and compressing it back)
Stock ROM (extracted to easily accessable folder, since we are going to port the ROM not using normal File Manager but a recovery based file manager
Custom ROM(S) (download links are in the 2nd post)
I'll suggest you to concentrate on booting the ROM rather fixing bugs at first shot, because if we are sure that the ROM boots we can go further, otherwise it's waste of time.
{
"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"
}
Marshmallow ROM porting guide
=> Download and Extract the ROM. Since ROM(S) is zipped out of custom recovery backup you'll see system.ext4.win (which is a compressed system folder) boot.emmc.win (boot.img) and some, maybe, compressed using system.new.dat.
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy boot.emmc.win to working directory of AIK and rename it to boot.img
=> Unpack boot.img
=> Replace the following
/ramdisk/lib/modules with /ramdisk.s/lib/modules
/ramdisk/lib/modules/mali.ko with /system/lib/modules/mali.ko from stockrom
=> delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.emmc.win and replace Custom ROM boot.emmc.win with ported boot.emmc.win.
Porting System
=> Boot to recovery and wipe system, data, cache and dalvik-cache and flash the CM13/Marshmallow ROM
=> Go back to tab menu of TWRP tap on 'Mount tab' Mount system and go back to flash tab and flash aroma file manager zip
=> Now you are on Aroma FM. Copy and replace the following files with stock ROM files:
/system/lib/hw/<all files> except files audio.primary.sc8830.so & bluetooth.default.so
/system/etc/ all audio related files except audio_effect.conf
/system/etc/codec_pga.xml
/system/etc/ media related files
/system/etc/tiny_hw.xml
/system/lib/egl/libGLES_mali.so
/system/lib/libEGL.so
/system/lib/libGLES_trace.so
/system/lib/libGLESv1_CM.so
/system/lib/libGLESv2.so
/system/lib/libMali.ko,if any
=> After replacing files exit Aroma FM and reboot the system. Booting will take a while (~10m) so please be patient.
Bug Fixing Guide
Camera Fix
Open lib files one by one on stock rom lollipop & search for "_ZN7android5Fence4waitEj"(without quotes) with notepad++ (mainly look into the files related to camera.sc8830.so, to know open it with HeX editor and see what are the necessary lib***.so files)
In my case "_ZN7android5Fence4waitEj" are available on stock libui.so where that file needed by camera.sc8830.so
SO open camera.sc8830.so with HexEditor and search for libui.so
Then rename libui.so of stock rom file to libcm.so and save it
Copy and paste modified file to the exact directory and wipe data, cache, dalvik-cache (data is nedded because if the camera HAL fails to load at first time CM ROMs won't show camera app in that case it is must to wipe data)
Then reboot & make sure camera.sc8830.so loaded correctly with logcat
Fix for possible bootloops when porting Marshmallow ROM using lollipop kernel
Soon.....
Note:-I'm sure the marshmallow ROM(s) will boot on lollipop device also (because I personally tested with my phone but I need confirmation that this works on marshmallow devices also.
Lollipop ROM porting guide
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy custom ROM boot.img to working directory of AIK
=> Unpack boot.img
=> Replace the following:
/ramdisk/lib/modules with /ramdisk.s/lib/modules
/ramdisk/lib/modules/mali.ko with /system/lib/modules/mali.ko from stockrom
delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.img and replace Custom ROM boot.img with ported boot.img.
Porting system
=> Boot to recovery and wipe system, data, cache and dalvik-cache and flash the CM12/lollipop ROM
=> Go back to tab menu of TWRP tap on 'Mount tab' Mount system and go back to flash tab and flash aroma file manager zip
=> Now you are on AromaFM. Copy and replace the following files with stock ROM files:
/system/lib/egl/libGLES_mali.so
/system/lib/hw/<all files> except files audio.primary.sc8830.so & bluetooth.default.so
/system/lib/modules<all files>
/system/vendor/lib/libbt-vendor.so with stockrom /system/lib/libbt-vendor.so.
=> After replacing files exit Aroma FM and reboot the system. Booting will take a while (~10m) so please be patient.
Typing Bug Fixing Guide
KitKat ROM porting guide
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy custom ROM boot.img to working directory of AIK
=> Unpack boot.img
=> Replace the following
/ramdisk/sbin files with /ramdisk.s/sbin files
/ramdisk/init.sc8830.usb.rc with /ramdisk.s/init.sc8830.usb.rc
/ramdisk/init.usb.rc with /ramdisk.s/init.usb.rc
=> Delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.img and replace Custom ROM boot.img with ported boot.img.
Porting system
=>Replace the following:
/system/lib/egl/<all files>
/system/lib/hw (following files) :
camera.sc8830.so
camera2.sc8830.so
gralloc.default.so
gralloc.sc8830.so
hwcomposer.sc8830.so
keystore.default.so
lights.sc8830.so
local_time.default.so
power.default.so
sensors.sc8830.so
sprd_gsp.sc8830.so
/system/lib/modules<all files>
/system/vendor/lib/libbt-vendor.so with stock ROM /system/lib/libbt-vendor.so
Booting will take a while (~10m) so please be patient)
NOTE: If you stuck at Splash Logo (Manufacturer's logo) then delete CM11/system/lib/egl/libGLES_mali.so from recovery and then wipe data, cache, dalvik-cache and reboot.
Bug Fixing Guide
Camera Fix
Copy files camera.sc8830.so, camera2.sc8830.so & libandroidfw.so from stock ROM
Rename libandroidfw.so to libandroidcm.so
=> Download and install Hex Editor (Users who are using Android for porting can use Hex editor from playstore)
Open camera.sc8830.so with Hex Editor and search for libandroidfw.so & rename it to libandroidcm.so
Save camera.sc8830.so file, copy and paste it to CM/CM based ROM
Do the same for camera2.sc8830.so
This will fix the error "Cannot load Camera HAL" which is caused by camera.sc8830.so mising start_SprdPrefTracking & stop_SprdPrefTracking argument which is available only on original libandroidfw.so on your stockrom.
Reboot your device
If you haven't seen camera app then you may need to wipe the data and dalvik-cache but there is an alternative for this. The alternative is using third party camera app from play store if the camera works then you are good to go
but to have CM stock camera you must need to wipe data
WiFi/Hotspot fix
Part - I
Make sure your stock ROM WiFi (WLAN) driver name is sprdwl.ko on /system/lib/modules
Copy the following folder(s) from stok rom & paste to cm-11.0 rom
--/system/etc/wifi/<all files>
/system/etc/dhcpcd/<all files>
--/system/etc/connectivity_calibration.ini (related to WiFi connectivity)
--/system/etc/connectivity_configure.ini (related to Bluetooth connectivity)
I suggest you to replace files from Aroma FM (since we don't need to set permissions, etc which will automatically done by Aroma FM)
If you are replacing files from root explorer you need to properly set the permissions and Ownership/Group of particular for otherwise there will be no point in replacing the files and this will result in either unfixed bug or bootloop for this properly note down the permissions and Ownership/Group of individual files
for ex: /system/etc/dhcpcd/dhcpcd-run-hooks has permissions "-r-xr-x--- or 0550" and Owner is "dhcp" and Group is "shell"
Part - II
Unpack cm-11.0/based ported boot.img and replace "init.wifi.rc" file with this init.wifi.rc
Flash the modified boot.img using Flashify/ from recovery using flash image option (recommended)
To test whether the WiFi driver properly loaded or not
use terminal emulator type
Code:
su
<enter>
cat /proc/modules
<enter>
see whether the sprdwl.ko present on loaded modules list.
Try to use WiFi and immediately see the logs (use logcat Extreme app from play store) set if there are any errors
Do the same with Hotspot
as a result you may need to replace some files under --/system/bin/
ex:
--/system/bin/dhcpcd
--/system/bin/hostopad
--/system/bin/wcnd
--/system/bin/wpa_cli
--/system/bin/wpa_supplicant
etc
To root flash Magisk (systemless-root only for lollipop and above) or SuperSU
Credits: Hadi Khoirudin, Advan S4p [Official] fb group, @@ki,
@Jitheshwar (it's me :silly: )
Created 2/10/2017
Last Updated 3/10/2017
Downloads:-
Marshmallow
CyanogenMd 13.1
Bug fix Update (extract zip and replace files and port boot.img and then zip it, boot to recovery wipe cache and dalvik-cache flash the zip and reboot)
=====================
Resurrection Remix 5.7.4
Offline Charging fix
PAC-MAN ROM
Lollipop ROMs
CyanogenMod 12.1
=====================
Resurrection Remix
WiFi-Hotspot-fix-for-CM/based-lollipop-ROMs
KitKat ROMs
PAC-MAN ROM
=====================
MIUI7-7.4.26
Video codec fix
WiFi-Hotspot-fix-for-CM/based-KitKat-ROMs
More links have been adding
Reserved
You could have given me the credits.......well nice thread.....just a updated version of my thread
@ki said:
You could have given me the credits.......well nice thread.....just a updated version of my thread
Click to expand...
Click to collapse
But I took nothing from your work. I made this thread keeping CM ROMs in mind. But I have given credits to you in recovery porting thread since I used some of your work. Anyway you have given me Idea. PM me with more suggestions.
Edit: credits updated.
Jitheshwar said:
But I took nothing from your work. I made this thread keeping CM ROMs in mind. But I have given credits to you in recovery porting thread since I used some of your work. Anyway you have given me Idea. PM me with more suggestions.
Edit: credits updated.
Click to expand...
Click to collapse
Sorry for being so rude.......well i will try to suggest if anything good comes to my mind
Will the camera fix work with evercrossmod rom
[email protected] said:
Will the camera fix work with evercrossmod rom
Click to expand...
Click to collapse
No. That fix is for CM/CM based roms only. For stock based ROMs you just need replace camera libs.
Jitheshwar said:
No. That fix is for CM/CM based roms only. For stock based ROMs you just need replace camera libs.
Click to expand...
Click to collapse
This did not worked...the camera icon is showing but it says app not installed.I replaced the previous hw files (camera.sc8830.so and the camera2.sc8830.so). Now the app is opening but can't connect to camera.
[email protected] said:
This did not worked...the camera icon is showing but it says app not installed.I replaced the previous hw files (camera.sc8830.so and the camera2.sc8830.so). Now the app is opening but can't connect to camera.
Click to expand...
Click to collapse
You have to replace files having name "libcamera****.so" too.
How to unpack and repack system.ext4.win ?
[email protected] said:
How to unpack and repack system.ext4.win ?
Click to expand...
Click to collapse
just rename the file to system.ext4.win.tar.gz
and open it like a norma zip file
[email protected] said:
How to unpack and repack system.ext4.win ?
Click to expand...
Click to collapse
rename extension with .tar and extract it as usual but while repacking make sure you're using .tar compression type only. But I recommend using Aroma FM since extracting and compressing system.ext4.win may result in incorrect file permissions, as it is compressed by recovery.
@ki said:
just rename the file to system.ext4.win.tar.gz
and open it like a norma zip file
Click to expand...
Click to collapse
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).
Jitheshwar said:
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).
Click to expand...
Click to collapse
Now which software extracts .tar file. Plz tell me a software for windows
Jitheshwar said:
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).
Click to expand...
Click to collapse
Yup....i forgot to mention that......just thought why anyone wants to backup without compression......
[email protected] said:
Now which software extracts .tar file. Plz tell me a software for windows
Click to expand...
Click to collapse
A zip archiver like 7zip, Winzip, etc. Mist if these software will be available for free. If you are using mobile to port I recommend ZArchiver.
After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?
RustyDiamond said:
After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?
Click to expand...
Click to collapse
your kernel....
RustyDiamond said:
After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?
Click to expand...
Click to collapse
You may not replaced necessary lib(s).
Wipe everything before flashing the ROM (it is suggested to wipe internal storage also).
Don't replace everything (like camera libs) because they might give issues that you are facing, first key the device boot then fix bugs. If possible take logs using adb.
Hey, today in this post I've discussed on the topic
"How to unpack/repack img without PC or android tools (android tool is a little complicated and sometimes doesn't works)."
So let's get started
First of all download & install 'android image studio'
1: open it and click on repack/unpack
2: select the port ROMs boot or recovery img.
3: we get two folders
a.) Split_img --->> contains kernal zimage.
b.) Ramdisk----> contains init.rc recovery. Fstab etc..
4: to delete any file long press on it and click delete
5: to import any file click on import button in right panel & select the file
6: after making desired changes. Repack the img using repack button
7: a file will be created with the name image-new.img
8: export this file using export button and select the desired location.
Congratulations you have just ported an img without PC easily.
Link for the tool: https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
Link to my video toitorial for better understanding on this:
If you liked it just PRESS the THANKS button
I need more help, trying to open a .IMG boot file for Samsung s5, it gives the "No Image Supplied" error
Screenshot
Using AIS. Trying to port custom recovery but first thing I've tried is to just unpack and repack stock recovery. When repacking output of AIS is new IMG and new ramdisk. New IMG is smaller than original but from what I've read this should be okay. Flashed new IMG and attempted reboot recovery and all I got was black screen. Flashed stock recovery and it booted recovery fine. Not sure what I'm doing wrong. I used AIS to open the new image it created and then kept doing file/folder comparisons on the output. I narrowed down the difference being recovery.img-ramdisk.cpio. But when I unpack with cpio the contents of the archive are the same. Additionally, I repacked the contents with cpio but it still comes up as not matching the original recovery.img-ramdisk.cpio. My device can and does make replacement recovery images using applypatch with bonus files and boot img. Any help greatly appreciated!