Database Users

[Q] Completed DJ05 install successfully, but have a question.

This is my first post on this forum just want to say all of you guys are great. I have a verizon fascinate, i rooted, installed the DJ05 radio (modem), installed stockDJ05 rom, and 1212 test kernel. Then i installed the Blackhole 2.3 rom from sonofskywalker..All done successfully! BUT heres my question, I heard its good to wipe data and cache between flashing roms, and i dont know if this is going to affect the DJ05 "Radio"(modem). Is it safe to wipe data and cache through CLOCKWORK?

tyler1234567 said:
This is my first post on this forum just want to say all of you guys are great. I have a verizon fascinate, i rooted, installed the DJ05 radio (modem), installed stockDJ05 rom, and 1212 test kernel. Then i installed the Blackhole 2.3 rom from sonofskywalker..All done successfully! BUT heres my question, I heard its good to wipe data and cache between flashing roms, and i dont know if this is going to affect the DJ05 "Radio"(modem). Is it safe to wipe data and cache through CLOCKWORK?
Click to expand...
Click to collapse
Data and cache refer to user generated data not ROM/Kernel/Radio data. The modem you installed will not be wiped in the Clockwork wipe data and cache process.

Thank you! I was also wondering, since i installed the blackhole2.3(dj05)ROM, does that mean i dont even need the stock(dj05)ROM??
Just not sure and would like to know.

tyler1234567 said:
Thank you! I was also wondering, since i installed the blackhole2.3(dj05)ROM, does that mean i dont even need the stock(dj05)ROM??
Just not sure and would like to know.
Click to expand...
Click to collapse
This is like comparing a Jona Gold apple to a Golden Delicious apple. They are both apples and you either eat one or the other. Well normally anyway. The stock ROM is just the leaked factory DJ05 ROM. The blackhole 2.3 DJ05 is the result of someone, with greater skills then I possess, taking that stock ROM and modifying it to their (and maybe your) liking. They are both ROM's.

thanks once again!

I'm going to give this a shot this weekend. Probably a stupid question but better to ask than not - I need to flash the DJ05 modem before I can flash any ROM (stock, BH, SC, etc.), correct? So it would be -
1. Modem
2. Choice of ROM
3. Choice of kernel
Thanks in advance.
-87W

87wrangler said:
I'm going to give this a shot this weekend. Probably a stupid question but better to ask than not - I need to flash the DJ05 modem before I can flash any ROM (stock, BH, SC, etc.), correct? So it would be -
1. Modem
2. Choice of ROM
3. Choice of kernel
Thanks in advance.
-87W
Click to expand...
Click to collapse
Yes, that is what you would want to do.

On the Motorola Droid when you switched ROMs it was just fine to format everything listed in ClockworkMod Recovery. Is this the case for the Samsung Fascinate or is there extraneous data left over even after formatting all through ClockworkMod?

If you format everything listed in CWM, there shouldn't be anything lingering on the phone. You don't actually have to format data or cache when flashing if you don't want to. I never format data unless I start having issues that I can't fix any other way.

balaams_ass said:
This is like comparing a Jona Gold apple to a Golden Delicious apple. They are both apples and you either eat one or the other. Well normally anyway. The stock ROM is just the leaked factory DJ05 ROM. The blackhole 2.3 DJ05 is the result of someone, with greater skills then I possess, taking that stock ROM and modifying it to their (and maybe your) liking. They are both ROM's.
Click to expand...
Click to collapse
I like your explanation. Can you make a similiar, easy to understand explanation for the differences in kernels. Thanks

87wrangler said:
I'm going to give this a shot this weekend. Probably a stupid question but better to ask than not - I need to flash the DJ05 modem before I can flash any ROM (stock, BH, SC, etc.), correct? So it would be -
1. Modem
2. Choice of ROM
3. Choice of kernel
Thanks in advance.
-87W
Click to expand...
Click to collapse
This is correct.
But, do not fret too much. It's like chicken and egg. I guess I flashed ROM first and then modem, and I am still fine. You do not have absolutely virgin phone with empty memory anyway. So, whatever you do, something will be first and another thing second, because of sequential nature of the flashing process. It is fine to have this discrepancy while you flash.
Just make sure that when you going to ACTUALLY USE the phone everything is in sync.

Viper Rom DK 17 2.8

I know there is a Dk 28 version now but I'm still kind of new to the game and want to fully understand everything b4 moving on. I was able to get viper rom dk 17 2.8 installed this wkend after a bunch of mistakes on my part. Everything seems to be working well on this version except for the fact if I go to any web page that requires me to log in. When I click on where I type in my username or password the page will force close. Seems like some sort of security issue. Is there a setting I can change or is this a limitation of DK 17 version. Thanks for your help.

For future reference, this post should go in the Question and Answers section.
That being said, DK17 is an older leak, therefore support for it is going to be minimal. It also wasn't around all that long, so devs didn't spend a huge amount of time on it. The DK28 roms are going to be more stable.
If I were you I would go to this thread : Return to Stock
- Once your phone is back to stock, root it again like you did the first time using the one click.
- Download and install the DK28 modem and pit file using Odin. Should be the same steps you took to install the DK17 modem and pit.
- Then download one of the DK28 roms, i.e. viper, bonsai, quantum. Install those from clockwork.
If you need steps explained a little better than post, but don't do anything you are unsure of, cause you don't want to turn your phone into a paper weight.

swanysto said:
For future reference, this post should go in the Question and Answers section.
That being said, DK17 is an older leak, therefore support for it is going to be minimal. It also wasn't around all that long, so devs didn't spend a huge amount of time on it. The DK28 roms are going to be more stable.
If I were you I would go to this thread : Return to Stock
- Once your phone is back to stock, root it again like you did the first time using the one click.
- Download and install the DK28 modem and pit file using Odin. Should be the same steps you took to install the DK17 modem and pit.
- Then download one of the DK28 roms, i.e. viper, bonsai, quantum. Install those from clockwork.
If you need steps explained a little better than post, but don't do anything you are unsure of, cause you don't want to turn your phone into a paper weight.
Click to expand...
Click to collapse
Will do. Thanks for your help.

[Q] After flashing back stock ROM, the phone keeps blinking on the boot screen (HELP)

I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)

Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.

tamaleddon said:
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
Click to expand...
Click to collapse
I just flashed the RE version and it's making some progress. Definitely no weird colors.
PROBLEM:
-the boot screen is still flashing when trying to boot my phone, only this time it's with the "Darkcore & Darky's ROM" logo on it. The flashing is at a slower pace this time around.
ALSO:
I can get into the stock recovery screen, I hope this can somehow help
what should I doo!!?!

Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G

gfacer said:
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
Click to expand...
Click to collapse
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?

As far as i read on the Darky Site you have to activate Lagfix to install 10.2
Do you?
In other case.
Install Resurrection 9.2 FW:
(sorry. new member no links outside allowed: Go darky forum, stable roms, darky resurrection 9.2)
If that works your bootloader if for Froyo and afterwards you can go on to flash Darkys 10.2 like written in the Darky Forum.
But i would suggest to stay on Darky´s 9.5 with 2.2.1
It is the stable version with no bugs at all. This gingerbread sucks a lot with Akku Drain, Light sensor and other thing. Also no call records.
I will stay on 9.5 so far. Best solution at the moment...
The thing with installing 10.2 you installed without installing 2.3.3 rom before could be, that is maybe possible to install Darkys 10.2 Theme on a 2.2.1?
But no guarantee...

roma17 said:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
Click to expand...
Click to collapse
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App

sxi200 said:
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your response! Greatly appreciated. But at the time, I'm just looking to get my phone to work. It still doesn't work, it's still only stuck flashing the bootscreen, nothing else.
From my other post:
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much

Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App

Could be that you have a lagfix enabled and the stock ROM can't read the EXT4 file system. If so, try flashing another custom ROM via Odin (e.g. GingerReal), disable the lagfix to go back to RFS, then from there you can go back to the stock ROM.

gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Well CM7 forum is down but here is the most of the link, you can google this and look at the cached pages. cyanogenmod topic/15707-how-to-restore-to-stock-on-your-gt-i9000m/
You should be able to click to the multi upload link too.
Now - you are aware of course that our i9000m models can suck and die fairly readily, especially when flashing certain roms. Has yours even been returned yet? Mine has and they replaced the motherboard. You may actually have a warrenty job and in any regard they won't likely fight too hard (just flash it to one of the jl2 or kc1 rom first).
If you want to find out for sure. look for the i9000m threads where they install eclair and use the external sd to boot and then look at the memory (internal then shows as external I think - its in the thread). Basically if it shows 0 available you're hooped.

gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
I'm downloading the ROM from this link, could you verify it?
http://forum.xda-developers.com/showthread.php?t=883568

It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App

gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
there is a I9000UGJL2_homebinary_add_param.tar
and a SS_DL.dll
so All i would have to do is just put that .tar file in PDA field and get a regular .pit file and check off the re-partitions

gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!

Great!
My advice would be to pretend it never happened, but read all the instructions for the rom you are interested in and start from scratch.
Generally I would go custom froyo kernel from odin which will root you and give cwm generally, update bootloader to gb via a stock rom or ezbase, then flash 10.2 via cwm.
Darky has excellent guides also look at ezbase thread.
Sent from my GT-I9000M using XDA Premium App

roma17 said:
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Click to expand...
Click to collapse
To load Darky 10.2 successfully on your phone, you have to flash JVP or JVQ bootloader over your phone. The best solution is flash Stock Rom with bootloader over your phone. Then, flash Darky rom over your phone.

Upgrade from ACSRom 1.0 to CM9

He folks, hadn't updated my phone in a really long time (close to a year). I just updated to CWM 5.0.2.7 in preparation for upgrading to CM9 beta. I'm just wondering if I need to update my modem, kernel, or anything else beforehand.
Thanks for any info.

Nope you can if youd like but just flashing cm9 will be enough.

Big Goron said:
Nope you can if youd like but just flashing cm9 will be enough.
Click to expand...
Click to collapse
Well he should at least be on a GB modem lol.
I wanna mention one thing before you flash though. CM9 is a MTD ROM.
To learn about MTD, go here: http://forum.xda-developers.com/showthread.php?t=1387334
Having knowledge about this will probably prevent a lot of problems.

So basically, I can just run the CM9 beta.zip? I've got a current backup.
From what I can understand, running that .zip will switch my filesystem over to MTD, which is incompatible with a lot of other ROMs. I'm cool with that, I'll probably be sticking with either CM9 or CM7 anyway. But what happens if my install goes wrong?
In regards to modems, are there requirements for compatibility? I believe I'm on EC05, currently. If I do need to upgrade, what should I upgrade to, and is there a good guide for that?

If something goes wrong just re-download and re-flash the zip or odin with the pit file and repartition checked and try again. There's no modem requirement but I'm really liking FB15.
Sent from my SPH-D700 using Tapatalk

oflannabhra said:
So basically, I can just run the CM9 beta.zip? I've got a current backup.
From what I can understand, running that .zip will switch my filesystem over to MTD, which is incompatible with a lot of other ROMs. I'm cool with that, I'll probably be sticking with either CM9 or CM7 anyway. But what happens if my install goes wrong?
In regards to modems, are there requirements for compatibility? I believe I'm on EC05, currently. If I do need to upgrade, what should I upgrade to, and is there a good guide for that?
Click to expand...
Click to collapse
Well fortunately, a lot of roms are MTD-based now.
For a modem, there is no requirement. Modem will NEVER affect the system, just your network speeds and signal strength. It's recommended to update to the EL30 modem though.
Make sure you have a gapps.zip btw if you want gmail, the play store (android market), and all those goodies.
If you are still confused, watch these tutorials (thank qbking77)
http://www.youtube.com/watch?v=p2k60GnYlz4
http://www.youtube.com/watch?v=6RV4g6ya62M
Latest Gapps zip: http://goo-inside.me/gapps/gapps-ics-20120304-signed.zip

Thanks guys, this has been very informative.
One last question regarding the modem: I'm on EC05 currently with a custom ROM. Can I run a .zip to upgrade only my modem from EC05 to EL30? I've read through some threads, but they seem to be outdated. I don't have a PC, so Odin is not an option.

oflannabhra said:
Thanks guys, this has been very informative.
One last question regarding the modem: I'm on EC05 currently with a custom ROM. Can I run a .zip to upgrade only my modem from EC05 to EL30? I've read through some threads, but they seem to be outdated. I don't have a PC, so Odin is not an option.
Click to expand...
Click to collapse
Just flash this in CWM as long as you haven't updated to cm9 yet:
http://www.mediafire.com/?1w6j0k47kbcqzqp

Everything is up and running, now on CM9 b0, EL30, and CWM 5.0.2.7. Thanks for all the help guys!

oflannabhra said:
Everything is up and running, now on CM9 b0, EL30, and CWM 5.0.2.7. Thanks for all the help guys!
Click to expand...
Click to collapse
Its actually cwm 5.5.somethingsomething lol. Cwm recovery is built into cm9 now. Anyway, if you have any more questions just ask! Glad you got it running and everything!
Sent from my Galaxy Tab 10.1

Checkrom v7

I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...

Another checkrom thread..
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P

No, a direct question for answer I can't find anywhere.
I've always been helpful in fora on subjects I knew much about. Please, please refrain from answering if you don't know the answer or don't want to give it.

Look at the forum on www.checkrom.com. The instructions of flashing a kernel through Odin and a new rom are written in the V7-section.
Good luck
Sent from my GT-I9100 using xda app-developers app

Simply flash a safe kernel i.e. siyah kernel, reboot in to recovery and flash a rom(might want to do a full wipe beforehand) or restore a backup.
Good luck, this worked out for me.

frater said:
I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...
Click to expand...
Click to collapse
First off, wise decision...
With respect to getting out of this, you want to flash a 4.0.3 based ROM. Don't go for a 4.0.4 based one quite yet, regardless of recovery type, if you're after a quick and safe fix.
You want to flash Siyah Kernel first, and then flash the ROM from there.
Siyah Kernel can be flashed via ODIN (flash the TAR as a PDA file).
Then go about your procedure to flash as usual. As above I'll re-iterate, don't flash a 4.0.4 based ROM yet (LQ5 or LQM I believe), as these are not always 100% safe in all scenarios.
You're much better to stick away from these for now.
Again, I have no idea why "developers" are going about releasing ROMs which are based on these kernels, without clear and noticeable warnings about what people are getting into...
Oh well... Hope it goes well, just follow this and you'll be fine.

Use Odin to flash siyah,
then use siyah's recovery to install new rom

zzkonzz said:
Use Odin to flash siyah,
then use siyah's recovery to install new rom
Click to expand...
Click to collapse
Exactly what Pulser has already said. Why repeat it again?
Sent from my GT-I9100 using Tapatalk 2

Thanks all....
Now not on checkrom anymore...

It should be noted that Leo, the main dude, says on Checkrom.com:
"No more ROM development for SGS2.
On that note i am closing the thread."
...and slammed the thread closed here on XDA too!

The last time I used Odin was when I bought my SG2. Since then I flashed all my different ROMs with CWM.
Although I'm glad I'm not using checkrom anymore and never will because of the way they stopped their development I do have to admit it had more than decent battery life (their 4.04 version).
I‘m currently on wanamlite and after 2 hours I'm already on 60% :-(
I used to have cyanogenmod 7 on my HTC HD2?
It might be an idea to try 9 or 10

Check out ParanoidAndroid. I'm getting about 30 hours off of the battery.
Sent from my GT-I9100 using xda app-developers app

Very bad form closing the threads when quite a number of people had flashed the new checkrom with the promise of a fix. They could have at least fixed the kernal issue rather than just abandoning it. Very disappointed. Going to try to flash the kernal via ODIN if I can remember even how!