Hello,
If i need to resize the sd partition (swap and app, ie to expand swap fro 32 to 64mb) the only wai is to re-format the sd or i can use gparted?
If i change the swap size i must change the value in some files or rom do this in automatic way?
I've found some info about resize sd, but i haven't understand very well...
Tnx to xda!
Idk
idkidk said:
Hello,
If i need to resize the sd partition (swap and app, ie to expand swap fro 32 to 64mb) the only wai is to re-format the sd or i can use gparted?
If i change the swap size i must change the value in some files or rom do this in automatic way?
I've found some info about resize sd, but i haven't understand very well...
Tnx to xda!
Idk
Click to expand...
Click to collapse
Of course you can use Gparted! In my opinion it's the best/easiest way. It will also let you resize your ext if you need too, but don't make it more than 1GB. The ROM will automatically adjust to the swap size, nothing needs to be altered after changing the swap size.
I am not sure if I am remembering this correctly as it was some time ago, but Gparted would not resize an ext4 partition for me... If you are using ext3 then it should resize just fine...
If I am wrong, someone please correct me...
Vermithrax said:
I am not sure if I am remembering this correctly as it was some time ago, but Gparted would not resize an ext4 partition for me... If you are using ext3 then it should resize just fine...
If I am wrong, someone please correct me...
Click to expand...
Click to collapse
To be honest it doesn't really matter. Just boot in to Ubuntu or any other linux distro (assuming the gparted live CD doesn't have a file manager) and copy over the app, app-private, and and configuration files on your ext to a place on your hard drive. Then delete the partition, resize fat/swap as you wish then add a new ext4 partition, mount it and copy your stuff back. Only do that when the card is mounted in recovery, not when the phone has booted in to the ROM.
resize partition
You can try to resize partition with Partition Manager.
This is the best choice to resize partition.
And it is free for use.
I used it, worked well.
So, I tell you this; hope you can solve this problem efficiently.
extend-partition.com/help/how-to-resize-partition.html
Go and see it, you can get useful information.
Is there a way to dualboot roms?
Sent from my GT540 using Tapatalk
I really know nothing about dualbooting but i don't think the optimus swift has the guts for it
No.
someone correct me if i
am wrong, but our phones can't dualboot.
It could be possible by creating new partitions. For example, have two system partitions and two data partitions. We can flash one boot.img to the boot partition for the ROM to automatically boot, and flash another to the recovery partition. So when you hold home, it will boot into the second boot.img instead.(recovery images are exactly the same as boot images but with a modified ramdisk that runs the recovery program)
Where in the second boot.img, we can modify the init.rc file to mount a different partition as /system (a data2system rom works sort of like this, init.rc is modified so the data partition is mounted as /system, and system is mounted to /data, this is how you get more space as data is stored on /system, but Android thinks its acessing the data partition, where it is really accessing system) We can use this principle to dual boot.
Now, how will this work. Somehow split the system and data partitions into two bits (2 system partitions and 2 data) If we have the 1st ROM on the original system partition, and use its original boot.img, and then have the 2nd rom on the different system partition, and modify the ramdisk to use the different partitions as /system and /data, we could have a working dual boot.
However, there are some problems.
1. Our device has a NAND that is 512MB in size. It is split into:
Boot
Recovery
System
Userdata
Cache
and some other miscellaneous partitions. System is 250MB in size, and data is 134MB (under stock partition sizes) These split would barely fit any rom on it and hardly any data either. Maybe if the device had 1GB ROM, it may be different.
2. It may require some bootloader tweaking to create these new partitions, and for the device to recognise them.
Also, why would you want to dual boot your phone anyway? You have a computer for that
App
There is this app named BootManager
I've tried it out but this can't backup the boot partition. It's currently not supported. Maybe someone could try it out.
Keep in mind that it needs to be purchased for 'LEGAL' use.
jhonnyx1000 said:
There is this app named BootManager
I've tried it out but this can't backup the boot partition. It's currently not supported. Maybe someone could try it out.
Keep in mind that it needs to be purchased for 'LEGAL' use.
Click to expand...
Click to collapse
I tried that! Gives an error when backing up boot image!
Sent from my GT540 using Tapatalk
effortless. said:
Also, why would you want to dual boot your phone anyway? You have a computer for that
Click to expand...
Click to collapse
Actually I don't
Sent from my GT540 using Tapatalk
It is possible to dualboot. A russian guy already made it for us. It was meant to dualboot 2.1 and 2.2 but that rom has never made it to beta stadium.
The idea is that a second rom is stored on the sd card. I've tried to get it working but i didnt succed. But it should work.
It was on 4pda.ru. when i am on my computer, i will post a link.
Joost
Sent from my GT540 using Tapatalk
Couldn't we use the same principal as running Ubuntu chroot? As I thought chroot and loop devices where originally for HTC to test builds? Correct me if I'm wrong here
But I always thought if you had say a 32gb SD you could have 2 or 3 roms plus a couple Linux distros running on the device through chroot not same time obviously device would handle 2 max?
Also I was looking at a article to run native Linux on the eee pad transformer it looked like all they did was swap the boot.img or some kind of script so it ran off the SD card straight away. So my question would be could you add a feature to recovery that would allow you to change boot.img or script for each rom/distro then reboot straight into it making the device multi boot?
Sent from my GT540RR using XDA App
This is the topic about the dualboot, with download links to the 'dualboot' boot, and some explanation about the partitions on the sdcard.
http://4pda.ru/forum/index.php?showtopic=200838
Joost
liamwilli said:
Is there a way to dualboot roms?
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
This should be possible. But, would require customizing boot.img and boot loader.
ErnuB said:
I really know nothing about dualbooting but i don't think the optimus swift has the guts for it
Click to expand...
Click to collapse
effortless. said:
It could be possible by creating new partitions. For example, have two system partitions and two data partitions. We can flash one boot.img to the boot partition for the ROM to automatically boot, and flash another to the recovery partition. So when you hold home, it will boot into the second boot.img instead.(recovery images are exactly the same as boot images but with a modified ramdisk that runs the recovery program)
Where in the second boot.img, we can modify the init.rc file to mount a different partition as /system (a data2system rom works sort of like this, init.rc is modified so the data partition is mounted as /system, and system is mounted to /data, this is how you get more space as data is stored on /system, but Android thinks its acessing the data partition, where it is really accessing system) We can use this principle to dual boot.
Now, how will this work. Somehow split the system and data partitions into two bits (2 system partitions and 2 data) If we have the 1st ROM on the original system partition, and use its original boot.img, and then have the 2nd rom on the different system partition, and modify the ramdisk to use the different partitions as /system and /data, we could have a working dual boot.
However, there are some problems.
1. Our device has a NAND that is 512MB in size. It is split into:
Boot
Recovery
System
Userdata
Cache
and some other miscellaneous partitions. System is 250MB in size, and data is 134MB (under stock partition sizes) These split would barely fit any rom on it and hardly any data either. Maybe if the device had 1GB ROM, it may be different.
2. It may require some bootloader tweaking to create these new partitions, and for the device to recognise them.
Also, why would you want to dual boot your phone anyway? You have a computer for that
Click to expand...
Click to collapse
Your idea is right and would work but we can't afford to loose the recovery. It's important when modding. Unlike fastboot or KDZ modes, using recovery leaves one partition untouched. ie, when using recovery, the recovery partition is never modified. It doesn't touch boot loader either. It's almost impossible to brick a phone using recovery. And, if something goes wrong with other partitions, you can always boot into recovery and have stuff restored or fixed with an update.
jhonnyx1000 said:
There is this app named BootManager
I've tried it out but this can't backup the boot partition. It's currently not supported. Maybe someone could try it out.
Keep in mind that it needs to be purchased for 'LEGAL' use.
Click to expand...
Click to collapse
It's an HTC only app. It's an xda project. You can get it for free. Hit on to http://forum.xda-developers.com/showthread.php?t=1184173
joostvhoek said:
It is possible to dualboot. A russian guy already made it for us. It was meant to dualboot 2.1 and 2.2 but that rom has never made it to beta stadium.
The idea is that a second rom is stored on the sd card. I've tried to get it working but i didnt succed. But it should work.
It was on 4pda.ru. when i am on my computer, i will post a link.
Joost
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
Thanks. Would love to try it out.
Danzano said:
Couldn't we use the same principal as running Ubuntu chroot? As I thought chroot and loop devices where originally for HTC to test builds? Correct me if I'm wrong here
But I always thought if you had say a 32gb SD you could have 2 or 3 roms plus a couple Linux distros running on the device through chroot not same time obviously device would handle 2 max?
Also I was looking at a article to run native Linux on the eee pad transformer it looked like all they did was swap the boot.img or some kind of script so it ran off the SD card straight away. So my question would be could you add a feature to recovery that would allow you to change boot.img or script for each rom/distro then reboot straight into it making the device multi boot?
Sent from my GT540RR using XDA App
Click to expand...
Click to collapse
chroot is not a real dual boot solution. It's based on the idea of virtualization and so it has performance issues on a low end phone like GT540. When using chroot, parts of the Android OS as well as the other OS is run at the same time. This would be idea only in faster devices with more RAM.
And, yes, if you can modify the boot.img or recovery.img to boot into other partitions, it would be awesome. The beauty of linux is that you can directly mount images as a disk unlike in Windows where you need a separate software. Due to this, mounting a different partition would be easy but modifying the boot.img or bootloader is the risky part. If you do it wrong, your phone may get permanently bricked.
joostvhoek said:
This is the topic about the dualboot, with download links to the 'dualboot' boot, and some explanation about the partitions on the sdcard.
http://4pda.ru/forum/index.php?showtopic=200838
Joost
Click to expand...
Click to collapse
Thanks
joostvhoek said:
This is the topic about the dualboot, with download links to the 'dualboot' boot, and some explanation about the partitions on the sdcard.
http://4pda.ru/forum/index.php?showtopic=200838
Joost
Click to expand...
Click to collapse
I don't understand or talk Russian. Would anybody be kind enough to find out what modifications did he do to the boot.img and/or bootloader? If we do the same modifications, we might be able to dualboot.
But, there's one problem, the boot.img is not same for all versions. Maybe that is why you can't dual boot.
It wouldn't work on the gt540. We have a dual boot for the defy which has only 90mb of ram left Max when running dual system. Usually I'm running 190mb ram on stock and 240mb on miui. Major slow down on dual boot. So no point
Sent from my MB525 using xda premium
keewanchoapsss said:
It wouldn't work on the gt540. We have a dual boot for the defy which has only 90mb of ram left Max when running dual system. Usually I'm running 190mb ram on stock and 240mb on miui. Major slow down on dual boot. So no point
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
You are talking about chroot. In real dual boot, only one OS is loaded.
nibras_reeza said:
I don't understand or talk Russian. Would anybody be kind enough to find out what modifications did he do to the boot.img and/or bootloader? If we do the same modifications, we might be able to dualboot.
But, there's one problem, the boot.img is not same for all versions. Maybe that is why you can't dual boot.
Click to expand...
Click to collapse
Oh I'll be looking into this one tomorrow, I'd like to be able to have a dual boot... this would enable me to store testing roms onto sdcard and boot into them "safely" without forever having to go through backup & restore each time...
If I can crack it... I'll post it!!
Edit: I don't read Russian either... but I can reverse engineer things like this! -- Just had a brief look at it... I should be able to port his modifications over to another image, but as you said... it'll only work if both OS's are compatible with the one boot.img ... and this could take some trial and error.
Second Addition: Not to mention... it could cause issues for some people that use ext partition on sdcard for apps.... hmmz, will have to keep that in mind. (People like me ya'see lol)
olite said:
Oh I'll be looking into this one tomorrow, I'd like to be able to have a dual boot... this would enable me to store testing roms onto sdcard and boot into them "safely" without forever having to go through backup & restore each time...
If I can crack it... I'll post it!!
Edit: I don't read Russian either... but I can reverse engineer things like this! -- Just had a brief look at it... I should be able to port his modifications over to another image, but as you said... it'll only work if both OS's are compatible with the one boot.img ... and this could take some trial and error.
Second Addition: Not to mention... it could cause issues for some people that use ext partition on sdcard for apps.... hmmz, will have to keep that in mind. (People like me ya'see lol)
Click to expand...
Click to collapse
People who use ext for moving apps shouldn't face problems. Android is not Windows. =P It can handle unlimited number of partitions. Looking at the guide, I could understand that the method uses multiple ext partitions. People using sd-ext for apps would only need to increase the mtdblockn(where n is a number) by 1 or 2 if using swap as well.
Yup. Both OSs will work only if the boot.imgs are compatible. That means we might not be able to run 1.6 and 2.3. However, this wouldn't be applicable if you can loop the boot.imgs as well.
ie a setup likes.
BOOT has a GRUB like boot loader which is compatible with Android is SYSTEM.
SYSTEM partition has one OS.
Then, there will be different BOOT and SYSTEM is each of the sd-ext partition or they will be stored as imgs in SD.
When device boots, it will enter BOOT. Then, this will present a menu which will allow you to select OS. If you choose, default, it will load SYSTEM from phone. If you choose another, it will loop to a BOOT from the SD-ext which will loads its relevant SYSTEM from SD/SDEXT.
That's just my idea though. Basically, if you can get an idea of the modifications that need to be made to BOOT.img to loop mount another partition as BOOT or SYSTEM, then the problem is 80% solved.
nibras_reeza said:
People who use ext for moving apps shouldn't face problems. Android is not Windows. =P It can handle unlimited number of partitions. Looking at the guide, I could understand that the method uses multiple ext partitions. People using sd-ext for apps would only need to increase the mtdblockn(where n is a number) by 1 or 2 if using swap as well.
Click to expand...
Click to collapse
lol, yer I worded that wrong... I meant it *could* be a problem if they just followed his guide steps (since it doesn't account for existing use of ext on sdcard), but you'r right this isn't really a problem... it just requires an additional partition. Also, I'd probably change the partition layout instead so that applications such as Link2SD would still be able to "automatically" (it only checks partition #1) locate the ext partition intended for apps.
Something like this...
Partition #0: FAT32
Partition #1: EXT2/3 <-- sd-ext2
Partition #2: EXT2/3 <-- data
Partition #3: EXT2/3 <-- system
Partition #4: SWAP
This would allow most internal OS's to continue to function as per normal without any script modifications.
(Most swap mount scripts are just blind scripts, they simply try mounting each partition from #1 to #9 as swap... so swap location shouldn't be an issue)
#!/system/bin/sh
#
# find and enable swap
#
echo 30 > /proc/sys/vm/swappiness
# find swap partition
for PART in `seq 0 9`;
do
swapon /dev/block/mmcblk0p$PART
if [ $? = 0 ]; then
break
fi
done
Click to expand...
Click to collapse
nibras_reeza said:
That's just my idea though. Basically, if you can get an idea of the modifications that need to be made to BOOT.img to loop mount another partition as BOOT or SYSTEM, then the problem is 80% solved.
Click to expand...
Click to collapse
And a damn good one at that... sadly I think this might just be a lil bit out of my reach... for now! While I should be able to get it to work for 2.1-2.3 (Since they essentially use the same boot), I honestly don't know where to begin with boot looping (I understand the concept yes, just not sure how to implement it... wonder if I can bake a grub version for this...)
This idea is really exciting. I wish i could help but as it stands, based on my extreme lack of know-how, i'd be as much help as a sack of potatoes XD
Sent from my GT540 using XDA App
olite said:
lol, yer I worded that wrong... I meant it *could* be a problem if they just followed his guide steps (since it doesn't account for existing use of ext on sdcard), but you'r right this isn't really a problem... it just requires an additional partition. Also, I'd probably change the partition layout instead so that applications such as Link2SD would still be able to "automatically" (it only checks partition #1) locate the ext partition intended for apps.
Something like this...
Partition #0: FAT32
Partition #1: EXT2/3 <-- sd-ext2
Partition #2: EXT2/3 <-- data
Partition #3: EXT2/3 <-- system
Partition #4: SWAP
This would allow most internal OS's to continue to function as per normal without any script modifications.
(Most swap mount scripts are just blind scripts, they simply try mounting each partition from #1 to #9 as swap... so swap location shouldn't be an issue)
And a damn good one at that... sadly I think this might just be a lil bit out of my reach... for now! While I should be able to get it to work for 2.1-2.3 (Since they essentially use the same boot), I honestly don't know where to begin with boot looping (I understand the concept yes, just not sure how to implement it... wonder if I can bake a grub version for this...)
Click to expand...
Click to collapse
Porting grub eh? Hmm. I believe there should be an ARM version for grub but we might have trouble with the drivers and kernel. It might be a better idea to copy the menu layout from CWM recovery. The menu need not be intelligent.
As for me, I also don't know how to loop the boot images.
daggerxXxsin said:
This idea is really exciting. I wish i could help but as it stands, based on my extreme lack of know-how, i'd be as much help as a sack of potatoes XD
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
You could always risk your phone for others by using the pre-alpha. xD
Porting grub eh? Hmm. I believe there should be an ARM version for grub but we might have trouble with the drivers and kernel.
Click to expand...
Click to collapse
We wouldn't need a kernel for GRUB, as GRUB loads the kernel. We would have to modify the bootloader (or MBR) to use GRUB.
I'm on latest CM9 with Semaphore 1.2.4, but this latest update used up a lot of space in /system partition which only left me 2MB spaces. I need extra spaces for system app and new bootanimation, how?
You cant change the system partition size however to get the space in it try moving your app to sdcard.
-----Sent using RemICS-i9000-----
Even I need help with it..
Sent from my GT-I9000 using Tapatalk 2
erpurohit said:
You cant change the system partition size however to get the space in it try moving your app to sdcard.
Click to expand...
Click to collapse
How sure are you on that? From what I understand PIT files in ODIN can change partition layout. If one can change partition layout, one should be able to increase /system as well.
That said, I find Android very confusing. Some examples:
Onboard flash is not a SD card. A SD card is something you can just pull out of the device. Yet android refers to the onboard flash - or well, more accurately a specific partition on the onboard flash - as SD card.
CWM backup is supposed to do a *FULL* backup. Yet it does not include my pictures. No matter what format/wipe options I choose in CWM, the pictures don't go away... I have a whole different concept off a full wipe / factory reset / format SD than that.
It seems several tools format the wrong thing.
App data directories seem to move all over the place. I usually make nandroid backups and I have issues restoring my app *data* every time I use another ROM.
All that said, I'm a big time linux user. I'm extremely familiar with system maintenance on computers. However Android is new to me. All the confusing on naming etc. however is a HUGE !#@%!!#% obstacle.
But why explain things clearly or use terms what they're for. Much easier to confuse people right? At least someone can make money of it then.
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
jay_ingale said:
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
Click to expand...
Click to collapse
All new version of jelly bean will be of this size only....
Delete /system/media/videos and convert cyanogenmod wallapapers to user apps. Saves ~15 mb
Sent from my GT-I9000 using xda premium
Sorry to bump such old thread.
I was offered a I9000 that I would like to use as second phone.
I flashed I9000XXJVU_I9000OXAJVU_OXA through odin, and then root (cf-root) and MackayRom 1.7 .
As it says in the rom thread, I have a space problem. Is there any chance better than this one?
Any possibility of repartitioning the internal storage?
Here is my partition scheme:
Developer delta-roh made a script for the HTC Sensation that enables it to mount /sd-ext as "internal memory", on a sufficiently fast sdcard this would mean you could make the data partition as big as your sd-ext partition.
This is the thread: TURBO DATA - 8GB DATA PARTITION
The script is only for the Sensation, but the dev said in the thread it could theorically be adapted for other phones:
This is ONLY for the HTC Sensation/XE; it can work also for flashable images of other devices, but then you have to open the batch mni.bat file in the directory @bins and to change the strings for userdata_org1/2, userdata_new1/2 - however, you should only do this if you know exactly what you are doing - and look out the string pairs org1/new1 and org2/new2 have to have the same length! NO SUPPORT!
Click to expand...
Click to collapse
The script involves converting a ROM zip, and requires a ROM with a boot.img file. Adapting it would involve tinkering a bit with partition names, as the Desire's are probably different... But it could be feasible, and it could solve the internal memory problem many Desire 500 users have.
I have a Sensation with a class 10 sdcard, and the mod works pretty well for me, it solved the internal memory problem.
I do not have a Desire 500 handy right now (it's my girlfriend's phone), but maybe somebody could try their hand at this? They're both HTC phones and have similar partitions. Maybe it's not too hard?
Any devs want to try?
Working, thank you very much (tested on single sim)
Puzzlemanx said:
Working, thank you very much (tested on single sim)
Click to expand...
Click to collapse
What? Really? You didn't even need to adapt it? Tell us everything, please, which ROM did you use? Which SDCard? This could be great news!
I simply did what is said in the article... (stock rom)