Database Users

NexusHD2-ICS-CM9 A2SD Discussion

How to increase the internal storage size for the NexusHD2-ICS-CM9 ROM.
May 17 updated:
Another choice. Don't need to flash anything.
Just install Link2SD app from the Google Play (a.k.a. Android Market).
Jan. 20:
Flash any of the A2SD scripts below when you install too many apps and the internal memory (i.e. data partition) is out of space.
Caution: Don't use any of them if you are not an advanced user. Otherwise you may have low volume, performance lag and other strange issues.
Installation guide for 40ad2sdx-a2Recovery.zip
Installation guide for Data2SD.
Installation guide for AD2SDX - AMARULLZ DATA TO SD-EXT.

This rom gets better by the hour! Thank you very much Tytung
Sent from my HD2 using XDA App

Thanks
Does the freeze issue related to A2SD ? My phone working and connected to GSM network but the touch screen is not working at all.

Thank you very much Tytung for the nice Rom !!!!

From the other thread:
manu44 said:
I have installed the Rom v1.1 by using the 40ext script to move the dalvik to sd card
and now i used it without the script
The DIfferemce is there
- No more apps lagging...Whatsapp used to take around 25 sec to show up when i was using my adtosd script
- No more screen lagging
- No more low sound issue
Click to expand...
Click to collapse
Of course you will get no more low sound issue, but since I have changed the read ahead SD speed to 2048 (not sure if thats the reason though) and changed the script that it copies all to SD card ext partition, I have a lot fewer lags than before, when the read ahead was 8mb and I used the unmodified Amarullz script (which leaves dalvik on internal).
Here are my posts for reference:
geenyous said:
Thanks tytung, will upload there next time.
Hmm, but I am using Amarullz script and still have ~300mb left.
Appears that it does the same as the app2sd script TyphooN is using, so every app you install still leaves a bit on internal but the majority goes to sd-ext. This would be about right as I have now 50mb less internal than with TyphooN (150mb partition compared to 200 now) and I had roughly 57mb free space on TyphooN internal with the same apps installed.
Anyone has an idea what to do besides uninstalling some apps?
Thx!
Click to expand...
Click to collapse
bobjbain said:
You can delete the stuff in the cache directory under /sd-ext/data_s/com.android.providers.downloads
...
That's bizarre, I don't know where it gets the 208m for /sd-ext when I have 2G ext4 partition on my card.
And why is /data 1G??
Anyway geenyous, in adb cd to /sd-ext/data_s/com.android.providers.downloads and issue a 'df *' that will tell you how much free space the system actually thinks you have in that directory.
HTH
Click to expand...
Click to collapse
This didn't work, that directory was almost empty...
uzi2 said:
http://forum.xda-developers.com/showpost.php?p=21216357&postcount=384
http://forum.xda-developers.com/showpost.php?p=21232738&postcount=438
http://forum.xda-developers.com/showpost.php?p=21233560&postcount=445
Click to expand...
Click to collapse
OK, just to report on the above Issue:
I have now reinstalled everything with the modified script posted by uzi2 above, now I have plenty of space (actually the internal sd-ext is empty, feels like bit of a waste) as all my stuff is on sd-ext4 (SD card), even dalvik cache. I can now install and update apps again. Just to make it clear for everyone: there is an sd-ext, which is located on NAND and there is sd-ext4 which is located on your SD card after you format it properly.
If you look at Amarullz script, you will see that per default, it will leave dalvik cache as well as system apps on sd-ext (internal). Now, this together with a 200mb system partition will lead to the sd-ext filling up as you install more apps which are considered system apps and consequently you will not be able to dl and update from market anymore. What uzi did, is remove the parts from the script that copy dalvik and those apps to sd-ext. Now, sd-ext is empty, no matter how many apps you install. Maybe it would be good to keep dalvik on sd-ext and only remove the "system apps move to sd-ext" part of the script? Dalvik was like 170mb of size last time I checked, is that constant or number of apps dependent? I must say I don't see any performance issue with dalvik on SD, but it just feels like a bit of a waste
Btw, I also changed the SD speed fix value to 2048 from ~8000 in the script as I think I can recall to have read that this would give the best performance.
Here is the code I am using atm (all the same like uzis except the SD speed):
Code:
#!/system/bin/sh
#
# AMARULLZ DATA TO SD-EXT MOD FOR ANDROID ( AD2SDX )
# ==================================================
#
# by amarullz [at] yahoo [dot] com
# xda-developers : amarullz
# (c) 2011
# * Oct 19 (ALPHA01)
#
# Info: ~ For Changing Log
##
###
# Initializing
###
#-- SDCard Speed Fix
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
#-- Unmount /sd-ext if it already mounted
busybox umount /sd-ext;
#-- Mount /data and move it to /sd-ext
busybox mount /data;
busybox mount --move /data /sd-ext;
#-- Mount sd-ext to /data ( You Will Get 1GB/2GB Internal Memory :D )
busybox mount -t ext4 -o noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /data;
busybox chown 1000:1000 /data;
busybox chmod 771 /data;
###[ SDEXT mmcblk0p2 STRICT ]###
# app, app_s, lib_s, app-private, data : should in /data (mmcblk0p2)
#
# ~ ALPHA02 - Add framework_s into (mmcblk0p2) strict - MODIFIED
###
for i in dalvik-cache tts_s app app_s lib_s plugins_s app-private framework_s weather_s data;
do
#-- If Symlink in /data, delete it
if [ -h /data/$i ]
then
busybox rm /data/$i;
fi;
#-- If Directory Exists in /sd-ext, move it to /data
if [ -d /sd-ext/$i ]
then
busybox mv /sd-ext/$i /data/;
fi;
#-- If Directory Not Extst in /data, create it
if [ ! -d /data/$i ]
then
busybox mkdir /data/$i;
#-- Just Open All Permissions ;)
busybox chmod 0777 /data/$i;
fi;
#-- Now Create Symlink From /sd-ext to /data
if [ ! -h /sd-ext/$i ]
then
busybox ln -s /data/$i /sd-ext/$i;
fi;
done;
###
# Now create symlink of the rest non Symlink Directories and Files on /sd-ext to /data
#
# ~ ALPHA02 - Fix ls to ls -a, it's ok, because we test -h for symlink
###
cd /sd-ext;
for i in `ls -a`;
do
if [ $i != ".." -a $i != "." ]
then
if [ ! -h /sd-ext/$i ]
then
if [ ! -h /data/$i ]
then
busybox ln -s /sd-ext/$i /data/$i;
fi;
fi;
fi;
done;
cd /;
###
# It should also need to create the rest non Symlink Directories and Files on /data to /sd-ext
# ~ ALPHA02 - Some Directory may be missing if we don't use it
###
cd /data;
for i in `ls -a`;
do
if [ $i != ".." -a $i != "." ]
then
if [ ! -h /data/$i ]
then
if [ ! -h /sd-ext/$i ]
then
busybox ln -s /data/$i /sd-ext/$i;
fi;
fi;
fi;
done;
cd /;
#-- Of Finished.... :D
And this is the part I would suggest maybe you could leave it in to get dalvik to sd-ext (internal):
Code:
###[ SDEXT mmcblk0p2 STRICT ]###
# app, app_s, lib_s, app-private, data : should in /data (mmcblk0p2)
#
# ~ ALPHA02 - Add framework_s into (mmcblk0p2) strict
###
for i in framework_s app app_s lib_s app-private data;
do
#-- If Symlink in /data, delete it
if [ -h /data/$i ]
then
busybox rm /data/$i;
fi;
#-- If Directory Exists in /sd-ext, move it to /data
if [ -d /sd-ext/$i ]
then
busybox mv /sd-ext/$i /data/;
fi;
#-- If Directory Not Extst in /data, create it
if [ ! -d /data/$i ]
then
busybox mkdir /data/$i;
#-- Just Open All Permissions ;)
busybox chmod 0777 /data/$i;
fi;
#-- Now Create Symlink From /sd-ext to /data
if [ ! -h /sd-ext/$i ]
then
busybox ln -s /data/$i /sd-ext/$i;
fi;
done;
###[ INTERNAL mtdblock5 STRICT ]###
# For performance, dalvik-cache should be on /sd-ext
###
for i in dalvik-cache;
do
#-- If Symlink in /data, delete it
if [ -h /sd-ext/$i ]
then
busybox rm /sd-ext/$i;
fi;
#-- If Directory Exists in /sd-ext, move it to /data
if [ -d /data/$i ]
then
busybox mv /data/$i /sd-ext/;
fi;
#-- If Directory Not Extst in /data, create it
if [ ! -d /sd-ext/$i ]
then
busybox mkdir /sd-ext/$i;
#-- Just Open All Permissions ;)
busybox chmod 0777 /sd-ext/$i;
fi;
#-- Now Create Symlink From /sd-ext to /data
if [ ! -h /data/$i ]
then
busybox ln -s /sd-ext/$i /data/$i;
fi;
done;
And this the part that should be removed:
Code:
###
# Now Important Thing, is to move the com.htc* and com.android* data to /sd-ext (internal)
# For Good performance. So the system applications will run smooth.
#
# System application will read/write in Internal memory, and 3rd apps will run on sdcard
#
# Notice: Will be affected in 2nd boot :D, so Reboot the system after 1st boot...
###
#-- Prepare data_s in /sd-ext ( For system data )
if [ ! -d /sd-ext/data_s ]
then
busybox mkdir /sd-ext/data_s;
#-- Just Open All Permissions ;)
busybox chmod 0777 /sd-ext/data_s;
fi;
#-- Now Move All com.htc* and com.android* to Internal Memory
cd /data/data/;
for i in `ls -d com.htc* com.android*`;
do
#-- Only Non Symlink
if [ ! -h /data/data/$i ]
then
busybox mv /data/data/$i /sd-ext/data_s/;
fi;
done;
#-- Create Symlink of /data/data_s/* to /data/data/ (mmcblk0p2)
cd /sd-ext/data_s/
for i in `ls -d *`;
do
#-- Only If Symlink Not Exists
if [ ! -h /data/data/$i ]
then
busybox ln -s /sd-ext/data_s/$i /data/data/$i
fi;
done;
Or you could do it the other way around, leave system apps on sd-ext (internal) and move dalvik to SD card? Uzi2, as you say your script is tested, did you test this and what were your findings?
I have attached the script in a flashable zip the way I use it now, all on SD card as well as SD speed fix change for anyone that also runs into market install / update troubles.
You have to do a fresh install though, clearing dalvik with the modified script will not move it to SD card and you have to install it the tried way, i.e. flash ROM (kernel), boot, reboot, reboot into recovery, flash script, reboot, set up google account and restore apps. Putting it in right from the beginning gave me bootloops (factory wipe install).
EDIT: Ok, it is confirmed that Dalvik cache is app dependent, it now has a size of 187MB (compared to the 178 I saw before) and I have another 200mb of sd-ext4 left to install more apps. So it is very well possible, that after installing further apps, the 10% space threshold of sd-ext (internal) will be reached again and Market will quit dl / updating apps as it did before. So it looks like the only viable option will be to leave the second part of the script in, the one where all the system (and htc) apps get moved to internal. Looking at the script, it appears that you could put this part in and it will move the apps to internal even after all has been on SD card, can anyone with coding skills please confirm?

Best way to use this script
May i add, that the best possible method is to copy the script file to the ROM zip Before Flashing. This way i didn't encounter any crashes, low volume, whatsoever!

d33f said:
May i add, that the best possible method is to copy the script file to the ROM zip Before Flashing. This way i didn't encounter any crashes, low volume, whatsoever!
Click to expand...
Click to collapse
This is because, there is no need to fix permissions using this method.
Obviously there is no need to wipe dalvik-cache on a fresh install, but if you refrain from doing so on an update, you should not encounter problems.
Please remember to copy the script into init.d on every update.

d33f said:
May i add, that the best possible method is to copy the script file to the ROM zip Before Flashing. This way i didn't encounter any crashes, low volume, whatsoever!
Click to expand...
Click to collapse
I really hate to ruin the party here, especially as I am also a fan of easy solutions, but after I made a factory wipe (a state where most new users will come from when they change CWM partition) and put the script in an otherwise unmodified zip, I had bootloops. And not just one, several.
This then worked for me:
- Format SD card with one FAT32 partition (primary, 32kb block) and one ext4 partition (primary, 4kb block)
- Boot into CWM
- Flash ROM (& Flash Kernel)
- Reboot and don't touch anything
- Reboot into recovery
- Flash script
- Reboot into ROM
- Reboot into CWM and fix permissions
- Reboot into ROM and start setting up your phone
- Done
If you update your ROM, then do the following:
- Unzip script zip (not ROM!)
- Copy the script (called something like "10ad2sd" or "40ad2sdx") to system/etc/init.d/ in ROM zip with something like 7zip
- Boot to CWM
- Flash ROM (& Kernel)
- Done

Thank you for this
This solved all my storage issues. Especially on this new rom. Now I am not experiencing any bugs whatsoever.

geenyous said:
I really hate to ruin the party here, especially as I am also a fan of easy solutions, but after I made a factory wipe (a state where most new users will come from when they change CWM partition) and put the script in an otherwise unmodified zip, I had bootloops. And not just one, several.
Click to expand...
Click to collapse
Was it a bootloop? How long did you leave it, before deciding this?
It will also depend on which a2sd script you use, so just because you encounter problems doesn't mean it's universal.
Edit:Having read the FAQ, I think you may be using Amarullz RC02, whilst I am using Alpha02 (amended)

uzi2 said:
Was it a bootloop? How long did you leave it, before deciding this?
It will also depend on which a2sd script you use, so just because you encounter problems doesn't mean it's universal.
Click to expand...
Click to collapse
You know me, I am not screaming wolf just to get attention. I was using exactly the same script you posted and I never said it was universal. I waited 10 mins, 3 times in a row before I decided to reflash without the script. Took some 3-5 mins and the Set up screen was there. Whatever is the cause here, none of us seem to understand it, at least I don't and you have not posted the reason.
So lets just leave it as it is, if it works, fine, if not, then go the long way, as easy as that

geenyous said:
You know me, I am not screaming wolf just to get attention. I was using exactly the same script you posted and I never said it was universal. I waited 10 mins, 3 times in a row before I decided to reflash without the script. Took some 3-5 mins and the Set up screen was there. Whatever is the cause here, none of us seem to understand it, at least I don't and you have not posted the reason.
So lets just leave it as it is, if it works, fine, if not, then go the long way, as easy as that
Click to expand...
Click to collapse
Even so, 10mins may not be long enough for the ROM to load and the script to perform it's initial functions. You are confusing 2 different versions of the Amarullz script. You may not have read my Edit before replying.

Q !. What tipe of SD card should i use class 4 class 6 or class 10 for a2sd scripts ?

uzi2 said:
Even so, 10mins may not be long enough for the ROM to load and the script to perform it's initial functions. You are confusing 2 different versions of the Amarullz script. You may not have read my Edit before replying.
Click to expand...
Click to collapse
Yes, I have replied before you edited, but still I am using your script
I have never used the one I linked to, just took that from OP. Before using yours I also took the one from Amarullz thread, but the flashable one (added link to FAQ).
Anyhow, it may be that 10 mins are not enough, but I am sure as hell that any other second on this topic is wasted, so I am going to leave it here.
nueloc said:
Q !. What tipe of SD card should i use class 4 class 6 or class 10 for a2sd scripts ?
Click to expand...
Click to collapse
4 or 6 is best.

I've installed 40ad2sdx-a2Recovery.zip as it was said it should be installed, and my phone is going nuts..
EVERYTHING is so slow, even thoe SetCPU is configured correctly.. my phone acts like it's on 400MHz all the time!
Second thing, and the biggest thing are all those FCs.. almost every app is FC, and when I start it again, it SOMETIMES works ok..
Facebook is useless, Market sometimes, Quadrant is giving me <1000 results, Twitter is so slow I can't stand to load up a page, Gallery is working every second time..
And it all worked so darn fast before this App2SD patch..

Hey guys...I've got a problem with the latest ICS build ([15.Jan.2012] NexusHD2-ICS-4.0.3-CM9 V1.1). I'm using a T-Mobile HD2 with MAGLDR v1.13, and I can load ICS up successfully. Calling works and my signal reads full with 3G (with Wind Mobile), but I can't activate the wifi (switching on results in nothing, as if the system attempts to but can't), and 3G appears to be inaccessible with Google Accounts/browser even though it is configured correctly. I've tried wiping, re-installing (with 1024 MB ext4 partition), and putting initrd.gz in an update folder for updating...nothing appears to be working. Can anyone help? Much thanks in advance.

Cold-Tea said:
I've installed 40ad2sdx-a2Recovery.zip as it was said it should be installed, and my phone is going nuts..
EVERYTHING is so slow, even thoe SetCPU is configured correctly.. my phone acts like it's on 400MHz all the time!
Second thing, and the biggest thing are all those FCs.. almost every app is FC, and when I start it again, it SOMETIMES works ok..
Facebook is useless, Market sometimes, Quadrant is giving me <1000 results, Twitter is so slow I can't stand to load up a page, Gallery is working every second time..
And it all worked so darn fast before this App2SD patch..
Click to expand...
Click to collapse
As I understand it, 40a2sdx is Amarullz RC02, which is known to cause problems with this ROM. The Alpha02 is 40a2sd and should work well.
Edit: Sorry, I see that Alpha02 is also 40adsdx. The script I used is based on Alpha01 (40a2sd) - Sorry for the confusion.
The links are now correct in the FAQ

I got problems with touch screen.When i unlock my phone it acts like im still presing or scrolling,and its driving me crazy.When i type sms it presses button by itself,it scroll menu by itself.Even today,when i touch screen the screen get some purple colour,and when im not touching it its ok.Please help me

RyanGDI said:
Hey guys...I've got a problem with the latest ICS build ([15.Jan.2012] NexusHD2-ICS-4.0.3-CM9 V1.1). I'm using a T-Mobile HD2 with MAGLDR v1.13, and I can load ICS up successfully. Calling works and my signal reads full with 3G (with Wind Mobile), but I can't activate the wifi (switching on results in nothing, as if the system attempts to but can't), and 3G appears to be inaccessible with Google Accounts/browser even though it is configured correctly. I've tried wiping, re-installing (with 1024 MB ext4 partition), and putting initrd.gz in an update folder for updating...nothing appears to be working. Can anyone help? Much thanks in advance.
Click to expand...
Click to collapse
mare.djurdjev said:
I got problems with touch screen.When i unlock my phone it acts like im still presing or scrolling,and its driving me crazy.When i type sms it presses button by itself,it scroll menu by itself.Even today,when i touch screen the screen get some purple colour,and when im not touching it its ok.Please help me
Click to expand...
Click to collapse
Please state which version of A2sd you are using, how it is installed and why you think it is a2sd related. Otherwise the main thread may be more appropriate for your questions.

I'll forward this over to the main thread then...I actually don't know what the A2sd version is. x.x

[Q] a2sd not working in miui.es

I have installed from a factory reset miui.es 2.2.3. I realized that the /cache partition was not used, so I did an a2sd cachepart. However, I got these errors:
Code:
...
[X] No a2sd.swap environment variable found.
[X] Problem detected: Darktremor Apps2SD may not have ran
during boot. Cannot read a2sd.mountpoint.
...
[ ] Moving /data/dalvik-cache to /cache/dc
[ ] Unmounting ...
BusyBox v1.19.3-cm7 bionic (2011-11-14 16:52 +0100) multi-call binary.
Usage: umount [OPTIONS] FILESYSTEM|DIRECTORY
Unmount file systems
-a Unmount all file systems
-r Try to remount devices as read-only if mount is busy
-l Lazy umount (detach filesystem)
-f Force umount (i.e., unreachable NFS server)
-d Free loop device if it has been used
[ ] Rebooting phone...
Anyway, the cache was copied to the /cache partition, but it was also left in the /data partition. I tried to remove it by hand, but after a reboot it is again there.
To sum up, MIUI seems to be ignoring a2sd. Anyone having this issue?

Debian install on top (with Android as chroot)

Hi everyone
I'm working on a long term project (as in, I'll work on it whenever I have time). I want to get Debian installed on the Nook Color natively with Android as a chroot (on top). Of course, I'm not an Android expert, so I'll be needing your guidance to do it. And, If you want, you can also join in and volunteer your Nook Color to torture experimentation.
I am following this guide by Kuisma (he was a user on these forums, but he told me he doesn't come here anymore, which sucks ):
http://whiteboard.ping.se/Android/Debian
So far, I'm done with:
1. Partition 32GB microSD card. Made a 4GB FAT32 storage partition, 25GB remaining ext3 partition for Debian. CHECK.
and
2. Create Debian root filesystem. Basically, use debootstrap to install to microSD (installed on ext3 partition). Installed openssh-server, tightvncserver, and lxde-core. Easy. CHECK.
and
3. Unpack initramfs. CHECK.
==================================================
All I have to do...is the complicated steps in between, lol.
Edit initramfs and init, unpack boot.img, note down the physical offset address, remake the boot.img..
==================================================
For now, my question is: how do I acquire the initramfs? (I'm on CM7.2 Mirage). Already got it. Unpacked it.
Now, I am in the process of modifying the init.encore.rc and possibly other files. After that's done, I'll repack the new initramfs, replace with the one in /boot, and see how it goes.

sagirfahmid3 said:
Hi everyone
I'm working on a long term project (as in, I'll work on it whenever I have time). I want to get Debian installed on the Nook Color natively with Android as a chroot (on top). Of course, I'm not an Android expert, so I'll be needing your guidance to do it. And, If you want, you can also join in and volunteer your Nook Color to torture experimentation.
I am following this guide by Kuisma (he was a user on these forums, but he told me he doesn't come here anymore, which sucks ):
http://whiteboard.ping.se/Android/Debian
So far, I'm done with:
1. Partition 32GB microSD card. Made a 4GB FAT32 storage partition, 25GB remaining ext3 partition for Debian. CHECK.
and
2. Create Debian root filesystem. Basically, use debootstrap to install to microSD (installed on ext3 partition). Installed openssh-server, tightvncserver, and lxde-core. Easy. CHECK.
==================================================
All I have to do...is the complicated steps in between, lol.
Edit initramfs and init, unpack boot.img, note down the physical offset address, remake the boot.img.
==================================================
For now, my question is: how do I acquire the initramfs? (I'm on CM7.2 Mirage).
Click to expand...
Click to collapse
It is uRamDisk in the boot partition. If you have CM7 on emmc then it mounts /system and /data on emmc. If you have installed CM7 on SD, the SD installer modified the uRamDisk to mount them on SD.
The Nook Color does not use boot.img. It uses a fat32 boot partition with files (of which uRamDisk is one).
Sent from my Nook HD+ running CM10.1 on emmc.

Excellent, thanks for the reply. I am running CM7.2 Mirage installed on emmc. Anyways, I looked inside the /boot folder which contains: MLO, charging.zip, romrestore.zip, u-boot.bin, uImage, uRamdisk, uRamdisk.bak, uRecImg, and uRecRam.
The MLO and u-boot.bin are used for a bootloader (second stage? cyanoboot?), and the uImage contains the kernel according to this. The uRecImg and uRecRam is for the recovery (CWM for example?).
So, I think that means I just need to mess with the uRamdisk and uImage files.
How would I go about from here? Creating/replacing a modified initramfs?
I'll try using the unmkbootimg script on them both and see if it does anything.

sagirfahmid3 said:
Excellent, thanks for the reply. I am running CM7.2 Mirage installed on emmc. Anyways, I looked inside the /boot folder which contains: MLO, charging.zip, romrestore.zip, u-boot.bin, uImage, uRamdisk, uRamdisk.bak, uRecImg, and uRecRam.
The MLO and u-boot.bin are used for a bootloader (second stage? cyanoboot?), and the uImage contains the kernel according to this. The uRecImg and uRecRam is for the recovery (CWM for example?).
So, I think that means I just need to mess with the uRamdisk and uImage files.
How would I go about from here? Creating/replacing a modified initramfs?
I'll try using the unmkbootimg script on them both and see if it does anything.
Click to expand...
Click to collapse
MLO is the x-loader and will not need to be changed. u-boot.bin is the bootloader and has been customized by the NookieDev team to include the cyanoboot menu. Source is available in the NC dev forum. It does not need a second stage bootloader since the first bootloader is unlocked. uImage is the linux kernel that has been all set up to match the hardware in the NC. It probably does not need to be modified. uRamDisk is the ramdisk that includes the initramfs. To edit that you first need to extract everything. Then when modified, recompile. The other files are as you guessed. I use linux to work on the ramdisk. First rename uRamDisk to ramdisk.org. Create a folder below that file and cd to it. Then use these three commands:
Code:
dd if=../ramdisk.org bs=64 skip=1 | gunzip -c | cpio -i
find . -regex "./.*"| cpio -ov -H newc | gzip -9c > ../ramdisk-repacked
mkimage -A ARM -T RAMDisk -n Image -d ../ramdisk-repacked ../ramdisk.modded
The first line extracts the contents of the ramdisk to the folder you are in. Then edit the contents as you see fit. init.encore.rc is the initramfs.
After editing, use the next two lines to recompile the ramdisk. Then rename the ramdisk.modded to uRamDisk and you are done.

Excellent! Thanks, it's extracted.
Now, the real fun begins
(College started so it might take some time to get it done, but yeah, I think it's possible to get Debian installed as the root OS).

If anyone is interested in the boot process of the Nook Color, here is a diagram:
{
"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"
}
If anyone is interested about the contents of the STOCK init.encore.rc from CM7.2 Mirage ROM, here's what it contains:
Code:
on early-init
start hwprops
on init
# setup global environment
export PHONE_STORAGE /mnt/emmc
export DSP_PATH /system/lib/dsp
export DEFAULT_BASEIMAGE /system/lib/dsp/baseimage.dof
# create mountpoints
mkdir /mnt/emmc 0000 system system
mkdir /mnt/usbdisk 0000 system system
symlink /mnt/emmc /emmc
symlink /mnt/usbdisk /usbdisk
# for encore
mkdir /rom 0777 root root
on fs
# mount partitions
mount vfat /dev/block/mmcblk0p2 /rom sync noatime nodiratime uid=1000,gid=1000,fmask=117,dmask=007
mount ext4 /dev/block/mmcblk0p5 /system wait ro barrier=1
mount ext4 /dev/block/mmcblk0p6 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p7 /cache wait noatime nosuid nodev barrier=1
on post-fs
# load kernel modules
#insmod /system/lib/modules/bridgedriver.ko
#insmod /system/lib/modules/dm-mod.ko
#insmod /system/lib/modules/dm-crypt.ko
#insmod /system/lib/modules/tun.ko
# change permissions for alsa nodes
symlink /dev/snd/pcmC0D0c /dev/pcmC0D0c
symlink /dev/snd/pcmC0D0p /dev/pcmC0D0p
symlink /dev/snd/controlC0 /dev/controlC0
symlink /dev/snd/timer /dev/timer
chown audio audio /dev/pcmC0D0c
chown audio audio /dev/pcmC0D0p
chown audio audio /dev/controlC0
chown audio audio /dev/timer
on boot
# wireless
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
chown dhcp dhcp /data/misc/dhcp
# bluetooth power up/down interface
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chmod 0660 /sys/class/rfkill/rfkill0/state
# bluetooth uart
chown bluetooth bluetooth /dev/ttyS1
setprop wifi.interface tiwlan0
setprop wlan.driver.status "ok"
# Temporary workaround for SOD
# Only needed for 2.6.29
#write /sys/power/wake_lock 1
# Enable Power Management - thanks NookieFroyo for this
# Mount Debug file system
mount debugfs /sys/kernel/debug /sys/kernel/debug
# Enabling sleep in idle path
write /sys/kernel/debug/pm_debug/sleep_while_idle 1
# Enabling Voltage OFF in idle path
write /sys/kernel/debug/pm_debug/voltage_off_while_idle 1
# Enabling OFF mode
write /sys/kernel/debug/pm_debug/enable_off_mode 1
# Enablig DVFS with ondemand governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
# Enabling SmartReflex for Zoom3 OMAP3630
write /sys/power/sr_vdd1_autocomp 1
write /sys/power/sr_vdd2_autocomp 1
# Permissions for setting the DSP Frequency
chown media root /sys/power/dsp_freq
# Permissions for DSP bridge device
chmod 0777 /dev/DspBridge
# Permissions for Overlay
chmod 0777 /dev/video1
chmod 0777 /dev/video2
chmod 0777 /dev/omap-resizer
chmod 0777 /dev/omap-previewer
# change permissions for overlay managers and display devices
chmod 0777 /sys/devices/platform/omapdss/manager0/name
chmod 0777 /sys/devices/platform/omapdss/manager1/name
chmod 0777 /sys/devices/platform/omapdss/display0/name
chmod 0777 /sys/devices/platform/omapdss/display0/enabled
chmod 0777 /sys/devices/platform/omapdss/display0/timings
chmod 0777 /sys/devices/platform/omapdss/overlay0/manager
chmod 0777 /sys/devices/platform/omapdss/overlay1/manager
chmod 0777 /sys/devices/platform/omapdss/overlay2/manager
chmod 0777 /sys/devices/platform/omapdss/overlay0/enabled
chmod 0777 /sys/devices/platform/omapdss/overlay1/enabled
chmod 0777 /sys/devices/platform/omapdss/overlay2/enabled
# SGX driver
chmod 0666 /dev/pvrsrvkm
#Set read_ahead buffers
write /sys/block/mmcblk0/bdi/read_ahead_kb 1024
write /sys/block/mmcblk1/bdi/read_ahead_kb 1024
# There's no back seek penalty on MMC
write /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/queue/iosched/back_seek_penalty 0
# Allow us to seek up to 1GB back
write /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/queue/iosched/back_seek_max 1048576
# Only pick one request from each queue at each round robin
write /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/queue/iosched/quantum 1
service hwprops /sbin/hwprops
critical
disabled
oneshot
# Initialize the SGX driver
service pvrsrvinit /system/bin/pvrsrvinit
user root
oneshot
# Start of SGX driver
service pvrsrv /system/bin/sh /system/bin/sgx/rc.pvr start
user root
oneshot
# Update the battery data heuristics every hour
service logbatterydata /system/bin/log_battery_data.sh
user root
group root
# OMAP specific services start here
service clearboot /system/bin/clear_bootcnt.sh
user root
group root
oneshot
# OMAP stuff:
# most of this is unused for the moment.
# load DSP firmwarevpl
service baseimage /system/bin/dspexec /system/lib/dsp/baseimage.dof
user root
group audio
oneshot
#service pppd_gprs /etc/init.gprs-pppd /dev/pts/1
# user root
# group radio cache inet misc
# disabled
#service fw3a /system/bin/fw3a_core
# user media
# group system camera
service uim /system/bin/uim-sysfs
user root
group media bluetooth
oneshot
service wlan_loader /system/bin/wlan_loader \
-f /system/etc/wifi/firmware.bin \
-i /system/etc/wifi/tiwlan.ini \
-e /rom/DevConf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /system/bin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /system/bin/wpa_supplicant \
-Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd_tiwlan0 /system/bin/dhcpcd -ABKL tiwlan0
disabled
oneshot
service iprenew_tiwlan0 /system/bin/dhcpcd -n
disabled
oneshot
I will contact Kuisma with my modified init.encore.rc (not posted here) and see if everything is alright, repack modified initramfs, replace it in the /boot partition, and let you guys know how it goes. If it works, awesomesauce, if it doesn't (and assuming it doesn't brick my Nook Color too hard) I will fix it and retry until I get it right.

[Q] /storage/sdcard0 not possible to delete

Hello
I installed CyanogenMod 11 (M12) on my Samsung Galaxy S4 i9505 and now I have a different folderstructure as on my former Samsung Galaxy S2 with CM 10.2.1
There is an empty folder
/storage/sdcard0
which I cannot delete. I would like to create a symlink from this sdcard0 to my real internal storage:
ln -s /storage/emulated/0 /storage/sdcard0
but this is not possible because I cannot delete this folder.
What can I do?
I think I need this symlink to get working some older paths from Backup-restores from my CM 10.2 SGS2.
Any ideas?
Thank you
frank

Just rm the sdcard0. You can create a init.d script to do it automatically at every boot
Code:
#!/system/bin/sh
# A simple script to symlink internal memory to /storage/sdcard0
#
rm -rf /storage/sdcard0
ln -s /storage/emulated/0 /storage/sdcard0
Save it as 99sdsym and put in /etc/init.d (apply 0755 permissions and ownership Owner 0:root/Group 2000:shell)
Otherwise, if you don't need init.d script, run this in Terminal Emulator:
Code:
su && rm -rf /storage/sdcard0 && ln -s /storage/emulated/0 /storage/sdcard0
Inviato dal mio GT-I9505

AntaresOne said:
Just rm the sdcard0. You can create a init.d script to do it automatically at every boot...
Click to expand...
Click to collapse
Thank you muchly!
This quite didnt work on my S4 because of r/o but a little change made it work:
Code:
#!/system/bin/sh
# A simple script to symlink internal memory to /storage/sdcard0
su
mount -o remount,rw /
rm -rf /storage/sdcard0
ln -s /storage/emulated/0 /storage/sdcard0
Now again my WhatsApp images are working again
Thanks again
But moment, if you this serious about Android OS, could you hint me as well in another, maybe related issue I have with TitaniumBackup Pro?
Cannot protect (lock) the backups anymore. Getting "Sorry, the operation failed".
Tried to move the Backup folder on external sdcard from internal, but both same.
Idea of it?
Thanks
EDIT: maybe it is like in the (rare) answer of Titanium "Support" mentioned that my internal and external sd-cards, just don't have the feature to set read-only flag.
I only wonder, why this did work on the older CM 10.2.1 SGS2 phone perfectly with the internal sd-card.

[Discussion/Guide]Dalvik-Cache filling internal memory, possible fix

I've been having problem with Honor 4x(kirin 620) internal memory randomly filling without me even using phone. I realized it was dalvik-cache that was filling memory. It was taking like ~700MB after a month use.
I'm using ksrt12 rom AEX v4.6 for Honor 4X. There is a lot of free space in other partitions like /cust /cache /system so I did some searching and found similar discussion with an older/other device about moving dalvik-cache to /system partition and creating symlink to /data. This way you could free some space and put that wasted space in other partitions in some good use without re-partitioning your device.
Make dalvik-cache to take storage space form /cust and /cache
1. Make script like this and put it in /etc/init.d
Give it permissions 700 (rwx-------)
Code:
#!/system/bin/sh
mount -o remount,rw /cust
# If folders don't exist, create them
[ -d /cust/arm64 ] || mkdir /cust/arm64
[ -d /cache/arm ] || mkdir /cache/arm
# Making sure that dalvik-cache in /data is empty
rm -r /data/dalvik-cache/{arm64,arm}
mkdir /data/dalvik-cache/{arm64,arm}
# Set permissions
chmod 711 /cust/arm64 /cache/arm
# The part that actually does something useful
mount --bind,rw /cust/arm64 /data/dalvik-cache/arm64
mount --bind,rw /cache/arm /data/dalvik-cache/arm
2. Reboot to recovery and wipe dalvik-cache, cache and cust.
3. Reboot to system
4. Done!
If you want to wipe dalvik-cache you must wipe /cache and /cust

-deleted

updated thread to a bit easier solution