[mod] [2011-03-22] TPT NAND Backup & Partition Tool - alpha3 [Gen1]

[Guest Fok@]

Hello,

I can confirm that the alpha 3 is working fine on FLB r11. I have installed without wipe and I haven't lost anything. I got around 70MB extra space.

[Guest wbaw]

OK am I right in thinking I do it in the following order:

- Flash attached zip

- Install by doing the VOL + Method

- Install ROM of choice (CM7)

or do you do it this way:

- Install ROM of choice (CM7)

- Flash attached zip

- Install by doing the VOL + Method

If its the second method I take it you do it after a fresh install of your ROM before installing Apps etc??

The second method & no you don't need to do it after a fresh install.

It will backup your current rom, all your apps & data, then the last step vol + & power on flashes it all back to your phone with updated partition sizes.

[Guest ak167777]

sorry, wanner ask a noob question ~^^~

I have installed r12 and without partition my sd card (ext3) before.

Is it required to format and partition my sd card with ext3 before apply the blade_backup_alpha3-cache-auto-10.zip?

thanks ^^

[Guest rak007]

Hello,

I can confirm that the alpha 3 is working fine on FLB r11. I have installed without wipe and I haven't lost anything. I got around 70MB extra space.

Can you tell me exactly which file did you use to flash ??

[Guest Schwinni]

Is it required to format and partition my sd card with ext3 before apply the blade_backup_alpha3-cache-auto-10.zip?

No, no need to have an ext partition on your SD card. The calculated image files will go to the image folder on your SD card (FAT partition).

[Guest xzyk]

Hi, need some help please.

I've read all the posts and cannot find an answer to this; unless i misunderstood something.

Anyway, after completing alpha3, which went all fine, I end up with the expected 2mb on my system cache. This is causing me problems installing updates like Go SMS, which is 2.2MB in size. It simply fails.

Quick Info is reporting system cache correctly as 2mb with only 892KB free. I also did try reboot to free up more cache to no avail.

Is there a quick easy way to simply increase this 2mb system cache to something more workable like, say 4 or 5MB ? without having to do restores ?

This is on JJ9 with a2sd.

thanks for any help.

Edited March 24, 2011 by xzyk

[Guest Schwinni]

Is there a quick easy way to simply increase this 2mb system cache to something more workable like, say 4 or 5MB ? without having to do restores ?

This is on JJ9 with a2sd.

thanks for any help.

Try to install cache2tmpfs_blade_froyo_signed.zip linked in the first post.

[Guest wbaw]

Try to install cache2tmpfs_blade_froyo_signed.zip linked in the first post.

Yeah, that will fix it.

The backup script should automatically do it, but maybe it didn't work properly.

No point in having a 5mb cache size, because some apps are bigger than that & they'll fail to install, so it's all or nothing for cache size.

The cache2tmpfs patch will redirect the app install cache to a temporary ram partition, so you keep more space on your nand & apps install a little faster too.

Edited March 24, 2011 by wbaw

[Guest xzyk]

Try to install cache2tmpfs_blade_froyo_signed.zip linked in the first post.

Thanks, that worked fine. Quick Info now showing 42MB system cache and the 2.2MB GoSMS update downloaded fine, so all is well.

I think think this happened because after generating the partitioned zip, following the execution of blade update, i then replaced the boot, userdata and system img files (to keep all my settings, apps etc..) before executing the partitioned zip.

Edited March 24, 2011 by xzyk

[Guest wbaw]

Thanks, that worked fine. Quick Info now showing 42MB system cache and the 2.2MB GoSMS update downloaded fine, so all is well.

I think think this happened because after generating the partitioned zip, following the execution of blade update, i then replaced the boot, userdata and system img files (to keep all my settings, apps etc..) before executing the partitioned zip.

It did.

The boot, system & userdata .img files that it generated were a backup of your phone, they already contained all your apps & settings, plus the patch for the small cache partition. That's the whole point of the script.

If you install another froyo rom, you'll need the patch again.

Edited March 24, 2011 by wbaw

[Guest xzyk]

It did.

The boot, system & userdata .img files that it generated were a backup of your phone, they already contained all your apps & settings, plus the patch for the small cache partition. That's the whole point of the script.

If you install another froyo rom, you'll need the patch again.

yes, thanks wbaw. I've slapped myself on the wrist, lesson learnt !

thanks for a great utility, it will greatly help people like myself who like loading a lot of apps. :D

[Guest rak007]

I am facing an issue quiet similar to what xzyk faced. Itried updating Titanium Backup (around 1.2 MB) and Documents to Go (Around 4.7 MB) separately and in both times they error out with "Installation Unsuccessful". What seems to be the issue ?

Quick Info does show the cache as 42MB and free as 40.60 MB :S

Edit: Just tried downloading "Fruit Ninja Kaka valentine" which is around 2.93 MB and it worked fine. Not sure why earlier ones failed. I will try with some other app too which is even more in size and see what happens.

Edit2: It works fine. Not sure why the above mentioned apps are not working. Just updated a 13 MB opera installation properly.

Edited March 25, 2011 by rak007

[Guest Rotmann]

I am facing an issue quiet similar to what xzyk faced. Itried updating Titanium Backup (around 1.2 MB) and Documents to Go (Around 4.7 MB) separately and in both times they error out with "Installation Unsuccessful". What seems to be the issue ?

Quick Info does show the cache as 42MB and free as 40.60 MB :S

Read the instructions again and the solution for xzyk. If you don't follow the instructions how do you want it to work?

[Guest reluctant_traveller]

Could someone host the latest files temporarily? My corporate firewall blocks all access to sites like box.net, mediafire, rapidshare, dropbox etc etc.

Or perhaps be willing to e-mail me the files?

EDIT: Agh, it passed my mind that I could use my blades browser itself to download them.. let me see if that works first!

ZOMG EDIT: what a moron, just realised I could click the direct links to the files stored on Modaco's server rather than clicking the mirror links!! To think I have already downloaded countless ROM images from here already.. doh

Edited March 25, 2011 by reluctant_traveller

[Guest iKrautDroid]

263 MB free on kallt_kaffee's Swedish spring.

Great! :D :D

[Guest rak007]

I am currently on FLB r11b and may be shifting to SS RLS3 or whatever is latest when i actually switch.

I have currently used this Mod to repartition my internal memory and as a result have more than 250MB of Data memory.

Do i need to do anything prior to installing the new ROM or correct me if i am wrong, but i think i should do the following

1. Take a Nandroid backup of my current ROM

2. Install SS ROM

3. Do a full wipe

4. Boot into new ROM

I am expecting that all the things that the MOD must have done to my internal memory are resetted at this point and i need to apply the patch again to get more Data memory for my apps to install on internal memory.

Is my understanding correct ??

Edited March 28, 2011 by rak007

[Guest css771]

I had used this mod while on cm7 and have a 3mb cache and /system with 10MB buffer space.

Flashed ss rls3 after complete wipe with the last few lines from the init.qcom.post_boot.sh script appended to the file already in SS (since kk has made some freq changes there); adb install and direct apk install would restart the phone. So flashed the cache2tmpfs script through recovery. But then phone wouldn't boot. So did a full wipe and reinstalled again with the stock init.qcom.post_boot.sh from SS and all market installs and other installs seem to be working fine.

Edited March 28, 2011 by css771

[Guest womble_sanfran]

I am currently on FLB r11b and may be shifting to SS RLS3 or whatever is latest when i actually switch.

I have currently used this Mod to repartition my internal memory and as a result have more than 250MB of Data memory.

Do i need to do anything prior to installing the new ROM or correct me if i am wrong, but i think i should do the following

1. Take a Nandroid backup of my current ROM

2. Install SS ROM

3. Do a full wipe

4. Boot into new ROM

I am expecting that all the things that the MOD must have done to my internal memory are resetted at this point and i need to apply the patch again to get more Data memory for my apps to install on internal memory.

Is my understanding correct ??

I have a feeling your understanding is WRONG, as far as I know Swedish Spring doesnt have a TPT image so hence you just install SS ROM and then the ramcache patch and you are running eith the extra data memory.

[Guest Smiff2]

ok so i'm upgrading from FF (2.1) with stock partitions to SS RLS3 (2.2).

should i flash this (blade_backup_alpha3_cache_auto_10) before or after flashing SS? obviously i'll be doing a full wipe.

the "calculates based on your current ROM" has me thinking i should wipe, flash SS and THEN use this. is it ok to do all this in one session of clockwork, no reboots in between?

Edited March 28, 2011 by Smiff2

[Guest wbaw]

ok so i'm upgrading from FF (2.1) with stock partitions to SS RLS3 (2.2).

should i flash this (blade_backup_alpha3_cache_auto_10) before or after flashing SS? obviously i'll be doing a full wipe.

the "calculates based on your current ROM" has me thinking i should wipe, flash SS and THEN use this. is it ok to do all this in one session of clockwork, no reboots in between?

All correct, do this after you install a rom. you can do it all in one session of clockwork, wipe data, install rom, run blade backup, then tpt install it. if you press & hold vol+ straight after you've finished in clockwork & pressed the home button to reboot it, then you can go straight into tpt mode & install the new partitions straight away.

Since you're upgrading to a 2.2 rom, you'll be ok to use the nocache version & get an extra 40mb space compared to the cache version.

Before you start, charge the phone fully then power it off, remove it from the charger, leave it for 30 seconds, then power on with vol- to get into clockworkmod. Sometimes clockworkmod can be a bit buggy if it's been started from a reboot, rather than a cold boot, or if it's plugged into a charger or usb.

Edited March 29, 2011 by wbaw

[Guest Smiff2]

thanks very much wbaw!

actually i was going to avoid the nocache version because i'm worried about creating problems for someone else in the future if she ever changes ROM again.. i don't think she'll run out of space since she's been ok on FF 2.1 + 2.2 already has the automatic move to SD feature + the 128MB system partition :D

[Guest rak007]

So when i tried to directly install SS RLS3 over current FLB r11b, the cache got screwed up as in, in quick info it showed only 2 MB and hence as expected market stopped working (not completely, as in bigger apps were not getting downloaded)

So i ran the zip which made the cache and other partition sizes as stock and then flashed the SS RLS3 again and then again ran the nocache zip and it worked like a charm. Getting more than 260 MB free on SS RLS3

Thanks wbaw for your super efforts.

[Guest targetbsp]

So when i tried to directly install SS RLS3 over current FLB r11b, the cache got screwed up as in, in quick info it showed only 2 MB and hence as expected market stopped working (not completely, as in bigger apps were not getting downloaded)

If you change one froyo to another after using nocache, you have to use the patch 'cache2tmpfs' as explained in post 1 :D

[Guest Smiff2]

All correct, do this after you install a rom. you can do it all in one session of clockwork, wipe data, install rom, run blade backup, then tpt install it. if you press & hold vol+ straight after you've finished in clockwork & pressed the home button to reboot it, then you can go straight into tpt mode & install the new partitions straight away.

just realized doing it all in one step was a bad idea in case you need to revert! better to use the new ROM for a bit and then repartition. can't see any downside as your script should be "lossless" if i've understood correctly. thanks.

it would be nice if it printed out the new partition sizes in clockwork so you could see what it's done? :D

Edited March 30, 2011 by Smiff2

[Guest Schwinni]

just realized doing it all in one step was a bad idea in case you need to revert! better to use the new ROM for a bit and then repartition. can't see any downside as your script should be "lossless" if i've understood correctly. thanks.

Yes, since all partitions (in the phone) are dumped, the process is "lossless".

it would be nice if it printed out the new partition sizes in clockwork so you could see what it's done? :D

You can look up the sizes by looking at the files in /sdcard/image.

And, you should delete the content of the image folder, because if you hold the VOL+ key when booting after a few days/weeks your phone will be reset to the day you changed the partition layout.

Edited March 30, 2011 by Schwinni