Related
I am very new to the android parralel scene (and the android and smartphones in general) so please excuse me if I have missed obvious things.
I am trying to do a custom android kernel on a CyanogenMod stable in order to activate SCTP support on a HTC Magic (sapphire) PVT 32B (google branded).
I have followed the this tutorial : wiki.cyanogenmod.com/index.php/Building_from_source to make the kernel (2.6.29-cm42) and this tutorial wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port for the packing.
My base is update-cm-4.2.14.1-signed.zip
I have tried with my new package as a module (and also redone modules.sqf) and also in-kernel.
I have tried the full update, and I've also tried to patch the kernel on a clean Cyanogen install.
Everytime I get stuck on the spash screen (google io09 developer conference).
Thanks for having read that post!
NB: Before the manipulation I had made a nandroid backup so I can get back without problem.
I use cm-recovery-1.4.img as recovery image with fastboot, and I noticed that I can't use adb to push data on the sdcard and then install it with the recovery. In fact the commands seem to work, but behind the scene it is the old sdcard.zip that is installed. I have to use my backup, fullboot, put my test update on the sdcard, rebootfastmode recover and then install.
Ah also, I would be really happy if you could tell me how to diagnostise errors on the bootphase. I'm currently totally helpless (and that's why I am posting here ^^).
I am now trying to build a new complete cyanogenmod from source with my custom kernel and modules. I don't think it will resolve my problem but I hope it will help me in understanding the problem.
While waiting for my repo sync (that won't end before tomorrow :/) I have made a new attempt at a CyanogenMod mod.
So i recompiled my kernel
Regenerated the modules
generated the modules.dep
Remade modules.sqf using update-cm-4.2.14.1-signed.zip as a base
Inserted wlan.ko and my new boot.img (made with unpack repack) into update-cm-4.2.14.1-signed.zip
Signed with the testkeys from the tutorial
Fastboot
update
Stuck...
I zipped some file if it could be of any help
my .config, zImage, boot.img, wlan.ko and modules.sqf
Thanks for reading
After some irc chat session I discovered it would be possible that my problem come from a bad boot.img generation.
I use old unpack / repack scripts (with whose you can't use the --base parameter).
I will try to fix this now, and retest!
Custom MTD Partitions
This is an implimentaion of lbcoder's Custom partition layouts
be sure to checkout that thread for the full history
What does it do?
Well, basically Custom MTD Partitions resizes your MTD partitions
for instance this is a CM6.1RC1, ( heavily customised )
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 73.0M 72.8M 236.0K 100% /system
/dev/block/mtdblock5 134.8M 107.2M 27.6M 80% /data
/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules
/dev/block/loop1 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /sd-ext
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
most of my Apps are on sd-ext, dalvik-cache is on data
/dev/cache is where the real cache partition is mounted, /cache is actually a bind mount from /sd-ext/cache
Applicable to..
Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )
The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **
v1.5.3 confirmed to work on heroc
v1.5.6 confirmed to work on bravo + bravoc ( with S-OFF )
unsure if it will work with your device? checkout the source on github ( or ask your favourite dev to take a look )
The 'Tech' in Breif
This method is beautifully simple...
When booting we give the kernel the mtd partition table we want to use..
Thats it
In practice we need to do this when booting to recovery, and booting the rom.
below are files to make this as simple flashing a rom.
Credits :-
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5 )
Safety First
This method is safe, however it is not without risk
Two things could potentially go wrong
Recovery flash corrupt
This is extremely unlikely, and tbh could happen anytime you flash recovery
If in the very unlikely event that you find you can't reboot to recovery you have three options
re-flash recovery via fastboot ( the preferred option )
re-flash recovery via ROM ( not a great option with cm5.0.x/cm6 )
Do the whole root thing all over again ( no one wants to do that )
system, cache , data partition unmountable - corrupt
Under the right ( or wrong ) circumstances it is possible to get 'junk' files stuck in system ( or cache,data ), and in such away that recovery can not delete them, more serious corruption can render the partitions unmountable.
It is actually quite straight forward to fix this, but it does require fastboot
Code:
fastboot erase system -w
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in then
Code:
for i in system cache userdata;do erase_image $i;done
and reboot
I would advise you seek out how to 'fastboot', which tbh is a good thing to have regardless of using this 'hack' as it can get you out of so much trouble
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
Prevention is better than cure
I have only managed to corrupt partitions when switching partition layouts while having files on cache or data, for example going from System 67.5 Cache 67.5 to System 90 cache 5 with
cache approx 80% 'used'...
I have not been able to repeat this if I wipe Cache before rebooting,
therefore I advise that you wipe both cache and data * after patching recovery ( and rebooting )
* along with system if you are using clockwork
OK, now lets patch recovery and a ROM
Install Instuctions
It really is quite simple
download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
create mtdpartmap.txt and put on /sdcard/ see configuration *
reboot to recovery
nandbackup
wipe cache + data
flash FR-recovery-v1.5.6-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Either : -
Nandrestore
Flash ROM + extras
flash FR-boot-v1.5.6-CustomMTD_S.zip
reboot
* configuration
The script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 90mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
data would be 117.8mb ( 116.7 useable )
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
Code:
echo "mtd 55 2" > /sdcard/mtdpartmap.txt
data would be 152.8mb ( 151.7 useable )
NB, above data sizes are for G1s, MT3Gs should add ~78mb
All In One Patch runner ( New to v1.5.3 )
new option to run the All In One Patch script ( versions 1.3.6 and higher )
the format is
Code:
aio <option1> <option2> <option3>...
e.g.
Code:
aio swap remount shabang lwp
By default it will install the sd-ext mount ( option sdext )
so a line just reading aio will be fine
Note: the patch must be on the root of the sdcard, and its file name must start with "fr-patch" and end with ".txt"
if you have several versions the newest ( as per files datetime stamp ) will be used
Faking your SPL
If your using an SPL that is not officially supported by your ROM and that ROM checks your SPL you can 'patch' to fake it.
Code:
echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )
you can by all means use any text editor you like, the script will automatically convert to unix format
NOTE : you are dodging the checks the ROM dev put in place, do not complain to them if this doesn't workout for you
in post 2 I have some 'CM6' Kernels I compiled for (1)0.95.xxxx SPLs
but I will only likely do these for RCs and Finals ( and there maybe a delay ).
In that post I point you towards the 'SafeSPL' ( 1.33.2003 ) this SPL is compatible with the current CM6 kernels ( so no need to wait for me or someone else to compile with bluetooth as modules ), but 1.33.2003 is not 'officially' supported ( its stock at 67.5mb system ) so you need to Fake your SPL ( say 1.33.2005 ) and resize to 90mb system ( or whatever you feel is optimum )
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
NB New Config option !!! to automatically run fr-patch136+
e.g.
Code:
mtd 90 2
spl 1.33.2005
aio swap remount shabang lwp a2sd
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.6.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
The Future....
lbcoder has already suggested ways in which we can implement this 'on the fly'
so for instance it would be possible for a ROM , to instruct recovery what MTD partition layout is required, reload mtd kernel modules, and then flash ROM + boot.img
for those with huge partitions
Hey, you could go all silly and dual boot between ROMs ..
Anyway, enjoy and feel free to modify/improve on these
Changelog
v1-5-6 : 2010-10-28
Calculate userdata size, greatly improves compatibility
Added a version to patch a boot.img ( boot-rpp ) with run-parts
didn't want to , but some are using roms which don't have run-parts, so the 06BindCache script wasn't running
Added a remove version ( remove )
flashing this will return the recovery to SPL's layout
I may well integrate that better, so you don't need a separate zip
AutoMTD_partitionPatcher can convert a recovery.img to a AutoMTD flashable zip
PatchUpdateScript.sh <full path to>/recovery.img
boot patcher is much cleaner, it just uses the cmdline of the running recovery
removed the default 90 2 sizing, you *must* set your own size in mtdpartmap.txt
v1-5-4/5
added stuff
removed stuff
moved stuff
see v1-5-6
v1-5-3 : 2010-08-13
This should be last version we need
greater compatibility with none dreams/sapphires
option to launch All in One Patcher
v1-5-2 : 2010-08-0
Bug fixes
recovery was getting written to boot ( flash_image <partition> is now a variable )
typo in env variable was causing cache and data calculations to fail
AutoMTD now prints version number ( when flashing patched Zip )
tided up system "0x" 'fudge' ( to be compatible with trout/sapphire fall back )
removes temp files from memory when done
v1-5-1 : 2010-08-06
Bug fixes, had an extra '0x' on the system start + functions had wrong env var for the location of dmesg derived partition map
v1-5 : 2010-08-06
Version numbers brought into sync
Zipe Filename - 'reordered' ( easier to see version numbers in CWR )
AutoMTD Patcher - changes as per boot Patcher + zip recursion fix ( my bad habit, thanks go to mblaster for pointing this out )
Boot Patcher - cleaned up cache bind mount
Now supports leagcy /system/sd mount point
[*]supports ROM Manager ( real cache partition mounted on /dev/cache, recovery dir symlinked from 'fake' to 'real' cache )
Recovery Patcher - can 'fake' your SPL ( see configuration )
Recovery Patcher - creates more noise ( advise wipe and reboot )
Single Patcher script ( so I don't have make the same changes to three different files that essentially do the same job )
No longer 'Hardcoded' to 32[a/b] Partition Layout ( figures out SPL layout via dmesg ) **
uses original boot/recovery img's base configuration ( i.e. EBi0 and EBi1 compatible )
=< v1.4
Recovery Patcher v1.3, added SPL faker
Boot Patcher v1.2, fixed oversite where boot.img was not 'dumped'
Recovery Patcher v1.1 initial
Boot Patcher v1.1 ( was a fail, it didn't patch boot.img on CM roms as the tmp boot.img was deleted, my fault for just using the AutoMTD Patcher's script ( which runs before the tmp boot.img is deleted )
Boot Patcher v1 initial
Todo
- 2010-08-13 redundent ( launching AIO script ) - I might add some stuff to cm5/6's backup routine via the Auto patcher, things like the "All in One" installed scripts: 05mountsd and remount
windows compatible AutoMTD script ( meh, I hate batch scripts )
- 2010-08-13 DONE - thinking of adding a config option to launch the "all in one" script, but have to make that recovery compatible first
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
mediafire downloads
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
The attached files are OLD
Custom MTD FAQ
FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my SPL starts with 0 or 10, and I want to try CM5.0.8 or/and CM6. DO I need to do anything extra?[/b]
A yeap, it seems the newer kernels are just a bit too big for x0.95.x00x SPLs, you can get round it with the below kernels. And to flash CM6 you need to 'fake' your SPL ( see configuration in OP ) or edit the updater-script. faking is easier.
However, I would recommend the 1.33.2003 SPL ( you still need to fake your SPL, but you won't need the 'special' kernels )
guide for flashing 1.33.2003 SPL by Ezterry
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-11
I have compiled a kernel, which I hope is NoneDanger compatible
the source is simply CyanogenMod's github, I have taken the config from cm6rc1, and simply changed the bluetooth to modules
this approach has worked in the past
It is pre-patched with AutoMTD, so just flash cm6rc1, then flash this
FR-CM6RC1-bootimg4NoneD-AutoMTD.zip(MD5: 386D9A05A3C0FFC08E5B3F844D437AA7)
mirrors
http://rapidshare.com/files/406402016/FR-CM6RC1-bootimg4NoneD-AutoMTD.zip
http://www.mediafire.com/?152jnqwyme3
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-27
NoneDanger compatible Kernel for RC2
FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 7858a8a8d126919318d1718c6e5167ec )
http://www.mediafire.com/file/ttxfcocsti3mma3/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
I'll have to dig out the src
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-08-15
NoneDanger compatible Kernel for RC3
2010-08-17 ( Sorry, old one had a status6 bug )
New one here
87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
src = http://github.com/CyanogenMod/cm-kernel/tree/48c57f11abaaf3de6c81f6f5c44cfe2637251184
no modifications its straight cm ( besides the config, which you can get from the compiled kernel or zcat /proc/config.gz )
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q do I need to flash both of the files each time I install a new rom?
A No, you only need to flash the recovery patcher once, unless you want to resize or you install a new recovery.
the boot patcher *must* be flashed after you have installed a new ROM or Kernel update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my cache looks odd in df, I see two and its the same size as data or sd-ext, is something wrong?
A everything is fine, since we shrunk cache its no good for things like the Market, so a script is installed to 'bind mount' cache with /sd-ext/cache or data if sd-ext is not mounted.
it actually turns out that /cache is not actually used in CM6, so I might adapt the script a little in a future release.
EDIT: as of version 1.5 the cache bind mount script mount 'real cache' separately, which should reduce confusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q When I tell ROM Manger to do something in recovery, it just reboots to recovery and does nothing. it used to do the action but not since I installed CustomMTD
A yeah, nearly forgot about that, I was going to fix it last week, basically ROM Manger writes commands to /cache, but its writing it to our bind mount so.. when recovery boots it doesn't see the commands.
In all honesty that one hasn't been pointed out to me yet, but yeah I can fix it..
EDIT: as of version 1.5 the cache bind mount is compatible with ROM Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
asb123 said:
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
Click to expand...
Click to collapse
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Firerat said:
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Click to expand...
Click to collapse
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead. I remember you said something about it being a miltiple of 128K.
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Ace42 said:
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead.
Click to expand...
Click to collapse
yeap, should be fine
personally I would be tempted to use clockwork, since you can erase system ( part of partition options )
.img files can be found here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I don't recommend flashing via ROM Manager with CM5 or CM6
fastboot it over, or flash via recovery
I may be a little over cautious recommending a full wipe, but I have never had problems when system, cache and data are clean.
if you are 'growing' system make sure cache and data are clean
if your 'shrinking' make sure system is clean ( so 'hangovers don't mess up /cache or data )
asb123 said:
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Click to expand...
Click to collapse
yes, you can 'grow' or 'shrink' at will
just hope it doesn't get used to be lazy and not trim bloat
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
TheNewGuy said:
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
Click to expand...
Click to collapse
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Firerat said:
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Click to expand...
Click to collapse
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
Because he bind mounted it.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
JAguirre1231 said:
Because he bind mounted it.
Click to expand...
Click to collapse
sorry for confusion
When I download stuff with dolphin HD it goes to /sdcard/download
maybe its different with stock browser
the cache bind mount is
added a few extra comments to make it easier to follow
/system/etc/init.d/06BindCache
Code:
#!/system/bin/sh
# check we don't already have a bind mount
# ( so if ran manually multiple times we don't end up with strange things happening )
if [ "`awk '/\/cache/' /proc/mounts |sed -n '$='`" -gt "1" ];
then
echo "cache already bind mounted"
echo `awk '/\/cache/' /proc/mounts`
exit
fi
# check if /sd-ext mounted, if yes then bind to /sd-ext/cache, if not /data/cache
if [ "`grep -q sd-ext /proc/mounts;echo $?`" = "0" ];
then
CacheDir=/sd-ext/cache
else
CacheDir=/data/cache
fi
# check we have something to bind mount, and create if not
if [ ! -d $CacheDir ];
then
install -m 771 -o 1000 -g 2001 -d $CacheDir
fi
mount -o bind $CacheDir /cache
# check dalvik-cache exists ( this is really for magics )
# so they don't end up in bootloop because dex files can not be created
if [ ! -d $CacheDir/dalvik-cache ];
then
install -m 771 -o 1000 -g 1000 -d $CacheDir/dalvik-cache
fi
actually, errm yeah it is d/l to /sdcard/downloads
not my doing
I guess cache really is pointless on froyo
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
speedysilwady said:
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
Click to expand...
Click to collapse
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Firerat said:
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Click to expand...
Click to collapse
lol yeah i was just gonna say the get prop error occured lemme remove those asserts resign and see what happens
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
double edit: i get the same error for any rom i try to flash when i look at the logcat. the only difference is cm's latest nightly build rebooted on the g1, super e freezes at the g1 screen...ima try to modify the .txt to go back to the stock layout so i can nandroid my cachehacked cm5.08 back if not...idk what to do..
speedysilwady said:
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
Click to expand...
Click to collapse
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Firerat said:
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Click to expand...
Click to collapse
noo this wasnt cm5.08 this was the latest nightly, same one youre 0704 on.
it got to the g1 screen and right when its abt to hit the boot animation it reboots.
i tried super e but it froze on the g1 screen
trying to get back to 67 67 for cache and system so i can nandroid but its weird that the logcat wont show no matter what rom i use.
I am trying to figure out how to port the recently released 3.4.10 kernel to CM10.1 for our device (One XL evita). I am able to build CM10.1 from source and I am able to build standalone kernels.
So far I've build CM10.1 with the HTC linux 3.4.10 kernel sources in place of the CM10.1 kernel sources at kernel/htc/msm8960 and the build completed with no errors but the device won't boot. The screen won't even turn on. I knew it obviously wasn't going to be this simple but I am stuck on how to proceed.
The CyanogenMod "porting intro"
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
seems to indicate that you should be able to get CM up and running with any kernel. Can anyone give me some pointers on what the basic requirements are for a kernel to boot?
vanja_z said:
I am trying to figure out how to port the recently released 3.4.10 kernel to CM10.1 for our device (One XL evita). I am able to build CM10.1 from source and I am able to build standalone kernels.
So far I've build CM10.1 with the HTC linux 3.4.10 kernel sources in place of the CM10.1 kernel sources at kernel/htc/msm8960 and the build completed with no errors but the device won't boot. The screen won't even turn on. I knew it obviously wasn't going to be this simple but I am stuck on how to proceed.
The CyanogenMod "porting intro"
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
seems to indicate that you should be able to get CM up and running with any kernel. Can anyone give me some pointers on what the basic requirements are for a kernel to boot?
Click to expand...
Click to collapse
We're already working on it....
h8rift said:
We're already working on it....
Click to expand...
Click to collapse
H8 I know you guys are always hard at work on the ROM but I'm trying to learn about the process by having a go myself. You never know, If I get up to speed I may be able to help you guys out. I'm not expecting to just get a perfect kernel up and running, I'm just hoping to build something that I can boot and play around with.
Do you have any advice? Is there a set pathway to getting a kernel up and running or a checklist of things that need to be in place? Is there any way to debug the kernel when it won't boot?
So the kernel is booting but not turning the screen on. I've attached the last_kmsg.
This is a summary of the errors that I've found.
Code:
pm8xxx-regulator pm8xxx-regulator.5: Failed to find supply ext_5v
Failed to create debugfs directory
pm8xxx_vreg_probe: regulator_register failed: 8921_usb_otg, rc=-517
pm8xxx_vreg_probe: error for 8921_usb_otg, rc=-517
pm8xxx_vreg_probe: regulator_register failed: 8921_hdmi_mvs, rc=-517
pm8xxx_vreg_probe: error for 8921_hdmi_mvs, rc=-517
LED trigger bkl_trigger failed to register (-17)
fail to get slimbus logical address -6
pm_qos_param: network_latency setup failed
[BATT][BMS] r_sense=10,i_test=0,v[failure=2000
[SMD][PKT] smd_pkt_open: DATA5_CNTL open failed -19
smem_alloc failed ch=34
smem_alloc failed ch=35
...
binder: t->buffer binder_alloc_buf fail
binder: 157:544 transaction failed 29201, size 80-4
mdp4_mixer_blend_setup: Error: no bg_pipe at mixer=0
Warning: unable to open an initial console.
Code:
WARNING: at /scr1/cm/system/kernel/htã/msm8960/fs/proc/generic.c:493 proc_register+0x148/0x1a8()
proc_dir_entry '/proc/emmc' already rdgistered
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock.c:185 clk_enable+0x58/0x210()
dsi1_s_p_clk: Don't call enable on unprepared clocks
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock-local.c:313 __branch_disable_reg+0x120/0x138()
dsi1_byte_clk status stuck at 'on'
WARNING: at /scr1/cm/system/kernel/htc/msm8960/fs/sysfs/dir.c:368 sysfs_add_one+0x7c/0x9c()
sysfs: cannot create duplicate filename '/dev/char/10:1'
WARNING: at /scr1/cm/system/kernel/htc/msm8960/arch/arm/mach-msm/clock-local.c:313 __branch_disable_reg+0x120/0x138()
dsi1_byte_clk status stuck at 'on'
@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
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. ??