Solved problems: restoring nandroid backup / converting to ext4 - Samsung Galaxy SL i9003

Hi! This is my first thread. I hope i chose the appropiate subforum.
I saw no particular thread concerning this information. I took the liberty of compiling it all together here.
This thread may come handy if:
-You tried to restore a nandroid backup and for an unknown reason cwm would not allow you, giving a /system error. Even though you tried reflashing rom you could not restore the corresponding backup.
-You tried ext4 conversion, there was an error sometime during the conversion and you ended with a bootlooping phone.
I will convey you my personal experience.
Warning: When flashing kernels, roms, converting to ext4, rooting and doing other modifications you lose your warranty. I am not responsible for any inconvenience or problem you may encounter after/while doing this. Modifications are up to each user and they are their responsibility.
Read carefully everything.
Before anything, i recomend creating a nandroid backup in cwm, just in case. I also recommend having the baterry well charged.
Mi personal experience is based on KPH with Bam Custom Kernel (r14fix with CF-Root), deodexed. I had 23 free MBs in /system.
Moving on:
-Error while restoring nandroid backup:
Quoting XDA_Bam from this forum:
“It is not possible to successfully restore a nandroid backup if there are less than 10 MB of free space in /system. This is a "feature" of the RFS file system and we currently do not know any way to circumvent this. This also affected the ext4 conversion process, but has been fixed in beta 14. Credits go to madrooster for stating this fact and loSconosciuto for testing it on our device.”
Quoting IoSconosciuto from this forum:
“Nandroid backups of the /system partition where the backed up partition had less than 15MB of free space will not restore completely, due to the way the rfs filesystem works. This should only affect restoring a backup of a stock ROM.”
Depending on the source, the necessary free space varies from 10-15 MB. The more free space you have in /ststem, the better, just to be completely sure. Stock roms generally have less than 10 free MB and because of that problems appear when trying to restore the backup. What you need to do is to free some space in /system. Here are some ways of achieving that:
a) Uninstall some unnecesary system apps (you need to be root and have a file explorer app, such as Root explorer or ES file explorer).
b) Another way is to deodex the phone. Deodex apps take up less space than the equivalent odexed apps from default.
Regardin b), IoSconosciuto said:
“If skin's tool worked in the past, it's because Samsung is adding more and more stuff in /system, older ROMs were smaller. That's why there were no problems before. Another reason is that lot of users deodex their rom first. The result of this operation is more free space in /system. ("odexed apk + odex" > "deodexed apk")”
To know how much free space you have in /system you can use Titanium Backup. It is right away in its main screen when opening the app. (Titanium backup requires root)
Another user, in another forum not only solved the problem when restoring a nandroid backup on his i9003, but he also could successfully restore an otherwise non working backup on Motorola Atrix. So, this may be something more universal regarding Android and rfs file system!!
-Error while converting the partitions to ext4:
This issue is closely related to the first one since converting to ext4 implies restoring a nandroid backup.
Quoting again IoSconosciuto:
“Due to the ext4 overhead, you have less free space in /system after the convertion and that gives problems when you restore a backup. These few MBs of memory are not lost, they are reserved, but you can't use them for normal data.”
Again, when trying to convert to ext4 it is recomended that you have al least 10-15 free MBs of space in /system. The more, the better. Ways of freeing more space are as previously described: a) and/or b)
When the phone tries to restore the backup it may encounter that there is not enough free space, it then gives /system error and you have a phone half-way through conversion that bootloops and you have to flash everything again...
Nonetheless, amig.bagaria (user from this forum) developed a tool (.apk) that backup, converts and restores the backup automatically: ext4 add-on .apk
Use thing method instead of flashing the zip in CWM. One of the main advantages of this app is that when converting it is able to discern is there is enough free space in /system. If there is, it converts flawlessly. If there is not, it informs the lack of space and restores the /system backup in RFS!! (the rest of the partitions will still be on ext4, with exception of /system that will have returned to RFS). The phone will boot normally and in this way we avoid flashing everything from scratch if something goes wrong!
Using this app is as simple as: install, open, allow superuser permission, touch “Convert to ext4”. The phone will automatically boot in CWM and will do everything on its own. You just have to sit back and watch. Once finished it will automatically reboot.
To check the conversion you can open again amit.bagaria´s app. There under each partition you can read either rfs or ext4. If all partitions were correctly converted, in addition of reading “ext4” below each partitions, the “Convert to ext4” option will appear gray-shaded and you will not be able to select it. If it still appears in white it means that something still needs converting. Probably /system. Check above.)
Note: I use this app having Bam Custom Kernel (r14fix with CF-Root). It is important to have the latest version of amit.bagaria´s CF-Root (version 9, from 01/02/12). I have no idea if this method functions with Skin1980´s CF-Root. The most logicall thing should be that i does NOT function. It is up to each individual user to try and see the outcome...
One last thing:
Bam latest Kernel (r14fix) if modified to have more free space in /system:
“Universal CF-Root: Corrected problems because of too little free space in /system when converting to ext4 by permanently moving InfoAlarm.apk from/system/app to /data/app. Thanks to loSconosciuto.”
Anyway, you should check again your free /system space in /system and make more space if it is still necessary.
I hope to have been clear and that this helps you as it helped me.
Tale care!
Credits go to: XDA_Bam, IoSconosciuto & amit.bagaria. I might be forgetting other users in this thread in question: http://forum.xda-developers.com/showthread.php?t=1355675

Nice thread, never knew the rfs limitations Just a suggestion, maybe change the thread title to [HOW TO]Solve NANDroid restore error|Convert to ext4.
Anyway,you could add that the backup could be corrupted as there wasn't enough space on the sd card to complete the backup. Also, never ever change the file/folder name or the restore would fail. You could also add how to check md5 to ensure that the backup is not corrupted.
Sent from my GT-I9003 using xda app-developers app

bscraze said:
Nice thread, never knew the rfs limitations Just a suggestion, maybe change the thread title to [HOW TO]Solve NANDroid restore error|Convert to ext4.
Anyway,you could add that the backup could be corrupted as there wasn't enough space on the sd card to complete the backup. Also, never ever change the file/folder name or the restore would fail. You could also add how to check md5 to ensure that the backup is not corrupted.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Thanks.
I think that the tittle can not be edited...or can it be?
Anyway, my intention was to adress this specific type of errors. Of course I could add all the things you listed and maybe others, but that will make it a more general thread. I typed it thinking of people who already had certain knowledge (that is why i did not bother to explain how to flash cwm, kernel, how to root and so on...).
I could always add some more things, since explanations are allways useful.
Anybody´s comments shinning more light on the topic are welcomed. Just like yours!

Taxman. said:
Thanks.
I think that the tittle can not be edited...or can it be?
Anyway, my intention was to adress this specific type of errors. Of course I could add all the things you listed and maybe others, but that will make it a more general thread. I typed it thinking of people who already had certain knowledge (that is why i did not bother to explain how to flash cwm, kernel, how to root and so on...).
I could always add some more things, since explanations are allways useful.
Anybody´s comments shinning more light on the topic are welcomed. Just like yours!
Click to expand...
Click to collapse
It can, but it's up to you. I go to advanced edit I think, haven't used the computer in a long time to access xda.
Edit: also, flash the kernel you made the backup with, it would normally restore unless the backup has been tempered with
Sent from my GT-I9003 using xda app-developers app

Nice write-up
The actual limit of free space for a successful conversion is somewhere at or below 10 MB, IoSconosciuto tested it. The ext4 conversion itself costs you about 4 MB in partition size (not free space, but the result is the same). This means if you convert to ext4 with 10 MB free in /system, the backup and restore will work and you will have 6 MB free after the conversion. Since the partition is ext4 afterwards, that suffices to make and restore later backups.

XDA_Bam said:
Nice write-up
The actual limit of free space for a successful conversion is somewhere at or below 10 MB, IoSconosciuto tested it. The ext4 conversion itself costs you about 4 MB in partition size (not free space, but the result is the same). This means if you convert to ext4 with 10 MB free in /system, the backup and restore will work and you will have 6 MB free after the conversion. Since the partition is ext4 afterwards, that suffices to make and restore later backups.
Click to expand...
Click to collapse
You are right! In my particular case, the conversion cost me exactly 4,4 MBs.

thank u bro at last im done with it, thank you.

Related

Question about 4EXTRecovery

Hi everybody,
i am sure, that everybody except me seems to know how to install this awesome recovery...
I already renamed the zipfile to PG88IMG.zip, have put it into the root of the sd card, rebooted, the bootloader says 'parsing PG88IMG.zip', then nothing happens...
So, could someone please enlihgten me how to flash this thing? (if possible without creating an expensive brick ;-)) thanks a lot
Who told you to do that?
EDIT:
This should be a one click zip.
http://forum.xda-developers.com/showthread.php?t=1130004
Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)
glubber008 said:
Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)
Click to expand...
Click to collapse
................... You'll need to extract the images from the zip images and I suspect, with respect that you don't know what your doing.
So leave that method well alone!
yes, of course - i don't know how to flash this recovery ;-)
i already know that
that's the reason, why i'm asking here, you know... ;-)
try doing this
1.put the zip on your sd card
2.reboot into recovery
3.go to install from sd card
4.choose the zip from sd card
5.select the zip file & choose yes
the phone should flash the recovery & restart again into recovery
choose reboot
ah, thanks a lot ;-)
btw, exploring the zip, i found the following in the updater-script:
assert(getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga" || getprop("ro.product.board") == "saga");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
So, you are right, it flashes the recovery.img correctly to the recovery partition, then reboots again into recovery, all understood now, thanks again...
btw:
i might be new to android, but not to computers - i am actually a programmer ;-)
that's why i'm usually asking before doing something i don't understand completely...
anyways,
it worked, thanks again for pointing me into the right direction
Ah,
i found out, that the PG88IMG.zip method only works, if there's an android-info.txt file in the archive, so it seems, that the parser of the hboot checks the contents of this file and if this thing is valid, it continues to the builtin flash routine.
That's the reason, why this method fails with the 4Extrecovery zip file.
on the other hand, if you want to flash from the recovery system, there must be a folder called META-INF with 'some' defined structure in it, a file called updater-script (i dont know, what this update-binary file is - it is a binary ELF executable, maybe the interpreter? maybe the compiled form of the updater-script? - will run 'strings' on it...); anyways, this file is then executed and contains basically the information how to install / flash this thing.
So, thanks for helping me doing the first steps on this awesome platform ;-)
EDIT:
it seems, the update-binary file is the interpreter for the updater-script:
the relevant strings are:
wrong updater binary API; expected 1, 2, or 3; got %s
failed to open package %s: %s
META-INF/com/google/android/updater-script
Ok, enough for today... ;-)
EDIT2:
...and update-binary is part of the recovery, as found here for example:
https://github.com/arco/android_bootable_recovery/blob/gingerbread/updater/install.c
nice, nice...
EDIT3:
...currently building my own recovery, this thing is plain c, so not a big problem for me, we'll see...
EDIT4:
..flashed this thing, it's working, so i guess i can now start hacking on it ;-)
is it possible to install 4EXTRecovery to desire s with s-on? and how?
realies said:
is it possible to install 4EXTRecovery to desire s with s-on? and how?
Click to expand...
Click to collapse
no, it is not possible
you need s-off to install recovery
does CWM have to be removed to install this?
greenster4470 said:
does CWM have to be removed to install this?
Click to expand...
Click to collapse
No. Use CWM to flash it like any other mod! It'll automatically re-start recovery, and you'll in be in your shiny new 4EXT recovery.
As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks
harshs23 said:
As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks
Click to expand...
Click to collapse
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.
Thank you, make a lot more sense to me now.
enigmaamit said:
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.
Click to expand...
Click to collapse
Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL
4EXT Recovery Control
https://market.android.com/details?id=ext.recovery.control
Although the free version is available, I highly recommend an investment in the application that supports this incredible recovery. The added features in the market version outweigh the free version drastically.
harshs23 said:
Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL
Click to expand...
Click to collapse
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.
enigmaamit said:
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.
Click to expand...
Click to collapse
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.
harshs23 said:
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.
Click to expand...
Click to collapse
You're more than welcome. This is what all of us are here for...

Firerats + Data2ext Complete Installation Guide: Now works with Sense roms!

This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.​
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!​
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...
Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA
Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE
App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd
laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app
ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!
laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.
Updated
Edit: Updated again to fix minor wording issues and make links much prettier!
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?
dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.

[Q] Resize internal partitions

Hi,
This has been asked many times before with no real solution that applies to different devices.
I'm running out of space on my /system partition and can't install any more apps even though I don't have that many installed.
I want a way to re-size the Android partitions manually to whatever size I want. Or just delete all current partitions and create new ones.
How do I do that? Is there any GUI partitioning tools similar to the ones available for Windows?
I don't want to move files from /system to another partition. I want to change the partition size.
My current /system partition:
For what reason are you moving apps to /system? You can't install them there, you have to push/move them there, installs go to /data. So keep them in /data, where they're installed by default. You have tons of space available there.
Partition table (start addresses and sizes) is hard-coded in bootloader, and can be redefined in kernel boot parameters (in this case recovery needs to be recompiled with the same parameters too, otherwise it won't write to the same partitions the kernel will read from). You're welcome to hack any of those. As you could probably understand from this paragraph, I wouldn't expect having GUI tools for that.
Thanks for the reply.
I'm not trying to move apps to /system. I thought apps are installed there by default because every time I try to install a new app it gives me an error message saying that there is not enough space on /system.
Now I know that apps are not installed in /system.
I just need more space in /system so I can install new apps without any errors.
What can I do to get more space on /system partition? Can I replace the bootloader?
I don't have any Android programming experience. I probably need something that is available out there to do the job.
In stock form, you shouldn't even have write permissions to /system. Nothing should be ever written there, and it can be 99.99999% utilized - there shouldn't be any free space left for anything, it shouldn't normally be used.
If you're getting that error when trying to install an app - you need to check what's reporting the error. It's not a "real" error, it means there's something wrong with your phone.
Try wiping cache partition from recovery...does this make any difference?
Jack is correct.
Swyped from my DesireS
refer to this
if this may help you http://forum.xda-developers.com/showthread.php?t=1959691
:highfive:
mayank88288 said:
refer to this
if this may help you http://forum.xda-developers.com/showthread.php?t=1959691
:highfive:
Click to expand...
Click to collapse
Way to bump a year old thread :thumbup:
“I'm bad and I'm going to hell, and I don't care. I'd rather be in hell than anywhere where you are. ”*―*William Faulkner

[MOD][REC][29/10]Data2SD -- I/O-Boost

Data2SD MOD: Moves /data partition to External SD, noticeable performance increase
All files attached are flashable .zips Installation instructions updated.
clemsyns cpu OC 1800 kernel is out! Good stuff!
Symlink added to /data2 (internal storage now found as /sdcardi)
You will need to disable journaling using the guide in post #3 if you are on CleanROM 2.1 to 2.3
as the rom does this as standard. If not you will get error!
I have had nothing to do with the development of this MOD, all credit goes to TweakerL
Also a huge thanks to scrosler for the fantastic CleanROM
Thanks to clemsyn for the amazing kernel!
Feel free to go to original thread and give your thanks: http://forum.xda-developers.com/showthread.php?t=1803252
and also to seek information, the thread is full of it.
What/Why/How?
This MOD was developed to aid the I/O-issues the Transformer Prime has and the Infinity inherited. Since it was a known fact that the internal
storage was slow/poor, TweakerL decided to try mounting the /data partition to the MicroSD card. Hence an obvious necessity
will be that you have a fast MicroSD card. Several have been tried and there is no real conclution as to what is the best in regards
to manufacturer or class (a class 6 card can have better random write speeds than a class 10 card), I use a Sandisk 64GB UHS-I
class 10 card and so does several others with good results.
The way this works is that you change the ramdisk so that it mounts /data to the second partition of your micro sd. Your internal
storage (the old /data partition) will be mounted as /data2.
Requirements
1. Unlocked and Rooted
2. You MUST repartition your Micro SD. The .zip you flash will mount /data to mmcblk1p2, which basically says "mount /data to the
second partition in the external SD." also, the ramdisk expects that partition to be ext4, so essentially:
Make sure you have an external SD with at least two partitions and that the second partition is formatted to ext4. I use fat32 on the first partition
because it's recognized by most devices.You will also need to make both partitions "primary" partitions. I personally use Gparted to repartition
my stuff, but feel free to use whatever you like. Even if you're on windows you can still use gparted by using virtualbox, or you can use a tool
called MiniTool Partition Wizard, I haven't tried it myself but it is reported to be good.
3. Research your Micro SD, find out if it has good random write speeds. There is no use in this mod if you card is slower than your internal
memory.
4. Although it's not a requirement it is a recommendation to have gone through the Nvflash procedure. It has saved alot of people from bricks
and is just great to have.
5. Verify that the .zip is compatible with your ROM, if it is not listed feel free to ask for a version for your preferred ROM.
Disclaimer
I take no responsibility for whatever happens to your device using this MOD, it is flashing a kernel so take precautions!
Installation
1. Boot to recovery, flash your preferred ROM
2. Reboot to initial setup (Don't run through)
3. Reboot to recovery, flash the matching Data2SD.zip
4. Disable journaling (Optional on all ROMs except CleanROM)
5. Reboot
When it reboots you will get a blue progress bar and it will be just as you flashed a new rom, you'll get the device setup screen.With my
MicroSD I get about twice the Random Write speed with this mod; Internal=0.20mb/s External=0.40mb/s . We will have a look at doubling
these figures further down (I currently have Random write speed average of 0.8mb/s).
Reverting
Flash a ROM
Feel free to ask any questions!
MD5 checksum for cm10-1025data2sd : 78b9e62e27204efeb0bdd3c926c4a30a
MD5 checksum for CleanROM2-3Data2SD: 60eef4e666ec97216ee0801189233719
MD5 checksum for clemsyn's 600 OC kernel ver8: e07b4a5a5f7ae2976a86460e5309199a
MD5 checksum for clemsyn's 650 OC kernel ver8: cf6d36da2d26db2e72c1c110a87cad7f
MD5 checksum for clemsyn's 650 OC kernel ver22: 1ec0e9c5c5ac7b012e3095f03f7dd234
Modded Recovery
Enough with the screenshots, I think people know what it's all about by now!
TWRP 2.3.1.0 Data2SD Edition
Modded by flumpster, thanks a million!
Attached is a version of the latest TWRP recovery, the only mod done is changing where
it mounts /data so it backs up the correct partitions!
Backup to External will backup to your first partition (fat32 maybe) and backup to internal will
backup to your ext4/2 partition.It is recommended to back up to external which is the fat partition.
If you backup to internal which is now the ext partition and something goes wrong with that partition
you wont have access to your backup.
Instructions:
You must remove the old twrp settings from your prime for this to work correctly. Delete any
TWRP folders that are in sdcard, data2/media and removable/sdcard. If you have backups there
already that you want to keep leave the backups folder in the TWRP directories and then just
delete the files that are in the root of the TWRP folder to get rid of the settings left behind.
If you are on a windows pc just extract the zip somewhere and run the bat file and then follow the
onscreen instructions. It will flash it for you. If not, navigatate to the fastboot folder, find the .blob
and flash the usual way with fastboot.
I have tested it myself but would love some feedback on this as I am currently the only one testing.
Disabling journaling!
This is a mod that flumpster tested and found to work fine. I have tested it to and it is fast as a shark. It is somewhat
controvertial though, someone thinks disabling journaling on the ext4 file system could cause crashes. Also if you are
plagued with random reboots it can cause data loss. I've been running it for a couple of days without issues and getting fantastic results.
Here is a description on how to do it if you want to try:
To Disable Journaling in EXT4
Go into TWRP and then open a command prompt on your computer where adb is.
Type adb shell and enter it then type the following commands one at a time.
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk1p2
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk1p2
e2fsck -f /dev/block/mmcblk1p2
Watch out for the fourth line, after tune2fs - that is a capital O not a zero. The one further along the line is a zero.
To check if it has worked type the follwing after them
tune2fs -l /dev/block/mmcblk1p2 | grep features
If you don't see has_journal in the output all is good.
And the size of the ext4 partition should be?
I was planning on taking a stab at porting this project to the TF700 this weekend. Thanks for your work! Going to test ASAP.
maxrdlf95 said:
And the size of the ext4 partition should be?
Click to expand...
Click to collapse
That is up to you really, the ext4 partition will be your new "internal storage" so if you if you need to store alot there like big games etc. you'll need more. If like me you have little use for internal storage you increase the size of first partition. I have 49gb fat 32 as my first partition and 11gb ext4 as my second.
I transfer movies etc. from a windows machine to the fat32 partition.
Good question though, I should have mentioned it in the OP.
Sent from my ASUS Transformer Pad TF700T using xda premium
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Kisakuku said:
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Click to expand...
Click to collapse
Yes, of course. Thank you for pointing that out, I've used CheckROM on another device so it got mixed up. OP updated.
fordwolden said:
Data2SD MOD: Moves /data partition to External SD
Click to expand...
Click to collapse
This looks very interesting!
fordwolden said:
Disabling journaling!
Click to expand...
Click to collapse
Actually the ROM does this during install. However on 2.0 it was causing issues with the latest TWRP so I temporarliy took it out.
It ended up being a twrp issue. IM going to put it back in for version 2.1 (with will be 10.4.4.18 based) and revert to the old version of twrp. The newer 2.3.x builds dont seem as reliable at this time.
But good write up!
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Edit: No longer applicable, sd-ext backup no longer supported. Modded TWRP recovery in post #2
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
heh... i was just going to ask about that. thanks for the clarification.
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
People really use Nandroid? lol :angel:
scrosler said:
People really use Nandroid? lol :angel:
Click to expand...
Click to collapse
Some feel more comfortable doing it! I feel like it's "bringing a knife to a gunfight"! False safety.
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Moning2 said:
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Click to expand...
Click to collapse
Gospel singers from the General section? Now that's a first for me! I'm glad you're happy with your tablets,
now try downloading CleanROM 2.1 while multi-tasking on your device, still happy? I bet you want to unlock
before the download is finished!
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
New version has symlinked /data2 partition so your internal storage will now be found in /sdcardi. Just for ease
of use.
rikc said:
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Click to expand...
Click to collapse
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
fordwolden said:
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
Click to expand...
Click to collapse
Ok, thanks, that's clear!
I want this on stock rooted unlocked ROM
fordwolden said:
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
.
Click to expand...
Click to collapse
Oh come on, Uranium has been around Earth for four and a half billion years and it's still here, can't be that unstable
Gesendet von meinem GT-N7000 mit Tapatalk 2

[SOLVED] Completely format system data cache partitions[making all zeroes]

I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
____________________
Solved. See post 17 for details.
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
Had to search a bit, but found an article that explains how to do this. It links to 3 apps (havn't tested myself, just remember there's no going back), from the description the first one only works on SD card, the second one might (it does not mention which partitions it formats), and the last one seems to be removed.
I did not read the whole article, but I suggest you do that before doing anything.
Good luck.
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
Hi,
A RUU will reset everything back to stock, and fix any partition issues.
Is that what you are after?
malybru said:
Hi,
A RUU will reset everything back to stock, and fix any partition issues.
Is that what you are after?
Click to expand...
Click to collapse
As he said, he wants it to be completely formatted, meaning no data can be recovered, which is like a hard full wipe - no way to restore.
RUU does format the data partition, but it only removes records of files, and the data itself is still available and possible to read (until new files will be written over it).
No! I dont want to get involved with RUU stuff.. I just want to completely wipe my phone.. Like complete formatting of the USB drives. All system and data partitions set to zeroes.
In simple words, if you do quick formating on pendrives, you can restore (some or all data before format, depends on what you've put on the drive after format ) using some Data Recovery tools.
What i believe is that recovery just wipes the memory addresses, without putting zeroes on all the memory locations. have been googling for this for almost a week, haven't got any clue yet!
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
I would do it this way (this is something I came up with, and if it screws up anything, you are responsible) :
Write a script that reformat your nand rom and then dumps (creates) a huge file containing zeroes. Then reformat using 4ext and repartition.
I am curious, why exactly do you want to do this? The lack of results from Google would suggest that this is not something people would normally do.
JAM THAT THANKS BUTTON.
Happy to help.
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
pushpann said:
No! I dont want to get involved with RUU stuff.. I just want to completely wipe my phone.. Like complete formatting of the USB drives. All system and data partitions set to zeroes.
In simple words, if you do quick formating on pendrives, you can restore (some or all data before format, depends on what you've put on the drive after format ) using some Data Recovery tools.
What i believe is that recovery just wipes the memory addresses, without putting zeroes on all the memory locations. have been googling for this for almost a week, haven't got any clue yet!
Click to expand...
Click to collapse
On my first commented I linked to an article which gives two ways to wipe your phone (set to zeroes and all). Here are the two apps:
https://play.google.com/store/apps/details?id=com.kovit.p.forevergone
https://play.google.com/store/apps/details?id=ch.ethz.infsyssec.sddroid
Try those to see if they format the Data partition.
Far_SighT said:
I would do it this way (this is something I came up with, and if it screws up anything, you are responsible) :
Write a script that reformat your nand rom and then dumps (creates) a huge file containing zeroes. Then reformat using 4ext and repartition.
I am curious, why exactly do you want to do this? The lack of results from Google would suggest that this is not something people would normally do.
JAM THAT THANKS BUTTON.
Happy to help.
Click to expand...
Click to collapse
Hmm.. My phone has become very laggy.. No matter what ROM flash, what firmware I flash.
DennisBold said:
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
Click to expand...
Click to collapse
By hearing what you say, i kinda feel little scared to do these steps. Anyway thanks for the suggestion..
astar26 said:
On my first commented I linked to an article which gives two ways to wipe your phone (set to zeroes and all). Here are the two apps:
https://play.google.com/store/apps/details?id=com.kovit.p.forevergone
https://play.google.com/store/apps/details?id=ch.ethz.infsyssec.sddroid
Try those to see if they format the Data partition.
Click to expand...
Click to collapse
Those apps dont work.. By internal data they mean internal sdcard not system or data partition.
BTW just saw this app called lagfix. It says it will discard the unused blocks, but doesnot work on my phone.. Has anyone tried it? For me it's saying trim on system,data and cache not supported! DAMN
DennisBold said:
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
Click to expand...
Click to collapse
Yeah, I had similar thoughts. I was going for repartition becasue then the whole of nandroid can be wiped in one go.
To clean the phone, sledgehammer / mowing the device with a car (or both, one after the other) are the best methods.
Here's one more idea. Create a pseudo nandroid backup with all of your nandroid partitions(/system /data /cache etc) filled with garbage/zeroes. Then restore that. And bam, the nandroid is hard formatted (after a quick format of course).
Like always, it's your phone. I am not responsible for anything that you do to it.
JAM THAT THANKS BUTTON.
Happy to Help.
pushpann said:
Hmm.. My phone has become very laggy.. No matter what ROM flash, what firmware I flash.
By hearing what you say, i kinda feel little scared to do these steps. Anyway thanks for the suggestion..
Those apps dont work.. By internal data they mean internal sdcard not system or data partition.
BTW just saw this app called lagfix. It says it will discard the unused blocks, but doesnot work on my phone.. Has anyone tried it? For me it's saying trim on system,data and cache not supported! DAMN
Click to expand...
Click to collapse
Tried it yesterday, it's meant for certain devices that did not use the TRIM command like they should (Many Nexus 7 tablets were slowed down by this issue), but it seems the Sensation does not need it (or at least our kernels do not support the command).
What seems as the only way to do so is to create many blank files and delete them (like many already said). you can create a large file and copy it a few times to the Data partition, which will fill it, and then delete it. using a normal file manager will work (or you can use "adb push" command to push the file a couple of times).
Far_SighT said:
Yeah, I had similar thoughts. I was going for repartition becasue then the whole of nandroid can be wiped in one go.
To clean the phone, sledgehammer / mowing the device with a car (or both, one after the other) are the best methods.
Here's one more idea. Create a pseudo nandroid backup with all of your nandroid partitions(/system /data /cache etc) filled with garbage/zeroes. Then restore that. And bam, the nandroid is hard formatted (after a quick format of course).
Like always, it's your phone. I am not responsible for anything that you do to it.
JAM THAT THANKS BUTTON.
Happy to Help.
Click to expand...
Click to collapse
You sure it does complete format while restoring nandroid? BTW i still am not sure how to fill system and data partitions with zeroes or garbage! Anyway thanks for the heads up
pushpann said:
You sure it does complete format while restoring nandroid? BTW i still am not sure how to fill system and data partitions with zeroes or garbage! Anyway thanks for the heads up
Click to expand...
Click to collapse
You shouldn't have to worry about formatting empty space. No one ever, except possibly computer forensics is going to want information from an empty phone. They have access to browsing history from Google, call records from your mobile provider and ban access details from your banks. They wouldn't need your phone. There are things that make it hard for the average person. Including mounting the NAND disk in a way that it can be opened like a normal disk drive, and then running the tools to restore data. If someone really wanted data it's possible but they will not go through all that for 500MB of bank details, porn or whatever people do with phones these days. If you're trying to hinder the police because you did something wrong, then you should just stop.
Theoretically it can be done through an android device but cross compiling tools to recover data is long and tedious to do. There is nothing so important that someone would spend hours creating tools for an Android device to restore data that may already be irrevocably gone. Not to mention the learning curve for new software. If you are worried, burn the device and buy something new. That is the general rule for sensitive data. Make sure it's gone before you move on.
It's safe to click "Format all partitions" and then erase your SD card and give your phone away.
If it helps, install Android on top. Choose something big. Most of your application data is stored on your SDCard FYI.
Lastly, if it's lag you are trying to fix. Go backwards with Android not forwards. JellyBean demands more than ICS and ICS demands more than GingerBread. Having the latest OS doesn't work for everyone. For example, Windows 8.1 doesn't work for me because there's no fastboot support without huge editing of system drivers. The same is true in Android. GingerBread stability may be more important than ICS or JB features, or JellyBean features may be more important. However don't expect lag free 4.2 or 4.3, our devices may work with it, but they were never intended to go above 4.1(Ville C2 updates stop there too I think) due to hardware limitations. Others may argue differently, but you should question the effort they're (including me) putting in with kernel and device tree upgrades. It's amazing work nonetheless but it basically shouldn't have to be done if the device were supported. Buy a new device if you want the latest and greatest. My Sensation has become a trophy for me to the amazing things you can do with one of HTCs first dual core phones. I don't expect it to work without some kinks and bugs or even fatal flaws but I still respect it for having running Sense 3.0 to 5.0 (yes I've tried it).
Sorry for the rant. I'm a little bit grumpy, but hope it helps explains why you can mostly erase and install a new version of android then throw the device away and be relatively safe.
There's probably going to be someone who reads all of this and thinks I'm crazy, to that guy or girl. Thanks for reading all of it!
Sent from my HTC
DennisBold said:
You shouldn't have to worry about formatting empty space. No one ever, except possibly computer forensics is going to want information from an empty phone. They have access to browsing history from Google, call records from your mobile provider and ban access details from your banks. They wouldn't need your phone. There are things that make it hard for the average person. Including mounting the NAND disk in a way that it can be opened like a normal disk drive, and then running the tools to restore data. If someone really wanted data it's possible but they will not go through all that for 500MB of bank details, porn or whatever people do with phones these days. If you're trying to hinder the police because you did something wrong, then you should just stop.
Theoretically it can be done through an android device but cross compiling tools to recover data is long and tedious to do. There is nothing so important that someone would spend hours creating tools for an Android device to restore data that may already be irrevocably gone. Not to mention the learning curve for new software. If you are worried, burn the device and buy something new. That is the general rule for sensitive data. Make sure it's gone before you move on.
It's safe to click "Format all partitions" and then erase your SD card and give your phone away.
If it helps, install Android on top. Choose something big. Most of your application data is stored on your SDCard FYI.
Lastly, if it's lag you are trying to fix. Go backwards with Android not forwards. JellyBean demands more than ICS and ICS demands more than GingerBread. Having the latest OS doesn't work for everyone. For example, Windows 8.1 doesn't work for me because there's no fastboot support without huge editing of system drivers. The same is true in Android. GingerBread stability may be more important than ICS or JB features, or JellyBean features may be more important. However don't expect lag free 4.2 or 4.3, our devices may work with it, but they were never intended to go above 4.1(Ville C2 updates stop there too I think) due to hardware limitations. Others may argue differently, but you should question the effort they're (including me) putting in with kernel and device tree upgrades. It's amazing work nonetheless but it basically shouldn't have to be done if the device were supported. Buy a new device if you want the latest and greatest. My Sensation has become a trophy for me to the amazing things you can do with one of HTCs first dual core phones. I don't expect it to work without some kinks and bugs or even fatal flaws but I still respect it for having running Sense 3.0 to 5.0 (yes I've tried it).
Sorry for the rant. I'm a little bit grumpy, but hope it helps explains why you can mostly erase and install a new version of android then throw the device away and be relatively safe.
There's probably going to be someone who reads all of this and thinks I'm crazy, to that guy or girl. Thanks for reading all of it!
Sent from my HTC
Click to expand...
Click to collapse
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
pushpann said:
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
Click to expand...
Click to collapse
The lag isn't from formatting. You can try ARHD ICS if you want. Or probably Sense 4+ with 4.1.2 but anything above that might not work out great.
Sent from my HTC
pushpann said:
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
Click to expand...
Click to collapse
How old is your Sensation? I could well be that your nand is dying. In that case, repartition your phone and make /system and /data from parts seldom used (like /cache).
If you want data security, full encryption will keep noobs away.
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
pushpann said:
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
Click to expand...
Click to collapse
Just found something and wanted to add - for future reference - Android Tuner seems to be able to make the TRIM operation on all partitions on our sensation, in a much easier way.
pushpann said:
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
Click to expand...
Click to collapse
Can you guide me? i want to do that but i'm noob . how did you do that? pls help me
BSHD666 said:
Can you guide me? i want to do that but i'm noob . how did you do that? pls help me
Click to expand...
Click to collapse
hehe you found it:good:

Categories

Resources