My English is bad
I want to install GSI, but my phone's(vie-al10)system partition is too small...
I tried to use parted, It can't boot on EMUI8. IT JUST boot on LineageOS16...
Can anyone help me?
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?
Hi folks,
I have been using G1 for 6-7 months and had never faced this frigging problem ...i think it all started when i tried to flash an HTC sense ROM!! I did all the things as instructed for flashing, but it dint work.. Then i reverted to Gingerbread(version-2.3.4) which i was using before. Though the ROM worked i was sickened to see my internal storage memory as it had only 17.75MB left!!! . My phone has now Total space just 17.75MB out of which the available space is only 6.70MB!! .. Here is a screenshot of my phone storage-
While flashing a swap size of 32 was kept and sd-ext was given 512MB
Any idea how to recover from this frigging problem?????
thanx...
Remove cMTD ...
Flash the following File, reboot into fastboot, do a "fastboot erase system -w" and reinstall your ROM. This should help ...
Thnx for that quick reply.. .. by 'fastboot' did you mean 'recovery mode'.. I flashed the file and then manually wiped all the data's,dalvik-cahce and other things.. is that enough?
@ AndDiSa It worked .. that was frigging awesome man!! thanx a lot.. now i have 92MB free.. can you please explain me what the problem really was?
haha your problem was that you flashed a custom MTD partition (most likely 145 2) on your device for that sense rom.. but when you do that you need to flash fr-boot after you flash any other rom while you still have that partition.. but since you went back to a diff rom you thought you didnt need the fr-boot lol, so your phone didnt have the correct amount of mb..
When you wipe your data and all that it does NOT remove the custom mtd... thats why you needed to flash the FR-Remove file!! to remove the MTD partition... which basically put your device back how it was when first rooted... 90 2 ... thats the stock partition size for a g1
So long story short your device will be fine and you can re try to flash that sense rom or do anything you want... just be sure to remove a custom mtd if you flashed one for a rom... and plan to change roms.. unless you switch to a rom that also needs a mtd partition.. than you dont have to flash remove.. just flash the boot file after flashing rom. lol sorry if that was confusing..
ldrifta said:
haha your problem was that you flashed a custom MTD partition (most likely 145 2) on your device for that sense rom.. but when you do that you need to flash fr-boot after you flash any other rom while you still have that partition.. but since you went back to a diff rom you thought you didnt need the fr-boot lol, so your phone didnt have the correct amount of mb..
When you wipe your data and all that it does NOT remove the custom mtd... thats why you needed to flash the FR-Remove file!! to remove the MTD partition... which basically put your device back how it was when first rooted... 90 2 ... thats the stock partition size for a g1
So long story short your device will be fine and you can re try to flash that sense rom or do anything you want... just be sure to remove a custom mtd if you flashed one for a rom... and plan to change roms.. unless you switch to a rom that also needs a mtd partition.. than you dont have to flash remove.. just flash the boot file after flashing rom. lol sorry if that was confusing..
Click to expand...
Click to collapse
... that was very confusing.
The base you explained correctly: There was still installed the cMTD patch which gave you a custom partition layout with a big /system partition, but a very small /data partition.
This partition layout is defined by boot img parameters, as in recovery, as for the ROM. Most new ROMs (especially GB-ROMs) detect cMTD automatically, i.e. it's sufficent to patch the recovery image while the boot image is patched automatically when installing the ROM.
When you switch between ROMs the partition layout will be kept, as it was for you when you switched back to the "old" GB-ROM. To return to the "standard" layout (which is defined by the SPL you have installed on your phone), you either have to flash a "clean" recovery, or to remove the cMTD layout with the file I gave you.
If you are more interested in cMTD, in my signature you can find a link to the appropriate thread ...
AndDiSa said:
... that was very confusing.
The base you explained correctly: There was still installed the cMTD patch which gave you a custom partition layout with a big /system partition, but a very small /data partition.
This partition layout is defined by boot img parameters, as in recovery, as for the ROM. Most new ROMs (especially GB-ROMs) detect cMTD automatically, i.e. it's sufficent to patch the recovery image while the boot image is patched automatically when installing the ROM.
When you switch between ROMs the partition layout will be kept, as it was for you when you switched back to the "old" GB-ROM. To return to the "standard" layout (which is defined by the SPL you have installed on your phone), you either have to flash a "clean" recovery, or to remove the cMTD layout with the file I gave you.
If you are more interested in cMTD, in my signature you can find a link to the appropriate thread ...
Click to expand...
Click to collapse
lol sorry im not really sure how the mtd partitions really work.. i just knew i had to use it at one point and i read up a little about it but that was a while ago... so i kinda forgot the exact details.. thank you for clearifying!!
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
doctoralex said:
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
Click to expand...
Click to collapse
I'm facing the same problem. I think I know what the problem is but I cannot solve it!
I currently have installed Stefan 28G ics rom (2nd edition) and my goal is to add about 100mb to the system partition, reducing internal /sdcard.
If I use fdisk command from adb shell I find out that the partion IS actually resized, but the file system on it isn't!!
So: partition now is 650Mb, but file system on it is 550Mb!
That's because nvflash simply makes a dd of the system.img (which has the old partition size) to the partition so in my opinion there are two solutions:
a) open system.img in a linux environment, add some stuff to reach 650Mb on it and repack it with the new size
b) backup system data, formata the partition (which is already resized) to get 650Mb file system and then restore your system data
I think that all "resizing guide" doesn't talk about this second step because in that case the system.img has always the right size.
Any ideas?
Raffaele80 said:
I'm facing the same problem. I think I know what the problem is but I cannot solve it!
I currently have installed Stefan 28G ics rom (2nd edition) and my goal is to add about 100mb to the system partition, reducing internal /sdcard.
If I use fdisk command from adb shell I find out that the partion IS actually resized, but the file system on it isn't!!
So: partition now is 650Mb, but file system on it is 550Mb!
That's because nvflash simply makes a dd of the system.img (which has the old partition size) to the partition so in my opinion there are two solutions:
a) open system.img in a linux environment, add some stuff to reach 650Mb on it and repack it with the new size
b) backup system data, formata the partition (which is already resized) to get 650Mb file system and then restore your system data
I think that all "resizing guide" doesn't talk about this second step because in that case the system.img has always the right size.
Any ideas?
Click to expand...
Click to collapse
I solved my problem!
As explained before I have just added some stuff to the system.img file and then resized the file system:
dd if=/dev/zero bs=4096 count=35328 >> system.img
e2fsck -f system.img
resize2fs system.img
PS: bs and count depend on the partition size that you have set before in the .cfg file
Then NVFlashing again solve the problem!
doctoralex said:
I have a problem. I have try to resize the partition using nvflash. I have use guide from modaco and also the preconfigured files. The problem is that /system is always at ~360mb (stock size). All other partitions are resized propertly.
Any help?
Click to expand...
Click to collapse
Backup your rom with cwm.
Format /system in cwm.
Restore your cwm backup.
Sent from my LG-P990 using xda app-developers app
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
So I'd like to install some kind of a gsi which is larger than 3 gb so i'd want a system partition to be about 5-6GB in size but I never used parted in my life, I'm a noob at this. please help