|
I just put rubix focused 1.0 on my DroidX and so far it seems pretty good. It is definitely smoother than the leaked 2.2 ROM and it has every piece of Blur and Verizon bloatware crap removed. Also it has swype unlike the FlyX ROM which was completely retarded. Easily installs through ROM manager/Clockwork Recovery from the 2.2 leak. Kept root and all.
|
# ¿ Oct 27, 2010 21:23 |
|
|
# ¿ May 16, 2024 09:16 |
|
Going to make the plunge to CM7 on my Droid X. I've been using rubix focused 2.0 and while it seems alright, it's slow, outdated, and has some bizzare issues. I haven't really kept up on the lingo, but I understand the basic steps are: 1.) SBF back to 2.3.340 2.) Root using ZDroot 3.) Install Droid2 Bootstrapper 4.) Boot into recovery 5.) Install CM7.zip 6.) Install GAPP thing, reboot. Are the nightlies just updated "patches" for CM7? Basically I just download the latest one and boot to recovery -> install nightly.zip? No need to wipe data/cache?
|
# ¿ Jun 28, 2011 00:56 |
|
Flashed CM7 on my Droid X uneventfully, and it is 100% holy poo poo improvement over stock/other Droid X "roms". I miss Swype though.
|
# ¿ Jun 28, 2011 22:27 |
|
Dancing Peasant posted:Same here, I need my Camcorder functionality as well. But if I can just flash it with zips, I think I might jump. An SBF is probably your best bet. There is anecdotal evidence that there is some instability when installing the nightlies after you've done the "monster" zip install.
|
# ¿ Jun 29, 2011 17:12 |
|
right arm posted:So just in case no one has seen this yet (it's not on ROM Manager at the moment), the Droid X now has a very good, in my opinion, ICS port located here: http://rootzwiki.com/topic/13425-romcm9-encounterics-x-beta-3-stability/ I've been using this for the past week and it is very, very good. I never use te camera anyways so there's really no reason not to use it. I swear the battery life is much better than CM7, too.
|
# ¿ Jan 3, 2012 21:50 |
|
Mughe posted:No. Flashing CM10/CM10.1 on the galaxy S3 can lead to losing IMEI/ERI information and basically dropping your phone from the network. Something about dummy information being loaded during boot up of the phone. It can thankfully be fixed but it's a long process. I think this happened to me. I was on CM10 and updated to the latest nightly (thinking, of course, without any warning, that it would be like any other nightly) and suddenly I'm stuck at "Waiting for network..." during first boot. So do I Odin back to stock, re-root, re-unlock bootloader, install CM10.1 nightly 122412(awesome how there isn't even a different link, so how the gently caress would you know it was a newer Android version unless your homepage was XDA devs?), then install 121212 gapps? Next phone is going to be an iPhone. gently caress this poo poo.
|
# ¿ Dec 25, 2012 09:11 |
|
|
# ¿ May 16, 2024 09:16 |
|
LastInLine posted:It continues to amaze me that people buy phones knowing they are going to modify them yet purchase devices controlled by carriers who are actively attempting to prevent you from doing so. Then when something goes wrong it's somehow the fault of the OEM/developers that it did so. Well you're right, thanks for rubbing it in! Where do I turn in my bitter, encrusted, Stallman-beard? EDIT: So, I reflashed gapps, same problem. My IMEI matches what's beneath my battery, but my phone number is wrong. Even on the latest stable ROM, with latest stable gapps. Welp. VVVV - Except 3G was completely hosed in every single nightly because there wasn't a RIL for Jellybean. forbidden dialectics fucked around with this message at 12:02 on Dec 25, 2012 |
# ¿ Dec 25, 2012 10:16 |