hi people
i tried flashing a few roms (OD, CM and Pays), but while they flash fine, all of them get stuck at their boot screen (the animation keeps looping). is there any reason for this?
i have an ext3 partition and i haven't updated the radio (4.05.00.11 from orange) but from what i gather that should only affect the camera.
brpqzme said:
hi people
i tried flashing a few roms (OD, CM and Pays), but while they flash fine, all of them get stuck at their boot screen (the animation keeps looping). is there any reason for this?
i have an ext3 partition and i haven't updated the radio (4.05.00.11 from orange) but from what i gather that should only affect the camera.
Click to expand...
Click to collapse
Happened to me but not anymore as I:
1. In recovery mode, do a full wipe, cache wipe and Davlik wipe.
2. have learnt to be patient as some custom ROMS, on their first boot can take up to 10 minutes!!
3. after the first boot I then reboot/turn off then restart the phone.
Since then not many problems.
Hope this helps.
Cheers
Aussie
I'll give that a shot! I did wait quite a while, though (20mins for OD)
If I make a nandroid, then do a full wipe and then restore nandroid, will I be back to where I originally started, or does a full wipe delete some stuff not backed up in a nandroid backup?
some roms also need a ext partition on the sd card to work, so make sure you read carefully before choosing a custom rom.....................sudeki300
Updating the radio would be a smart idea.
There is a Froyo compatible radio suitable for OrangeUK on the forums, no idea which one tho (you'll have to flash and re-flash). Or just pay the few quid to unlock the phone.
As far as your custom rom. Best advice is to nandroid, backup your SD-Card and reformat. Partition your SD for EXT2. EXT3 will put undue writes on your SD because of the journaling, thus reducing the overall lifespan of that card.
Stick back your data and flash your new rom. It should take about 5-8 minutes to boot, then you can restore your apps (if you titaniumed/mybackuped) and enjoy custom rom goodness.
ah ok. those steps sound simple enough, i'll try it
so just to clarify, nandroid backs up the data that a full wipe deletes, correct? (sorry if that's a very obvious question!)
Related
Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance
02keilj said:
Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance
Click to expand...
Click to collapse
who is your provider? im not 100% on this on the desire hd, but on the standard desire, you would find your providers RUU rom then flash that to return you to stock then youd have too reroot. but like i said, imma desire user who just got a dhd, so ask some1 with alil more knowldge
Did you do a full wipe, before flashing CM7? If not run one now (i.e wipe /system / cache /data and /dalvik-cache from CWR) before re-flashing CM7. With multiple FC's that is normally the issue, going back to a non cm ROM, not entirely sure about CleanDroid, is problematic without carrying out a full wipe also and may even require using an older version of CWR, see CleanDroid thread for more info on that.
Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it
Ok so ive decided to restore it to stock rom. Will this be possible if my phone cant connect to the PC to sync with HTC sync?
02keilj said:
Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it
Click to expand...
Click to collapse
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .
hedayat7 said:
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .
Click to expand...
Click to collapse
Thanks, I have made sure I didnt miss the full wipe. Ive re-tried wiping and flashing between CM7 and CleadDHD at least 20 times with the same problems. I think ill format my SD card and then copy the files across again. Ill also try the Full wipe 1.3 and see if that helps.
Im wondering if my friend makes a backup of his DHD through Clockwork 3.0.0.6 and then copies the backup file from his SD card to mine, will I be able to restore that backup?
Then from there I can factory reset again to wipe his saved settings?
Thanks for the replies so far guys
Is it possible my clockwork is faulty? I treid updating it through rom manager prior to flashing CM7 and it failed but i assumed it just reverted back to what I already had before. Is there a way I can reinstall clockwork through the current version?
nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.
hedayat7 said:
nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.
Click to expand...
Click to collapse
I will probably make a copy of it rather than use theirs, just in case it ruins their card like it did mine. Would I have to copy their EXT partition data too? If so I can easilly do that in ubuntu yes?
Hi guys, I've been trying to flash the CM7 HBOOT over the past few days but can't seem to get it to work. Basically, I used the Fastboot method and it was successful but got stuck on the Splash screen (did wipe cache and dalvik cache and restore nandroid).
The problem is I can't seem to find a guide on how to resize the partition to those in given in the partition tables. Could someone please be kind enough to help me with that?
I've also tried the Bootloader method (with the goldcard) but it doesn't work. It doesn't recognise that the PB99IMG.zip file is there.
Help would be much appreciated!
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Awesome man! Just one question. If I use the second method, will it resize the partitions automatically?
If you're looking to resize the partitions yourself so you have a different amount of space for /cache and /data and all that, I have no idea how it's done, but it's clearly possible since people make these different Hboot files.
If you're wondering why you're stuck at the splash screen it's probably because your NANDroid restore is too large for your new partitions. Even if you were running CM7 before you flashed the new partitions your /cache would have been too large to fit in the MUCH smaller (5MB) new partition. You should have (though maybe you did) wiped your cache and dalvik first, then taken an NANDroid back up to have it fit. If you didn't wipe them before taking a back up you will need to just flash the ROM again and not use your backup. Should get you back up and running.
bangrahman said:
Awesome man! Just one question. If I use the second method, will it resize the partitions automatically?
Click to expand...
Click to collapse
If you are referring to the partition on the sd, I don't think so.
You can use the recovery mode to resize your partition (backup your sd card before...)
jordan.harris01 said:
If you're looking to resize the partitions yourself so you have a different amount of space for /cache and /data and all that, I have no idea how it's done, but it's clearly possible since people make these different Hboot files.
If you're wondering why you're stuck at the splash screen it's probably because your NANDroid restore is too large for your new partitions. Even if you were running CM7 before you flashed the new partitions your /cache would have been too large to fit in the MUCH smaller (5MB) new partition. You should have (though maybe you did) wiped your cache and dalvik first, then taken an NANDroid back up to have it fit. If you didn't wipe them before taking a back up you will need to just flash the ROM again and not use your backup. Should get you back up and running.
Click to expand...
Click to collapse
OHHHHH!!! Thank you so much dude. Cleared a lot up for me.
Okay.This is so damn annoying now lol. I've done everything correctly. Wiped everything, flashed cm7 hboot SUCCESSFULLY and restored my nandroid yet it STILL freezes on the splash screen.
I checked the size of the cache partition in my backup etc. and it was only a few kb so clearly small enough to fit in the cache partition of CM7 Hboot. I just don't get why it doesn't work!
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Great work...fastboot with a GUI - the safe way to flash.
bangrahman said:
Okay.This is so damn annoying now lol. I've done everything correctly. Wiped everything, flashed cm7 hboot SUCCESSFULLY and restored my nandroid yet it STILL freezes on the splash screen.
I checked the size of the cache partition in my backup etc. and it was only a few kb so clearly small enough to fit in the cache partition of CM7 Hboot. I just don't get why it doesn't work!
Click to expand...
Click to collapse
When you flash the cm7 hboot, did you check after the restart that hboot version was CM7?
Instead of restoring your rom could you try to reinstall a CM7 ROM?
Just to check it at least you can have a phone working…
Let me know
you cant restore NANDROID made on stock hboot, while on CM7 hboot, at least not a full restore (all partitions)
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Exactly what i was looking for!
Thankyou!
Hi guys!
I am sorry if this has already been answered somewhere, but I searched pretty thoroughly and I couldn't find a solution
I am trying to S-OFF an HTC Desire for a friend of mine and install CyanogenMod using this guide http://forum.xda-developers.com/showthread.php?t=1016084.
We rooted the phone without any issues, but before going through Alpharev I decided to make a nandroid backup through the phone's original recovery image (just as advised on Alpharev's site: "We try to leave the current ROM and datastructures completely intact. It is, however, advised to ALWAYS nandroid backup your phone before you run this procedure.
You will then always have a correct/current backup to fall back on in case something breaks."). So I just went into the Backup and Recovery menu and I chose backup.
Unfortunately after backing up, the phone went into a boot loop. We tried taking-out the battery and even doing a hard reset but nothing helped. Eventually we flashed the original RUU from O2 (it's an O2 Germany phone) and this fixed the issue.
I am a bit concerned since I wasn't able to find anyone who had the same problem and it is a bit weird that the phone should go into a boot loop without even installing another ROM or anything - just trying to do a backup of the stock ROM. I am thus a bit hesitant to go on with the S-OFF...
Any help would be deeply appreciated!
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Thanks! Do you know why the boot loop could happen?
Moscow Desire said:
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Click to expand...
Click to collapse
I suppose, there was some code that didn't get deleted due to the rooting process, if you used unrevoked. Although it rarely happens, sometimes it does.
Or maybe it didn't like some Application. Who knows. All it takes, is 1 peice of bad code.
With AlphaRev, although many use it, I believe it changes your bootloader code.
And, you can sometimes have problems as well.
But follow the steps I mentioned, and you should be ok.
Just make sure you create and use the Gold Card first.
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
TheGhost1233 said:
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Right - I thought about that, but then I was hesitant, because I figured if it went into a boot loop then it probably did not create the backup image properly... So can I still restore the backup image now? It is saved on the sdcard so it should be intact after the RUU, right?
It "should be", but, one can only assume so.
Typically, I make a couple of backups each week. One never knows. Yeah, it will tell you successsful. but, better safe than sorry.
So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks
So, I'm planning to finally S-OFF, mainly for the extra internal storage, and the extra speed since I won't be needing my ext3 parition any longer, so just to get some things straight -
1) I am currently on the latest Oxygen ROM, is it OK to S-OFF with this ROM?
2) I've made a nandroid backup of my ROM for restore, thing is, once I re-partition without an sd-ext, what happens when restoring the nandroid? Because when restoring, it needs to restore sd-ext... What do I need to do?
Thanks
As far as I know, Oxygen has a built in a2sd enabled when it sees that you have an EXT partition and might mess up Alpharev's (and or Revolutionary's) S-off process accourding to their site. I suggest you flash CM7 rom temporarily then S-Off with this installed since natively it doesn't support A2SD.
I'm not sure about the 2nd question. My logic tells me that I leave the ext, and do a nandrestore because it will obviously look for an ext partition to flash the data files back. The problem is once, restored and rebooted I don't know if there is a command or zip file you can flash to undo the a2sd and transfer the data from the ext to the data partition of the phone.
It would be better to go do a fresh reinstall of the rom and use titanium backup to restore your apps back.
Thanks, I probably will do the long TB restore process.
Re. the ROM issue - Will flashing Leedroid 2.5.0 Froyo ROM be good enough? As it seems to be pretty stock-ish.
Quoting Alpharev.nl
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
For my understanding as long as the ROM doesn't use data2ext, or 'anything'2ext out of the box it's good to go. I've S-off with Cyanogenmod rom on my phone so I can only speak from what I experienced.