Develop Bugs

E: unknown volume for path [/sd-ext]

How do I fix this? I made an EXT partition of 256mb and I even tried formatting the sd card. Using a Patriot 16gb Micro sd Class 10 (don't know if that is relevant)
Also installed the recovery from fastboot. CWM 3.0.0.5

James_Caliber said:
How do I fix this? I made an EXT partition of 256mb and I even tried formatting the sd card. Using a Patriot 16gb Micro sd Class 10 (don't know if that is relevant)
Also installed the recovery from fastboot. CWM 3.0.0.5
Click to expand...
Click to collapse
Where are you getting this error? Are you trying to set up Apps2ext? I think currently that only works on Enomther's ROM. If you aren't trying to run Apps2Ext, what is the EXT partition on your SD card for?

ianmcquinn said:
Where are you getting this error? Are you trying to set up Apps2ext? I think currently that only works on Enomther's ROM. If you aren't trying to run Apps2Ext, what is the EXT partition on your SD card for?
Click to expand...
Click to collapse
Apps2EXT is the same as Apps2SD right? If that's the case then yeah that's what I'm trying to do. I thought EXT Partition works with CM7? If not then guess I'll stop trying. I get that error in recovery when I wipe Dalvik Cache and when I try to mount SD-EXT Partition or when I try to format it.

James_Caliber said:
Apps2EXT is the same as Apps2SD right? If that's the case then yeah that's what I'm trying to do. I thought EXT Partition works with CM7? If not then guess I'll stop trying. I get that error in recovery when I wipe Dalvik Cache and when I try to mount SD-EXT Partition or when I try to format it.
Click to expand...
Click to collapse
Apps2sd and Apps2sd are two diffreant thing apps2sd stores apps on a FAT formatted sdcard (which is what Froyo uses as native apps2sd with apps that allow it and no widgets) , while apps2ext stores apps on a partition on your sd card formatted to EXT file system, which your phone mounts as part of its internal system so it will support widgets and apps that previously could only be supported on internal storage, so it considers it internal storage even though its on the sd card, so no they are not the same thing, right now the only rom that supports apps2ext is Enoms rom.
Sent from my HTC Vision using XDA App

James_Caliber said:
Apps2EXT is the same as Apps2SD right? If that's the case then yeah that's what I'm trying to do. I thought EXT Partition works with CM7? If not then guess I'll stop trying. I get that error in recovery when I wipe Dalvik Cache and when I try to mount SD-EXT Partition or when I try to format it.
Click to expand...
Click to collapse
I think nowawdays Apps2SD is used to refer to the system built-in to Froyo for moving apps to the SD card (does not use ext file system or need special partitioning). This just works out of the box on any Vision ROM.
CM7 uses the ext4 filesystem for all of it's partitions, which is new (not sure if that's what you are talking about). Hadn't heard it supports Apps2Ext, but maybe?
If you aren't using Apps2Ext though, you should expect to see a warning about a missing sd-ext partition when doing that stuff in recovery, so you're okay.

[Q] Can't make apps move to SD card

Heya,
Today I flashed a fresh Defrost 6.1a (Which is said to support A2SD+), Flashed Gapps. So far so good.
I took my 8GB SD card and partitioned it in Ubuntu using Gpareted. I set the FAT32 partition first, then a ext3 partition (512MB) second.
Ubuntu read both with accurate sizes.
I put the card back into the phone and looked "SD card & phone storage", it no said my SD card is only 6.89GB, but the Internal phone storage was still low.
I decided to check a little more with Titanium Backup, which surprisingly said that my ext3 partition is only 256MB and is half full (talking about a fresh ROM here).
Can someone point me to where I did wrong?
Maybe format using ext4?
Put the ext partition first?
Reflash ROM after partitioning?
TNX

I have never got A2SD working either. I think you need to install a script or something. Here is a post about A2SD. Also, Android 2.2+ supports moving apps to SD anyway.
If you want more space to install apps, you can install one of AlphaRev's HBoot templates which can increase the /data partition, that's if you have S-Off.
I couldn't be bothered farting around with A2SD and so I did that instead.

CoreOxide said:
Maybe format using ext4?
Click to expand...
Click to collapse
No, it will not make it work and will only increase your memory card's wear.
CoreOxide said:
Reflash ROM after partitioning?
Click to expand...
Click to collapse
So you flashed the a2sd enabled ROM on the device which didn't have memory card prepared? I always thought such enterprises would end in a boot loop. Flash it again if this is the case.
GoogleJelly said:
Also, Android 2.2+ supports moving apps to SD anyway.
Click to expand...
Click to collapse
It is not teh same thing!
erklat said:
How do you inspect if a2sd is working? Coz I think u r doing it wrong. Install Quick system info and check what it says under a2sd storage and if it slowly decreases when you install apps, which means it is working. You don't have to set default install location anywhere, the script does that for you.
What you are referring to here, is Froyo's built-in a2sd which requires the app to be optimized for app2sd, that's why only some of your apps seem to be on the SD card. Furthermore, it will transfer the apps to FAT32 partition, that you don't want for it to do since Android first loads apps which need to be loaded at startup, and afterwards it mounts the SD card, which will lead to some apps failing to start after boot.
a2sd tricks the phone into thinking that ext partition is it's internal memory. Froyo app2sd != a2sd script, don't confuse those two, they are not the same.
Click to expand...
Click to collapse
Sent from my HTC Desire using Tapatalk

[Q]SD Card SD-EXT Dissappeared[Q]

I have an 8GB SanDisk MicroSD, it had a 500MB SD-EXT partition made using ROM Manager with 0MB of Swap. I was using OpenDesire, the latest version.
However I decided to change to Cynanogen 6.1.1, as it is more stable. I decided to Un-Mount and Format my SD Card, as I know this wont format my SD-Ext. After Formatting my SD Card wouldn't re-mount so I connected it to my computer, and formatted it again, by right clicking and clicking Format in My Computer.
After doing this it said I had 7.86 GB of Memory on my SD-Card. This is how much is left on the SD Card with no Partition's or data. After I installed Cynanogen, when wiping the user data, I noticed that it said there was no SD-Ext partiton, and so it couldn't format it. I immidiatley went back to ROM Manager to create one, however when it gets to the Clockwork MOD Part I just get a error about a signature or something? Can anyone please help - thanks!

Perhaps the format option under settings wiped the whole SD card and repartitioned it with a single FAT partition, therefore deleting the EXT partition. Format from within windows/linux in future. AFAIK, there would not be an ext on a stock rom and therefore no need for one, so the format option just goes ahead an obliterates.
If you've got a nandroid you could just repartition and restore.

Sounds like it just formatted the whole thing into a single partition. Just partition it back again as your really suppose to do when switching roms.

Partitioning for CM7 and App2SD

I am using Cyanogenmod 7 and App2SD (as explained here). I want to move EVERYTHING to the SD card (including data) and use ext4. How should I partition the card (using Gparted) to have it working properly?
I tried doing it with Clockworkmod but it is very limited (only 1 partition+swap?) and does not ask me if it should be ext4.

yah its better if u use gparted live cd..cwm create by default an ext3
but be aware that any cwm recovery below 5.x will format ur ext partition in ext3 as soon u do a wipe or a restore on it! to use an ext4 u should use cwm 5.x and up (or alternative amon_ra 2.0.1)

My question was: How should partitions look on the card. What types, sizes and for what purpose. For 4gb and 8gb card. I checked the default partitioning done by CWM and it was 1.8gb fat + 1.8gb ext3 + swap. Why the division? Why fat? Can I do it differently, like 10mb fat + 3.8gb ext4?

Dont make your EXT partition over 2GB

All the data moved from the phone to SD card though app2SD - would they be kept on ext or fat partition? Is the FAT partition the one visible on the computer if the phone is connected as a USB storage?

impactor said:
All the data moved from the phone to SD card though app2SD - would they be kept on ext or fat partition? Is the FAT partition the one visible on the computer if the phone is connected as a USB storage?
Click to expand...
Click to collapse
You need to be clear on your definitions before we can answer that.
Do you mean:
1)apps2sd = /manage applications/<application name>/Move to sd?
2)apps2sd = App on teh market that uses the mechanism in 1) to move in bulk?
3)apps2sd = a2sd/+ script that moves apps to ext partiton?
Yes, FAT is the main data storage partition

I have installed app2sd and then done
Cache2SD
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
Now, after reset there is not a single installed application, not even gmail. Even those installed on system partition before (not moved to SD card) are gone and I can't even access Market to reinstall them.
Is this normal? What can I do now?

gmail is not installed with cm, and if u not find it on the market mean is not available in ur country
this is not related to app2sd things..ur orignal problem was the space..with the app2sd u should have solved it now..reinstall all ur apps (leave ur apps on the internal memory, they will automatically moved on the ext) and u shouln't get anymore low space messages

How can I reinstall them if I don't even have Market anymore?

impactor said:
How can I reinstall them if I don't even have Market anymore?
Click to expand...
Click to collapse
maybe u didn't read cm instructions ya?
after flash cm, u have to flash in recovery the gapps package here
this contains the market

I didn't reflash CM. I only installed App2SD

impactor said:
I didn't reflash CM. I only installed App2SD
Click to expand...
Click to collapse
before u said "after reset"..what means?

I mean "after reboot".
I just tried installing gapps for CM but evne though the installation looked successful, after reboot I still cannot see any new apps, including the market.
I also cannot install any nightly build over current RM 7.1 as I am getting an ERROR during installation attempt.

After few tries, I managed to install newest nightly build (7.1 RC won't install at all as it says the zip is BAD even though md5 is correct).
Anyway, I installed google apps afterwards, but I only got google talk in the app menu. Still no Market...

[Q] pb99diag missing after partiton resize

Seems I've made a bit of a booboo somewhere. I was recreating the ext3 partition on my sd card. I deleted the existing ext4 partition and resized the fat32 partition to take up the slack left behind. When I checked the partitions afterwards, everything was fine and all my files were present and correct in my fat32 partition. I booted into recovery, formatted all partitions except my fat32 and went to install my rom again. Except I forgot to put it on the sd card. So I copied it back on to my sd card, stuck the card back in the phone, booted into recovery and promptly got a message that pb99diag.zip is missing. I've checked the entire fat32 partition and there's no sign of it. I tried renaming "OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip" to "pb99diag.zip" but it doesn't seem to like it.
How can I get back into recovery without the pb99diag.zip?

found a similar thread: http://www.modaco.com/topic/348778-hboot-looking-for-pb99diagzip-why/
It's because you resized it, I believe it might eventually stop searching for the file and go into recovery, but it's not ideal.
I'd try backing up sd again, and completely reformatting and partitioning again, but using up to date gparted instead.
- Also, why did you need to change from ext4 to ext3? ext4 is marginally faster, most ROMs support ext4.
- And are you trying to install an RUU? In which case you don't need an ext partition at all?
Sorry just trying to understand your overall aim...

- Also, why did you need to change from ext4 to ext3? ext4 is marginally faster, most ROMs support ext4.
- And are you trying to install an RUU? In which case you don't need an ext partition at all?
Click to expand...
Click to collapse
I had 2 2gb ext partitions, ext3, ext4. I didn't need 2 so deleted 1 and just created a single ext3 partition. I wanted to go back to my PA jb 4.2.2 which was working fine until I used link2sd to free up some more system space but because its sh1t it just completely ballsed up my entire install. I installed an RU and this left me rooted with s-off and it was plain sailing from there to reinstall recovery and flash my custom rom again. I'm using a different sd card now (for testing purposes) but I'm still getting the pb99 errors. As you say, it will eventually allow me into recovery and I can continue what I'm doing but it takes ages and I've never had this issue before.
I'm using MiniTool Partition Wizard Professional to create my partitions.

mickrick said:
I'm using MiniTool Partition Wizard Professional to create my partitions.
Click to expand...
Click to collapse
There's your main problem, do not use MiniTool Partition Wizard. More often than not it creates improperly aligned partitions. Link2SD won't have helped either, it's a messy method and you don't need it with 4.2.2 ROMs, follow the instructions to activate A2SD via terminal commands.
I would backup the FAT32 partition of your sd card, and reformat and repartition the whole thing using gparted. Use this video guide to help
Basically you want to remove all partitions and create one FAT32 partition, and max 2GB ext4 partition. You might as well keep it ext4 over ext3, it should be marginally faster.
Then full wipe and reflash ROM, don't use link2SD.
You should also look to s-off, search for guides, much more powerful, and useful if things go wrong.