Database Info

[Q] Go back to stock kernel?

Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks

Konstigt said:
Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks
Click to expand...
Click to collapse
Extract rom from original RUU first. Then you can extract boot.img from rom package.

I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.

Insomnis said:
I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.
Click to expand...
Click to collapse
I have a nandroid backup. I looked around in it but was unable to find the kernel. The most interesting file was boot.img (16MB) but I could not find how to open that image-file.
I looked at Bricked/faux123 threads but could not find the stock kernel there.

Aha, is boot.img the image that I should flash?
Then I will try do do that with fastboot..

Yep boot.img has kernel & ramdisk

Fuses said:
Yep boot.img has kernel & ramdisk
Click to expand...
Click to collapse
It was the file size that tricked me... 16MB compared to ~ 3-4MB for just zImage. But I guess it's the ramdisk that adds on size.

nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.

Fuses said:
nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.
Click to expand...
Click to collapse
Aha... thanks for setting me straight.

I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored

Konstigt said:
I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored
Click to expand...
Click to collapse
Me too. please guide me . Thaks

[DEV] CWM-Based Recovery 6.0.4.7

ClockworkMod Based Recovery 6.0.4.7, Swipe Enabled For Galaxy Core​
Donate and support Galaxy Core Development​
| [ Info ] |
Recovery built/compiled from Cyanogenmod recovery sources, with swipe ability to make the
operation without hardware keys. Recovery is Android 4.4 Compatible. Yes it is for every rom.
| [ Installation ] |
Method 1 :
via ClockworkMod Recovery
Method 2 :
via Odin
| [ Compatibility ] |
Android 4.2 (CM , stock)
Android 4.3 (CM , stock)
Android 4.4 (CM , stock)
| [ Download ] |
From DevDB : Download
XDA:DevDB Information
ClockworkMod Based Recovery 6.0.4.7, a Tool/Utility for the Samsung Galaxy Core
Contributors
ankur850, koush
Version Information
Status: Stable
Stable Release Date: 2014-03-02
Beta Release Date: 2014-02-18
Created 2014-02-12
Last Updated 2014-03-02

| [ Credits / Thanks ] |
koush for hard work on codes of CWM.
CyanogenInc for Cyanogenmod
Me for making this stuff.
Sandeep Kumar for risking his device. but his device is safe

ankur850 said:
| [ Credits / Thanks ] |
koush for hard work on codes of CWM.
CyaogenInc for Cyanogenmod
Me for making this stuff.
Click to expand...
Click to collapse
Great work... Thanks for ur Recovery.. It will definitely be useful in future

*If someone builds 4.4 Rom :-/
Sent from my GT-I8262 using Tapatalk

Is this working on I8260???
Sent from my GT-I8260 using xda app-developers app

weim1 said:
Is this working on I8260???
Sent from my GT-I8260 using xda app-developers app
Click to expand...
Click to collapse
awesome work rep dev ^_^

anyone tried ?

ankur850 said:
anyone tried ?
Click to expand...
Click to collapse
Gonna try it today, I will submit feedback
Sent from my GT-P7320 using xda app-developers app

Tried on i8260 with I8260XXAML3 stock rom, but blackscreen after galaxy core i8262 logo.

Guys do you have a separate recovery partition? Can I get the size of all the partitions in your phone please?

mmcblk0 - 7456 MB
mmcblk0p1 - 0 MB
mmcblk0p2 - 0.2 MB
mmcblk0p3 - 20 MB --- MODEM
mmcblk0p4 - 0 MB
mmcblk0p5 - 1 MB
mmcblk0p6 - 1 MB
mmcblk0p7 - 2 MB
mmcblk0p8 - 12 MB --- BOOT
mmcblk0p9 - 3 MB
mmcblk0p10 - 3 MB
mmcblk0p11 - 4 MB
mmcblk0p12 (mounted as /persist) - 7.9 MB. Filesystem - EXT4
mmcblk0p13 - 12 MB --- RECOVERY
mmcblk0p14 - 4 MB
mmcblk0p15 - 4 MB
mmcblk0p16 (mounted as /efs)- 11.8 MB. Filesystem - EXT4
mmcblk0p17 - 24 MB
mmcblk0p18 - 4 MB
mmcblk0p19 - 0.5 MB
mmcblk0p20 - 2 MB
mmcblk0p21 (mounted as /system) - 1281.8 MB. Filesystem - EXT4
mmcblk0p22 (mounted as /cache) - 709.5 MB. Filesystem - EXT4
mmcblk0p23 - 320 MB --- PRELOAD
mmcblk0p24 (mounted as /data) - 4913.2 MB. Filesystem - EXT4
mmcblk1p1 -- EXT SDCARD
Emulated (mounted in /storage/sdcard0) - 4863.2 MB. Filesystem - FUSE.

not working black screen in recovery mode

shrisangram said:
not working black screen in recovery mode
Click to expand...
Click to collapse
Same for me.

MirXas said:
Same for me.
Click to expand...
Click to collapse
ok, thanks for reporting the issue, although cwm 6.0.4.7 is not my priority right now.
You already got a working cwm for flashing upto android 4.3.
Maybe i'll try to fix the issue on later time when you need it.

Hey folks, Recovery is now stable, as i announced in thread. So now you can use it.
Some basic features : Swipe functions, left-right-up-down to do operation in recovery, without hardware keys
Happy flashing !

Working perfectly on GT-I8260.

thanks, stable at i8262 Fully Worked

i8260, flashed with Odin
Result: recovery loop

ji_llona said:
i8260, flashed with Odin
Result: recovery loop
Click to expand...
Click to collapse
seems like you landed to recovery every time when you select reboot. right ?

ji_llona said:
i8260, flashed with Odin
Result: recovery loop
Click to expand...
Click to collapse
Try flashing again, it must work.

[Q] Invisiable backups

I seem to have dug myself into a hole. I tried to test KitKat on my Galaxy Mega (GT-I9205). I found two roms that said they supported the Mega, so I made a backup of my current rom and flashed the first rom I found, played around with it and decided to go back to Jelly Bean, backup restored, no problems, all normal.
Then I tried the second rom (cm11 unofficial). Installed, no problems, played around with it and decided it wasn't for me and tried to revert to the JB rom backup. No chance. The recovery environment (which used to be cwm but somehow is now twrp v2.7.0.5 - don't ask me how? ) cannot even see any of the backups I have (and I have plenty, some of which were made by cwm and some by twrp - although probably not the same twrp version, not sure on that).
What I have tried.
Renaming the backups, moving the backups to different folders, using twrp to do a backup of the new rom to see where it saved it and then moving the backups to that folder, but it simply refuses to see them. So I can't go back. I even tried flashing a cwm recovery zip from within twrp - ok, I realise that is not likely to work, and sure enough it didn't..
My next thought was that I will have to continue using the cm rom that I have installed, but it has a problem too. When gapps is not installed every single application runs normally, but as soon as I install gapps both Titanium Backup (6.1.5.6) and Rom Manager (5.5.3.7) crash. I have tried this three times (two different gapps versions) and including cache and dalvik wipes before flashing gapps, absolutely no change.
So in short I have a perfect backup that can't be seen, I have a cm11 rom without gapps that works perfectly normally and I have a cm rom with gapps where two of my most important applications constantly crash.
I would really like to go back to JB - but if anyone can tell me how to fix titanium and rom manager on the present install, that would be fine, I would stick with cm11.
Another complication is that I don't use windows (linux only) so Odin is not an answer for me.
Help!
Edit: Here is another thought. I can easily do without Rom Manager, since Twrp took over my recovery it does nothing anyway, but is there a replacement out there for Titanium Backup? Even something half as capable I would be able to cope with until TB maybe issues an update that works with gapps on cm11.
Edit2: It seems there is such a tool. Jrummy Ultimate Backup seems to have the same functions as Titanium and it runs perfectly so far whereas Titanium still crashes all the time. This might be the answer to continuing to use Cm11.

Well here is a clue. When I look at the backups in the Ultimate backup interface, it actually identifies them by type and it appears that the backups I thought were twrp backup (I even included the letters 'twrp' in the backup name) are in fact cwm backups not twrp. This may be why twrp can't see them!!
Don't think I will ever be able to go back to these now unless I force another recovery onto the phone (cwm of course) - without Odin that is none too easy.
However, the good news is that at the moment (early days still) the CM11 rom with Ultimate Backup on it is running very smoothly so maybe I don't have to go back at all, we will see.

I finally solved this after 4 days puzzling over it. I will tell you how even though I received absolutely no help from anyone on the forum.
All my backups (which used to work) look like this:
Code:
/h/c/b/c/2014-08-10-lite> ls -l
total 2235668
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.b
-rw-rw-r-- 1 manjaro 1000 492 Aug 15 15:39 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.b
You can see from the fourth column that I have three zero byte files in there - don't ask me how, it is just how the backups were written, I didn't interfere with the process and all five backups were the same and they had been used to restore the image before without problem.
What I did was to change it to this:
Code:
/h/c/b/c/2014-08-10-lite-COPY> ls -l
total 2235672
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.a
-rw-rw-r-- 1 manjaro 1000 339 Aug 16 11:45 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.a
Removed the zero byte files, renamed the other files appropriately and then regenerated the nandroid.md5 file with the correct values, cd to the backups folder and run:
Code:
md5sum *>nandroid.md5
(on Linux that is)
The amended backup restored at the first attempt.
This process was much complicated by the fact that these backups were done in CWM and my running ROM had TWRP. Thanks to the writers of Heimdall for solving that problem for me - nothing windows or android possessed was capable of doing so.
Having succeeded in restoring the backup I then flashed TWRP onto the Jelly Bean rom so it is now a simple rom flash to switch from one the other.

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

[MTK][TOOL][APP]MTKTransfROM, port your ROM directly from phone!

Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Code:
[B]system/bin/vold [/B] (Copy this file from your device)
[B]system/etc[I]/[/I][/B] (Copy entire directory, replacing existing files)
[B][I]-[/I]system/etc/ [/B] (First delete ROM folder and then copy entire folder)
[B]system/lib/libaudio[I]*[/I][/B] (Copy all files that starts with libaudio...)
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.​

Can you add support for MT6752 devices?

You can add it yourself putting your custom files in the folder I explained in the tutorial

RacerOttavio97 said:
You can add it yourself putting your custom files in the folder I explained in the tutorial
Click to expand...
Click to collapse
Thanks, I will try it and see if it works :fingers-crossed:

I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.

HypoTurtle said:
I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.
Click to expand...
Click to collapse
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.

RacerOttavio97 said:
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.
Click to expand...
Click to collapse
MTKsplit can/does run on android itself - thats why I wrote it. It's a sh - primarily using dd to split the boot/recovery. I removed the #! at the top so the same script can be run fron recovery and system (making it default to the shell that calls it - /sbin/sh in recovery and /system/bin/sh in system).
Just tested the MTKsplit against a 6592 recovery.img and it works fine:
Code:
[email protected]_phone:/tmp # ls -la
ls -la
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
[email protected]_phone:/tmp # MTKsplit recovery-6592 unpack
MTKsplit recovery-6592 unpack
Unpacking recovery-6592 - will only take 30 seconds
All Done...
Command line: f30"
Ramdisk unpacked to /tmp/work
[email protected]_phone:/tmp # ls -la
ls -la
-rw------- root root 4265472 2015-10-05 16:24 kernel
-rw------- root root 512 2015-10-05 16:23 kernel_header
-rw------- root root 2048 2015-10-05 16:23 mtk_header
-rw------- root root 1598976 2015-10-05 16:24 ramdisk.cpio.gz
-rw------- root root 512 2015-10-05 16:24 ramdisk_header
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
drwx------ root root 2015-10-05 16:24 work

Android sdk
Is it necessary to be the port rom is the same android sdk level of my mobile stock rom ?!

RacerOttavio97 said:
Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.
Click to expand...
Click to collapse
playstore-item not found
what ca i do..??

link not work