i m trying to flash nikgapps basic version but whenever i try it says "storage full" so i want to resize system partition but in wipe section i dont see any system partition.
you cant see system partition. Use Flamegapps.
did you find a solution to this problem?
you can't resize system partition at all. It's dynamic hence comes under Super partition
Related
I just saw an interesting thread in the development section that explains an alternative to the Death SPL. The method there lets you flash ANY rom on any SPL, but I dont really understand how it works.
The thread can be found here: http://forum.xda-developers.com/showthread.php?t=704560
So basically, you shrink the cache partition to allow for more room for the actual ROM(which partition does that go in?)?
To do this do we edit the boot.img in the ROM update.zip? What else do we do?
Could someone explain this in a way a 9th grader could understand?
kingkurry said:
Could someone explain this in a way a 9th grader could understand?
Click to expand...
Click to collapse
Take file by firerat, flash file. omgroflpartitons.
If you don't understand the instructions as they are, wait for it to be perfected before you try anything. This will probably end up being integrated into releases that need it, so you don't need to worry about the specifics at the moment.
Will that patch file work for all ROMs. He said its only been tested with CyanogenMod 5. And I want to understand what im doing, not just do it without thinking about it...
Also, does the recovery patcher decrease the size of the partition that holds the recovery image?
Does it permanently change the size of the recovery partition?
When you flash a ROM, what partition is it being flashed too? Is this the one being increased in size?
What does the boot.img in an update.zip package hold, and is that copied to the boot partition?
Sorry but my curiosity is killing me
OK well to break it down we have 6 partitions on the internal memory:
Misc - Here be dragons
Recovery - Contains recovery system (+seperate recovery kernel) - recovery.img lives here
Boot - Contains kernel & important initialization stuff - boot.img lives here
-------------
System - Contains the whole android system (the "ROM", if you like).. everything else from an update.zip apart from the boot.img
Cache - Used by system and recovery for temporary storage
Userdata - Contains all personal data, downloaded apps, settings etc.
The first three partitions must be left at the default size so don't worry about them.
What this patch does is pass a command to the kernel which remaps the 3 large partitions at boot time. Since we're flashing system images from recovery, we also need to pass the same command to the recovery kernel before attempting to flash the main system, or we'd be writing to one place then telling the kernel to look for it in another.. bad idea.
This method allows any partition setup you like, but the most useful at the moment (and this is the way firerat has set up his scripts to suit cm5) is to make the /system partition just the right size for the "ROM" with a bit of breathing space, make the /cache partition a minimal size for the recovery system to use, then have /userdata fill the remaining space so we can load it up with apps. Since we've reduced cache to a minimal size, it's redirected at boot time to a place on the sdcard instead.. this give us maximum space to divide between /system and /data with no wastage.
Does that help at all..?
Thanks dude. That does help a lot.
Just wondering though, how much breathing space do u need in the system partition?
What does the recovery system use the cache partition for and how do we know what "a minimal size for the recovery system to use" is?
Is it possible to reduce the userdata partition to the minimum possible size a partition can be(if i recall correctly it was 128kb) and use an ext partition on your SD card instead?
If we shrink the Cache partition a lot, does this mean we have to use linux swap to compensate for the lowered amount of cache?
Also do we have to remap the partitions every time we flash a new ROM?
And what are the "dragons"?
kingkurry said:
And what are the "dragons"?
Click to expand...
Click to collapse
He's saying that it's just there. There could be anything from nothing there to a text document containing the ingredients to the cure of AIDs.
Well what about every thing else? Can you guys help me with that? Also what is the total size of all 3 of the big partitions combined?
I've search the forum and find different ways to move dalvik-cache from data partition to cache partition, from creating links or mounting, to a2sd command, but none of them worked for me. In all cases after reboot another dalvik-cache with system access will created along the dalvik-cache the method created in data partition. so I have two dalvik-cache folders (that one of them is link) and system will use the real one that will waste my data partition size.
this is how it look like:
Code:
drwxrwx--x system system 2010-10-23 12:30 dalvik-cache
drwxrwxrwx root shell 2010-10-23 11:41 dalvik-cache
I am struggling to find a way to free some memory on /data partition, as I rooted without unlocking the boot loader, I couldn't be able to resize the data system and cache partitions, (booted into fastboot mode, used fastboot command to erase system but it couldn't be erased with a access denied error).
Anybody can you please help?
I am on stock Froyo 2.2.1 and rooted without unlocking bootloader.
bohlool said:
I've search the forum and find different ways to move dalvik-cache from data partition to cache partition, from creating links or mounting, to a2sd command, but none of them worked for me. In all cases after reboot another dalvik-cache with system access will created along the dalvik-cache the method created in data partition. so I have two dalvik-cache folders (that one of them is link) and system will use the real one that will waste my data partition size.
this is how it look like:
Code:
drwxrwx--x system system 2010-10-23 12:30 dalvik-cache
drwxrwxrwx root shell 2010-10-23 11:41 dalvik-cache
I am struggling to find a way to free some memory on /data partition, as I rooted without unlocking the boot loader, I couldn't be able to resize the data system and cache partitions, (booted into fastboot mode, used fastboot command to erase system but it couldn't be erased with a access denied error).
Anybody can you please help?
I am on stock Froyo 2.2.1 and rooted without unlocking bootloader.
Click to expand...
Click to collapse
I think the stock kernel re-establishes the file system on boot and does not support moving anything.
I think you'll need a custom rom and kernel with apps2ext support to do what you're wanting.
Try the latest test release of my rom (in my sig), has everything you need.
djmcnz said:
I think the stock kernel re-establishes the file system on boot and does not support moving anything.
I think you'll need a custom rom and kernel with apps2ext support to do what you're wanting.
Try the latest test release of my rom (in my sig), has everything you need.
Click to expand...
Click to collapse
Is there any other way? e.g. Changing something, or Install something to make it no re-establishment? Or any way to change the partition sizes on Stock ROM (rooted but without unlocking boot loader)
bohlool said:
Is there any other way? e.g. Changing something, or Install something to make it no re-establishment? Or any way to change the partition sizes on Stock ROM (rooted but without unlocking boot loader)
Click to expand...
Click to collapse
Nope.
Root and be done with it, that's why people get the Nexus...
Edit: Hang on... I didn't read properly...
But the answer's still no... Just load a custom rom/kernel, you're already rooted.
Edit 2: Even with a custom rom you can not change partition sizes.
Just a quick question:
What happens to system-dalvik-cache under /cache, if I resize this partition to e.g. 5 MB?
I've read somewhere that CM7 moves it to /data. true? Are there any other disadvantages of such a small cache-partition?
many thanks!
Someone?
10chars
Yes, on CM7, if the cache partition is too small, it will move it to the /data partition. I think it is /data/local/cache
Dalvik-cache never resides on /cache anyway. /cache is for Market and OS OTA downloads. If you make it too small - your Market downloads might fail.
I didn't even realize he was talking about dalvik cache. The dalvik cache resides on the /data partition by default for both system and data apps.
As Jack_R1 said, the cache is only used for temporary files, like OS upgrades and market downloads. If the cache partition gets below a certain point (I think it is 5MB), CM7 will automatically change the cache directory to the /data partition.
On my device the market download folder has already a symlink to my /data partition. Other then my system dalvik. At least it seems so.
Thanks for your help. So i can go ahead and resize with blackrose
Hey there.
In twrp I can't change my system partition file system to F2FS. To do it, I enter twrp and do the "normal" steps (wipe, advanced, change to f2fs).
TWRP says it changed but if I perform the same steps the file system type remains ext4.
Is this supposed to be like this?
You cannot format the system
It's really not practical to change the filesystem of /system since it's distributed as an image and not as files. You theoretically could do it, but it would be a lot of work and you'd have to redo it from scratch every time you updated your ROM. Also, you wouldn't get most of the benefits of f2fs since you'd almost never be writing to it.
hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
n0te8user said:
hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
Click to expand...
Click to collapse
If you are using twrp from this thread, it's mentioned on the 3rd post
corsicanu said:
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Click to expand...
Click to collapse
or maybe try to disable data encryption which is mentioned on the 1st post
corsicanu said:
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Click to expand...
Click to collapse
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
ace2nutzer said:
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
Click to expand...
Click to collapse
i know i tried this but mine stock rom installed after flashing with odin (turkey) and after apply twrp format data stock rom are very different. the second i said seems like global rom. it contains weird settings and apps I will do what you say and take a screenshot,1 2 hours later you will understand me better.