Related
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 recently had to Run the repartition un-superbrick guide, Where I had to change the Start and end Point of the UMS partition.
After a long battle, I Managed to get a rom Running (Stock ics German open lpy).
The effects of the restoration Process were as follows:
Random Freezes, which require Force reboot. seems to be prone to them right After boot.
The Freeze occurs also when installing any App from play Store. However, I Was able to install SwiftKey 3 via apk.
The Internal sdcard is only 8gb on size, Where it used to be 11.
Any Ideas what to do?
Bump.. No one has any Ideas? :/
+1 same here would love to know as well. Only mine freezes after some multitasking not exactly like yours.
Sent from my GT-N7000 using xda premium
Same issue here. My UMS is 4 Gb. I think is problem of data partition but i restored it about 10 times. I'm running G&B ICS rom
Try to ODIN back to stock Gingerbread, root, and flash a safe CM9 rom.
Edit:
Or stay on Gingerbread. See if you still have freezes.
After restoring from brick, i installed GB stock from my operator and still freezing ramdomly, once was cuz i did multitasking, another one cuz i installed apps from market.... Cyanogen the same, i'm thinking that another partition is bad, but cache is good:
Here my modified values:
mkpartfs primary ext2 5000 6100
mkpartfs primary ext2 9000 11000
mkpartfs primary fat32 11500 15200
name 9 FACTORYFS
name 10 DATAFS
name 11 UMS
Hello
Did you find a solution I got the same problem but I don't know what I can do to solve it
I have the same problem. Anyone can solve it?
im experiencing the same situation, perhaps any solution/findings?]
Install cm based rom from gb, they use around 100mb space instead of 600mb. The issue here is that you're maxing out your reduced partitions so stock roms will struggle.
Sent from my GT-N7000 using xda premium
Changing rom is a good idea.
Another idea is to use tool under adb to check partitions. Use e2fsck with -c option to scan the partitions 7, 9, 10 to see if it find bad blocks and sometimes can fix them. If it reports no bad blocks find, that means those partitions are ok. Some time it find bad blocks and could fix or mark them, then we do not need to do re-partition again. (it will tell kernel to avoid those faulty blocks). If e2fsck freezes then there are serious fault it cannot fix and will requires more re-partition. It also no harm to check partition 11 as well, using dd/parted tool. Hope it may help. cheers.
A little leg work is required.
FIRST, NANDROID BACKUP
Second you'll need to format and partition your external sdcard as follows.
Four partitions:
First partition is for normal use formatted to FAT32
THESE PARTITIONS SHOULD BE FORMATTED TO WHATEVER KERNEL YOU PLAN ON USING. FOR EXAMPLE IF YOU ARE GOING TO USE FAUX 1.45 EXT4, FORMAT THE FOLLOWING PARTITIONS AS EXT4. IF YOUR NOT GOING TO USE EXT4 KERNEL FORMAT THE FOLLOWING PARTITIONS AS EXT3! If you're using windows download mini partition tool and set all partitions as primary, not logical and label them appropriately!
Second partition is for /system. Should be 350 MB
Third partition is for /cache. Should be 750 MB
Fourth partition is for /data. Should be 2.3 GB
Now that you have your sdcard partitioned download terminal emulator and run the following command BEFORE you flash the sd rom.
su
mkdir -p /sdcard/Boot/Phone
mkdir -p /sdcard/Boot/SD
cp /dev/block/mmcblk0p11 /sdcard/Boot/Phone/boot.img
Click to expand...
Click to collapse
Reboot and flash Nottachtrix to your sdcard
Once you've booted into Nottachtrix on your sdcard download terminal emulator and run the following command
su
cp /dev/block/mmcblk0p11 /sdcard/Boot/SD/boot.img
Click to expand...
Click to collapse
now download smanager from the play store and run the attached script (created by sendust7 and modified by me) as root with argument 1 to boot back into your phone rom (argument 2 from phone rom to boot back to SD). Rename the script to boot-rom.sh. You'll need smanager in your phone rom to reboot back into your sdrom
I did not develop this rom, only modified to boot from external sd card. Report any bugs/requests here.
A huge thanks to Sendust7 without whom I would have never had any clue on how to even get started and to Nottachtrix for the best Atrix GB rom out there.
Nottachtrix1.3.1.sd-ext.zip
If you're having problems with formatting sdcard go here and show sendust7 some love.
I'm working on an update that will eliminate running any commands. Just partition and flash.
now i'm partioning my sdcard,will report for u soon
i have a question: can i flash anyrom on emmc and it doesn't affect on this rom on sdcard,right? and how can i flash mod to this rom?
edit:can't boot,in the end of the installation,it failed to extract boot.img
can u make video guide?
mafiarock93 said:
now i'm partioning my sdcard,will report for u soon
i have a question: can i flash anyrom on emmc and it doesn't affect on this rom on sdcard,right? and how can i flash mod to this rom?
edit:can't boot,in the end of the installation,it failed to extract boot.img
can u make video guide?
Click to expand...
Click to collapse
I can when i get home....which kernel did you select?
Sent from my DROID RAZR using Tapatalk 2
hatefuel19 said:
I can when i get home....which kernel did you select?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
i choose faux 1ghz and 1.3 ghz,both dont work for me,just get error
i really want to flash nottachtrix to sdcard and another rom like miui to emmc,also can u add faux kernel from topogigi 1.1 rom,he've added init.d support to the kernel,if u know how to add init.d support to faux kernel,please add it to latest 026 faux kernel,tks btw ^^
So could I have NottachTrix with webtop on SD-Ext and CM9 on device? I would love to be able to use Netflix again!
Sent From My ICS Moto Atrix 4G
does webtop work correctly?
Adam
Does the rom automatically install to sdcard?
Any way to boot nottachtrix on internal with working webtop and cm7 or cm9 on external?
Sent from my MB860 using XDA
i choose faux 1ghz and 1.3 ghz,both dont work for me,just get error
i really want to flash nottachtrix to sdcard and another rom like miui to emmc,also can u add faux kernel from topogigi 1.1 rom,he've added init.d support to the kernel,if u know how to add init.d support to faux kernel,please add it to latest 026 faux kernel,tks btw ^^
Click to expand...
Click to collapse
I dunno what might be happening. Maybe bad download. I've installed with all faux kernels and no problems here. Sorry but I am not a dev, only modified a few things in the installer to get this to flash to external sd card. I'm uploading a video of the entire process from the point of installing to sdcard. Should have it posted soon.
So could I have NottachTrix with webtop on SD-Ext and CM9 on device? I would love to be able to use Netflix again!
Click to expand...
Click to collapse
YES! That was my entire motivation for getting this working. I haven't been able to get webtop2sd working but I think gentop would be a reliable candidate if you want full linux.
Does the rom automatically install to sdcard?
Click to expand...
Click to collapse
Yes, once you have your sdcard partitioned properly it flaseh to sdcard just like regular installer would flash to phone
Any way to boot nottachtrix on internal with working webtop and cm7 or cm9 on external?
Click to expand...
Click to collapse
You should check out
sendust7's post on this
ok,when i have free time,i'll try again,tks btw,i'll see your guide video to see if it help me,which app do u use to partitioning your sdcard?
Sent from my MB860 using Tapatalk 2
mafiarock93 said:
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
You can use GParted from any Linux based Live CD.
Mini partition tool for windoze
Sent from my DROID RAZR using Tapatalk 2
I´m going crazy over here: I followed everything in the instruction to the letter (although I used mini partition tool) and every time I got the following message at the end of the install:
Installing Kernel
assert failed:
package_extract_file("customize/ramfix/faux/100/kernel/boot.img", "/cache/boot.img)
After reboot I always land on my phone Rom - no chance to get into SD-Rom...
I guess something went wrong with the partioning...
You should really make a guide for windows on how to partition the SD Card.
If youre using mini partition tool on windoze all partitions should be primary, not logical. The boot img extracts to /cache, then mmcblk0p11 (phone boot partition) and then is deleted from cache. Double check your partitions on sdcard and make sure there all primary
Sent from my DROID RAZR using Tapatalk 2
I actually got it working!
It´s only painfully slow and unresponsive - guess my class 4 SD-Card is to ****ty xD
Thank you so much for your work!
schwarzlichtkind said:
I actually got it working!
It´s only painfully slow and unresponsive - guess my class 4 SD-Card is to ****ty xD
Thank you so much for your work!
Click to expand...
Click to collapse
I wondered that exact answer... is it slow? Hmm I wonder what class my SD card is.
Sent from my MB860 using Tapatalk 2
I honestly havent noticed a difference in speed other than 1st boot, but then again i use 1.45 kernel on daily driver and my sd is class4
EDIT: schwarz what got it working? Primary partition?
Sent from my DROID RAZR using Tapatalk 2
hatefuel19 said:
I honestly havent noticed a difference in speed other than 1st boot, but then again i use 1.45 kernel on daily driver and my sd is class4
EDIT: schwarz what got it working? Primary partition?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yes, but since I'm really noobish in the Dual-Boot-business, I also made another mistake: I didn't know that you actually have to name the partitions. After doing that and using gparted, it worked... Kind of... Had a boot loop on first try (faux 1GHz kernel), flashed again and used stock D 00 kernel.
I need further testing
Sent from my MB860 using Tapatalk
How can I flash the webtop, I tried flashing the fruitcake webtop-236 but it returned an error.
Sent from my MB860 using Tapatalk
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:
Hello, I am new to SD-ext and Link2SD and such things, I googled around a little and found the most suitable solutions for the internal memory shortage of CM10.1 is either Link2SD or INT2EXT+
Now I want to ask, which is better at performance, more stable?
I would have went around experimenting as they say but the problem is that I don't know how to remove either of them, so please tell me that too, so if I didn't like one of them I remove it and try the other.
That's all for now, thanks in advance!
I would suggest int2ext, because effectively it increases the size of your internal storage instead of moving apps to sd. As long as you have a class 10 or better sd, you won't notice any difference in performance.
Sent from my GT-S5570 using xda premium
ast00 said:
I would suggest int2ext, because effectively it increases the size of your internal storage instead of moving apps to sd. As long as you have a class 10 or better sd, you won't notice any difference in performance.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Unluckily I don't have a class 10 SD right now and I doubt my ability to get one for a while. Currently having a Class 4 16GB SD, what do you think would work best?
Mathspy said:
Unluckily I don't have a class 10 SD right now and I doubt my ability to get one for a while. Currently having a Class 4 16GB SD, what do you think would work best?
Click to expand...
Click to collapse
You can still use int2ext, but you will get a quite noticeable performance decrease. Just test it! To remove just go to system/etc/init.d, then you can just remove its files.
Sent from my GT-S5570 using xda premium
ast00 said:
You can still use int2ext, but you will get a quite noticeable performance decrease. Just test it! To remove just go to system/etc/init.d, then you can just remove its files.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
I actually tried Link2SD (With a EXT4) but it didn't read or create a script. I googled, people said use EXT2, so I just said, since it didn't work, let's try INT2EXT.
I flashed it (without removing Link2SD) and nothing changed...
I, just now, removed Link2SD and restarted: no changed.
What do you advice me to do? ((I think the problem is because this ROM doesn't support EXT4, but I am not sure of course))
Mathspy said:
I actually tried Link2SD (With a EXT4) but it didn't read or create a script. I googled, people said use EXT2, so I just said, since it didn't work, let's try INT2EXT.
I flashed it (without removing Link2SD) and nothing changed...
I, just now, removed Link2SD and restarted: no changed.
What do you advice me to do? ((I think the problem is because this ROM doesn't support EXT4, but I am not sure of course))
Click to expand...
Click to collapse
Int2ext needs ext 4. After removing link2sd, you should reposition your sd to ext 4. And which Rom you have? Because current ones are all sporting init.d, so they support sdext.
Sent from my GT-S5570 using xda premium
Mathspy said:
I actually tried Link2SD (With a EXT4) but it didn't read or create a script. I googled, people said use EXT2, so I just said, since it didn't work, let's try INT2EXT.
I flashed it (without removing Link2SD) and nothing changed...
I, just now, removed Link2SD and restarted: no changed.
What do you advice me to do? ((I think the problem is because this ROM doesn't support EXT4, but I am not sure of course))
Click to expand...
Click to collapse
there's an updated version of Link2EXT (4.2) as on some devices the SD-EXT wasn't found
ast00 said:
Int2ext needs ext 4. After removing link2sd, you should reposition your sd to ext 4. And which Rom you have? Because current ones are all sporting init.d, so they support sdext.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
I have CM10.1 Lastest nightly. What do you mean by reposition your SD to EXT4? You mean to create a EXT4? (I already have one)
pryerlee said:
there's an updated version of Link2EXT (4.2) as on some devices the SD-EXT wasn't found
Click to expand...
Click to collapse
Oh, so you think that update will work? I will try it now.
EDIT: Nothing new: After reinstalling it and choosing EXT4 it still say "Mount script cannot be created"
NEW EDIT: I apologise, I now know where did the error come from, I stupidly enough installed an EXT3 instead of EXT4.
Link2sd work fine with me on CM7 or CM10.1
On your cm7 you should set allow installing data on sd card and in settings of link2sd should be set on automatic
Ext2 on link2sd work fine with me
Sent from my GT-S5570 using xda app-developers app
in some devices, even If your partition is of ext2 or 3., it mounts it as ext4 itself
so while using link2sd try recreating mount script as ext4
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in some devices, even If your partition is of ext2 or 3., it mounts it as ext4 itself
so while using link2sd try recreating mount script as ext4
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
When im shifting between cm7 and cm10.1 recreating mount script on link2sd using ext2 also work on my mini
Sent from my GT-S5570 using xda app-developers app
Thankies!
and2nckiko said:
Link2sd work fine with me on CM7 or CM10.1
On your cm7 you should set allow installing data on sd card and in settings of link2sd should be set on automatic
Ext2 on link2sd work fine with me
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Would you mind writing me a little guide of what you did to install it on CM10.1?
(I will try EXT2 if everything you have done I tried.)
soham jambhekar said:
in some devices, even If your partition is of ext2 or 3., it mounts it as ext4 itself
so while using link2sd try recreating mount script as ext4
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
I changed it to EXT4, and tried it as EXT4 when it was EXT3 but nope, still doesn't want to work...
and2nckiko said:
When im shifting between cm7 and cm10.1 recreating mount script on link2sd using ext2 also work on my mini
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Well, seems I should really change it from EXT4 to 2, I guess that's what I will try.
Thanks everyone so far! :good:
Since you have the latest CM10.1 nightly.. I suggest u try this..
Take a complete back up of your SD card.
Make sure u have uninstalled any apps and removed any scripts related to link2sd and such scripts. (When there's any doubt whether the old scripts would cause any problem, i always prefer wiping the device and freshly installing the rom to avoid any mistakes)
If u do not have any problem flashing the ROM again, i really suggest u to do so and then do the below steps. Definitely should work.
Reboot into recovery mode.
Go to advanced option and select SD partitioning option
Select the partition size as 1024mb and swap size as 0mb.
Proceed with partitioning.
Reboot your device.
Save fixed-int2ext+ for android 4.2..1 by CronicCorey on the root of your SD card..
Boot into recovery again.
Go to mounts and storage option and mount data, system and sd-ext.
Go to install zip from SD card.. Choose zip from SD card.. Select the int2ext+ script.
After installation.. Go to mounts and storage and unmount data and system and format sd-ext.
Now reboot the device and check.. It'll be done.
I have done this many times and it's worked. I use 16gb class 4.. No issues.. Smooth for me..
After installing this script.. Make sure u dont wipe dalvik cache using recovery mode. Your device will get into boot loop.. Use wipe dalvik cache script specifically created for int2ext by croniccorey..
For more details/downloads refer to the following link:
http://forum.xda-developers.com/showthread.php?p=37961204
Sent from my GT-S5570 using xda premium