Huawei U8220 (Non-Pulse)

[Guest BigBearMDC]

Lets make a new approach:

Throw A2SD out of the init.rc, let the device boot up and enter the PIN and then run "/system/bin/a2sd" through the shell / terminal emulator.

That should also work.

Greetings,

BigBear

Edited April 21, 2010 by BigBearMDC

[Guest Rizzly]

Lets make a new approach:

Throw A2SD out of the init.rc, let the device boot up and enter the PIN and then run "/system/bin/a2sd" through the shell / terminal emulator.

That should also work.

Greetings,

BigBear

Well, that was a good idea, but since the terminal emulator was moved in the process I couldn't see what happened (just that it didn't work). I tried with adb while android was loaded instead, but got these errors:

/system/bin/a2sd

--- Welcome to Android/CyanogenMod!

sysctl: /etc/sysctl.conf: No such file or directory

--- Checking ext filesystems

e2fsck 1.41.6 (30-May-2009)

/dev/block/mmcblk0p2 is mounted.  


WARNING!!!  Running e2fsck on a mounted filesystem may cause

SEVERE filesystem damage.


Do you really want to continue (y/n)? yes


/dev/block/mmcblk0p2 was not cleanly unmounted, check forced.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Entry 'lost+found' in / (2) has deleted/unused inode 11.  Clear? yes


Pass 3: Checking directory connectivity

/lost+found not found.  Create? yes


Pass 4: Checking reference counts

Pass 5: Checking group summary information

Free blocks count wrong for group #0 (7679, counted=7680).

Fix? yes


Free blocks count wrong (444309, counted=444310).

Fix? yes


Free inodes count wrong for group #0 (4028, counted=4029).

Fix? yes


Directories count wrong for group #0 (3, counted=2).

Fix? yes


Free inodes count wrong (250436, counted=250437).

Fix? yes



/dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p2: 43/250480 files (11.6% non-contiguous), 55992/500302 blocks

mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Device or resource busy

cp: cannot stat '/data/app/*': No such file or directory

cp: cannot stat '/data/app-private/*': No such file or directory

modprobe: chdir(2.6.27-perf): No such file or directory

/system/bin/a2sd: /system/bin/rzscontrol: not found

swapon: can't stat '/dev/block/ramzswap0': No such file or directory

+++ Apps-to-SD successfully enabled

I tried to restart the phone to see if worked despite all the errors, it didn't. I also tried to start it with adb when in recovery mode, it went like this (I tried with mount -a to get it to work):

/system/bin/a2sd

--- Welcome to Android/CyanogenMod!

sysctl: not found

[: not found

[: not found

[: not found

[: not found

modprobe: not found

/system/bin/a2sd: /system/bin/rzscontrol: not found

swapon: not found

setprop: not found

sync: not found

setprop: not found

/ # mount -a

/ # /system/bin/a2sd

--- Welcome to Android/CyanogenMod!

sysctl: not found

[: not found

[: not found

[: not found

[: not found

modprobe: not found

/system/bin/a2sd: /system/bin/rzscontrol: not found

swapon: not found

setprop: not found

sync: not found

setprop: not found

And interesting comparison might be to see how it works for someone with an ordinary pulse, perhaps it's just not startable this way ;)?

[Guest BigBearMDC]

Well, that was a good idea, but since the terminal emulator was moved in the process I couldn't see what happened (just that it didn't work). I tried with adb while android was loaded instead, but got these errors:

/system/bin/a2sd

[...]

+++ Apps-to-SD successfully enabled[/code]




I tried to restart the phone to see if worked despite all the errors, it didn't.



I also tried to start it with adb when in recovery mode, it went like this (I tried with mount -a to get it to work):



[code]/system/bin/a2sd

[...]

setprop: not found

And interesting comparison might be to see how it works for someone with an ordinary pulse, perhaps it's just not startable this way ;)?

I also tried this, getting the same errors.

We would have to unmount the SD-Card first for it to be working.

Greetings,

BigBear

[Guest Rizzly]

I also tried this, getting the same errors.

We would have to unmount the SD-Card first for it to be working.

Greetings,

BigBear

Hmm, weird, I tried with adb while the phone was running again, this time it had no troubles mounting /system/sd. When I checked everything was moved ok, and I made sure all /data/app-files were actually being read from the sdcard. It seems that when the phone is running, the homescreen/menu doesn't get refreshed (the apps where nowhere to be seen). So this problem is very persistent, I still have to load a2sd in some way during startup.

I figured since everything was on the sd-card and linked with /data/app you might only need to mount mmcblk0p2 to /system/sd, indeed that was the case. I tried restarting the phone and just mount everything, it worked like a charm. The problem with the apps not showing up was of course still there, since I did the mounting after the phone had been booted. With all this in mind I tired to make a script wich does this for me, I ended up just using these lines from the original a2sd-script in the new one (wich I named a2sdmnt):

#!/system/bin/sh

echo "--- Welcome to Android/CyanogenMod!";


sysctl -p


# mount and set perms

	busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd;

	busybox chown 1000:1000 /system/sd;

	busybox chmod 771 /system/sd;

I yet again restarted the phone, then I ran the script, indeed everything was mounted and reachable again (well, from adb, I still couldn't start the apps on the phone). Now to the daunting task of trying to load the script on startup, I edited the init.rc lines that originally loaded a2sd into this:

start a2sdmnt

# Start A2SD service


service a2sdmnt /system/bin/logwrapper /system/bin/sh /system/bin/a2sdmnt

	disabled

	oneshot

When I restarted the phone with the new boot image with this init.rc in it, nothing! I checked on the phone with adb, and mmcblk0p2 was not mounted to /system/sd. Again, am I screwing up somewhere doing something wrong, or does a2sd just refuse to work in the U8220?

[Guest andre.rigon]

hi folks,

I've just bought a huawei U8220 from CTBC, Brazil.

After 3 days, I've got "no space left" message.

After some search, I've found that I need to root my phone to use app2sd, or even install a custom ROM.

How can I do that? At least, root my phone to have space to install apps, since my SD card is not used?

Any help or suggestion would be great.

Thanks in advance.

André