Database Info

[MOD][RECOVERY] Custom MTD Partitions (resize Data,System and Cache ) [ 2010-10-29 ]

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.

(ROM)CM7.1(2.3.7)Sapphire32a(NR-6.35.16.19)Sept 30(Unofficial)

I Was Helping another member get a rom working for the 6.35 radio sapphire and thought I'd look into making cm7 run better on our new radio magics, I've had it compiling for a long time now but it was slow and laggy and several things were broken. So I concentrated on DietGingerbread.
Well I succeeded this weekend at making it run ok and everything is working as it does on any other cm7 phone install.
It has my 710 kernel with 245/528 as default. (updated kernel, added 352000 to cpu freq table)
You must have 1.76.2007 spl
You should have 6.35.16.19 radio
cwm-carz-v4.0.1.4-0820-recovery, RA's hero recovery on sapphire does not work
install the rom
install gapps (optional)
Custom MTD explained below. (optional)
________
New Sept 30
Fixed merge issue in frameworks/base, fixes settings for lockscreen and a few other quirks
2.3.7 now
cm-7.1.0-09302011-6355Sapphire
________
New Sept 28
Latest cm7 source, a few changes, unlock bubbles are nice
New kernel with many changes, it has great battery life again, only 3% drop overnight now, 40 hours 35 minutes on battery and I have 18% left still, no problems over a weeks use.
Gapps package has the new market now, the old one auto updated to the new one every time for me anyways
Everything is on Andriodspin now, nice fast servers
cm-7.1.0-09262011-6355Sapphire (I didn't wipe and it works perfectly, your mileage my vary)
--------------
Aug 20
2.3.5, CM teams updates merged and tested
New kernel
Updated power profile (not sure if it affects battery or not)
Incall ui off by default, you can enable in settings
Off animation is not on by default anymore, you can turn it on in settings (it's still buggy for me anyways, I need to rewrite the code so it isn't using gles2.0)
Led settings are back (not that a lot of you noticed it gone lol, I didn't notice either)
Many tweaks for more speed, mostly in ADW
Fast enough now that I don't even overclock at all now
I forgot to add, I fixed gles1.1, neocore now works
Finally, here is the update!
cm-7.1.0-08202011-6355Sapphire-signed
This is the gapps you should use, the minimal package that way all is updated and current from the market
gapps-gb-20110613-signed.zip
*Optional*
This is the newest recovery, 4.0.1.4,(in fastboot usb mode: fastboot flash recovery cwm-carz-v4.0.1.4-0820-recovery.img )
cwm-carz-v4.0.1.4-0820-recovery (unzip and use the fastboot binary in the zip to flash, you can not flash the zip from recovery!)
--------------
New July 10 (fixed)
This is the version I have in a post in this thread (over 350 downloads and only one issue so far)
Updated kernel with camera speed improvement (not in the previously posted rom, I'll post an update package for you guys)
Fixed audio issue after taking pictures
Recovery 4.0.0.5
Rom:
CyanogenCARZ-7.1.0-07102011-6355Sapphire-signed (todays build downloaded and tested)
gpsshim replacement for wake issue http://www.multiupload.com/DKOFY5UNR3
Kernel: (update zip for those already running the july version)(not needed for above rom)
carz-2.6.34.4-07072011-signed
Google apps:
gapps_mdpi_gb_20110613_S(go to market and update)
Recovery: (fixes a wipe issue)
carz-clockworkmod-v4.0.0.5-recovery
--------------
June 21
Updated to latest cm/aosp sources, new kernel with updated usb and audio, fastest version yet. Also 4.0.0.2 recovery is working great so far.
Testing reports are good, wipe if you have issues.
CyanogenCARZ-7.1.0-06192011-6355Sapphire-signed
Carz-Clockworkmod-4.0.0.2-recovery
gapps_mdpi_gb_20110307_S
--------------
June 08
A very stable and fast release so far
New kernel with updated usb, tethering and debug notification working now
New recovery (optional)
I did not wipe but I was coming from builds that were only 1 day old, If in doubt wipe and format system.
on off animations may or may not work for you, still looking into it
cm-CyanogenCARZ-7.1.0-06062011-6355Sapphire-signed
This is not needed for anything but testing for you guys, tethering involved rom changes also.
carz-2.6.34.2-06052011-signed (flashable zip with new kernel and modules)(modules are sqf)
Recovery coming, v3.2.0....
--------------
May 23
Many updates from both the cm team and aosp (close to RC I think)
Smoother and more responsive
Updated kernel
If you have any boot issues you have to fully wipe and format system from recovery
update-cm-CyanogenCARZ-7.1.0-05232011-6355Sapphire
MD5SUM: cf815615f72cf5df900e2f8f73b57c5d
Clockworkmod-Carz-recovery-v3.1.0.1-05-23-2011.zip (newest recovery compiled with rom)
--------------
May 14 Consider this a Nightly
No wipe update if coming from may 08 version
update-cm-CyanogenCARZ-7.1.0-05142011-6355Sapphire
p
md5sum 8f3fda6dbb4b47ac3098ab28b3f29181
--------------
May 08 Stable
Sorry about the wait, I had real life work to do, also several things quit working with the cm7.1.0, 2.3.4 update, it's all good now I believe and seems much faster, This is on a clean install without custom mtd that I tested.
update-cm-CyanogenCARZ-7.1.0-05092011-6355Sapphire for mtd use, everything else is the same as the version below
update-cm-CyanogenCARZ-7.1.0-05072011-6355Sapphire
MD5SUM 137e6ec97d0498c5097bce4e42bfe102
I also started compiling clockworkmods recovery with the rom for our devices, it has all the options plus a few I've never seen before.
Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011
It's a zip with the recovery and the fastboot binary, unzip, cd to directory and:
Code:
fastboot flash recovery Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011.img
--------------
April 24
You must wipe all for this release, I used google to save settings and apps before wiping and then used it to restore everything, works now on mtd also.
If you use seo's 2.0 recovery (as I do) you have to use fastboot to erase system, as the recovery does not. (I'm looking in to fixing it)
Code:
fastboot erase system -w
Cyanogen-CARZ-7-6355sapphire-signed
Here is a new boot mtd flasher for custom MTD, I fixed cm7 so it doesn't bind data/local/download to cache/download anymore, market fixed for good on MTD
DGB-boot-v1.5.8-CustomMTD_S
(I will have a newer compile out later today with a few changes like the kernel)
--------------
Cyanogen-7-RC4-6355Sapphire
MD5SUM
Cyanogen-7-RC4-6355Sapphire-MTD
--------------
Cyanogen-7-RC3-6355Sapphire
CM7 RC3 carz v03.27.2001.2-MTD
--------------
gapps
Limited support as I'm only pulling in cm teams changes. Enjoy! Big props to all of Cyanogenmods team.
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
New Nightlies
--------------
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed.zip
MD5SUM f005d14bd708403ff92dafba475837ff
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM ce91ba7861de46e9e52bd12c8d39ecb9
I have no long movies, please check and see if they work now
--------------
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed.zip
MD5SUM
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM
--------------
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed-AutoMTD.zip
--------------
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed-AutoMTD.zip
MD5SUM
Custom MTD: Please know what you are doing here, read and then read some more.
first before anything run this either in term or using adb (only "df" in term)
Code:
adb shell df
you should get something like this
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 174080 [COLOR="Red"]139540[/COLOR] 34540 80% /system
/dev/block/mtdblock5 169728 19832 149896 12% /data
/dev/block/mtdblock4 133120 39968 93152 30% /cache
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 4352 4352 0 100% /system/xbin
/dev/block/mmcblk0p2 468331 8226 435120 2% /sd-ext
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/secure/asec
look at "/dev/block/mtdblock3 174080 139540 34540 80% /system"
I used "mtd 140 3" in my mtdpartmap.txt
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
These instructions are from firerats thread (recommended reading material) modified a little for my use.
Install Instructions:
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
Create mtdpartmap.txt and put on /sdcard/ (use 140 3) see configuration above or in Firerats thread < recomended
reboot to recovery
nandbackup
wipe (I also "fastboot erase system -w" )
flash DGB-recovery-v1.5.8-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
wipe again
Flash any of my custom MTD roms
reboot
Click to expand...
Click to collapse
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
The above is what I did and I'm running fine right now,
Below is with 130 3 mtdpartmap, I trimmed some stuff out
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 133120 131772 1348 99% /system
/dev/block/mtdblock5 340736 83740 256996 25% /data
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/mmcblk0p2 468331 10053 433293 2% /sd-ext
/dev/block/mmcblk0p2 468331 10053 433293 2% /cache
/dev/block/mtdblock4 3072 780 2292 25% /dev/cache
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/secure/asec
169 > 340 on data

Great job!

Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.

Unkjcr said:
Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.
Click to expand...
Click to collapse
Sure but can you wait till it gets tested out a little bit first?

carz12 said:
Sure but can you wait till it gets tested out a little bit first?
Click to expand...
Click to collapse
Sure! I was thinking in testing the ROM first before doing that. Thanks

Awesome, downloading asap

Hi Carz,
Do i need to change my SPL and recovery?

Dexreyes said:
Hi Carz,
Do i need to change my SPL and recovery?
Click to expand...
Click to collapse
Not if it's what is in your sig.

carz12 said:
Not if it's what is in your sig.
Click to expand...
Click to collapse
Thanks Carz, I'm downloading it right now, will test this, looks promising!

So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!

Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
Have you turned on jit yet?
Sent from my Dream/Sapphire using XDA App

i got install error, status 7 when installing this rom. Please look into this.

hellokittyr said:
i got install error, status 7 when installing this rom. Please look into this.
Click to expand...
Click to collapse
Do you have 1.76.2007 spl?
Sent from my Dream/Sapphire using XDA App

Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
It supports apps2sd (native) and supports app2ext if I add the script
Sent from my Dream/Sapphire using XDA App

thx carz, testing it right now...

Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log

Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
[email protected] said:
Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log
Click to expand...
Click to collapse

So far so good, are there any plans on a MTD friendly version?

orange_24 said:
Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
Click to expand...
Click to collapse
Em, could you specify what do you mean by 'reset' ? Wiping? Rebooting?
I started with a wipe, and rebooted since... Didn't help.

install Completed but reboot to recovery ?

Sharp FX PLus/Capa ADS1 - Root, System Dump, ClockWorkMod Recovery, Device Info

EDIT 12/24/2014: Finally got back into my XDA account and finally updating this post with (hopefully) functionall links to the files I still have, Merry Christmas everyone!!
HI, found the misc development section so I'm putting all my findings on the Sharp FX Plus ADS1. Closest device I found that has cyanogenmod is the ZTE V9 (Theres a Z71 and some others also), I'm sure there are others but figure I'd post this in an appropriate spot incase anyone is curious. I'm attempting to get CyanogenMod of booting on this for a nice learning experience.
This phone has a Froyo 2.2.2 ROM, when "slimmed" or de-bloated the little thing is pretty snappy. Chainfire 3d Pro installed with no problems, ClockworkMod Recovery backups/restore work (updating to newer version doesnt "recognize" CWM installed, but older one allows reboot into recovery), Terminal and ADB dont give me any issues at all, logcat can be done from boot with the insecure boot.img. Hopefully this information is usefull to anyone curious.
Removed "links other information" - my old domain is not up.
Drivers:
-Sharp has them available from this site (for Windows/OSx)
Device:
Qualcomm MSM7x27 @ 600MHz
Adreno 200
512MB RAM, 512MB ROM (200-ish available to user).
Root:
-SuperOneClick 2.3.3 worked fine for me
ClockWorkMod Recovery:
-You should already be rooted before doing this.
-Made from the stock recovery.img processed on the CWM builder site. Its version 6.
-Only thing that doesnt work at the moment is mounting via USB mass storage. Aside from that, works like a charm.
-Download the files zip (attached to this post)
-Copy flash_image and the recovery.img of choice (stock is in root of archive, CWM folder contains the ClockWorkMod Recovery).
-Run these commands from terminal (on device or adb)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
System Dump:
-I can try and make a "stock ROM" flashable zip, but I'll need a stock dump from a rooted ADS1. I only have the modified "stock ROM".
LINKS NOW AT DEV-HOST
Modified ROMS:
Stock 2.2.2 based (google apps pre-installed)
ADS1-2.2.2 test-acemod4x
CM6 Z71 port
CM6.1.2-ADS1 Z71 test-port
modded google apps for the CM6 port ONLY
Other info:
-output of mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock1 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /persist yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /fotaup yaffs2 rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackup-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.adobe.reader-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.aol.mobile.aim-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
-output of cat /proc/mtd
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00040000 "boot"
mtd1: 0a500000 00040000 "system"
mtd2: 00100000 00040000 "splash"
mtd3: 02800000 00040000 "cache"
mtd4: 00080000 00040000 "fota_state"
mtd5: 02100000 00040000 "fota_up"
mtd6: 00080000 00040000 "misc"
mtd7: 00280000 00040000 "persist"
mtd8: 00500000 00040000 "recovery"
mtd9: 0bcc0000 00040000 "userdata"
-Also BOARD_KERNEL_ stuff (when breaking the original kernel down)
Code:
BOARD_KERNEL_CMDLINE mem=458M console=ttyMSM2 androidboot.hardware=qcom
BOARD_KERNEL_BASE 13600000
BOARD_PAGE_SIZE 4096

Was stuck for a while trying to repack a insecure kernel, few "bricks" (thank goodness for CWM's backups lol).
Got it to work and boot! Its still the same original boot.img but I was able to repack it with ro.secure=0 and other changes to the default.prop (enabled adb, debugging etc..)
Heres a link with info on it, and heres the files (in zip this time) incase anyone wants to test.
Basically (if anyone wants to try this insecure.boot.img) for test (make sure you have CWM and a Nandroid backup first) - Phone should already be rooted (SuperOneClick 2.3.3), ADB Debugging on (I used a ADB shell to do this, you should be able to run the commands from the terminal on the device itself)
Open the archive, copy the flash_image (if you havent from the CWM Install), also copy the insecure.boot.img over to the sdcard (you can alsio do this with the original boot.img to restore)
Code:
su
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
flash_image boot insecure.boot.img
reboot
All goes well, the phone should reboot normally. MInes took a little longer on initial booting, but it went through using that boot.img and the stock rom.
Now onto the next hurdle (getting CyanogenMod to compile) - The problem I was having before was using a version of mkbootimg that did not support the --pagesize option.
I'll try repacking the zImage that was built into a CM7 ramdisk and see if I can get past the "Sharp" screen and try to boot..
If anyone has any thoughts on the subject it would be greatly appreciated, back to the terminal I go

CM6 Booted
Well, went back to trying to see what would "boot" in this phone. My attempt to port CM6 to this ADS1 is somewhat successful!!!!
Currently botted into a modified Z71 CM6 ROm, using the insecure.boot.img I repacked for the Sharp ADS1.
Compared the system structures side by side and added the ADS1 bits (also for the surf_keyboard and other stuff).
Removed Z71 specific files, made a hybrid build.prop with the ADS1 changes.
Result: Boots!! Pretty Usable!!!
Still Broken:
-No camera/camcorder (checking the libcamera files)
-WiFi
-keyboard backlight
-some keyboard buttons (@ key, everything else is good - onscreen and swype are in from stock rom)
Works:
-battery charging (even switches to the sharp charging screen when its off but plugged in)
-radio - H+ on the status bar, data, sync, sms, etc.. (havent tried MMS yet)
-bluetooth - enables fine, just need something to pair with
-boots (initial boot takes a while as it does its firstrun thing, reboots are very fast)
-sound works
-graphics seem smooth as butter (going through the UI, etc..)
-touchscreen
-qwerty keyboard
-screen rotation works
-CM6 gapps work
Anyways, I'm kinda excited that atleast CM6 booting and (aside from the broken stuff) somewhat usable! I'll attatch the logcat I made with adb as it booted, did some testing, etc.. Incase anyone wants to see.

CyanogenMod 6 ROM testing Updates.. (SO FAR SO GOOD!!)
(I accidentally posted this in the General thread I had, and it wouldnt let me delete it - so I put the information in this as its under the Misc Development section)
Update on "porting" CM6 for the Commtiva Z71 to the Sharp ADS1.
Not Working:
-WiFi - logcat shows an error when loading the libra.ko seems to load librasdioif.ko fine however
-Camera - logcat shows problem loading liboemcamera.so (using the ADS1 libs and Camera.apk)
-3d Acceleration - works, but has some hiccups (so it still needs *some* work - importing some Adreno200 EGL libs over improved greatly so far)
-USB Mounting - havent gotten to this yet, still working on WiFI/Camerea. ADB however works flawlessly (push, pull, reboot, lolcat/logcat, etc..)
[email protected] Key and SYM on physical keyboard arent mapped correctly (going to see if I can poll the keys and figure that out) also the Camera physical button does not map.
Working:
-Calls (speaker also, mute, normal, etc..)
-Data (uploaded my wordpress post from the device, market sync works, etc..)
-SMS/MMS
-SDCARD (can be browsed internally, SD-Ext for app2sd works, no USB Mounting yet)
-Bluetooth
-Audio
-Keyboard Backlight+Sensors (properly shuts off when screen is slid closed)
-Deep Sleep seems to be working (battery life seems to be decent, still gotta work other bugs out)
-Rotation sensor (open keyboard, screen rotates for you also)
-Auto brightness sensor looks to be working normally (even turns keyboard backlighting off it seems)
http://acebox.info/2012/07/sharp-fx-plus-ads1-z71-cm6-test-rom/
I'm a little stumped on the WiFi + Camera issue, both roms (CM6-Z71 and ADS1-Stock) are running similar Kernels, and the version of Froyo is almost identical; CM6-Z71 Is actually 2.2.1 and ADS1 is 2.2.2 as I recieved it (CyanogenMod runs sooo much better ).
wifi libs (in /system/lib/modules):
Code:
libra.ko
librasdio.ko
modules.dep.bb
If anyone has some time to help or atleast offer some insight, I can repost the stock dumps, nand backups, kernel, ramdisk, logcats - and even a cwm zip I've made for flashing a "slimmed" version of the stock 2.2.2 Froyo as well as any "working" version of the CM6 "port" I'm attempting). I've been comparing logcats from the stock rom and this to see what can possibly be stopping wifi/camera working..
The CM6 ROM IS EXPERIMENTAL AND NOT A DAILY DRIVER AT ALL - (I wouldnt consider it untill WiFI, Camera, etc.. are functional. It is usable - even updated my wordpress post from the device with screenshots, hower it is still an Development Work In Progress).
If anyone is feeling brave (or wants to help test), I've uploaded the CWM zips I used (experimental) onto my site (linked in this post). FLASH CLOCKWORKMOD RECOVERY AND DO A NAND BACKUP FIRST!! Then go nuts flashing away lol. Hope someone finds this usefull.
PS. THIS IS NOT A DAILY DRIVER ROM, ONLY FOR TESTING!
Info/ROM links - current ones posted here towards the bottom (so I only have to update one set of links lol)

WiFi partially working
UPDATE:
Got wifi working, test release here more information here. I fixed a few things in the ramdisk and updater-script. Now to get the camera/video and USB mounting working (ADB is fully functional, push/pull/logcat/lolcat work).
Also the original Swype, Weather, SMS and Email widgets work. For the market, flash the CM6 20110501 MDPI gapps package from here (its persistent between full wipes, use a NAND backup to return to clean install, workingo n a updater-script that fully wipes and removes all traces of GAPPS (doesnt seem to currently).
Shots of About Phone and Storage (theres some room I think)

UPDATE (EGL and Camera fixed!) - Notes on swapping libs between roms
Saw a nice way of using readelf and it helped getting a lot of things sorted out.
Basically made a shell script and but it into my ~/bin folder and used that to manually check dependencies of the libraries. checked them and made sure they matched, flashed the phone and now its almost 100%!
I believe replacing libc.so from the CM6's /system/lib with the ads1 broke adb logcat - adb shell works, push/pull work fine. Gallery3d is now VERY smooth, Camera works fine now (tested snaps, etc..)
so, to recap lol..
STILL BROKEN:
-USB Mass Storage (going to check ramdisk)
-adb logcat/lolcat (cannot link executable since fixing EGL)
-Need to check GPS (noticed I've been checking with WiFI only)
WORKS:
-Phone/Data
-SMS/MMS
-WiFI/Bluetooth
-Camera/Video
-EGL smooth
-SD Internal mounting/browsing (SD-Ext also for APP2SD)
-CyanogenMod 6 settings
-ADWLauncher Settings
-Sharp Widgets (SMS/Email)
-Gapps (use the CM6 MDPI version)
-Slide out Keyboard (still going to look at the @, Sym and Camera button mappings)
-Keyboard Backlight (with light sensor adjusting)
-Rotation Sensor
I'll post a link to an updated version soon if anyone wants to test, just sorting out a few small things - progress is progress! Hopefully have USB mounting working.

test version cm6-z71 port beta1
Got the ROM somewhat stable, EGL seems to be working VERY smoothly (tracked back dependencies) and Camera/Video work (using CM6 camera apk, going to test with the Froyo/Sharp camera apk).
Link to test here - more information here.
Hope this is helpful to anyone testing.

Updated Ext3 ClockWorkMod - CyanogenMod 6.1.2 USB test.
Updated the ClockWorkMod Recovery from the builder site (generated using a dump of the stock.img)
Now it formats /sd-ext as Ext3 and not Ext4 (more info here). Also included the stock recovery image and tools.
Also got a test version of the CM6.1.2 port (more info here) - USB mass storage should work, no Google Apps (can be downloaded seperately - get CyanogenMod 6 MDPI version).
BUGS/TODO:
-Looking at a hardware keyboard "glitch" - Sym key brings up the "Select Input Method" menu (vs the Symbol menu). The @(AT) key also is unresponsive, using KeyTest.apk - shows as picking up #215 - but its not doing anything.
-Need to test the GPS
-Need to test Bluetooth pairing more
-Checking issue with init.d automounting sd-ext (running /system/etc/init.d/05mountsd works)
-If ADW Launcher stays stuck in Portrait mode (wont rotate), uncheck System Persistent from the ADW System options if its checked in and having problems.
DOWNLOADS:
CWM-EXT3-TEST (unpack to your SDCARD)
CM6.1.2-ADS1-B4a2 (flash with CWM, backup and data wipe prior to testing)

Notes on building CyanogenMod from source possibly..
Noticed when I got my initial zip back from the CM builder site, it had a device tree for the ads1. There isnt any "vendor" specific one matching, however I'm playing with one mocked from the Z71 tree (as they seem oddly similar).
I've already contacted Sharp about the sources, but not sure if I'm asking correctly . Maybe they'll respond. I was also asking about if they would have some kind of update.zip for the phone, theres a few other members that have "bricked" phones - a Sharp signed update.zip would work nicely for the stock recovery (unless theres another method)
However, just incase - testing this for a "proprietary mock up" to see if anything can work lol
-compared the extracted-files from the z71, removed the ones the ads1 did not have.
-ran a recursive diff between the bin, lib, etc folders between a Z71 cm6 rom (which I've based my test) and a system dump I made of the ADS1.
-added missing files for now (some might be for the Sharp UI Launcher)
-extract files works, copies the requested files off the phone (I've got a blend of a few ads1 froyo bits ontop of z71 cm6 atm)
-testing the local_manifest.xml to get it to work, experimenting
Still missing rild and libaudio sources (as well as some other ones I noticed in the Z71 tree) - going to experiment building a Froyo rom from source, using existing rild/audio libraries. Not entirely sure what I'm doing (as there is no real support for this device at all), just proceeding carefully and examining the surroundings as best as I can lol.

Z71-CM7.2.0 boots (needs work, but its something!)
Tested with a Z71 CM7 port that uses a similar kernel version to whats available for the ads1..
http://acebox.info/2012/07/sharp-fx-plus-ads1-cm7-test/

Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.

wisesoar said:
Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.
Click to expand...
Click to collapse
Hi, SuperOneClick 2.3.3 did the trick for me.
Unfortunately, dont have a backup of the stock system, The Clockworkmod custom recovery can backup the entire phone state to your sdcard, and you can restore the entire phone back to that exact state. Also if you can get a stock dump (all stock apps), let me know - I can probably try making a "flash to stock" cwm zip for it.
I'm not sure but think Sharp would have to release sources for the device? Or find sources that would be compatible with this device. Its pretty similar to a Commtiva Z71 as far as I can tell. I'd like to eventually try CM9 booting on this, so started with getting CM6/Froyo to work first - and found the Z71 worked with few modifications.
I found a Z71 Gingerbread 2.3.7 CM7.2 rom runs a similar 2.6.32.x kernel that boots (with modification) and somewhat works (no network, local/audio/touch/keyboard works). Would be nice to see something newer than froyo on this phone, so I'm posting whatever info on it while learning things in the process.
EDIT:
Not sure if Sharp will update the phone to Gingerbread, they havent released a update.zip for restoring the stock Froyo image yet. The device can definitely run Gingerbread, I'm playing with Z71 libs on a hybrid ROM that boots and (aside from phone/data/wifi/networking and screen timeout issue) runs rather quickly and smooth. I've been trying to contact Sharp about this device, but havent heard back yet. Guess I'm asking the wrong questions lol.

Kernel notes revisited
UPDATE: re-uploaded what was built with the modules for testing (previously only uploaded zImages)
Added some notes when I tried building the kernel incase anyone's interested - here. I've uploaded a test mock up of a device/vendor tree. The kernel config off the device as well as some test kernels (zImage only) built from the cm-kernel source. android-msm-2.6.35-unified and android-msm-2.6.33-ds
The device tree actually came from the ClockWorkMod builder site iirc, modded with some Z71 bits (to make the vendor side). Hopefully this helps anyone testing, as I havent had time to play with source building much (working on fixing bugs in the CM6 test port).

Updated ROMs (Froyo based)
DISCLAIMER: These are testing roms, they work pretty well for me - but always backup before flashing anything. Not responsible if sliding open the keyboard rips the fabric of time. WIth that out of the way...
I've uploaded 2 roms for the Sharp FX Plus (ADS1) - one is based off the stock 2.2.2 (Holo launcher, init,d, etc..) second rom is an updated version of the Z71 port I've been playing with (more on those here)
Downloads:
stock-based 2.2.2-acemod4
cm6.1.2-port-beta7
modified/slimmed google apps package

Found a user setting up official cyanogenmod support, thanks to rnorris. The github repo for the sharp fx plus ads1 is at.. more information here
https://github.com/rnorris97/sharp-ads1
I also set one up for testing unofficial device and vendor trees out for the ADS1
https://github.com/acebox/sharp_ads1_device_vendor_test
Good times for the little droid!!
Sent from my cm10-A500 using xda app-developers app

GPL Source?
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here

AmauryRR said:
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here
Click to expand...
Click to collapse
Any news? I'm interested in this phone.

deofavente said:
Any news? I'm interested in this phone.
Click to expand...
Click to collapse
Unfortunately none, I've been trying to get some information from either Sharp or PCD Phones on the modified kernel source and no dice. They were pointing to eachother, and being very helpful unfortunately.
It is a nice phone, and I would like to see what can be done from source vs porting roms. Definitely still some potential for the lil slider droid!
Hopefully something pops up, I've been moving around so if something pops up I'll dust mines off and get back to playing with it.

Rom Download Link ALL BROKEN....
i'm Try to download stock moded rom and cm6 rom.but download link all Broken...

all link broken please some upload sharp ads1 room and als its procedure to flash my phone have booting problem not starting sharp logo and restart i make the hardreset but still same problem.........

[Q] Coolpad 7268

Hi, everyone!
I got this pretty device o DX
Coolpad 7268
MSM8225Q 1.2GHz Quad-Core
GPU Adreno203
BUT! The system has tons of customizations and I cant even use the google play. So I decided to install a custom ROM on it.
But I cant find one.
I found a chinese website that explains some kind of rooting process... lots of chinese, so its a bit confusing and the softwares needed are also in chinese. For me its almost impossible to do. I heard that coolpad launched this model with an pure Android on it, for the american market. It will solve all my problems, But I can find the rom nowhere.
I think I need the recovery and the ROM for the process...
Somebody can please help me?

*update*
I tried lots and lots of rooting metods. Nothing can do it succesfully. eRoot, superOneClick... nothing can do it.

Root coolpad
I want to root my coolpad 7268 i / spice coolpad2 mi 496... Plz provide some information in this thread

Here is partition list :
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,relatime,size=4096k,mode=771,gid=1000 0 0
debugfs /mnt/debugfs debugfs rw,relatime,gid=512 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.3/by-num/p17 /system ext4 ro,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.3/by-num/p18 /cache ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p14 /persist ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p21 /data ext4 rw,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p22 /tombstones ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p25 /autobak ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I am unable to root this in any way - **** spice mobiles. Also, unable to take a dump of the recovery - keeps giving permission denied.

More Info
Drivers : https://drive.google.com/file/d/0ByoBGpu4hq-bT1cyWWNOeFhXYnc/edit?usp=sharing
To go into the stock recovery, keep both volume buttons pressed while powering on the phone. Else, from ADB, use "adb reboot-recovery" command. You will see the android with red excalamation. Press the Home button to get the screen like below. Long press the power button to select.
Stock Recovery :
There are four options.
First option is unknown. Second option is for installing zip from external SD card. Third option is format data partition. Fourth option is format cache.
Also, I got another option by keeping power up button pressed while inserting USB cable :
Update : On going to the ~download mode [image above], a new uninitialized disk drive of 3.61GB is there in Disk Managment and a Yulong CP7268 USB Storage Device is there in Device Manager with this Hardware ID - USBSTOR\DISK&VEN_YULONG&PROD_CP7268_STORAGE&REV_2.31\8&10C80774&0
Update 2 : Once in this pseudo download mode - I can see about ~20 odd partitions, some of them ext4, and some unknown file format. Parition 17 is the system partition and 18 is the recovery parition.
However, on Ubuntu, I am not able to modify the system partition by adding the su binary since it says owner is "user #2000". Also there is a su binary of 61.40 KB already in the xbin folder.

I
drivers of coolpad mi 496
Sent from my Spice Mi-496 using XDA Premium 4 mobile app

You will be happy to know that I have received this device too (45 minutes back)
Cost me Rs. 5450 only off Snapdeal
Custom recovery flashed and rooted. Root procedure and firmware ports coming soon
Have to work all night tonight so firmware ports will be done over the next couple of days.

Free Radical said:
You will be happy to know that I have received this device too (45 minutes back)
Custom recovery flashed. Root procedure and firmware ports coming soon
Cost me Rs. 5450 only off Snapdeal
Click to expand...
Click to collapse
I too finally hit on the same idea - flash cwm and then root - since by going into download mode I was not able to modify the files.
Thanks mate.
Edit - there is an autobak parition of about 1GB - is it possible to remove that and join with sdcard partition? since we already have shortage of sd card space.
Edit 2 : This is the lonk for the place I got drivers and other stuff - Yulong site : www.yulong.com/product/download/dow...nfoBO.downloadInfo.mobileType=7268#downListUL
I have made the newest ROM link into torrent since I was getting too little speeds as a webseed - http://burnbit.com/torrent/262996/20130629165410699_2_zip
The ROM is in CPB format - I dont know how to open it. If anyone wants to me to upload the same file to G drive - will do the same.

You are on the correct path mate.
The cwm recovery.cpb for coolpad 7268 is working for the Mi-496 proving that this is indeed a clone of the same device.
Don't flash the entire rom. Wait a while and I shall post the exact cpb files, flash tool and recovery.cpb I have used. There is also a mini-root.cpb which I will flash after taking a rom backup and report back here, Lets make a new all things root thread for the Mi-496

Free Radical said:
You are on the correct path mate.
The cwm recovery.cpb for coolpad 7268 is working for the Mi-496 proving that this is indeed a clone of the same device.
Don't flash the entire rom. Wait a while and I shall post the exact cpb files, flash tool and recovery.cpb I have used. There is also a mini-root.cpb which I will flash after taking a rom backup and report back here, Lets make a new all things root thread for the Mi-496
Click to expand...
Click to collapse
Thats fine with me. I too would like to know how to use the CPB files - the yulong software that I downloaded was showing up some weird chinese error and just fc'd on me.
This is how I took backup of the phone.
I took a 4GB or bigger USB drive (I used a 8GB drive). All the data on this drive will get deleted.
Then, install Minitool Partition Home Edition. Plug in the USB drive.
Next - switch off the phone. Keeping the volume up button pressed, plug in the microUSB cable to the phone. The phone will go into the pseudo download mode.
Now, you will get a Coolpad/Yulong 7268 disk drive in your device manager. Also, if you open disk managment, you will see a 3.61 GB partition which is "uninitiated" - I did not initialize it.
Next open Minitool Partition software - select the wizard option. Then you will see several disks Disk 1, Disk 2 and so on. The Coolpad USB disk will have lots of small partitions. Right click on Disk # (where # is the disk number) and right click - copy. A new Copy Wizard will come up and there, select the USB drive which you have inserted in USB port. Next, it will ask whether to adjust the partition size - select option 2 - keep the size same.
Now it will start copying, once finished, you have a soft copy of the phone. This may not be useful always, though.
TO make the img files, I booted into Ubuntu and then gave command
"dd if=/dev/sdc1 of=sdc1" Replace sdc with sdX where X is the USB drive mount. Then, replace 1 by 2 uptill 23. This created all imgs in home directory of Ubuntu - I moved them to a different location.
EDIT : For those who want a flip cover for temporary - buy a Karbon A6 flip cover or silicon cover - it will be a decent fit. You will need to cut out the holes for USB, headphone and speaker grille. Got one for INR 150 yesterday.

Spice Coolpad 2 MI-496 / 酷派 7268 Discussion Thread - xda-developers

coolpad -2
Oh ho! Thank god I am not alone with this device.
I also bought it from snapdeal via Rs.500 off coupon
but really a disappointed after use it for two days. Really amazing to find this thread and now will be use it with the full power.
By the way, is it have, sms bugs, I cannot receive any mail from banking alert.
Thank you guys for the awesome work. I am not really helpful at software side but will be tested as soon.

Probably due to the crap preloaded on the device. Shall post a cwm flashable rooted stock rom later. Trying to get MIUI to boot.
Not that bad a device considering HTC Desire 600 which has the same SoC sells for 26k which is almost 5 times the price you are getting this for.

Its good device @6000.... and working fine... all games are running on it...but getting hoy after playing games.. only thing i want is to root my phone .. to make it supercomputer smartphone..
Sent from my Spice Mi-496 using XDA Premium 4 mobile app

Hello @Free Radical i want drivers of spice mi 496 and want to know how to root this device
Sent from my Spice Mi-496 using XDA Premium 4 mobile app

sohanjaryal said:
Hello @Free Radical i want drivers of spice mi 496 and want to know how to root this device
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ADB and USB drivers - https://drive.google.com/file/d/0ByoBGpu4hq-bT1cyWWNOeFhXYnc/edit?usp=sharing

Thanks @vivek.krishnan
Sent from my Spice Mi-496 using XDA Premium 4 mobile app

Will be posting a cwm flashable stock based rom later today. Its currently uploading.
Prerooted, deodexed, zipaligned, debloated and optimized
Should be the first rom for this device and a backup if you mess up and want to go back to stock.
Already tested. Expect the download link near midnight today.

Thank you guys for the efforts.
Indeed very good device among the competitors.
Sent from my Spice Mi-496 using xda app-developers app

Thanks @Free Radical
Sent from my Spice Mi-496 using XDA Premium 4 mobile app

[Q] [HELP] Running Debian on top and Android chrooted

Hello!
I'm trying to run debian on P500, but not chrooted below android. I want the reverse.
I followed this guide strictly:
http://whiteboard.ping.se/Android/Debian
Everything went well, no apparent errors. The only trouble is: the system doesn't boot I can't explain why. I'll write exactly what I did, so maybe you can help me to find what I'm doing wrong.
## Partitioning the SD card
I partitioned it in 4 partitions using fdisk, and created filesystems with mkfs:
sdb1 - ~2GB vfat (for android)
sdb2 - ~1GB ext4 (for /data - I'll mount /data here after everything is working)
sdb3 - ~12GB ext4 (for debian root filesystem)
sdb4 - ~1GB swap area
## Creating the new initramfs
I used cm-11-RC7 as base. I extracted the boot.img using unmkbootimg, a tool provided by the author of the guide, which gave me a initramfs.cpio.gz file and a zImage file.
I did exactly as described in the guide, but using busybox-armv6l (downloaded from http://busybox.net/downloads/binaries/latest/) and changing /dev/mmcblk1p2 to /dev/mmcblk0p3 (this is how my P500 called my sdb3 partition) in the /init file.
Everything went well, and I got a boot.img with busybox and the modified /init file.
## Creating the Debian filesystem
I did exactly as described in the guide, changing only the debian version (--foreign sid) and the mirror (from ftp.se to ftp.br).
Everything ok, I can use debian at this point, but chrooted below android.
## Creating the new Android root file system
I extracted the original initramfs to /android on debian filesystem and created the log/ subdirectory, as described in the guide.
## Finishing scripts
I removed the /etc/init/ folder and all files in /dev of the debian root filesystem; and created the files /etc/init, /etc/init.stage2 and /etc/rc.local as described in the guide.
## Installing the boot.img
Since I can't put my phone in fastboot mode (home+power has no effect, and I can't use LGMDP because I'm running linux) I tried two ways:
- Using the Flash Image GUI (http://forum.xda-developers.com/showthread.php?t=2086361)
This works, I got a "Success" output after flashing the modified boot.img.
- Changing the original boot.img file by the modified boot.img in the rom zip
This works, the rom is installed succesfully.
## Using it
That's where I can't explain. After flashing the modified boot.img (or modified zip rom) I reboot the phone, and got this bootloop:
LG screen > screen turns off > hardware buttons light turns off > LG screen
... and so on, forever.
What am I doing wrong?
Thanks a lot!
------------------------------------------
I could not make this work yet, but I would like to say thanks to:
Google (for android)
CyanogenMod (for the great system they provide)
AndroidARMv6 team and all developers of our beloved P500 (for making dreams possible )
Mikael Q Kuisma (for the great guide and tools - http://whiteboard.ping.se/Android/Debian)
joeykrim (for the Flash Image GUI - http://forum.xda-developers.com/showthread.php?t=2086361)

Possible problems
I think that the possible problems would be:
- Wrong busybox version
I tried with the busybox extarcted from the ROM (/system/xbin). Same result.
- ROM incompatibility
I tried the same procedure using as base CM11-RC7, Omni-4.4.3-NightlyBuild, CM10.2.0, CM10.1.6, CM9.2.3, AOKP-4.0-Beta6, CM7 and the original rom. Nothing.
I can't see the reason for this not to work...