Good news for those who have disabled security on their HTC Desire.
Having tried Firerat's Custom MTD patch on my HTC Desire and almost bricking it twice, I decided to break it apart and examine things in more detail.
As it currently stands v1.5.3 of his patch will corrupt your mtd0 partition if applied to your desire, so do not try it!
I read through lbcoder's custom partitions layout thread, then broke apart Firerat's patch to determine what it was doing, and what was going wrong on the HTC Desire.
The result, I have modified Firerat's Custom MTD script so it works on the HTC Desire and have successfully modified the partitions on my phone so system is 125MB, cache is 5MB, and data is 317MB.
Now after moving all my apps & dalvik-cache from SD-EXT back to DATA I still have 130MB free! w00t!
I will be providing minimal support for this, I am purely providing this to allow others to modify their partition table just as I have done. Ensure you read Firerat's original thread for further information and/or troubleshooting, it's 99% his patch/work, I just made a small change to stop mtd0 from being overwritten.
These are the steps I performed on my phone and are based on ClockworkMod Recovery v2.5.0.7.
If none of this makes sense to you then this is not for you:
Disable security on your phone. (S-OFF in FASTBOOT)
Place bravo-recovery-v1.5.3-CustomMTD.zip & bravo-boot-v1.5.3-CustomMTD.zip on SD card
Reboot into recovery
Take a Nandroid backup
Create mtdpartmap.txt on SD card with size of system & cache, the example provided sets system to 125MB and cache to 5MB, this will depend on your ROM: echo "mtd 125 5" > /sdcard/mtdpartmap.txt
Format system, data, and cache (found under mounts and storage)
Flash bravo-recovery-v1.5.3-CustomMTD.zip, this patches recovery to use the new partition sizes
Reboot into recovery
Format system, data, and cache again for good measure (found under mounts and storage)
Flash ROM, or restore Nandroid backup, it will be flashed to NAND based on new partition sizes
Prior to rebooting, flash bravo-boot-v1.5.3-CustomMTD.zip, this patches ROM kernel to load with same partition sizes.
Enjoy
Warnings:
Do not attempt to flash radio via recovery/ZIP, only do it via fastboot.
Has only been tested on HTC Desire, may not work on other phones.
Some users have suggested small cache size affects performance in games, if you play games on your phone it may be worth setting cache to 20-35MB
Uninstalling:
Removing this is simple.
Boot in to fastboot
Fastboot flash the original unmodified clockwork img
Reboot into recovery
Format system, data, cache
Install ROM/ZIP, gapps etc, reboot
Download:
bravo-recovery-v1.5.3-CustomMTD.zip
bravo-boot-v1.5.3-CustomMTD.zip
Credits:
AlphaRev - for bringing S-OFF to HTC Desire
Firerat - for the original patch. I will be forwarding you the exact changes/details shortly.
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)
Kali- for porting CM6 to Desire thanks a bunch
I don't take any credit for this, other than the time invested to get it working on the Desire.
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208112 0 208112 0% /dev
tmpfs 208112 0 208112 0% /mnt/asec
/dev/block/mtdblock3 128000 123932 4068 97% /system
/dev/block/mtdblock5 315008 184048 130960 58% /data
/dev/block/mtdblock4 5120 776 4344 15% /cache
/dev/block/mmcblk0p2 505636 2307 477224 0% /sd-ext
/dev/block/vold/179:1
7431564 5413644 2017920 73% /mnt/sdcard
/dev/block/vold/179:1
7431564 5413644 2017920 73% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Reserved
Just in case
Interesting
Nice work.
Now THIS is what I was waiting for when I s-offed my desire
Good stuff can't wait to try it out.
Thanks.
Yeahaa ... that's what many people waiting for ... Thank you very much for that work !
Nice work!
Very very Interesting...
HTC Desire
DeFrost 5.1 rom
Which is the command to see the partition sizes? i undestand is under adb but cant find the commands
wait a sec... couldn't this be used to resize the /system to fit the complete Desire HD rom... ofc that would not allow you to have custom apps, but still
daedelus82, you seem to have made the most out of your nightshift . Thanks from all of us wondering how to put S-Off to good use.
Hi, that seems very good news and tool but can you explain me the advantage to resize or manipulate the partition ??
My English is not perfect for understand "lbcoder's custom partitions layout thread" or "Firerat's patch".
Regards, Oijkn.
Short Question: Is there anything that prevents us from mounting /dev/block/mmcblk0pX as /data? Seems like a trivial Apps2SD for me, but perhaps that would be too easy...
Otherwise ~420MB /system would be possible. Don't know if thats enough for those DesireHD Roms.
Oijkn said:
Hi, that seems very good news and tool but can you explain me the advantage to resize or manipulate the partition ??
My English is not perfect for understand "lbcoder's custom partitions layout thread" or "Firerat's patch".
Regards, Oijkn.
Click to expand...
Click to collapse
The main use is to get more space for apps on /data by shrinking /system to exactly the size needed for the rom you use and shrinking /cache as it is not really used anyway (at least on g1 it was only used for ota updates, which you don't get on a custom rom).
Other use would be to fit a huge rom on a blown up /system partition.
Question before you release it: how to predict what size of /system I need? It is equal to size of /system folder in ROM's flashable file?
Second question: it is good idea to shrink /system to something like 5 MB and move all system apps to /data (then all apps can be easily uninstalled and updated)?
mblaster said:
The main use is to get more space for apps on /data by shrinking /system to exactly the size needed for the rom you use and shrinking /cache as it is not really used anyway (at least on g1 it was only used for ota updates, which you don't get on a custom rom).
Other use would be to fit a huge rom on a blown up /system partition.
Click to expand...
Click to collapse
Thanks mate for the explain ^^ I understood a little better. Do you think that patch will make my desire more efficient ??
I think this will benefit the community a lot.
Sense HD users might finally get the whole system on nand.
AOSP users will have more memory to install appss on nand.
Win-win for everybody
Will this script Resize the Partitions automatically depending on which ROM you are flashing?
wow
it sounds great
worst case we delete some unnecessary apps, and HD port can fit to the device
wow
i tried this on my g1, trust me its not worth the trouble. stick with apps2sd if youre having space problems.
warsng said:
i tried this on my g1, trust me its not worth the trouble. stick with apps2sd if youre having space problems.
Click to expand...
Click to collapse
But thats just it though... I am using using A2SD and still having space trouble!
I think this is moronic , an ext4 partition to maintain the system and a swap partition for oom situations and cached processes is enough.
Obviously there are some benefits like if your system partition is corrupted you don't lose the data but since most non-dev users will end up either reflashing the device from scratch or take it to the service center anyway , it's not logical.
Plus , i've never seen an ext4 partition get corrupted on hdds let alone ssds...
USB connectivity is solved by MTP and you can do what you cannot with mtp with adb...
It would save the developers from a lot of work and not just devs on xda , manufacturers' own devs.
I looked at my partition table and there are over 10 partitions , what the f... is this i mean ?
When you compile a new kernel , you need to write scripts mounting over 10 partitions , manually...
and i'm not even counting the flags that refer to those partitions...
I had to learn a lot of things to compile a kernel for our device from the source , now i find out that i have to do this huge manual labor for no logical reason , i'm pissed off naturally.
Does anybody have something , i missed ? or Am i right on the spot ?
I'm really hoping that i missed something , because if i didn't then it'd mean that people who made this system are idiots.
pls help me ...i am new to these things
1: i made ext3 in recovery and flashed cm10...installed s2e ,everything worked great.. got 1gb ext3 and installed apps on it...
2:next flashed "sense 5.0"(only rom zip)by "hpsgill" and made restore using titanium....now i cannot use my sd-ext and my internal memory is getting low...but able to move apps to sdcard(fat32) as native apps2sd by os..
3:folders of /data,/sd-ext are empty on root...
What to do to use my ext3....?pls help me
Should i make partition every time whenever i flashed a new rom?
or should i flash any extra zips?
pls help me .....
use recovery always install ur sense rom, 1 time is enough create sd-ext partition. dont use app2sd try shekuthanwar memory script. it move ur data, apps..
Hi guys I ask you because I do not find anything around
I have a cell phone with B63M romextralite2013 installed by CWM5504 with good result but now I wanted to put on the Link2SD to raise a bit of memory to device, but doing primary fat32 partition and tried ext2 / ext3 / ext / 4 / fat32 always gives me a script error installation that can not 'be created mount: no such device would know where I am wrong? and yet I do partitions with mini tool partition 9 I tried also in recovery mode to make the partition but the result is always the same ....
I should not put a rom cooked new reliable that has everything ???? if you could tell me a rom reliable and guidance ??
thanks for the answers
sorry for my english I'm Italian and I'm helping with google translator
Thanks for all
up plese
guys dose anyone knows the what is the data & cacsh type for mount is (fat ) or (exfat4 ) or exfat3 or what
i have install custom rom Lineage and stuck at boot animation for long time ......
so anyone have an idea how to make it work Plz help me
The data partition is F2FS.
It's filing system
And there is no need to ask something with language like this "help meeee"
If u want help, u should make ur subject more respectively because this is international forum.
Next time be carefull.
Thanks.
22trika said:
guys dose anyone knows the what is the data & cacsh type for mount is (fat ) or (exfat4 ) or exfat3 or what
i have install custom rom Lineage and stuck at boot animation for long time ......
so anyone have an idea how to make it work Plz help me
Click to expand...
Click to collapse
Data and cache to my knowledge are ext4... not fat.
There is no exfat4 or exfat3, you are extrapolating it incorrectly... there is exFat, Fat12, Fat16, and Fat32 (plus a few others that are of minor importance) that are collectively referred to as "fat" file systems and these are MS-DOS or Windows file system types. The file systems types ext2, ext3, ext4, XFS, JFS, ReiserFS, ZFS, and F2FS are all Linux file system types. These file system types fit into a partition type of MBR (MS-Dos Master Boot Record) or GPT (GUID Partition Table) with the later being used by Android.
None of that has any direct relation I can see to your problem of Lineage not working. What device, ROM, recovery, and process did you use? Did you clean flash? What Gapps? How long did you wait (first boot can exceed 20 minutes)?
You really are not giving us ANYTHING to go on here, just throwing out random questions that are most likely unrelated to your problem.
riggerman0421 said:
The data partition is F2FS.
Click to expand...
Click to collapse
and what about system and cache !!!
Cache is part of the data partition IIRC, the system should be ext 4.
help!!!
im having moto g3 xt1550 ... i had done lineage and custom recovery aslo rooted and bootloader unlocked but , for volte i mistakely installed miui 7.1.3
now the phone is dead (bricked) im tried all the ways to get into recovery but its not happening the screen is still black all!!!
please help me and thanks in advance !!!
the solution i need is to just enter the boot menu or recovery !!! :cyclops::cyclops::cyclops: