yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] eyegor:
Ever regretted switching to the new radio because of the really small data partition? You've come to the right place!

While sifting through the G1 forum i Have come across this wonderful tool by firerat and lbcoder!

(For newest version check firerat's thread:HERE )

Basically, it is a tool for resizing partitions of your phone.

IT CAN BE USED FOR ANY RADIO AND ANY MAGIC/SAPPHIRE PHONE! TAKE THE SAME STEPS!

How should I use it?

Here are some basic steps that anyone should follow to get a gigantic data partition!

1. Flash a ROM of your choice

2. Run "adb shell df"

3. See how much data is on /system and /cache

3.' Put mtdpartmap.txt and both patches on the ROOT of your SDCARD

4. In mtdpartmap.txt write slightly larger values ( for example if a ROM takes up 158MB, write 160 and if cache is 2.5MB write 3)

5. Make a nandroid backup

6. IMPORTANT: boot into fastboot and run "fastboot erase system -w"

7. boot into recovery and flash the recovery patch

8. IMPORTANT: Run "adb shell reboot recovery"

9. Restore nandroid

10. Flash Boot patch

11. ENJOY!

N.B You need to perform step 10 every time you flash or restore a ROM.

mtdpartmap.txt looks like this:

90 2

Where "90" stands for /system space and "2" for /cache space. Change these values but be sure to check step 2. Changing partition size is as simple as changing those two values.

N.B If you are using a ROM that has dalvik-cache moved to cache disregard the amount of space used on the cache partition and set it to 3MB as a test, increase in case of problems. Dalvik-cache WILL BE CREATED ON THE DATA PARTITION. (It is bind-mounted, and basically then /cache is as large as /data)

With a clean install of CursorSense I was able to get 290MB of usable data space, but for example Fusebox Froyo should only take up about 90MB of /system space so you could get 370MB of data! (if I calculated right :P)

ALL credits go to firerat and lbcoder! Please give them credit where it is due.

Thanks!
[myTouch 3G, Magic Android Development] dekimaks:
I do not understand,which value I write in txt free or used space?
[myTouch 3G, Magic Android Development] eyegor:
If a rom uses 98MBs then write 100... Basically then it will create a 100MB large partition.
[myTouch 3G, Magic Android Development] dekimaks:
First I check my space it is 158,I write 160,and I Folow our yours steps...

In the end I reboot my phone,and I chech again,is is a same,now I have 158 used space again.It seams do not work on my HTC.Please help
[myTouch 3G, Magic Android Development] eyegor:
Did you perform all the stepps exactly how I wrote them?

The mtdpartmap.txt has to contain two values. Not just 160 but for example 160 3
[myTouch 3G, Magic Android Development] klothius:
Nice work, I've already put together automatic system deletion plus recovery patching and I'll be releasing an update for smoki soon enough and I'm already in the process of creating automatic rom flashing plus patching the bootimg. So...great work, no need anymore for moving the dalvik cache to /cache...and in return we should get better first boot times(creating dalvik cache natively on /data is faster than on /cache) ;)
[myTouch 3G, Magic Android Development] eyegor:
Nice! I like that people started implementing this. Personally, i think its a HUGE improvement!
[myTouch 3G, Magic Android Development] dekimaks:
Yes,my system is 158,my cache is 64,and I put in txt 160 66,and folow all steps.

I ll try again:(
[myTouch 3G, Magic Android Development] eyegor:
Put 160 3. You cant expect a major boost if you use such a large cache partition.
[myTouch 3G, Magic Android Development] klothius:
post not needed
[myTouch 3G, Magic Android Development] capychimp:
and then when someone wants to flash a rom, (that is larger than the partition they got from flashing a rom that has this implanted) , they have to go here and learn to reconfigure, and then they scream cause they can't figure it out ;) this is gonna be fun with time ;)
[myTouch 3G, Magic Android Development] klothius:
Not really....I'll be including a tool to change the partition size with my next update made for my rom...others can do it for theirs....or even less complicated is to use the same one as the one I'll include will leave system partition at 170MB and that is what SenseUI roms need...AOSP roms need way lower space on system, so there shouldn't be any conflict. IF someone wants to experiment with AOSP and letting the data partition have more space and less space on system, then they should use the manual method....in turn the person will know that it doesn't have enough system space for a senseui rom and will adjust it accordingly...or just flash the one I'm preparing now.
[myTouch 3G, Magic Android Development] eyegor:
Its the same steps no matter if they are doing it the first or the 100th time... i think all it will do is help people...of they try to think a bit...
[myTouch 3G, Magic Android Development] capychimp:
so to implant it we have to change our update script to the binary one?
[myTouch 3G, Magic Android Development] eyegor:
I recommend you read the original post for that info :)
[myTouch 3G, Magic Android Development] klothius:
Yes, I was wrong there and I saw that right after I wrote it, but I forgot to change my post...I was just thinking ahead. Thanks for correcting me ;)
[myTouch 3G, Magic Android Development] eyegor:
Thanks for the support lbcoder. I dont know much about the matter, and my only goal was the popularisation of the patch in this part of the forum.:-)

Klothius can you please edit the post about the dalvik problem to eliminate possible confusion? Thanks :-)
[myTouch 3G, Magic Android Development] klothius:
I did ;)
[myTouch 3G, Magic Android Development] eyegor:
Thank you :)
[myTouch 3G, Magic Android Development] keinengel:
Awesome!

C:\Users\Sebi>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.8M 0 95.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 148.6M 21.4M 87% /system
/dev/block/mtdblock5 290.8M 128.6M 162.2M 44% /data
/dev/block/mtdblock4 290.8M 128.6M 162.2M 44% /cache
/dev/block/mtdblock5 290.8M 128.6M 162.2M 44% /cache
/dev/block//vold/179:1 3.7G 3.4G 264.0M 93% /sdcard

(running CursorSense 1.2.6.1)

Now, a few questions:

1. How do I undo the patch? Is it enough to reflash my recovery, wipe everything from fastboot and restore the backup from before the patch?

2. I sometimes flash other ROMs, just to test them. Would there be a problem if I forgot to flash the boot patch after the ROM?

3. When I install an AOSP ROM and want to use the patch, what's the order? Do I change the TXT, flash the ROM and then the boot patch? Or do I need to wipe from fastboot when changing between Sense UI and AOSP?
[myTouch 3G, Magic Android Development] eyegor:
1. Yup, that's enough.

2. I really don't know, but i'd make sure i flashed the patch. IMO it can't hurt that bad but still..id flash it.

3.I don't really understand this question but...if you wan't to "shrink" the system partition you have to erase system from fastboot else other partitions will be corrupted by residual data.

As i did not read the whole firerats thread I guess you would get better information there. I was a mere messenger in this case.
[myTouch 3G, Magic Android Development] keinengel:
Cool, that's all I needed to know :) Thanks!
[myTouch 3G, Magic Android Development] capychimp:
what about building it in your great tool? @eyegor
[myTouch 3G, Magic Android Development] eyegor:
I might discuss it with mumi but he is against integrating adb commands in the radio switcher.
[myTouch 3G, Magic Android Development] capychimp:
ok was just an idea :)
[myTouch 3G, Magic Android Development] eyegor:
It's a great idea :)
[myTouch 3G, Magic Android Development] wjsturgis3:
This sounds like a great idea. I have a 32A magic with CM 6.0.0 RC2, bcrooks EBI1 port. My system partition is 90MB, data 295.8MB and cache 80MB. By your suggestion I would use a 90MB system and 3MB for cache adding 77MB to data.

My question is: since I'm using Amon_RA 1.7.0H recovery which has nandroid backing up and restoring cache by default, what will happen when I do the nandroid restore with a 3MB chache partition with a 35MB cache.img file?

Would I have to wipe cache before doing my nandroid backup in order for this to work?
[myTouch 3G, Magic Android Development] eyegor:
The cache is bind-mounted to the data partition, basically making the cache partition as big as the data partition. My guess is that the restore cache.img would then go to the data partition.
[myTouch 3G, Magic Android Development] wjsturgis3:
Thanks for the reply eyegor.

I guess I'll just have to try it since all I have to do to backout is to reflash recovery from fastboot and do a nandroid restore, right?
[myTouch 3G, Magic Android Development] wjsturgis3:
Just rechecking Firerat's original thread and noticed that he now has version 1.5.2 of the patch.zip files. Should these be used and might it be a good idea to refer folks to his thread for the latest versions(save you some time and effort)?
[myTouch 3G, Magic Android Development] eyegor:
I'm not sure if those are universal like these that I posted, I'll refer to his thread, good suggestion.
[myTouch 3G, Magic Android Development] wjsturgis3:
I tried Firerat's version 1.5.2 version of the files, they worked like a charm. Here are my before and after stats.

Before:

Filesystem size Used Available Use% Mounted on

tmpfs 95.8M 0 95.8M 0% /dev

tmpfs 95.8M 0 95.8M 0% /mnt/asec

/dev/block/mtdblock3 90.0M 82.7M 7.3M 92% /system

/dev/block/mtdblock5 295.8M 86.0M 209.7M 29% /data

/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin

/dev/block/mtdblock4 80.0M 28.6M 51.4M 36% /cache

After:

Filesystem Size Used Available Use% Mounted on

tmpfs 95.8M 0 95.8M 0% /dev

tmpfs 95.8M 0 95.8M 0% /mnt/asec

/dev/block/mtdblock3 90.0M 82.7M 7.3M 92% /system

/dev/block/mtdblock5 372.8M 112.7M 260.0M 30% /data

/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin

/dev/block/mtdblock5 372.8M 112.7M 260.0M 30% /cache

/dev/block/mtdblock4 3.0M 776.0K 2.2M 25% /dev/cache

Thanks again for finding and making this info available.
[myTouch 3G, Magic Android Development] eyegor:
You're welcome :)
[myTouch 3G, Magic Android Development] gader:
Yesterday I was trying to flash 6.35.08.29 radio zip in recovery.

I was unable to do this. I saw only something like this:

Writing radio

e:\ ... ?insuficient space? ...

and reset

Is it possible because the changed partition size?
[myTouch 3G, Magic Android Development] keinengel:
Yes, it's because of the partition hack. Just flash it from fastboot.
[myTouch 3G, Magic Android Development] eyegor:
Or first reflash the recovery. It will undo your custom partitioning.
[myTouch 3G, Magic Android Development] Serris:
ok I've been messing around with this for two hours, and phone just hangs on "HTC Magic" screen. I'm using RCMagic 4.2. I have set custom mtd to 175 and 3. I also tried the patcher from g1. nothing boots, and I have followed exactly all steps correctly. any ideas?
[myTouch 3G, Magic Android Development] eyegor:
Hmmm... I'm using it with stock 2.1 from Rogers and it works just fine. No idea....sorry :/
[myTouch 3G, Magic Android Development] wjsturgis3:
That's because the Smoki ROM already has partition remaping as part of the ROM. I guess you should post your question in that thread.
[myTouch 3G, Magic Android Development] Serris:
Well, I using RCMagic 4.2, so Smoki is no use to me, and I know that klothious, implemented partitioning into his rom.

Have you partitioned your RCMagic 4.2?
[myTouch 3G, Magic Android Development] Serris:
I found out that if I use both mtd patchers 1.5.2 from firerats thread, the phone boots, but it is not partitioned. This thing is so damn annoying.
[myTouch 3G, Magic Android Development] keinengel:
Have you set everything up before applying the patch? Patching before the first boot breaks it.

eyegor, what sizes do you use with stock?
[myTouch 3G, Magic Android Development] Serris:
What exactly do you mean by "Patching before the first boot breaks it." I have followed both eyegor's and firerats instructions (more than couple of times).
[myTouch 3G, Magic Android Development] keinengel:
I mean flash the ROM you want to use, let it boot for the first time and then try patching.

Could you please tell us what adb shell df spits out?
[myTouch 3G, Magic Android Development] Serris:
Default RCMagic 4.2

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 97756 0 97756 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 174080 153276 20804 88% /system
/dev/block/mtdblock5 169728 76448 93280 45% /data
/dev/block/mtdblock4 133120 20272 112848 15% /cache
/dev/block/mtdblock4 133120 20272 112848 15% /data/dalvik-cache

After recovery patch, nandroid restore and boot patch. MTD is set: cache 3mb, system175 mb.

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 3072 1168 1904 38% /cache
/dev/block/mmcblk0p1 7771284 6011448 1759836 77% /sdcard
/dev/block/mtdblock3 179200 153280 25920 86% /system

Trying to boot, stuck at "HTC Magic" screen forever.

Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 97756 0 97756 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 179200 153280 25920 86% /system
/dev/block/mtdblock5 294656 76456 218200 26% /data
/dev/block/mtdblock4 3072 3032 40 99% /data/dalvik-cache
/dev/block/mtdblock5 294656 76456 218200 26% /cache
/dev/block/mtdblock4 3072 3032 40 99% /dev/cache

I tried to patch stock rogers 2.1, and it works, but with RCMagic nothing.
[myTouch 3G, Magic Android Development] capychimp:
in rcmagic remove the dalvik cache script in etc/init.d

it moves dalvik to cache, hence your error
[myTouch 3G, Magic Android Development] Serris:
Capy, I can't thank you enough, I've been messing with this for days, and now it finally works. Thanks :)
[myTouch 3G, Magic Android Development] capychimp:
it's cause the rom is made for not using partition thingy, and it moves dalvik, so if your cache is only 3mb, dalvik doesn't have space and your fried ;) hehehehe not moving dalvik you keep it on data and you can make cache 3mb ;) and you have a rom running like it is meant to with dalvik the right place
[myTouch 3G, Magic Android Development] arfan1984:
@ Eyegor

i am using rogers official 2.1 by capychimp...i used ur method and it worked well...i put values 170 5...but now my internet browser just closes during browsing...is it due to small cache ? before editing my cache was around 70mb...pls reply
[myTouch 3G, Magic Android Development] eyegor:
your cache is bind-mounted to the data partition so basically it is not even bigger than before.
[myTouch 3G, Magic Android Development] arfan1984:
You mean to say that my browsing problem is not due to this partition hack?? Pls tell me in easy words..
[myTouch 3G, Magic Android Development] arfan1984:
@EYEGOR

Also i want to know that after doing 170 5 partition, any software at market which is greater than 5mb can not be downloaded. i get error of insufficient space...when i re-edit the matdpart.txt file to 170 15, and reflash boot partition, nothing happens. it shows the same space at "busybox df -h" command. i.e. 170 for system and 5 for cache...

pls reply
[myTouch 3G, Magic Android Development] eyegor:
Perhaps that ROM has dalvik-cache moved to /cache?
[myTouch 3G, Magic Android Development] eyegor:
Wow, you are right. I can't download big applications either!

This is odd, I could with other ROMs and this hack.
[myTouch 3G, Magic Android Development] blizard80:
if u don't bind cache u cant download in market anything bigger than cache partition.
[myTouch 3G, Magic Android Development] arfan1984:
What do i need to bind cache? how to bind cache? pls help
[myTouch 3G, Magic Android Development] eyegor:
the patches are supposed to bind cache automatically.
[myTouch 3G, Magic Android Development] blizard80:
you have to change init.rc for patch to work... and for that in stock rom's u have to modify boot.img...

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[myTouch 3G, Magic Android Development] eyegor:
Great.....

Isn't the patch supposed to edit everything automatically?
[myTouch 3G, Magic Android Development] blizard80:
i think the patch assumes that init.rc has the ability to start scripts from init.d directory... that the usual in Cyanogen's rom's and custom rom's. not in stock rom
[myTouch 3G, Magic Android Development] Serris:
Should we mention this to firerat and ibcoder? Maybe they could fix it.

EDIT: I have just tested it, and it works just fine on RCMAgic, I downloaded 15 mb file from market and have 3mb cache.
[myTouch 3G, Magic Android Development] Bladyle:
I use 175 3 when I install my Rogers 2.1 with root but, now I have problems with downloading larger apps from market. Can I change /cache settings without reinstall ?
[myTouch 3G, Magic Android Development] liderzre:
I use latest nightly from CyanogenMod.

D:\Goran\android-sdk-windows\tools>adb shell df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 98052 0 98052 0% /dev

tmpfs 98052 0 98052 0% /mnt/asec

/dev/block/mtdblock3 92160 87368 4792 95% /system

/dev/block/mtdblock5 302848 75464 227384 25% /data

/dev/block/loop0 4096 4096 0 100% /system/xbin

/dev/block/mtdblock4 81920 30248 51672 37% /cache

/dev/block/vold/179:1

1386860 909712 477148 66% /mnt/sdcard

/dev/block/vold/179:1

1386860 909712 477148 66% /mnt/secure/asec

/dev/block/dm-0 2088 832 1256 40% /mnt/asec/tv.justin.andr

oid-1

/dev/block/dm-1 19724 17416 2308 88% /mnt/asec/com.outfit7.ta

lkingtompro-1

/dev/block/dm-2 3124 1388 1736 44% /mnt/asec/com.cyxb.fishi

n2go_lite-1

/dev/block/dm-3 5200 3760 1440 72% /mnt/asec/com.fring-1

/dev/block/dm-4 2088 464 1624 22% /mnt/asec/com.agilesoftr

esource-1

/dev/block/dm-5 3124 2020 1104 65% /mnt/asec/com.facebook.k

atana-1

/dev/block/dm-6 2088 640 1448 31% /mnt/asec/com.imdb.mobil

e-1

/dev/block/dm-7 2088 744 1344 36% /mnt/asec/net.b92.androi

d.brisbane-1

/dev/block/dm-8 3124 1136 1988 36% /mnt/asec/com.dropbox.an

droid-1

/dev/block/dm-9 6236 5060 1176 81% /mnt/asec/com.google.and

roid.apps.maps-2

/dev/block/dm-10 3124 1784 1340 57% /mnt/asec/com.twitter.an

droid-1

/dev/block/dm-11 13500 11608 1892 86% /mnt/asec/com.navngo.igo

.javaclient-1

/dev/block/dm-12 4164 2736 1428 66% /mnt/asec/com.qo.android

.am3-1

D:\Goran\android-sdk-windows\tools>

What should i put in mtdpartmap.txt ?

95 85 ?

Thanks
[myTouch 3G, Magic Android Development] eyegor:
90 3

Or 95 3
[myTouch 3G, Magic Android Development] liderzre:
I see system 92160. But where to see cash size? (for future use ) . Thanks.
[myTouch 3G, Magic Android Development] eyegor:
/dev/block/mtdblock4 81920 30248 51672 37% /cache

Two lines under.
[myTouch 3G, Magic Android Development] liderzre:
I can resize cash from 80 to 3 mb whitout problems ?
[myTouch 3G, Magic Android Development] Bladyle:
After waste half a day to make this to work I give up. I can't make to bind-mounted automatic, so can't download big files...I will use 15mb for cache
[myTouch 3G, Magic Android Development] camapghe:
My nooby question is, what is the benefit of increase cache size?

EX: recommended setting is 90 2, what is the benefit of 90 3 or 90 4? I'm quite blur about this part.
[Vibrant Q&A, Help & Troubleshooting] deku_nut:
I'm hoping this won't get me yelled at for posting this here but here goes.

My vibrant came with swype, which I enjoy from time to time. I tried to pull the APK to put on my mytouch which has cm5.0.8 (i use it with a t-mobile prepaid card with barnacle for cheap mifi) and when I install the apk every single running process on the phone FC's (from core processes to setcpu and cmupdater) to the point where I have to wipe and reflash the cm5.0.8 zip.

any suggestions?

thanks!
[Vibrant Q&A, Help & Troubleshooting] adm1jtg:
I have another thread trying to get the droid x skype running on the vibrant as it has the voice icon in it and the vibrants version does not. Bottom line is you cant just install it as an app as you found out. It appears there is more to it then just the apk file. If the person I am working with on this is able to figure it out I will post the results in my thread just search on voice swype or my name
[Vibrant Q&A, Help & Troubleshooting] deku_nut:
Awesome, what's the thread?
[Desire General] AwHughes:
Hello,

I am willing to offer someone 20USD if they can tell me how to fix my HTC desire. I was running on a Asia ROM which was upgraded to a Euro one so i could update. Upon updating to 2.2 I have no wifi, or SD and "process system" keeps crashing

The details of the phone are:

Model A8181

OS: 2.2 (from OTA)

Baseband: 32.36.00.28U_406.00.02_2

Kernel: 2.6.29-0cb9f166

Build is 2.09.405.8

Please Help Me.
[Desire General] flakz0r:
You need to flash the newest radio, should fix all your problems. :)

You're using a radio from eclair (2.1).
[Desire General] ratykat:
With the 2.2 ota, im not sure if there is a way to downgrade, as I read one of the devs accidentally upgraded to an OTA release. This is due to the bootloader being updated to one that hasnt been hacked yet.

My 2 cents is hold tight and hope one of the devs figures a way to downgrade, that way you could install a custom 2.2 which doesnt have these issues.

Good luck, sorry i couldnt be of much use :/

EDIT- i completely missed that flakz0r lol, can it still be flashed through recovery if he used a 2.2 OTA update? if so http://android.adamg.co.uk/bravo/radio/32.43.00.32U_5.09.00.20.zip :)
[Desire General] Pyr0x64:
you still have the older 2.6.29 kernel too

flash the radio to the latest and flash one of the 101 roms people are releasing based on the new ota 2.2 as that should update your kernel
[Desire General] noble8:
Did you download the ota update, or have you got root and installed one of roms on this forum? If it's ota I dont see how your radio can be the one you've stated. If it's a rom from the forum flash the new radio 32.43.00.32U_5.09.00.20.zip
[Desire General] flakz0r:
I dont know, but it should be possible. Also, the official OTA update comes with the new radio, so i dont understand how he was able to update the rom but not the radio. That is assuming he isnt rooted, of course. :)
[Desire General] abc27:
I just fixed something like this today. It's a bit of an involved process though. Send me a pm so we can talk via IM.
[Desire General] NeoPhyTe.x360:
+10 .
[Desire General] flakz0r:
Yeah, you just need the radio. Put it on your sdcard and flash it like you flashed the rom. Dont touch your phone, let it work, takes a while.
[Desire General] Darkzen15:
so....who got the 20 dollars?
[Desire General] casca:
lol i think it should be falkz0r he was the first to provide a solution...

btw...he managed to go from asian to european version through goldcard and the RUU file. Done that to my previous Hero too.
[Desire General] hensk:
not me ,I have seen this thread right now :D
[Desire General] abc27:
Me :D

I got him through the entire process using teamviewer and MSN. Still haven't got the $20 though....

And flashing a radio isn't a solution :p
[Desire General] abc27:
Wouldn't have worked.
[Desire General] flakz0r:
Wasnt expecting to receive anything, XDA is a place to share knowledge and help each other. I expect people to help me too when i'm in trouble. :)
[Droid Eris Q&A, Help & Troubleshooting] jonblackwell:
Does anyone know how to modify Rosie/sense to get the zoom transitions to look like the stock launcher rather than the boring swipe they do?

Kaoslengendary rom as the zoom transitions, I've tried taking Rosie.apk from that and putting it on my plainjane rom but ruins the phone/apps buttons.

Thanks!
[Droid Eris Q&A, Help & Troubleshooting] homewmt:
Use a different launcher such as launcherpro
[Droid Eris Q&A, Help & Troubleshooting] truelove79:
Wait until there are more and better versions of ROMs with Espresso Sense. That version of Sense has zoom transitions.