I ran the partition alignment check and 4EXT indicated that my fat32 partition is out of alignment. The phone is working properly, so... I'm not sure if I really need to do this. Anyway, in the option for partitioning, you can either preserve the fat32 or reformat the whole card. I'm guessing that preserving the fat32 will persist the alignment issue, so a complete format is necessary.
OK...
Well, I have a problem with understanding what to do with the partition sizes. In the Info menu, I see system (789Mb), data (1.1Gb) and cache (102Mb). In the Partitioning menu all you're presented with is EXT1, EXT2, and swap. Does system=EXT1, data=EXT2, and cache=swap? Obviously those existing partitions don't fit within the presented size selections, which... brings me to my next problem.
I have a couple of backups, but now I'm wondering if I change the partition sizes, will my backups no longer work? That would be a serious drawback...
And finally... I had read somewhere a suggestion on recommended partition sizes, but I made the mistake of not saving a bookmark to it and searches aren't turning up anything. I'd greatly appreciate it if someone experienced with 4EXT partitioning could chime in here. Thanks!
Related
http://forum.xda-developers.com/showthread.php?t=717874 original G1
http://forum.xda-developers.com/showthread.php?t=855424 Reused on EVO
I'm wondering if someone smarter then I can Figure out how to mod the script for the Atrix since we have a unlocked bootloader now.
I notice it is for S-OFF phones, but I'm thinking that this doesn't matter on our phone since we are able to flash radio's ect.
The way I see it we have two main groups of Atrix users, those that want to take space from /sdcard and use it in /osh and those that don't care about /osh and would use the increase space in /sdcard
Mods, sorry if this is the wrong section but It is a development question, I though would be best here.
So reading into these it seems that there are two zips/scripts. The first setups the recovery, you then reboot into recovery flash your android back on then run the second script which tells the kernel what to use for partition sizes.
If you want to go back to stock you reflash the recovery image.
The ATRIX has a very different partition table then evo, hero or g1. So well need someone who understands it better then I to look at the scripts.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
Here is more info, this is for the nook color, but it looks as though we could re-partition the internal memory as we desire. The risk is huge. Also I believe that CWM will re-write the partition table when doing wipes. I don't know the way all of this functions well enough to make the jump and make the /osh 2 or 4gb but that is what I'm looking into.
that might be rather dangerous doings resulting in unworkable touchscreen etc, since for seom reason repartitioning the internal nand ****s up /pds . several people had great problems by doing so.
Moved to proper forum.
crnkoj said:
that might be rather dangerous doings resulting in unworkable touchscreen etc, since for seom reason repartitioning the internal nand ****s up /pds . several people had great problems by doing so.
Click to expand...
Click to collapse
I did read that, but it seemed that it was before it was known that we need to back up the pds partition. But of course we should have images of all the partitions before doing something like this. It sounded relativity safe according to those threads. The partition table has to be written every time you flash and ClockWorkMod apparently will correct the partitions to factory settings if things get messed up.
But then this is why I posted the question, I don't know enough about how clockwork mod works nor how moving the pds partition would effect things.
Again if we can figure this out we can get enough room on /osh so that sogarths hack is not needed (it is redundant and sort of a waste of space (not bashing, it is the best option currently avaiable) to copy the /osh part to a new spot on the sdcard then link everything back in). For those not interested in webtop we can get them more system or sdcard space.
/system 315M 301.9M 13.1M 4096
/data 2G 895.9M 1.1G 4096
/cache 619.8M 87.8M 532M 2048
/osh 755.8M 643.1M 112.6M 2048
315M is too small for cm10 to install extra mods like sony walkman. i wonder if someone can resize it
xuefer said:
/system 315M 301.9M 13.1M 4096
/data 2G 895.9M 1.1G 4096
/cache 619.8M 87.8M 532M 2048
/osh 755.8M 643.1M 112.6M 2048
315M is too small for cm10 to install extra mods like sony walkman. i wonder if someone can resize it
Click to expand...
Click to collapse
I agree with you. For those don't using lapdock, /osh partition really waste of memory but resize partition could brick the device.
here another tool to resize partition.
http://forum.xda-developers.com/showthread.php?t=1171531
http://forum.xda-developers.com/showthread.php?t=1370963
Well, for those who were wondering (since fastboot resizing is not implemented yet), the procedures to resize your internal partitions are the exact same as HTC Dream with customMTD..
Just follow directions from the original idea/poster (Firerat and lbcoder): http://forum.xda-developers.com/showthread.php?t=717874
I have tested it on my rhod400 and it works, just be sure that you have the correct sizes.. if it is too large, you will be wasting valuable internal space that could be used for /data, and too small, your phone won't boot..
There is practically no chance of bricking your phone as you can always do a task29 and re-flash LK and recovery and as a final note, remember keep /cache greater than 30 mb so corruption will be last likely..
my fat32 partition isnt perfectly aligned you may ant to re-partition the whole sdcard.
when i go to re-partition the sd card which option do i choose ?
-revove all partitions and start from scratch
or
-no, save my fat32 partition
when ever i select any i get a list of numbers like, 128,256,341 and so on....dont know what they mean or which one to choose.
why are you making so many threads for one phone problem... its hard for people to give help and advice when they havent seen other problems your having... but anyways repartition the whole phone, remove all partitions and start from scratch, and when it asks for a number, click skipp, and when its done check your partition alignment again and then do a fix permissions and system file check
So, I gave my sister a hand me down i777, it has CM10.2 installed on it... She constantly gets notified that 'Storage is low", this is referring to /data probably... On newer phones, ones that normally shipped with ICS and newer, they don't use two partitions for /data and /sdcard, because you might have tons of space available on one but not the other, and you won't be able to utilize it, rather, they ONLY have a /data partition, and user content instead goes in /data/media. This way, app installs go on the same technical patition as photos or videos... Anywho, this current setup is a real limitation on how many apps she can install, I suppose there's some apps2sd crap I could do, but she doesn't actually have an external SD, and there's TONS of space on the built in '/sdcard"
TL;DR: Can I switch the i777 to a '/data/media' partition layout instead of the old '/data, /sdcard/ layout?
Well, it LOOKS like I might be able to resize /data and /sdcard with a modified .pit file, which may be good enough for now, but I guess it begs the question why there isn't an official CM setup that includes a modified .pit that eliminated the /sdcard partition?
TWRP, Pitchblack, OrangeFox, whatever recovery I try, I always end up with this Super partition. And I can't see how much size it is. It's just sitting 8192MB by default.
Aren't there any recoveries that show partitions normally like system, vendor separately, with actual sizes filled ?
MPK99 said:
TWRP, Pitchblack, OrangeFox, whatever recovery I try, I always end up with this Super partition. And I can't see how much size it is. It's just sitting 8192MB by default.
Aren't there any recoveries that show partitions normally like system, vendor separately, with actual sizes filled ?
Click to expand...
Click to collapse
That's because there are no dedicated partitions for system, vendor, and product. They are all located inside one partition called "super". Think of it as one big partition that houses other smaller partitions. The size of the individual partitions is variable hence you'll only be able to see the size of the super partition.
The size of the super partition is fixed and cannot be resized after a rom is installed. The super partition was created to eliminate the need for vendors to allocate specific sizes for sub partitions. Before the super partition, each partition had to be allocated a specific size and any free memory left after writing data to it could not be used when other partitions required more space. This free space was therefore wasted.
In the super partition, the sub partitions can be the exact size of the files contained within them. Any free space is left inside the super partition and can therefore be used by other sub partitions if they need it.
Unfortunately, the biggest setback for developers is that they cannot modify the contents of sub partitions once they're made read only (usually on the first boot after installing a new rom). People who try to modify these partitions often get into boot loops forcing them to reinstall the stock rom.
twistyplain said:
That's because there are no dedicated partitions for system, vendor, and product. They are all located inside one partition called "super". Think of it as one big partition that houses other smaller partitions. The size of the individual partitions is variable hence you'll only be able to see the size of the super partition.
The size of the super partition is fixed and cannot be resized after a rom is installed. The super partition was created to eliminate the need for vendors to allocate specific sizes for sub partitions. Before the super partition, each partition had to be allocated a specific size and any free memory left after writing data to it could not be used when other partitions required more space. This free space was therefore wasted.
In the super partition, the sub partitions can be the exact size of the files contained within them. Any free space is left inside the super partition and can therefore be used by other sub partitions if they need it.
Unfortunately, the biggest setback for developers is that they cannot modify the contents of sub partitions once they're made read only (usually on the first boot after installing a new rom). People who try to modify these partitions often get into boot loops forcing them to reinstall the stock rom.
Click to expand...
Click to collapse
Understood. But can we access /system & /vendor folders & modify files in it through root explorer.
So you're saying there's no way to remove system bloatware & unwanted apps ?
twistyplain said:
That's because there are no dedicated partitions for system, vendor, and product. They are all located inside one partition called "super". Think of it as one big partition that houses other smaller partitions. The size of the individual partitions is variable hence you'll only be able to see the size of the super partition.
The size of the super partition is fixed and cannot be resized after a rom is installed. The super partition was created to eliminate the need for vendors to allocate specific sizes for sub partitions. Before the super partition, each partition had to be allocated a specific size and any free memory left after writing data to it could not be used when other partitions required more space. This free space was therefore wasted.
In the super partition, the sub partitions can be the exact size of the files contained within them. Any free space is left inside the super partition and can therefore be used by other sub partitions if they need it.
Unfortunately, the biggest setback for developers is that they cannot modify the contents of sub partitions once they're made read only (usually on the first boot after installing a new rom). People who try to modify these partitions often get into boot loops forcing them to reinstall the stock rom.
Click to expand...
Click to collapse
Thx for explanation bro. Currently I have this issue. Can you take a look into this thread below & answer there ?
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
MPK99 said:
Understood. But can we access /system & /vendor folders & modify files in it through root explorer.
So you're saying there's no way to remove system bloatware & unwanted apps ?
Click to expand...
Click to collapse
In some custom miui roms like miui eu it is possible without causing a bootloop. Sometimes a bootloop will occur because of the root explorer you use. However, of you're still on stock rom you'll very likely end up in a bootloop. AOSP roms don't have this weaknesses but they're not as stable as miui.
I recommend installing a debloated rom like MiuiMix or miui eu. Then get help from the support forums to find out how to get into system without killing the rom.
Everytime I tried to flash a ROM without wiping system (bc I can't) I got error 7. So I had to do a format data and I lost all of my stuff. Is there any way of wiping system so I don't have to do a format data?
Piusak said:
Everytime I tried to flash a ROM without wiping system (bc I can't) I got error 7. So I had to do a format data and I lost all of my stuff. Is there any way of wiping system so I don't have to do a format data?
Click to expand...
Click to collapse
Once after booting up any rom, check whether the device is encrypted or not. (Security > Encryption)
If it is, then offcourse, in recovery you had to wipe everything if you wanna flash a new rom. This device has dynamic partition update, that merges all OS partitions (system, vendor, product) & encrypts data partition if it's decrypted.
Ofcourse you also can't able to modify partitions while encrypted, caz you'll end up into errors.