yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] UltimoJedi:
Yes.

I had understood that it was because of the boot.img :)

Unfortunately I don't succeed in finding the correct base adress for my Legend (as already says also in the other thread) :mad:
[Legend Android Development] schpinn:
The ROM I'm using is a port of CyanogenMod, so no SenseUI on it. 4a does not seem to fix my problems, it even seems the problems got worse, since it can't even mount my ext3 partition. I've sent you an email with a logcat from my phone.
[Legend Android Development] tkirton:
This base address is very elusive on the Legend. I can't find any information on it.

Someone tried the Nexus One and the Hero base, but was unsuccessful. I noticed that the Magic is the same base as the Hero, so I started thinking maybe the Legend is the same base as the Tattoo (which I do have the base address for).

Try the Tattoo address and see if that works.

UPDATE: UltimoJedi was kind enough to tell me what the base address was on my Hero thread. It is now posted in the Rom Installation Guide.
[Legend Android Development] tkirton:
I was reading the logcat you sent. Thanks for sending the information regarding the /dev/block. I'm going to have to open up the boot image to see what's going on (since you mention there's a delay in most roms for the Legend).
[Legend Android Development] tkirton:
Bumped due to a Legend rom being included.
[Legend Android Development] tkirton:
Bump...new version released (2.7.5 RC2)
[Legend Android Development] tkirton:
Bump...new version 2.7.5 RC3
[Legend Android Development] maormark:
problem to include Darktremor Apps2SD in rom

I did everything listed, But no file is created named nowboot.img

0x12c00000 - HTC Legend

typed ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img #0x12c00000#

its say:

[ ] creating New Boot Image

./makeboot: line 4: ./scripts/mkbootimg: No such file or directory

Any idea what to do?.
[Legend Android Development] tkirton:
You are either missing the mkbootimg or you don't have the proper structure installed.

...or there's an error in the program.

If mkbootimg is in the same directory as makeboot, just take an editor (gvim) and edit the line that has mkbootimg. Just take out a slash and the word "scripts". Save and try again.
[Legend Android Development] maormark:
That's what I did based on the terminal:

To run a command as administrator (user "root"), use "sudo <command>".

See "man sudo_root" for details.

ubuntu@ubuntu:~$ cd ..

ubuntu@ubuntu:/home$ cd ..

ubuntu@ubuntu:/$ cd media

ubuntu@ubuntu:/media$ cd 2EF4A9CBF4A9961D

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D$ cd workspace

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd scripts

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk

[ ] Extracting Ramdisk from Boot Image

Page size: 2048 (0x00000800)

Kernel size: 2178840 (0x00213f18)

Ramdisk size: 166445 (0x00028a2d)

Second size: 0 (0x00000000)

Board name:

Command line: no_console_suspend=1 console=null

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

[ ] Uncompressing Ramdisk Image

536 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd scripts

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk

rm: cannot remove `../newramdisk.gz': No such file or directory

[ ] Creating Ramdisk Image newramdisk.gz

537 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000

[ ] Creating New Boot Image

./makeboot: line 4: ./scripts/mkbootimg: No such file or directory

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$

after i taked out the slash and the word "scripts" from the file makeboot

and tried again it's says:

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000

[ ] Creating New Boot Image

./makeboot: line 4: ./mkbootimg: No such file or directory

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$

Still not working.
[Legend Android Development] tkirton:
Do you have a mkbootimg in scripts directory? If so, is the permissions set correctly on it (I usually do a chmod 777 mkbootimg just to be sure).

Download the tools again: http://www.darktremor.info/files/tools/buildscripts.tar.gz and uncompress them in the scripts directory.
[Legend Android Development] maormark:
Same thing :(

To run a command as administrator (user "root"), use "sudo <command>".

See "man sudo_root" for details.

ubuntu@ubuntu:~$ cd ..

ubuntu@ubuntu:/home$ cd ..

ubuntu@ubuntu:/$ cd media

ubuntu@ubuntu:/media$ cd 2EF4A9CBF4A9961D

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D$ cd workspace

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd scripts

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk

[ ] Extracting Ramdisk from Boot Image

Page size: 2048 (0x00000800)

Kernel size: 2178840 (0x00213f18)

Ramdisk size: 166445 (0x00028a2d)

Second size: 0 (0x00000000)

Board name:

Command line: no_console_suspend=1 console=null

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

[ ] Uncompressing Ramdisk Image

536 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ cd ..

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd ramdisk

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/ramdisk$ cd ..

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd scripts

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk

./makeramdisk: line 2: cd: /ramdisk: No such file or directory

rm: cannot remove `../newramdisk.gz': No such file or directory

[ ] Creating Ramdisk Image newramdisk.gz

114 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000

[ ] Kernel File: ../boot.img-kernel

[ ] Ramdisk File: ../newramdisk.gz

[ ] Output File: ../newboot.img

[ ] Base Address: 0x12c00000

[ ] Erasing File: ../newboot.img

rm: cannot remove `../newboot.img': No such file or directory

[ ] Creating new boot image.

./makeboot: line 69: ./mkbootimg: No such file or directory

[ ] Setting Permissions: ../newboot.img

chmod: cannot access `../newboot.img': No such file or directory

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$
[Legend Android Development] tkirton:
You must have a permissions issue on mkbootimg.

Go into the scripts directory and type the following:

chmod 777 mkbootimg

Then try again.

I just tested this script again...same script you are using. Works perfectly on my system.
[Legend Android Development] maormark:
Unfortunately I still could not get it works, maybe it's too much to ask from you to make the ROM, but if you can here is the link:

http://rapidshare.com/files/4120489...ISR_2.05.461.52_signed_081010_083339.zip.html

The problem by terminal:

To run a command as administrator (user "root"), use "sudo <command>".

See "man sudo_root" for details.

ubuntu@ubuntu:~$ cd ..

ubuntu@ubuntu:/home$ cd ..

ubuntu@ubuntu:/$ cd media

ubuntu@ubuntu:/media$ cd 2EF4A9CBF4A9961D

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D$ cd workspace

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ chmod 755 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ chmod 777 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace$ cd scripts

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 *

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootimg

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootimg

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootfs

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootfs

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./getramdisk

[ ] Extracting Ramdisk from Boot Image

Page size: 2048 (0x00000800)

Kernel size: 2178840 (0x00213f18)

Ramdisk size: 166445 (0x00028a2d)

Second size: 0 (0x00000000)

Board name:

Command line: no_console_suspend=1 console=null

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

[ ] Uncompressing Ramdisk Image

536 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk

./makeramdisk: line 2: cd: /ramdisk: No such file or directory

rm: cannot remove `../newramdisk.gz': No such file or directory

[ ] Creating Ramdisk Image newramdisk.gz

114 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeramdisk

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 makeramdiskubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeramdisk

./makeramdisk: line 2: cd: /ramdisk: No such file or directory

[ ] Creating Ramdisk Image newramdisk.gz

114 blocks

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 makeboot

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 makeboot

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x12c00000

[ ] Kernel File: ../boot.img-kernel

[ ] Ramdisk File: ../newramdisk.gz

[ ] Output File: ../newboot.img

[ ] Base Address: 0x12c00000

[ ] Erasing File: ../newboot.img

rm: cannot remove `../newboot.img': No such file or directory

[ ] Creating new boot image.

./makeboot: line 69: ./mkbootimg: No such file or directory

[ ] Setting Permissions: ../newboot.img

chmod: cannot access `../newboot.img': No such file or directory

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$
[Legend Android Development] tkirton:
I'll see what I can do.

However, I did see where you ran the chmod 777 on makeboot. Try running that same command on mkbootimg (maybe I specified the wrong file).

chmod 777 mkbootimg

Then try again.

While you are doing that, I'll see about making the modifications in the boot.img for you.
[Legend Android Development] maormark:
I also tried it you can see rows 11,12:

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 777 mkbootimg

ubuntu@ubuntu:/media/2EF4A9CBF4A9961D/workspace/scripts$ chmod 755 mkbootimg
[Legend Android Development] tkirton:
Nevermind...I see that now. Sorry about that.
[Legend Android Development] maormark:
Do not want to hustle but if you have time so here is the boot.img file:

http://www.mediafire.com/?0w6592jh6u6agia

Thanks in advance
[Legend Android Development] tkirton:
Here's your image:

http://www.darktremor.info/temp/maormark-boot.img
[Legend Android Development] mercury700ir:
Hi...

I used the 0.9 kitchen tou cook a rom,

I cooked it and intalled it..

it works well BUT,

I have some doubt that A2SD+ is work or not??!!! >>>> so I check the adb\shell\ a2sd check, then it gave me this:

after it I tried to use : a2sd cachesd, then I got this:

I used a 8 GB class6 SD card, with 1 GB ext3, and 96 MB SWAP file

-----------------------------------------------------

Can anybody help me to find a solution for A2SD+ working??

----------------------------------------------------

I need thisssss....

Please help me as soon as possible... :((
[Legend Android Development] tkirton:
You're using 2.7.5 RC1...upgrade to 2.7.5 Final and see if that helps.
[Legend Android Development] dhanu007:
I always used to put rom in my sd card and just boot in recovery and flash zip from mem card...wht is this app2sd ? Can somebody plz link me how to do it in my HTC LEGEND? and is it advantageous than wht i am doin ?
[Legend Android Development] tkirton:
Apps2SD allows a user to execute applications from the Secure Digital card. Before Froyo, you could only store applications in internal storage. Even with Froyo (unless you have a program that you can choose where to install, have a program that can force apps to install on SD card, or have a rom like CyanogenMod that can force a program to be installed on the SD card) the application will automatically install in internal storage.

There are two different versions of Apps2SD:

The older method of Apps2SD (known as Apps2SD-EXT or Classic Apps2SD) uses a partition on your SD card formatted as an EXT2, EXT3 or (with some roms) EXT4 partition. This partition stores your applications. The internal storage location is redirected to this new partition.

The newer method of Apps2SD is available on Android 2.2 (Froyo). It is commonly referred to as Froyo Apps2SD. This moves your application (provided it is either force directed via a program or rom, or the program allows you to choose where to install it) to a secure section of your SD card. It uses the existing FAT32 partition (the same partition that your music and pictures are stored) to run your applications.

Even with Froyo, you can end up with applications on your internal storage. You can run Classic Apps2SD even in Froyo if you want full control of your apps (on an OS level)...and it is compatible with all versions of Android (so if you decide to use an Eclair Rom rather than a Froyo Rom, you can retain your programs when you downgrade...the Froyo Apps2SD only works with Froyo...Eclair doesn't understand the Froyo method and, therefore, your applications will be inaccessible).

Hope that helps.
[Legend Android Development] dhanu007:
thanks tkirton , but my problem is how to do it ?.. I cant find a proper method..atleast link me to some.I want to install mytouch legend rom on HTC but its only for app2sd . cant i use my normal method and just flash it ?
[Legend Android Development] maormark:
After I replaced the file that you created (the boot.img) I added these files to a folder system/bin :

a2sd, apps2sd.hlp, bash, busybox.a2sd, chka2sd, dtinstall, fixa2sd,

jita2sd, launcha2sd, starta2sd, sysinit, zipalign.

created a new zip file and tried to install it he writes:

Install from sdcard...

Finding update packege...

Opening update packege...

verifying update packege...

E:Wrong digest:

boot.img

E:Verification failed

Installation aborted.

What am I supposed to do?.
[Legend Android Development] tkirton:
Flash it like you would flash a new ROM. Nothing special with installation. Just make sure the rom you are using can support Apps2SD, otherwise the program won't start up during boot.
[Legend Android Development] tkirton:
I would erase the copy on the phone and retransmit it. Also, make sure the zip is signed.
[Legend Android Development] maormark:
How I do that?.
[Legend Android Development] Vuska:
Hi...

sorry for newbie question...

How to know about my App2sd version ?

(My Rom support app2sd but i dont know which version is)

Thank you
[Legend Android Development] tkirton:
New version of Darktremor Apps2sd (2.7.5.1) now available.
[Legend Android Development] tkirton:
Bump...new version released: 2.7.5.2
[Legend Android Development] mccard:
OK, so I have azure 1.0 installed and I have been using the 'manage applications' feature to transfer my apps to SD. Can anyone tell me if this method is better/ different?
[Legend Android Development] tkirton:
That's the Froyo Apps2SD, which puts the apps in a secure section of the FAT32 partition. Some people say it's better, other say it has issues. I've never really used it since I'm comfortable with my Darktremor Apps2D, which puts the apps in an EXT2, EXT3 or EXT4.
[Legend Android Development] cryshop:
Okay, this question may be quite noob but after running "a2sd install", my apps disappeared, I also did "a2sd repair" and It says everything run from SD Card, but the fact is I can't see any.

HTC Legend - Mytouch Legend ROM

Edit : flashed the newest version and everything works just fine now.
[Legend Android Development] alvinm93:
don't work on Htc Legend 2.1 , block at HTC White Screen (full Wipe, SD card partitioned)
[Legend Android Development] tkirton:
That's not what the post above yours say...

What rom are you using?
[Legend Android Development] cryshop:
Froyo Apps2SD : when I connect my phone to PC via USB cable and set my phone as Drive Disk, it pops up FC sometimes and some apps miss their icons.

Darktremor : when I connect my phone to PC via USB cable and set my phone as....anything (Disk Drive, Sync, Charge Only), my phone reboots quite alot. Don't know what's the problem.
[Legend Android Development] tkirton:
Have you tried wiping the dalvik-cache? Try that, which will force the phone to rebuild the dalvik-cache.
[Legend Android Development] dan168:
This might sound like a stupid question, but when you move the apps to SD, can you select which one you want to move, or does the command "/system/bin/a2sd reinstall" move ALL the apps you have installed to the SD card?

Also, if I want to move the apps back to the internal memory later, how does the program work if I have more apps than what the internal memory can hold...? E.g. if I have 200mb worth of apps on the SD card, and the internal memory only has say 100mb free...?

Thanks! :)
[Legend Android Development] tkirton:
This is Froyo Apps2SD. That works completely different from Darktremor Apps2SD.

a2sd reinstall moves all applications from /data/app and /data/app-private to the SD card.

If you try to transfer more than the internal storage can handle, you'll get a move error, where some of your files are in internal storage and some are on the SD card. You will lose access to the ones on the SD card until you tell Darktremor to use the SD card again.
[Legend Android Development] cryshop:
So, If i wipe dalvik-cache, what will happen to my phone, will I lost some data or settings?
[Legend Android Development] tkirton:
Nope. The dalvik-cache is a cache directory for the DalvikVM, the runtime Java interpreter. The cache information is parts of each of your programs to make them launch faster. Erasing this will cause the cache to be rebuilt.

Your settings for your programs are located at /data/data, which isn't affected by wiping dalvik cache.
[Legend Android Development] maxq1:
@ tkirton

remember me from the desire thread for the same topic? anyway, i was that legend-user guy (only realized i was posting under the dt-desire thread just a couple of weeks back. silly me. sorry 'bout that). i used to be on azure, then went with the nightlies. right now i'm on b62. from azure and nightly to nightly, i had to issue 'remove' & 'nocachesd' BEFORE flashing any kernels for the new kernel to boot/work. just over the weekend, i did 'nocachesd' and forgot about 'remove' prior to flashing b62 over b50. i was guessing that my gizmo will still boot since only the apps are affected; but..wala..stuck on the animated boot screen! did nandroid restore, issued 'remove' then flashed b62 and everything went good. tried wiping dalvik, but no dice there too, even on prior flashing that i did.

i'm concluding that, at least for my case, going from one rom to another, especially without wiping data, i need to restore first all apps and dalvik back to internal storage before flashing to another kernel. it's not a complicated process; cumbersome though. care to enlighten, my man?

also, any updates on the gui version? wifey's beginning to suspect i'm carrying out an online illicit affair via encrypted means on the terminal emulator. :rolleyes: geez...
[Legend Android Development] Sckank:
I used ROM-manager to create a partition of 512MB to use. I managed to get the apps backuped with Titatium over to the card and I managed to get LauncherPro installed but after I cant flash anything and I cannot install apps. Need some help. :-) Froyo BTW...

EDIT: Reinstalled and reflashed everything and it worked. :)
[Legend Android Development] tkirton:
No update on the GUI version. I'm still trying to find someone who can build the GUI, but it hasn't been a high priority (trying to get 2.7.5.3 done, but I have been slow at getting that done and tested).

I'll keep you informed. Also, I posts updates to my Facebook group:

http://www.facebook.com/home.php?sk=group_169478586398411&ap=1
[Legend Android Development] radu_radu:
Use choose install location from market. Need root, but works great
[Legend Android Development] hellpank:
B 0.1 Legen's Rom

Hi, A2sd not get work in this rom. The author says it supports. The partition is ext3. I need some helps. Because I flash and particioned few times.

C:\android-sdk-windows\tools>adb.exe shell a2sd check
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)

[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[ ] Starting Apps2SD Check Program.
[ ] Checking for ext partition
[X] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.

Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.

I don't see my partitions: 512MB ext3 128MB swap.

[ ] Partition Information:
Filesystem Size Used Available Use% Mounted on
tmpfs 146.1M 0 146.1M 0% /dev
tmpfs 146.1M 0 146.1M 0% /mnt/asec
/dev/block/mtdblock3 240.0M 234.5M 5.5M 98% /system
/dev/block/mtdblock5 185.1M 48.0M 137.1M 26% /data
/dev/block/mtdblock4 40.0M 1.3M 38.7M 3% /cache
/dev/block/vold/179:1
14.2G 2.5G 11.8G 17% /mnt/sdcard
/dev/block/vold/179:1
14.2G 2.5G 11.8G 17% /mnt/secure/asec

remaining sysinfo in the attached
[Legend Android Development] BesFen:
Work fine on my own ROM, Just follow the intruction in page 1.
[Legend Android Development] hellpank:
Thanks, but i want Froyo rom.
[Legend Android Development] BesFen:
Mine is froyo.

Someone already post voda froyo Rom with DT a2sd.
[Legend Android Development] whitetigerdk:
Go for my unofficial froyo rom.. it has a2sd working..
[Legend Android Development] Vanteks1:
Can't get A2SD working

anyone have some advice for me, I'm not sure if my rom supports A2SD. I believe it does because it has an A2SD section in the SD card settings. I have the original droid running MIUI with slayers 1GHZ kernel.

My 16GB sd card is formatted with a 512M ext3 partition, an 32M swap partition and the rest is fat32.

these are the results when I try to run A2SD

# a2sd

a2sd

[ ] Launching Darktremor A2SD

Starting Darktremor A2SD version 2.7 Update 3r1

[ ] Mounting /system as read-write

[*] Starting A2SD (Lite Version) in mode.

[ ] Searching for Mount Point...

[ ] Mount point found..no further action required.

[ ] Checking for ext partition

[ ] Ext partition found.

[ ] Checking Ext partition...

e2fsck 1.40.8 (13-Mar-2008)

/dev/block/mmcblk0p2: clean, 10/130560 files, 27008/522112 blocks

[ ] Mounting ext partitions...

mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument

[X] Mounting ext partition failed.

[X] Can't continue script...aborting.

[ ] Setting File System Ready property to 1.

[ ] Remounting /system to read-only.

# a2sd check

a2sd check

[ ] Launching Darktremor A2SD

Starting Darktremor A2SD version 2.7 Update 3r1

[ ] Mounting /system as read-write

[ ] Starting A2SD in check mode

[ ] Running A2SD Check Program.

[ ] Searching for Mount Point...

[*] Mount point /system/sd located.

[ ] Checking for ext partition

[X] Ext partition found, but not mounted.

Your rom may not be setup to run A2SD.

Check with your rom developer if the boot image

is programmed to run A2SD.

[ ] Setting File System Ready property to 1.

[ ] Remounting /system to read-only.
[Legend Android Development] Vanteks1:
Anyone?
[Legend Android Development] spicyjoe:
Hi, when i enter the code to reinstall apps into my sd card, it gives me an error saying sd card not mounted.... :S
[Legend Android Development] tkirton:
bump---new version available.
[Legend Android Development] tkirton:
There's been a couple of new versions of the software since then, but I see this from time to time. What rom are you using and does it support running scripts on boot (easiest way to tell is if it says it is A2SD+ or any other Apps2SD compatible except Froyo or Gingerbread native Apps2SD).