Jump to content

Recommended Posts

Posted

i got it working once. I replaced my SD with a class6 and now i'm having the same problem, i.e. it find the ext partition but it cannot mount it. I'm starting to think this a2sd is more trouble than its worth...

Guest mike557
Posted
Can't get mount sd/ext to stick from modrecovery...run a2sd check: sd/ext found but not mounted..ext is ext2, 512MB, linux swap 14MB...can anyone help, please :)

First partition FAT32, as per guide>>

Are we supposed to be using a swap file especially if this is a class2 memory card?

Posted

you don't have to use a swap file, but when you execute 'a2sd check' if it doesn't find out it will tell you. Ofcourse its not helpful enough to then tell you whether this actually matters, usual developers code writing, they assume we are all inside their heads when they write their code.

Posted

ok, after a lot of testing here's what i found.

Executing the the a2sd zip from from clockworkmod recovery seems to do its thing, but then once you reboot Quick System Info shows A2SD storage as 'Information not available'.

I then go into adb and issue 'adb shell a2sd check', this tells me that the EXT is found but not mounted.

So I issue a 'adb shell mount /dev/block/mmcblk0p2 /system/sd' which mounts the EXT extension.

Another 'adb shell a2sd check' now shows all fine except 'No Apps2SD Flag File not found' (i know this is bad english but that's what it says) and suggest that I should execute the a2sd repair.

When I issue either the a2sd repair or the a2sd reinstall the last step of this process is a reboot.

So, my phone reboots, goes past the Orange logo and then gets stuck at the next logo (mine is the Modaco one off the r3).

At this stage the only way to repair is to go back in recovery mode and load the data partition from my backup.

It appears that on boot the EXT is not being mounted.

If anyone can shed any light on this i would be grateful because this thing is driving me up the wall.

Guest philmein
Posted
ok, after a lot of testing here's what i found.

Executing the the a2sd zip from from clockworkmod recovery seems to do its thing, but then once you reboot Quick System Info shows A2SD storage as 'Information not available'.

I then go into adb and issue 'adb shell a2sd check', this tells me that the EXT is found but not mounted.

So I issue a 'adb shell mount /dev/block/mmcblk0p2 /system/sd' which mounts the EXT extension.

Another 'adb shell a2sd check' now shows all fine except 'No Apps2SD Flag File not found' (i know this is bad english but that's what it says) and suggest that I should execute the a2sd repair.

When I issue either the a2sd repair or the a2sd reinstall the last step of this process is a reboot.

So, my phone reboots, goes past the Orange logo and then gets stuck at the next logo (mine is the Modaco one off the r3).

At this stage the only way to repair is to go back in recovery mode and load the data partition from my backup.

It appears that on boot the EXT is not being mounted.

If anyone can shed any light on this i would be grateful because this thing is driving me up the wall.

same issue here goes past the android logo but sticks on the modaco logo might have to wait for a new version

Posted (edited)

from my investigations, i'm not sure it is a version issue. I have tried v2.7.5.1 and v2.7.5.2 (and many other flavours in between). I have done extensive reading, on relevant forums, and I'm starting to think it a boot image issue. The boot image has to support this to enable it during boot-up.

I did get it to work once (see above) but i do a lot of ROM changes and I suspect something i did affected it, but i'm buggered if i know what.

Maybe some 'expert' on here can shed some further light on it.

EDIT: ok, found the problem. I was running MCRi r2 instead of r3. This was because (as reported on another thread) r3 broke my TaskManager so I reverted back.

The hint was in Paul's own changelog at (

http://android.modaco.com/content/zte-blad...oot-root-mcri/) reproduced below:

Changelog

r3

•Reverted 'Orange' logo to Android logo (from V880 dump)

•MCRi will now check for .gz.gz files on /sdcard and rename them appopriately (n00b friendly)

•MCRi will now run-parts from /system/etc/init.d if found (adding possibility of A2SD, CacheDalvikCache etc. etc.)

Funny enough reloading r3 did not break the TasKManger now and both a2sd and TaskManager are working fine.

Two problems remain for me:

1. The well documented android wifi disconnect on sleep.

2. The CPU high useage on reboots where i have to use my workaround of going into Camera, press Settings and then coming immediately back out, which bring my CPU down immediately to the usual 2-030percent.

Hope it helps others. :)

Edited by xzyk
Guest leetron1
Posted (edited)
from my investigations, i'm not sure it is a version issue. I have tried v2.7.5.1 and v2.7.5.2 (and many other flavours in between). I have done extensive reading, on relevant forums, and I'm starting to think it a boot image issue. The boot image has to support this to enable it during boot-up.

I did get it to work once (see above) but i do a lot of ROM changes and I suspect something i did affected it, but i'm buggered if i know what.

Maybe some 'expert' on here can shed some further light on it.

EDIT: ok, found the problem. I was running MCRi r2 instead of r3. This was because (as reported on another thread) r3 broke my TaskManager so I reverted back.

The hint was in Paul's own changelog at (

http://android.modaco.com/content/zte-blad...oot-root-mcri/) reproduced below:

Changelog

r3

•Reverted 'Orange' logo to Android logo (from V880 dump)

•MCRi will now check for .gz.gz files on /sdcard and rename them appopriately (n00b friendly)

•MCRi will now run-parts from /system/etc/init.d if found (adding possibility of A2SD, CacheDalvikCache etc. etc.)

Funny enough reloading r3 did not break the TasKManger now and both a2sd and TaskManager are working fine.

Two problems remain for me:

1. The well documented android wifi disconnect on sleep.

2. The CPU high useage on reboots where i have to use my workaround of going into Camera, press Settings and then coming immediately back out, which bring my CPU down immediately to the usual 2-030percent.

Hope it helps others. :)

Reapplied r3 root and reflashed r3 ROM task manager still busted and still no a2sd..tried everything i can think of..nevermind>>

EXT found but not mounted although mounted via recovery!! Oh well...

Edited by leetron1
Posted

got the same "not mounted" issue, but since I got hell a lot more storage space compares to pulse. I decided to give it a pass for now...

Posted

this is slightly ot but can someone just confirm for me what should sd cards be formatted to to work on the Sf? And what allocation unit size?

Guest StevenHarperUK
Posted (edited)
got the same "not mounted" issue, but since I got hell a lot more storage space compares to pulse. I decided to give it a pass for now...

I have it working but on reboot I have to go to the clockwork mod menu and remount the sd-ext. Then reboot. I then get a 20% chance of it working.

When it fails I am stuck at the MoDoCo splash and it goes black every 10 seconds.

Anyone else get this

Edited by StevenHarperUK
Guest JohnMetz
Posted
this is slightly ot but can someone just confirm for me what should sd cards be formatted to to work on the Sf? And what allocation unit size?

I followed others instructions to use the GParted live cd (you boot to it and it does not touch your existing PC installation). Gparted allows you to resize your existing FAT32 partition (smaller) thus leaving some space. I backed up my existing SD and used Gparted to shrink this partition by 512M. You then add a new ext2 partition on the space you just freed when shrinking the FAT32 partition. I also used the r3 kitchen and included the Apps2SD option and it all appears to work.

I am tempted to try the r4 version that just came out.

John

Posted

im actually just backing up the 2gb that comes with the SF so i can use a 4gb i had spare, and i was just using windows to format the 4gb to FAT and default allocation size. hope thats right?

Guest x.balli.x
Posted
I have it working but on reboot I have to go to the clockwork mod menu and remount the sd-ext. Then reboot. I then get a 20% chance of it working.

When it fails I am stuck at the MoDoCo splash and it goes black every 10 seconds.

Anyone else get this

yes am getting the same issue even if i try to install any theme / GalaS Framework....so fianlly i reflashed Sebastian's de-oranginated, cant be asked wid MCR

Posted

I have apps2sd up & running on my SF with Paul's r3 ROM. If I reflash with the r4 or Sebastian's ROM will that mess things up? I think Paul's r4 ROM already has apps2sd on it?

Guest StevenHarperUK
Posted
I have apps2sd up & running on my SF with Paul's r3 ROM. If I reflash with the r4 or Sebastian's ROM will that mess things up? I think Paul's r4 ROM already has apps2sd on it?

I think were ok, but if someone can confirm that it would be great.

Guest x.balli.x
Posted
I think were ok, but if someone can confirm that it would be great.

Had it working once on r3 but doesnt seem to work on r4

Guest Pakatus
Posted
I think were ok, but if someone can confirm that it would be great.

Seems not.

A2SD in terminal emulator...returns a big "Not found" to me.

  • 5 weeks later...
Posted

I have the same "not mounting" problem I am with modaco r4....all the partitions are set up correctly ...

Anyone ?

Thanks :rolleyes:

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.