yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] bigbiff:
Any answer for the new amon ra 2.1.1? :)
[EVO 4G Android Development] Firerat:
use clockwork
[EVO 4G Android Development] -viperboy-:
Great, thanks so much! This needs to go into the OP!!
[EVO 4G Android Development] bigbiff:
Heh, I am using Amon RA 1.8 with the mod.
[EVO 4G Android Development] freeza:
Stuck on splash with new amon recovery 2.1.1
[EVO 4G Android Development] Nyckrs:
so this mod only works on clockworkmod recovery?
[EVO 4G Android Development] Firerat:
nope

but I know it works with clockwork, and older RA recoveries

'stuck'

doesn't tell me anything useful, and as I don't have an Evo I can't replicate to figure out what the problem is.

I suppose I could disect RA 2.1.1 and try and figure it out , but I'm busy with other things

no doubt someone smart will come along and resolve the issue, or at least give something more useful than 'stuck'

until then, use what works.
[EVO 4G Android Development] DroidGnome:
In step 3 of the uninstall process you mention:

1) Should we already have a recovery.img from somewhere previously, or does your patch backup the original as that filename? (If it backs up, what if recovery.img already exists on the SDCard, will it overwrite, or rename?)

2) I'm assuming that the code you listed isn't something you type, but a series of menu options, correct? As in "Fastboot --> Flash --> Recovery, then select the Recovery.img file" ?

Just want to make sure I understand ALL the steps before I attempt this on my Evo. I haven't used the fastboot menu since I originally rooted my evo months ago, so I'm not positive what I might have done with my recovery.img
[EVO 4G Android Development] SteelH:
Reboot your phone into fastboot mode (power off, then power on holding vol down, you'll see fastboot as a choice IF you have the ENG bootloader 0.76). Then you issue the fastboot commands from your PC, fastboot is not recovery (and thus you wont see that in the RA or clockwork). The recovery image to be flashed needs to be in the same dir as fastboot.exe You do not put the recovery.img on /sdcard.
[EVO 4G Android Development] DroidGnome:
I finally figured out my problem.. for whatever reason, I had installed just ADB onto my PC (I think it was part of an HTC or rooting package I used)... I did not have the full Android SDK, which is what includes Fastboot.exe in it's tool folder.

Installed the SDK (After first installing the JRK it requires) and found the fastboot.exe , going to try this now.. hopefully this will give me more space and solve the issue we've been discussing in your ROM thread :)
[EVO 4G Android Development] SteelH:
Make sure you have the correct HBOOT, only 0.76 supports fastboot commands...
[EVO 4G Android Development] DroidGnome:
I do, I've one of the original Evo's from day 1 release, so I never updated my Hboot or anything. Also the scripts seem to work GREAT with your ROM, though I did modify the default sizes to 275/75 instead of the default 250/125.
[EVO 4G Android Development] SweepinJR:
So I've been using this with my hero for a while now, and I've loved it. When I bought my evo last night I was happy to see it working with this phone too.

So here's what I did. Rooted. Flashed my rom, flashed my kernel, flashed gapps and vvm. Root uninstalled all the junk I didn't want. Installed everything I did want.

Then used df -h to see that my system partition was using 119mb and cache was currently using 36mb.

I created a text file using mtd 120 45...i feel I was generous with the 45 cache, I prob coulda used 40. Copied that txt and the zips to sdcard.

Next I boot to recovery, do a nandroid backup. After that wipe everything and run the recovery zip. Wipe all again and use adb shell to reboot recovery.

Once back in recovery, do a nandroid restore, flash the boot zip, and reboot! You can see my results in my sig.

From my Evo 4g on Tapatalk
[EVO 4G Android Development] SweepinJR:
RA 2.2.1

From my Evo 4g on Tapatalk
[EVO 4G Android Development] freeza:
Interesting.......I don't get why it's not working for me. It worked fine when I had RA 1.8

RA 2.2.1 and now 2.3 test04 with netarchy's 4.3.2 sbc kernel and a custom 3.70 ROM

Does busybox have anything to do with this mod?

I just troubleshooted an issue with DTApps2SD not working because of busybox version. It'd be interesting to know if busybox of bash had anything to do with this working.

Can someone verify that this is working with at least somewhat of the same combination:

newest radio

newest wimax

hboot 0.76

pri 1.77

nv 1.90

any sense rom (3.70)

ra 2.3 test04

netarchy 4.3.2
[EVO 4G Android Development] SweepinJR:
Sense roms are usually pretty large, what partition sizes are you trying?

I would flash ra 2.2.1 and try starting fresh. This should not be affected by any firm ware or roms.

From my Evo 4g on Tapatalk
[EVO 4G Android Development] Firerat:
DTApps2SD is crap
[EVO 4G Android Development] SweepinJR:
Okay so i have a question. Is the 40mb cache partition really necessary? I was using 2-4mb cache on my hero. Does the evo just need more cache space?

From my Evo 4g on Tapatalk
[EVO 4G Android Development] freeza:
whatt! I love dtapps2sd.

I'm going to try this mod again today and try and give better information if it doesn't work :-D
[EVO 4G Android Development] freeza:
I'm using 255 150 and they worked fine before flashing the new recovery.
[EVO 4G Android Development] freeza:
Well, whatdoyaknow... 2.3 test04 works with the mod! :D
[EVO 4G Android Development] Firerat:
then you are a fool
[EVO 4G Android Development] CaptainMorgan:
Well, I get a report of 6MB of cache used, so 2-4 won't cut it. But, Im on MIUI rom, may use more cache than another. I'm thinking 20MB though would be more than sufficient.
[EVO 4G Android Development] SweepinJR:
The hero running AOSP roms would run on 2-4 just fine.

Right now my phone shows that it is using 31MB of the 40MB cache I have. Guess there's just a huge difference between the phones and roms.
[EVO 4G Android Development] SweepinJR:
So question.

Now that I am running MikFroyo, I had run a2sd nocache to move dalvik to /data and to troubleshoot some other issues, which just ended up being a wrongfully deleted apk.

Since I did that, I created a 4MB cache partition and restored my nandroid over it.

Now, a df -h output shows the cache partition and data partition to be the same partition.

So the question is...is everything okay like that, or should I revert back to having dalvik on /cache and re-do my partitions again?
[EVO 4G Android Development] thorracing1:
Does it work on evervolv
[EVO 4G Android Development] SweepinJR:
I guess using my phone all night has answered my own question. Everything is running good so I guess I'm golden.

From my EVO 4g Tapatalk
[EVO 4G Android Development] DroidGnome:
Well I cannot comment on the 'df -h' output, no clue what that is.. but I can tell you two things.

A 4meg cache is probably going to cause you some headaches with application updates from the market. Unless you've also managed to get your market to use another location for temporary downloads, it uses the /cache by default. Since apps can now be up to 50megs in the market, you'll want a cache of at least that size to accomidate any large apps. (Angry Birds for examples is approx 23-30 megs, depending on the version). I did the same thing you did a while back and had nothing but headaches. Leaving the dalvok on the cache will also give you the same issue, if there is not enough free space leftover.

However.. I can tell you that I run MikFroyo as well, 4.4 version. And have partitioned mine as System = 225, Cache = 100 (leaving approx 612 for data ). I moved the dalvik to the cache via the A2D -nocache command. (see mikfroyo thread for info). I'm also using a 1gig ext3 partition as my app partition with A2SD that's built into MikFroyo. Not a single issue with my device that I've found. (Though I turned off zipalign at boot to speed things up a bit. I just run it every so often manually if I'm installing new apps)

Hope that helps your decisions.
[EVO 4G Android Development] SweepinJR:
One of the first things I did was install angry birds from the market...no issues.

From my EVO 4g Tapatalk
[EVO 4G Android Development] DroidGnome:
Interesting.. I wonder where it downloaded the temporary file to since your cache is clearly not large enough for it. Are you running any other scripts that move your market's cache files somewhere else? (I had tried some early scripts but they did not function properly).
[EVO 4G Android Development] SweepinJR:
That'd what i was talking about. My 708mb data partition has somehow become my cache partition as well.

The 4mb specified in my mtdpartmap.txt doesn't appear to exist at all.

From my EVO 4g Tapatalk
[EVO 4G Android Development] DroidGnome:
Hmm i never took either of the two partitions specified in mtdpartmat.txt below a 2 digit number. I once had something like 250 75, but that was the lowest I went. Perhaps the script didn't know how to handle the single digit and did something 'odd'??

Maybe make a Nandroid, up the cache to say 10 and see if it comes back? Though from your postings, perhaps it isn't really an issue at all :)

I never understood the separate partitioning terms for /system, /data and /cache as they are really nothing than folder shortcuts and not true partitions like ext3/ext4 etc.. and since they are all part of the same FAT partition, why lock out the space.. (Unless they were worried people would FILL the entire /data partition somehow.)
[EVO 4G Android Development] SweepinJR:
I ran 2mb on my hero with cm6...

I just tried pushing it up to 80mb, didnt make a difference.

Everything operates fine so im going to ignore it

From my EVO 4g Tapatalk
[EVO 4G Android Development] soundwavedj:
Guys I need some help. I can't change the partition sizes. I edited the values in the text file and flashed the boot image and no dice. I even repeated the installation steps last night as well and same values were there from the original installation. Any help would be much appreciated. Thanks
[EVO 4G Android Development] :
You are doing something wrong then.

Where are you saving mtdpartmap.txt? also mtdpartmap.txt is read when flashing the recovery zip. Your new partitions sizes are available once you format and reboot recovery.
[EVO 4G Android Development] soundwavedj:
I save iit right to the root of the SD. I edited the file to change the size and flashed the boot file. When that didn't work I followed the steps off the first post when I originally installed it. It installed perfect for a sense Rom so I'm not sure what is wrong.
[EVO 4G Android Development] SweepinJR:
1. Boot to recovery

1b. Since you're having issues, at this point I suggest you reflash your recovery img, and reboot into recovery again. I keep the PC36IMG.zip on the root of my SD and just boot into bootloader and let it run the flash.

2. Wipe everything (in the EVO world there is Calkulin's format all zip that works nice)

3. flash the mtd recovery zip

4. Wipe everything again

5. use ADB shell to reboot into recovery.

6. flash rom, or restore nandroid (whichever you're doing)

7. flash mtd boot zip

8. reboot and enjoy
[EVO 4G Android Development] soundwavedj:
This worked and I think reflashing the original recovery worked. Thanks alot!

So basically whenever I change partition sizes like for example increasing system size to account for a sense rom I have to just edit the text file and reboot or reflash the original recovery and repeat the steps above?

Sorry ...long question
[EVO 4G Android Development] SweepinJR:
You shouldn't have to flash the recovery each time. All that really does is flash the partition sizes back to factory.

But, that said, I've had the best luck with the EVO if I flash the recovery between MTD Partitionings.
[EVO 4G Android Development] :
This is correct.

Anytime you change mtdpartmap.txt you have:

1) Make/save changes to mtdpartmap.zip

2) flash firerat's recovery zip

3) Follow on screen instructions on what to format (/system, /data, /cache)

4) Reboot recovery ('adb reboot recovery' works wonders)

5) flash new ROM, gapps, kernel, etc -- or restore nandroid.

6) flash firerat's boot zip (this must be the last thing you flash before rebooting)

Win.
[EVO 4G Android Development] SweepinJR:
We were referring to reflashing the recovery image each time before flashing the mtd recovery zip...but yeah.

From my EVO 4g Tapatalk
[EVO 4G Android Development] Mich2Ga:
Very easy to do, install & uninstall...
[EVO 4G Android Development] :
You posted: "You shouldn't have to flash the recovery each time."

I posted "This is correct". Then I went on to post a mini guide.
[EVO 4G Android Development] soundwavedj:
Anyone out there have a link for a good "how to fastboot " video or instructions. Thanks
[EVO 4G Android Development] Just_s:
Changing Recoveries?

So here's a new question (might be obvious, but I'm unsure.)

If I flash a new recovery, say from Ra to Clockwork or Ra 2.2.2 to Ra 2.3, that will undo everything in this tweak correct?

And if I decide to not redo the tweak, I can just take the files off of my SD and go on my merry way correct?

Or do I still need to:
[EVO 4G Android Development] Firerat:
best way to upgrade is to flash the new recovery in recovery, then flash the recovery patcher

you must use the command line

adb shell mount /sdcard
adb shell flash_image recovery /sdcard/recovery.img

or create a flashable zip

these are not compatible with your phone ( they are for G1 )

http://www.mediafire.com/?eufe1p61c8pny

unless you replace the recovery.img in the zip and resign ;)

you can create your own flashable zip from an img file by using AutoMTD_partitionPatcher script , just point it at the .img ( requires linux )

Advantage of the zip is, its easy you just flash it , and reboot
[EVO 4G Android Development] freeza:
Is there anyway we can use the DEV partition with this mod?

It's like 215 MB and only 8 of it is used!
[EVO 4G Android Development] tempe38:
Is this supposed to work with a specific recovery? I'm on the latest version of Clockworkmod but it wouldn't flash the format all zip so I flipped to Amon Ra. Everything seemed to work flashing but then my phone got stuck on the white HTC screen booting up. I had to flash back to clockworkmod and reload the nand backp I made to get booted again. Or is this one of those things that takes a really long time to boot the first time?
[EVO 4G Android Development] TheNewGuy:
I am a big firerat fan and used this for my G1....now I have a G2 and I was wondering....since you can modd it to work on the evo 4G..is it possible to modd it for the G2?
[EVO 4G Android Development] frickinjerms:
700mb of available space on cm7.0.3.1?

well don't mind if i do :D

no issues whatsoever on amon ra 2.3 with stock cm kernel

hmm hickup... editing the mtdpartmap.txt file and then rebooting into recovery and reflashing cm and the boot patch doesn't resize my partitions to the new values added... so i need to flash the recovery patch everytime as well?
[EVO 4G Android Development] helljumperx:
This didn't work on my phone and now my 32gb sd card is slow as hell for transfering stuff from computer to sdcard.

how do you do this part?

"Reflash custom recovery console using Fastboot

Code:

Fastboot flash recovery recovery.img"

i need every step to fix this please. don't be vague.
[EVO 4G Android Development] :
This mod does not modify, touch, or even know your SD card exists. This mod did nothing to your SDcard.

Since you don't know what you are doing, just reflash your recovery from ROM Manager off the Market. You can flash Amon_RA (at the bottom) or ClockworkMod.
[EVO 4G Android Development] helljumperx:
okay, so then the partition mod of my sd card probably slowed it down then correct? how can I reformat my sd card from scratch with no partitions or anything?
[EVO 4G Android Development] :
What kernel are you using? There is a known issue with the following kernels that cause slow SD transfers that you are talking about.

CyanogenMod 7 stock kernel (2.6.37)

Tiamat 3.x & 4.x (2.6.37 & 2.6.38)

SavagedZen all versions that I am aware of (1.x, 2.x)

Toast's Kernel (2.6.38).

The current workaround is to use the recovery to 'mount usb' or 'usb-pc' and use that to transfer files.

Netarchy's kernels for Sense based ROMs do not exhibit this behavior because they are older.
[EVO 4G Android Development] helljumperx:
oh okay, well I'm using savagedzen. so that is probably my problem then.
[EVO 4G Android Development] helljumperx:
actually, its still going slow....

is it because i messed with trying to set up ap2sd and partitioned my sd card? how can I undo that?
[EVO 4G Android Development] clark44:
What sense ROM does this work with??
[EVO 4G Android Development] soundwavedj:
I've used this on a bunch of sense roms with no issue. The newer 2.0 and 2.1 I haven't cuz the Rom files are so big that it wouldn't make too big of a difference. Hope that helps
[EVO 4G Android Development] XsMagical:
Nice tool, thanks for the info
[EVO 4G Android Development] augoza:
So, i did it. Cool. Thanks calkulin! One question, if i flash a new rom or kernel do i flash that zip right after or does it matter?
[EVO 4G Android Development] stephen240:
So I'm trying to flash a kernel then the mtd. Tiamat Kernel.

After I flash the kernel and the MTD and reboot I'm stuck in fastboot? WTF?

Help please!
[EVO 4G Android Development] sw99:
Quick question...before I found this I had previously been using titanium backup to move apps into the system partition, thus freeing up the data partition. Is there any downside to doing this other than needing to use TB to merge updates to these new system updates?
[EVO 4G Android Development] stephen240:
Okay it only happens when I flash the Tiamat 4.0.4 kernel then the MTD. If I flash MIUI with the stock kernel it works fine.

Any thoughts?
[EVO 4G Android Development] eurominican:
Thank you Calkulin! Just did the mod lets see how it goes.
[EVO 4G Android Development] augoza:
Whenever i flash a new rom i always to a FORMAT ALL. Even though i do that i still just need to flash the FR_BOOT, or do the whole installation process again? thx
[EVO 4G Android Development] vudu:
Just the boot file. The format all does not touch the recovery.
[EVO 4G Android Development] block:
does this work for the newest rooted android update? I started the process and got to format_all.zip and it gave me an error...??
[EVO 4G Android Development] mattykinsx:
I don't know whether support for this is dead or not but I notice that, no matter which recovery it is, if you patch it you cannot successfully flash anything related to Radios, Hboot, NV, PRI via a .zip (such as, but not limited to, these)...

Thus the only way is to either do it via the hboot or to reflash a non-modified recovery and then flash a zip. (Obviously the second method means you have to redo this whole process in order to use the modified partitions.)

I believe it's related to how these flash as they obviously write as a zip and then run on a reboot.
[EVO 4G Android Development] DroidGnome:
Custom Partition on Gingerbread?

Ok so I've used this quite a bit on my Froyo ROMS (all MikFroyo builds with minor mods), but I'm wondering if anyone's tried this yet on a Gingerbread ROM?

I'm still setting GB up on my phone at the moment and before I go and try to mess with things I figured I'd ask.

Unfortunately the Rom I use (MikG) uses almost all of the /system partition already, so all I can steal from is the /cache.

Why did Gingerbread increase the /cache partition to 160 megs! I never see it used, so thinking of dropping it back down to 75 like I had in Froyo.. thoughts?
[EVO 4G Android Development] piscesjoey:
Someone in the Synergy thread mentioned he been using 350 50 and it was all good
[EVO 4G Android Development] yznhmr:
Seems like now my Activesync to my exchange server wont work now.. With SynergyRC1

I have no idea how to fix it now..

I have deleted the Account and rebooted and reset it up, but it still wont sync.. gives me errors..

BTW i was one of the 2 who mentioned 350/50

edit 2:

I have redone the process, including wipe all again, and then wipe each manually 2x (data, cashe, Delvvic), the reloaded the nand, then the boot file.. and now all is good.. I believe.. ( i am having some issues.. not sure if its related to this or not)
[EVO 4G Android Development] Jfree3000:
Never mind, somehow figured it out.
[EVO 4G Android Development] vasiaeva:
One not answered question " how to find out how much system/cash memory my rom using???
[EVO 4G Android Development] panamakid:
download Quick System Info
[EVO 4G Android Development] Adam1422:
Sorry for the stupid question but if I am running synergy what should my memory settings be?
[EVO 4G Android Development] Jfree3000:
350 50, left me with 433MB of free space with 30 or so apps installed.
[EVO 4G Android Development] panamakid:
same settings for me.
[EVO 4G Android Development] ro_bro:
using adb, do the following command:

df -h
[EVO 4G Android Development] ro_bro:
I just thought I'd clarify a bit from the original post, since the steps that I take work for me:

Install

1. Copy FR_Boot_CustomMTD_v1.5.7b_for_EVO, FR_Recovery_CustomMTD_v1.5.7b_for_EVO, FORMAT_ALL zips(& custom mtdpartmap.txt if you want to change the default sizes) to your SD card

2. Reboot into recovery

3. Make a Nandroid backup if you didn't already

4. Format cache, data & system partitions using my FORMAT_ALL.zip for ease

6. Flash FR_Recovery_CustomMTD_v1.5.7b_for_EVO.zip(this patches the recovery to use the custom partition sizes)

7. Reboot into recovery again -- Here, I choose 'reboot' from the recovery, press the power button and immediately press and hold the 'volume down' button. This makes it go into the white bootloader screen. There, I choose 'recovery' and press the power button again to reboot into recovery.

8. Restore Nandroid backup or flash new ROM but don't reboot

9. Flash FR_Boot_CustomMTD_v1.5.7b_for_EVO.zip(this patches the kernel to load the custom partition sizes)

10. Reboot

Additional things to consider:

If you are switching ROMS and the ROM sizes are significantly different (for ex., going from an AOSP ROM like CM7 and then going into a huge Sense based ROM), you will have to follow all the steps again. You CANNOT just change the values in mtdpartmap.txt and then just flash the FR_Boot_CustomMTD_v1.5.7b_for_EVO.zip file and boot. I've tried this multiple times, it does not work. You have to go through the WHOLE process again.

Yeah, that makes switching ROMs more of a pain for you flash-a-holics if you switch back and forth from Sense. I usually just flash between AOSP ROMS, so I keep it at 160/90.

Also, for those of you asking if it matters what ROM it is, etc, it does not. Think of it like this. If you have a certain amount of water, and your water bottle is big and has a lot of additional space, you can use a smaller water bottle to hold that water. You're just trying to increase/decrease the size of this "water bottle" for your system and cache essentially, so that more space is available for your 'data' partition, which is where your apps are stored.

You will only have problems when you try to hold a lot of water in a container that can't fit it.

attached is a screenshot of what I see when I run "df -h" via adb

Hope this clarifies things and helps others.
[EVO 4G Android Development] vasiaeva:
Thanks man !!
[EVO 4G Android Development] Dozenboy0012:
Anyone able to get this to work on Synergy? I cant seem to get it to work?
[EVO 4G Android Development] block:
I did all the steps now my phone wont boot past the htc evo white screen
[EVO 4G Android Development] Jfree3000:
Yeah I am running this on Synergy now, change the script to 350 50 and try the process over again, should work.
[EVO 4G Android Development] barry.bishop72:
just got through dealing with that for 2 days (although I did repartition my sd card as well so maybe the two together did something). I had to reflash a recovery image and made sure I had the latest version of Amon. Everything worked fine after.
[EVO 4G Android Development] droiddawg:
This is genius
[EVO 4G Android Development] scottx .:
Works great! Awesome!

HTC Supersonic 004 - MIUI 1.7.15 - Tiamat v4.0.5-SBC - Amon_RA

Some 'df -ah' love: