it shouldn't do, I have the script convert it to unix format
I've just tried it, and it worked for me
attached is a 70 2 config
put on root of the sdcard
flash recovery-v1-1
wipe
reboot
restore/flash rom
flash boot-v1-2
Last edited:
[MOD][RECOVERY] Custom MTD Partitions (resize Data,System and Cache ) [ 2010-10-29 ]
- Thread starter Firerat
- Start date
it shouldn't do, I have the script convert it to unix format
I've just tried it, and it worked for me
attached is a 70 2 config
put on root of the sdcard
flash recovery-v1-1
wipe
reboot
restore/flash rom
flash boot-v1-2
Thanks, didn't know a 1.2 was out. But now you flash boot before flashing the rom?
Fireat,
Again - thank you for all your help. I am currently traveling and on the plane today, I made a Nandroid (+ext) backup of SuperBad 1.7(ROM I re-installed last night). Did a complete wipe and restore. Well, once again, the restore did not complete (same as with the first issue after installing MTD, the restore dots just continue...forever, filling and scrolling more than one screen. normally it's <10 lines)...so something is wrong.
Then I reinstall the same ROM again (after wiping) and got my phone to work at least. I connected it to the laptop and did an ADB shell with the flash_image command. The result was (see attachment).
So I rebooted into recovery and console command, try to flash recovery. The command returned almost instantaneously - as if it did not do anything. But it did not gave any errors either. Since it's the same recovery that I had before, how can I tell if it actually did flash it again? Maybe I should flash a previous version 1.6.x and then 1.7.0, just to make sure it does something (make any sense?)
I have not tried to restore a nandroid backup again, after my last attempt of the flashing of recovery.
Are there any other diagnostics I can run to see if the different partitions are OK (you mentioned /system) before.
When I do a fs, I see all the partitions just fine...(see second attachment)
Any ideas? Should I just try and do another restore and if that fails, re-install the ROM again?
Could it be that one of the areas of flash-memory got screwed-up? I have been flashing a lot of ROMS on this G1 and always do a full wipe......ideas?
Please let me know. I'm still traveling and will check once I land again, for any feedback or ideas.
Thanks
Bert
Attachments
are you trying to flash recovery from a CM5 based ROM?
Don't it has a bug, user recovery or fastboot
but it looks like it worked
flash_image checks the header of the installed boot.img, if it matches the one you are wanting to flash, it just stops
I myself have seen the same issue you are having with the "restore for ever"
Edit: probably worth pointing out I first saw it a while ago, way before this 'hack', but I've also managed to get in the same state while testing, but I set out to break it
from PC
Code:
fastboot erase system -wafaik RA recovery just mounts and deletes, if the yaffs2 filesystem is screwed up in anyway it won't do a 'proper job'
if you can't fastboot, then try clockwork recovery 2.0.2.0, it has
erase_image
this should do the same thing as a fastboot erase
erase_image system
erase_image cache
erase_image userdata
or use the partition menu in clockwork recovery (cwr)
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
get the .img file from ^^^
HTC Dream (GSM)
and flash via recovery .. don't do it from CM5 based ROM with flash_image or ROM Manager, chances are it won't work
Last edited:
hey firerat
Just wanted to give a warning to all noobs like me. You will be stuck in a boot loop if you install this hack and then find that you want to change your ext partitons. I didnt realize I was on ext2 and used Amon RA 1.7.0 to change ext2-ext3 then ext3 -ext4 got in a stuck in loop. To fix I had to reflash recovery img.
Just wanted to give a warning to all noobs like me. You will be stuck in a boot loop if you install this hack and then find that you want to change your ext partitons. I didnt realize I was on ext2 and used Amon RA 1.7.0 to change ext2-ext3 then ext3 -ext4 got in a stuck in loop. To fix I had to reflash recovery img.
It's working...thanks
Fireat,
Well, I think must have gone seriously wrong with the first flash. That's why I could not boot a Nandroid restore. I did install the clockwork recovery (but does not like it: I'm not sure what are the different format / delete options for partitions. With RA-recovery, they are seperated and I know which one does what). Anyway, I tried it once again after using clockwork recovery - and still no luck. Then I decided that I should increase my setting sizes form 85 5 to 10 (just as a test). I re-installed RA-recovery, did falshed the MTD-recovery, android restore and the MTD-boot (1.2) Boom! It booted!...
This is the before and after shot(See attachment)
I think I'll scale back a little on the settings, until I reach optimum values.
GREAT features....thanks!
Fireat,
Well, I think must have gone seriously wrong with the first flash. That's why I could not boot a Nandroid restore. I did install the clockwork recovery (but does not like it: I'm not sure what are the different format / delete options for partitions. With RA-recovery, they are seperated and I know which one does what). Anyway, I tried it once again after using clockwork recovery - and still no luck. Then I decided that I should increase my setting sizes form 85 5 to 10 (just as a test). I re-installed RA-recovery, did falshed the MTD-recovery, android restore and the MTD-boot (1.2) Boom! It booted!...
This is the before and after shot(See attachment)
I think I'll scale back a little on the settings, until I reach optimum values.
GREAT features....thanks!
Last question - (i promise...LOL)
If I make a change in the sizes (mtdpartmap.txt), what should I wipe & flash? I tried to find it in the OP, but I only find the instructions for a new install. I tried to only wipe (Data & Cache) then flash MTD-recov, reboot2recov and get
E:/Can't open CACHE:recovery/log errors....
I then:
1) re-flashed the original RA-recovery,
2) reboot2recov,
3) wiped everything (0-4),
4) flash MTD-recovery,
5) reboot2recov,
6) nandroid restore,
7) flash MTD-boot,
8) reboot.
What are the steps if you want to just apply a size change in the partitions, what do you need to wipe and what do you need to flash?
Bert
If I make a change in the sizes (mtdpartmap.txt), what should I wipe & flash? I tried to find it in the OP, but I only find the instructions for a new install. I tried to only wipe (Data & Cache) then flash MTD-recov, reboot2recov and get
E:/Can't open CACHE:recovery/log errors....
I then:
1) re-flashed the original RA-recovery,
2) reboot2recov,
3) wiped everything (0-4),
4) flash MTD-recovery,
5) reboot2recov,
6) nandroid restore,
7) flash MTD-boot,
8) reboot.
What are the steps if you want to just apply a size change in the partitions, what do you need to wipe and what do you need to flash?
Bert
If you want to apply a SIZE CHANGE, you currently need to wipe EVERYTHING!
And not only that, but the cache and userdata partitions need to be wiped with the NEW CUSTOM TABLE LOADED.
when you shrink system, cache will get the hangover from it
2mb cache _should_ be fine, but you *must* clear it
the easiest way is to just blank everything via fastboot
Code:
fastboot erase system -wclockwork recovery's partition format also seems to work well.
Honestly, if you have problems, just clear system , cache and data
as long as your nand backups are not larger than the target, they will restore just fine
( the system.img and data.img are not 'flashed' direct, the files are extracted into the /system and /data folders respectively )
Just remember to flash the boot patcher after the restore
been playing,
I currently have my recovery 'patched' to report itself as 1.33.2005
so no need to be messing with the updater-script
I'll play with it some more, and make it optional in the config
added recovery Patcher v1.3 to post 2
http://xdaforums.com/showthread.php?p=7061481#post7061481
NoneDangerSPl users can use this to trick a ROM into thinking it is DangerSPL
( no need to edit the update(r)-script to install on NoneDanger )
I would not advise it, its easy and cheap to replace a worn out sdcard, your MTD goes and you don't have much in the way of options.
Regardless of what I do there's always ~30MB of xxxMB of /data being used by something, are there other files using that space?
I changed my recovery to clockwork since it has the partition wiper you mention to me before, I like it a bit more since it has that rom manager app(surprised amon doesnt have one).
I changed my recovery to clockwork since it has the partition wiper you mention to me before, I like it a bit more since it has that rom manager app(surprised amon doesnt have one).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11Custom 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 )
most of my Apps are on sd-ext, dalvik-cache is on dataCode: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
/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
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in thenCode:fastboot erase system -w
and rebootCode:for i in system cache userdata;do erase_image $i;done
*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 !
data would be 117.8mb ( 116.7 useable )Code:echo "mtd 90 2" > /sdcard/mtdpartmap.txt
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
data would be 152.8mb ( 151.7 useable )Code:echo "mtd 55 2" > /sdcard/mtdpartmap.txt
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
e.g.Code:aio <option1> <option2> <option3>...
By default it will install the sd-ext mount ( option sdext )Code:aio swap remount shabang lwp
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.
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )Code:echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
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
it will thenCode:PatchUpdateScript.sh <zip file to patch>
- create a temp directory ( in your current directory )
- copy your zip to it
- extract required files
- patch update(r)-script
- zip and sign.
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
- added stuff
- removed stuff
- moved stuff
- see v1-5-6
This should be last version we need
- greater compatibility with none dreams/sapphires
- option to launch All in One Patcher
- 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
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 )
- Now supports leagcy /system/sd mount point
- 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 OLD3Custom 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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~3The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet1
You have to remove it, when you want to flash radio / spl using recovery and not fastboot, otherwise cache partition is not big enough to flash the radio / spl.
@elfasio: did you reboot to recovery after applying the FR-remove-v1.5.6-CustomMTD_S.zip otherwise there is still the 'old' partition layout. You should also do a
fastboot erase system -w
after changing partition layout, otherwise you could mess up things.1
http://www.mediafire.com/?lifib6a9ptj5j#2,1
firerats the link.
enter to v1.5.6. and there is the zip you're looking for
