yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] daedelus82:
This recovery & patch allow installation of AOSP based ROM (CyanogenMod/OpenDesire/DeFrost) with partition sizes set to match that of Nexus One.

No more need for Apps2SD hacks!

It is very easy to install, however requires security to be disabled on your device (S-OFF in FASTBOOT).

Steps to install:

1. Download AOSP Based ROM to your SD card.

2. Download nexified-boot-patch-v1.0.0-bravo.zip to your SD card.

3. Reboot in Fastboot

4. Fastboot flash recovery nexified-recovery-clockwork-2.5.0.7-bravo.img

5. Reboot into recovery

6. Wipe data/factory reset

7. Flash ROM

8. Flash nexified-boot-patch-v1.0.0-bravo.zip

9. Reboot & Enjoy

Both the recovery, and the boot patch, have kernel cmdline:

mtdparts=msm_nand:640k@0x1FF60000(misc),4608k@0x4240000(recovery),3072k@0x46C0000(boot),148480k@0x49C0000(system),97280k@0xDAC0000(cache),202368k@0x139C0000(userdata)

Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.

The patch also removes "dalvik.vm.dexopt-data-only=1" from build.prop which places dalvik-cache on the cache partition as per AOSP.

I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.

My current partitions are:

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1

Warnings:

Do not flash radio via recovery, only via fastboot. You should not be flashing radio via recovery anyway, it is strongly discouraged.

Credits:

AlphaRev - for bringing S-OFF to HTC Desire

Firerat - for the original mtd patch which I learned a lot from.

Lbcoder - for the initial information on how to modify partitions via kernel commands, i learned a lot from him as well.

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

Kali- for porting CM6 to Desire thanks a bunch

I am doing this to try and spark further interest in this, in the hopes that other developers may improve on it, as the default partition sizes on the desire are crap.

How to uninstall / set partitions back to normal:

Boot into Fastboot

Fastboot flash standard/unmodified clockwork recovery or amon_ra

Reboot into recovery

Wipe data/factory reset

Flash ROM & Reboot

Downloads:

nexified-recovery-clockwork-2.5.0.7-bravo.img

nexified-boot-patch-v1.0.0-bravo.zip
[Desire Android Development] xtcislove:
Should this work with OpenDesire 0.34,too?

And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
[Desire Android Development] beanbean50:
nice work.....

back in a flash
[Desire Android Development] daedelus82:
No, the partition sizes are passed as kernel parameters, so recovery & ROM must be patched to use the same parameters.
[Desire Android Development] cgrec92:
so what are the advantages of this?

i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?

thanks for your hard works
[Desire Android Development] Rudolfje:
Well done!

Very brave of you to almost brick your device (twice?) and continue development nonetheless.

I don't need it, but many others will love this. Thanks a lot.
[Desire Android Development] nbedford:
If I follow your procedure am I stuck on nightly-132, or once i've got the resized partitions can I continue to flash CM6 nighlites?
[Desire Android Development] marinierb:
These kernel parameters:

mtdparts=msm_nand:640k@0x1FF60000(misc),4608k@0x4240000(recovery),3072k@0x46C0000(boot),148480k@0x49C0000(system),97280k@0xDAC0000(cache),202368k@0x139C0000(userdata)

Where exactly are they set? I assume it's somewhere inside the boot.img?
[Desire Android Development] djind:
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps? :(
[Desire Android Development] mon@diac:
great works on my Desire..Thanks daedelus82 and other persons...I see 197 Mb on available space..
[Desire Android Development] aleksei87:
Thank you very much daedelus, i was waiting for this since the day s-off was released :)

Could you upload a version of the stable CM6 too?
[Desire Android Development] patp:
Great Work! I hope this becomes the norm, we need that /system space for apps.
[Desire Android Development] vecc:
Excellent! At last! Thank you very much!
[Desire Android Development] daedelus82:
Hello, yes I will patch CM6.0.2 stable as well. I have to go to work now but within a few hours. I will also try to answer other questions but have to run right now.
[Desire Android Development] ieftm:
Please note, this WILL break 'fastboot flash' functionality.

But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).

That is currently under development.
[Desire Android Development] daedelus82:
Yes, boot.img for ROM, and recovery.img for recovery

Sorry I have patched CM and Clockwork Recovery only.

Only breaks fastboot flashing of system and/or userdata, as fastboot will flash it to different blocks than the kernel is using. All other partition locations/blocks are unmodified meaning flashing of recovery, boot, and radio will be fine.. Also if you flash userdata, system, and boot all at same time it will also work, as overwriting boot will remove the kernel cmdline.

Would love to see a HBOOT implementation of this that does not require kernel modifications.

Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.

I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.

My current partitions are:

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
[Desire Android Development] nawoa:
Thanks very much for this, I'll be flashing it shortly. I have two questions if you don't mind!

Why must radio be flashed using a different method?

Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.

Maybe something like 96 System, 64 Cache, and the rest for data? (just for the love of god make it a multiple of 16 or my OCD will break the universe)
[Desire Android Development] daedelus82:
Updated OP. Added CM6 stable v6.0.2

You can patch system and cache to whatever sizes you want, it really depends on your ROM. If you have less than 96MB in your system partition then partitioning it to 96MB should be fine. I normally like to leave a few MB spare for good measure. See below for description on flashing radio from a re-partitioned recovery.
[Desire Android Development] 77flem:
Thx !! we are waiting for that ;-)
[Desire Android Development] nawoa:
Hmm... Because of the radio flashing issue and because I use DT-A2SD anyway, I think I'm going to hold off on using this until there's the HBOOT solution you guys are talking about.

Crossing my fingers that all I need to do is install standard clockwork recovery then go to a standard CM build.
[Desire Android Development] daedelus82:
As previously advertised, my nexified-recovery-clockwork-2.5.0.7-bravo.img is an easy to flash clockwork recovery with the partitions pre-configured to 145MB system, 197MB data, and 95MB cache.

I have now made a patch that will work for any CM ROM that patches boot to the same partition sizes, and removes "dalvik.vm.dexopt-data-only=1" from build.prop in order to move dalvik-cache to /cache as per AOSP.

All you have to do is:

Fastboot flash nexified-recovery-clockwork-2.5.0.7-bravo.img if you haven't already

Reboot into recovery

Wipe data/factory reset (you can skip this if partitions have previously been formatted at 95MB cache and 197MB data, and you are simply upgrading)

Install CM6 ROM/NIGHTLY

Apply nexified-boot-patch-v1.0.0-bravo.zip

Reboot

See OP for full details
[Desire Android Development] daedelus82:
You should not flash radio via recovery anyway, it has always been discouraged and increases the risk of bricking your phone.
[Desire Android Development] mr_dinosaur:
So, I take it we could delete the mtdpartmap.txt since we don't need to indicate the Nexus One file system partitions anymore.
[Desire Android Development] daedelus82:
Yep. The partition sizes are hard-coded into the recovery, and the boot patch. Keeps things simple, less chance of people stuffing it up :P
[Desire Android Development] gerrygrigore:
Only CM nightly ?

Tell me please, this can be applied only for the nightly builds of CM 6 or it is OK for the last stable 6.0.2 CM ?
[Desire Android Development] daedelus82:
Works with CM 6.0.2 as well.
[Desire Android Development] diapolon:
Hello daedelus82, it also works with OD 4.0.36 as well!
[Desire Android Development] daedelus82:
As far as I can tell OpenDesire pretty much is CM, with maybe a change or two, one being the name.
[Desire Android Development] typhex:
sorry for the dumb questions, but what exactly does this patch give me? Do i need ext partition now or not? As i understood from the first post, is that the partitions are changed so that i got more space left or am i wrong?
[Desire Android Development] Rudolfje:
This patch resizes your phone's partions on internal memory.

Downsizing /system and enlarging /data and thus more space for apps.

You can still use apps2SD and keep you ext partition.
[Desire Android Development] paulvallee:
Fastboot not sending nexified recovery

I'm running unrevoked + CM6.0.2 on an HTC Desire.

./fastboot-mac flash recovery nexified-recovery-clockwork-2.5.0.7-bravo.img

sending 'recovery' (4216 KB)... OKAY

writing 'recovery'... INFOsignature checking...

FAILED (remote: signature verify fail)

Any thoughts?

Thanks,

Paul
[Desire Android Development] alienwolf426:
your desire is not S-OFF ... look into http://xdaforums.com/showthread.php?t=794314 if you don't know what I'm talking about
[Desire Android Development] paulvallee:
Unrevoked docs mention that they s-off. Are you sure? I don't have a PC and this method will be a major PITA.
[Desire Android Development] daedelus82:
Unrevoked Forever (S-OFF) currently only supports CDMA Desire, clearly states this on their website. Is yours CDMA or GSM?
[Desire Android Development] tehownt:
For GSM Desires you have to use AlphaRev (alpharev.nl) to S-OFF it.

See here for more info xdaforums.com/showthread.php?t=794314
[Desire Android Development] tehownt:
Also,

can we get this into official CM 6.1 ?
[Desire Android Development] pampyre:
Running this with CM6 Nightly - brilliant - been waiting to sort the bad partition sizes for ages! Loadsa thanks
[Desire Android Development] yeikos:
I prefer this :(

system: 133120 (130MB)

cache: 25600 (25MB)

data: 289408 (282MB)

Could I replace this...

mtdparts=msm_nand:640k@0x1FF60000(misc),4608k@0x4240000(recovery),3072k@0x46C0000(boot),148480k@0x49C0000(system),97280k@0xDAC0000(cache),202368k@0x139C0000(userdata)

for this?

mtdparts=msm_nand:640k@0x1FF60000(misc),4608k@0x4240000(recovery),3072k@0x46C0000(boot),133120k@0x49C0000(system),25600k@0xDAC0000(cache),289408k@0x139C0000(userdata)

In this files:

nexified-boot-patch-v1.0.0-bravo.zip > MTDPartPatcher/patchbootimg.sh (line 12)

nexified-recovery-clockwork-2.5.0.7-bravo.img -> (line 1)

I think that hexadecimal memory addresses are a problem :s
[Desire Android Development] daedelus82:
For those people on AOSP based ROMs that want Nexus One sized partitions, I recommend AlphaRev's modified HBOOT. It is preconfigured to have partition sizes similar to that of Nexus One.

If you want different/custom partition sizes please see my other thread
[Desire Android Development] gerrygrigore:
Boot patch + Nexified Recovery and/or AlphaRev's Modified HBOOT ?

Sorry for this dumb question but it is pretty confusing and I don't want to make a mistake. So, if I want to install Cyanogenmod (6.0.2 for example) and to have Nexus One partitions, which way is better to follow ? The one you described here on post #1 (first page) or it is enough just to apply the AlphaRev's Modified HBOOT and after that to flash the CM ?

Can you detailed more please, step by step, the best way ?

Thank you.
[Desire Android Development] shawe_ewahs:
Can be possible do another version of Custom MTP Partitions with big /system and little /data? Can be usefull for devs that are working on dumps of HTC Desire HD/Z.
[Desire Android Development] daedelus82:
Hi, it is possible to have custom sized partitions using the scripts in my other thread.

I would be more than happy to make another version of this easy flash recovery & boot patch for Sense HD if somebody could tell me what partition sizes are best.

edit: also if any ROM modifications are required, such as build.prop edits or anything.. if all the is needed is partitions sizes changed + a boot patch then no problem at all.

I have emailed two HD ROM developers, awaiting their responses.
[Desire Android Development] gerrygrigore:
Help please

Sorry for this dumb question but it is pretty confusing and I don't want to make a mistake. So, if I want to install Cyanogenmod (6.0.2 for example) and to have Nexus One partitions, which way is better to follow ? The one you described here on post #1 (first page) or it is enough just to apply the AlphaRev's Modified HBOOT and after that to flash the CM ?

Can you detailed more please, step by step, the best way ?

Thank you.
[Desire Android Development] daedelus82:
Hi, just apply alpharev modified hboot, format partitions and install ROM. If you need assistance with using alpharev please see their thread. Thanks
[Desire Android Development] shawe_ewahs:
Thanks for the reply :)
[Desire Android Development] @ngel:
Can you kindly elaborate this? AFAIK, flashing guides coming from pros in this forum never mentioned that "discouragement".

I know that flashing radio via ZIP/recovery IS dangerous, as it's the only way we can actually brick our Desire: but I never heard about an alternative way.

Can you please explain how exactly we are supposed to safely flash a radio update?

Thank you. :)
[Desire Android Development] Ronaldo_9:
will this work with leedroid sens UI rom?
[Desire Android Development] daedelus82:
Via fastboot.

Fastboot flash radio radio.img

It's the safest way to flash radio.

Could not do this prior to AlphaRev S-OFF, which is why radio recovery zip's were created.
[Desire Android Development] LuffyPSP:
what if i have this and i wanted to use a Sense rom?
[Desire Android Development] BillThyCat:
What about CDMA?

Anyone know if this works for CDMA? I know the roms are different, not sure about the recovery/fastboot. I don't really want to try this unless I can get some form of assurance that this part of the phone is identical between the Bravo and BravoC.

Also, is this reversible? i.e. when the official CDMA 2.2 update is released by HTC?

Thanks,

BTC
[Desire Android Development] daedelus82:
Reboot your phone, and run the following command: adb shell dmesg|awk '/0x.+: "/{ print }'

If the output looks similar to this then yes it should work fine:

<5>[ 11.619476] 0x00001ff60000-0x000020000000 : "misc"
<5>[ 11.620727] 0x000004240000-0x0000046c0000 : "recovery"
<5>[ 11.625396] 0x0000046c0000-0x0000049c0000 : "boot"
<5>[ 11.628723] 0x0000049c0000-0x0000143c0000 : "system"
<5>[ 11.866302] 0x0000143c0000-0x000016bc0000 : "cache"
<5>[ 11.904357] 0x000016bc0000-0x00001ff60000 : "userdata"

Also uninstall instructions are in the OP.
[Desire Android Development] ipfreelytech:
Here's a thread for CDMA. I tested and can confirm working.

http://forum.cyanogenmod.com/topic/8859-custommtd-partitions/
[Desire Android Development] nespresso33:
A small guide please if we have an ext3 partition with app2sd , we have to format the sd card before doing your steps ?

Thanks
[Desire Android Development] paulvallee:
I have an issue applying the Oct 28 nightly on my HTC Desire CDMA running "Nexified" partition-mapped CM6.0.2.

It fails on application with:

assert_failed: getprop("ro.product.device") == "bravoc" || getprop("ro.build.product") == "bravoc" || getprop("ro.product.board") == "bravoc"

E:Error in /sdcard/cm_bravoc_full-3.zip (Status 7)

Installation aborted.

Any thoughts? Do I need to wait for daedalus82 to "nexify" CM6.1?

TIA

Paul
[Desire Android Development] Ennon:
Um, I did this on my CDMA Desire. We don't have fastboot working. How would I go about uninstalling this?
[Desire Android Development] LuffyPSP:
guys, wanna ask something, if i want to flash an update of a rom without wipe, do i need to re-flash the nexified zip again?
[Desire Android Development] LuffyPSP:
guys, will this work on MIUI rom?
[Desire Android Development] traspler:
One small question:

Instead of following the guide in the first post, isn't it way more convenient to just get the updated, patched HBOOTs from AlphaRev with a different partition table (N1Table or Sense) they have on their website?

(Actually, that's only available for GSM Desires at the moment)

Does this not also give me new partitions I can then use or is this something different?
[Desire Android Development] xtcislove:
Yes.

Make nandroid backup first look at the size of system.img in /sdcard/clockworkmod(orother)/backup(or nandroid)/Date/system.img .

For example it has 100MB choose 110 mb for data and 20 for cache if u play games.

Wipe Cache add the patches and restore nandroid backup and u are fine!
[Desire Android Development] najar360:
I have done this method and currently running out of cache. Only left 7mb. Anyway im using dark tremor to move Dc to cache partition. Coz i don't know how to use firerat. Any advise? Is there any diff between firerat and dark tremor?
[Desire Android Development] Izeltokatl:
for all those on CDMA (USCC), I used the following to get the MTD changed very easily on my CM6.1

http://xdaforums.com/showthread.php?t=806321
[Droid Incredible Q&A, Help & Troubleshooting] jesselaz:
I am using virtuous 3.0.1 and I am wondering if there is any way to get the trackpad to be a one click camera from the home screen? Or if there is any ROM where this feature is built in? Sorry if I am posting in the wrong forum.
[Droid Incredible Q&A, Help & Troubleshooting] kungfuturkey:
This would be the right forum... But as far as I'm aware there is not any way to have that done, but if you search you can have a long press on the search button do that for you.
[Droid Incredible Q&A, Help & Troubleshooting] jesselaz:
thank you but a long press is not what I want...I find myself trying to take quick pictures sometimes and it takes to long to get to the camera feature to do it, thats the only thing I miss about my Blackberry
[Droid Incredible Q&A, Help & Troubleshooting] luvit:
Checkout quickshot app or aquickcamera app.

If you are savvy, you may get an extra edge by adding the taker app scripts.
[Galaxy S I9000 Q&A, Help & Troubleshooting] juzz86:
Hi all,

I have a Telstra i9000T (I'm in Australia, so I need the 850MHz band) and I'm pretty disappointed in the experience after coming from a Nexus One. Does anyone have any suggestions or can anyone confirm any working custom ROMs which can be used on the i9000T safely?

All the reading I've done has seen little mention of the Telstra model, save for the rooting methods and a bit of general stuff. I would ideally like a stock-standard ROM, as I'm not a big fan of TouchWiz (and definitely not the typical Telstra bloat) and had a paid version of LauncherPro on my Nexus, which I loved. I've had no trouble rooting, but haven't tried a lagfix yet as noone seems to know about the i9000T.

I see that CyanogenMod seems to be booting on the Vibrant now, and Bionix was another one I was looking at. Does anyone with an i9000T have any experience (or any luck) with flashing custom software?

Edit: Also, has anyone had any luck with a lagfix on this model? I just tried OCLF and got a 'Permission Denial' error, something to do with sending the 'Flight Mode' command. Is it worth giving Voodoo a crack?

Thanks in advance! :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] t1mman:
You can try Voodoo for the lagfix, looks like it's the best one so far

http://project-voodoo.org/download

Also, Galaxy S is missing a great deal of update / optimisation as of now :| Kind of tricky but I assume waiting for the Froyo update from samsung would give a great boost (and overall better srability). As for the release of thoses updates, speculations says mid october
[Galaxy S I9000 Q&A, Help & Troubleshooting] juzz86:
Many thanks t1, appreciate the tip. I think I'll have a go at Voodoo, it sounds like it does what I'm after.

I am really disappointed in the software of this phone. I've generally always had HTC devices, but decided it may be time to branch out a bit (and I don't mind the design). Kinda makes me wish I hadn't. Haha.

Roll on the middle of October then!

Cheers,

Justin
[XPERIA X2 General] SkinnerDev:
Hi,

I have an X2 with French operator and I don't understand why time auto sync to 'GMT + 2 Minsk'. I think phone auto sync with my sim card.

If I set time manualy, 10 or 20 minutes after phone resync and set time of Minsk...

Can you give me solution for set time?
[XPERIA X2 General] SkinnerDev:
Do you need more information?

Please help me!!!
[XPERIA X2 General] Prydplante:
Hello!

The only thing I can think of is that you should try to go to Start-Settings-Personal-Phone-Timezone and set auto time to OFF...
[XPERIA X2 General] SkinnerDev:
Wow, it's amazing! It's my girlfriend phone and I have never see this menu.

Thanks
[Hero CDMA Q&A, Help & Troubleshooting] Vandelay007:
I changed my splash screen using the herc.img method - The only downside I see to this is not being able to boot into recovery mode by pressing the volume down key and the power key at the same time - I can obviously boot into recovery mode via alternate methods - like if I am already powered up by using Quick Boot or if my phone is off, I can use adb reboot recovery and that works -

but I'm thinking more along the lines of if I need to get into recovery and I am not at home and can not get to a computer -

any other ways that work?
[Hero CDMA Q&A, Help & Troubleshooting] kyouko:
:eek: you can't get into the hboot screen?

You can access recovery by pressing POWER and holding the HOME button.

But if you can't access hboot/fastboot screen...that seems like a much bigger problem to me.
[Hero CDMA Q&A, Help & Troubleshooting] danaff37:
Should have nothing to do with the splash screen. I changed mine, and can access fast boot and recovery fine
[Hero CDMA Q&A, Help & Troubleshooting] Vandelay007:
Please disregard....I figured out what to do...
[Android Software Development] Kaotika:
I'm aware of http://xdaforums.com/showthread.php?t=779822 but it's not exactly what I'm looking for.

I would prefer it to fit better with BattStatt & Tajm, meaning it would read for example like this:

ONE

UNREAD

SMS

and so on, just like Tajm & BattStatt do