Help Memory card "Read Only" error after sd-ext in mildwild oxygen v4.9

[1gouravgg]

I Recently installed a custom ROM "Mildwild based on Oxygen v4.9" to get rid of the annoying "Low memory" error. after installing i booted into 4ext recovery and parted sd-ext (1.5GB). After this i installed mounts2sd to move all application data and dalvik cache to sd-ext.

whole process went smoothly but now i see a new strange error of "memory card is not mounted or available".
i just see the contents of memory card through file manager but cant copy,delete any file.
any idea,whats going'on?

 

[nicka3200]

You don't need mount2sd. It's probably that causing problems. Mild wild has the necessary scripts per loaded.

Factory reset then restore your apps again using titanium back up.

Titanium will also tell you if your ext partition is working.

 

[1gouravgg]

You don't need mount2sd. It's probably that causing problems. Mild wild has the necessary scripts per loaded.

I moved all apps data to sdext,
but there is no other way bcuz htc desire has only 255MB internal memory and after installing several apps it shows "low memory error" due to apps data in phone memory.
any other safe way to free up phone memory by moving apps data?

 

[Hadron]

But as Nicka says, MildWild ROMs have the a2sd scripts included, so adding a second a2sd solution in addition is not a good idea -2 modules trying to do the same thing risks conflicts. The built in one will move apks and dalvik cache without you adding anything.

If you really want to use the other one, you should edit the ROM before flashing to remove the built-in a2sd (/system/etc/init.d/10apps2sd). But I would recommend trying the built-in one first. I've seen a number of people here try data2sd solutions (moving app data to ext as well as app and dalvik), but most gave up on them fairly quickly, so I'd avoid that if at all possible. With the built in a2sd you should not hit problems after installing "several apps" - I've installed > 130 apps with ROMs like that with no problem. If you are S-Off you can use a custom hboot with MildWild to increase your actual data space, with the built-in a2sd script in addition, which unless you have some app that's using a pathological amount of data should be sufficient for most people.

 

[1gouravgg]

You don't need mount2sd. It's probably that causing problems. Mild wild has the necessary scripts per loaded.

Factory reset then restore your apps again using titanium back up.

Titanium will also tell you if your ext partition is working.

But as Nicka says, MildWild ROMs have the a2sd scripts included, so adding a second a2sd solution in addition is not a good idea -2 modules trying to do the same thing risks conflicts. The built in one will move apks and dalvik cache without you adding anything.

If you really want to use the other one, you should edit the ROM before flashing to remove the built-in a2sd (/system/etc/init.d/10apps2sd). But I would recommend trying the built-in one first. I've seen a number of people here try data2sd solutions (moving app data to ext as well as app and dalvik), but most gave up on them fairly quickly, so I'd avoid that if at all possible. With the built in a2sd you should not hit problems after installing "several apps" - I've installed > 130 apps with ROMs like that with no problem. If you are S-Off you can use a custom hboot with MildWild to increase your actual data space, with the built-in a2sd script in addition, which unless you have some app that's using a pathological amount of data should be sufficient for most people.

is there any way to move 'app data' bcuz I use large no. of apps and phone memory can't store more than 144MB of app data.?

 

[nicka3200]

Read the root memory f a q in the all things root guide section of this forum. It will tell you ever think you need to know.

 

[Hadron]

There are things people call "data2sd". It's possible, but as I said a lot of people who tried it gave up (performance or stability problems). 144MB is still a lot of app data - with 181 apps (system plus user) I'm not using anything close to that in data (my dalvik cache is much bigger than my app data).

If you want to try that, you'll have to research the data2sd solutions available - I've paid them little attention lately, so can't suggest one. You will need a fast sd card.

But as you use 4Ext recovery, I'm guessing you are S-Off. In that case, you could use a custom hboot to give yourself more storage. Read the root memory faq, which will explain the options and how to do this. If in any doubt at all, ask before going ahead, because the hboot is a critical part of the system, so you don't want to do it wrong. MildWild ROMs will fit in the CM7r2 hboot easily, which will increase your data space to 287MB. With just a little editing (removing things you don't need from the zip before flashing the ROM) you should be able to fit it in the Oxygen r2 hboot, which gives you 332 MB of space. And the a2sd that the MW ROMs contain will still move apks and dalvik cache to sd-ext, so that gives you a lot more space. Most people here opted for that type of solution rather than using a data2sd method.

 

[1gouravgg]

But as you use 4Ext recovery, I'm guessing you are S-Off. In that case, you could use a custom hboot to give yourself more storage. Read the root memory faq, which will explain the options and how to do this. If in any doubt at all, ask before going ahead, because the hboot is a critical part of the system, so you don't want to do it wrong. MildWild ROMs will fit in the CM7r2 hboot easily, which will increase your data space to 287MB. With just a little editing (removing things you don't need from the zip before flashing the ROM) you should be able to fit it in the Oxygen r2 hboot, which gives you 332 MB of space..

can u tell me how to insert hboot cm7r2,i just got confused with that lenghty guide.

 

[nicka3200]

First & foremost do a full back up from recovery.

Download the hboot from AlphaRev.

Verify the MD5SUM of the file you downloaded against the one in the table on the AlphaRev site. There is guide here.

Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)

'fastboot reboot-bootloader'

'fastboot erase cache'

Reboot into recovery & restore the back up you took (changing hboot will corrupt data on all internal partitions).

 

[Hadron]

Take a nandroid backup before doing anything. Flashing hboot will probably corrupt your ROM, so you need to restore the nandroid afterwards.

There are instructions on the alpharev site.

But please read everything concerning this (the faq, alpharev site, Nicka's post) repeatedly until you are sure you know what you are doing. This is a more serious modification than flashing a ROM, and you don't want to get it wrong.