[zImage][Port] Mali r3p1 driver [Samsung 4.2.2] Kernel - Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve

I built a kernel which includes Mali r3p1 driver.
It helps to port Samsung 4.2.2 STOCK Firmware [ i9300 I9300XXUFME3 ].
It includes correct modem source and all driver will be work.
For developers,
1. You should modify the ramdisk for this kernel.
[ Please mod I9300XXUFME3 for I9305 ]
2. Put my modules to lib/modules/.
3. Make boot.img [ make.sh ]
4. Mod android ROM [ ril, sensors and etc.... ]
[ You should base I9300XXUFME3 4.2.2 ROM ]
Sorry to poor english ;(
I'm Korean.
and I don't have I9305 device.
but Korean Galaxy S3 LTE (SHV-E210S/K) and Korean Galaxy Pop (SHV-E220S) were already ported Samsung 4.2.2 ROM ( I9300XXUFME3 base ).
More Korean device's information link :
http://blog.naver.com/sktjdgns1189/100198243057
http://theteamdev.com
Thanks

Thanks man!!!
Would be awesome to try 4.2.2!

Ah sweet this is probs y my 4.2.2 port didn't work
Sent from my GT-I9305 using xda app-developers app

Could anyone provide a link for a working custom recovery for Samsung SHV-E220S, pls?
I'm looking for 2 days, found 2 versions, Odin flashable, but after flashing OK(?!), I'm still on stock recovery(3e)!!!
SOLVED!
Due to xda mskip problem is solved:
Quote
"Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit."
All credits go to mskip!

you can find here
bib*oops said:
Could anyone provide a link for a working custom recovery for Samsung SHV-E220S, pls?
I'm looking for 2 days, found 2 versions, Odin flashable, but after flashing OK(?!), I'm still on stock recovery(3e)!!!
SOLVED!
Due to xda mskip problem is solved:
Quote
"Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit."
All credits go to mskip!
Click to expand...
Click to collapse
http://www.sayanogen.com/file
you can find here
much roms for galaxy pop [shv-e220s]

Related

[HOW TO][N00B][w/oPC]How to make a flashable.zip[No PC needed!]

This is my most favourite topic!
I will enlight you all how to create your own flashable zip file. I'm trying to make it as n00bfriendly as I can.
Code:
DISCLAMER
Follow this guide step by step so nothing can happen. Anyway I'm not responsible for any damage caused because of me or this thread. If you have any questions or problems, don't be shy and
[B]ask me I will help or create it for you![/B]
So here we go:
There are two ways how to do it:
WAY ONE (PC):
What you need:
*brain (for those who don't know...)
*your pc
*notepad++
*7zip
*FlashGuide.zip (can be found in attachments)
WAY TWO (I9001):
*brain (yes, here too...)
*your I9001 (you don't need root)
*FlashGuide.zip (can be found in attachments)
*Explorer or RootExplorer app
******************************
WAY ONE (PC):
1.download the files for your pc and install them
2.open 7zip and unzip FlashGuide.zip
3.In the folder FlashGuide you will see two sub-folders which are as "META-INF" and "system"
4.see: META-INF
5.see: SYSTEM
WAY TWO (I9001):
1.download the files for your I9001
2.open the app and unzip FlashGuide.zip
3.In the folder FlashGuide you will see two sub-folders which are as "META-INF" and "system"
4.see: META-INF
5.see: SYSTEM
-----------------------------
META-INF​
Go back to the root of the folder and open up"META-INF". leave those files untouched and open "com" and then "android".
Inside the android folder, you will see two files named as "update-binary" and updater-script.
WAY ONE (PC):
Open the "updater-script" file with "notepad++".
You are free now to type some code you want just press HERE
WAY TWO (I9001):
Open the "updater-script" file by longpress it and choose "Text Editor".
You are free now to type some code you want just press HERE
-----------------------------
SYSTEM​
Concentration! It's nearly finished. Let's see, what you have to do with the "system" folder. It's in the root of the FlashGuide folder.
You should add your MOD now, HOW TO:
ADD an APP
If you want to add an apk file then create a folder named "app" and that "app" folder contains the apk file(s) that you want to put in the system partition of the ROM.
FRAMEWORK
If you want to add framework-mods then add a folder named "framework" into the "system" folder.put your framework mods into that folder. (in the most cases the Framework mods are in a Framework-res.apk file.)
LIBS
If you want to change libs then create a folder named "lib" and put the libs in there.
BIN
If you want to put bin files then the subfolder in the system subfolder will be "bin" and it will contain the bin files.
SCRIPTS
If you want to add scripts then name a folder in the system "etc", create there a folder named "init.d" and put the scripts in there.
NOW CHECK THIS LIST:
I updated the UPDATER-SCRIPT
√
I updated SYSTEM
√
IF NOT BOTH BOXES ARE TICKED, THEN YOU HAVE TO GO BACK!
After doing all that:
WAY ONE (PC):
open 7zip, go to the directory where the FlashGuide folder is located and zip it
WAY TWO (I9001):
After you modded the "Updater-Script" a backup had automatically been created. In this case it's the Updater-Script.bak data. Just delete it. Then go back to the directory where the FlashGuide folder is located, do long press the FlashGuide folder, scroll down, select "zip this folder" and follow further instructions.
Now you can rename the .zip to whatever you want!
THAT's ALL FOLKS!
PRESS HELP IF I THANKED YOU!
-----------------------------
HOW TO EDIT THE UPDATER- SCRIPT:
So once the updater-script has been opened with text editor (notepad++/Explorer), you will have to type some codes or you will get no reaction.
1​
To Display the information of the particular Mod when you select to flash it in CWM Recovery
Code:
ui_print("***The Text you want to display***");
2​
To mount the /system partition
Code:
run_program("/sbin/busybox", "mount", "/system");
3​
To add the apps in the /system partition
Code:
package_extract_dir("system", "/system");
4​
To unmount the /system partition
Code:
run_program("/sbin/busybox", "unmount", "/system");
5​
To delete some apps, frameworks,...
Code:
delete("/system/app/XY.apk");
or
delete("/system/framework/franework-res.apk");
6​
To show progress
Code:
e.g.:
show_progress(0.500000, 0);
show_progress(0.500000, 20) show_progress(0.500000, 40) show_progress(0.500000, 60) show_progress(0.500000, 80) show_progress(1.000000, 0)
Basically the show_progress command indicates the progress of the installation of the MOD.
an example how to use it: [HIDE]
after writing the name/info of the mod write:
show_progress(0.500000, 0);
after writing the code to mount the system partition,you can write the next one:
show_progress(0.500000, 20);
extracting the package from the system partition: show_progress(0.500000, 40);
unmount system partition show_progress(0.500000, 60);
after writing the "happy ending" of installing this zip, write: show_progress(0.500000, 80);
maybe a "reboot system" or "thanks for flashing" phrase, write: show_progress(1.000000, 0)[/HIDE]
Basically the show_progress command indicates the progress of the installation of the mod.
In this case the progress bar fill up in increments of 10, with a 0.5 second delay. What is actually being done by these lines, however, is to keep adding 0.5.
If the progress commands had enough time, this would also mean that each chunk would fill at a slower pace (since the duration is increasing), but the script moves fast enough that the user never sees this.
None of this actually changes the functionality of the script, hence my earlier declaration that this was somewhat POINTLESS to learn. This is strictly an aesthetic issue for the user, but if you are going to write scripts, I hope this comes in handy.
NOTE:
If you are using CM, you have to mount your "system" manually, using the option "mount and storage" in CWM
PRESS HELP IF I THANKED YOU ;D
IF YOU WANT TO LET ME CREATE YOUR FLASHABLE ZIP, TELL ME.
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
very detailed, well done :good:
Sent from my Galaxy Nexus using xda app-developers app
tomixdev said:
very detailed, well done :good:
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot! you know, it's my first Tutorial! Cheers
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
yeah, thanks man now i don't have to use my pc (which hangs even for a windows 7) to make a zip
I've juste tried this and at the flash, it show me an error ...
In the zip there was just root browser in app and the modded update-script !
Sent from my GT-I9001 using xda premium
LiiQuoR said:
I've juste tried this and at the flash, it show me an error ...
In the zip there was just root browser in app and the modded update-script !
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
please tell me what you wanted to do and upload the file. i will correct it for you
EDIT: have you deleted the updater-script.bak file?
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Its ok i'm an idiot ! But when i flashed the zip i had a bootloop !
It's just a test but here is my zip : http://depositfiles.com/files/psp2rs2op
Can you put the show_progress in it and can you explain the "(0.500000, 20);" in the command plz !
Sent from my GT-I9001 using xda premium
LiiQuoR said:
Its ok i'm an idiot ! But when i flashed the zip i had a bootloop !
It's just a test but here is my zip : http://depositfiles.com/files/psp2rs2op
Can you put the show_progress in it and can you explain the "(0.500000, 20);" in the command plz !
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
of course i can do. but not now, tomorrow i'm all yours
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
outerh3aven said:
of course i can do. but not now, tomorrow i'm all yours
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Click to expand...
Click to collapse
K ! Thanks :thumbup: and good night !
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
K ! Thanks :thumbup: and good night !
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
Sorry, really well done .zip! Just forgot to add the delete section (If you have an app, etc. already installed) should work now.
will add delete section, permission section and set_progress section right after school.
:thumbup: really well done LiiQuouR!
EDIT: if you are on a Cyanogenmod, aosp or anything what isn't stock 2.3.6 rom, you have to mount system manually
In CWM go to mounts and storage and choose system
, might be the mistake too...
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
I'm on UltraGen 1.6 with twrp!
Thx ! Can you just explain the comand show_progress now^^?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
I'm on UltraGen 1.6 with twrp
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
UltraGen is CM9 based, so you have to mount manually
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Ok in the command for unmount system you have written "umount" its "unmount" no?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
LiiQuoR said:
Ok in the command for unmount system you have written "umount" its "unmount" no?
------------------------------------------------------------------
Device : Samsung Galaxy S+ (i9001)
Rom : UltraGen 1.6
Kernel : CastagnaIT Kernel V7.3 Ex/Uv
Recovery :TeamWin Recovery Project (TWRP) 2.3.1.1
Sent from Belgium with XDA Premium
Click to expand...
Click to collapse
I don't know how it's in TWPR, I'm using CWM. usually the system is not mounted
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Are you sure of your zip ?
Because i've mounted /system , i've flashed the zip and it failed and when i reboot the phone , it bootlooped... can you please review my zip? (Yours)
Sent from my GT-I9001 using xda premium
LiiQuoR said:
Are you sure of your zip ?
Because i've mounted /system , i've flashed the zip and it failed and when i reboot the phone , it bootlooped... can you please review my zip? (Yours)
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
sorry, today I'm totally retarded, got a 3hour nostop test and i'm exhausted as hell... will do it some time later at home.
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
In the end line of update script you.should put an empty line and after mounting system you should unmount it and be sure your premissions are fixed!
If you do that rules you will never have a bootloop!
alireza7991 said:
In the end line of update script you.should put an empty line and after mounting system you should unmount it and be sure your premissions are fixed!
If you do that rules you will never have a bootloop!
Click to expand...
Click to collapse
wrong, but thanks for your try. worked for me every time without this empty line.
finally got my mistake (today was not my day). used the gb meta-inf files to make a ics zip
can be downloaded here LiiQuoR
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
outerh3aven said:
wrong, but thanks for your try. worked for me every time without this empty line.
finally got my mistake (today was not my day). used the gb files to make a ics zip
can be downloaded here LiiQuoR
sent from my GameBoy Color
------------------------------
working on:
Project Stock (4.0.4)
Click to expand...
Click to collapse
Ok ! But link doesn't work ! Always a problem not your day as you said
Sent from my GT-I9001 using xda premium

[Q] Problems with galaxy note [N7000] & android commander

Hello this will be my very first post at XDA although i have browsed the forums everyday since i can remember...
here is what i have:
Device: Galaxy Note N7000
Rooted: Yes
CWM: Yes
Rom: Slim Bean [latest version] & all the mods/add ons
Android Version: 4.1.2
Kernel: I did not flash one so it would be the one that comes with slim bean rom.. here is the info in my "about phone settings" 3.0.15-CM-gf76e4eb [email protected] #1
here is my problem:
i have installed everything by the book and i have a fully working note with the slim bean v3.1 [latest] adb works and i can successfully get root access using "adb shell su" i have the latest busybox pro installed and the latest supersu pro installed.
i have always used android commander to pull and push files to and from devices and other stuff without any problems, but with my new galaxy note i constantly get the root access NO. i have usb debugging enabled and i even have adb over network enable either way i still have no root access... if anyone can help me solve this i will be willing to donate i am at my witts end trying to figure it out..
people have told me many things such as i have a stock kernel or i need to fnd a way of changing secure adb to insecure adb whatever this means...
thanks in advance
[SOLVED]
it was the kernel which stopped root access being given to android and total commander so the slimbean kernel was based on stock or so i would guess.. i flashed the hydracore OC v7 kernel from xda and bam it works great now lol..

[GUIDE][CM Port][ MT6589 only] Port CyanogenMod 10.2/11 for all MT6589 devices

@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

Latest N750XXUCNK2 Full Firmware (SC Imported) OG

Download
Code:
philz_hl3g_build4_2.tar
Update.zip
Pit And Odin.zip
De-Bloater_NEO_N750_Soft_Removal.zip
Code:
Flash Latest Custom Recovery For N3N Yet philz_hl3g_build4_2.tar
Flash De-Bloater_NEO_N750_Soft_Removal.zip using Recovery
Remove All Waste Pre Installed
System Apps 422 Files Worth More than 700 MB+
List of removed files inside De-Bloater
PHP:
delete("/system/app/AccuweatherPhone2013.apk");
delete("/system/app/AccuweatherPhone2013.odex");
delete("/system/app/AlarmWidget.apk");
delete("/system/app/AlarmWidget.odex");
delete("/system/app/ApplicationsProvider.apk");
delete("/system/app/ApplicationsProvider.odex");
delete("/system/app/AssistantMenu.apk");
delete("/system/app/AssistantMenu.odex");
delete("/system/app/Bloomberg.apk");
delete("/system/app/BluetoothTest.apk");
delete("/system/app/BluetoothTest.odex");
delete("/system/app/Blurb.apk");
delete("/system/app/Books.apk");
delete("/system/app/Bridge.apk");
delete("/system/app/Bridge.odex");
delete("/system/app/BrowserProviderProxy.apk");
delete("/system/app/ChatON_FEATURE_H.apk");
delete("/system/app/Chrome.apk");
delete("/system/app/ClipboardSaveService.apk");
delete("/system/app/ClipboardSaveService.odex");
delete("/system/app/DigitalClock.apk");
delete("/system/app/DigitalClock.odex");
delete("/system/app/Drive.apk");
delete("/system/app/Dropbox.apk");
delete("/system/app/DropboxOOBE.apk");
delete("/system/app/DualClockDigital.apk");
delete("/system/app/DualClockDigital.odex");
delete("/system/app/EasyFavoritesContactsWidget.apk");
delete("/system/app/EasyFavoritesContactsWidget.odex");
delete("/system/app/EdmVpnServices.apk");
delete("/system/app/EdmVpnServices.odex");
delete("/system/app/ELMAgent.apk");
delete("/system/app/ELMAgent.odex");
delete("/system/app/Evernote.apk");
delete("/system/app/FactoryCamera_FB.apk");
delete("/system/app/Flipboard.apk");
delete("/system/app/FWUpgrade.odex");
delete("/system/app/GearManagerStub.apk");
delete("/system/app/GestureService.apk");
delete("/system/app/GestureService.odex");
delete("/system/app/Gmail2.apk");
delete("/system/app/GMS_Maps.apk");
delete("/system/app/GoogleCalendarSyncAdapter.apk");
delete("/system/app/GoogleContactsSyncAdapter.apk");
delete("/system/app/GoogleSearchWidget2.apk");
delete("/system/app/GoogleSearchWidget2.odex");
delete("/system/app/GoogleTTS.apk");
delete("/system/app/Hangouts.apk");
delete("/system/app/InteractiveKeyguardTutorial.apk");
delete("/system/app/InteractiveKeyguardTutorial.odex");
delete("/system/app/InteractiveTutorial.apk");
delete("/system/app/InteractiveTutorial.odex");
delete("/system/app/KeyguardSPlannerWidget.apk");
delete("/system/app/KeyguardSPlannerWidget.odex");
delete("/system/app/KNOXAgent.apk");
delete("/system/app/KNOXAgent.odex");
delete("/system/app/KnoxAttestationAgent.apk");
delete("/system/app/KnoxAttestationAgent.odex");
delete("/system/app/KnoxMigrationAgent.apk");
delete("/system/app/KnoxMigrationAgent.odex");
delete("/system/app/KnoxSetupWizardClient.apk");
delete("/system/app/KnoxSetupWizardClient.odex");
delete("/system/app/KnoxSetupWizardStub.apk");
delete("/system/app/KNOXStore.apk");
delete("/system/app/KNOXStore.odex");
delete("/system/app/Magazines.apk");
delete("/system/app/MediaUploader.apk");
delete("/system/app/MobilePrint3.apk");
delete("/system/app/MobilePrint3.odex");
delete("/system/app/MobilePrintSvc_CUPS.apk");
delete("/system/app/MobilePrintSvc_CUPS_Backend.apk");
delete("/system/app/MobilePrintSvc_Epson.apk");
delete("/system/app/MobilePrintSvc_HP.apk");
delete("/system/app/MobilePrintSvc_Samsung.apk");
delete("/system/app/MobilePrintSvc_WFDS.apk");
delete("/system/app/MobileTrackerEngineTwo.apk");
delete("/system/app/MobileTrackerEngineTwo.odex");
delete("/system/app/Music2.apk");
delete("/system/app/PanningTryActually.apk");
delete("/system/app/PanningTryActually.odex");
delete("/system/app/PickUpTutorial.apk");
delete("/system/app/PickUpTutorial.odex");
delete("/system/app/PlayGames.apk");
delete("/system/app/PlusOne.apk");
delete("/system/app/PolarisViewer5.apk");
delete("/system/app/PopupuiReceiver.apk");
delete("/system/app/PopupuiReceiver.odex");
delete("/system/app/QuickMemoCover.apk");
delete("/system/app/QuickMemoCover.odex");
delete("/system/app/QuickMemoWidget.apk");
delete("/system/app/SamsungContentsAgent.apk");
delete("/system/app/SamsungWatchON.apk");
delete("/system/app/SamsungWidget_ActiveApplication.apk");
delete("/system/app/SamsungWidget_ActiveApplication.odex");
delete("/system/app/SapaMonitor.apk");
delete("/system/app/SBrowser.apk");
delete("/system/app/SBrowser.odex");
delete("/system/app/SBrowserTry.apk");
delete("/system/app/SBrowserTry.odex");
delete("/system/app/SCONE_Android_ProxyService.apk");
delete("/system/app/SCParser.apk");
delete("/system/app/SecEmail_J.apk");
delete("/system/app/SecEmail_J.odex");
delete("/system/app/SecExchange.apk");
delete("/system/app/SecExchange.odex");
delete("/system/app/SecFactoryPhoneTest.apk");
delete("/system/app/SecHTMLViewer.apk");
delete("/system/app/SecHTMLViewer.odex");
delete("/system/app/ShareShotService.apk");
delete("/system/app/ShareShotService.odex");
delete("/system/app/SmartcardManager.apk");
delete("/system/app/SmartcardManager.odex");
delete("/system/app/SmartcardService.apk");
delete("/system/app/SmartcardService.odex");
delete("/system/app/SPlannerWidget_2013.apk");
delete("/system/app/SPlannerWidget_2013.odex");
delete("/system/app/SPrintSpooler.apk");
delete("/system/app/SPrintSpooler.odex");
delete("/system/app/Stk.apk");
delete("/system/app/Stk.odex");
delete("/system/app/SViewCoverService.apk");
delete("/system/app/SViewCoverService.odex");
delete("/system/app/SysScope.apk");
delete("/system/app/talkback.apk");
delete("/system/app/TravelService.apk");
delete("/system/app/TravelService.odex");
delete("/system/app/UserDictionaryProvider.apk");
delete("/system/app/UserDictionaryProvider.odex");
delete("/system/app/Videos.apk");
delete("/system/app/WeatherWidgetDaemon.apk");
delete("/system/app/WeatherWidgetDaemon.odex");
delete("/system/app/WebManual.apk");
delete("/system/app/WebManual.odex");
delete("/system/app/WlanTest.apk");
delete("/system/app/WlanTest.odex");
delete("/system/app/WritingBuddyService_2013.apk");
delete("/system/app/WritingBuddyService_2013.odex");
delete("/system/app/YahoostockPhone2013.apk");
delete("/system/app/YahoostockPhone2013.odex");
delete("/system/app/YouTube.apk");
delete("/system/priv-app/ContextProvider_H.odex");
delete("/system/priv-app/DeviceTest.apk");
delete("/system/priv-app/DiagMonAgent.apk");
delete("/system/priv-app/DiagMonAgent.odex");
delete("/system/priv-app/EasyLauncher.apk");
delete("/system/priv-app/EasyLauncher.odex");
delete("/system/priv-app/FmmDM.apk");
delete("/system/priv-app/FmmDM.odex");
delete("/system/priv-app/FotaClient.apk");
delete("/system/priv-app/FotaClient.odex");
delete("/system/priv-app/GalaxyFinder.apk");
delete("/system/priv-app/GalaxyFinder.odex");
delete("/system/priv-app/GmsCore.apk");
delete("/system/priv-app/GoogleBackupTransport.apk");
delete("/system/priv-app/GoogleFeedback.apk");
delete("/system/priv-app/Hearingdro.apk");
delete("/system/priv-app/HwModuleTest.apk");
delete("/system/priv-app/KLMSAgent.apk");
delete("/system/priv-app/MagazineHome.apk");
delete("/system/priv-app/MagazineHome.odex");
delete("/system/priv-app/MusicFX.apk");
delete("/system/priv-app/MusicFX.odex");
delete("/system/priv-app/NoiseField.apk");
delete("/system/priv-app/NoiseField.odex");
delete("/system/priv-app/PageBuddyNotiSvc2.apk");
delete("/system/priv-app/PageBuddyNotiSvc2.odex");
delete("/system/priv-app/Pinboard.apk");
delete("/system/priv-app/Pinboard.odex");
delete("/system/priv-app/S_Translator_CSLi_STUB.apk");
delete("/system/priv-app/SamsungApps_H.apk");
delete("/system/priv-app/SamsungLink18.apk");
delete("/system/priv-app/Samsungservice_xhdpi.apk");
delete("/system/priv-app/sCloudBackupApp.apk");
delete("/system/priv-app/sCloudDataRelay.apk");
delete("/system/priv-app/sCloudDataSync.apk");
delete("/system/priv-app/sCloudQuotaApp.apk");
delete("/system/priv-app/sCloudSyncCalendar.apk");
delete("/system/priv-app/sCloudSyncContacts.apk");
delete("/system/priv-app/sCloudSyncSBrowser.apk");
delete("/system/priv-app/sCloudSyncSNote.apk");
delete("/system/priv-app/sCloudSyncSNote3.apk");
delete("/system/priv-app/SecSafetyAssurance.apk");
delete("/system/priv-app/SecSafetyAssurance.odex");
delete("/system/priv-app/SensorService2_5.apk");
delete("/system/priv-app/SHealth2_5.apk");
delete("/system/priv-app/SimpleWidget.apk");
delete("/system/priv-app/SimpleWidget.odex");
delete("/system/priv-app/SketchBookStub.apk");
delete("/system/priv-app/SNS.apk");
delete("/system/priv-app/SPDClient.apk");
delete("/system/priv-app/SPDClient.odex");
delete("/system/priv-app/SPPPushClient_Prod.apk");
delete("/system/priv-app/StoryAlbumStubActivationUpgrade.apk");
delete("/system/priv-app/StoryAlbumWidget.apk");
delete("/system/priv-app/StoryAlbumWidget.odex");
delete("/system/priv-app/S-Voice_Android_phone.apk");
delete("/system/priv-app/SyncmlDM.apk");
delete("/system/priv-app/SyncmlDM.odex");
delete("/system/priv-app/TripAdvisor_Stub.apk");
delete("/system/priv-app/Velvet.apk");
delete("/system/priv-app/AutomationTest_FB.apk");
delete("/system/priv-app/CloudAgent.apk");
delete("/system/priv-app/ContentSearch.apk");
delete("/system/priv-app/ContentSearch.odex");
delete("/system/priv-app/ContextProvider_H.apk");
Code:
Flash Update.zip to get some latest apk with ads free ROM
Files Included com.google.android.gms-1.apk Latest Google Service Framework
[COLOR="Red"]com.sec.watchon.phone-1.apk[/COLOR] bring back watch on app in ROM
as samsung discontinued watch on in newer ROMs
[COLOR="Red"]eu.chainfire.supersu-1.apk[/COLOR]
Super SU Use this to root your ROM as well
1st go into recovery than go to advance reboot u will ask
for apply su apply that than reboot into rom open super su it will
ask for binary update do a normal update
than u r rooted reboot enjoy rooted rom without flashing auto cf root
[COLOR="Red"]hosts[/COLOR] for Removing ads
[COLOR="Red"]Phonesky.apk[/COLOR] latest Playstore
Download N750XXUCNK2 Full Firmware
Inside Files List
Code:
AP_N750XXUCNK2_3349537_REV00_user_low_ship.tar.md5
BL_N750XXUCNK2_3349537_REV00_user_low_ship.tar.md5
CP_N750DDUCNG3_1663889_REV00_user_low_ship.tar.md5
CSC_ODD_N750ODDCNG5_2311980_REV00_user_low_ship.tar.md5
FULL LATEST FIRMWARE DIRECTLY IMPORTED FROM SAMSUNG OFFICIAL SOURCE
U CAN ALSO USE TO UNBRICK YOUR #NOTE 3 NEO
ENJOY
thank you for Neo Support !!
Can you help two problems:
1. Re-post the links because all unable to download after 6 ad clicks.
2. In detail, how do I use the downloaded files to unbrick my Note 3 neo 750L. it was bricked, because I changed from 4.4.2 back to 4.3 by Odin (I am novice).
Thank you,
Unable to download.. it is asking to download some exe file which is detected as malware....
The files are unavailable after dozens of charity clicking the adfocus links. Annoying!

(GUIDE)(PORT CM 12.1 ) MTK6592 CM 12.1 PORTING GUIDE (Only For Porters) :)

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. ??

Categories

Resources