Database Info

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

Custom MTD Partitions
This is an implimentaion of lbcoder's Custom partition layouts
be sure to checkout that thread for the full history
What does it do?
Well, basically Custom MTD Partitions resizes your MTD partitions
for instance this is a CM6.1RC1, ( heavily customised )
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 73.0M 72.8M 236.0K 100% /system
/dev/block/mtdblock5 134.8M 107.2M 27.6M 80% /data
/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules
/dev/block/loop1 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /sd-ext
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
most of my Apps are on sd-ext, dalvik-cache is on data
/dev/cache is where the real cache partition is mounted, /cache is actually a bind mount from /sd-ext/cache
Applicable to..
Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )
The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **
v1.5.3 confirmed to work on heroc
v1.5.6 confirmed to work on bravo + bravoc ( with S-OFF )
unsure if it will work with your device? checkout the source on github ( or ask your favourite dev to take a look )
The 'Tech' in Breif
This method is beautifully simple...
When booting we give the kernel the mtd partition table we want to use..
Thats it
In practice we need to do this when booting to recovery, and booting the rom.
below are files to make this as simple flashing a rom.
Credits :-
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5 )
Safety First
This method is safe, however it is not without risk
Two things could potentially go wrong
Recovery flash corrupt
This is extremely unlikely, and tbh could happen anytime you flash recovery
If in the very unlikely event that you find you can't reboot to recovery you have three options
re-flash recovery via fastboot ( the preferred option )
re-flash recovery via ROM ( not a great option with cm5.0.x/cm6 )
Do the whole root thing all over again ( no one wants to do that )
system, cache , data partition unmountable - corrupt
Under the right ( or wrong ) circumstances it is possible to get 'junk' files stuck in system ( or cache,data ), and in such away that recovery can not delete them, more serious corruption can render the partitions unmountable.
It is actually quite straight forward to fix this, but it does require fastboot
Code:
fastboot erase system -w
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in then
Code:
for i in system cache userdata;do erase_image $i;done
and reboot
I would advise you seek out how to 'fastboot', which tbh is a good thing to have regardless of using this 'hack' as it can get you out of so much trouble
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
Prevention is better than cure
I have only managed to corrupt partitions when switching partition layouts while having files on cache or data, for example going from System 67.5 Cache 67.5 to System 90 cache 5 with
cache approx 80% 'used'...
I have not been able to repeat this if I wipe Cache before rebooting,
therefore I advise that you wipe both cache and data * after patching recovery ( and rebooting )
* along with system if you are using clockwork
OK, now lets patch recovery and a ROM
Install Instuctions
It really is quite simple
download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
create mtdpartmap.txt and put on /sdcard/ see configuration *
reboot to recovery
nandbackup
wipe cache + data
flash FR-recovery-v1.5.6-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Either : -
Nandrestore
Flash ROM + extras
flash FR-boot-v1.5.6-CustomMTD_S.zip
reboot
* configuration
The script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 90mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
data would be 117.8mb ( 116.7 useable )
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
Code:
echo "mtd 55 2" > /sdcard/mtdpartmap.txt
data would be 152.8mb ( 151.7 useable )
NB, above data sizes are for G1s, MT3Gs should add ~78mb
All In One Patch runner ( New to v1.5.3 )
new option to run the All In One Patch script ( versions 1.3.6 and higher )
the format is
Code:
aio <option1> <option2> <option3>...
e.g.
Code:
aio swap remount shabang lwp
By default it will install the sd-ext mount ( option sdext )
so a line just reading aio will be fine
Note: the patch must be on the root of the sdcard, and its file name must start with "fr-patch" and end with ".txt"
if you have several versions the newest ( as per files datetime stamp ) will be used
Faking your SPL
If your using an SPL that is not officially supported by your ROM and that ROM checks your SPL you can 'patch' to fake it.
Code:
echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )
you can by all means use any text editor you like, the script will automatically convert to unix format
NOTE : you are dodging the checks the ROM dev put in place, do not complain to them if this doesn't workout for you
in post 2 I have some 'CM6' Kernels I compiled for (1)0.95.xxxx SPLs
but I will only likely do these for RCs and Finals ( and there maybe a delay ).
In that post I point you towards the 'SafeSPL' ( 1.33.2003 ) this SPL is compatible with the current CM6 kernels ( so no need to wait for me or someone else to compile with bluetooth as modules ), but 1.33.2003 is not 'officially' supported ( its stock at 67.5mb system ) so you need to Fake your SPL ( say 1.33.2005 ) and resize to 90mb system ( or whatever you feel is optimum )
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
NB New Config option !!! to automatically run fr-patch136+
e.g.
Code:
mtd 90 2
spl 1.33.2005
aio swap remount shabang lwp a2sd
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.6.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
The Future....
lbcoder has already suggested ways in which we can implement this 'on the fly'
so for instance it would be possible for a ROM , to instruct recovery what MTD partition layout is required, reload mtd kernel modules, and then flash ROM + boot.img
for those with huge partitions
Hey, you could go all silly and dual boot between ROMs ..
Anyway, enjoy and feel free to modify/improve on these
Changelog
v1-5-6 : 2010-10-28
Calculate userdata size, greatly improves compatibility
Added a version to patch a boot.img ( boot-rpp ) with run-parts
didn't want to , but some are using roms which don't have run-parts, so the 06BindCache script wasn't running
Added a remove version ( remove )
flashing this will return the recovery to SPL's layout
I may well integrate that better, so you don't need a separate zip
AutoMTD_partitionPatcher can convert a recovery.img to a AutoMTD flashable zip
PatchUpdateScript.sh <full path to>/recovery.img
boot patcher is much cleaner, it just uses the cmdline of the running recovery
removed the default 90 2 sizing, you *must* set your own size in mtdpartmap.txt
v1-5-4/5
added stuff
removed stuff
moved stuff
see v1-5-6
v1-5-3 : 2010-08-13
This should be last version we need
greater compatibility with none dreams/sapphires
option to launch All in One Patcher
v1-5-2 : 2010-08-0
Bug fixes
recovery was getting written to boot ( flash_image <partition> is now a variable )
typo in env variable was causing cache and data calculations to fail
AutoMTD now prints version number ( when flashing patched Zip )
tided up system "0x" 'fudge' ( to be compatible with trout/sapphire fall back )
removes temp files from memory when done
v1-5-1 : 2010-08-06
Bug fixes, had an extra '0x' on the system start + functions had wrong env var for the location of dmesg derived partition map
v1-5 : 2010-08-06
Version numbers brought into sync
Zipe Filename - 'reordered' ( easier to see version numbers in CWR )
AutoMTD Patcher - changes as per boot Patcher + zip recursion fix ( my bad habit, thanks go to mblaster for pointing this out )
Boot Patcher - cleaned up cache bind mount
Now supports leagcy /system/sd mount point
[*]supports ROM Manager ( real cache partition mounted on /dev/cache, recovery dir symlinked from 'fake' to 'real' cache )
Recovery Patcher - can 'fake' your SPL ( see configuration )
Recovery Patcher - creates more noise ( advise wipe and reboot )
Single Patcher script ( so I don't have make the same changes to three different files that essentially do the same job )
No longer 'Hardcoded' to 32[a/b] Partition Layout ( figures out SPL layout via dmesg ) **
uses original boot/recovery img's base configuration ( i.e. EBi0 and EBi1 compatible )
=< v1.4
Recovery Patcher v1.3, added SPL faker
Boot Patcher v1.2, fixed oversite where boot.img was not 'dumped'
Recovery Patcher v1.1 initial
Boot Patcher v1.1 ( was a fail, it didn't patch boot.img on CM roms as the tmp boot.img was deleted, my fault for just using the AutoMTD Patcher's script ( which runs before the tmp boot.img is deleted )
Boot Patcher v1 initial
Todo
- 2010-08-13 redundent ( launching AIO script ) - I might add some stuff to cm5/6's backup routine via the Auto patcher, things like the "All in One" installed scripts: 05mountsd and remount
windows compatible AutoMTD script ( meh, I hate batch scripts )
- 2010-08-13 DONE - thinking of adding a config option to launch the "all in one" script, but have to make that recovery compatible first
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
mediafire downloads
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
The attached files are OLD

Custom MTD FAQ
FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my SPL starts with 0 or 10, and I want to try CM5.0.8 or/and CM6. DO I need to do anything extra?[/b]
A yeap, it seems the newer kernels are just a bit too big for x0.95.x00x SPLs, you can get round it with the below kernels. And to flash CM6 you need to 'fake' your SPL ( see configuration in OP ) or edit the updater-script. faking is easier.
However, I would recommend the 1.33.2003 SPL ( you still need to fake your SPL, but you won't need the 'special' kernels )
guide for flashing 1.33.2003 SPL by Ezterry
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-11
I have compiled a kernel, which I hope is NoneDanger compatible
the source is simply CyanogenMod's github, I have taken the config from cm6rc1, and simply changed the bluetooth to modules
this approach has worked in the past
It is pre-patched with AutoMTD, so just flash cm6rc1, then flash this
FR-CM6RC1-bootimg4NoneD-AutoMTD.zip(MD5: 386D9A05A3C0FFC08E5B3F844D437AA7)
mirrors
http://rapidshare.com/files/406402016/FR-CM6RC1-bootimg4NoneD-AutoMTD.zip
http://www.mediafire.com/?152jnqwyme3
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-27
NoneDanger compatible Kernel for RC2
FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 7858a8a8d126919318d1718c6e5167ec )
http://www.mediafire.com/file/ttxfcocsti3mma3/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
I'll have to dig out the src
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-08-15
NoneDanger compatible Kernel for RC3
2010-08-17 ( Sorry, old one had a status6 bug )
New one here
87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
src = http://github.com/CyanogenMod/cm-kernel/tree/48c57f11abaaf3de6c81f6f5c44cfe2637251184
no modifications its straight cm ( besides the config, which you can get from the compiled kernel or zcat /proc/config.gz )
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q do I need to flash both of the files each time I install a new rom?
A No, you only need to flash the recovery patcher once, unless you want to resize or you install a new recovery.
the boot patcher *must* be flashed after you have installed a new ROM or Kernel update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my cache looks odd in df, I see two and its the same size as data or sd-ext, is something wrong?
A everything is fine, since we shrunk cache its no good for things like the Market, so a script is installed to 'bind mount' cache with /sd-ext/cache or data if sd-ext is not mounted.
it actually turns out that /cache is not actually used in CM6, so I might adapt the script a little in a future release.
EDIT: as of version 1.5 the cache bind mount script mount 'real cache' separately, which should reduce confusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q When I tell ROM Manger to do something in recovery, it just reboots to recovery and does nothing. it used to do the action but not since I installed CustomMTD
A yeah, nearly forgot about that, I was going to fix it last week, basically ROM Manger writes commands to /cache, but its writing it to our bind mount so.. when recovery boots it doesn't see the commands.
In all honesty that one hasn't been pointed out to me yet, but yeah I can fix it..
EDIT: as of version 1.5 the cache bind mount is compatible with ROM Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet

looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?

asb123 said:
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
Click to expand...
Click to collapse
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder

Firerat said:
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Click to expand...
Click to collapse
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead. I remember you said something about it being a miltiple of 128K.

With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?

Ace42 said:
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead.
Click to expand...
Click to collapse
yeap, should be fine
personally I would be tempted to use clockwork, since you can erase system ( part of partition options )
.img files can be found here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I don't recommend flashing via ROM Manager with CM5 or CM6
fastboot it over, or flash via recovery
I may be a little over cautious recommending a full wipe, but I have never had problems when system, cache and data are clean.
if you are 'growing' system make sure cache and data are clean
if your 'shrinking' make sure system is clean ( so 'hangovers don't mess up /cache or data )

asb123 said:
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Click to expand...
Click to collapse
yes, you can 'grow' or 'shrink' at will
just hope it doesn't get used to be lazy and not trim bloat

Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.

TheNewGuy said:
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
Click to expand...
Click to collapse
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else

Firerat said:
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Click to expand...
Click to collapse
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.

Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
Because he bind mounted it.

Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
JAguirre1231 said:
Because he bind mounted it.
Click to expand...
Click to collapse
sorry for confusion
When I download stuff with dolphin HD it goes to /sdcard/download
maybe its different with stock browser
the cache bind mount is
added a few extra comments to make it easier to follow
/system/etc/init.d/06BindCache
Code:
#!/system/bin/sh
# check we don't already have a bind mount
# ( so if ran manually multiple times we don't end up with strange things happening )
if [ "`awk '/\/cache/' /proc/mounts |sed -n '$='`" -gt "1" ];
then
echo "cache already bind mounted"
echo `awk '/\/cache/' /proc/mounts`
exit
fi
# check if /sd-ext mounted, if yes then bind to /sd-ext/cache, if not /data/cache
if [ "`grep -q sd-ext /proc/mounts;echo $?`" = "0" ];
then
CacheDir=/sd-ext/cache
else
CacheDir=/data/cache
fi
# check we have something to bind mount, and create if not
if [ ! -d $CacheDir ];
then
install -m 771 -o 1000 -g 2001 -d $CacheDir
fi
mount -o bind $CacheDir /cache
# check dalvik-cache exists ( this is really for magics )
# so they don't end up in bootloop because dex files can not be created
if [ ! -d $CacheDir/dalvik-cache ];
then
install -m 771 -o 1000 -g 1000 -d $CacheDir/dalvik-cache
fi
actually, errm yeah it is d/l to /sdcard/downloads
not my doing
I guess cache really is pointless on froyo

hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!

speedysilwady said:
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
Click to expand...
Click to collapse
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL

Firerat said:
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Click to expand...
Click to collapse
lol yeah i was just gonna say the get prop error occured lemme remove those asserts resign and see what happens

hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
double edit: i get the same error for any rom i try to flash when i look at the logcat. the only difference is cm's latest nightly build rebooted on the g1, super e freezes at the g1 screen...ima try to modify the .txt to go back to the stock layout so i can nandroid my cachehacked cm5.08 back if not...idk what to do..

speedysilwady said:
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
Click to expand...
Click to collapse
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw

Firerat said:
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Click to expand...
Click to collapse
noo this wasnt cm5.08 this was the latest nightly, same one youre 0704 on.
it got to the g1 screen and right when its abt to hit the boot animation it reboots.
i tried super e but it froze on the g1 screen
trying to get back to 67 67 for cache and system so i can nandroid but its weird that the logcat wont show no matter what rom i use.

[JIT Updated 31/12/10] Frozen Eclair- For 2.21 & AND NOW 2.34.1 Firmwares

Firstly I am posting this with permission of [email protected] Modaco. All props go to him for the origina JIT files - buy him a beer or summat.
Original Thread (Modaco)
For all those asking what JIT is this is a good explanation:
What is JIT for Android
Please don't flood the thread asking what JIT is - Google is your friend.
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead. If anything goes wrong and you get into a bootloop or something then use my debricking guide posted in this forum. Make a backup first by Tenfars Clockwork Mod for Defy
After I attempted JIT in a half arsed way previously and not getting good results (force closes etc). Antibyte has done it the right way and compile his "Frozen Eclair" JIT package.
NB: if you have removed apps this will add them back in as it is based on all the apps from the stock rom.
Ok So this is super easy now - one update.zip applied via Tenfars Clockworkmod Recovery Get it Here! - so no excuses not to give it a try! You won't be sorry.
As always start by making a backup via Clockwork Recovery.
There are now 2 packages - Choose the one for the the appropriate stock ROM you use (2.21 or 2.34.1), make sure you choose the right one for godsake or bad things will most probably happen!
Download FrozenEclairDefy_V2.zip Here for 2.21 Stock ROMs
Download FrozenEclair_V2.34.1.zip Here from 2.34.1 No Blur Stock ROMs
Instructions:
Place the FrozenEclair.....zip on the root of your sdcard
Boot into recovery
Select "Install zip from SDCARD"
Select "Choose zip from sdcard"
Select FrozenEclairDefy......zip from the list
Select "YES - Install - FrozenEclair......zip
The above will then install and then you just need to reboot. 1st boot will take longer than usual while it rebuilds the dalvik cache.
For some reason this removes root, so just reroot by Z4Root or your preferred method once the phone has rebooted. This will also mean you will have to reapply your overclock if you use milestone overclock (well it did for me anyways!)
##If you get any untoward things happening like force closes/apps not working my advice is to 1) reflash the .sbf (you follow my guide for this) and if that doesn't work 2)do a full wipe of all data. This is hacking and stuff like that happens all the time so be prepared##
MY Advice if you want to change to 2.34.1 ROM from 2.21. Follow this process:
Back up all user apps/their data by titanium backup.
Boot into recovery and make a backup of your 2.21 ROM.
Then wipe data/cache in the recovery options.
Using the debranding guide, flash the 2.34.1 firmware.
After 1st boot it will be as if you have a new phone.
Install z4root - root the badboy.
Then after reboot install Tenfars ClockworkMod - apply the mod and boot into it
Flash the deodex/JIT package.
After 1st reboot, reroot with Z4root.
Reinstall titanium back up from the market and reinstall you user apps/data.
Reset up your system settings.
Once you've got it back how you like it, boot back into recovery and back up the new rom.
So to reitterate thanks for this go to:
Antibyte @ Modaco for the JIT Files and full Update.zip 2.21 ROM
Paul @ Modaco for the deodexed/optimised app/framework for the 2.21 ROM
Me for the XDA guide and the original Update.zip for V1 and the deodexed app/framework for 2.34.1 ROM, and the JIT update.zip
Sorensiim for the generous hosting of all my files, meaning direct downloads and no shady file sharing sites - good lad!
Changelog:
19/12/10:
Frozen Eclair V1 - JIT For Defy
Tut on deodexing rom
Update.zip for installing JIT
20/12/10:
Frozen Eclair V2 - JIT For Defy
Recompiled and more optimisations
Whole process automated in 1 easy update.zip that includes deodexing and installing JIT.
Tut/OP updated to reflect the above changes
31/12/10:
Frozen Eclair V2.34.1 for 2.34.1 No Blur Stock ROM released

Wow! A preemptive thanks from me to you and the guys at Modaco!
Sent from my MB525 using XDA App

Hey
stupid question maybe, but what is JIT good for?

so what is JIT exactly? ( all i know so far is that it makes your quadrant scores higher so i assume it makes your phone faster in general or onlky in games?) and have you had any problems yet?

Great ! But what's MCR optimised ?

kendael said:
Great ! But what's MCR optimised ?
Click to expand...
Click to collapse
Paul runs the apks through his optimisation process, I don't know exactly what it does, but i trust Paul -but if you don't then just use the standard deodexed apps

For those that don't know I have added a link to the OP which gives a pretty decent explanation for what JIT for android is, or you could google "what is android jit" and you''ll find plenty of info lets use this thread to discuss this mod and any bugs etc.

I just read the introduction of Dalvik JIT. This is really amazing. I will try it later, since it will affect the warranty anyway.

Everythings works well. Quadrant with 900 mhz before JIT= 1175. Quadrant with 900 mhz with JIT installed = 1280. Thanks Paul! Good work. Keep it up.

Wow this sounds great! Thanks.

Can anyone tell me why i get an Unrecognized option '-h' for dalvikvm -h? I wanted to test if JIT is realy enabled.

# dalvikvm -h
dalvikvm -h
Unrecognized option '-h'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all}
-Xnoquithandler
-Xjnigreflimit:N (must be multiple of 100, >= 200)
-Xjniopts:{warnonly,forcecopy}
-Xdeadlockpredict:{off,warn,err,abort}
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgenregmap
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
Configured with: debugger profiler jit show_exception=1
Dalvik VM init failed (check log file)
-----------------------------------------------------------------
This is the output from that on mine it doesnt mean anything however
Key line is this:
Configured with: debugger profiler jit show_exception=1
however if you do a logcat you will see the following from time to time proving jit is enabled:
12-19 14:53:55.641 1678 1681 I dalvikvm: Jit: resizing JitTable from 4096 to 8192

You are right. I have checked it with logcat.

Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.

Zaben said:
Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.
Click to expand...
Click to collapse
whats your linpack - are you overclocked?

Higgsy said:
whats your linpack - are you overclocked?
Click to expand...
Click to collapse
Stock 800 Mhz, I haven't messed with that stuff yet. The best I could get out of Linpack is 11.934. Neither Linpack or Quadrant are consistent. Quadrant scores vary from 937 to 1223. I haven't been able to reproduce the 1223 score.
I'm reverting here in a sec. The accounts problem has it where I can't get contacts to open. I may try again next weekend from a fresh reset.

Applied it fine and is working OK so far. Thanks! Quadrant on stock is 1241 now.
Loving the recovery applied zip. I would like to create one for the deodexed/optimised files as well - is there a FAQ about creating these?

A++ on this, defy is a really nice phone, thanks to dev efforts

Version 2 and fully automated update.zip process updated in the OP

whenever i enter recovery, it says "Can't open /cache/recovery/command" and there is no "install ZIP from SD CARD" option only reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. help

Motorola XT800W Openrecovery (based on Androidani Openrecovery 3.3)

D//After all, Thank you for your great work, Skrilax_CZ!.
//And also, thank you tenfar, your defy bootstrap apk!
2011.01.09.
Totally new version is released, so this page is re-written.
Now, you can use recovery mode when your phone is bricked!
-No need to boot to android. just press button to go to Recovery mode.
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Source code, binarys are available.
Download link : code.google.com/p/openrecovery-for-xt800w/downloads/list
It's another version of sh hijacking bootstrap openrecovery.
The original one 'Skrilax_CZ' made doesn't works for xt800w (moto glam), so I changed 'sh' binary.
1.How to install
-If you are using old version, please remove it before you install.
2.1
(You have to be rooted, busybox had installed.)
Copy OpenRecovery.zip and OpenRecovery directory to your sdcard root.
Install XT800W_OpenRecovery.apk
Run XT800W_Recovery on your phone.
Click Install button.
2.2 (alternative method - via adb shell or ssh (not recommend))
(You have to be rooted, busybox had installed.)
Copy OpenRecovery.zip and OpenRecovery directory to your sdcard root.
$su
#cp /sdcard/openrecovery/orbootstrap/install_script.sh /tmp
#cd /tmp
#chmod 755 install_script.sh
#./install_script.sh
Click to expand...
Click to collapse
2. How to use
2.1
Run XT800W_Recovery on your phone.
Click Recovery button!
2.2
Reboot your phone.
When the phone vibrate or led backlight is turned on, press any button(ex, Volume, power, search, camera)
2.3
(alternative method - via adb shell or ssh(not recommend))
$su
#/system/persistent/orbootstrap/openrecovery.sh
-If you want to add custom script, add it to scripts directory or
See files in amenu directory and mod directory.
Click to expand...
Click to collapse
3. Vibration, led button backlight, waiting time while boot setting.
Open /system/persistent/orbootstrap/bootToRecoveryOption
1st line : vibration time in second. min 0, max 10
2nd line : 0 - led off, 1 - led on
3rd line : waiting time for detrmine go to recovery or not. in seconds. min 1, max 10
Initial Value is
2
1
2
it means, 2seconds vibrate(first line), led back-light is on(second line), 2seconds wait for pressing key(third line)
To set no vibration, led is off, 2 seconds to wait,
0
0
2
(all lines have no blank, no alpahbet, no tab ect...
just type numbers and go next line!)
Click to expand...
Click to collapse
4. What's different?
4.1. XT800W_Recoery app design and recovery running method changed.
4.2. sh binary changed(only do exec >> shell + hijacking)
4.3. Now you can use this with out boot in android! just press the button.
5. How does it working?
install_script.sh - backup orignal sh to sh.bin, copy custom implementated sh binary.
When you press any key while phone is vibrating or led backlight is on in booting,
(or there exsist /system/persistent/recovery_mode file)
sh runs /system/persistent/orbootstrap/utils/a.sh
a.sh sets recovery environment and calls 2nd-boot.
2nd-boot restart init process
init process boot into recovery mode.

hounjini said:
D//After all, Thank you for your great work, Skrilax_CZ!.
//And also, thank you tenfar, your defy bootstrap apk!
2011.01.09.
Totally new version is released, so this page is re-written.
Now, you can use recovery mode when your phone is bricked!
-No need to boot to android. just press button to go to Recovery mode.
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Source code, binarys are available.
Download link : code.google.com/p/openrecovery-for-xt800w/downloads/list
It's another version of sh hijacking bootstrap openrecovery.
The original one 'Skrilax_CZ' made doesn't works for xt800w (moto glam), so I changed 'sh' binary.
[/SIZE]
4. What's different?
4.1. XT800W_Recoery app design and recovery running method changed.
4.2. sh binary changed(only do exec >> shell + hijacking)
4.3. Now you can use this with out boot in android! just press the button.
5. How does it working?
install_script.sh - backup orignal sh to sh.bin, copy custom implementated sh binary.
When you press any key while phone is vibrating or led backlight is on in booting,
(or there exsist /system/persistent/recovery_mode file)
sh runs /system/persistent/orbootstrap/utils/a.sh
a.sh sets recovery environment and calls 2nd-boot.
2nd-boot restart init process
init process boot into recovery mode.
Click to expand...
Click to collapse
Xt800w already have the 2.2?

big thx ~~~
what about the system?
I dump the system with your recovery but failed.
Have you decided to dump the system?

motoxt800w said:
Xt800w already have the 2.2?
Click to expand...
Click to collapse
moto said that 2.2 is planned to be released in q1 2011

2.2....When brush ah 2.2？

hounjini said:
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Click to expand...
Click to collapse
I can't use apply update.zip in OpenRecovery to uprom
or because I use Cygwin to cook rom fails?
any one was like me?

sorry for a very noob question, but how to root xt800w. I just got this phone today and i search there is no specific subforum for this one. Thx for the clues...

I can't go into bootloader so please guide me slowly ...any video for bootloader?

[Q] How to increase vibration duration of soft keys
HELP!
I have Motorola Glam XT800W running MIUI.1.5.27.Ko Android 2.3.4 and I love everything about it except the limited personalizing options.
My main concern is how do I increase the vibration duration in pressing the soft keys? They are set so low that I can barely feel it.
Another is my notification led lights are not working at all, its not that its defective. I think it has to do something with the rom. How should I fix this?
Is there a way that I can upgrade my phone to MIUI 4.0 ICS? Please advice. Thank you very much!

need help
can anyone here help me on how to unbrick my xt800w?it is always stuck up on booting please someone help me on this thing :crying::crying::crying::crying::crying::crying::crying:

[Huawei IDEOS U8150] [ROM] based on V100R001C191B822 release

I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Mini How To
How to install recovery and custom ROMs
Changelog and Downloads
2011-02-11
IMPORTANT NOTE: I have not tested this ROM as I not own U8150 anymore
FILENAME: U8150V100R001C191B822_021211_094422.zip
MD5: 110c084c71729aca1ea8361dcb5fe5f5
* Reverted back to Launcher2
* Added Apps2SD
* Add couple apps I think is useful: wifi analyzer, android terminal, alogcat, cache cleaner-ng. (these can be easily uninstalled)
* Built with latest kitchen 0.120
* Removed Gingerbread keyboard and Google Goggles
2011-01-15
FILENAME: U8150V100R001C191B822_011511_221843.zip / Mirror
MD5: 357e5efb21d3272bb0820c0e14cfe913
* Added Boot Animation - Android Scribble 2.0 no flare
* Added Gingerbread Keyboard - Renamed Gingerbread Keyboard - updated 2010-12-28
* Unlocked Market - thanks xxhp for the package
* Added Google Goggles and AdFree
2011-01-09
This ROM should have overall better performance(hopefully)
Note:
Do a wipe of data and must clear dalvik-cache because of JIT being enabled (under 'wipe' in AmonRA Recovery 1.6.2 ROM)
FILENAME: U8150V100R001C191B822_010911_182214.zip
MD5: d8fae03567ebfa1602a116cc9e5aa587
* Added more ring tones from CM rom
* Ring delay fix
* CDRom symlink fix
* Fixed proximity delay (phone come off of the "black screen" faster)
* Turned Automatic brightness ON
* Now wifi will scan once every 1 minutes when not around a known location.
Help minimize battery drain.
* Added JIT
* Set Setup Wizard to run 'Optional'
2011-01-05 Initial Release
FILENAME: U8150V100R001C191B822_010511_014603.zip
MD5: 059fe7693164b1031a63fce373d57717
* Rooted (Superuser.apk + su)
* BusyBox installed
* /system/framework is deodexed
* /system/app is deodexed
* twitter/facebook/documents2go moved to /data/app
* swapped out Launcher 2 for Zeam Launcher
* Apps like Gmail, Maps, Vending etc updated.
If you like my work please make a donation via the Donate to me button on the left
Enjoy

Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)

Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me

hachoo said:
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Click to expand...
Click to collapse
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.

[How to] install recovery and custom ROMs
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Part 1 Installing Recovery ROM
Please refer to this post before flashing Recovery ROM - AmonRA Recovery 1.6.2 and BLUE Screen
The custom recovery allows you to do all sorts of lovely things such as installing ROM update zips (for the forthcoming custom ROMs), wiping various parts of the device, backing up and restoring and much more.
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
Downloads
AmonRA Recovery 1.6.2 - DOWNLOAD (MediaFire Pro) / MIRROR (CoBlitz / ROMraid) - MD5: 65d4dcbbedb956a9f88dd1981fb31ef8
How to install - Windows, Linux and OSX
Download the recovery image of your choice above and extract the zip file
Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
WINDOWS - double click 'install-recovery-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
Part 2 Installing Custom ROM
Note: When using the Custom Recovery image use the Trackball to move up / down and press to select. Use the volume down button to go back.
Download a Custom ROM of your choice and place the ENTIRE ZIP (Do not extract it) onto the root of your SD card. By "Root" I mean do not place the file in any subfolders
Enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
From Custom Recover Main menu and select the 'Backup/Restore' option. Choose a 'Nand backup' and let it run it's course
Return to the Custom Recover Main menu and select the 'Wipe' option. Choose the First option 'Wipe data/factory reset' and confirm. <- this is optional after installing one of my ROMs. I personally have not bothered with it with my ROMs
Return to the Custom Recover Main menu and select the 'Flash zip from sdcard'. Select the custom rom you wish to flash, confirm and wait.
Part 3 Restoring back to original ROM
Note: Upgrade operations will erase the user data.
Find and Download ROM from Link provided on WiKi that you want to install
Copy the entire dload folder (with UPDATE.APP in it) to the root directory of the MICRO SD card.
Make sure your handset is power off. Insert the MICRO SD card into the handset. Pressing the END key and VOLUME UP key, and then press the POWER key to power on the phone and enter the Software Upgrade Mode.
You can see process bar start from 0 on the screen. (this take a few minutes)
Then the handset will restart automatically. Then it is OK.
Reference:
Part 1 info taken from here

quail said:
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
Click to expand...
Click to collapse
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.

Trekker56 said:
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
Click to expand...
Click to collapse
Sorry I did think to add a how to install recovery/custom ROM how to, well there is one now.
Thanks

hachoo said:
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Click to expand...
Click to collapse
I have played around with Linux Kernels in the past just not the Android kernel yet... but I am sure it not that hard to patch it and recompile.
I am happy with the 600MHz that setCPU unlocks it too.

quail said:
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
[*] Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
Click to expand...
Click to collapse
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.

tankknat said:
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
Click to expand...
Click to collapse
You should not be getting a blue screen, you sure your using the correct key combination?
Yes you need the USB cable plugged in to use the bootloader. Yes the bootloader is ment to just sit at the IDEOS logo

yeah im 100% sure i used the correct key combo for the restore recovery mode, and sweet as for the bootloader, just wasnt 100% sure on that one.

Thank you OP for the info here, I used them to flash the recovery and I'm going to flash your ROM.
Having a Desire from the very first day I'm not new to these things, but this little boy is in my hands since this afternoon and it's amazing that you came with this just in time.
Will report back in a while with impressions.

OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?

@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version

quail said:
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
Click to expand...
Click to collapse
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?

@ngel said:
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
Click to expand...
Click to collapse
thanks, fixed the typo.
ATM there is no newer version.

@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
Another thing I am not sure what the diff is between the Italian ROM and the Australian ROM. I wonder if you phone is not fully compatible with the Australian ROM?

ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...

First version working
I had the same problems as @ngel using the newer version. Fail with the iso symlink.
Used the first version you posted up and that worked without a problem.
Zeam Launching is really snappy. Or I just haven't bogged down my phone with a whole bunch of crap yet.
Thanks for your work I bought my Ideos through 2 Degrees in New Zealand.
Request:
I quite like the look of the black notification bar and green icons. Would you be able to theme this rom with those? Also could you include the gingerbread keyboard. I know I can install it separately but would be cool to have Touch Pal and the original keyboard removed and replaced with the gingerbread one.

tankknat said:
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
Click to expand...
Click to collapse
Did you power on your unit holding the 'volume up' and 'red' key?

Ported CM7-RC12 on XT720(Korean Motoroi) - Old version

This rom story has been moved development thread.
Follow link:
http://forum.xda-developers.com/showthread.php?t=1227835
--------------------------------------------------------------------
Ported CM7-RC12 to XT720(Korean Motoroi)!!
[Outline]
CM-7.1.0-RC12 customized.(default base is nadlabak's Milestone ROM)
Model : Korean Motoroi XT720
Based Rom : STSKT_N_79.33.50R (Android 2.2.1)
[Work]
3G fixed.
WiFi fixed.
Battery fixed.
USB fixed.
KeyPad fixed.
Sensor's fixed.
Touch fixed.
App2sd fixed.(ext3)
Etc.
[Not Work]
USB Connect icon(Status-bar)
overclock
[Install]
1) RSD for STSKT_N_79.33.50R (Android 2.2.1)
2) root
3) OpenRecovery install
4) Update-pack download and copy (/sdcard/OpenRecovery/updates)
5) OpenRecovery boot
6) Wipe Data / Factory reset
7) Apply Update (CM-7.1.0-RC12-XT720-J.Y.Daddy-Beta1.zip)
8) reboot
[Mirror]
http://www.multiupload.com/8Z6Y5O1HSW
[2011.08.15]
And MIUI Gingerbread 1.8.12 version, we also succeeded in porting.
Yet there remains a minor bug, but can be used.
If you succeed in porting MilestoneXT720 CM7, of course, a port will become MIUI Gingerbread!
Good Luck!!
Alpha-1 Version Download :
(MIUI-1.8.12-KO-XT720-J.Y.Daddy-alpha1.zip) http://www.multiupload.com/NOJWWVYF00
Thanks for your help.

Quick question: Is this compiled from source for XT720 or is it a binary port of nadlabak's A853 (or other) ROM?

We did not compiled.
Through a variety of modules that are compatible with the process of extraction is created by the ROM.
Of course, the default base is nadlabak's A853 ROM.

For European xt720 we get bootloop...

I believe you must 1st sbf to Korean 2.2 for it to boot. Just like the one we already have. And Mioz what about the 5 point touch module for milestone? You think that might make our touch work.

fjfalcon said:
For European xt720 we get bootloop...
Click to expand...
Click to collapse
When you update from a different ROM will be bootloop.
Based rom is Korea Froyo Rom(STSKT_N_79.33.50R).

easye420 said:
I believe you must 1st sbf to Korean 2.2 for it to boot. Just like the one we already have. And Mioz what about the 5 point touch module for milestone? You think that might make our touch work.
Click to expand...
Click to collapse
We are the "5 point touch module" tested. Is not active.
However, we have "3 point touch module" has to.
It is active only in Korea Motoroi XT720.

J.Y.Daddy said:
We are the "5 point touch module" tested. Is not active.
However, we have "3 point touch module" has to.
It is active only in Korea Motoroi XT720.
Click to expand...
Click to collapse
Does the 3 point touch module enable touch on cm7 on motoroi?

easye420 said:
Does the 3 point touch module enable touch on cm7 on motoroi?
Click to expand...
Click to collapse
CM7 touch does not work. So, can't test yet.
Possibilities are very high.

hello i'm members of androiders,too
I heard usb problem fixed by vista of androiders.
can you find vista's thread that fixed usb problems??
i want to this project will be successful.
(in korean)낭만로드님 제가 그전에 비스타님의 글로 터치제외한 모든버그를 고쳤다는 글을 읽은것 같습니다. 한번 비스타님의 글을 뒤져보심이......
Sent from my A853 using XDA App

siwkim said:
hello i'm members of androiders,too
I heard usb problem fixed by vista of androiders.
can you find vista's thread that fixed usb problems??
i want to this project will be successful.
(in korean)낭만로드님 제가 그전에 비스타님의 글로 터치제외한 모든버그를 고쳤다는 글을 읽은것 같습니다. 한번 비스타님의 글을 뒤져보심이......
Sent from my A853 using XDA App
Click to expand...
Click to collapse
Oh! nice to meet you.
This work will progress up with Vista's.
And some members are doing together.
(in korean)
여기서 한국사람을 뵈니 색다르네요. 한글도 ㅎㅎ;
지금 말씀하신게 바로 저와 비스타님이 진행해서 현재 여기까지 온거에요.
즉, 저와 비스타님 뿐만 아니라 로이포럼에서 연구소 쓰레드로 진행해 왔는데
터치문제는 지금 난관에 부딪혀서 이렇게 XDA에 올리게 된 것입니다.

have you tested XT720(milestone)'s original touch module?
i think that module make topuch work.
(in Korean)낭만로드님 답변을 해주시니 감사할 따름입니다.
혹시 유럽발 XT720의 기본 터치모듈이 작동하는지 확인해 보셨나요?? 아마도 모듈 문제 같은데 한번 테스트 해보심이...
Sent from my A853 using XDA App

siwkim said:
have you tested XT720(milestone)'s original touch module?
i think that module make topuch work.
(in Korean)낭만로드님 답변을 해주시니 감사할 따름입니다.
혹시 유럽발 XT720의 기본 터치모듈이 작동하는지 확인해 보셨나요?? 아마도 모듈 문제 같은데 한번 테스트 해보심이...
Sent from my A853 using XDA App
Click to expand...
Click to collapse
hmm.. good idea. i will try.
(in korean)
그건 미쳐 생각 못했네요 ㅎㅎ; 어차피 이것 저것 다 시도해보는터라 한번 해보아야겠네요.
아이디어 고맙습니다^^;
------------------------------------------------------------------------------
[Test Result]
Are the same. touch doesnt work. (in korean: 달라지는게 전혀 없네요 --)

Proprietary files comparison
Attached is a zip that contains a text file with md5 sums and two csv spreadsheets that can be used to compare some relevant ROMs. The ROMs included in the comparisons are:
1. STSKT_N_79.33.50R (Motorola's 2.2.1 for Motoroi XT720)
2. update-cm-7.1.0-RC12-11.07.14-Milestone-signed (Nadlabak's CM7 for A853)
3. android_vendor_motorola_umts_sholes (nadlabak's github)
4. CM-7.1.0-RC12-XT720-J.Y.Daddy-alpha-1 (port of #2/#3 for Motoroi XT720)
5. SC_2.2_XT720_Beta3a (Dexter's/WanHu's port of #1 for Milestone XT720)
The spreadsheet is limited to only the files included in android_vendor_motorola_umts_sholes/proprietary. These are the files that are copied verbatim from the A853 Motorola ROM and used by nadlabak's build. Some files needed on XT720 don't have the same name, but they are not included (i.e. cameraCalFileDef5M.bin and cameraCalFileDef8M.bin is used on A853 but cameraCalFileDef.bin used instead on both XT720s) The columns of the spreadsheet are:
1. file name
2. md5sum
3. path hint
Using the md5sum you can see if the file included in each one is different from the others. For example:
Code:
pvrsrvinit 579227b3cbaca8a67f24075d5b51d2d8 CM-7.1.0-RC12-XT720-J.Y.Daddy-alpha-1/system/bin/pvrsrvinit
pvrsrvinit 3c3d144ae96061476218d283e393c54e SC_2.2_XT720_Beta3a/system/bin/pvrsrvinit
pvrsrvinit 579227b3cbaca8a67f24075d5b51d2d8 STSKT_N_79.33.50R/system/bin/pvrsrvinit
pvrsrvinit 579227b3cbaca8a67f24075d5b51d2d8 update-cm-7.1.0-RC12-11.07.14-Milestone-signed/system/bin/pvrsrvinit
pvrsrvinit 579227b3cbaca8a67f24075d5b51d2d8 android_vendor_motorola_umts_sholes/proprietary/bin/pvrsrvinit
This indicates that the file /system/bin/pvrsrvinit is identical on STSKT_N_79.33.50R, update-cm-7.1.0-RC12-11.07.14-Milestone-signed, CM-7.1.0-RC12-XT720-J.Y.Daddy-alpha-1 because they all have md5sum=579227b3cbaca8a67f24075d5b51d2d8. But on Milestone XT720 (SC_2.2_XT720_Beta3a) the md5sum=3c3d144ae96061476218d283e393c54e. This means that this file was changed by Dexter/WanHu from the version in Motoroi XT720 version in order to get the ROM to work on Milestone XT720.
So, one way to go about this is to try and see if there are some files that might need to be updated. For example, files that are identical in STSKT_N_79.33.50R and SC_2.2_XT720_Beta3a very likely need to be identical in both CM-7.1.0-RC12-XT720-J.Y.Daddy-alpha-1 and a Milestone XT720 port. So one thing to do is to study these lists and identify files that seem suspicious.
The comparisons.md5 file has md5sums for all files in the ROMs (i.e. not just the ones in nadlabak's github).
Edit: added a shortlist.csv to the zip that removes files that are identical in all five ROMs

Or we can just debug the ROM via adb and see if any useful error-messages regarding the touch screen come up.

Vistaus said:
Or we can just debug the ROM via adb and see if any useful error-messages regarding the touch screen come up.
Click to expand...
Click to collapse
I wasn't able to find anything useful using logcat or dmesg when I was trying to binary port stlifey's, so I wasn't expecting to see anything useful here, either. The touch is quite strange on our phone. For example if you use a different bootanim binary, *poof* touch doesn't work (I was trying to get the live logcat/live dmesg working, chainfire seemed to think that was strange, too). Or if you delete /system/media/bootanim.zip to try and use the default android animation, *poof* no touch. Even in those cases, I couldn't find anything in the logs that was different.

Some questions for Motoroi owners
Can someone with a Motoroi XT720 post the output of "getevent" run over ADB?
Is there an OpenRecovery for Motoroi XT720 that works when holding volume-up at boot to enter OpenRecovery?
It looks like when I apply the 50R sbf on Milestone XT720, then the volume keys are on event3 (check this by "adb shell getevent /dev/input/event3" and pressing volume up/down):
Code:
/dev/input/event3: 0001 0073 00000001
/dev/input/event3: 0001 0073 00000000
But on Milestone XT720 running a Milestone XT720 kernel, the volume up keys are on event4 (check this by "adb shell getevent /dev/input/event4" and pressing volume up/down)::
Code:
/dev/input/event4: 0001 0073 00000001
/dev/input/event4: 0001 0073 00000000
This is what I get from getevent on Milestone XT720 when running 50R:
Code:
add device 1: /dev/input/event6
name: "sensors"
add device 2: /dev/input/event5
name: "lm3530_led"
add device 3: /dev/input/event4
name: "proximity"
add device 4: /dev/input/event3
name: "sholes-keypad"
add device 5: /dev/input/event2
name: "qtouch-touchscreen"
add device 6: /dev/input/event1
name: "cpcap-key"
add device 7: /dev/input/event0
name: "compass"
And this is what I get running a normal Milestone XT720 ROM:
Code:
add device 1: /dev/input/event7
name: "sensors"
add device 2: /dev/input/event6
name: "lm3530_led"
add device 3: /dev/input/event5
name: "proximity"
add device 4: /dev/input/event4
name: "sholes-keypad"
add device 5: /dev/input/event3
name: "qtouch-touchscreen"
add device 6: /dev/input/event2
name: "cpcap-key"
add device 7: /dev/input/event1
name: "accelerometer"
add device 8: /dev/input/event0
name: "compass"
So, it seems that the accelerometer device is missing when booting the Korean kernel on Milestone XT720 and this shifts the keyboard to event3? Or does accelerometer not exist on Motoroi?
Edit: Here's a modified sh binary for Milestone XT720 users running 50R. I'm pretty sure this will not work on Motoroi XT720 based on looking at the key mapping file in the stock 50R. My theory is this is a problem for Motoroi kernels on Milestone XT720, only. I just used a hex editor to change /dev/input/event4 to /dev/input/event3. This works on my Milestone XT720. Replace /system/bin/sh and /sdcard/OpenRecovery/orbootstrap/str/sh with this copy, but be very careful--if you flash a non-korean sbf the volume up will stop working. Eventually it would be better to have a single binary that checks both event4 and event3, but I haven't figure out how to recompile orbootstrap yet. And you should probably be religious about reapplying this after applying updates etc incase it gets replaced with a bad version, etc.

Mioze7Ae said:
Can someone with a Motoroi XT720 post the output of "getevent" run over ADB?
Is there an OpenRecovery for Motoroi XT720 that works when holding volume-up at boot to enter OpenRecovery?
Click to expand...
Click to collapse
Thank you very much for your help.
The same OpenRecovery Motoroi is being used.
Volume-up key at boot to enter the OpenRecovery available.
And acceleration sensors are also Motoroi.
I do not know why that does not appear in MilestoneXT720.
However, CM-7.1.0-RC12-XT720-JYDaddy-alpha-1 does not appear in.
[Question]
"sh binary" input device to control possible?
CM-7.1.0-RC12-XT720-JYDaddy-alpha-1 after install
other input devices has confirmed that the event occurred.
"/ dev/input/event3". In other words, the only thing can't see the qtouch-screen events.
Thanks.

I don't think the event renumbering is much of a problem for Android on MsXT720, because the 50R works fine (except for the missing accelerometer) and touch works there. It was just that the hijacked sh from open recovery is uses /dev/input/event4 to read the keys. Since they are not shifted on Motoroi and touch does not work, and Milestone is shifted and touch does work on stock 50R, I think the problem must be somewhere else.
Did you try using /system/bin/bootanimation and/or /system/bin/linker from 50R? Dexter changed those for MsXT720 when he ported 50R to the MsXT720. That may give clues about what files are kernel-specific (since this ROM wad compiled for A853).
Maybe I can try breaking the WanHu ROM on MsXT720 to see which files stop the touchscreen.
Sent from my XT720 using XDA Premium App

Mioze7Ae said:
Did you try using /system/bin/bootanimation and/or /system/bin/linker from 50R? Dexter changed those for MsXT720 when he ported 50R to the MsXT720. That may give clues about what files are kernel-specific (since this ROM wad compiled for A853).
Maybe I can try breaking the WanHu ROM on MsXT720 to see which files stop the touchscreen.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
bootanimation change not try.
change bootanimation!! i will try it, tonight.
and then will shared result.