There are a lot of ways of moving /data to SD ext(2nd) partition. Here I'll show you an easy way to do it which is fully compatible with Samsung Galaxy ACE(and possibly other devices as well). If you don't like the method used here, try other Data2SD/ext mod which may suit your needs.
Why move dalvik-cache to RAM? Basically, the idea of moving the whole /data partition to SD ext partition is to primarily get more space for installing apps. And in this case, it does perform very well and combined with fast SD cards, it could even provide real-life performance boost. Now the downside to this, is that while most /data contents just get copied and read not that much often, dalvik-cache stores some info that needs to be read and updated very frequently. This results in a high I/O read/write frequency and thus results in shortening of the SD card life(in theory, the same could also be said when left internally but this time dealing damage to the nand disk instead). To counter this, the method I used is to move dalvik-cache to a virtual-disk like partition known as a tmpfs. tmpfs resides in RAM and has dynamic resizing structure which can allocate space depending on your needs. This way, dalvik-cache won't be using any physical disk and therefore causing damage to none. Almost too good to be true right? Well the drawback is, because tmpfs resides in RAM anything written onto it get's lost when rebooted or in-case of power loss thus resulting in loooong boot times(depending on the apps installed), as dalvik-cache contents are being rebuilt on every boot. Well I think that's enough of dalvik-cache and lets start with the mod.
WARNING
USING A NON-APP2SD / NON A2SD / NON-LINK2SD ROM OR SIMPLY UNINSTALLING NON-APP2SD / NON A2SD / NON-LINK2SD IS STRICTLY RECOMMENDED
DO NOT EVEN TRY THIS MOD IF YOU HAVE ANY FORM OF NON-APP2SD / NON A2SD / NON-LINK2SD INSTALLED
ALWAYS PERFORM A BACKUP BEFORE TRYING OUT STUFF LIKE THESE
Disclaimer: I am not responsible for anything bad happening in the world blah blah, you know the drill!
Put the files of Data2SD_for_SGA.zip inside the corresponding places on your phone manually.
system/bin/e2fsck
system/xbin/busybox_d2sd
system/etc/install-recovery.sh
--------------------------------------
Basic Requirements
1. Fresh ROM
2. Rooted
3. No A2SD, No App2SD, No Link2SD
4. SD Card Partioned to Ext2 and Fat32
5. SD Card must be original (NOT Class A) as much as possible Class 4 and up.
6. Make sure that your SD Card is partitioned accordingly. Just like how you did when using link2sd.
7. Previous link2sd users need not partition your SD Card. Just format the EXT2 partition.
Steps
1. Flash DXKC1 ROM in your phone
2. Partition your SD Card with EXT2 (first) then the remaining FAT32
3. Root your phone with SuperOneClick then reboot
4. Before inserting the SD Card remove .android_secure, Android and LOST.DIR folders. And make sure that EXT2 is clean
5. Copy the extracted Data2SD_for_SGA.zip on your SD Card
6. Install Root Explorer on your phone
7. Copy the files from the extracted Data2SD_for_SGA.zip to your phone using root explorer
system/bin/e2fsck
system/xbin/busybox_d2sd
system/etc/install-recovery.sh
8. After successfully copying the files, reboot phone.
9. Turn on phone and wait. The initialization might take some time depending on the speed of read/write of your sdcard.
10. If errors has been encountered, REPEAT THE STEPS FROM STEP 1.
Thanks Ungaze
All credits goes to Ungaze of TCP / XDA
Hi, it tried 3 times and it's not working for sga.
Would that work also on GingerBread? AFAIK automount scripts make SGA reboot as per Link2SD issue.
@mastrone -> Link2SD and Data2SD is a different thing.. But both won't work on Gingerbread because install-recovery.sh is quoted inside init.rc
@roninxt -> worked for me... i am using DXKC1 ROM...
tazzz811 said:
@mastrone -> Link2SD and Data2SD is a different thing.. But both won't work on Gingerbread because install-recovery.sh is quoted inside init.rc
@roninxt -> worked for me... i am using DXKC1 ROM...
Click to expand...
Click to collapse
I'm also using that rom. But i didn't flash to a fresh rom. I had a Link2sd installation before and i followed the steps. I also uninstalled Link2sd.
Can someone explain why do we need a fresh rom?
Can someone explain why do we need a fresh rom?
Click to expand...
Click to collapse
When you have an applications installed before putting data2sd in its place... Some or most of the application will result to FORCE CLOSE... That's the reason why it should be applied on a FRESH ROM.
I experienced it before when i got excited on applying Data2SD having 200 apps installed... The result, i got FORCE CLOSES on most of my applications.
But you can still try it out on a currently running ROM in your phone, make sure that you have no a2sd, app2sd or link2sd installed..
Change the title
please specify this for GINGERBREAD or FROYO
roninxt said:
Can someone explain why do we need a fresh rom?
Click to expand...
Click to collapse
Basically to avoid/minimize errors with conflicting mods prior to this mod. If you're an advanced user(or something like that) you probably know what you're doing already so fresh ROM install is not necessary but still recommended.
@tazz811
Nice work man, I'm assuming that the current custom ROM available for SGA does not have init.d support as of now and that's why you placed the script inside the install-recovery.sh script. Well, this might sound useless but, why not make install-recovery.sh call any scripts from init.d? Maybe something like:
Code:
list=`ls /system/etc/init.d/*`
for k in $list
do
sh $k
done
this way, you can run the data2sd script from init.d which will then make it easier to make modifications as well as allow other scripts to run on init.d.
@Ungaze... Thanks for the idea... You owe all the credits... It's me LTGB
list=`ls /system/etc/init.d/*`
for k in $list
do
sh $k
done
Click to expand...
Click to collapse
my understanding of this simple script is, it will run any script found inside system/etc/init.d/ folder.
Internal Storage Capacity Increased
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got huge Quadrant Score
This is the result of Data2SD on my SGA - DXKC1 ROM
tazzz811 said:
This is the result of Data2SD on my SGA - DXKC1 ROM
Click to expand...
Click to collapse
what is read/write speed of yours SD card..?
what is read/write speed of yours SD card..?
Click to expand...
Click to collapse
i'm using transcend 8gb class4
tazzz811 said:
my understanding of this simple script is, it will run any script found inside system/etc/init.d/ folder.
Click to expand...
Click to collapse
Exactly
Dude, TCP is already a giveaway lol.
is it working with VillainROM or KPE too..? or it is just for FROYO..?
is it working with VillainROM or KPE too..?
Click to expand...
Click to collapse
No.. It's not working on a rooted Gingerbread ROM (Stock or Villain ROM). The init.rc is kinda secured even if you unquote install-recovery.sh it will revert back to the original state. Therefore install-recovery.sh will not be executed during boot time.
http://62.0.5.133/oi51.tinypic.com/qzk8z9.jpg
working on it! thanks man. TCP rules
Ok i got it to work. I have about a couple of apps installed about 10 and i was successful running the script. I uninstalled all my other apps. I didn't encounter force closes. So yes i can confirm that d2sd will work even on an existing sga rom. But you need to uninstall most apps including big ones as this might lead to a force close.
not work on my SGA,install from fresh rom dxkc1
my sd card 8 GB class 10 - make ext-2 first then fat32
following your instruction, tried almost 10 times and still not work for me....
Related
original topic here
http://forum.xda-developers.com/showthread.php?t=919326
just in case you miss it
this app is great for our phones with limited storage space
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
way better to use than App2SD App and/or the App2SD script that most of us are using with the XT720
Thumbs up To get Link2SD working the XT720...
Thanks to Riley600
I've worked with the developer and found the issue. Motorola phones can't mount the ext2 partition and need to install the ext2.ko file (this file is installed when you install app2sd).
Unfortunately, right now the steps are manual to install this (otherwise the apk would largely increase in size). But once this is done (you need root access, obviously), Link2SD will work. I used Root Explorer to copy ext2.ko to the necessary directory - however, I'm sure it can be done using adb commands. I'm not confident enough with my adb skills to give instructions based on that - so if someone else knows better than I, please feel free to give your own instructions.
1) Download the ext2.ko file (zip attached)
2) Extract it to your SD card
3) Use Root Explorer to navigate where you extracted it to and copy the file
4) Navigate to /system/lib/modules/ and paste the ext2.ko file there
5) Reboot - Link2SD should now mount the ext2 partition and function correctly!
Currently, if you link a file to the SD card, it will not show up in the Market until it is unlinked. The developer is looking into a solution for this. Otherwise, it's a solid program - I've left my Home Launcher (ADW) on the phone's memory which seems to have reduced stuttering and slowdowns from when it was installed on the SD card with app2sd.
I'll try to answer any other questions about the installation of this program on the XT720 if you have any.
Thanks to Bulent for working with me to find a solution to the issue with Motorola phones!
Attachment on post # 8 http://forum.xda-developers.com/showpost.php?p=10866898&postcount=8
How does one removed an already installed version of App2SD (via the script) and retain all their programs? I searched it and some people seem to indicate that you have to reflash your phone...
AllGamer said:
original topic here
http://forum.xda-developers.com/showthread.php?t=919326
just in case you miss it
this app is great for our phones with limited storage space
way better to use than App2SD App and/or the App2SD script that most of us are using with the XT720
Click to expand...
Click to collapse
Any tips on getting this to work? I tried setting up my SD card with both the "Mini free" tool & gParted live CD & the app won't recognize my ext2 partition.
same here I tried his new version too
Sent from my Milestone XT720 using XDA App
I have the same issue as the others. It says it can't mount my partition but it's there and worked with app2sd. Any suggestions?
So, is it not working?
raidontaro said:
So, is it not working?
Click to expand...
Click to collapse
Doesn't seem like it. I provided the developer with some info about our phone so hopefully he can use that to get it working with the XT720.
To get Link2SD working the XT720...
I've worked with the developer and found the issue. Motorola phones can't mount the ext2 partition and need to install the ext2.ko file (this file is installed when you install app2sd).
Unfortunately, right now the steps are manual to install this (otherwise the apk would largely increase in size). But once this is done (you need root access, obviously), Link2SD will work. I used Root Explorer to copy ext2.ko to the necessary directory - however, I'm sure it can be done using adb commands. I'm not confident enough with my adb skills to give instructions based on that - so if someone else knows better than I, please feel free to give your own instructions.
1) Download the ext2.ko file (zip attached)
2) Extract it to your SD card
3) Use Root Explorer to navigate where you extracted it to and copy the file
4) Navigate to /system/lib/modules/ and paste the ext2.ko file there
5) Open an adb shell with super user (su) permissions and run the following command:
Code:
insmod /system/lib/modules/ext2.ko
6) Reboot - Link2SD should now mount the ext2 partition and function correctly!
It's a solid program - I've left my Home Launcher (ADW) on the phone's memory which seems to have reduced stuttering and slowdowns from when it was installed on the SD card with app2sd.
I'll try to answer any other questions about the installation of this program on the XT720 if you have any.
Thanks to Bulent for working with me to find a solution to the issue with Motorola phones!
I've made small change in the application and released 1.0.5. What I did for Motorola users is to add insmod line to install-recovery.sh script if /system/lib/modules/ext2.ko file exists.
In this way all you have to do manually is to copy ext2.ko file to modules directory and then install link2sd.
You can install latest version from the app thread.
Thanks to Riley for his contribution.
nice i'll try this when i get home in about 20 mins... ur the men... lol
I havent tried apps2sd, but this seems like an very creative app that i'll have to give a try
bakpinar said:
I've made small change in the application and released 1.0.5. What I did for Motorola users is to add insmod line to install-recovery.sh script if /system/lib/modules/ext2.ko file exists.
In this way all you have to do manually is to copy ext2.ko file to modules directory and then install link2sd.
That means first four steps in Riley's instruction are sufficient, after these you can install link2sd-1.0.5 and start using.
You can install latest version from the app thread.
Thanks to Riley for his contribution.
Click to expand...
Click to collapse
Instructions updated - thanks Bulent
I've no idea if it is due to the fact that my SD card is malfunctioning, but after following steps I still received the error when I open the app. So I ran the install-recovery.sh script through terminal apparently and got the below message
Any ideas?
# sh install-recovery.sh
insmod: init_module '/system/lib/modules/ext2.ko' failed (File exists)
mount: No such file or directory
#
Sent from my Milestone XT720 using XDA App
hardKNOXbz said:
I've no idea if it is due to the fact that my SD card is malfunctioning, but after following steps I still received the error when I open the app. So I ran the install-recovery.sh script through terminal apparently and got the below message
Any ideas?
# sh install-recovery.sh
insmod: init_module '/system/lib/modules/ext2.ko' failed (File exists)
mount: No such file or directory
#
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Did you set up a ext2 partition on your SD card? You need both a Fat32 partition and a ext2 partition. Instruction on how to set that up on your SD card are here:
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
Once you do that and then follow my instructions with the ext2.ko I posted here, it should work (it did for me).
Riley600 said:
Did you set up a ext2 partition on your SD card? You need both a Fat32 partition and a ext2 partition. Instruction on how to set that up on your SD card are here:
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
Once you do that and then follow my instructions with the ext2.ko I posted here, it should work (it did for me).
Click to expand...
Click to collapse
Yeah formatted the card as fat32 and gave 900mb for ext2 partition (both as primary ) with the recommended software. I'll try it with another SD. Thanks for ur help.
Sent from my Milestone XT720 using XDA App
Strange, not sure what the problem is then.
New xt720 user here, i havent done the app2sd and froyo jit yet but was planning of doing it til i found this thread. If installing link2sd requires you to unistall the app2sd how do I install the jit as instructed here http://forum.xda-developers.com/showpost.php?p=7909401&postcount=52
basically i want to install links2sd and jit, would it be a whole new process?sorry for my ignorance.
allahmar said:
New xt720 user here, i havent done the app2sd and froyo jit yet but was planning of doing it til i found this thread. If installing link2sd requires you to unistall the app2sd how do I install the jit as instructed here http://forum.xda-developers.com/showpost.php?p=7909401&postcount=52
basically i want to install links2sd and jit, would it be a whole new process?sorry for my ignorance.
Click to expand...
Click to collapse
You just need to select the menu item for JIT and not Apps2SD from the numerical list the script presents you.
Riley600 said:
Strange, not sure what the problem is then.
Click to expand...
Click to collapse
check this out... this is what i've found in the directory /dev/block/vold through adb
Code:
pwd
/dev/block/vold
# ls -l
ls -l
brw-rw---- root root 179, 1 2011-01-25 10:04 179:1
brw-rw---- root root 179, 0 2011-01-25 10:03 179:0
#
i guess my ext2 partition is 179:1, should i edit my install-recover.sh file for this?
Edit: didn't work, i guess my ext2 partition is not being recognized. i'll try to find a linux machine and see if i can partition with Gparted
Odd, did you put the ext2.ko file in the correct directory? I was running into similar problems until I had the file in the directory noted and then the command to install it.
Thanks
Works perfect I checked yesterday. Greetings from Guatemala. Sorry for the English but the Google translator xD.
FlintFire_v1.0
Based on latest official stock firmware Android 2.2.2
FEATURES:
1)TJ Styles OC'd Kernel
2).Darktremor Apps2SD 2.7.5.3 beta 4(requires that you have ext2 or ext3 partition on your SD card; exact procedure to create one is described in installation procedure.)
3) Fully deodexed and zipalligned apps and framework.
4) Rooted.
5) Installed BusyBox with support for init.d scripts
6) Replaced stock boot animation with custom animation
8)Support for OpenVPN(not tested) and CIFS.
9)Removed some stock apps and updated Gapps.
8)Updated Documents to go and Maps to 5.9 with worldwide navigation.
9)Added a init.d script and tweaks to build.prop(Increased screen density and possible increase in net speed)
10)Repalced stock Launcher and File Manager.
11)Added the V6 SuperCharger Script(Just go to terminal and type: superc)
Firmware should also work with compatible devices such as: Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600 but I don't have these devices, so I cannot verify. As always make a backup before installing any custom firmwares.
Requrements:
Clockworkmod Recovery from here
Installation:
1)Create a backup using Clockworkmod Recovery.
2)If you dont have a A2SD EXT2 partition follow the first part of the instructions from here
3)Download the ROM and store it in the root of your SD Card.
4)Reboot into recovery mode,wipe data and cache and install the ROM.
Migrate from stock or another build:
1)Make backup of your phone using Titanium Backup (select all user applications).
2)Copy all files and folders from SD card to local folder on your computer.
3)Install Clockwork Recovery Partition, create partition on SD card and install ROM as described in installation guide.
4)Copy all files and folders from local folder on your computer back to SD card.
5)Restore applications using Titanium Backup and reboot your phone.
Download:
Code:
http://dl.dropbox.com/u/21654931/FlintFire_v1.0.zip
Credits:
TJStyle for his OC'd kernel and kernel source.
hucqim80 for his recovery
dsixda for his kitchen
Darktremor for his excellent Apps2d
zeppelinrox for his V6_Supercharger
Brut.all for his hacked version of Google Maps
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
v1.0
Initial Release
one question
hi
is ext4 ok as i have ext4 on my SD and is see u have mentioned that we need ext3
haree said:
hi
is ext4 ok as i have ext4 on my SD and is see u have mentioned that we need ext3
Click to expand...
Click to collapse
ext4 should work but you wont be able to backup your SD-EXT using clockworkmod recovery.
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
then restart and restore your apps.
googlehome said:
ext4 should work but you wont be able to backup your SD-EXT using clockworkmod recovery.
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
then restart and restore your apps.
Click to expand...
Click to collapse
hi
do i need to bakup my SD card to my PC before i do this as give below
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
i just have a Ext4 done via CWM and as of now app2sd works im using amalgamations rom right now
what u have mentioned is a little new to me
haree said:
hi
i just have a Ext4 done via CWM and as of now app2sd works im using amalgamations rom right now
what u have mentioned is a little new to me
Click to expand...
Click to collapse
If you made your partition using CWM then it is ext2 and not ext4 .
Please check your partition type by connecting your device to your PC and opening a partition manager which recognizes ext partitions.you will see that your SD Card is split into 2 partitions
FAT32 and EXT2.(You dont need to check if you trust my word )
You can safely use my ROM because your are using EXT2 and not EXT4.
whaaat... 1512 in quadrant... impressive
googlehome said:
If you made your partition using CWM then it is ext2 and not ext4 .
Please check your partition type by connecting your device to your PC and opening a partition manager which recognizes ext partitions.you will see that your SD Card is split into 2 partitions
FAT32 and EXT2.(You dont need to check if you trust my word )
You can safely use my ROM because your are using EXT2 and not EXT4.
Click to expand...
Click to collapse
hi
1.i trust ur words 100% man
2.im lazy to do all that checking i do have ur rom downloaded ill use it and keep u posted
thanks buddy for ur kind reply
Edit : i tried ur rom and it was good.but as i need the original keyboard and could not get it to work on ur ROM i went back to
amalgamation 1.3 ROM thanks
Which languages are included?
Sent from my ViewPad7 using XDA App
GHome, tell me how to get 1500 in quadrant score
wazzzuuuup2 said:
GHome, tell me how to get 1500 in quadrant score
Click to expand...
Click to collapse
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Use the data2sd feature:
>su
>a2sd datasd
No German language, only English, Vietnamese, ...?
Vcrone said:
No German language, only English, Vietnamese, ...?
Click to expand...
Click to collapse
dont ill include more languages in my next update
googlehome said:
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Click to expand...
Click to collapse
After I did that my tablet rebooted and was unable to boot. Guess it's stupid to try to convert the ext2 partition when it is in use? Well how do I do it then?
googlehome said:
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Use the data2sd feature:
>su
>a2sd datasd
Click to expand...
Click to collapse
it doesnt work... my quadrant score still stuck <1000 and even worst....
High quadrant score in the screen-shots is based on high CPU and high IO score so I would guess these tweaks would be highly dependent on sd card speed to get higher scores unless there is some swapping to ram going on to "fake" these IO speeds. I've read something about that while checking out data2sd > http://forum.xda-developers.com/showthread.php?t=852219
@googlehome: What brand and type of sd card are you using ? I'm very curious because I'm looking for the best one possible for our device.
Amalgation said:
High quadrant score in the screen-shots is based on high CPU and high IO score so I would guess these tweaks would be highly dependent on sd card speed to get higher scores unless there is some swapping to ram going on to "fake" these IO speeds. I've read something about that while checking out data2sd > http://forum.xda-developers.com/showthread.php?t=852219
@googlehome: What brand and type of sd card are you using ? I'm very curious because I'm looking for the best one possible for our device.
Click to expand...
Click to collapse
Im using a class 2 (not the best)16gb SD Card.You can create an ext3 partition with gparted from your PC.Im using ext3 currently
Thank you every much googlehome. Thank you. Thank you.
But i'm still can't play youtube HQ.
sorry for my weak english...
By the way, Wi-Fi is not working on my device with this ROM, just like it's not working with Amalgation's EUViewPad. It is, however, working with CleanViewPad ROM. I have HWVer 103.
Some of my impressions.
Wifi works on my Viewpad 7 HWV 1.03. Tle launcher is notably slower than the stock one. There is no email application and I don't know how to send and receive emails. It is not good as emails are very basic tablet function for me.
I am really courious how to "revive" icons from Dock "thrown" in the recycle bin?
Everything else is OK. One of my Quadrant scores was 1045.
hi all,
i juz wana know bout the functionality of all the programs in CWM 4.0.0.9.i had it installed but dun know much bout the stuff inside.juz knw bout back up n storage and applying updates from zip..and what is dalvik cache means...
Need info on dalvik cache? www.google.com will help u.
Sent from Galaxy Ace GT-S5830 using Grif's Cyanogenmod & allinone script.
Dont jus say thanks, use d 'THANKS' button. [XDA RULE]
Yes, just google everything. This factual stuff can easily be found through search.
There you go.... not from v4.0.0.9 but its of a old version but will give you and idea or to anyone else .. will not post a link to some other site so just posting the explaination here
Options explained
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.reboot system now
This one is self-explanatory.
2.apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses.
3.wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup
4.wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
This option brings up the following sub-menu:
A. apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
B. choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file and select it for installation
C.toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
D. toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (i don’t), it’s best not to change this option.
E. +++++Go Back+++++
Takes you back to the main recovery menu, obviously!
6.backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
A.Backup
Takes a Nandroid backup, as explained above.
B.Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
C.Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions
7.mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
A. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
B.format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device. To learn more about the contents of all these partitions, see our guide to Android partitions.
C.mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8.advanced
This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations. Here are the options from this section:
A.Reboot Recovery
Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
B.Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
C.Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
D.Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
E.Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
F.Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
G.Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Hope it helps :d
@devilcode , permission to add into the newbie guide please
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
@devilcode , permission to add into the newbie guide please
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Yea sure bro if you want i can insert screenshots also...before every point
EmoBoiix3 said:
@devilcode , permission to add into the newbie guide please
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Just quoted one of the sentence there to google and it shows that THIS is the actual source. Dont know if the poster is the author though.
QNBT said:
Just quoted one of the sentence there to google and it shows that THIS is the actual source. Dont know if the poster is the author though.
Click to expand...
Click to collapse
yea i mentioned ill not post an outside link in the begging so just pasted it here i dont have permission to post links yet
devilcode said:
yea i mentioned ill not post an outside link in the begging so just pasted it here i dont have permission to post links yet
Click to expand...
Click to collapse
ah, sorry. My bad.
devilcode said:
Yea sure bro if you want i can insert screenshots also...before every point
Click to expand...
Click to collapse
Do it .
I'd be grateful
devilcode- ur explanation is much appreciated..thank you...
all your guidance are very useful..especially devilcode..thanks man...now i can know the functions well....
EmoBoiix3 said:
Do it .
I'd be grateful
Click to expand...
Click to collapse
Their Edited My post With screen shots ...You can post in Newbie Guide now
ravin_jr said:
all your guidance are very useful..especially devilcode..thanks man...now i can know the functions well....
Click to expand...
Click to collapse
Ur welcome Glad to help ... N Click Thanks if you are really thankfull
Install and Configure a2sdgui ROM's CyanogenMod
Hello fellow good here I leave this tutorial hos to use a2sdgui based on CyanogenMod ROMs, as these ROMs do not include this system and its installation is different from a stock rom; a2sdgui is an app that allows us to extend the internal memory the mobile to have more space to install apps, this is accomplished by configuring two aspects: SD memory partition and installing a script called darktremor a2sdgui, well initiate:
THE WHOLE PROCESS IS DONE AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKS IN MOBILE IF YOU DO EVERYTHING AS SHOWN TO WORK ALL YOU ASSURE THAT CORRECTLY
RECOMMENDED TO DO BEFORE INSTALLING THE MOBILE APPS
Requirements:
- ROM based CyanogenMod 7.1 or 7.2
- Install a2sdgui (DOWNLOAD FROM THE MARKET)
- Script darktremor a2sdgui 2.7.5.3 Beta 04 (Download)
- SD card partitioned
Instructions:
1. - Install a2sdgui
2. - MicroSD Memory Partitioning:
First download the MiniTool Partition Wizard.
http://download.cnet.com/Partition-W...=dl&tag=button
Once installed, we put our SD on the PC (with a reader, adapter or anything like that) and open the program.
If you already have some partitions it is recommended that if we start from 0 erase all as shown.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After deleting all now begin creating them.
We give and we get this Edit menu and the first is FAT32.
We have to make FAT32 and Primary, we assign space is relative, I having 8GB (class 6) I put all but 1.5 will be for ext4 and swap.
Now for the ext4 partition, select PRIMARY. Now the partition type is relative, it is recommended that if your card is less than 6 class partition is ext2. If Class 6 or more ext4. That and I leave to your judgment, in my case I assign 1 GB will be to host the apps as if they were in the internal memory.
Now we use the remaining space for the swap partition (PRIMARY), in my case 500 Mb RAM With this more of our ACE will have 800 MB of Ram (the swap partition is a partition that is used like RAM, it is so important!)
APPLY Now we give and we get this message should accept and the thing to end as you see in the two screenshots below.
Partitions that I recommend are:
3. - Restart the phone in recovery mode
4. - Scroll to and select mounts & storage mount / data and mount / system
5. - Made the above should be unmount / data and unmount / system
6. - Now return to the main menu of recovery
7. - Enter to install zip from sdcard> choose zip from sdcard>-2.7.5.3-beta04 dtapps2sd-signed.zip
8. - Restart the phone, when you start DO NOT OPEN OR ANYTHING IN THE MOBILE, the mobile just restart again, it is NORMAL not alarmed.
9. After reboot, enter A2SDGUI. On the menu that appears in the display of APPS on SD are expected to be active and SWAP may also, in case this is not no more to give up and active. At the end of the menu is the VALUE SET 0-100, I got 100 and I gave the side.
10. - Now we turn to LowMen directly and I have chosen this, to me is the one that best suits me. The option below elijais leave more free memory, it is better but in my case having 800 mb is fine for me up there.
11. - Now let's Dalvik-Cache and choose it and click Move & Rebuild and phone will reboot.
AND THIS IS WHAT WE HAVE TO END MUCH MEMORY FREE AND ESPECIALLY A lot of RAM! ENJOY!
Link2sd is better ..and s2e is better heavenly
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Robbang said:
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
Click to expand...
Click to collapse
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
raymanlololo said:
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
Click to expand...
Click to collapse
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Robbang said:
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Click to expand...
Click to collapse
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
try this
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
ps1max said:
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
Click to expand...
Click to collapse
ambujpriyadarshi1991 said:
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
Click to expand...
Click to collapse
I think you guys didn't understood me; I'm on the stocklite v3, and it's a custom rom with DT scripts installed. Anyway I'll take a look over that threads ;-)
EDIT:
Haha, i've messed it up!
I don't know why or how, but now i have the app2sdgui running, but....also i had runngin link2sd, and several apps linked. Now i have a lot of "andro-boxes" (linked apps that are, seems, not readable) in my phone, a sdcard partitioned and a lot of information blocked.
I'm trying to create the mount scripts on link2sd to unmake the links, and start using app2sdgui, but link2sd can't because "device or resource busy"
Good, i'm the best! XD
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
If you use Swype beta you need authenticate them, but u can use a altenative, a swype modify, i dont know if i can post the link here, because i dont know if this is a warez... ?? but put in the google and search for DA SWYPE. In this web site you have many options of colors of swype.
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
Same goes here...cant activate the swap
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.