ROM Developers: Please switch to ext3 for a2sd!

Search This thread
By:
Advanced…
DOHCtor

DOHCtor

Senior Member
Apr 10, 2009
1,109
121
Southern California
LucidREM said:
did you try my boot.img? it's based off the US build .. not sure if the boot.img matters
Click to expand...
Click to collapse
Is your modified u.s. boot.img compatible with the adp rom?
cyanogen said:
I think you're the first person to call it "bloated" :confused:
Click to expand...
Click to collapse

I'm just bad at wording it. It's definitely not bloated. It just doesn't fit my needs. I just want a basic rom that is rooted, can do a2sd, and with no extra apps. If I wanted the extra apps, I would push them into the rom myself. But now I need a boot.img to support ext3 and safely unmounts it when shutting down.

This doesn't mean I don't appreciate your hard work.

edit: I just flashed Unitas boot.img that was based off the US rom and it works on the ADP as well. #mount shows that it's mounted as ext3 with noatime.
 
Last edited:
You must log in or register to reply here.

Similar threads

cyanogen
[ROM][BBQ] CyanogenMod-6.1 for Dream & Magic :: V6.1.0 (12/05/2010)
Replies
5K
Views
2M
A
alpha-tester
bbuchacher
[ROM]Super D 1.11 "Rehab is for Quitters" (4/28)
Replies
8K
Views
2M
M
Michigan Jason
cyanogen
  • Locked
[ROM] CyanogenMod - This is Bat Country! (EXPERIMENTAL) [9/18 - v4.1.11.1]
Replies
8K
Views
2M
Mikey
Mikey
cyanogen
[ROM] CyanogenMod - No, you can't have a pony (STABLE) [UPDATED 03/04 - v4.2.15.1]
Replies
14K
Views
4M
BookCase
BookCase
K
How-to- Root, Hack, and Flashing your G1/Dream Read first!!
Replies
2K
Views
3M
LucidREM
LucidREM

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    cyanogen
    cyanogen
    99% of the problems users are having with Apps2SD are caused by the unclean shutdown of the ext2 filesystem, because Android does not unmount it when rebooting or shutting down the system, and there are no tools on the device to fsck the filesystem on boot. Ext3 is journaled and this isn't an issue because the journal will simply replay on boot.

    I'd like to put an end to this.

    Attached is e2fsprogs (tune2fs, e2fsck, resize2fs, and mke2fs) built for Android/ARM. You should also use the "-t auto" mount option so that it's still backwards compatible with ext2.

    To convert your ext2 to ext3, you can simply run "tune2fs -j /dev/block/mmcblk0p2" after you have these tools on your device, and reboot (assuming your ramdisk allows for mounting as "auto"). You should unmount and e2fsck the partition first, if it's not been checked for errors.

    Step by step by neoobs
    View
    1
    N
    neoobs
    Directions for what I did:

    1. unzip e2fsprogs
    2. type
    Code: 
    adb remount
    3. Download lucids script (search it)
    4. type
    Code: 
    adb shell
    5. type
    Code: 
    adb push e2fsprogs/system /system
    6. type
    Code: 
    lucid rem
    7. reboot into recovery
    8. type
    Code: 
    adb shell
    9. type
    Code: 
    mount system
    10. type
    Code: 
    e2fsck /dev/block/mmcblk0p2
    11. type
    Code: 
    tune2fs -j /dev/block/mmcblk0p2
    42. type
    Code: 
    reboot

    All done
    View
    1
    jaygajay
    jaygajay
    Henchman said:
    Do I do this BEFORE trying to install the Hero Rosie rom?
    Click to expand...
    Click to collapse

    Do it after so that when you flash the Hero ROM it won't overwrite the boot.img if you had flashed it before the ROM

    Kinslayer81 said:
    You need to do a 'busybox mount' instead of plain mount, because the built in mount command doesn't support the 'auto' type. Even if you're stuck at the boot you can run this command via adb shell and you'll see the phone will finish booting (once dalvik-cache becomes available again).
    Click to expand...
    Click to collapse

    Wow. Okay I will repack another boot.img with 'busybox mount' and post results later after work.

    DOHCtor said:
    It does makes sense but my phone was already able to use the ext3 partition without the modded boot.img. So it was pointless for me to flash that boot image?

    So what I think you're saying is that I didn't have to do anything since my phone had a fresh rom install, fresh ext3 partitioned sd card, and everything was mounted already? (I'm using symlinks to run my apps and dalvik-cache on sd).
    Click to expand...
    Click to collapse

    The phone has ext3 built in but some ROMs explicitly mount with an '-t ext2' command. So even if you formatted your card to ext3 and android supports it, it is still using ext2. Unless the ROM you are using already had the '-t auto' command in the boot.img. Type 'mount' in treminal or 'adb shell mount' from your computer and see what filesystem your /system/sd partitioin is using.
    View

New posts