Database Develop

simplest way to switch from JF 1.5 to current Cyan?

I bought a g1 off of craigslist and it already had root. JF 1.4 ....
Around the time cupcake was released I updated it to jf 1.51
Now since there will be no more JF updates I wish to switch to Cyan builds.
I'm unsure of the proper way of doing this?
Should I go back stock .. unroot and then go thru the steps to load cyan?
Or is there a better way? A wipe?
I'm asking to be clear because internet access is strictly from my g1.
Although I can download all the files I need, I do not have constant access.
I'd appreciate any tips or pointing me to the proper thread.

Check the threads in Dream >Dream Android Development look for Cyanogen's thread on his release of 4.1.999, follow the instructions and you will be fine. I'd also suggest at least flashing Cyanogen's v1.4 Recovery Image over JF's, easier to flash any .zip on sdcard. So, new recovery image (use search option in forums, or look in the same thread i mentioned for cyanogen recovery image 1.4) then update to cyanogen's latest rom build

So simply flash a new recovery, then follow the cyan steps?
Cool, easy as pie.
I certainly appreciate it.
Thank you

Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder

B-man007 said:
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
Click to expand...
Click to collapse
that is why there is a full update made for it.

haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol

B-man007 said:
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
Click to expand...
Click to collapse
sleep is for the weak. also it is really hard to flash two things while in recovery it causes hemorrhoids and anal fissures.

haha trust me...someone somewhere will make something incredibly easy look like rocketscience

B-man007 said:
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
Click to expand...
Click to collapse
you mean rocketsurgery

david1171 said:
you mean rocketsurgery
Click to expand...
Click to collapse
*sigh*
yes its true.

B-man007 said:
*sigh*
yes its true.
Click to expand...
Click to collapse
lmao me went to smart person learning place

I'd like to chime in here as well since I'm having such a hard time searching for info on the conversion from jf1.51 to the latest build of CM. The amount of posts are staggering!
So, I vaguely remember setting up apps2sd following the guide at the bottom of this page - http://yokohead.com/2009/06/how-to-root-android-g1-with-cupcake-and-appstosd/
Will CM automatically detect this partition?
Also, will I lose the google experience? I'm still confused as to where we are on that.
Thanks for your time! If anyone knows an updated post on this process, please point me to it.
TJ

Well the sticky by fingerlickin at the top of this section is a good place to start....
all you have to do is find the singleflash update in the dev section, backup and clear everything off your ext3, and wipe+flash the single update. you can restore the ext backup then.
also you should upgrade to cyan 1.4 recovery
to do so
su
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
you wont lose the google experience

Thanks B-Man007,
After a couple attempts, all is working well. I'm thoroughly impressed with the snappiness of this build. Although it's only my second time updating a ROM, I'm going to blame the amount of posts for my hesitation and confusion. It was easy to just go in and do it.
I actually updated to the latest Amon-Ra(sp?) recovery. At first my Rom was running real slow and the recovery allowed me to update my ext2 to ext3. Loving it now!

The amount of posts does make it quite confusing i agree, especially with the high amount of conflicting posts
Ya ext3 is a must, but you could have upgraded from cyans too haha
cyan usually has the fastest builds out there though at times it can get very slow.

Another noob here. A few months ago I rooted and flashed to xrom 1.5. When I do a reboot, my recovery screen tells me its "CyanogenMod v1.4 + JF".
Since xRom is experiencing some problems w/ updates, I figured I might try the latest build of Cyanogen. I re-booted, went to recovery mode. Wiped. Then flashed the latest Cyan and even found the 1.6 ota on another site. Flashed both zips, then did a re-boot and it hangs now.
I tried it over and over a few times, wiping then flashing again. Wiping, then re-booting, then flashing the rom, etc. Over and over with the same results.
Then as a test, I tried flashing back to xRom... perfectly fine.
As another test, I tried wiping and flashing to another rom, the rooted stock option (the HTC rom version)... and got the same results as when I tried Cyan... just hangs.
Wiped and flashed again back to xRom... works fine.
So at this point, I'm thinking I need a more updated recovery rom? Any other possible problems? Yes, I did a search all over and this was the best thread that matched my problem.
If it helps... I have a T-mo G1, firmware 1.5, JACxROMv1.5, kernel version 2.6.29.6-jac-ski root. And I know many will slap their foreheads when I say this: But the SD is NOT partioned at all (kept trying and trying with zero success, so I eventually gave up).

Help with Cyanogen and modding

Ok, i have a need for a bit of help. I rooted and flashed to Jesusfreaks adp. I tried to get it to RC33. LONG story short, JF is installed. My kernel is 2.6.27-00392-g8312baf
NO clue what that means but im at fireware 1.5 and Build number CRB43
I want to get to Cyanogen. It looks a little smoother then JF and more frequently update. BTWi have a G1
I followed this guide TO THE T!
simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
and after i rebooted, it took forever to boot (which is usual)
All my apps crashed. My desktop didnt even load. It had force closes like *android.phone and *android.mail
I figured it was because i was trying to mod off of the Jesus freak setup. Can anyone help me out and tell me how to either COMPLETELY wipe my phone and restore it to its origional G1 official build and then i can re-root to Cyanogen OR a way to mod from Jesusfreak to Cyanogen

copy and paste this into your browser... follow the directions...
wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod[/url]

Just read that guide over and thats all exactly what i already did. I have tried to signed-dream flash and then after taht the cyan mod. It installed the OS no problem. It just didnt have any programs working. IT is as if the phone had the OS but no program files. It wouldnt even load the phone at all. it was a black screen with a status bar and infinate force close screens. Any idea what that is a result of? I had to flash recover back to my JF os

Try this:
1. Flash recovery Amon_Ra (Great improvment on JF and Cyans recovery)
Code:
Copy recovery-RA-dream-v1.5.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
2. Boot into recovery (Home+Power)
3. Wipe Data/Factory Reset
4. Wipe EXT
5. Repair EXT
6. Flash Super D (I suggest Super D only because there is less flashing involved and it's a great improvement on the Cyan roms.. super quick too)
From here you should be set.

so if i already have root and all that, do i still need to follow step 1? Like flash with Amon_Ra? or can i just wipe, and reload the D rom? also your rom says its myHero2.2? is that a good rom? Im just trying to find the best rom to use on a g1. I have read up on Jesusfreak, its very stable, but it is pretty much just a open version of the regular tmobile os. THe only difference is the apps store is an older version. In your opinion, what is the best G1 rom and what are its percs?
thanks for all your help. This has been a working progress haha, finding a good rom and sticking with it. and can you give me a list of all the files needed for the best rom? if they have a step by step guide to it, thatd be great! i would look myself, but im still new at all this and there are like a bajillion different roms/ ways to load the rom. Im a PSP hacker, not an experienced phone guru

Tigger166 said:
so if i already have root and all that, do i still need to follow step 1? Like flash with Amon_Ra?
Click to expand...
Click to collapse
I would just so you're current on your recovery. The updated recovery has added features compared to JF's recovery
Tigger166 said:
or can i just wipe, and reload the D rom? also your rom says its myHero2.2? is that a good rom?
Click to expand...
Click to collapse
I would load the new recovery and then flash Super D. Again it's the most stable and is wicked fast. Yeah used to use myHero2.2 but i haven't updated my sig in a while. It's getting mundane at this point.
Tigger166 said:
Im just trying to find the best rom to use on a g1. I have read up on Jesusfreak, its very stable, but it is pretty much just a open version of the regular tmobile os. THe only difference is the apps store is an older version. In your opinion, what is the best G1 rom and what are its percs?
Click to expand...
Click to collapse
This is going to be more of a difficult question to answer. It just depends on what you're after. I really prefer Super D because of it's speed. Again its built from the Cyan roms so you get Cyan + extras. That's what I would go with. Simple, easy, and fast.
thanks for all your help. This has been a working progress haha, finding a good rom and sticking with it. and can you give me a list of all the files needed for the best rom? if they have a step by step guide to it, thatd be great! i would look myself, but im still new at all this and there are like a bajillion different roms/ ways to load the rom. Im a PSP hacker, not an experienced phone guru
Click to expand...
Click to collapse
Well that's the cool part about the community here at XDA. All the files are set up for you. To flash a rom:
Code:
Download the .zip file and place it on the root of your sd card
Reboot into recovery
Make a backup (i prefer switchrom)
Wipe Data/Factory Reset
Wipe EXT
Repair EXT
Flash rom from .zip
Reboot.
It's that easy.

New recovery 3.0.0.5

Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny

I don't see why not. You can try and if it don't work you can flash an older version in ROM Manager

vinnyjr said:
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
Click to expand...
Click to collapse
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.

I guess I won't find out until I try. Newly rooted and going to give CyanogenMod a try. Know I am going to be happy as hell with it.
Thanks

The new recovery should be fine with flashing any roms. As for any standing problems with it, im am uncertain. You may want to wait 2 weeks or so to see if their are any problems from people using it. Personally I like Amon ra so i cant say.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
Click to expand...
Click to collapse
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?

mikeacela said:
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
Click to expand...
Click to collapse
Yes. I did full wipe on everything. I even fix permission. No luck at all.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
Click to expand...
Click to collapse
I used it to flash and install tonight's build successfully...

I have a "side question".
To flash any GingerBread flavor, do we need 3.x.x.x ou 2.5.x.x is working?
I haven't give CM7 a try yet, but I'm not sure if I need/want to upgrade to 3.x.x.x, 2.5.1.4 work well for me.

DumbUglyDragon said:
I used it to flash and install tonight's build successfully...
Click to expand...
Click to collapse
I got it too. No more crazy rebooting. I solve it by reformatting my SD card and recreating ext3. I guess 3.0.0.5 recovery messed up my ext3 partition. Now, MM CM14 is working pretty well. FYI, I am using 2.5.1.4 recovery.

Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.

doesn't work with MIUI for me!
don't understand that, but luckily its not a big deal flashing older versions!

baseballfanz said:
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
Click to expand...
Click to collapse
I hear you there! That was me last night! DON'T USE 3.0.0.5! The only fix I found to actually work was to completely format my SD card and then re-partition it, then use RA and a fresh install. What a pain in the arse!

Same thing here. Switched to 3.0.0.5, and the next thing, my ext was fried and I had to reformat the entire card. Could be coincidence, but...
Sent from my Nexus One using XDA App

[RECOVERY][UNOFFICIAL]Clockworkmod 3 series

Wiping and backup problems have been fixed in CWM3 > 3.0.0.5. If you had trouble before, try again with ROM Manager. Try to flash the recovery at least twice before giving up, or use an alternate method below.
Ensure that "wipe recovery" option in ROM Manager settings is checked. There is no good reason to not have this checked. It should probably be the default. This will not affect your backups.
3.0.0.8 has fixed the SLCD problems. If you get the black screen with white bars, upgrade to 3.0.0.8.
Koush's official answer as to why you can't flash old .zip files with 3x.
Why you should upgrade to CWM 3 series from 2 series
CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME
ROM Manager won't work with 2 series anymore
support for journaling filesystems. Your data is safer.
pretty orange color
power down from recovery
better partitioning support
may be required for Cyanogenmod in the future. It is not required for the inc as of now.
Why you should not upgrade to CWM3 series
Fear of messing with recovery is not a good excuse
You want to install ROMs from ROM developers that use 2 year old technology and have refused to upgrade their zipping mechanisms (put pressure on them to change their installation scripts)
You like old ROMs that haven't been updated in ages
You are one of the few that the new recoveries don't work on. Ask and someone can probably help you get through this.
WHERE TO GET OLD VERSIONS OF CLOCKWORKMOD:
http://mirror1.kanged.net/recoveries/ - contains img files for all old versions
*http://dougpiston.com/?page_id=85 - contains PB31IMG for flashing through HBOOT, including 2.5.12 and 3.0.0.8. This is the easiest way to manually update recovery.
HOW TO INSTALL IMG FILES
***YOU SHOULD INSTALL THROUGH ROM MANGER IF AT ALL POSSIBLE. TRY TWICE IF IT DOESN'T WORK ON THE FIRST TRY***
Rename the image file you're interested in to recovery.img
OPTION1: ADB
Code:
C:\YOUR_ADB_DIR\>adb shell
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION2: Android Terminal from phone
Copy the recovery.img to the root of your sd card.
Code:
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION3: Use PB31IMG.zip
Download specific recoveries from dougpiston.com
If it is not available elsewhere, oll your own PB31IMG.zip
This is not as hard as you think. Download any recovery PB31IMG.zip, such as the one attached to this thread. Replace the recovery.img in the zip file with the one of the desired CWM recovery. Rename to PB31IMG.zip. Place in root of your SDCARD. Reboot into HBOOT. Install.
What to do if you have trouble with CWM3
Check partitions for errors
Try installing through ROM Manager, or installing through one of the alternate methods listed above
make sure wipe recovery is checked in ROM Manager settings.
make sure you have the latest version of ROM Manager. Check in the market.
How to manually wipe recovery partition.
The utility is present in CM7 builds. I cannot vouch for other ROMs. This can also be done easily through fastboot mechanisms, but afaik fastboot is not available for the incredible because there are not leaked engineering HBOOTs.
This should never need to be done except in extreme circumstances.
Code:
$su
$/system/bin/erase_image recovery
How to get into recovery manually w/out ROM Manager
Shut down your phone. Hold down volume down. Press power, keeping volume down held. This is HBOOT. Scroll down to recovery and push the power button again.
HTC Incredible Amend vs. Edify: How to get old ROMs working with CWMv3
Amend and Edify are scripting languages used to write the installation routines for .zip files, including ROMs. Amend is quite old, from the cupcake days, and as such does not have features necessary for modern ROMs. To simplify development, Koush removed amend support with the advent of CWMv3. He had announced that he was going to do this for months. Nonetheless, some older ROMs that are not actively developed anymore may be desirable, and many of these do not use the more modern edify scripting. There is a thread here on how to easily convert amend scripts to edify using amend2edify: http://forum.xda-developers.com/showthread.php?t=903598.
Other sources for help
IRC
#cyanogenmod or #koush - it is recommended you try the solutions noted in this thread first. Self initiative is important, but seek help if you need it.
Who are the people behind CWM:
koush is the primary developer, slayher and CUViper help adapt it to the incredible, I'm sure many others.
How to build Clockworkmod yourself:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
EDIT 2/27/11: This thread used to contain info regarding a custom build of CWM3006. It is still attached to this thread, but koush has upgraded CWM to 3008 which contains the 3006 fixes and more.
Click to expand...
Click to collapse

Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?

BrettApple said:
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
Click to expand...
Click to collapse
It is really odd, as I can install this version and backup/restore fine, then switch back to 3.0.0.5 and backup locks up consistently.
Its true re: the wiping bugs. It seems there's a lot more noise about the 3 series CWM than the 2 series, although I wonder if its just a lot more people are installing it and not quite understanding how cwm/hboot/cm7 interact. Hard to tease it apart.
I'm talking to koush and trying to get him to recompile it and make it official, regardless.

I tried the above CWR and my recovery screen is all black with white boarder on each sides.

meazz1 said:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
Click to expand...
Click to collapse
Thats quite odd. Try reflashing a working recovery and then back to this one?
What ROM/Radio/Phone (inc slcd or amoled)?
You can also extract the recovery.img out of the zip file and flash it with adb or flash_image.
Let me know please, I'll pull it down if there's consistent problems.

dont pull it booted on my device and ROM.... i'll do some extensive testing and report back

Sounds like this is for AMOLED only
Side note, I looked at an SLCD Incredible today. Noticeable difference in screens. I will say that AMOLED is much brighter and produces better color than SLCD, but SLCD wins hands down in crispness.

ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
right now with 3.0.0.5 if you flash via rom manager without a full wipe... chances are... you'll end up wiping and reinstalling because of fc issues

Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.

lllboredlll said:
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
Click to expand...
Click to collapse
1) I believe if a recovery doesn't show up in the clockworkmod available recoveries, it will not show the proper ROM Manager version. Flash 2.5.0.5 and you'll see the same effect.
2) Looking into this now.
3) That's good to hear! Thank you for testing this! This, coincidentally, is primarily how I use CWM as RM has not been stable/consistent for me in ages.
lllboredlll said:
ok
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
Click to expand...
Click to collapse
I hear what you're saying.
To get the hooks in place, install 3.0.0.5 first via ROM manager, then go into hboot and install this 3.0.0.6. ROM Manager still thinks you have 3005 and backup/etc. works.
I don't mean this to be production quality, but it should help bridge the gap until koush gets a new version out.

shoman24v said:
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
Click to expand...
Click to collapse
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more ***

No problem. RM still shows 3.0.0.5, but that's not a big deal. I still see the latest nightlies available from RM.
And, like I said, I never flash within RM.
Nor do I recommend that.

tdiman said:
EDIT 2/26/11: This information, as hoped, has been deprecated by the release of CWM 3.0.0.7. You should use that one, because CUViper and koush found more bugs re: the communication between ROM Manager and CWM, as well as the fixes noted below.
Click to expand...
Click to collapse
Just in case someone comes along late to the party, please note the above information added to the OP.

Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App

jdmba said:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no. thats not correct - i have restored a bunch without issues.

I updated to 3.0.0.5 a few weeks ago when it came out. All seems to work fine for me except I can't restore to a previous version to flash other Roms (well at least from Rom Manager). Many of the other Roms that are out right now are not Edify.
Sorry if this is the wrong thread to post this in.
I've googled changing the Roms to edify myself, but I'm kind of lazy and switching recoveries seemed like it would be the easier route.

I think koush has been trying to gently encourage app developers for months to change over.
If you search this forum you'll find older versions of cwm.

The version number is reporting fine for me..... and i Love the new look of the recovery. I'm missing the fast scrolling from the previous builds, other then that I love it

Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.

thelunchboxosu said:
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
Click to expand...
Click to collapse
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.

[Q] New to android

I just bought a Motorola Milestone from a friend with android 2.2.2 fryo already installed and running at 800mhz.
i was just wondering since this isnt exactly the latest rom, how easy is it to install a new rom (are they all ready to go, no weird stuff to install after?) and to go back to the current rom just in case.
it also already has been rooted.

it is very easy. does the phone already have an open recovery installed on it?

dont know really.. i have ROM Manager installed, believe this also contains backup thingy like NANdroid?

Well if you have clockwork recovery already installed just put the custom rom file in your sd card and boot in to recovery then wipe, install zip from sd, pick the rom, wait for it to finish then reboot.

since you're asking for a good rom, and for the relative howto, these are my 2c:
1) you should really put in your sdcard a good recovery, if you don't know what version you have at the moment. Download the zip and put it in your sdcard.
http://code.google.com/p/minimod/downloads/detail?name=Minimod%20V0.06.zip
MAKE A FULL NANDROID BACKUP before flashing roms, to get back easily
2) to me, CyanogenMod 7 is the best rom for daily use, since you have a sort of equilibrium between features and performance. I prefere original kabaldan rom, but you could also try OH NO! version. In general, all you have to do is put the zip file you want to flash in sdcard/OpenRecovery/updates, and reboot by holding camera button. You'll get either OpenRecovery menu (wher you'll find "apply update" functions) or standard recovery screen (a warning triangle).
If you get the triangle you have to press volume up and camera button together, and "apply update"; you'll get the aformentioned OpenRecovery menu.
If you want to try CyanogenMod 7, look at this thread: http://forum.xda-developers.com/showthread.php?t=941346 (first post)
KEEP IN MIND that you'll have to put both the rom zip and the gapps zip in the updates fode of your sdcard (that is, these links: https://github.com/downloads/nadlabak/android/update-cm-7.1.2-Milestone-KANG-signed.zip and http://www.multiupload.com/NQAPSYPKIW)
2bis) you should give a look at the milestone development forum; you'll find info about almost every good rom you can use

Scoutme thnx for your reply! yes i was looking at cm7 so i am going to try that. So if i backup and the new rom sucks, i can just go back to the previous one using the backup. Just wanted to know, current rom is actualy really nice and fast, so dont know if cm7 is going to make it slower. Just gonna give it a try then^^
Sent from my Milestone using XDA App

just updated with your link, works perfectly! phone seems fast enough, but does anyone know if its still clocked at 800mhz or is it al back to stock? anyone using this also clocked their phone becouse of getting slower? fyi it was already clocked when i got it