Related
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.
[DEV] data2"XYZ" general filesystem discussion (Updated Dec 20 - Benchmarking)
I will rewrite this posting soon. As for now please check the scheduler Benchmark:
http://forum.xda-developers.com/showpost.php?p=9959265&postcount=257
================================================================
data2btrfs (this is DEV status so don't ask how to install - there is (little) linux expirience required)
Update about btrfs dec 15: Still testing btrfs and im REALLY amazed. Battery life has no difference to ext4 but performance is FAR better then ext4. I do still get lags in some cases (like fast! downloads) but this is simply a hardware issue which can not be addressed. Im using a class 2 sd only and i dont think that this can get ANY better. I think btrfs should run like HELL on a class 6+ card.
Update dec 14: Atm i'm using btrfs with "ssd_spread" (for ssd harddisk with older controllers. The controllers in SD should suck compared to some modern SSD so this will effect SD-Cards even more than "ssd" optimization (more info). And im amazed. It is even more smooth than nilfs (maybe less cpu) and so far the smoothest expirence i had with data2sd/data2ext. Even compared to EXT4 without journaling.
Why btrfs?
1. Btrfs is "copy-on-write" filesystem and i think that "copy-on-write" or logbased (like nilfs) will be the future.
2. Btrfs and nilfs are both better for "old" or "cheap" SSD-Drives because they are optimized for it. While this will decrease the performance of a modern SSD-Harddisk (since they are getting better and better in emulating a rotating device like a classic HD) it will INCREASE the general performance on ssd like an sd-card because their controllers is a lot worse than one of a state-of-the art SSD-Harddisk. So these optimization.
3. MeGoo (a linux made for smartphones) already has chosen it as default even though its still beta and i think they have some good reasons for this.
4. Btrfs has the same (and theoratically it should be even less - tiny) battery consumption. Other then nilfs wich had horrible battery (over 1%/h on its own even when phone was idle). Thats why i moved to btrfs from nilfs.
EDIT: Removed something really stupid xD
Safety concerns about data2btrfs
script: Considering the script i addressed ALL safety conserns that there are at present. This is based on the findings of the SGS devs and mounting directly on /data is even more save then cyanogen's app2sd+ (at least for the desire which unmounts /data - SGS doesn't). Only dalvik-cache is symlinked and a data corruption there is unimportant and can be helped by a simple wipe of the cache. So no concerns about this. (But note: the script is still "young" and there might be still errors - thats why i also don't provide a zip for ext4 yet)
btrfs is indeed still in an experimental state. But speaking FOR MYSELF ONLY (everyone should estimate this on its own) i don't have any concerns. The reasons are:
-experimental state is almost over and i doubt that there are any major bugs present.
-many Linux already use it and its default for MeGoo
-I have backups for all sensible data on my computer (like license keys - this can be lost if you backup already corrupted data with titanium/etc)
How to use it
(experienced linux users who know what they do ONLY)
- (recommended for ~ +20% speed) Delete your old ext partition create a new primary partition if it is not aligned yet. Gparted has a "align to mb" option wich makes alignement increadibly easy. Since 1024kb alignement is enough for sd there isn't anything else you need to care about.
- Make a btrfs partition with your favorite linux distribution (im still a ubuntu noob ) with btrfs utils.
- Make sure you flash a Rom that doesn't need sd-ext for installation (check the META-INF/../update-script for "copy_package XYZ SD-EXT:XYZ" - delete or format sd-ext there isn't a problem you will get an error (like on leedroid) on install but this doesn't matter)
-make sure you have Kernel with btrfs support (see below for this)
Kernels with btrfs support (SENSE ONLY for now)
-NeoPhyTe.x360 's (ext2, ext3, ext4, reiserfs, xfs, jfs, btrfs, nilfs2)
-Coutts99 Kernels (chose the btrfs-test-kernel ofc ;-) )
Known Issues
no btrfs support in recovery this means:
-no backup of the sd-ext partition (it isn't ext anymore ;-) )
-wont work with ROMs that need sd-ext for installation (some HD roms)
Thanks
- cyanogen who made app2sd+ in the first place.
- sibere and ownhere who started all the data2sd.
- supercurio and Unhelpful of SGS' Voodoolagfix (#Project-Voodoo on freenode) for their helpfull script tipps.
- Coutts99 and Neophyte for their Kernels.
- woti23 for all those test's in this thread.
- All devs of XDA in generall for all this nice stuff that is done here
Further Plans for the script
- Changing scheduler settings depending on results in the btrfs thread to get the last out of your SD while assuring safety (thanks woti23 for all the testing).
- Trying to add support to delete the ext partition and create it new with an 1024k alignement (~ +20% more speed)
- Mounting /app-cache to /cache or internal data partition (8 MB more RAM since its mounted on RAM)
- Changes for the mount options of the internal YAFFS2 Partition to optimize the speed of the "dalvik-cache" (have to look into YAFFS2 what can be done)
- Adding some lines of code to clear up any present symlinks on first boot to make it ROM upgrade compatible
- Adding e2fsck with check on every boot (script is quick edit of my script for btrfs - no e2fsck yet)
- Other changes based on the results in this or other threads about data2ext/data2sd
- Remove the errors i made ^^
---------------------------------------------------------------------------------------
Remark: i moved the data2ext4 script to my other script and set the dev tag again. I also added UBIFS discussion to the title. I also removed the nilfs utils and the data2ext4. The data2ext script can be found here. If someone wants to test nilfs you can PM me (but battery SUCKS incredibly )
---------------------------------------------------------------------------------------
Changelog: :
(dec 15): One minor change in assigning a variable. Doesn't change ANYTHING in actual behavior but code it's more "logical" (assigning the output of "busybox ls" to the variable instead of the command ^^ d'oh)
(dec 15) Fixed a stupid error that could lead to exit code (2) ....... and uploaded the proper file for btrfs (not the ext one). Sorry.... -.-
(dec 16) Fixed the fix ....
(dec 16) the scripts create now the folder it needs if it is not present yet (sorry i also forgot this in required ... was only there in the ext4 thread ^^)
=========================================================================
DISCLAIMER: BTRFS is still under development and thus an EXPERIMENTAL filesystem. Please refer to the btrfs wiki for more information.
melethron said:
Quick Info: NILFS2 - data2nilf2 will be much faster then data2ext and won't have Lags.
Long info:
After some thought's how to make things better for data2ext i started to think about how a flash based memory actually works.
Your Sd-card isn't a HDD (as you may have noticed ^^). It is actually a NAND based flash memory wich is divided into pages of 2-4kb and they are grouped to blocks of 128kb-512kb (!). But you will never see these. And you cant never change these (mkfs -b as much as you like ^^). This is done in hardware by a controller. All you will see is - you may call it an emulation - the LBA provided by the "flash translation Layer" (FTL). While the FTL can read/and write per page (2-4kb) it can't overwrite it. It needs to delete the data first AND THIS CAN ONLY BE DONE PER BLOCK !!! (Thats why read mb/s is higher then write mb/s).
What this means. Your filessystem should be aligned on the Blocks and should also avoid the need to erase blocks.
So forget every filesystem that my rock on your HDD (it may prefer e rewriteble sector if it's close f/e. If you "emulate" a filesystem through the controller it should respect the "true nature" of the hardware. A logbased filesystem would be far better since it will more likely take advantage of erased blocks. Also you may want that the blocks of the FS fit on the blocks of the NAND (alignement - but this mathes for every fs).
... Well long story short ... you need NILFS2
Links
http://www.usenix.org/event/lsf08/tech/shin_SSD.pdf
and this:
http://forum.xda-developers.com/showpost.php?p=7647224&postcount=21
(For germans: http://www.hardwareluxx.de/community/f227/os-optimierungen-fuer-flash-ssds-543445.html#post10373042)
Btw: In the XDA thread linked use it for the internal sd in samsung galaxy S for a LAGFIX. Wasn't lag the reason data2ext sucks atm.
My 2nd partition would already use this by now but there are 2 things needed:
-Kernel Support
-mount binary
Im to noobish to provide both ... so .... help ... anyone .... pls ?!
Click to expand...
Click to collapse
Ill try and sort a kernel
http://mirror.couttstech.com/android/bravo/kernel/nilfs_test_kernel.zip
Usual [email protected] kernel with NILFS built-in
As for mount binary. busybox mount might work. I've just been playing with aufs and normal mount worked for that.
coutts99 said:
Ill try and sort a kernel
Click to expand...
Click to collapse
NICE! looks far more promissing than btrfs (at least for flash memory)
melethron said:
NICE! looks far more promissing than btrfs (at least for flash memory)
Click to expand...
Click to collapse
I was going to have a play with this but forgot to bring home my spare sd card and my sd card adaptor
Sent from my HTC Desire using XDA App
Another One Nilfs2+Reiserfs
http://neophyte.vipme.com/ftp/_Extras/NeoPhyTe-2.6.32.26_Nilfs2_Reiserfs_v70.zip
coutts99 said:
http://mirror.couttstech.com/android/bravo/kernel/nilfs_test_kernel.zip
Usual [email protected] kernel with NILFS built-in
As for mount binary. busybox mount might work. I've just been playing with aufs and normal mount worked for that.
Click to expand...
Click to collapse
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
melethron said:
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
Click to expand...
Click to collapse
Nilfs2
Sent from my HTC Desire using XDA App
NeoPhyTe.x360 said:
Another One Nilfs2+Reiserfs
http://neophyte.vipme.com/ftp/_Extras/NeoPhyTe-2.6.32.26_Nilfs2_Reiserfs_v70.zip
Click to expand...
Click to collapse
Neo, have you got mount binary cross compiled for arm?
Sent from my HTC Desire using XDA App
coutts99 said:
Neo, have you got mount binary cross compiled for arm?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Not, we need this, but I havent got source of this.
need mkfs.reiserfs, and mkfs.nilfs2
http://forum.samdroid.net/f55/i-o-p...e-your-spica-ext2-2218/index44.html#post44349
NeoPhyTe.x360 said:
Not, we need this, but I havent got source of this.
need mkfs.reiserfs, and nilfs2
Click to expand...
Click to collapse
OK, if no one makes any progress tonight ill get on this tomorrow.
Thanks Neo!
Sent from my HTC Desire using XDA App
NeoPhyTe.x360 said:
http://forum.samdroid.net/f55/i-o-p...e-your-spica-ext2-2218/index44.html#post44349
Click to expand...
Click to collapse
Ah good link!
Sent from my HTC Desire using XDA App
I would just like to mention here that I made a special note about bloc alignment on sd card on my thread. I provided a link for that and FAT32 can be aligned to the actual bloc 128kb/512kb size of an sd/usb flash memory. This is the reason why I use 2 fat32 (aligned) partitons.
Sent from my HTC Desire using XDA App
melethron said:
Thanks x 3 times.
About binary
"Mount -t auto" didn't work with nilfs2 with ubuntu. "Mount -t nilfs2" calls mount.nilfs2 i think.
EDIT: Did you add nilfs or nilfs2?
Click to expand...
Click to collapse
ubuntu:
you maybe want to install nilfs2-tools first
then it mounts without -t option
am i the only one who is a little scared about this:
#> mount /dev/sdb1 /mnt/nilfs2
mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
sibere said:
I would just like to mention here that I made a special note about bloc alignment on sd card on my thread. I provided a link for that and FAT32 can be aligned to the actual bloc 128kb/512kb size of an sd/usb flash memory. This is thefbreason why I use 2 fat32 (aligned) partitons.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I still don't get the point using FAT for the 2nd partition. Also did you see what ownhere posted here:
Why create a small loopback device? the reason is item 3. But I found some bug with this case, any data write to loopback device need twice kernel IO command, one virtual one real, so the cpu usage will be high
Click to expand...
Click to collapse
About the 512kb. Are sure this is the max size "erase block" size for microsd?
melethron said:
I still don't get the point using FAT for the 2nd partition. Also did you see what ownhere posted here:
About the 512kb. Are sure this is the max size "erase block" size for microsd?
Click to expand...
Click to collapse
I have used loop so far because I have run some I/O test on my phone (not quadrant) and I always had a better result with loop than with direct format.
ownhere post is great but he's not always 100% right. For instance, the fact that ext2 partition when mounted on /data is not unmounted properly by the system in wrong. You can read my post here http://forum.xda-developers.com/showpost.php?p=9704670&postcount=9 to see the tests I did. I do confirm that the FS is unmounted by the system on shutdown.
About ext4 4K block size, you can do the same with EXT2 (my actual bloc size is 4096).
But I'm reading with great interest the thread about alternatives FS for NAND data storage. The erase block size is different for different devices and manufacturers. But at least if you align blocks to a multiple of 128kb, you will get a noticeable improvement in I/O than no alignment at all.
woti23 said:
ubuntu:
you maybe want to install nilfs2-tools first
then it mounts without -t option
am i the only one who is a little scared about this:
#> mount /dev/sdb1 /mnt/nilfs2
mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
Click to expand...
Click to collapse
y i have nilfs2-tools. I only meant that -t auto doesn't work. -t nilfs2 works fine.
I also got scared by the warning and googled the warning: http://www.spinics.net/lists/linux-nilfs/msg00595.html
Quoting a dev:
NILFS2 is almost stable. We have a record of nine months operation on in-house samba servers and a webDAV server.
> There is still still warning when mounting verbosely though:
> mount.nilfs2: WARNING! - The NILFS on-disk format may change at any time.
> mount.nilfs2: WARNING! - Do not place critical data on a NILFS filesystem.
>
> As per the first message, Is the on disk format expected to change any
> time soon?
Well, I don't want to change disk format in a way that breaks
compatibility. I'm considering to remove the above message at the
next utility release.
Click to expand...
Click to collapse
Reading this im willing to use it.
sibere said:
ownhere post is great but he's not always 100% right. For instance, the fact that ext2 partition when mounted on /data is not unmounted properly by the system in wrong. You can read my post here http://forum.xda-developers.com/showpost.php?p=9704670&postcount=9 to see the tests I did. I do confirm that the FS is unmounted by the system on shutdown.
Click to expand...
Click to collapse
ownhere got this (wrong) information from me don't blame him...
You proofed me wrong on this and i admit that i was only guessing ....
After reading cyanogens post i thought that he tried to mount on /data before or tried to create an init.d/rc0.d to make a clean unmount. I didn't dare to think that any good dev would just say "... give a **** about a proper umount and use a journling fs". I mean wtf ....
melethron said:
ownhere got this (wrong) information from me don't blame him...
You proofed me wrong on this and i admit that i was only guessing ....
After reading cyanogens post i thought that he tried to mount on /data before or tried to create an init.d/rc0.d to make a clean unmount. I didn't dare to think that any good dev would just say "... give a **** about a proper umount and use a journling fs". I mean wtf ....
Click to expand...
Click to collapse
Do you mean that you/he/they stated without trying ?
I never take a guess for granted
I assume no liability for any damage to your phone!
You can use my complete rom or parts of it to make your own rom. Only post a small thanks on your owm thread.
Big thanks to: iaio72, spear1403, tgzw, Quarx, Simondo, ein1002, santimanuel, epsylon3 and ...
Language support for final 4.0 --> da, de, el, en, es, fi, fr, hr, hu, id, it, nb, nl, pl, pt, pt-BR, sv, th, ti, vi, zh_CH, zh_TW + arabic* and ru*
MS2Ginger 4.0
- based on 4.5.2-109-DHT-25 - Android 2.3.6 blur lite rom
- support for Defy, Defy+, Milestone 2, Bravo
- MS2Ginger4 can used as 2nd-system (tested on GB kernel only) !! system image file have to be >= 350 MB
- multibootmanger app by royale1223
- new bootmenu 1.1.8, CWM 5.0.5/6, multiboot big thanks to m11kkaa
- 2 way to boot the rom: normal and via 2nd-init (default)
- new reboot option form cm7.2 --> trigger: all keys at the same time vol- , vol+ , power (only tested on Defy)
- disabled blurhome rotation
- button backlight can set from 10-100 % via build.prop
- mmcfix from CM7
- CPU settings default safe 30/300 38/600 {48/800} 58/1000
- Camera will work on SOC and Bayer camera (green* and red)
- better camera support for bayer camera
- new 720p record* and play (Milestone 2 - Android 2.3.6 files)
- 720p record in m4v (h264 can be enabled via build.prop)
- Milestone 2 froyo camara app for SOC camera (fixed green strips)
- BlurHome from Milestone 2 - 2.3.6 (no widget updating bug)
- Battery min. 2-5 mA/h
- no wifi, apn, vpn bugs
- wifi channels 12, 13, 14 enabled
- bootmenu + cwm (vsel4/clk4 added) "did not work for SOC camera with greenbreadMOD"
- bootmenu with Stable, Custom, Stock-Recovery
- call record libs
- init.d support
- zipalign at boot
- ramscript
- backlight button fix for Defy with bayer camera (can removed via optional patch)
- deepsleep support
- max 10 finger multitouch
- support for farsi-arabic, hebrew (thanks to MMarv)
- CyanogenMod-settings not finished (alpha) - sorry, will try to fix it if i have more time.
(* via greenbreadmod for MS2Ginger4.0 and if you never flashed a Android 2.3.6 full sbf with bl7)
(* 720p record only for Bayer camera Defy and Milestone 2)
Download: ROM, BlurApps, Greenbread: (MS2Ginger4.0.zip, BlurApps-MS2Ginger4.zip,Milestone2patchMS2Ginger4.0withbaseband.zip )
Mirror 1 (google)
Mirror 2 (Dev-Host)
More information for BlurApps --> LINK
Soft-sim-unlock for MS2Ginger 4.0
based on Dabb guide: http://forum.xda-developers.com/showthread.php?t=1447950
Install View attachment 1129769 via CWM.
If you like MS2Ginger feel free to donate! Donations will be used to purchase a Defy with SOC camera (green lens)
Bugs and problems Reporting: http://code.google.com/p/ms2ginger/issues/list?can=1&q
- wifi bug like all 2.3.6 Motorola roms http://forum.xda-developers.com/showthread.php?t=1502817
(fixed, disable unlimited lease time for IP adress on your rooter)
Timeline:
19.06.12 - MS2Ginger 4.0 released
05.02.12 - MS2Ginger 3.0 released
Patch and updates for current release
none for MS2Ginger 4.0
HOW to INSTALL:
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Put "Milestone2patchMS2Ginger4.0withbaseband.zip" to the root of your sdcard
Put "Milestone2-GB-kernel-update.zip*" to the root of your sdcard (only if you have a froyo kernel)
-------------------------------------------------------
Root your Milestone 2 and Install BOOTMENU - CWM for Milestone 2
REBOOT
run 2nd-init (voldown on blue LED)
Go to "Recovery"
Go to "Latest or Stable or Custom Recovery"
"wipe data and cache"
Go to "Backup and Restore"
Go to "Advance Restore"
Select "MS2Ginger4.0"
"restore system"
Go to "install zip from sdcard"
select and install "Milestone2patchMS2Ginger4.0withbaseband.zip"
"Install "Milestone2-GB-kernel-update.zip" via install zip" (only if you have froyo kernel)
reboot
Booting up can take a while, max is about 10 minutes.
Team:
- walter79
- spear1403 (theming)
- santiemanuel
- Defy red lens tests spear1403
- Defy greens lens tests luciferps and Cristi_10
- Defy plus tests Dollo73 and free2live
- Milestone 2 tests Carolinux and Motodoido
Translation Team: (each language max. 4 person) View attachment 806172
Brazillian Portuguese: pupiloalpha , Cassinander , filipeazev
Bulgarian Auris 1.6 vvt-i
Farsi: MMarv
Hungarian: szabof1 , balika01
Polish: yackoo , szacuken , Antszej
Serbian: atomskasarma
Spanish espaciosalter20
Spanish-Argentina YaPeL
walter79 said:
Welcome.
The idea:
Defy is running Milestone 2 Android 2.2.2 ROMs. (DACH retail based)
So maybe we could make a working Gingerbread for Milestone 2.
- Defy has rooted only Android 2.3.4 /system nandroid-backup http://forum.xda-developers.com/showpost.php?p=14793844&postcount=8
- it is also possible to run 2nd-init on milestone 2
- read this (Defy 2nd-int + froyo kernel + Gingerbread-system working) http://forum.xda-developers.com/showthread.php?t=1130656
- i think it could be possible to get gingerbread working on milestone 2
- basband should be change with original milestone 2 files
- /lib/hw/ from milestone 2 needed
- kernel from milestone 2
- fix for camera
Whats your opinion?
Click to expand...
Click to collapse
I'm sorry to kill your optimism, but we are unable to flash onto /system for now. Big files at least..
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
walter79 said:
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
Click to expand...
Click to collapse
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
But nandroid backup works, or?
Mikevhl said:
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
Click to expand...
Click to collapse
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
dangpzanco said:
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
Click to expand...
Click to collapse
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
r2beta0 said:
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
Click to expand...
Click to collapse
Lol, I think it's a lucky shot finding this...
Sent from my Milestone 2 XDA App
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
Did not work.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
r2beta0 said:
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
Click to expand...
Click to collapse
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
dangpzanco said:
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Not yet, still working on it on my free time. Unfortunately 'free time' is a scarce resource
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
dangpzanco said:
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
Click to expand...
Click to collapse
First attempt failed. I had some problems formatting /system partition. The only way I could get it to format was through Recovery Menu. Maybe the problem is reformatting the system. The command mount("MTD", "system", "/system") also doesn't work. I'm starting to think that Motorola messed with the file system. Will try again using delete_recursive instead of format.
There is any d2 / d2g rom based on GB?
With all the problems developers were facing lately, I guess motorola add the same "weird" protections in m2 2.2 to GB d2 rom
It's very hard to make a custom ROM with all these protections and without knowing what happens when phone tries to boot. All we get is the damned M logo and no info at all. Without some output from the phone everything we can do is guessing.
I was reading that new fission roms based on GB (for d2), were facing the "motorola logo" stuck problem. That´s why the developer gave up.
But, like you say, there is no way to know if it´s the same problem.
I have no knowledge at all on android platform. I´d stuck on winmo 6.
If you need some testing, I can try, there is nothing more I can offer
Second attempt failed. It may have nothing to do with format or system file. I'm really clueless Jut the M logo again. Maybe the /system protection checks for some date/time on some random file? Will reflash with RSD and 'touch' everything in /system to see if the damned thing still boots.
Did you compare the hash of apex files to the moto original files?
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.........
A lot of users around here like to try out different kinds of ROMs on their devices. It is advisable though, to always keep a backup of a stable (usually stock) ROM on your SD card. The truth is that it is very time-consuming to have to backup and restore ROMs in recovery just to boot to a new ROM for a few hours, run some tests and then go back to the stable one. It is also true that AOSP based ROMs may not support special features of certain devices (e.g. 3D displays and cameras or FM tuners), so a stock-based ROM must always be handy in case you need those features. This is why Dual-Boot can be useful. It allows people to switch between two ROMs almost as quickly as a simple reboot.
I have followed these guidelines to create Dual-Boot on four different phones and I suppose that the same method can be used for any phone.
The idea is to keep any stable ROM as primary and install an AOSP-based JB (4.1) or newer ROM on the SD-card.
WARNING: If you are not familiar with the way Android works, you can easily brick your device by flashing the wrong partition. I won't assume responsibility if you do and I can't offer support since I cannot possibly own all the devices this guide may be applicable to. If you don't fully understand these guidelines, then stay away. If you still want to try, remember, you are on your own! Questions, suggestions and remarks should be properly posted in the thread for everyone to read. Take no ofense, I will not reply to PMs.
Click to expand...
Click to collapse
Prerequisites:
A) You need to fully unlock your device (Root, Bootloader unlock, S-Off or whatever else your device has that may prevent you from flashing partitions).
B) You need to find a suitable way to unpack and repack your boot.img. Different ways are available for different devices. I can only suggest those that I have tested for mine.
C) You need to have a working updated busybox.
D) A ROM zip file to install onto the SD card. This ROM must NOT be using Aroma Installer.
Steps:
1. First you need to figure out the locations and sizes of your system, data, cache and boot partitions (you can use Partition Table from Play Store).
2. Create three additional partitions at the end of your SD card with the sizes you found. You can either use AParted on your phone or MiniTool and a card adapter on your PC. The partitions must be all primary and formatted to ext4.
(HINT1: If you use AParted, you probably want go hit "Decline" on the agreement, otherwise it will install adware junk)
(HINT2: You may want to create a larger Data partition, so that you have more space to install apps)
(HINT3: If you can convert ZIPs using DBootRecovery from 2nd post, then do it and jump to step 7)
3. Now you have to unzip the ROM file you want to install, browse to /META-INF/com/google/android, find the updater-script and edit all lines that contain mmcblk0ps (where s is your internal system partition number) to mmcblk1p2 (your new SD-system partition). Some ROM zips (like MIUI) also install stuff to the data partition, so be careful and change the respective lines from mmcblk1pd (where d is the number of your internal data partition) to mmcblk1p3.
4. You also need to unpack the boot.img, find the fstab.nick in the ramdisk (nick is the nickname of your device) and edit the sysyem, data and cache mountpoints to /dev/block/mmcblk1p2, 3 and 4 accordingly.
In some ROMs, the fstab. file plays no important role. In this case you must search inside files ending in .rc in the RamDisk for lines that have to do with the system, data and cache partitions. For example, in HTC One SV stock-based ROMs, you must change [email protected] with /dev/block/mmcblk1p2. Data and cache also follow this pattern.
5. If you need to flash GApps, then you must also modify that updater-script by changing the line run_program("/sbin/busybox","mount","/system"); into mount("ext4","EMMC","/dev/block/mmcblk1p2","/system");
Any other add-on you may want to flash must first be edited as described in steps 4 & 5.
6. Pack and zip everything back and reboot to recovery.
7. Make a backup of your current ROM and flash your modified zip(s).
When you reboot, your device should load your secondary ROM.
To switch back to the primary ROM you need to reflash your primary kernel (from the backup you took). Use dd if=path/backup.boot.img of=/dev/block/mmcblk0pb (where b is your boot partition) and reboot.
To boot back to your secondary ROM, just use the above command to flash the boot.img extracted from your modified ROM.zip. This process can now be done automatically using SwitchROM.sh from 2nd post
If you don't like scripts or terminal commands, another way to flash your boot images is Flashify.
If for any reason your 2nd ROM doesn't boot (e.g you haven't found the right method to pack your boot.img), you can advanced-restore just your primary boot.img from your backup in recovery. This way you'll be able to boot back to your primary ROM which is otherwise unaffected by the procedure.
In order to complete step 4, these links may be a good start:
i) These tools by Modding.MyMind work on my HTC.
ii) These ones by michfood work on my HTC but only unpack my LG boot.img
iii) and this one by berni987654321 packs my LG boot.img (download dualboot_tool.zip at the end of 1st post).
Don't forget to hit "Thanks" on those pages too.
Important:
- Be extra careful if your secondary ROM supports OTA updates which are applied through recovery. Only download but NEVER apply them before you tweak the zips as described above. Otherwise they will overwrite your primary ROM!
- Actually, every zip you want to flash to your secondary ROM must be edited first, otherwise it will flash to your primary.
- You can only use your regular custom recovery to flash edited zips to your secondary partitions. You can't use it to backup, restore or wipe them. Those functions will only affect the primary ROM. For this reason, I have created the DBoot Recovery script. For more info, read on to the second post.
Special thanks to @berni987654321 from whom I learned almost everything there is to know about Dual-Boot. This guide is based on his work.
DBoot Recovery Tools
Here are the scripts I promised.
Initial Setup
1. In order to use the scripts, you need to have partitioned your SD card the way I described in the previous post.
2. Download the zip from the link at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
3. Install Script Manager from Play Store
4. Install (or update) Busybox
Inside the Dual Boot folder you will find two scripts and some more folders. Please do not change anything there. Just use ScriptManager to run the scripts. Their usage is explained below.
DBootRecovery.sh
Purpose: Manage your secondary ROM.
This tool is designed to run on the primary ROM, but some major functions are also available on the secondary.
1st run
Open ScriptManager, browse to the DualBoot folder and tap on DBootRecovery.sh. At the top of the screen that follows, select the first two icons (Fav and SU). I also prefer to enable the Wklock icon (it has to be enabled in settings first). Then you can hit Run.
When you run the script for the first time, it will try to read the /proc/emmc file (if it exists on your system) in order to determine your normal partitions. If the file exists, it will present you the data, so you can accept or reject them. If it doesn't exist, it will ask you to enter your partition numbers manually. In both cases, the data will be exported to a new file (part.ini) in the DualBoot folder and you will not be asked again.
The main screen
The top two lines are important. After a selection you made completes and returns to the main screen, the first two lines will inform you of its success or if any errors occurred.
Main menu
1. Backup ROM2
This option will create a backup of your secondary ROM. It will actually create images of your secondary system (mmcblk1p2) and data (mmcblk1p3) partitions. Those two will be saved in the backup folder inside DualBoot. Be careful, a new backup will overwrite the old one. If you want to keep an old backup, make sure you move or rename it.
2. Restore ROM2
This option will flash the images you took with option 1 back to their respective secondary partitions. It will only be available while you are on your primary ROM (you don't really expect to flash a partition while it's being used).
3. Convert ZIPs
This tool wil automatically do all the edits described in the 1st post to all ZIPs it can find in the OriginalZIPs folder. It is based on @Modding.MyMind's binaries [point (i) in 1st post]. If they don't work for you, you will see an error message. The original ZIPs will be kept intact and the edited ones will be created in the DBootZIPs folder. It is not certain that it will function equally well on all devices/ROMs, so before you flash your edited ZIPs, please check that they were edited correctly. This tool will NOT flash ZIPs. It will only convert them, so they can be flashed as secondary ROMs using your regular custom recovery. The tool will also put boot2.img in the img folder for use with the Switch ROM function. If you are on your primary ROM, it will also backup your current boot partition into a boot1.img in the img folder.
4. Advanced options
After selecting this, you will be taken to another menu where you can find more options. Most of them are not available while on your secondary ROM.
9. Switch ROM
This does the same as the individual SwitchROM.sh script. Read below.
0. Exit
I have decided not to explain this option.
Advanced menu
1. Wipe System2
2. Wipe Data2
3. Wipe Cache2
4. Wipe Dalvik2
These options just do to the secondary ROM what their name implies. They will only be available while on your primary ROM. If you want to factory-reset your secondary ROM, just wipe your Data2 and Cache2. When you flash new addons, it is advised to wipe Cache2 and Dalvik2. You can also wipe everything if you want to clean-install a completely new ROM.
5. Update binaries
Whenever Modding.MyMind updates his binaries, download and put them in your DualBoot/bin folder. Then, use this option to update existing binaries in your /system/bin folder.
0. Main Menu
Returns to the previous menu
SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the DualBoot/img folder. These files will be automatically generated when you convert a ROM zip (using option 3). Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Fav and SU) and Run. It will automatically detect the current ROM, flash the boot image of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
In previous versions of this script for the LG Optimus 3D, I had included a reboot command. The reason why I am not using it any more is that the device would turn off abruptly and not "shutdown" the way it does when selecting it from the Power-Menu.
DOWNLOAD:
Get the latest version from here.
TROUBLESHOOTING:
If, while converting a zip, the script gives you an error that yourboot.img is incompatible, then either you have an encrypted header, or you have a truly incompatible boot.img! In any case, visit [Without PC] Unpack, Edit, Repack boot.img to read how to deal with encrypted headers, or to download the latest boot_manipulation.zip
Changelog:
13.03.2014 Initial upload of ZipEditor and SwitchROM.
17.03.2014 Updated ZipEditor to support the conversion of HTC-OneSV ROMs (AOSP and Stock based). Thanks to Modding.MyMind for assisting.
23.03.2014 First upload of DBootRecovery. The ZipEditor is now contained in it. If you are wondering about the v3.0, previous versions were device specific (only for the LG-P920). This is the first one for use on any Android.
21.06.2014 Version 3.1: Added support for the new LG P920 KitKat ROM. Fixed a bug where Dalvik2 cache would not be properly wiped. Changed a few minor details for better script operation.
Very insightful bro. Thanks for the share. I will definitely try this out. This may be my motivation to work on my Port Rom again. Was getting tired of wiping, flashing, wiping, flashing.... Was a nuisance and I unfortunately only have one device for my current model. This will be really useful to me in the future. Huge thanks again for letting me know about this thread.
Sent from my C525c using Tapatalk
Hey, getting ready to do this now with a 2gig. Using it as a test run lol. Anyways, to confirm, you leave the first part as is, meaning, fat 32, but add three additional parts to make a total of four partitions within the sdcard. So for example, part 1 (fat32), part 2-4 (ext4) which those would be the system, data, and cache. I'm confident that is how it is done, but wanted to clarify. Will do it now and check back for a reply later lol. Meanwhile, this has also given me a couple of dev ideas
Sent from my C525c using Tapatalk
Aww snap! Lol
Modding.MyMind said:
Hey, getting ready to do this now with a 2gig. Using it as a test run lol. Anyways, to confirm, you leave the first part as is, meaning, fat 32, but add three additional parts to make a total of four partitions within the sdcard. So for example, part 1 (fat32), part 2-4 (ext4) which those would be the system, data, and cache. I'm confident that is how it is done, but wanted to clarify. Will do it now and check back for a reply later lol. Meanwhile, this has also given me a couple of dev ideas
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Trust your confidence. You are right!
If you have a large card and use MiniTool, you can "shrink" your main partition to make room for the additional three. This way it won't be wiped.
Sent from the 3rd dimension!
dreccon said:
Trust your confidence. You are right!
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Outstanding, just finished partitioning it. Will tackle the boot.img now.
Sent from my C525c using Tapatalk
One additional piece of info. Be extra careful if your secondary ROM supports OTA updates which are applied from recovery. Only download but NEVER apply them before you tweak the zips. Otherwise they will overwrite your primary ROM!
Sent from the 3rd dimension!
dreccon said:
One additional piece of info. Be extra careful if your secondary ROM supports OTA updates which are applied from recovery. Only download but NEVER apply them before you tweak the zips. Otherwise they will overwrite your primary ROM!
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Not unless I make a change with the recovery lol
Anyways, I am still messing with my boot.img the fstab file for my device doesn't contain a list of mount points.
This is really the only thing it has as far as partitions are listed:
Code:
userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
Sent from my C525c using Tapatalk
Here's HTC OneSV K2_CL recovery.fstab
# mount pointfstypedevice[device2]
/boot emmc/dev/block/mmcblk0p20
/cacheext4/dev/block/mmcblk0p36
/dataext4/dev/block/mmcblk0p37
/devlogext4/dev/block/mmcblk0p25
/miscemmc/dev/block/mmcblk0p22
/int_sdvfat/dev/block/mmcblk0p38
/recoveryemmc/dev/block/mmcblk0p21
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/systemext4/dev/block/mmcblk0p35
russellvone said:
Here's recovery.fstab
# mount pointfstypedevice[device2]
/boot emmc/dev/block/mmcblk0p20
/cacheext4/dev/block/mmcblk0p36
/dataext4/dev/block/mmcblk0p37
/devlogext4/dev/block/mmcblk0p25
/miscemmc/dev/block/mmcblk0p22
/int_sdvfat/dev/block/mmcblk0p38
/recoveryemmc/dev/block/mmcblk0p21
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/systemext4/dev/block/mmcblk0p35
Click to expand...
Click to collapse
Thanks bro, i was actually trying to remember where that file was at haha.
Sent from my C525c using Tapatalk
And the fstab.k2cl is found in the source code, I'm not sure it's in the finished boot.img
russellvone said:
And the fstab.k2cl is found in the source code, I'm not sure it's in the finished boot.img
Click to expand...
Click to collapse
It is in the boot.img, I just ended up having a blonde moment when looking for the fstab recovery file haha. I knew it would have the correct info for me.
@Modding.MyMind
Could you post the fstab.k2cl in text form here please sir
russellvone said:
@Modding.MyMind
Could you post the fstab.k2cl in text form here please sir
Click to expand...
Click to collapse
Here you go. That is all of it lol
Code:
# Android fstab file.
#
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
Sent from my C525c using Tapatalk
Is this from a JB or KK ROM?
Sent from the 3rd dimension!
dreccon said:
Is this from a JB or KK ROM?
Sent from the 3rd dimension!
Click to expand...
Click to collapse
JB 4.1.2
Sent from my C525c using Tapatalk
Then you might want to look for the mountpoints in the init.rc file also in the ramdisk.
Sent from the 3rd dimension!
dreccon said:
Then you might want to look for the mountpoints in the init.rc file also in the ramdisk.
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Already snooping around lol
Sent from my C525c using Tapatalk
K2_CL info (I am wondering if I just apply the needed info to that fstab file if whether or not it will accept and read it)
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
/sys/kernel/debug /sys/kernel/debug debugfs 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p35 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p37 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p32 /carrier ext4 rw,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:38 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
/dev/block/vold/179:38 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:65 /storage/sdcard0/ext_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
Sent from my C525c using Tapatalk