Develop Bugs

HELP! Bricked when upgrading to Modaco's custom ROM (my fault)

I tried and failed to upgrade to Modaco's custom ROM. Here is what I did:
-downloaded and installed patched recovery image
-did Nandroid backup
-installed 'enhanced' custom ROM (from stickied thread) WITHOUT wiping the phone (because I forgot)
-after reboot, the hero image would just loop over and over again
-rolled back to Nandroid backup and wiped this time
-re-installed Modaco's ROM ---> got boot loop again
-read this thread (http://forum.xda-developers.com/showthread.php?t=547284) and tried to clear data by booting while pressing HOME + BACK (I think this is where I unknowingly deleted my nandroid backup)
-still got boot loop, tried restoring backup ---> got "Error performing restore! Try running 'nandroid-mobile.sh restore' from console"
-used adb to push other ROMS onto the SD card and tried to install them, same problem
-tried repartitioning sd card using this (http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/)
-partitions are 1434MB fat32, 512MB ext3, 32MB linux-swap
-tried doing partitioning both before and after installation of ROM --> no effect
-tried repairing ext filesystems --> no effect
I don't know what else to do. Just to be clear, when booting: both androids come up and make the noise and then the htc noise chimes in and "hero" is replaced by "htc" before the loop is repeated. I'm pretty sure the Hero is unbranded (bought it from Chess in Norway).
Thanks a lot in advance for your help.

hi there is your hero branded or unbranded?
if branded ie orange try down loading the rom HTC site for orange if undranded then again down load it from HTC and flash from with in windows follow instructions from HTC site

locutus-of-borg said:
hi there is your hero branded or unbranded?
if branded ie orange try down loading the rom HTC site for orange if undranded then again down load it from HTC and flash from with in windows follow instructions from HTC site
Click to expand...
Click to collapse
It's unbranded, but I can't flash it with the Windows because the phone doesn't get far enough to sync.

Format your fat32 partition in Windows, I got a bootloop til I did this once.
Copy anything on your sd card to hd if you need to.

soulehmoo said:
Format your fat32 partition in Windows, I got a bootloop til I did this once.
Copy anything on your sd card to hd if you need to.
Click to expand...
Click to collapse
How would I do that?

Put the card in a reader and plug it in.
Then my computer r-click the drive letter thats for your card and click format.

soulehmoo said:
Put the card in a reader and plug it in.
Then my computer r-click the drive letter thats for your card and click format.
Click to expand...
Click to collapse
Oh. Any way to do it without a card reader?

Never had to do it, always had a card reader. Could try just formatting fat32 with the recovery to just try get it working but that'll wipe your nandroid backups. If you haven't already.

soulehmoo said:
Never had to do it, always had a card reader. Could try just formatting fat32 with the recovery to just try get it working but that'll wipe your nandroid backups. If you haven't already.
Click to expand...
Click to collapse
I had tried that, but no luck.
I ended up downloading this: http://forum.xda-developers.com/showthread.php?t=561124
With it, I formatted my SD to just have a FAT32, then I installed the generic ROM from Modaco's thread. It boots up now and seems to be ok (new ROM is much faster).

Well if the generic works no reason why modaco's won't.
In that recovery image you have now do the fat32 linux-swap and ext2 format, upgrade to. Ext3 then give modaco's a whirl.

soulehmoo said:
Well if the generic works no reason why modaco's won't.
In that recovery image you have now do the fat32 linux-swap and ext2 format, upgrade to. Ext3 then give modaco's a whirl.
Click to expand...
Click to collapse
Most definitely. I'll update tomorrow. And thank you guys for your help.

One more thing. It is not "Bricked phone", man! Don't scare anybody here

Did you install the core one first and THEN the enhanced one? You haven't said that you did when you explain what steps you took.

I guess I did just install the enhanced version without installing the core... The new firmware (generic) is a big improvement thus far, but I still think I'll try Modaco's this weekend. Thanks again for the help.

Error when installing App2SD

Hi, i am trying to install app2sd using the Nimbu guide found here : http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
However, when i follow that guide and start to flash from the sd card, i get this error:
E:Can't symlink /system/xbin/[
E:Failure at line5:
symlink busybox SYSTEM:xbin/[
The card i am using to flash the app2sd is NOT partitioned. Is this an issue?
Here is some other info on my phone
- i have an orange phone, but i reflashed to the 1.21.... generic rom
- After installing this rom, i flashed the radio back to this one: update-bravo-radio-32.30.00.28U_4.05.00.11-signed.zip
If you need any more info let me know and thanks for your help

ok, just to update this...
i have now managed to install app2sd by reinstalling rootedupdate.zip
HOWEVER, now when i turn my phone on it just goes to the white HTC screen and hangs there, it doesnt ever boot up. Can anyone shed any light as to why its doing this and how i can fix it?
i have partitioned the SD card and did install it with a goldcard
in the mean time im gonna flash back to a non app2sd rom

anyone know why it might be doing this? it just hangs on the white htc splash screen straight after powering on

gyro11 said:
anyone know why it might be doing this? it just hangs on the white htc splash screen straight after powering on
Click to expand...
Click to collapse
If you are stuck in a boot loop, then like you suggested, it's most likely because you have not partitioned the SD Card.
You only need to create a Gold Card if your phone is software branded and is running a non-generic rom.

but ive rebooted the phone with a partitioned SD card and that doesnt work...Does the card i install App2sd need to be partioned?

gyro11 said:
but ive rebooted the phone with a partitioned SD card and that doesnt work...Does the card i install App2sd need to be partioned?
Click to expand...
Click to collapse
You replace the Gold Card sd card with your normal sd card. Then in recovery, you need to partition your SD card, this is for the benefit of allocating extra space with the ext partition, which is used specifically for the installation of App data.
That's why it is recommened to set a 0MB swap, ext2 with 512MB (for apps), and the rest of the partition to FAT32.
Make sure you wipe Factory Reset, Dalvik, Cache, SD:EXT and then flash the ROM. After you have done this and while you are still in recovery (don't reboot phone yet), install Apps2SD zip (only if you are installing a ROM that does not include Apps2SD). Power off phone and then insert your sd card into the phone (not the Gold Card). You then enter Recovery Mode again and partition the SD card accordingly.

ok, but im not sure your understanding (i might be wrong...)
I have 2 sd cards....1 which is a gold card which is NOT partitioned and contains the install file for app2sd
and 1 which is the sdcard i run in my phone under normal operation.
I am ONLY using the non partitioned card to install app2sd. As soon as it is installed i remove this card and insert the Partitioned card
Does this make sense? So i know that a partioned sd card Must be used when running the phone with apps2sd, but do i need a Partioned goldcard just to install it? i can i just use a standard goldcard for the installation (and then put in the partioned card after installation) (note...i am using a goldcard as i have an orange uk desire with a generic rom)

Ah yes i understand you now. Yep, the Gold Card should not be partitioned, only formatted as FAT32. After you have used the Gold Card to install Apps2SD, you then insert the other SD card and partition using that.
-------------------------------------
Sent via the XDA Tapatalk App

ok, so that is how i had it, with the partioned sdcard, but i am still getting the white htc splash screen and not getting any further. Any idea why this might be happening?
im installing it on the 1.21... update

try ext3 , NOT ext2
that did it for me.

rhedgehog said:
try ext3 , NOT ext2
that did it for me.
Click to expand...
Click to collapse
Do you mean to select the option:
SD:ext2 to ext3
as i have already done that and it didnt work

Hmm... strange...
Have you tried repartitioning your sd card? Set the values for swap and ext to zero, then check to see if it boots ok.
-------------------------------------
Sent via the XDA Tapatalk App

MasDroid said:
Hmm... strange...
Have you tried repartitioning your sd card? Set the values for swap and ext to zero, then check to see if it boots ok.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
nope, just tried with these settings and unfortunately still no luck. I even tried it without any sdcard in there at all and still the same result.
Could the radio version have anything to do with it? as (other than the update) thats the only other thing ive flashed to it

gyro11 said:
nope, just tried with these settings and unfortunately still no luck. I even tried it without any sdcard in there at all and still the same result.
Could the radio version have anything to do with it? as (other than the update) thats the only other thing ive flashed to it
Click to expand...
Click to collapse
What Radio version did you flash exactly? I don't think that would cause a problem unless you flashed an incompatible version. Are you running Bootloader 0.75.0000 or 0.80.0000?
I would suggest you flash back to stock Radio and then flash back to stock ROM also, as this will restore the stock Kernel. Then after that, carefully take it step by step and try again.
From the steps you have carried out, it all sounds ok to me. When you attempt this again after returning everything to stock, try a ROM that already includes Apps2SD, leaving you to just partition the SD card (after wiping and flashing the custom ROM while in Recovery).

The rom im using is the rootupdate base (1.15) with the 1.21... generic rom manually installed.
I then flashed the following radio:
update-bravo-radio-32.30.00.28U_4.05.00.11-signed.zip
This is really annoying as im finding myself flashing my phone daily now to get this working. I appreciate all your help but i think now im just gonna wait for a stable release of froyo to come onto the forums and update with that

Thats the stock radio version that you re-flashed so don't see how that would cause a problem.
-------------------------------------
Sent via the XDA Tapatalk App

[Q] Boot Loop...after memory card change?......Rooted Dinc

I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?

Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.

SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.

I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)

SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?

Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".

SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.

Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App

linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.

See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.

Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.

smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....

Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.

1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.

Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.

i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.

Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.

IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.

AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth

i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason

Unable to flash new/seemingly any rom - Any help?

So a while back I rooted my desire, and played about with a few roms, then stuck with cyanogen for quite a while. This is the order of a few actions I took which I think may be where the problem occurred.
So from being rooted with cyanogen 7:
I decided to s-off the phone with alpharev
I then put a new splash screen on
Then decided I wanted a new sd card (I was told by a mate it will just go straight in no problems) So I bought an 8gb card stuck it in put my backed up data on the card and booted, all was fine.
I then thought about trying a few new roms that had appeared, and I tried flashing one only for the phone to hang forever on the splash screen.
I've been trying a few things to try to resolve it, stabbing in the dark, such as running unrevoked3 (maybe to root again, only for it to say the firmware is too new) I made my new sd card a gold card, like I did with the original.
None of these helped. has anyone any ideas or know how to sort this out???

What recovery do you have? Which ROM did hang?

Did you do a full wipe?
Does the rom you want to instal require a ext partition?
Sent from my GT-I9100 using XDA Premium App

I wiped the cache, and dalvik cache, even did a factory reset in recovery. Im using clockwork recovery.
I tried InsertCoin_GB_Sense2.1_CM7_v20 and Reflex_S_2.0_LITE_GingerBread_Sense-2.1_GRI40_A2SD+
Maybe these need an ext partition? Would that be it? I'm not sure how to set that up yet.

yes those roms need ext partition, don't know about reflex bu have insertcoin myself, 1GB ext4.
1.go to recovery
2.press on partition sd,choose the size, then after it's finished convert it to ext3 in partition sd again below the option of making one, you can make ext4, but thats up to you. ext3 is needed..
Don't forget to backup your sd, you'll lose everything on it

The ROM you mentioned is an a2sd ROM. So yes, you'll need to partition your SD card if you want to use a a2sd rom.
Sent from my HTC Desire using Tapatalk

Thanks for this I will get on it and let you know

I can't find an option in my clockwork to partition the sd. Just been searching a bit and seen it can be done through rom manager, that rebooted the phone and left me with the ! in a triangle and the small droid on the screen and when I press the power button it is in recovery it says installation aborted. Is there a guide for the Desire? I can't seem to find one....
Sorry found a guide on here. Will try to do it now.

Ok so I am really struggling to get anywhere with a few different guides to partition the card. Through rom manager it also says signature failed, although I have tried toggling the permissions. Major

stevoh84 said:
Ok so I am really struggling to get anywhere with a few different guides to partition the card. Through rom manager it also says signature failed, although I have tried toggling the permissions. Major
Click to expand...
Click to collapse
Steveoh like i told, do it from recovery(easiest), when you rooted you were able to change the recovery(unrEVOked), do so and change it to Ra recovery
Still if you don't want to this program can help youhttp://www.partitionwizard.com/free-partition-manager.html
Download this and do it from you pc, although it's very easy to do from recovery, takes 5,6 minutes mostly waiting..

I have created a partition with the program you recommenced. How will I know that it is ext 3? And that my phone will use it?
found it!

[Q] CWM recovery dooesnt see Restore files after formatting to Fat32 with GParted.

Before installing a Custom ROM on my rooted Desire I am trying to sort out the SDCard as required but am running into problems.
The guides I've read say to change the size of the Fat32 partition on my card to allow an Ext partition. The trouble is in GParted my card just comes up as 'unallocated'.
If I do format it to Fat32 and add an Ext partition (both Primary) once I put my recovery files (and or update.zip for custom ROM) on the card and enter CWM Recovery it doesnt see the files. It just says 'no files found'.
At one point my phone said it couldn't mount SD Card. This even occured when booting phone as usual as no memory card was showing up.
Has anyone else had this problem?

Well I've spent about three hours on this again today still to no avail.
I tried formatting the card in recovery then brought it up in gparted. The card was still showing up as 'unallocated' and when I created the Fat32/Ext partitions the card once again failed to be read by recovery. Although Windows has no problem seeing it.
Eventually my phone and gparted couldnt see or mount the card at all. After running my phone and formatting the card it eventually saw it.
I thought the problem may be because I connected my card to gparted through the phone so tried a card reader but the card reader didn't appear to work. I don't know if the difference I explained is important.
Is it feasible to install a decent custom rom with A2SD with the partition created through recovery? (which gparted also didnt see) as I am having an absolute headache with gparted. Every work around I try just creates a new problem.

Try this: Use Gparted to partition whole card to 1 FAT32 primary partition and then partition it via 4ext recovery into two partitions as required.

Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?

Steveh8204 said:
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Click to expand...
Click to collapse
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in

Droidzone said:
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Click to expand...
Click to collapse
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?

Steveh8204 said:
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Click to expand...
Click to collapse
You were the one who mentioned a full wipe! I thought that was what you meant.

Droidzone said:
You were the one who mentioned a full wipe! I thought that was what you meant.
Click to expand...
Click to collapse
The installation instructions mention a full wipe but reading further it does mention a factory reset so its ok. Will let you know how I get on once the kids are in bed.

Right after some messing about I've had some success. I booted back into Android once I'd used GParted and after a while it saw my SD Card ok.
My Windows PC only saw 12.9GB (of a 16GB card), my phone saw the full 14.9gb in Android and GParted saw both partitions.
As I'd just done a factory reset and my PC saw my Phone I transferred the ROM File to my memory card and installed.
As I had downloaded the Extreme edition I followed the Classic install instructions as instructed and rebooted (after booting to android after install).
The LEd flashed green a couple of times as mentioned but then stopped and is now stuck on the htc screen.
Am I right the file I installed (Supernova_2.4.0.0_signed) is the classic version? Should I have downloaded a sepaerate file for the A2SD installer? The instructions don't seem to suggest this.
And most importantly how do I get my phone to work? lol, please help!
Update: Before I installed the ROM it was showing up correctly in GParted and in Windows it was only showing the Fat32 section which I assumed to be correct. After removing the battery I am back to starting up as normal (with the new Custom ROM) but the SD Card will not show up in GParted and will only allow me to use in Windows if I format first which I havent done. Therefore I can only conclude the file system has got lost somewhere which is why the A2SD installer crashed.
I've very happy with the improved ROM but I still don't have extra stoarge space which was the whole point in upgrading.
Any idea where I can go from here?

The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com

Droidzone said:
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Click to expand...
Click to collapse
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?

Steveh8204 said:
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Click to expand...
Click to collapse
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?

Steveh8204 said:
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Click to expand...
Click to collapse
Take my advice and move over to 4ext recovery.. It's the best atm.. you'll love it.
Edit:
I saw your post at droid-force.com and have responded to it there/