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?
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...
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!
First of all I would like to apologize if you have heard these questions a thousand times before, but I have done a fair amount of reading and haven't gotten enough concrete answers to be confident enough to continue.
I just got up the courage to root my Fascinate after over a year of having it by following droidstyle's excellent guide. It was very painless and worked first shot, so no worries there. Now I'm at the point of what to do next... I have already frozen the bloatware and looked into some 'root-friendly' apps but I'm not sure where to go from here. I think I've decided I want to get the most out of this thing as I'm not due for an upgrade for (what seems like) a long time. I'm under the impression that installing a good ICS rom is the way to go but I just have a few noob questions before I continue.
1) From what I have been reading Glitched AOKP ICS is the best rom to use currently on the Fascinate, correct? Also quick question, regarding the link to download it... is the current version the build 34 one or the milestone 5 one at the top?
2) Rooting my phone initially didn't erase any of my apps or data. What will installing an ICS rom erase, if anything? I will make backups of course, but I'm just wondering what to expect. Will the 'bloatware' apps still be there or will installing ICS install new system apps?
3) What market apps should I consider 'must haves' to tweak stuff? I already bought setcpu but haven't invested in anything else yet.
4) I plan to follow section 4 of droidstyle's guide but need clarification... even though I have rooted stock 2.3, I should still follow all steps right?
Thank you for listening to my noob questions and thanks to anyone who can offer advice. I have been building and working on computers for years but this cell phone hacking stuff is all new to me (obviously).
Crawshayi said:
First of all I would like to apologize if you have heard these questions a thousand times before, but I have done a fair amount of reading and haven't gotten enough concrete answers to be confident enough to continue.
I just got up the courage to root my Fascinate after over a year of having it by following droidstyle's excellent guide. It was very painless and worked first shot, so no worries there. Now I'm at the point of what to do next... I have already frozen the bloatware and looked into some 'root-friendly' apps but I'm not sure where to go from here. I think I've decided I want to get the most out of this thing as I'm not due for an upgrade for (what seems like) a long time. I'm under the impression that installing a good ICS rom is the way to go but I just have a few noob questions before I continue.
1) From what I have been reading Glitched AOKP ICS is the best rom to use currently on the Fascinate, correct? Also quick question, regarding the link to download it... is the current version the build 34 one or the milestone 5 one at the top?
2) Rooting my phone initially didn't erase any of my apps or data. What will installing an ICS rom erase, if anything? I will make backups of course, but I'm just wondering what to expect. Will the 'bloatware' apps still be there or will installing ICS install new system apps?
3) What market apps should I consider 'must haves' to tweak stuff? I already bought setcpu but haven't invested in anything else yet.
4) I plan to follow section 4 of droidstyle's guide but need clarification... even though I have rooted stock 2.3, I should still follow all steps right?
Thank you for listening to my noob questions and thanks to anyone who can offer advice. I have been building and working on computers for years but this cell phone hacking stuff is all new to me (obviously).
Click to expand...
Click to collapse
1) M5 is newest. Get glitched build off of the exynos server.
2) Complete wipe. A desktop equivalent would be formatting your hard drive with Windows Vista installed and doing a fresh install of windows 7.
Backup all data and contacts locally or on the cloud. Do NOT use Verizon to backup your contact data. Use Google or a local backup instead.
No bloatware will be present since custom roms do not come from the carrier.
3) NSTools. Maybe Root Explorer or wi-fi tether for google
4) Just follow the guide. Rooting doesn't have much to do with recovery and intalling ics and such.
Not to knock ICS, because I love AOKP, but you could also consider working your way there over time. I had a lot of fun playing with different Touchwiz ROMs like SC3 and TSM Res. You may even find one along the way that you want to stick with for a while. At the very least, you'll learn to get where a complete data wipe doesn't even slow you down.
There's so much good stuff still available for this phone. My phone is sheer perfections right now, but I still have plans to try out GeeWiz and MIUI.
Everyone knows the current destination is Glitched AOKP, but the fun is in the journey.
I agree. I would download everything rom,kernel, and app you can find for the phone between here and rootzwiki, just in case links go dead. Tsm res and awesome sauce are two very good roms that I had a ton of fun with. They are more forgiving to the new user as far as making mistakes goes. Couple of things to know before you continue are that you can use the three finger method to get into recovery on touchwiz roms but not the ics roms(must enter recovery through power off menu). You also cant just flash back and forth from touchwiz roms and cm7 or ics roms, as you have to follow certain steps
Sent from my SCH-I500 using Tapatalk
Well I was planning on jumping right into ICS as it looks amazing and I don't think I want to wait... however I wouldn't be opposed to the idea of trying different roms later on down the road. Is it going to be a pain to go backwards from ICS, or just flash like usual? Also, to those that have tried most of the 'good' roms, what would you consider your top 3 non-ICS?
Also on the subject of backing up my apps... I have been using Mybackup as it seems the most simplistic to use and reliable. Will my apps be exactly as they were when I backed them up (after switching to ICS) or is it just better to re-download what I need and configure them again?
I hate to spam some more questions but I figure since I already am... just a few more...
I haven't really messed with Setcpu that much, but is it bad to have it at 100/1000 or should I keep the max lower than that? And last one... what's the best wifi tether to use so Verizon won't send their goons after me? Is the USB tether from clockwork mod any good?
Thanks to all of you for your input. I think I'll be attempting to flash to ICS tomorrow night and hopefully all goes well.
You can go from touchwiz roms to isc roms by flashing but you need to do a lot more using the computer to go backwards. It will make more sense once you have a better understanding. Use titanium backup to backup your apps. If you really dont have any then just redownload them. If you are on the touchwiz roms you can use setcpu, but for ics roms you are going to be using an app called nstools or from control (built into settings section of rom). Again, more of this will make sense later down the road that is why I figured it would be better to start on a from like tsm Res or awesome sauslce
Sent from my SCH-I500 using Tapatalk
Well I'm still on the fence here on what to do. I really want to run ICS but with all the little glitches I've read about I think maybe I'll try some of the better GB roms first... I think TSM Res looks top for me with the features, but I might try more than just 1. I've heard not to restore data backups when going ICS... does this apply to GB roms as well? Should I also switch the radio or is what I have the same as the GB one? Thanks
Crawshayi said:
Well I'm still on the fence here on what to do. I really want to run ICS but with all the little glitches I've read about I think maybe I'll try some of the better GB roms first... I think TSM Res looks top for me with the features, but I might try more than just 1. I've heard not to restore data backups when going ICS... does this apply to GB roms as well? Should I also switch the radio or is what I have the same as the GB one? Thanks
Click to expand...
Click to collapse
AOKP milestone 5. You WILL thank me for it. Make sure its Steve's glitchy (the kernel of course) build.
Sent from my SCH-I500 using xda premium
mezster said:
AOKP milestone 5. You WILL thank me for it. Make sure its Steve's glitchy (the kernel of course) build.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
You don't like the one they just released a few days ago?
Crawshayi said:
You don't like the one they just released a few days ago?
Click to expand...
Click to collapse
That is a nightly and has a minor bug where apps on SD card force close. No biggie for more experienced users who know its a nightly and can deal. Nightlies are bleeding edge releases and as such can contain a bug or two. Milestones are stable releases to be used as a reliable daily driver if one is needed (some do). I recommend the m5 release since it is a milestone and you are new to this. I also want to see you have the best experience possible.
Sent from my SCH-I500 using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I'm in a similar spot. I put CM7 on my wife's phone a while ago, but she has downloaded so much crap on it it's running like garbage and crashing.
Does the AOKP M5 have any bugs I should be aware of? As long as it's working well and everything is working (WiFi, Camera, MMS, etc), she'll be fine with it as a daily driver.
Two other questions I have.
Where can I get the correct glitchy Kernel?
Do I just need to download the ROM and kernel, wipe data/cache, then flash the ROM then kernel, then gapps (in that order) in Clockwork Recovery? Anything else?
She really likes the ICS stuff I've been showing her on my Rezound, especially the speech to text typing.
Thanks for your feedback.
EDIT
Added Information:
Just to make sure my i's are dotted and my t's are crossed--
Build for Verizon Fascinate:
http://forum.aokp.co/page/releases/_/milestone-5-r20
fascinatemtd Samsung Fascinate
Glitch Kernel:
http://forum.xda-developers.com/showthread.php?t=1459475
Are those right?
EDIT 2
Should I update radios as well? (Assuming yes since going to AOKP from CM7). Which ones should I do? Again, is this a simple flash in CWR? What's the install sequence?
Thanks.
EtherBoo said:
I'm in a similar spot. I put CM7 on my wife's phone a while ago, but she has downloaded so much crap on it it's running like garbage and crashing.
Does the AOKP M5 have any bugs I should be aware of? As long as it's working well and everything is working (WiFi, Camera, MMS, etc), she'll be fine with it as a daily driver.
Two other questions I have.
Where can I get the correct glitchy Kernel?
Do I just need to download the ROM and kernel, wipe data/cache, then flash the ROM then kernel, then gapps (in that order) in Clockwork Recovery? Anything else?
She really likes the ICS stuff I've been showing her on my Rezound, especially the speech to text typing.
Thanks for your feedback.
EDIT
Added Information:
Just to make sure my i's are dotted and my t's are crossed--
Build for Verizon Fascinate:
http://forum.aokp.co/page/releases/_/milestone-5-r20
fascinatemtd Samsung Fascinate
Glitch Kernel:
http://forum.xda-developers.com/showthread.php?t=1459475
Are those right?
EDIT 2
Should I update radios as well? (Assuming yes since going to AOKP from CM7). Which ones should I do? Again, is this a simple flash in CWR? What's the install sequence?
Thanks.
Click to expand...
Click to collapse
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
jbreakfield said:
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
Click to expand...
Click to collapse
Might sound like a cheesy question, but what radios are you running?
Thanks for your help.
jbreakfield said:
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
Click to expand...
Click to collapse
QFT.
Get the Glitched build as it has fixes, extra available RAM, and much more not available in the AOKP official build.
Wifi, cam, and MMS all work fine. I can't honestly think of anything not working off the top of my head. NovaLauncher (Regular is free, Prime is $4 and well worth it for gestures) is recommended at this point since Apex has gotten a little slow.
Radio is recommended to be EH03 though I think ec09 and anything newer than eh03 work fine. I am running EH03 and no complaints.
I think I remember reading something about torch not working in ICS... is that the type of app that turns on the LED? Believe it or not I use that a lot and it would be a pain if it didn't work when I switch.
Also, is there any way to check what radio you're currently using before flashing? Tried looking that up but couldn't find it
Ah yes...torch doesn't work but you can use the tiny flashlight app to turn on the flash and achieve the same functionality.
Sent from my SCH-I500 using xda premium
bobloblaw1 said:
Ah yes...torch doesn't work but you can use the tiny flashlight app to turn on the flash and achieve the same functionality.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
The Tiny Flashlight + LED app? That's actually what I'm using now and if that works then I'm all set... I thought when people said 'torch' they just meant any app that turns on the LED
I flashed and ran into 1 problem. I had to flash Team Hacksungs Build 2 ROM first. Flashing glitched put me in an endless boot. Then I couldn't boot to recovery. I really was flipping out.
I had to Odin a new recovery in, wipe, then flash Team Hacksungs Build 2 ROM. For some reason, it booted into AOKP (?) then. I went back to recovery, wiped, reflashed AOKP and got it working.
I haven't searched yet, but anyone know where I can change the boot screen? It's really not a "wife friendly" boot screen.
As I understand it, torch refers to the built in flashlight feature in aokp called torch. Tiny flashlight plus the widget give similar functionality.
Sent from my SCH-I500 using xda premium
So far ive been running CM9 and its alot smoother although there are minor glitches and some times it reboots and apps force close but dragonkiller also leaves dev tools installed has anyone heard if the kernel has been updated
The kernel cannot be updated because Moto and Verizon lock the bootloader.
dragonkiller is working on a kernel bypass
DigitalMD said:
The kernel cannot be updated because Moto and Verizon lock the bootloader.
dragonkiller is working on a kernel bypass
Click to expand...
Click to collapse
Thanks im still very new to this
I have a Fascinate which is 2 years old. It runs ICS very smoothly. Of course I can flash a custom kernel, then tweak the kernel to my liking. It's sad for the X2 we cannot. It makes the life of our developers much harder in getting things to run smoooooth.
Both my fascinate and my X2 have the same ram..not a ram issue, it's just the damn bootloader that is locked.
/rant
DROID DOES, Apple did...like I forgot when
I was running CM9 on my Droid X until it crapped out on me yesterday and Verizon is sending me a X2. I believe the X had a locked bootloader also and it ran CM9 very well.
Since I can't post in the thread I want to cause I don't have 10 posts yet I am wondering a couple things about getting CM9 on the X2 when it arrives. The OP for CM9 Alpha5 is sort of misleading... I have flashed a ton of roms on my X but the X2 seems like there is an extra step or two. Will I need to be on 2.3.4 or 2.3.5 before flashing CM9? I already downloaded BSR for X2, I see something about a patched BSR for CM9; will I need this if I coming from Gingerbread or just the BSR?