Ok I'm on molten 2.3, can I just install over I also have a back up of my original 2.3.4 it's rooted and supercharged with frozen bloat, which one it's better to flash over? I'm not a noob but still little nervous...thanks ask in advance..
Sent from my DROID X2 using xda premium
Any 234
keep orig bsr
have the new bsr, google apps and beta.cm7 on sd
flash as in the op
3 wipes
Booted to cm7 install orig bsr, install recov but not mode.
Install new bsr over old , install recov and recov mode.
Enjoy .
Hulk0069 said:
Ok I'm on molten 2.3, can I just install over I also have a back up of my original 2.3.4 it's rooted and supercharged with frozen bloat, which one it's better to flash over? I'm not a noob but still little nervous...thanks ask in advance..
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Several people have reported success flashing this over another ROM. But to be on the safe side, I sbf'd to a clean version of 2.3.4. It doesn't take that long and you know you'll get it right the first time.
skwoodwiva said:
Any 234
keep orig bsr
have the new bsr, google apps and beta.cm7 on sd
flash as in the op
3 wipes
Booted to cm7 install orig bsr, install recov but not mode.
Install new bsr over old , install recov and recov mode.
Enjoy .
Click to expand...
Click to collapse
Wait I take the install old bsr back that was alpha only.
So old bsr going to cwr to flash cm but only new bsr booting up to cm7.
maggard5 said:
Several people have reported success flashing this over another ROM. But to be on the safe side, I sbf'd to a clean version of 2.3.4. It doesn't take that long and you know you'll get it right the first time.
Click to expand...
Click to collapse
Yea, i was on Eclipse 2.3.4, and i didn't want to chance it, SBFing back and all was a pain, but worth it, i think. I did Nandroid Eclipse just in case tho...i will miss HDMI, i did find that quite useful.
Everything went fairly smoothly, few hangups restoring Titanium, (system settings restore - hosed nearly everything) had to start over, live and learn.
On a side note, once i got everything up and running smoothly, Smart bench scores were at around 3,300, first thing i tried was music, fired up MixZing, went to the lock screen to check the widget, and BAM, a skip and a pop, seems like old times...so depressing. But i will pick my self up with a cool CM7 theme...make it all better
So maybe I'll wait till they work out the kinks, molten it's pretty smooth, no hdmi here either, and video is choppy, but it'll do for now.....it's still fast, no lag...wish there was molten themes tho for 2.3 when Cm7 gets kinks ironed out maybe I'll try it.
Sent from my DROID X2 using xda premium
I flashed the Alpha over Eclipse and the Beta over the Alpha and everything works great. I guess it just depends. Just follow the rules on flashing. All you need to do is wipe data, cache and dalvik cache and flash like normal the ROM then the Google Apps. Then when you are done, install the patched BSR. Not that difficult.
EDIT: And trust me, there is not very many kinks in this ROM.
Hulk0069 said:
So maybe I'll wait till they work out the kinks, molten it's pretty smooth, no hdmi here either, and video is choppy, but it'll do for now.....it's still fast, no lag...wish there was molten themes tho for 2.3 when Cm7 gets kinks ironed out maybe I'll try it.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Every ROM has it's kinks, but let me tell you - I have tried every ROM for the X2, which includes Molten, Liberty3, Eclipse 1.3 and 2.0.x, and NONE of them have ever ran my X2 as smoothly as CM7. Reason why? There is absolutely no BLUR what-so-ever in it. Molten, Liberty3 and Eclipse all have some sort of BLUR in them. With CM7, Dragonzkiller and company have completely removed it because they rebuilt this from scratch from the original CM7 sources, which are AOSP.
Therefore, I have found that I no longer have to use Zep's V6 scripts to enhance the performance of the X2 with CM7. This just goes to show that BLUR is definitely a resource hog.
You should really give it a try. Just nandroid your Molten install so you can go back to it if you don't like CM7.
CM7 is really the best ROM out there now performance-wise. And, it opens up the road to allow ICS to come to the X2, whether Motorola does it or not.
It's kind of like flipping the bird to Motorola, especially after they lied about unlocking boot loaders. Needless to say, the X2 will be my last Motorola product ever. And, I will steer all other potential Android buyers that I know away from Motorola as well because of this.
Following the exact intrustions given by draginkillrz I think is always a good bet.
DX2-CM7
I flashed over the OTA 2.3.4 and had no problems.
XGrinder911 said:
Following the exact intrustions given by draginkillrz I think is always a good bet.
DX2-CM7
Click to expand...
Click to collapse
I will second that. When the beta came out, I just went ahead and flashed it over the alpha CM7. Things seemed to work pretty good until I tried to install the Swype beta onto my phone. Reading where others had success, I followed their instructions to the letter and it kept force closing on me.
I finally decided to just SBF to 2.3.4 and flash the beta over that. Problem solved AND I've seen even better performance than before. A lot less apps hanging and having to wait on them, etc.
So, listen to the Dragon lest you be smited by the wrath of his fire!
iBolski said:
So, listen to the Dragon lest you be smited by the wrath of his fire!
Click to expand...
Click to collapse
Wrath of fire? haha That was awesome...
Related
Didn't notice this before, but according to http://stats.cyanogenmod.com/ , there are two installs for 'daytona' (codename for Droid X2).
Also, cvpcs recently tweeted "i'll see what i can muster together. need to get some DX and X2 stuff posted".
Good news? Old news?
I didn't know they had even started on the X2, I knew the X1 already had it, or an RC at least.
cvpcs, who I believe ported CM4DX, just recently got the X2, but has been busy with life.
Also, the Droid X is becoming, or already is, an official CM supported device.
Before my brother got his X2, I was trying to get the CM7 build on it, but couldn't find the correct one on their site, this was almost 2 months ago though.
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
drapp said:
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Do tell plz
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
drapp said:
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
Click to expand...
Click to collapse
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
ericerk said:
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
Click to expand...
Click to collapse
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
drapp said:
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Yup yup xDD
---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
If you still have time to give it (X2) back i'd recommend it,Get a Bionic or something or the droid 3, something thats more popular, d3 has cm7 booting same with the bionic, don't lock your self in a crap phone if you don't absolutely have to...
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
2nd init for the x2 was created on GB. I believe our ATRIX ports use 2nd init. Naven and dragon just made them flashable in CWM by including the 2nd init hack in the flash.
drapp said:
Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Click to expand...
Click to collapse
the posted 2nd-INIT in dev section for us works on gb if that is what you are referring to.
About CM7 & 2nd-init
the 2nd init that is used for all motorola devices (except the ATRIX) for cyanogenmod is designed for both froyo and gb. It has a check in there to see if the executable bit exists and figure out what to do from there. that way any motorola device could (in theory) use it. I know that this version of 2nd init works for the X2 and will pretty much be used when it comes to porting over cm7. We're going to have to use GB as our base (not Froyo) simply because of the requirements of our kernel (which we can't change).
About my involvement
now i know that I was original one who was trying to crank out cm7 and that it kinda died out. that doesn't mean that i don't play around with it from time to time. I'm starting from scratch, but if naven and/or cvcps or whomever get it running before I do, more power to them. I have little to no time to work with this, but I know what approach i'm taking this time. It is to simply base it off the ATRIX (obviously) but then work in the 2nd-init and edify scripts that the X uses. I kinda did that the first time, but got too mixed up in all of the details.
I don't want anyone to think that because I'm working on it that any results will arise. I'm merely trying to say that someone is working on it. Just maybe not as fast or with as much time as you guys will like. I want to have CM7, too. But we don't have a team or anything so it takes a lot of work.
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
Here's a link to cvpcs blog entry regarding 2nd-init when he was porting CM to Droid X.
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
2nd-init allows us to have a new init.rc script, not just scripts in general and in reality has no affect on init.d unless the init.rc script is told to do so. Basically 2nd-init kills the init process (and all spawned processes) that uses the stock init.rc and uses a new one which we copy during hijacking the boot process and starts the init process again.
The root directory (where init.rc lies) of our phone is writable, but is reflashed every time the phone boots up, thus erasing any changes we might have made to init.rc (kinda defeats the purpose of having a custom script). This script is the script that gets everything set up during the boot sequence starting roughly around the time the motorola logo first shows up and all through the boot animation. We need to have a custom init.rc to get our phone's environment setup for CM7.
Our problem arises when we have to have the script satisfy both the OS and the kernel. Motorola's kernel expects certain criteria to be fulfilled within the phone to allow it to do it's thing. If these aren't satisfied, the kernel panics and reboots the phone (hence why we get bootloops). We can use logging (a rather tedious, slow, and painful method) of finding out where the kernel panics, and adjust as needed. But we need to have the environment ready for CM7 also, so those changes need to be in there without causing a kernel panic.
"Heavily modified" is a bad way to put it, more like "non-BLUR." If we could get CM7 working we can use the init and build files/setup/etc to allow us to have more ROMs based of AOSP. MIUI is based off of AOSP and in theory if we figure out CM7 we can even have AOSP ourselves. In fact the ATRIX recently got a port of AOSP (albeit buggy, but still).
The link above to cvpcs's blog goes into the details about it. It's really good read.
dragonzkiller said:
The link above to cvpcs's blog goes into the details about it. It's really good read.
Click to expand...
Click to collapse
It is also written in a '2nd init for dummies' fashion. Don't be afraid to read it!
Sent from my DROID X2 using XDA App
I agree this phone is one big piece of poo!
SE7EN- said:
I agree this phone is one big piece of poo!
Click to expand...
Click to collapse
I don't remember seeing anyone in this thread say that. Who are you agreeing with?
So hey all, I am new here so bear with me. I have been on Android for about a year and am finally ready to root and run a rom. Started out with a Samsung Fascinate which got traded for a Droid X and that got replaced with a Droid X2. Having some small issues with the DX2, and since I need to factory reset I figured I would go ahead and try to root and run a rom...
So my question is being a complete noob would I be better with CM7 or Miui. Originally on the DX I looked into Miui and really liked how it looked and really wanted it and did a lot of research on it, but before I could try it I had to send back my DX and they replaced it with a brand new DX2 in the box. Then looking into it I noticed that Miui was not available for the DX2, so I just gave up and stayed put.
Recently reading thru the forums I see Miui is available now for the DX2, but I also was looking into CM7 which also looks really nice. I was wondering would either of them be easier for a noob? (i.e. install and post install customization) I have read up on both not having functional FM radio and HDMI, which are not big deals because I rarely use either... but are there any other big problems with either of these roms that would make a noobie like myself steer clear from them and is one of them faster than the other? I also looked into eclipse and not sure if that is something I should consider. Are there any major issues with eclipse and is it more stable than the other two? Honestly right now I am just trying to figure out where to start. I want to do something, but also want the easiest route so that I do not brick my phone as my wife would probably kill me, haha.
There is just so much info out there, I really don't know where to start. I know you guys probably get these questions all the time, but I could not find a specific thread that talked about just these two (or three) roms specifically for the DX2. I have been trying for the past month or two to research this stuff, and I have learned a lot, but I need a little help to push me in the right direction...
Oh, and if you couldn't guess I am on stock GB 2.3.4 unrooted...
kalojado said:
So hey all, I am new here so bear with me. I have been on Android for about a year and am finally ready to root and run a rom. Started out with a Samsung Fascinate which got traded for a Droid X and that got replaced with a Droid X2. Having some small issues with the DX2, and since I need to factory reset I figured I would go ahead and try to root and run a rom...
So my question is being a complete noob would I be better with CM7 or Miui. Originally on the DX I looked into Miui and really liked how it looked and really wanted it and did a lot of research on it, but before I could try it I had to send back my DX and they replaced it with a brand new DX2 in the box. Then looking into it I noticed that Miui was not available for the DX2, so I just gave up and stayed put.
Recently reading thru the forums I see Miui is available now for the DX2, but I also was looking into CM7 which also looks really nice. I was wondering would either of them be easier for a noob? (i.e. install and post install customization) I have read up on both not having functional FM radio and HDMI, which are not big deals because I rarely use either... but are there any other big problems with either of these roms that would make a noobie like myself steer clear from them and is one of them faster than the other? I also looked into eclipse and not sure if that is something I should consider. Are there any major issues with eclipse and is it more stable than the other two? Honestly right now I am just trying to figure out where to start. I want to do something, but also want the easiest route so that I do not brick my phone as my wife would probably kill me, haha.
There is just so much info out there, I really don't know where to start. I know you guys probably get these questions all the time, but I could not find a specific thread that talked about just these two (or three) roms specifically for the DX2. I have been trying for the past month or two to research this stuff, and I have learned a lot, but I need a little help to push me in the right direction...
Oh, and if you couldn't guess I am on stock GB 2.3.4 unrooted...
Click to expand...
Click to collapse
Eclipse is the most stable. Cm7 and miui are both betas and not everything works.. Cm7 is good for speed, and miui for crazy customization options.
Sent from my DROID X2 using xda premium
Jubomime said:
Eclipse is the most stable. Cm7 and miui are both betas and not everything works.. Cm7 is good for speed, and miui for crazy customization options.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can I ask if you were just starting out and never messed with any roms before, which one would you choose out of the three?
kalojado said:
Can I ask if you were just starting out and never messed with any roms before, which one would you choose out of the three?
Click to expand...
Click to collapse
Eclipse is likely the most stable, with CM7 following closely behind. MIUI is still in alpha. I haven't tried MIUI yet, but I've read people are having problems. For installing, they should all follow the same process.
Woops, accidentally clicked thank on your post. Oh well lol
kalojado said:
Can I ask if you were just starting out and never messed with any roms before, which one would you choose out of the three?
Click to expand...
Click to collapse
Definitely recommend eclipse for starting out.
Sent from my DROID X2 using xda premium
Well Eclipse is currently based on Android 2.3.5, which means if you decided on that ROM, you would have to update to 2.3.5 then flash the ROM. Then if you ever wanted to switch to a different ROM, you would have to go through the process of SBF'ing back to Android 2.3.4 since all other ROMs are 2.3.4 based. However, Eclipse is the most stable as was mentioned already. Now between CM7 and MIUI, both are great ROMs. MIUI has some issues with audio and video in some scenarios but still works well. Flashing ROMs isnt that hard so if you have the time, try them all out. Just have all the files ready to restore your phone back to health in case something goes wrong.
One other thing to think about between Eclipse (which is stable and the upcoming 2.0.4 release is really stable and fast) and CM7/MIUI is HDMI.
Eclipse still can output HDMI since it still has some of the BLUR components in it.
CM7/MIUI are both compiled from AOSP components and have ALL of the BLUR components removed, hence no HDMI.
So, if you use HDMI and it's deal-breaker for you, then Eclipse is definitely the way you want to go. But, stability is also nice thing for Eclipse.
I see the stability of the ROMs as follows with the most stable listed first:
Eclipse 2.0.X
CM7 Beta
MIUI
CM9 (not released yet but it has Ice Cream Sandwich)
I was on Eclipse 2.0.3, then went to CM7 and stayed there for awhile. Then, I got onto the Eclipse beta team and started testing 2.0.4. The latest 2.0.4 is the most stable I've seen Eclipse, after a few minor issues, but that's why were were beta testing it. Definitely, I'm sticking with Eclipse.
One thing I've noticed, no matter how hard you try to leave Eclipse, I'm always noticing that people keep coming back to it. That alone should tell you how great a ROM it really is.
Thanks everyone. Seems like maybe I should try out Eclipse first, which is fine. I do want the most stable rom when it comes to my first time... then if I am feeling adventurous later I can try out the others. I will go do a search and hopefully can find a post that lets me know everything I need to do in one post. Thanks again for all the help, if anyone else wants to chime in, please do, I am open to any and all suggestions!
Go here:
http://www.eclipserom.com/forum/viewtopic.php?f=17&t=46
Motcher has given a step-by-step explanation on how to get Eclipse 2.0.3 up and running. Once you have that, then when Eclipse 2.0.4 goes public, you'll already be set to flash it.
Eclipse 2.0.3 is here -> http://www.eclipserom.com/forum/viewtopic.php?f=17&t=11
Both of these links go to the Eclipse forums where Nitro posts all his releases now.
kalojado said:
Can I ask if you were just starting out and never messed with any roms before, which one would you choose out of the three?
Click to expand...
Click to collapse
kalojado said:
Thanks everyone. Seems like maybe I should try out Eclipse first, which is fine. I do want the most stable rom when it comes to my first time... then if I am feeling adventurous later I can try out the others. I will go do a search and hopefully can find a post that lets me know everything I need to do in one post. Thanks again for all the help, if anyone else wants to chime in, please do, I am open to any and all suggestions!
Click to expand...
Click to collapse
Eclipse is a good choice for your first time. It'll be gentle I promise.
kalojado said:
Thanks everyone. Seems like maybe I should try out Eclipse first, which is fine. I do want the most stable rom when it comes to my first time... then if I am feeling adventurous later I can try out the others. I will go do a search and hopefully can find a post that lets me know everything I need to do in one post. Thanks again for all the help, if anyone else wants to chime in, please do, I am open to any and all suggestions!
Click to expand...
Click to collapse
Lucky for you, motcher created this sticky in the Development forum here,
http://forum.xda-developers.com/showthread.php?t=1391824
[REF]How to go from any 2.3.4 stock/custom rom to any 2.3.5 (412) based custom rom
It has all the instructions you need in one place , it is all very easy also , don't be afraid of bricking your x2
We have this little thing called sbf, as long as you have a computer you will be able to bring you phone back from any "bricked" state if any problems happen.
just stay away from modifying any boot partitions or anything like that. Stick to basics like flashing roms and tweaks/mods/scripts that are found here in the x2 forum and you won't ever hard brick your x2 to the point of no return lol
if you are ever unsure about what exactly a mod/tweak/script/ROM/hack does to your phone then just ask before doing it, trust me tho, sbf is freaking great, so many times I've gotten "bricked" at the Motorola dual core splash screen and a quick sbf flash brings it right back...
And in case you didn't notice, I recommend eclipse enjoy, happy flashing, and welcome
Sent from my DROID X2 using Tapatalk
Thanks so much for the info! I was out searching and wanted to ask if there was a specific link I could get that I could trust, but I didn't want to bother you all as I am sure you get these same questions over and over again. So thank you so much for passing that along... such a huge help and I am gonna attempt it here in a few moments...
Yeah, I have read a lot about sbf'ing and some people still act like I should be worried about bricking my phone, but I have also read other places where people have stated they have yet to see a phone they couldn't get back. So I am gonna try this, and just follow it step by step so I don't screw anything up! Will let you all know how it goes. Again, I can't thank everyone enough for all the great info!!
kalojado said:
Thanks so much for the info! I was out searching and wanted to ask if there was a specific link I could get that I could trust, but I didn't want to bother you all as I am sure you get these same questions over and over again. So thank you so much for passing that along... such a huge help and I am gonna attempt it here in a few moments...
Yeah, I have read a lot about sbf'ing and some people still act like I should be worried about bricking my phone, but I have also read other places where people have stated they have yet to see a phone they couldn't get back. So I am gonna try this, and just follow it step by step so I don't screw anything up! Will let you all know how it goes. Again, I can't thank everyone enough for all the great info!!
Click to expand...
Click to collapse
Yea
I haven't seen anyone truly hard brick an x2
just stay away.from the mounts& storage options in BSR , and I think the only things you should touch in the advanced menu in BSR is wipe dalvik cache and battery stats...don't mess with anything else and you will be just fine brotha
Also, if there is anything you are to "embarrassed" to ask on the forum, then just shoot someone a private message my pm inbox is always open
And yes, when rooted and you are doing hacks and tweaks and such, you always have the risk of something going wrong, but like I said, never seen a truly hard bricked x2 that couldn't be fixed via sbf, ...you really gotta kinda be TRYING to brick for that to happen lol
ashclepdia said:
Yea
I haven't seen anyone truly hard brick an x2
just stay away.from the mounts& storage options in BSR , and I think the only things you should touch in the advanced menu in BSR is wipe dalvik cache and battery stats...don't mess with anything else and you will be just fine brotha
Also, if there is anything you are to "embarrassed" to ask on the forum, then just shoot someone a private message my pm inbox is always open
And yes, when rooted and you are doing hacks and tweaks and such, you always have the risk of something going wrong, but like I said, never seen a truly hard bricked x2 that couldn't be fixed via sbf, ...you really gotta kinda be TRYING to brick for that to happen lol
Click to expand...
Click to collapse
Okay one quick question. On the link you provided the very fist download, RSD lite is not available. When you go to download it you get "Such file does not exist or it has been removed for infringement of copyrights." I went into the eclipse forum and there is mention of it being updated, but that is all I can find. Do you know where else I could get this file?
http://forum.xda-developers.com/showpost.php?p=22117008&postcount=135
Someone else asked same question other day
that link shows my response
Also,
U said you were on stock 2.3.4 right?
you won't need to sbf if you are, just install the 2.3.5 update zip
Then root with zergrush and good to go
Unless you are just getting everything set up for just in case you need to sbf...which is a great idea also
Good luck
ashclepdia said:
http://forum.xda-developers.com/showpost.php?p=22117008&postcount=135
Someone else asked same question other day
that link shows my response
Also,
U said you were on stock 2.3.4 right?
you won't need to sbf if you are, just install the 2.3.5 update zip
Then root with zergrush and good to go
Unless you are just getting everything set up for just in case you need to sbf...which is a great idea also
Good luck
Click to expand...
Click to collapse
Yes, thats exactly what I was doing. I wanted to make sure I had everything just in case something went wrong. Just figured it would be good to have everything all set But thanks again... much appreciation!
Miui is my rom of choice when it's in full release candidate polish, and maybe eventually Ace's Miui4DX2 will get there. In the meantime, there's a battery-eating wakelock issue, app-by-app sound issues (sound sometimes just doesn't work), and some kind of rendering issue that slows Netflix/certain games/MX Video and various other media apps to a 1 frame per minute crawl. There's also an issue where wifi drops out periodically and doesn't reconnect unless you prompt it (or install a service like "Wi Fi Fixer" that toggles it for you).
So until Ace releases a better beta (which could be as soon as tomorrow, or as late as never), I'd count Miui out as a daily driver.
CM7 as a rom is great--not quite as pretty as Miui (and I find Miui eliminates a lot of the sloppiness in pre-ICS Android), but it is rock solid. DZK's build is an almost perfect CM7 build, except it has the same wifi connectivity issue as Ace's Miui. The advantages it offers more than compensate for the annoyance of having to run Wi-fi Fixer and every now and then waiting for wi-fi to reconnect.
I'm running CM7 on my DX2 and am quite happy with it. I'll give Miui another shot if there's another release (and I'm excited to see how DZK's CM9 runs), but CM7 is likely to be the best daily driver for the X2 for at least another month or two
Eclipse is Blur based (so it has the advantage of functional HDMI), but suffers from the slowdowns/choppiness/audio tearing when multitasking we all know Blur brings. Nitro did a good job of cutting Blur's visual crap out, and he built in a few useful scripts.
Eclipse is definitely better than stock, but if you're gonna go through the trouble of rooting and rom-ing, I'd go with CM7. There's also the issue jsgraphicart mentioned about 2.3.5 vs 2.3.4 requiring a couple extra SBFs if you ever want to switch to something else.
DaveRichardson said:
Miui is my rom of choice when it's in full release candidate polish, and maybe eventually Ace's Miui4DX2 will get there. In the meantime, there's a battery-eating wakelock issue, app-by-app sound issues (sound sometimes just doesn't work), and some kind of rendering issue that slows Netflix/certain games/MX Video and various other media apps to a 1 frame per minute crawl. There's also an issue where wifi drops out periodically and doesn't reconnect unless you prompt it (or install a service like "Wi Fi Fixer" that toggles it for you).
So until Ace releases a better beta (which could be as soon as tomorrow, or as late as never), I'd count Miui out as a daily driver.
CM7 as a rom is great--not quite as pretty as Miui (and I find Miui eliminates a lot of the sloppiness in pre-ICS Android), but it is rock solid. DZK's build is an almost perfect CM7 build, except it has the same wifi connectivity issue as Ace's Miui. The advantages it offers more than compensate for the annoyance of having to run Wi-fi Fixer and every now and then waiting for wi-fi to reconnect.
I'm running CM7 on my DX2 and am quite happy with it. I'll give Miui another shot if there's another release (and I'm excited to see how DZK's CM9 runs), but CM7 is likely to be the best daily driver for the X2 for at least another month or two
Eclipse is Blur based (so it has the advantage of functional HDMI), but suffers from the slowdowns/choppiness/audio tearing when multitasking we all know Blur brings. Nitro did a good job of cutting Blur's visual crap out, and he built in a few useful scripts.
Eclipse is definitely better than stock, but if you're gonna go through the trouble of rooting and rom-ing, I'd go with CM7. There's also the issue jsgraphicart mentioned about 2.3.5 vs 2.3.4 requiring a couple extra SBFs if you ever want to switch to something else.
Click to expand...
Click to collapse
Well hrmm, now you got me thinking about CM7 again, lol. I am in the process of downloading the Eclipse files and maybe I will look into CM7 some more before I proceed. Honestly, I am not at all concerned with the HDMI issue, as I rarely use it... but with that being said can you tell me any more issues with CM7 that would turn off a user from making it their daily rom? if no HDMI is the only issue, that is not a deal breaker for me...
kalojado said:
Well hrmm, now you got me thinking about CM7 again, lol. I am in the process of downloading the Eclipse files and maybe I will look into CM7 some more before I proceed. Honestly, I am not at all concerned with the HDMI issue, as I rarely use it... but with that being said can you tell me any more issues with CM7 that would turn off a user from making it their daily rom? if no HDMI is the only issue, that is not a deal breaker for me...
Click to expand...
Click to collapse
I had issues with apps sometimes hanging and having to kill them. Also, Super User would sometimes forget an app already had the permissions to run as root. Sometimes, I'd have to go into the application manager and tell it to stop the application and try again and then it would get the SU permissions.
With Eclipse, I've have never had this problem. Again, it just shows how Eclipse is much more stable.
As it is, I don't know how much farther Dragonzkiller will stick with CM7 since he's working on CM9 right now. He's been so busy trying to get CM9 out that any more development/enhancing of CM7 and curing the SU and hanging process issues seems to have stopped at this point. But, not pointing the blame at DKZ as he's one busy dude with CM9.
However, Nitro is constantly busy working on Eclipse and not just for the X2. He also does it for the Bionic, RAZR, Galaxy Nexus, and Droid Charge. I don't know how he does it!
Great points. Thanks for the info. I tried to thank your post, but being new I did not know I was limited to 8 thanks per day, lol. But I wanted to let you know I appreciated the feedback!
I rooted my droid x2 when i first got it, then i realized im too much of a hax noob to mess with this stuff... or atleast I feel that way... I don't know what roms are worth a ****, and i feel like everything would just be better if i could go back to the start and just get auto updates from verizon. Is there a way to unroot the phone so i can just get autoupdates? Is there an easy way to just get an up to date version of the software onto my phone? I know I am supposed to search and all, but ive searched and I can't find anything that completely answers my questions. Any help would be greatly appreciated, if someone can help me just get the updated stock software version onto my phone i would be forever indebted to you.
Cyanogenmod 7. Dzk.
whoa look at that....
So if i download Cyanogenmod 7 is it going to be all bugged out and mess up all the time and run slow and just be all around ****? Or will I just be able to roll with it?
Okay, so check it out, Since you seem to be kind of stressing out The best thing for you to do is to Use this thread http://forum.xda-developers.com/showthread.php?t=1313103 And go back to a 2.3.5 kernel, Then install the ROM eclipse 2.1 think that's a great ROM to get started on and get comfortable. Just take the time to read all instructions Carefully before you do anything. No matter what happens you can typically bring your phone back to life. Cool?
Sent using XDA app from my abandoned DX2 running CM7. In dragonzkiller we trust ;p
joeyforc said:
I rooted my droid x2 when i first got it, then i realized im too much of a hax noob to mess with this stuff... or atleast I feel that way... I don't know what roms are worth a ****, and i feel like everything would just be better if i could go back to the start and just get auto updates from verizon. Is there a way to unroot the phone so i can just get autoupdates? Is there an easy way to just get an up to date version of the software onto my phone? I know I am supposed to search and all, but ive searched and I can't find anything that completely answers my questions. Any help would be greatly appreciated, if someone can help me just get the updated stock software version onto my phone i would be forever indebted to you.
Click to expand...
Click to collapse
To address your questions...
ROMS: Right now, the best custom ROMs to flash are Eclipse and CM7. Both are excellent. In my experience, I have found Eclipse to be a bit more stable. CM7 does have some bugs, but not everyone has experienced them. Eclipse will give you HDMI access, whereas CM7 will not. CM7 has "theme chooser" which allows you to theme your phone with great ease, whereas Eclipse themes need to be flashed. Personally, I don't think you can go wrong with either. They are both solid, fantastic ROMs to run.
Unroot/SBF'ing: Moon Shadow made a phenomenal step-by-step post of how to get back to factory settings. It provides all the directions, and even includes the files you need to download in order to complete the factory reset. Follow that post and you'll be back to factory in no time, if that's what you decide you want. You'll find that thread HERE.
Hope this helps!
alright, thanks this is exactly what i needed, I am flashing back to 2.3.4 and im thinking about trying out the cyanogen7 mod. but now that im flashed back to 2.3.4 (or will be soon) will it be like i never rooted the phone in the first place and i will just be able to get auto updates from verizon or what? I mean Im not a complete noob at doing stuff on a computer, are the mods actually worth the trouble and risk or is it more just an option to take up if you are going to be constantly messing with your phone?
Yes they are worth the trouble. And yes it will be back to factory if you flash back to 2.3.4. If you use a custom ROM for a week then go back to the stock ROM You will want to beat your head against the wall because it's such crap in comparison.
Sent using XDA app from my abandoned DX2 running CM7. In dragonzkiller we trust ;p
Alright, if thats the case, than In dragonKiller I trust
Try cm7 1st as it will only flash to 234 leak. Be sure to nandroid BU your stock after you're rooted and bootstraped. This is the BU you will restore to after you try cm and then want to Upgrade to 235 for eclipse.
Get me? No need to sbf between cm7 and eclipse if you save your stock blur BU.
Ohschit said:
....back to the stock ROM You will want to beat your head against the wall because it's such crap in comparison.
Click to expand...
Click to collapse
Hahaha +1. That's a great way to say it.
Sent from my MB870 using XDA
don't stress brotha
flash any ROM you would like
especially if you aren't worried about wiping data and downloading all
your apps again and such
as long as you stick to what's inn this forum you can always just sbf to get back to stock
(also, just being rooted alone wont stop you from being able to take an OTA update pushed by Verizon, you will only have issues if you removed bloat apps or did tweaks or something)
and don't be afraid to private message me, my inbox is always open to help with any questions (just ask a few users I got on their way recently with roms and tweaks and such)
above all, relax read, have fun happy flashing!
(if you couldn't tell, I recommend eclipse, stable, runs like a champ, has hdmi, if you use hdmi trust me on eclipse )
Sent from my DROID X2 using Tapatalk
---------- Post added at 09:12 AM ---------- Previous post was at 09:07 AM ----------
also just wanna add
I've never seen a true hard bricked Droid x2
(milestone x2 may be a different story, but we never heard from those users again)
so as long as you have Droidx2 sbf is the most amazing thing ever, it's great bringing your phone back from the dead
(nandroid is also your best friend, always nandroid backup before doing mods or tweaks, cuz if it's something you don't like, you can restore the backup you made prior to doing such mod/tweaks and BOOM, you are right back to where you were! NANDROID- LEARN IT, LOVE IT LIVE IT
)
ashclepdia said:
also just wanna add
I've never seen a true hard bricked Droid x2
(milestone x2 may be a different story, but we never heard from those users again)
Click to expand...
Click to collapse
Sorry but that is hilarious to me...
Sent from my DROID X2 using xda premium
Help a noob out? I have a virgin DX2 - never rooted - freshly updated to 2.3.5 (was in the soak) - and I'm finally ready to root it and try out a ROM. I've been lurking here for a week or so reading & trying to learn all I can about the process - and I think I'm ready to give it a shot.
Obviously Step 1 is to SBF back to 2.3.4 so I can get rooted, but after that is where I'm running into some indecision. I can't decide if I want to go straight to CM7 from there - or follow the instructions to keep root, SBF back to 2.3.5 and install Eclipse 2.2.
I know both ROMs have their loyal followers and I'm sure either would be a big improvement over stock Blur... and I know it's easy enough to try BOTH of them once I get the hang of all this... but I'd still appreciate some advice about which to try first.
For those of you who've tried both, which do you prefer? What are the pros & cons of each?
Thanks!
TheRaven65 said:
I know both ROMs have their loyal followers and I'm sure either would be a big improvement over stock Blur... and I know it's easy enough to try BOTH of them once I get the hang of all this... but I'd still appreciate some advice about which to try first.
For those of you who've tried both, which do you prefer? What are the pros & cons of each?
Thanks!
Click to expand...
Click to collapse
I'm guessing you've seen this thread? http://forum.xda-developers.com/showthread.php?t=1632111
Seems to center around Eclipse and CM7 mostly. Eclipse can be a bit more polished in my estimation, mostly due to HDMI, FM radio, less buggy, you know, all the bells and whistles working. For the most part, either way you go you'll be fine.
Currently I have myself and my wife on CM7, we both like it. No real issues to speak of.
I personally perfer CM7RC1 its a solid daily driver very minor issues and I never get bored with it. Here's my overview of both ROMs.
CM7RC1
Pros:
Extremely Smooth.
Lots Of Mods/Tweaks.
Endless Customization.
Gingerbread 2.37
Theme Engine.
Wifi Tethering
Fully AOSP.
Toggles.
Cons:
HDMI Mirroring Is Unsupported.
FM Radio Is Unsupported.
Bugs:
Data Triangle. (Fixed By Reboot, *228)
Battery Exclamation. (Fixed By Reboot)
Some Experience Wifi Connecting Issues. (Fixed By Manual Connect)
Eclipse 2.2
Very Smooth.
Few Mods/Tweaks.
Limited Customization.
Gingerbread 2.35.
Flashable Themes.
AOSP/BLUR Hybrid.
Toggles.
Cons:
Lack Of Customization.
Is Only Gingerbread 2.35.
No Tethering.
Bugs:
Some Experience Wifi Resetting. (No Fix ATM)
Sent from my MB870 using xda premium
I have tried out every x2 rom under the sun and as of right now I think your best bet is cm7. I would recommend running the cm7 mash up script, along with the dual core script, because with both of these the res is flawless.
but of course, I think you should try both of them out because it is personal preference. And if we get cm9 here soon then we will all be happy little cracked out, flashed up, ics'd whores with everything we can dream of for the x2, with some extra feta cheese.
Sent from my MB870 using XDA
S3AL3DF4T3 said:
I personally perfer CM7 its a solid daily driver very minor issues and I never get bored with it. Here's my overview of both ROMs.
CM7
Pros:
Extremely Smooth.
Lots Of Mods/Tweaks.
Endless Customization.
Gingerbread 2.37
Theme Engine.
Wifi Tethering
Fully AOSP.
Toggles.
Cons:
HDMI Mirroring Is Unsupported.
FM Radio Is Unsupported.
Bugs:
Data Triangle. (Fixed By Reboot, *228)
Battery Exclamation. (Fixed By Reboot)
Some Experience Wifi Connecting Issues. (Fixed By Manual Connect)
Eclipse 2.2
Very Smooth.
Few Mods/Tweaks.
Limited Customization.
Gingerbread 2.35.
Flashable Themes.
AOSP/BLUR Hybrid.
Toggles.
Cons:
Lack Of Customization.
Is Only Gingerbread 2.35.
No Tethering.
Bugs:
Some Experience Wifi Resetting. (No Fix ATM)
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
This is a fair evaluation of both ROMs but really it all boils down to personal preference and things like if you need HDMI and stuff like that...I personally never use HDMI or the FM radio...but still liked eclipse and that's what I have on my wife's phone albeit its 2.1...I am sure when CM9 comes out she will like to try it...in short flash them both run them for a week or so and see which one you like and go from there
Sent from my MB870 using xda premium
HitMyKush said:
I have tried out every x2 rom under the sun and as of right now I think your best bet is cm7. I would recommend running the cm7 mash up script, along with the dual core script, because with both of these the res is flawless.
but of course, I think you should try both of them out because it is personal preference. And if we get cm9 here soon then we will all be happy little cracked out, flashed up, ics'd whores with everything we can dream of for the x2, with some extra feta cheese.
Sent from my MB870 using XDA
Click to expand...
Click to collapse
The end of your post made my day...
Sent from my MB870 using xda premium
Just a caution on CM7; I haven't tried the latest release but on the first release the camcorder continuous auto-focus didn't function. It seemed to focus once when you press the shutter button and remain fixed, and sometimes that focus was in error itself. Not a lot of people seem to care about that but my phone has the heavy responsibility of archiving my sons' most important memories for them to look back on when they are older, so I just went back to stock rom. Other than that, CM7 seemed great.
I use CM7RC1 Dual Core Script, Build Prop Mashup, 8 Touch Point Mod, Cron Scheduler, Beats Audio, 3 CDMA Mods. My phone is blazing fast!
Sent from my MB870 using xda premium
In my experience the beats audio hack ruined my sound quality. Also the dual core script......Our 2nd core boots up automatically when there's a demand for more memory. Dragonzkiller even stated this is the dual core script thread. Keeping both on at all times pretty much only drains your battery faster. Only difference I noticed with it was the home screen animations were a little snappier. Wasn't enough change in performance for the lack of battery IMHO. Just a few things if you go the CM7 route. Never tried Eclipse so I can't help you there.
Sent from my stupid smartphone
Why do these keep popping up...the search bar is definitely not be used...
Anyways...Eclipse is literally a hair slower than cm7 but it is worlds more stable. Wifi on Eclipse far better than cm7's. Cm7 has some SU issues but they can be fixed by installing Super SU from the market and getting rid of the normal SU app.
Tethering is easier on cm7 is strong -- heat is something you'll have to worry about. I've tethered on Eclipse through the use of a Market app so a little more work must be done there.
Downside to Eclipse is that you must go to 2.3.5 to use it whereas Cm7 is 2.3.4. Battery life on Eclipse is better for me. I've had serious computer trouble this past month and have had to do some research for papers on my phone! With the brightness on full, Gmusic/Pandora/power amp going and internet on my battery would last ~6-9 hours.
I should also mention that I have the Second Core Script going and my battery life took a very small. Not backbreaking but noticeable.
Not going to lie ; your phone will heat up slightly more regardless of the rom you're on when you use the script
Personally I enjoy Eclipse much more than cm7. Blue is my favorite color
Come over to the dark side...
Hmm haven't ran into any sound issues yet. As far as the dual core script I understand the core will activate on demand. The thing is this only happens when the CPU becomes so over tasked by processes it create a short lag before kicking in. This script makes that laggy transition disappear. I would only recommend this script for people with the extended battery like me tho.
Sent from my MB870 using xda premium
S3AL3DF4T3 said:
The thing is this only happens when the CPU becomes so over tasked by processes it create a short lag before kicking in. This script makes that laggy transition disappear.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Obviously, lol... no "lag" or time needed to boot because its already always on...
Did you use the script editor in ROM toolbox to apply it, sealedfate? If so do you check apply on boot, or do you only use it when you see fit?
Sent from my stupid smartphone
If you have a X2 now I would say you have to try them both. Run one for a couple of weeks do a nano back up and then try the other for a couple of weeks. Then you can decide which you like better. Or you can do like I did and just keep going back and forth every few weeks because you love them both
I have the script in system/ect/init.d so it applies on boot. Helps a hell of a lot with 3D games.
Sent from my MB870 using xda premium
thelowend said:
Why do these keep popping up...the search bar is definitely not be used...
Click to expand...
Click to collapse
Actually, like I said in my first post, I'm been doing nothing but searching and reading on here for the past week or so. Eclipse 2.2 just dropped a week ago, so I was looking for fresh opinions from people who had tried CM7 and that version specifically.
I appreciate all the helpful comments from everyone though. I think I'll do like a few of you suggested and try them both eventually... starting with CM7.
Hopefully we can all add CM9 to the list of ROMs to try very soon!
Dragonzkiller is currently working on the CM9 release for DX2! Keep up to date on his twitter page
www.twitter.com/dragonzkiller
Sent from my stupid smartphone
RoyJ said:
Dragonzkiller is currently working on the CM9 release for DX2! Keep up to date on his twitter page
Sent from my stupid smartphone
Click to expand...
Click to collapse
Yep! I've been following his Twitter feed and the "CM9DX2 anticipation" thread on here. Can't wait to see how it goes. Sounds like he's REAL close!
Success! Following Moon Shadow's instructions to the letter, I successfully SBF'd back to 2.3.4, rooted, and installed CM7 without any problems whatsoever. CM7 is up and running! Just need to get my apps reinstalled and I'll be good to go. Man... you guys weren't kidding. The phone is SOOOO much faster/smoother now, it's not even funny. Should have done this a long time ago.
Thanks everyone!
OK, it appears that I spoke too soon. I realized soon after that the Google apps did not get loaded on my phone (Gmail, Maps, Nav, YouTube, etc.), but some of the other apps in that same ZIP file DID get installed (Talk). Also, my old background pic was still on the phone.
I was able to download/install the missing Google apps without any problem and they all work perfectly (including Nav from the car dock) - and everything else has been running flawlessly. The phone is very fast & smooth... no bugs... not a single force close or reboot yet after fairly heavy use for the last couple of days.
So... obviously something didn't go perfectly with my install, but as far as I can tell, everything is fine with the phone. How can I tell if I'm missing anything else? Should I just keep what I have or SBF back to 2.3.4 and start over again? I'm perfectly happy with it right now - but maybe I don't know what I'm missing.
TheRaven65 said:
OK, it appears that I spoke too soon. I realized soon after that the Google apps did not get loaded on my phone (Gmail, Maps, Nav, YouTube, etc.), but some of the other apps in that same ZIP file DID get installed (Talk). Also, my old background pic was still on the phone.
I was able to download/install the missing Google apps without any problem and they all work perfectly (including Nav from the car dock) - and everything else has been running flawlessly. The phone is very fast & smooth... no bugs... not a single force close or reboot yet after fairly heavy use for the last couple of days.
So... obviously something didn't go perfectly with my install, but as far as I can tell, everything is fine with the phone. How can I tell if I'm missing anything else? Should I just keep what I have or SBF back to 2.3.4 and start over again? I'm perfectly happy with it right now - but maybe I don't know what I'm missing.
Click to expand...
Click to collapse
Not sure how anyone might be able to tell you what you might be missing on your phone. It is pretty basic what you get, not a lot of bells and whistles put in by default.
Not aware of a comprehensive list of what you should have exactly.
Sent from my MB870 using XDA
I received my replacement X2 yesterday due to a failed "back" button. My original was running stock rooted 2.3.4 with the battery fix and a few bloat apk's removed. My new phone came with 2.3.5 installed.
I'd like to speed things up on the phone, but absolutely have to have BT, WIFI, camera, and video camera. I also need to fix this battery % issue. The phone needs to be rock solid without the lousy stock lag I experienced with my old phone.
Suggestions?
Sent from my DROID X2 using Tapatalk 2
royta said:
I received my replacement X2 yesterday due to a failed "back" button. My original was running stock rooted 2.3.4 with the battery fix and a few bloat apk's removed. My new phone came with 2.3.5 installed.
I'd like to speed things up on the phone, but absolutely have to have BT, WIFI, camera, and video camera. I also need to fix this battery % issue. The phone needs to be rock solid without the lousy stock lag I experienced with my old phone.
Suggestions?
Sent from my DROID X2 using Tapatalk 2
Click to expand...
Click to collapse
if you wanna stay stock i suggest deodexing the phone and frezzing or removing the bloated apps you dont use. if you want another rom that has all those capabilities your best bet would be to stick with a gingerbread based rom eclipse, cm7. cant tell you which is faster cause i havent used either of them
Try Eclipse 2.3 by Nitro. It has perfect stability, good battery life, and the speed is much better than stock. It is the only DX2 Rom that is completely finished with virtually no bugs. It has been around for awhile, so if you have any issues with installing it odds are someone here can help you out.
CM7 is stupid fast, but the wifi is sort of glitchy. Eclipse is slightly slower than CM7 but much, much more stable. Both are considerably faster than stock.
I've ran Eclipse for about 4 months, and CM7 for over a year. I prefer CM7 because I like the speed and can deal with the bugs, but it's all preference.
If you've never installed a Rom before, read up on the stickied posts and familiarize yourself with the process before you do anything. Pay special attention to the different bootstrap recoveries and sbfing. And ALWAYS follow the instructions for installing them EXACTLY as they are written unless otherwise told
Here's the link for Eclipse http://forum.xda-developers.com/showthread.php?t=1198857
Note that Eclipse uses 2.3.5 and CM7 uses 2.3.4
Also, 2.3.5 fixed the majority of battery issues that were present on 2.3.4
If you need your phone for work and school like I do, stay away from any Roms not using Gingerbread. They are all very unstable and buggy if you use your phone a lot.
Thanks for the suggestion. I installed Eclipse 2.3 this afternoon after work and I really like it so far. I didn't like the sd flip flop so I found the script to change it back to stock. I also became very accustomed to the stock calendar. Do you know if there's a way to install that?
I'm currently setting everything up and reinstalling all my apps.
Sent from my DROID X2 using Tapatalk 2
Ha yea I hated the sd card flip flop, changing it back was always the first thing I did after flashing lol
I know that on the Eclipse OP there is a download for what it calls "non-inverted calender". I don't really ever use my calender app, so I don't know whether or not that means the stock calender or something different. If you want to give it a try, it is not flashable so you simply have to install it using the normal .apk file method (download, put on sd-card, install from inside whatever file manager you use; I use Astro).
Always make a nandroid backup before though, just in case you don't like it or something goes wrong you can always revert back to how it was at the time of the backup.
Actually, it's not the calendar itself, it's the widget. I really like the stock blur calendar widget because it would show three events instead of just one. Very handy.
Does anybody know what I need to do to be able to have the stock calendar widget?
Sent from my DROID X2 using Tapatalk 2
royta said:
Actually, it's not the calendar itself, it's the widget. I really like the stock blur calendar widget because it would show three events instead of just one. Very handy.
Does anybody know what I need to do to be able to have the stock calendar widget?
Sent from my DROID X2 using Tapatalk 2
Click to expand...
Click to collapse
The deodexed zip of stock apps for your device but they will only work on the version of android they were made for. 2.3.4 stock apps will only work on Ginger bread roms
Sent from my Milestone X2 using xda app-developers app