Database Develop

SD card stuck in read only HELP!!!

Computer sees the card, Astro sees the card. Phone acts like it's not there.
Please help. I cannot figure out how to fix this.
Thanks James

I am having a similar problem but when I plug the microsdcard in my computer through the sdcard adapter or in my tmo dash it works just fine. I did a nandroid backup and after that my card was read only. trying changing the attributes in terminal and adb but neither worked and I will admit that im very new to linux stuff so im trying to read as much as i can to figure it out but its not easy.

Hey since no one else replied I decided to try a few things out. I formatted my sdcard in my vista computer and now the phone recognizes it. Not sure what caused that. I was about to reflash jf 1.41 to see if that fixed it but not necessary now. I'm gonna try backing up my phone again with nandroid to see if it duplicates. Seems to e ok even after backup. so now I have no idea what caused it. only other thing i was doing was pushing a new theme to my card through adb but it only pushed the filename. 0 bytes of data. I've looked up a ton of stuff to try to find out what I did wrong. from now on I think I will just use my spare card to update anything on the phone.
btw, card i was having problem with was a sandisk 8gb micro sdhc class 2. For the time being im only going to use this card for backup purposes as I also have a class 6 8gb card. hope this info helps.

Using a Class 6 8GB card here as well and same thing. I may wipe the card as well, but I was hoping iI could find some info as to what caused this... My card is stuck in read only mode too.. sucks.

in Terminal type
mount<enter>
you will get a list of what is mounted, and any attributes ( rw , ro etc etc )
to save typing it all out here, do Menu --> email To...
you now have an email draft, which is nice and pasteable

Here it is:
Code:
$ mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (rw)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p1 on /sdcard type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8)

ok , its defiantly read only,
why? I have no idea
in terminal do
cat /etc/fstab
have a look at the sdcard line, suspect it reads :
Code:
/dev/block/mmcblk0p1 /sdcard vfat ro
if it does you can fix it with
Code:
su
mount -o rw,remount /system
vi /etc/fstab
ok, vi isn't all that friendly, so here is a quick guide
use the trackball to scroll down to the sdcard line
now press Shift + a
now delete, and type w ( we are telling it to mount read write instead of read only )
press Trackball+1 ( emulates Esc on Desktop )
now shift+z, shift+z ( yeap twice) this saves the changes
your fstab line should now read
Code:
/dev/block/mmcblk0p1 /sdcard vfat rw
this should resolve the ro issue next time sdcard is mount
unmount sdcard in settings, remove card, and reinsert
Code:
mount
fingers crossed, sdcard is rw
nearly forgot, you will probably want to put system back as read only, replace rw.remount with ro,remount

Code:
$ su
# cat /etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/system/modules/modules.cramfs /system/modules cramfs ro,loop
/system/xbin/xbin.cramfs/system/xbin cramfs ro,loop
#
fstab has it as rw.
When I first boot up and do a mount, it's rw. If I immediately go into ASTRO and try to remove any files or directories it crashes. Then, if I go and round mount again it gives me the same result as before. ro.

well, you have me stumped
have you tried reinstalling astro?
do you have the same issue with linda?
in the meantime I'll sleep on it, 03:39 here

Firerat said:
well, you have me stumped
have you tried reinstalling astro?
do you have the same issue with linda?
in the meantime I'll sleep on it, 03:39 here
Click to expand...
Click to collapse
I haven't tried linda. I have just noticed that I get a "this software is BETA" message in Astro now.
The root of all this is that I removed a bunch of pictures through ASTRO last week and I've had broken thumbnails ever since in all applications that browse for pictures... photoslide, wallpaper, Pictures, etc... I've been trying to remove the .thumbnail directory since friday, but I keep getting this damn "Read-only filesystem" error and it's starting to really tick me off. Times like this when I get kind of annoyed at some of the half-assedness of some of the android apps.

I was going to just re-format the sdcard but went ahead an ran a chkdsk from Windows beforehand... came up with a ton of errors. I did chkdsk /f and it fixed them all and now everything is working fin. I really think ASTRO screwed something up when it deleted all the files.. anyone else have this happen or was it just a freak occurance?

tbh I doubt Astro would have managed to screw it,
anyway glad everything is good now

But that was when everything started. I deleted about 40 images in astro then the next day I went to look through my photos and I had a ton of broken thumbnails so I tried to use astro to remove the .thumbnails and albumthumbs directors and it would either say the system was read only or it would would just force close. All of the file errors were on the images that I deleted. (there were all 0k files)

I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.

KNK said:
I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.
Click to expand...
Click to collapse
its something with astro, i was backin up my apps yesterday and the exact same thing started happening to me so i just moved everything off my sd card to a folder on my computer and formated my sd card. it worked and i deleted astro its about to expire anyway

I just updated my ASTRO last night to the latest beta so it wasn't going to expire till 5/15 but I have removed it as it has completely corrupted the partition map of the SDCARD ... kinda funny I don't have it even partitioned it's just all FAT32.
Thanks ASTRO!

KNK said:
I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.
Click to expand...
Click to collapse
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere

Firerat said:
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere
Click to expand...
Click to collapse
I'm not sure what happened or even if it was related to Astro but yesturday for an unknown reason I phone was acting very strange.
Example:
The first occurance was when I opened Telenav to get me the directions back home (from hanging out with my gf) and the app said that I still needed to reactivate GPS. (Oh yeah... that's right... I deactivated it to save battery life. DUH!) After doing so the app crashed. I tried starting it up again and it would pop up for a second and the go back to my home screen (Open Home). So I did a reboot.
After my phone started back up all hell broke loose. About 12 of my apps popped up with Force Close!
Realizing the inevitable, I decided to use MyBackup to backup my settings (sms, caller log) and it gave me an unable to access DB or something like that.
I don't think that it was Astro but I can't figure out what could have caused this.
I spent about 3 hours last night reinstalling all of my apps from Market because even though they are all saved to the ext2 on the SD (Thank God!) it still says FREE in market the apps that I have installed. (BTW... anyone know a fix?)
So it wasn't my SD card, I didn't do anything new at all. No installed apps, no themes, no updates, nothing. I guess it was a ghost in the machine.
Any clues?

Firerat said:
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere
Click to expand...
Click to collapse
I did two things ... just to test it out. Cleared thumbnails ends up the same result corrupted partition(RO) then deleted a file from the SDCARD and once again it did the same thing.
I tried this with Linda File Manager and it is working fine no change to the SDCARD & I was able to do everything with it that I was able to do with ASTRO just about.
ASTRO is either locking the SDCARD to do it's deletes and not unlocking it after it's done or something is just not being done right that is ends up corrupting the card.

I had the same problem with the Discover app. I'd move images and music over wifi from my computer and then they wouldn't show up in the music/pictures app. Other apps would see them.. I was able to just delete them normally and then copy them over via USB and it worked fine. Seems some apps, when they write, bork up the permissions.

Weird memory readings..need explaining

Hi i noticed that i only have 28MB of ROM left. Installed apps ~90. I mean ok i have 16 games but it's small ones no 3D.
AppManager says 28M free of 196?! what's up with that. I though we have 512MB. To be sure i opened up shell and did a top and df -h. Here are the outputs. What the hell is going on there?
Filesystem______________Size______Used___Available__Use% Mounted on
tmpfs__________________192.9M____0_____192.9M___0% /dev
tmpfs__________________4.0M______0______4.0M____0% /sqlite_stmt_journals
/dev/block/mtdblock3_____145.0M___121.3M___23.7M___84% /system
/dev/block/mtdblock5_____196.3M___167.3M___28.9M___85% /data
/dev/block/mtdblock4_____95.0M_____78.2M___16.8M___82% /cache
tmpfs__________________8.0M______7.0M____1.0M____87% /app-cache
/dev/block//vold/179:1
RAM is also not shoing up as 512...although the device is rooted
and TOP:
Mem: 377904K used, 17136K free, 0K shrd, 8K buff, 42416K cached
CPU: 7.1% usr 21.4% sys 0.0% nic 71.4% idle 0.0% io 0.0% irq 0.0% sirq

after reading a different thread i found that different system compoents eat the rest of the ROM so we are left with ~200MB.
but what is mpfs__________________192.9M____0_____192.9M___0% /dev
Why is this not used at all?

There is no fix for the 196MB /data partition limitation yet. Your only option is to use apps2sd (after rooting). I have it set to 768MB on my SD card

thanks for the reply.. but still if i use apps2sd i won't be able to chose where to install an app.. right?

actually there is an option in the newest CM that allows you to turn on and off Install to SD so yes you can choose.

qiuness said:
thanks for the reply.. but still if i use apps2sd i won't be able to chose where to install an app.. right?
Click to expand...
Click to collapse
Its either /data or /sd-ext/data. CM adds this to the settings activity.
If you do decide to move to the other option, use titanium backup to backup to SD, then restore. It will automatically go to either /data or /sd-ext/data
Private data for apps is still stored in /data, but apps2sd does help in slowing down the filling of /data

thanks.. It's clear now.. sadly i`m not usin CM ROM since it has no smart dialing and some other stuff i cannot live without so i`m using the desire rom..
With the DESIRE being released momentarily i`m hope we get a cleaner/bugfree ROM.
Also i`m not sure what google is waiting for releasing a new ROM for the N1

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Tattoo] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Reserved...created because a Tattoo rom has it as part of its build.

I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?

I love this script. I think I'm going to be using it in the next version of my ROM. Thanks for making it, it's great

It shouldn't do that.
Try the RC3 (about to release it): http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-signed.zip
If that doesn't work, let me know and we go from there. There's a recovery log file that is created...I just have to remember where it is at (was looking at it just this morning).
dancer_69 said:
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
Click to expand...
Click to collapse

alredy running rc3 in our rom hehe

Which rom is that?
danne_jo said:
alredy running rc3 in our rom hehe
Click to expand...
Click to collapse

PuzzleROM
Sent from my Tattoo using XDA App

tkirton said:
Which rom is that?
Click to expand...
Click to collapse
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10

I saw that during my sweeps of the forums...added into my list.
danne_jo said:
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
Click to expand...
Click to collapse

i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] 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.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?

pardol said:
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] 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.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
Click to expand...
Click to collapse
Stock ROM doesn't support A2SD as it has no means to execute the script.
Try HCDR.ROM or PuzzleROM

Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App

pardol said:
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?

actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard

It doesn't work with Stock roms because there's no command in init.rc to launch Apps2SD (which is part of the boot.img). Now, you can modify the boot.img (or get an already modified boot.img) to add support. It will retain the stock rom feel but has a modified boot image.
pardol said:
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
Click to expand...
Click to collapse

That is because the EXT partition isn't mounted, so Linux (the OS behind Android) doesn't see an EXT partition on the SD card (needs a mount command to be executed, which Apps2SD does, but the rom doesn't launch the program).
pardol said:
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
Click to expand...
Click to collapse

i have the same problem and in order to run A2SD i have to mount the EXT3 Partition manually ; anyone knows how to auto mount the ext3 partition at system startup ?!!

ok. i have been able to install a2sd correctly and have it running since a ferw weeks now. The only flipside is i need a PC to be able to reboot the phone since the Ext3 partition does not start.
Is there a command i can put in the init.rc file to autorun a2sd in place of doing a
adb shell a2sd
every time i reboot the phone ?

Hi, how about if after start up , manually mount the ext3 partition and manually run apps2sd app ? As I rarely reboot the system so I think this can be an alternative solution. but could someone let me know the command ? thx

Installing tremers Froyo on ext2 partition

I found tutorial how to use ext2 partition on SDCARD for haret.
http://android-devs.org/forum/viewtopic.php?f=56&t=194
I created this
2 GB Fat32
1 GB ext2
1 GB ext2
so i have 4 GB disk and 3 partition just as its on tutorial
But after launching haret it should asked me
Press VolDn to launch Installer (to use ext2)
just after the
Checking for partitions
but in my case it just continue with installing without asking me and its uning only fat32
Any suggestion???

our rootfs doesn't have the install function, someone must edit the rootfs to boot into EXT partitions first!

I just copy rootfs to the / of the ext2 and system to /system, and then edit the init script so it remounts properly.
When I start doing partitioned releases I'll try and make it easy, probably by distributing prebuilt images by card size (4G, 8G etc.)

Tremere said:
When I start doing partitioned releases I'll try and make it easy, probably by distributing prebuilt images by card size (4G, 8G etc.)
Click to expand...
Click to collapse
I talked to phh yesterday.. he said ext2 and NAND booting have no effect on stability, performance and battery life. (rhod nand booting has been working for one month)
Performance could change but it would be less than 20%.
So I pray that someone will find the standby killer

So i need only one ext2 partition
Tremere said:
and then edit the init script so it remounts properly.
Click to expand...
Click to collapse
if i knew how and what to edit. Nevermind its not that important. You just focus on your work.

Matzemink said:
I talked to phh yesterday.. he said ext2 and NAND booting have no effect on stability, performance and battery life. (rhod nand booting has been working for one month)
Performance could change but it would be less than 20%.
So I pray that someone will find the standby killer
Click to expand...
Click to collapse
True. I think they also had an incorrect mount option on the rootfs until recently that slowed loopback performance. I think my last (unstable) release contained the fix for that.
For my own AOSP device tree I'm determined to start fresh without the rootfs and loopback crap. Maybe not a big performance gain but easier to 'get around' system wise.
if i knew how and what to edit. Nevermind its not that important. You just focus on your work.
Click to expand...
Click to collapse
off the top of my head, init.etc/init.froyo.rc and there is a line which tries to mount root as yaffs (flash). Not too hard to find.
You might want to have another ext2 for /data though.

How do I partition my micro sd card?
please excuse my bad English
I use translator

The easyest way for me. Download a release of Ubuntu from ubuntu.com and burn it to cd or make bootable USB. Boot live cd and partition from there.

wouldn't it be easier to download a live CD of gparted?

Jonny4911 said:
wouldn't it be easier to download a live CD of gparted?
Click to expand...
Click to collapse
System Rescue CD is my favorite for partitioning tasks. Should work on your sdcard.
Over in the raph forum, e334 posted a guide on partitioning ext2 from Windows

32gb - how much is usable for storage?

I have a S2 16gb with 11.5gb usable "usb internal storage". Will Htc One have at least 28gb?

bubu_bubu said:
I have a S2 16gb with 11.5gb usable "usb internal storage". Will Htc One have at least 28gb?
Click to expand...
Click to collapse
It's about 26GB.

Jesus 6gb used?

bubu_bubu said:
Jesus 6gb used?
Click to expand...
Click to collapse
Indeed this has been confirmed. Bearing in mind if you install a custom Rom you can probs decrease this amount.
Sent from my Incredible S using Tapatalk 2

It is fine in my opinion. Most of the apps you install goes into that occupied 6 gigs anyway

I would get the 64gb version but I don't think the carriers in my country will have it

Dharkan said:
It is fine in my opinion. Most of the apps you install goes into that occupied 6 gigs anyway
Click to expand...
Click to collapse
No, storage is unified: apps go in the 26. (I think).

Oh if that's the case it really don't make much sense. I mean what would they use 6 gigs for, I don't believe smartphones are getting that big updates.

26.1gb is free to be precise lol and 1.5gb RAM

Dharkan said:
It is fine in my opinion. Most of the apps you install goes into that occupied 6 gigs anyway
Click to expand...
Click to collapse
source of your information?
If it has 2 partitions and one acts like the onboard (6gigs), and the other one (26) acts like a sd or whatever it would be ok ..
otherwise it's just like with the surface tablets .. well not quite as bad, but still a bit silly^^

If im correct on my HTC One X which was 32GB, i only had 22GB free after jelly bean update and 6GB or so for apps..
so the apps and sd storage is split

Shasarak said:
No, storage is unified: apps go in the 26. (I think).
Click to expand...
Click to collapse
Wrong
Got this from the stock recovery posted here on dev section when I extracted it.
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/sda1 /dev/block/sda
/system ext4 system
/devlog ext4 devlog
/reserve vfat reserve
Shows that /data(userdata) partition where apps get's installed has a seperation partition that needs to be mounted. So nope it's not unified.
and yeah for the developers who plan on extracting kernels/recovery of HTC One here are the info you need.
Code:
BOARD_KERNEL_CMDLINE is "console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31"
BOARD_KERNEL_BASE is "0x80600000"
BOARD_PAGE_SIZE is "2048"

26 gigs is more than enough for me, I take up 5 to 6 on music alone and the rest on pictures and videos taken on phone, not much is taken with apps downloaded at the most 1gb so I'm quite comfortable with the amount of space on the phone although it would be awesome to have 28 or 29gb free
P.s. I do listen to all that music that takes up 5 to 6gb of space on my current phone in case some of you are wondering whether I listen to most of it wasting space on all that music
Sent from my HTC One S

I think it would be possible to repartition the /system partition to reduce it's size and merge it with the sdcard partition. Depends on the partition table. But if it's not possible I think we could also split the system partition and make a sd-ext there instead. But of course that's very dangerous and is not recommended on average users.

Riyal said:
Wrong
Got this from the stock recovery posted here on dev section when I extracted it.
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/sda1 /dev/block/sda
/system ext4 system
/devlog ext4 devlog
/reserve vfat reserve
Shows that /data(userdata) partition where apps get's installed has a seperation partition that needs to be mounted. So nope it's not unified.
and yeah for the developers who plan on extracting kernels/recovery of HTC One here are the info you need.
Code:
BOARD_KERNEL_CMDLINE is "console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31"
BOARD_KERNEL_BASE is "0x80600000"
BOARD_PAGE_SIZE is "2048"
Click to expand...
Click to collapse
I stand corrected.
Though, also a little surprised. Weren't HTC's flagship phones last year unified? That seems a retrograde step.

Shasarak said:
No, storage is unified: apps go in the 26. (I think).
Click to expand...
Click to collapse
In HOX the memory WAS NOT unified.
Anybody knows how many storage is free for apps?
P.D. Sorry, I reply to the post before full read the thread. Cancelling my reservation.

JmJ17 said:
In HOX the memory WAS NOT unified.
Anybody knows how many storage is free for apps?
P.D. Sorry, I reply to the post before full read the thread. Cancelling my reservation.
Click to expand...
Click to collapse
Wild guess is 2GB.
2GB data partition
12mb devlog
17mb kernel
17mb recovery
120mb cache
rest is system partition

On my one x i had around 11 usable, and i still have 2 gb free. so if i get the one , ill have around 17 gb of free space holy moly .. what can i do with so much free space, can i rent it out?

jags_the1 said:
On my one x i had around 11 usable, and i still have 2 gb free. so if i get the one , ill have around 17 gb of free space holy moly .. what can i do with so much free space, can i rent it out?
Click to expand...
Click to collapse
give it to me I need more extra space.

That's awful. Why did they go back from the awesome unified space in the HOX+. Thats was so great. If you had free space you could install apps. If the One really has an apps partition again, I'm going to have to move apps to sd-card again the whole time
Why did they make a step backwards?