Can't seem to run custom ROMs on my Desire anymore

Forums › Android › Can't seem to run custom ROMs on my Desire anymore

Kiwi1971

693 posts

Ultimate Geek
+1 received by user: 8

Topic # 85945 28-Jun-2011 16:09

I have a rooted HTC Desire which I have previously installed a number of custom ROMs [LeeDroid, Oxygen, CyanogenMod 7 etc] using ROM manager and Clockwork Modon without any issues.

I can install them without error and it completes the install as far as ClockworkModbut is concerned but none of them will boot past the white HTC screen and it just hangs there indefinitely.

After which failure I just restore my back-up of CM6 which is OK but I want to try a lighter more streamlined ROM for space issues. I don't really want to be stuck with one custom ROM for ever, for one thing, I get space low warnings constantly.

I have tried the whole unrevoked3 rooting procedure from start to finish then installing a ROM but it didn't help.
I have wiped and factory reset to no avail. Anyone got any suggestions as to what might have happened?

Is this to to with partitions etc as I thought these were created during the install process as it pretty much says it onscreen while I install it.

DLS

1 | 2

924 posts

Ultimate Geek
+1 received by user: 35
Inactive user

Reply # 486981 28-Jun-2011 16:19

Are you wiping everything?
I always wipe dalvik, cache, and then do the factory reset.

Kiwi1971

693 posts

Ultimate Geek
+1 received by user: 8

Reply # 486987 28-Jun-2011 16:26

TheUngeek: Are you wiping everything?
I always wipe dalvik, cache, and then do the factory reset.

ROM manager gives me the option to wipe everything and back up which I opt for but I perhaps have never done a factory reset in combination with a full wipe and previously never needed to.

Will have a go although I did do a factory reset before trying an install but maybe not in conjustion with a full wipe and a dalvik cache clear.

Will try that and see how I go.

Annoying as it used to be so easy.

DLS

TheUngeek

924 posts

Ultimate Geek
+1 received by user: 35
Inactive user

Reply # 486990 28-Jun-2011 16:28

I have heard of some ROM devs saying not to reflash using rom manager as it casues issues.
Do it via recovery reboot

Kiwi1971

693 posts

Ultimate Geek
+1 received by user: 8

Reply # 486996 28-Jun-2011 16:34

TheUngeek: I have heard of some ROM devs saying not to reflash using rom manager as it casues issues.
Do it via recovery reboot

The only issue I have had with ROM Manager is that when it reboots into recovery to install I get a signature verification error: Install aborted. Even though I disable Sig verification all the time.
However when i get this error I ensure it is disabled and restart recovery only...it then proceeds with the installation.
This also happens with backing up using ROM manager. Even though my sig verification is off, it will say it has failed this check every time until I restart recovery.

In any case I also try just going into CWMod and choosing install zip from SD card as I have previously but with the same results.

DLS

stevenz

2784 posts

Uber Geek
+1 received by user: 121

Reply # 487002 28-Jun-2011 16:37

ROM Manager is more trouble than it's worth. Do it using adb, fastboot and recovery.

Back up your apps with Titanium Backup if you can.

Boot into recovery, do a nandroid backup.

Wipe cache, dalvik cache and data, then flash the .ZIP for your desired firmware.

Unless you've flashed something fairly unusual (custom bootloader) then the partitions shouldn't have changed. If you have done that, then you might need to find a standard one and flash it back. Flashing a bootloader is pretty much the only thing that can perma-brick the phone if it goes wrong though.

You might want to try using a new SDCard and repartition it from within recovery with about 512MB for ext data so you can use APPS2SD which many custom firmwares will support, otherwise you can install the DarkTremor A2SD add-on. (Set Swap partition size to 0 if you do this, you don't need one).

@KnightNZ

TheUngeek

924 posts

Ultimate Geek
+1 received by user: 35
Inactive user

Reply # 487003 28-Jun-2011 16:37

ok
Have you tried it without using an app though?
Reboot into recovery and (or switch on using power/volume) and install from sd via the menu there?

I'm quite n00b at it oo, but did a lot of reading a few weeks go when I rooted

Kiwi1971

693 posts

Ultimate Geek
+1 received by user: 8

Reply # 487012 28-Jun-2011 16:48

Thanks both of you for the suggestions.
I always do a full Titanium and Rom back up before trying anything. Bit of a worry at the weekend when my latest back up would not restore due to a MD5 Mismatch but fortunately I had a previous one I could use that was only about 5 days old.
Although I read today that this mismatch might have been due to the naming convention I used having unacceptable characters.

I will look into Nandroid as I do see it mentioned a lot. However my CWmod backups are usually fine, is that an acceptable alternative to Nandroid for my purposes?

DLS

TheUngeek

924 posts

Ultimate Geek
+1 received by user: 35
Inactive user

Reply # 487016 28-Jun-2011 16:53

A Nandroid back up is backing up the full system of the phone.
It's not an app or anything.
the idea is you back it all up and if things go wrong you can restore your phone back to how it was before you started.

If in doubt, have a good read of the instructions for the ROM you want to install.
Knowing every term is very helpful if things don't go 100% as advertised

CdTDroiD

869 posts

Ultimate Geek
+1 received by user: 4

Trusted

Reply # 487205 28-Jun-2011 23:46

Backups can become corrupt if they have been renamed sometimes also make sure you always restore in the same recovery as you backed up with or you could brick your phone.

NEVER use ROM manager to flash, back up or anything it causes so many issues, i would just uninstall really...

Worst case just unroot by running factory RUU then re root and re flash.

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

eXDee

4025 posts

Uber Geek
+1 received by user: 1076

Trusted

Reply # 487207 28-Jun-2011 23:50

Reflash your HBOOT via fastboot (assuming S-OFF). I have had this problem at least twice, it may or may not fix it for you but it certainly helped for me.
http://alpharev.nl

CdTDroiD

869 posts

Ultimate Geek
+1 received by user: 4

Trusted

Reply # 487347 29-Jun-2011 11:20

eXDee: Reflash your HBOOT via fastboot (assuming S-OFF). I have had this problem at least twice, it may or may not fix it for you but it certainly helped for me.
http://alpharev.nl

How do you know he has flashed a different HBOOT to start with? That shouldnt have anything to do with his backup restoring. Also if you have booted into recovery via. ROM Manager and backed up then booted into recovery via. Vol Down + Power buttons and tried to restore you will have issues.

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

Kiwi1971

693 posts

Ultimate Geek
+1 received by user: 8

Reply # 487356 29-Jun-2011 11:36

CdTDroiD: How do you know he has flashed a different HBOOT to start with? That shouldnt have anything to do with his backup restoring. Also if you have booted into recovery via. ROM Manager and backed up then booted into recovery via. Vol Down + Power buttons and tried to restore you will have issues.

I haven't really got a backup restore problem. Yes, one of my backups failed to restore but was most likely because of the name I gave it having an invalid character like / or something.
I deleted it before I could rename it and try again so I can't be sure.

The main issue I raised was not being able to run custom ROMS even though they appear to have installed OK.

I have S-on according to my PWR+Vol down screen
BRAVO PVT3 SHIP S-ON
HBOOT-0.83.0001

I have reformatted my SD card in the past few months, was there a partition on there that I need to enable the ROMS to run? But i thought this would be created during install

I have tried to apply an S-OFF fix last weekend but it didn't take.

DLS

CdTDroiD

869 posts

Ultimate Geek
+1 received by user: 4

Trusted

Reply # 487359 29-Jun-2011 11:40

You need to partition your SD card before installing a ROM the install does not do it for you.

Forget about the HBOOT flashing to, it has nothing to do with it in your case, you are S-ON.

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

CdTDroiD

869 posts

Ultimate Geek
+1 received by user: 4

Trusted

Reply # 487363 29-Jun-2011 11:45

Also... do you have a file called update.zip on your SD card?

Follow me on Twitter !
Get help with Android from a XDA Recognized Developer - Google+

TheUngeek

924 posts

Ultimate Geek
+1 received by user: 35
Inactive user

Reply # 487365 29-Jun-2011 11:47

I think I do.
What is it?

1 | 2