Hi all! And now... my program on XDA
This program is designed for porting MTK ROMs, for other MTK devices...
It contain several of example projects, that you can use, to make your project for your device... examle projects is designed only for single platform porting (MT6575 to MT6575, MT6577 to MT6577, e.t.c.), but you can create project to port ROM from MT6589 to MT6577 If you can find out what files are needed for this... it depends only on you...
System requirements:
OS: Windows Vista - Windows 7
Additional
PC: .NET framework 4.0 and above, JDK
Phone: root access, adb root
Short instruction to use:
1. Run program
2. Change lang, if you need
3. Choose project and edit it for your device
4. Get your files from zip ROM, ft ROM, folders or phone
5. Get files from ROM to port
6. Edit updater-script, build.prop, repack boot.img if you need
7. Build ROM and flash it
8. If don't work - goto step 2, or replace some files manualy
Screenshots:
{
"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"
}
Video guide:
Older versions and changelogs you can find here: http://forum.china-iphone.ru/viewtopic.php?f=31&t=24506
Latest version: http://d-h.st/04WM
Sources: http://yadi.sk/d/SLzFHpcfNgYfo
GitHub thread: https://github.com/back37/MTK-FirmwareAdapter-Tool
To get a quick answer to your question - send them via email...
P.S. Why it open source for now?:
1. Now i don't have any MTK device and waiting for release MT6595...
2. I want to add making flashtool images without device, but i don't know how to do it... (looks like with linux you can create ext4 image... image size pick up from scatter, perms from updater-scripd, or just RW-R--R--)
Bro I have tried to use this tool but can't port anything coz of some errors . will try again with the help of video tutorial.
BTW glad to see ur thread on English forum (XDA).
Thanks
Sent from my MIUI using Tapatalk
kuldeepraj said:
Bro I have tried to use this tool but can't port anything coz of some errors . will try again with the help of video tutorial.
BTW glad to see ur thread on English forum (XDA).
Thanks
Sent from my MIUI using Tapatalk
Click to expand...
Click to collapse
Maybe it was because you used the old version... many of bugs was fixed in latest version, while i tried to make guide... Or you needed in some others files to run ported ROM...
The easiest way to check why you take this errors is try to make ported ROM manualy, by using any instruction and files from some project...
This program usefull only if you knows, that needed for you device to run ported ROM and completely useless if no...
Hi, can i use a nandroid backup?
Only if your backup is system ext3/4 image + boot.img...
i want to port a rom from one mt6592, to my t100s, how i can make a project? there is no any project to this mt6592.
NightShade said:
i want to port a rom from one mt6592, to my t100s, how i can make a project? there is no any project to this mt6592.
Click to expand...
Click to collapse
Choose any project and edit, how it needed for you... Name of project it's only name... Doesn't matter what project is selected, it's only file lists!
back37 said:
Maybe it was because you used the old version... many of bugs was fixed in latest version, while i tried to make guide... Or you needed in some others files to run ported ROM...
The easiest way to check why you take this errors is try to make ported ROM manualy, by using any instruction and files from some project...
This program usefull only if you knows, that needed for you device to run ported ROM and completely useless if no...
Click to expand...
Click to collapse
Will this tool run on win xp?
And after i get the base rom and port rom it still shows error ,saying base rom not found.
xXx~~~SHLOK~~~xXx said:
Will this tool run on win xp?
Click to expand...
Click to collapse
Don't know... some operations, like unpacking/packing boot.img may not work...
xXx~~~SHLOK~~~xXx said:
And after i get the base rom and port rom it still shows error ,saying base rom not found.
Click to expand...
Click to collapse
If your zip/image is correct, after getting files, they must be placed on: %ProgramDir%/WorkDIR/%CurrentlyChoosedProject%/YourFiles
And programm checking exist of folder system inside this dir...
P.S. If you use system.img from MTK droid root&tools, then it must havw name system.img, not system.ext4.img(rename it)...
Update
New version was released... it have some bugfixes with getting files from system.img and from folders...
back37 said:
New version was released... it have some bugfixes with getting files from system.img and from folders...
Click to expand...
Click to collapse
I am using Windows xp and it cant unpack and repack boot. So what changes i have to make to the boot if I do it manually
Nice thread...thanks
Sent from my Micromax A68 using XDA Free mobile app
xXx~~~SHLOK~~~xXx said:
I am using Windows xp and it cant unpack and repack boot. So what changes i have to make to the boot if I do it manually
Click to expand...
Click to collapse
You have two ways:
1. You can replace kernel by your in ported boot
2. You can replace bootclasspath in your ramdisk (rmdisk/init.rc)
Also you can try to modify scripts to working with WinXP or working with any Win ver. (write detection of windows version and some string for some versions... or replace some strings by working on any windows version)... if you make it for any version, just give me a link and i will add edited scripts in next version (of cource if others functions works on WinXP)... needed to edit imgpack.cmd and imgunpack.cmd (%ProgramDir%/Bin)...
2.0.0.5
Program updated!
New:
- Sound notification
- Czech lang
- Message show time
Fixed:
- Text coding, now program using unicode, it must be compatible with most of languages
sorry just ask..
this tool can mix any ROM ??
i mean just take Baseband or anything from ROM MTK 6572_a to BaseBand ROM MTK 6572_b ?
like we know sometimes from same kind MTK not support with another
i hope you know what i mean..sorry my bad english
thanks
sayaranu said:
sorry just ask..
this tool can mix any ROM ??
i mean just take Baseband or anything from ROM MTK 6572_a to BaseBand ROM MTK 6572_b ?
like we know sometimes from same kind MTK not support with another
i hope you know what i mean..sorry my bad english
thanks
Click to expand...
Click to collapse
Yes, it can mix any ROM, but to do it, needed some configures... for example, to take only baseband needed to do something like this:
1. Clear project and add only system/etc/firmware
2. YourROM - choose ROM that contained needed for you baseband
3. ROMtoPORT - check META-INF, choose yourROM
4. uncheck auto boot.img repack, build ROM
this is only exemplary steps, because this program not intended for this functions...
Thanks!
Thanks bro... I've used this tool for a long time, it's so good.
Thanks for your hard work bro!
Please add the MT6592 project as I searched WHOLE INTERNET BUT DIDN"T FIND GUIDE OR ANYTHING relative to MT6592 It's android 4.4.2 please help and add the mt6592 also
help
hey bro make a guide on how to create a project & then port port using that project.... Il will be helpful for us.
back37 said:
Hi all! And now... my program on XDA
This program is designed for porting MTK ROMs, for other MTK devices...
It contain several of example projects, that you can use, to make your project for your device... examle projects is designed only for single platform porting (MT6575 to MT6575, MT6577 to MT6577, e.t.c.), but you can create project to port ROM from MT6589 to MT6577 If you can find out what files are needed for this... it depends only on you...
System requirements:
OS: Windows Vista - Windows 7
Additional
PC: .NET framework 2.0 and above, JDK
Phone: root access, adb root
Short instruction to use:
1. Run program
2. Change lang, if you need
3. Choose project and edit it for your device
4. Get your files from zip ROM, ft ROM, folders or phone
5. Get files from ROM to port
6. Edit updater-script, build.prop, repack boot.img if you need
7. Build ROM and flash it
8. If don't work - goto step 2, or replace some files manualy
Screenshots:
Video guide:
Older versions and changelogs you can find here: http://forum.china-iphone.ru/viewtopic.php?f=31&t=24506
Latest version: http://d-h.st/OpE
Sources: http://yadi.sk/d/SLzFHpcfNgYfo
To get a quick answer to your question - send them via email...
P.S. Why it open source for now?:
1. Now i don't have any MTK device and waiting for release MT6595...
2. I want to add making flashtool images without device, but i don't know how to do it... (looks like with linux you can create ext4 image... image size pick up from scatter, perms from updater-scripd, or just RW-R--R--)
Click to expand...
Click to collapse
udayrane175 said:
hey bro make a guide on how to create a project & then port port using that project.... Il will be helpful for us.
Click to expand...
Click to collapse
Hi! It's done long time ago... it's just a Project edit guide that you can choose at MTK FirmwareAdapter Tool on youtube...
Related
i have created a plugins for android kitchen with bgcngm's MTK-Tools
i have to give Kowtow to
{
"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"
}
master shifu dsixda & bgcngm for sharing their great tool or this plugins wouldn't have exists !
With these tools combinations, modding & ROM porting on MT6573 platform becomes a breeze !
Enjoy...
Added on Sept 04, 2012 - Updated scripts & added pof nbimg
Credits to pof, now you can unpack/ repack boot_logo too... you can follow his original post here
Added on Sept 16, 2012 - ROM porting for MT6573 via Android Kitchen
Been working on these tuts for awhile back then but never seems to be able to complete it until now...
How to use Android Kitchen's Basic features on MT6573
How to use Android Kitchen's Advanced options on MT6573
How to use Android Kitchen for ROM porting on MT6573
Other successfully ported ROMs
Extract latest MT6575/ MT6577 system.img too...
This plugins is develop on cygwin. i have also ported it for linux...
Have Fun...
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
--------------------------------------
Added on 5th November 2012 - dsixda Android Kitchen natively supports MT65xx SoC !
Great News, dsixda's Android Kitchen now natively supports MT65xx !
Credits to jerben & of course Master Shifu dsixda !
For more info, refer to this post onwards...
Please do report any of your findings regarding MT65xx here...
--------------------------------------
Added on Feb 25, 2012
Operation to Support & Reward our MTK SoC Developers
Head up to here & show your support...
edit solved
You rock bro!
Sent from my GT-I5801 using xda app-developers app
glad u find it useful, bro...
all those cli is driving me crazy so i started looking at dsixda's scripts at Android Kitchen... :laugh:
Working on V2, more automation such as it will automatically copy boot_logo to temp folder for extraction then after editing, it will automatically copy it back to /system/media/images. No need to copy & paste...
yuweng said:
glad u find it useful, bro...
all those cli is driving me crazy so i started looking at dsixda's scripts at Android Kitchen... :laugh:
Working on V2, more automation such as it will automatically copy boot_logo to temp folder for extraction then after editing, it will automatically copy it back to /system/media/images. No need to copy & paste...
Click to expand...
Click to collapse
Gr8 bro!
Very good work but it doesn't work for me... i have created the rom and push in sdcard, in cwmr (created with TUTO to port cwmr to any mt6573 ) when i try to flash, it return too the main page of cwmr... any ideas ?
Hi e-infor,
You have given me no lead at all as why it doesn't work on ur phone.... First you need to let me know the link to ur ROM & all info that you know about ur phone so we can start trouble-shooting it...
Just for sharing, a fellow xda member pm me & we started diagnosing the problem then later we found out that he is having a MT6575 with yaffs partition ! MT6575 should have an ext4 system.img...Later on, i recommend him another shifu to help him on his problem...
i don't have MT6575 & i don't know if my tuts will work on it but i'm very sure dsixda's Android Kitchen will work on MT6575 as well as the newer MT6577... :good:
hi man ....
i've try to insert the modification into dsixda kitchen files... could you have a look?
my modification is at the attachment of this post
Hi, after search this night i have solved my probleme with created a new backup of my original rom et use a other rom for porting, the flashing it's ok ^^ .
My new probleme : I try to port MIUI on this phone, but actually dont work :/
@jurben
yeoh man, good job man... :good: It does unpack MT6573 boot.img & i've manual repack it & it works... :laugh:
i dare not touch those Android Kitchen scripts as they are all too complex for me...
Now you need to include mkbootfs & mod related scripts then it will be a fully working Android Kitchen for MT6573... :good:
@e-infor
It is not possible to port Miui over, as there are many great ROM cooker out there, they would have done it long time ago...
However, many have successfully ported Lewa OS to their MT6573 & lately, it support MT6575 & later on MT6577 too... :good:
It is very similar to MIUI...
Hi finally i have port other rom(goophone rom look like ios... ) but miui do no work with me
Big thank for your Tuto, he work perfectly...
Ps: it's too later but sorry for my english...
Sent from my H7300 using xda app-developers app
yuweng said:
@jurben
yeoh man, good job man... :good: It does unpack MT6573 boot.img & i've manual repack it & it works... :laugh:
i dare not touch those Android Kitchen scripts as they are all too complex for me...
Now you need to include mkbootfs & mod related scripts then it will be a fully working Android Kitchen for MT6573... :good:
Click to expand...
Click to collapse
i haven't finalize the modification sir. That modification hasn't work, but i've made good progress.
in final i want the kitchen to identify the boot image and than the script insert the modification to the source of mkbootimg and the extractor script but than cleaning the modification at the end of the job.
i see there is a script in that kitchen that do things like that to these files to adjust kernel offset parameter.
@jurben
in fact i have try my hands on it too & what you said is correct; existing Android Kitchen packing script will insert base address & that make the packed boot.img unbootable on MT65xx....
All in all, there will be quite a numbers of other scripts that need modding too; one that does the manual unpacking & others but i'm sure you'll find a way to make it work... :fingers-crossed:
We'll wait for your good news... :good:
@e-infor
u r most welcome & i c that u r becoming a Master Shifu ur self...
Its good to share & only that way we'll make android a better OS & contribute back to the community... :good:
I've made my "patch" to change the dsixda kitchen into MT65xx dsixda kitchen sir.
This is my "patch" : http://db.tt/q4I0Zjkf
I hope you can have a look.
Nice work ! Now the kitchen is a very useful all in one tool for MT65xx.
i'm tring to setting the working folder
but at the end i obtain an error
"build.prop" not found
why?
yeoh friend, you have given me no clue at all as why it didn't work, at least you could have list the name of the ROM or may be a link to your ROM...
From my experience, it should be a corrupted system.img...
However, in the past, i did tried a link from fellow xda member that he post for his stock ROM from his local distributor, Android Kitchen unpack it with error. Only a few folders & files got extracted, at the end i tried flashing it with SP Flash Tool & to my surprise it boots up fine !
So what i did was, at ADB shell, su then mkyaffs2image /system /sdcard/system.img & got the backup system.img & with that Android Kitchen unpack it just fine, funny as it sound...
yuweng said:
yeoh friend, you have given me no clue at all as why it didn't work, at least you could have list the name of the ROM or may be a link to your ROM...
From my experience, it should be a corrupted system.img...
However, in the past, i did tried a link from fellow xda member that he post for his stock ROM from his local distributor, Android Kitchen unpack it with error. Only a few folders & files got extracted, at the end i tried flashing it with SP Flash Tool & to my surprise it boots up fine !
So what i did was, at ADB shell, su then mkyaffs2image /system /sdcard/system.img & got the backup system.img & with that Android Kitchen unpack it just fine, funny as it sound...
Click to expand...
Click to collapse
i try to extract the system.img in that mode
http://bm-smartphone-reviews.blogspot.it/2012/04/creating-rom-dump-of-your-mt65x3-device.html
but not work
and in that
http://forum.xda-developers.com/showthread.php?t=1683883
but not work
i also tried to rename the cwmr system.img but not work
iff i run the command mkyaffs2image adb shell give me "command not found"
both of the tuts you mention works, i think you must have miss a step or two...
in fact, mkyaffs2image is scatter everywhere here at xda but i'll just attach it here just for your convenience sack...:good:
Use Root Explorer & copy it to /system/bin & at ADB shell, su then chmod 755 /system/bin/mkyaffsimage
if the command didn't work try cd /system/bin then only execute the command...
yuweng said:
both of the tuts you mention works, i think you must have miss a step or two...
in fact, mkyaffs2image is scatter everywhere here at xda but i'll just attach it here just for your convenience sack...:good:
Use Root Explorer & copy it to /system/bin & at ADB shell, su then chmod 755 /system/bin/mkyaffsimage
if the command didn't work try cd /system/bin then only execute the command...
Click to expand...
Click to collapse
i use it but always the same error
at the end of setting working folder
when ask for show information
i obtain the same error "build.prop" not found
this evening i try to reinstall cygwin and the kitchen
Easy step-by-step guide on how to port CM10.1 (Windows, Mac, Linux...)
{
"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"
}
by: MaceksMod
Prerequisites
Computer (duh)
Rooted phone/tablet/phablet with recovery of choice installed (do not ask me how to do this)
7-Zip or WinRar for editing our .zip files
Notepad++ for editing our build.prop file and our updater-script
AOSP based ROM for your device
CM10.1 ROM from a similar device
Basic knowledge of computers and custom Android ROMs
Step 1: Setting up your work space
First, we will make a folder where we will be doing all of our work, you can name it what you like but for this demonstration, I will be naming mine CM10.1 PORT. Inside of this folder we will need to make 2 sub-folders, name them "PORT" and "BASE".
Step 2: Extracting and placing our initial ROM files
Put your AOSP based ROM in the BASE sub-folder
Put the CM10.1 ROM we are porting in the PORT sub-folder
Extract the build.prop (/system) and the updater-script (/META-INF/com/google/android) from each ROM into their folder
Step 3: Prepping the BASE ROM
Delete every app except for the following from syste/app:
Phone.apk
Telephony.apk
Gallery2.apk
SystemUI.apk
Step 4: Importing CM10.1's System apps
Copy over all of the system apps from your CM10.1 ROM (except for the ones listed in step 3) in to the system app folder of your AOSP BASE ROM.
Optional Depending on ROM outcome: Swap the SystemUI.apk and the framework folder
Step 5: Editing the updater-script (EDIT THE BASE's FILE, NOT PORT's)
Remove any title (the lines will start with "ui_print (") (don't delete any line that doesn't start with that)
Paste the following code in, edit all ares surrounded by { }
Code:
ui_print("*********************************************");
ui_print(" UNOFFICIALL CyanogenMod 10.1 ");
ui_print("*********************************************");
ui_print(" PORTED BY: {YOUR NAME} ");
ui_print("*********************************************");
ui_print("Ported Using MaceksMod's CM10.1 Porting guide");
ui_print("*********************************************");
ui_print(" Credits ");
ui_print(" {Developer of CM10.1 PORT ROM} ");
ui_print(" {Developer of AOSP BASE ROM} ");
ui_print("*********************************************");
Step 6: Put the newly edited script back into the proper folder of the BASE ROM
Step 7: Editing the build.prop
Change the following lines in the BASE's build.prop to match the PORT's build.prop
Code:
ro.build.id=
ro.build.display.id=
ro.build.version.incremental=
ro.build.date=
ro.build.user=
ro.goo.rom=
ro.goo.developerid=
ro.goo.version=
ro.CyanogenMod.version=
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.buildzipid=
Step 8: Place your newly edited zip in the system folder of the BASE ROM
Step 9: Swap the BASE ROM's media folder with the PORT's
Step 10: Swap the BASE ROM's fonts folder with the PORT's
Showtime!
Step 11: Rename the BASE ROM to CM10.1_{your devices codename}_PORT
Step 12: Flash the ROM using the CM10.1 install instructions
PS: This will not fix any bugs either one of the ROM's has, it will most likely create 1 or 2 more, or if you're lucky, maintain the same stability your base rom has
reserved
Is that true?
Sent from my GT-I9003 using xda app-developers app
AW: [GUIDE]{PORTING}[CM10.1] How to port CM10.1 for Noobs
to op, could u please explain what u mean with 'CM 10.1 ROM from a similar device'
edit: f.e i have a xperia arc s, what would be a similar device?
Sent from my girls pants
Cartman44 said:
to op, could u please explain what u mean with 'CM 10.1 ROM from a similar device'
edit: f.e i have a xperia arc s, what would be a similar device?
Sent from my girls pants
Click to expand...
Click to collapse
Just another xperia device with similar specs, since xperia is open source, you shouldnt have too many problems porting using my guide, im not familiar with the device line so i dont actually know any similar ones
Wucaiting said:
Is that true?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Yes, this is how I port cm10.1, paranoid Android and Aokp (still working on pacman)
AW: [GUIDE]{PORTING}[CM10.1] How to port CM10.1 for Noobs
jacobmacek said:
Just another xperia device with similar specs, since xperia is open source, you shouldnt have too many problems porting using my guide, im not familiar with the device line so i dont actually know any similar ones
Click to expand...
Click to collapse
okey, thank u
Sent from my girls pants
Cartman44 said:
okey, thank u
Sent from my girls pants
Click to expand...
Click to collapse
Let me know how it goes
Didn't work for me. Went to flash and "Installation aborted" came up. Thought this guide seemed too easy lol
kaivorth said:
Didn't work for me. Went to flash and "Installation aborted" came up. Thought this guide seemed too easy lol
Click to expand...
Click to collapse
There is error in your updater script
what can i do if the device has no asop rom developed. i was wanting to port for galaxy s5830i the s5830 has cm10.1 what would need editing to port that rom from s5830 to s5830i
gavster26 said:
what can i do if the device has no asop rom developed. i was wanting to port for galaxy s5830i the s5830 has cm10.1 what would need editing to port that rom from s5830 to s5830i
Click to expand...
Click to collapse
Good question; I do not know how similar those devices are but I am currently porting jb from the lg optimus v to the vortex, and the devices are so similar that i can flash ant op v rom to the vortex and boot the rom and use it w/very basic funtionality, all I have to do on my end is modify the kernel, ril, build.prop, and updater script to use it as a daily-driver. Can you flash a rom from the s5830 to the s580i? Try to if you havent, dont worry, you wont brick your device, just make sure you have a backup ready in case it doesnt boot. If it does boot, I can help walk you through the process!
It's not only for cm10.1 it's for all the roms, and there are literally 10 guides about this, why u no use search button
Mod close thread
Sent from my One V using xda premium
jacobmacek said:
Good question; I do not know how similar those devices are but I am currently porting jb from the lg optimus v to the vortex, and the devices are so similar that i can flash ant op v rom to the vortex and boot the rom and use it w/very basic funtionality, all I have to do on my end is modify the kernel, ril, build.prop, and updater script to use it as a daily-driver. Can you flash a rom from the s5830 to the s580i? Try to if you havent, dont worry, you wont brick your device, just make sure you have a backup ready in case it doesnt boot. If it does boot, I can help walk you through the process!
Click to expand...
Click to collapse
They have different processors the s5830 uses Qualcomm armv6 and the s5830i uses a broadcomm armv6 and doesn't have a dedicated gpu. The roms don't cross flash
cybervibin said:
It's not only for cm10.1 it's for all the roms, and there are literally 10 guides about this, why u no use search button
Mod close thread
Sent from my One V using xda premium
Click to expand...
Click to collapse
whoa bro, not every method is the same, chill out
gavster26 said:
They have different processors the s5830 uses Qualcomm armv6 and the s5830i uses a broadcomm armv6 and doesn't have a dedicated gpu. The roms don't cross flash
Click to expand...
Click to collapse
try swapping kernels
jacobmacek said:
try swapping kernels
Click to expand...
Click to collapse
I will have to develop my own kernel then
gavster26 said:
I will have to develop my own kernel then
Click to expand...
Click to collapse
Look up a guide on how to compile cm10.1, you'll need 64 bit ubuntu 12.+
I was going to learn and start from scratch but I couldn't find where to download thee source from
gavster26 said:
I was going to learn and start from scratch but I couldn't find where to download thee source from
Click to expand...
Click to collapse
git hub, heres cm10.1 for it
https://github.com/bieltv3/android_device_samsung_cooperve_cm10.1
{
"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"
}
Hey Guys,
Ever since the tutorial for Lollipop deodexing was posted on XDA portal, I was working on a batch deodex tool.
And finally it is complete.
Update...
I'm bit stuck with my personal life hence I do not have the time to manage this project , anyone who likes to take it over can do so.
The code is open source.
Pull requests are welcome...
Update 2
I will be updating this project whenever I have time, in the meantime if anyone wants to join this project feel free to PM me and I can add you to the project. Code will remain open source
Lollipop Batch Deodex Source Code
Also featured on XDA Portal
Features
Checks if the prerequisites are installed.
Displays the count of Odexed Apps. Priv-Apps and Framework Apps before DeOdexing
DeOdexes System Apps, Priv-Apps and Framework Apps in Batch Mode
Automatically Zipaligns deodexed files
Click to expand...
Click to collapse
Credits
Just wanted you guys to know that the credit for finding out this method goes for the poster of this article HERE (it is in Korean btw, I think it is Korean do correct me if I'm wrong).
The credit for translating and posting on XDA goes to @Tech N You
Thanks to @Golvfor all the help in fixing oat conversion issues
Thanks to @_riddle for his amazing oat2dex tool
Click to expand...
Click to collapse
Pre-Requsites
Windows PC with .NET Framework 4.5
Java 7, with Path Variable Set up
Click to expand...
Click to collapse
Usage
Make sure Java is installed and Java Path Variable is set in your PC
Due to the nature of Java tools, run the app from a path where there is no spaces, like D:\JBD
Unzip the Odexed rom zip, to say D:\MyRom (for example)
So within the folder D:\MyRom there will be subfolder "system" and within system folder, app, priv-app and framework folders must be present, you should select "system"
Now run the app, after Java check, it will prompt you to select a folder where Odex files are found, you should select D:\MyRom
If your rom is Odexed and your selection was correct (refer the folder structure image above step), the app will show you how many files will be DeOdexed, now follow the on screen instructions.
Sit back and relax and wait till the app finishes DeOdexing your rom.
Download
Changelog
Version 2.5
Works with both Java 7 and 8
Ignorelist option removed (causes lots of permission issues)
Version 2.5 Beta
Lots of code optimization
Much Better Java detection, also checks which version of Java
Better cleanup
64 bit rom support, no need to rename files, detects automatically
Added ignore list as some apps cause issues with deodexing
Latest oat2dex v7
Version 2.4
Lots of code optimization
Better Java detection
Deodexed files are automatically zipaligned
Version 2.3
Small validation bug fixes
Optimized code
Version 2.2
Deodexing Boot Oat Files, now this is a complete deodex solution
Much faster and optimized deodex process
Code optimizations and bug fixes
Version 2.1
Better working directory cleanup on exit
Added logging, logs should appear in your desktop
Version 2.0
Fixed Critical bug, now rom boots and all deodexed files work
Full windows app, for user convenience
Multi-threading
Version 1.1
Added Deodexing Framework apps support
Lots of Bug fixes
Added Easy folder selection by user
Better Deodex status reporting
Better Java check method
Version 1.0
Initial Release
Additional Info
reserved
joeldroid said:
Reserved
Click to expand...
Click to collapse
Awesome work
You deserve to be on portal! :good: :laugh:
Thanks mate it was your article in the portal that grabbed my attention
Merry Christmas
joeldroid said:
Thanks mate it was your article in the portal that grabbed my attention
Merry Christmas
Click to expand...
Click to collapse
Haha thanx but you're the real one that made this batch deodex thing possible! :good: Congrats :good:
Merry Christmas to you too dude! :good:
Any chance of more detailed guide for not so clever ppl like me. I unziped my rom to a folder named deodex on my C drive, then set the config to C:\deodex\system. But when i run the deodex tool its says no apps found. Where have i gone wrong.
Thanks
@joeldroid, Awesome work!! Everything is really simple so far, but I'm running into a "baksmali failed" message when I have everything placed from what I understand. Think you could help me out a little? Backsmali Failed Image
Hey @joeldroid, you saved me the job of having to deodex everything manually, mate. Will see if this really works. Thanks in advance, and merry Christmas for you too!
Waiting for framework deodexing support!
raynan said:
@joeldroid, Awesome work!! Everything is really simple so far, but I'm running into a "baksmali failed" message when I have everything placed from what I understand. Think you could help me out a little? Backsmali Failed Image
Click to expand...
Click to collapse
Hey raynan,
I was getting this as well, in some Samsung apps like Samsung IME, Samsung DriveMode etc, this I believe is something to do with the structure of the app and Samsung is using an incompatible structure, where baksmali fails to decompile. But I will try looking into this further.
steha said:
Any chance of more detailed guide for not so clever ppl like me. I unziped my rom to a folder named deodex on my C drive, then set the config to C:\deodex\system. But when i run the deodex tool its says no apps found. Where have i gone wrong.
Thanks
Click to expand...
Click to collapse
sure thing,
I will add a better usage guide today. Yesterday after a long few days I was sleepy and tired. I will add a more detailed one for everyone.
joeldroid said:
Hey raynan,
I was getting this as well, in some Samsung apps like Samsung IME, Samsung DriveMode etc, this I believe is something to do with the structure of the app and Samsung is using an incompatible structure, where baksmali fails to decompile. But I will try looking into this further.
Click to expand...
Click to collapse
Ah, good to know I'm not crazy thanks. No rush from me, enjoy your holiday
joeldroid said:
Hey Guys,
Ever since the tutorial for Lollipop deodexing was posted on XDA portal, I was working on a batch deodex tool.
And finally it is complete.
This is what it currently does...
Deodexes System Apps and Priv-Apps
I'm currently working on deodexing framework apps too.
I will release an updated version with framework deodex support hopefully within a week (hey its Christmas you know )...
Just wanted you guys to know that the credit for finding out this method goes for the poster of this article HERE (it is in Korean btw, I think it is Korean do correct me if I'm wrong).
Usage:
Download
Click to expand...
Click to collapse
Finally you're on portal
Tech N You said:
Finally you're on portal
Click to expand...
Click to collapse
yeah I'm so happy.
Framework deodexing complete. Posting an updated version today
joeldroid said:
yeah I'm so happy.
Framework deodexing complete. Posting an updated version today
Click to expand...
Click to collapse
Looking forward to it
can you plz explain in another way what to do after extracting zip file?
where to place files?
steha said:
Any chance of more detailed guide for not so clever ppl like me. I unziped my rom to a folder named deodex on my C drive, then set the config to C:\deodex\system. But when i run the deodex tool its says no apps found. Where have i gone wrong.
Thanks
Click to expand...
Click to collapse
I have added a much detailed user guide. have a look and let me know if something is not clear.
Cheers
startracker said:
can you plz explain in another way what to do after extracting zip file?
where to place files?
Click to expand...
Click to collapse
Please see the updated user guide, thanks
Error
Rom:cm12
Sent from my GT-I9500 using Tapatalk
@joeldroid
Awesome work! keep it up,
*** Disclaimer***
I will not be responsible for dead devices, bricked SD cards or whatsoever. Use the tool after reading instructions don't blame anyone for your carelessness.
Click to expand...
Click to collapse
INTRODUCTION
Hello all XDA members, guest viewing this thread. What started as my deodexing tool has now taken a form of project all thanks to @Shikhar Arvind for his glorious ideas. Today I present you The ULTIMATE MEDIATEK TOOL or simple UMT :laugh::good:
A tool all about MediaTek! This tool would be your last stop for everything! Forget Linux and stay on Windows!
This tool has various features and would be more coming up soon!
SCREENSHOT
Here a peek of what this tool looks like
{
"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"
}
FEATURES
As name suggests it has all basic and advanced features integrated. Now much better and faster with version 2.5!
- Simple and Enhanced MENU layout
- Deodex Menu (Specially equipped for MTK, Can deodex any chipset, any android version, Can create flashable zip for deodexed ROM (You must be rooted and have BUSYBOX installed on your device to flash deodexed ROM's zip created by the tool, Can create deodex environment from phone itself all you need is to press ENTER and boom! )
- Boot/Recovery unpacking/re-packing without LINUX or CYGWIN and as easy as 1.. 2.. No three You'll get it when you use the tool NOTE - While repacking you will get something like this "Does C:\Ultimate_MTK_Tool\Unpacked specify a file name or directory? Select d as it is directory not a file
- Logo.bin editor (Theme your device your style, Create or edit logo.bin easily)
- ADB/Fastboot command menu (Over 14+ commands integrated including logcat capturing very very very easy now and totally handy! Option to enter own ADB command too! For devs and ROM porters especially)
- ROM/Recovery porting guides with bug fixing for newbies No need to go online and search for the guides! Port and modify all by yourself! KitKat porting guide too
- Having some troubles with tool/too many junk files? Reset the tool!
- EXT4 or SPARSE System.img extraction (ALL ROMs/ALL DEVICE) supported without linux or cygwin. (NEW)
Click to expand...
Click to collapse
INSTRUCTIONS
1) Extract the tool in root C: drive only or it won't work! :crying:
2) Make sure no spaces is there like C:/Users/Tech N You/Desktop/Ultimate_MTK_Tool it should be simply C:/Ultimate_MTK_Tool
3) Make sure JAVA JRE is installed on your machine and is defined in windows system path.
4) You must have correct ADB drivers installed too
CHANGELOGs
Check post 2 for Changelogs
DOWNLOADS
Check post 3 for download link
FAQ
Q) Please provide me download link for Java JRE?
A) All noobs want links, No one wants to use Search Well here it is JAVA-Download Windows
Q) Will this tool work with non MTK Devices?
A) Well I've been asked this a lot lately! You can try though but boot/recovery unpacking won't work with NON-MTK device.
Deodex may/may not work, but extraction of system.img will work for all device's ROM's.
Q) This option gives me this error?
A) Please kindly post the error in detail for me to evaluate.
Q) I want this particular feature. How can I get it?
A) Please leave a reply with your request of feature and I'll see what can be done!
Q) Nice work! How can I donate to you
A) Check my signature please
Click to expand...
Click to collapse
CREDTIS
@JesusFreke For his amazing creation Baksmali/Smali
Unreal Mitch for fixed baksmali/smali for MTK devices
@michfood for his amazing boot unpack/repack utilities
Kandan for his logo builder program
@Xtreme Ornob : For his amazing guide for porting! I edited it few with latest tips!
@Lars124 for his amazing Universal ADB Helper! Thanks Man you made my tool a great success! Sorry didn't ask your permission before using it I modded it and fixed few bugs and added compatibility with my tool
@Shikhar Arvind for his ultimate idea for this tool!
And many more who helped me somehow
Click to expand...
Click to collapse
XDA:DevDB Information
Ultimate MTK Tool, Tool/Utility for all devices (see above for details)
Contributors
Tech N You
Version Information
Status: Stable
Current Stable Version: v2.5
Stable Release Date: 2015-03-11
Created 2015-01-09
Last Updated 2015-03-11
CHANGELOG
v 1.0 (Deodexing Tool)
New version v1.5 (Deodexing Tool)
• Fixed minor script errors
• Added many new features
• Made it true one click tool
• Added API change option from menu itself
• Added option to zipalign apk's
• Whole now in Menu layout. Refer NEW Screenshot to know more
• Other minor fixes
Version 2.0 (Ultimate Tool)
• Added Boot/Recovery unpacking/repacking utility
• Added ADB/Fastboot commands
• Added logo.bin editing feature
• Added Porting Guides
• Made it a Multi-Tool
Version 2.5
•Added EXT4/Sparse System.img unpacking without needing linux or cygwin or kitchen! Supports all ROM for all devices
• Updated baksmali/smali to latest version 2.5, these are especially equipped for MTK and are Lollipop ready! Now more faster deodexing!
• Fixed BOOT?RECOVERY repacking bug! Ramdisk folder was packed while repacking.
• Fixed One click flashable creator
• Fixed ADB cache formatting endlessly
• Very fast boot/recovery packing and repacking about 1/100 of a second
• Updated the files with latest version as of March 11 2015
• Various Codes Optimization
• All these features under 11 MB:laugh:
DOWNLOADS
Here is download link for Version 2.5 the latest.
OLD VERSION
Version 2.0 download here.
Reserved yet again and for final time :silly:
Looks promising.
Sent from my Micromax A88 using XDA Premium 4 mobile app
TESTING!
Awesome
parasthakur37 said:
TESTING!
Click to expand...
Click to collapse
Vishesh said:
I connected my mtk device, n went for deodexeding, but it always shows error in terms of.. Cannot find system/app folder... Where i need too put such folder???
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Awesome
Click to expand...
Click to collapse
It will automatically create folders. Choose option 2 and connect device
Make sure you have enabled USB Debugging
Awesome Work :good: :good: ..Looks Cool...ofcourse, i will try it but not now. (busy in studies )
Brother.. Seriously hats of to u.. Great work.. Tried ur deoodexing tool n it's works amazingly well.. Well done brother.. Great tool for mtk device.. One thing u should right in op that, after tool create deodexed rom zip, we need to add meta folder from other zip into it else it won't flash using recovery.. Looking forward to what other amazing features it gonna have.. ☺☺
Vishesh said:
Brother.. Seriously hats of to u.. Great work.. Tried ur deoodexing tool n it's works amazingly well.. Well done brother.. Great tool for mtk device.. One thing u should right in op that, after tool create deodexed rom zip, we need to add meta folder from other zip into it else it won't flash using recovery.. Looking forward to what other amazing features it gonna have.. ☺☺
Click to expand...
Click to collapse
You don't need to add anything from any other zip. You must have a rooted odexed device with busy box installed. Deodexed ROM will install
Wow
Thank you for this amazing swiss K tool, if you can add a functionality to unpack system img (ext4) this will be the must of the must.
How this was not discovered yet by many members, keep going sir.
Thank you again :good:
mobilis2009 said:
Thank you for this amazing swiss K tool, if you can add a functionality to unpack system img (ext4) this will be the must of the must.
How this was not discovered yet by many members, keep going sir.
Thank you again :good:
Click to expand...
Click to collapse
That requires sim2img compilation and requires cygwin you see. Well thanks for your valuable suggestion. Will find a way round.
Reply
mobilis2009 said:
Thank you for this amazing swiss K tool, if you can add a functionality to unpack system img (ext4) this will be the must of the must.
How this was not discovered yet by many members, keep going sir.
Thank you again :good:
Click to expand...
Click to collapse
Itz very much possible , hopefully included in next update!
:good:
Shikhar A said:
Itz very much possible , hopefully included in next update!
:good:
Click to expand...
Click to collapse
Yes will do it. Thanks for your response
Support fo MTK 6752/8752
Hello, thanks for this amazing All-in-One tool..:good:
I was just wondering if It could work with the new released MT6752 (or MT8752 as It's called for tablets) as I own a Teclast T98 MT8752, and I wold want to give it a try for porting a CWM for another MT6752 based device to my own device...
Thanks in advance
Thanks
Bro, really this is great!
And more than that is that you share your work for the people :good::good::good:
Best regards,
flux1000 said:
Hello, thanks for this amazing All-in-One tool..:good:
I was just wondering if It could work with the new released MT6752 (or MT8752 as It's called for tablets) as I own a Teclast T98 MT8752, and I wold want to give it a try for porting a CWM for another MT6752 based device to my own device...
Thanks in advance
Click to expand...
Click to collapse
Yes it's for all mtk devices
netmanmac said:
Bro, really this is great!
And more than that is that you share your work for the people :good::good::good:
Best regards,
Click to expand...
Click to collapse
Thanx
Great work.
Just problem when i try to unpack my boot/recovery.img
[total hits/matching patterns/non-matching patterns]
warn : empty file: C:\Ultimate_MTK_Tool\tools\boot_tools\off2.txt -
0 files checked, 0 changed.
1 warnings occurred.
[*] Size of C:\Ultimate_MTK_Tool\Input\stock.img 14532880 byte
[*] Kernel offset -
[*] Ram_header offset -
[*] Ram_disk offset -
[*] Extracting kernel_header...
[*] Extracting kernel...
[*] Extracting ram_header...
[*] Extracting ram_disk...
error: end offset is lower than start offset
1 errors occurred.
[*] Unpacking ram_disk.gz...
[*] Unpacking ram_disk.cpio...
Le fichier specifie est introuvable.
La syntaxe de la commande n’est pas correcte.
[*] Unpacked Successfully
--ORIGINAL UNPACKING SCRIPT IS CREATED BY MICHFOOD I DON'T OWN THIS
--I JUST MODDED IT SO THAT MY TOOL CAN BE COMPATIBLE WITH IT
--ALL CREDITS TO MICHFOOD FOR THIS AWESOME SCRIPT
Click to expand...
Click to collapse
Any idea ? Thanks
( Device : Samsung galaxy Note Edge)
*MT6580 NOUGAT PORTING GUIDE (3.18.35+ Kernel)*
©AndroidHQ254Projects®
{
"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"
}
*Boot image*
- Replace *kernel* and *fstab.mtxxxx*
*system/lib*
- Replace the whole *egl* folder
*system/lib/hw*
- audio.primary.default.so
- bluetooth.default.so
- gralloc.default.so
*system/vendor*
- Replace the whole *firmware* folder
*system/vendor/etc*
- Replace whole *mddb* folder
- custom.conf
*system/vendor/lib*
- Replace the whole *egl* folder
- libcameracustom.so
- libshowlogo.so
*system/lib/hw*
- audio.primary.mt****.so
- gralloc.mt****.so
- hwcomposer.mt****.so
*Build.prop*
Change the following like stock
- ro.product.model
- ro.product.brand
- ro.product.name
- ro.product.device
- ro.product.manufacturer
- ro.build.product
- qemu.hw.mainkeys
- ro.sf.lcd_density
*Updaterscript*
Change mount points appropriately. You can check mount points using *diskinfo* app
Lastly, zip and flash using your favourite custom recovery
This guide should give you an almost bugless rom for the mt6580 Nougat
Try and let me know of any issues that you face
Guide prepared by
*DEnnisMUrimi*
It is System/etc .Not, System/vendor/etc
Sdcard corrupted issue
But the sdcard is working
Help me fix this
Bluetooth share stopped working issue
camera not working properly (it just stops while taking pictures
how to extract system.new.dat
??
in the ported rom, the folder "firmware" is placed in etc, and the stock is located in the folder "vendor", is it possible in this case to port the firmware?
Stock rom as in mtk 6592 kit kat or what
AndroidHQ254 said:
*MT6580 NOUGAT PORTING GUIDE*
©AndroidHQ254Projects®
*Boot image*
- Replace *kernel* and *fstab.mtxxxx*
*system/lib*
- Replace the whole *egl* folder
*system/lib/hw*
- audio.primary.default.so
- bluetooth.default.so
- gralloc.default.so
*system/vendor*
- Replace the whole *firmware* folder
*system/vendor/etc*
- Replace whole *mddb* folder
- custom.conf
*system/vendor/lib*
- Replace the whole *egl* folder
- libcameracustom.so
- libshowlogo.so
*system/lib/hw*
- audio.primary.mt****.so
- gralloc.mt****.so
- hwcomposer.mt****.so
*Build.prop*
Change the following like stock
- ro.product.model
- ro.product.brand
- ro.product.name
- ro.product.device
- ro.product.manufacturer
- ro.build.product
- qemu.hw.mainkeys
- ro.sf.lcd_density
*Updaterscript*
Change mount points appropriately. You can check mount points using *diskinfo* app
Lastly, zip and flash using your favourite custom recovery
This guide should give you an almost bugless rom for the mt6580 Nougat
Try and let me know of any issues that you face
Guide prepared by
*DEnnisMUrimi*
Click to expand...
Click to collapse
Hi, Thank you for your restlesa work.
So when you said to replace files from stock rom to port rom, what exactly to you mean? Do you mean our Mtk 6592 kit kat stock rom to port rom or you mean we must find another Mtk 6592 nougat that matches our phone specs? Please do clarify.
And How exactly are going to get to patch those files since our stock rom both files are .img e.g system.img, boot.img and so on. Please forgive my ignorance.
razorrzr1 said:
how to extract system.new.dat
??
Click to expand...
Click to collapse
https://androidmtk.com/download-mtk-extractor
kakulanex said:
Hi, Thank you for your restlesa work.
So when you said to replace files from stock rom to port rom, what exactly to you mean? Do you mean our Mtk 6592 kit kat stock rom to port rom or you mean we must find another Mtk 6592 nougat that matches our phone specs? Please do clarify.
And How exactly are going to get to patch those files since our stock rom both files are .img e.g system.img, boot.img and so on. Please forgive my ignorance.
Click to expand...
Click to collapse
This is a Nougat porting guide for MT6580 devices with 3.18.35+ kernel
Harishwarrior said:
It is System/etc .Not, System/vendor/etc
Click to expand...
Click to collapse
As for this guide, it is correct with nougat based on 3.18.35+ kernel
Harishwarrior said:
Sdcard corrupted issue
But the sdcard is working
Help me fix this
Click to expand...
Click to collapse
Replace sdcard and vold from stock bin folder
Harishwarrior said:
Bluetooth share stopped working issue
camera not working properly (it just stops while taking pictures
Click to expand...
Click to collapse
Check on how you ported
suartex said:
in the ported rom, the folder "firmware" is placed in etc, and the stock is located in the folder "vendor", is it possible in this case to port the firmware?
Click to expand...
Click to collapse
This is because you are not dealing with MT6580 Roms based on 3.18.35+ nougat kernel
AndroidHQ254 said:
As for this guide, it is correct with nougat based on 3.18.35+ kernel
Click to expand...
Click to collapse
Ooh..sorry my mistake
Harishwarrior said:
Ooh..sorry my mistake
Click to expand...
Click to collapse
Cool. I understand
AndroidHQ254 said:
This is a Nougat porting guide for MT6580 devices with 3.18.35+ kernel
Click to expand...
Click to collapse
Sorry, i got one for mtk 6592, help answer the question. am i gonna use my kitkat rom files to port to nougat rom?
If the two Roms are based on the same kernel you can use your stock Rom files when porting
kakulanex said:
Sorry, i got one for mtk 6592, help answer the question. am i gonna use my kitkat rom files to port to nougat rom?
Click to expand...
Click to collapse
If the two Roms are based on the same kernel you can use your stock Rom files when porting
Bro any one can tall me how to port N custom
me how to port N custom ROM on MT6580
With kernel 3.18.19 MM(6.×× To 7.××)
Thanks and One last thing
kakulanex said:
Sorry, i got one for mtk 6592, help answer the question. am i gonna use my kitkat rom files to port to nougat rom?
Click to expand...
Click to collapse
thanks.
how do i extract system.img?