Database Users

Someone Make a CM7 Rom Please.

I love the cm7 and wish someone would make a cm7 rom for the D2.

Its pretty much impossible with the locked bootloader. Cm7 needs a custom kernel that the locked bootloader doesn't allow, so were stuck with stock.
Sent from my DROID2 GLOBAL using XDA App

well that sucks.

Try liberty, it's about as good as it gets at the moment. I think keyjar is also working on a gummyJar GB version, which should be a solid rom as well. There is a working UD port for D2, but it's still on RC2 and hasn't been updated in a while, though I ran it for a few weeks and it was pretty solid. Liberty GB is also in the works, though not publicly available atm. CM7 isn't really necessary for the D2, since most of what you would get can be had in other roms currently available, just via some different means.

any way to get the lockscreen gestures currently?

Cm7 DOES NOT need a custom rom. It will run better if it does but it's not required. But we don't have aosp Rome such as cm7 because the locked bootloader makes it hard to make things work
Sent from my DROID2

Alright I wanna clear this up.
Cyanogenmod is a custom rom. We can install those on our Droid 2/X devices with Koush's Bootstrap tool. That said, we cannot install a custom kernel. Thus, cm-kernel for Droid 2/X is probably not going to happen anytime soon. However, that is not to say that Cyanogenmod 7 requires a specific kernel. I see no reason why Cyanogenmod 7 could not run on the stock Motorola kernel.
Moving on, cvpcs is working on a Cyanogenmod port for Droid X (and thus also Droid 2). When the rom will be stable, however, is unclear. As far as I understand, it's not really working.
-Zane

More importantly, this is the development section, not the request section. There is no request section for a good reason.
Sent from my DROID2 using XDA App

Ok, for those who aren't searching these days...
1 - Cyanogen won't come out officially with a D2 port until Moto unlocks the bootloader
2 - Cyanogen actually doesn't need a custom kernel to do what it does
2a - Go use Liberty..its effectively Cyanogen sans a 'custom kernel' and does all the same.
Me, I'm flashing back to stock for a while. Liberty 2.0 is causing me some headaches as of late and I can't download @#$ from the market it seems cause its like everything is fricken blocked now.

jediman said:
Ok, for those who aren't searching these days...
1 - Cyanogen won't come out officially with a D2 port until Moto unlocks the bootloader
2 - Cyanogen actually doesn't need a custom kernel to do what it does
2a - Go use Liberty..its effectively Cyanogen sans a 'custom kernel' and does all the same.
Me, I'm flashing back to stock for a while. Liberty 2.0 is causing me some headaches as of late and I can't download @#$ from the market it seems cause its like everything is fricken blocked now.
Click to expand...
Click to collapse
Thanks for clearing this up

Also motorola probably will never unlock the bootloaders on their phones so getting CM7 will be impossible

ljbaumer said:
Also motorola probably will never unlock the bootloaders on their phones so getting CM7 will be impossible
Click to expand...
Click to collapse
With xda theres no impossible

ljbaumer said:
Also motorola probably will never unlock the bootloaders on their phones so getting CM7 will be impossible
Click to expand...
Click to collapse
I thought Motorola stated that they would unlock the bootloader, but it was up to the carriers whether or not they would allow for it.

Jordan umts is the codename of the Defy... which is also locked.... and we are the 4th device in cyanogen 7 number of installs stats

BPMOmega said:
I thought Motorola stated that they would unlock the bootloader, but it was up to the carriers whether or not they would allow for it.
Click to expand...
Click to collapse
If it were there carriers fault then y do some phone come locked and some come unlocked? Motorola is just trying to put the blame on someone else
Sent from my DROID2

whezzel said:
If it were there carriers fault then y do some phone come locked and some come unlocked? Motorola is just trying to put the blame on someone else
Click to expand...
Click to collapse
Originally, yes, it was Motorola's policy to lock the bootloader, but they had announced recently that they would leave the bootloader unlocked, at least for phones on carriers that allowed it (so, I would at least guess that AT&T would be out of the picture, since they've even been controlling of the ability to sideload apps).

Working on it come help if you can:
http://forum.xda-developers.com/showthread.php?p=14705596

wwonka69 said:
I love the cm7 and wish someone would make a cm7 rom for the D2.
Click to expand...
Click to collapse
Ok, I'll do it.

lol.
Anyone got the link to the most recent version?

Official droid 2 nighlies. Cm7 with GB kernal is being developed over at rootzwiki
http://download.cyanogenmod.com/?device=cdma_droid2

To update or not to update

I just got my replacement atrix today, im trying to figure out whether I should update it to the 2.3.4 OTA or not. My old atrix I had unlocked on 1.83 and was running cherryblur. Is it easier to unlock on 1.83 or the new OTA or are both easy now?
Sent from my MB860 using XDA App

Basically, if want to be adventurous with the ROMS and crazy modifications, then root and unlock bootloader, or if you are fine with the official OTA update. Then just stick with those. I am sticking with OTA since I don't want to brick since I am using my ATRIX for college and job and need a reliable phone. I might root it though if I can figure it out.
My modding fun is with my Sony Ericsson Xperia X10. That's my xda fun.
Sent from my Atrix 4G with XDA Premium App

I was glad OTA keeps ALL of your settings and applications. I did it, only because Motorola says they will unlock the bootloader. When that happens I figure I'll finally root and go wild with ROMs, because my 1 year warranty may be close to expiring anyway.
For me, with no other changes but the OTA upgrade, my battery life BLOWS me away. I used to get down to 10-15% after 9 hours, casual internet and lots of mp3 playback.
Now I only get down to 45% doing the same exact stuff! Astonishing.
If you are waiting for unofficial unlock support from Motorola, do the OTA. you will be happy in the interim

Im already planning to unlock it and put roms on it, just wondering if its easy to unlock on 2.3.4 or if I should just keep it at 1.83. Cause froyo sucks and I wont have time to do anything on it til sunday.
Sent from my MB860 using XDA App

sunshine1982 said:
Im already planning to unlock it and put roms on it, just wondering if its easy to unlock on 2.3.4 or if I should just keep it at 1.83. Cause froyo sucks and I wont have time to do anything on it til sunday.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
According to this thread here:
http://www.atrixforums.com/forum/mo...official-2-3-4-build-4-5-91-can-i-unlock.html
you can still unlock but there is a small risk of bricking -- unlocking before flashing to 2.3.4 OTA is advised (or do what I did and click the first link on this thread http://forum.xda-developers.com/showthread.php?t=1136261 , run the SBF via RSD Lite 5.31 & motorola's drivers (you can find them on their site in the Atrix section)), send the unlock command via fastboot, and follow the rooting instructions -- all of which are again on the same first link on that page.
EDIT:
This allows you to flash an unlocked bootloader, GB 2.3.4 update, as well as root, all via one file. Remember that there are instructions to follow, it doesn't unlock or root for you, but provides all three as part of a flashable file.
Others feel free to chime in -- I'm only explaining what I did and worked for me. I understand that the general concensus is that SBF file carry a higher risk than other methods of flashing.

[Q] Is the Droid X rootable

I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!

floridatank said:
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
Click to expand...
Click to collapse
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App

bigshotrob22 said:
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!

floridatank said:
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
Click to expand...
Click to collapse
Nope! Like I said its unrootable
Sent from my DROIDX using XDA App

Unrootable...
But that doesn't mean you can't root.
SBF to froyo.
Flash the 2-part gingerbread .zips.
Flash a custom rom (Liberty?)
Or stay on the froyo kernel...
and try MIUI or Cyanogen.

Be careful and read as much as you possibly can before starting. Myself and at least one other on here with the latest iteration of the X have ended up with boot looping or totally non-responsive devices.
I have started a thread with my findings. I am by no means an expert but I do have much experience with rooting devices going all the way back to the PPC6700.
Good luck.

getting stuck in a bootloop is part of the exploration process IMHO.
At least once per new ROM I'll flash something 'just to see what happens' and end up SBF'ing back. Just make backups between steps if you aren't sure about what will happen next.

it would be nice if one of the devs or people who work on rooting or someone in the know would at least comment if we are going to get a real root with the OTA
i mean im running froyo with CM7 but i sure would like the new firmwares for all the radios flashed and then be running CM7
so if someone could give us some kind of update at least saying no one is even remotely working on trying to gain root on 4.5.596 Official OTA or that yea we are working on it but it is a ***** and taken longer then we expected
that lil bit of info goes a long ways
thanks

I am not aware of any dev working on this ATM.

I don't think rooting 596 ota is critical 2nd unit has opened up alot of new doors and the attention has shifted. However I have flashed all of drew gardens latest and ran cm4dx until nightly 47. Now I'm daily MIUI and loving it, despite locked bootloader the cdma_shadow still has alot of options.
Sent from my DROIDX using XDA Premium App

to my understanding .596 has better battery life and signals are better for wifi and cellular (at least more stable and less drops)
i do not know if this is true but i have read/heard alot of ppl saying the battery life is better on .596
after all there is a .596 for some reason and its not a lil bump from 2.2.340 its pretty big
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it

m16-maniac said:
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
Click to expand...
Click to collapse
the big deal is that there isn't a readily found exploit for the ota, the pre-rooted was done with a diff. method (brute force? recompiled?) but the versions are the same regardless
no ones holding back a secret root method, there just isn't a dev interested in spending huge amounts of time to recreate what already exists
i think it would be interesting to create a batch script that sbf's a phone and installs the pre-rooted .596 but all hidden behind a random animation so the user doesn't see what's happening. if i call it a 'one click' root method lots of people who don't seem to want to take the readily available pre-rooted gb for whatever reason would likely be happy. yeah i understand that if it includes a sbf then data may get lost, but if i said in the instructions of my 'app' that it would happen and they should have backups, people would still likely use it
sorry, but i just don't understand why so many people who want root are seemingly against using the pre-rooted option, as most of them don't have the knowledge to find an exploit or a root method from scratch themselves, so they are still using the work of someone else...

<Disclaimer>I'm going out on a limb here with limited knowledge of the X. <End disclaimer>
From what I read and I don't remember where, the rooting of an X involves a 2nd init method by which it takes control of the initial init. I believe I read the original init isn't able to be exploited and this is the basis of some of the more complicated methods of rooting the X.
If someone knows more about this please correct me or chime in.
I had an Incredible prior. The rooting was more comprehensive and simple. I believe that is because the bootstrap and recovery were not as difficult to get into. That being said, personally, I may be going back to another HTC device if the folks light years smarter than me aren't interested in developing a root method like the other devices out there.

New Atrix Owner on .91 -- should I go to .141?

Hello Everyone,
I am a new Atrix owner who just received the phone with .91 installed.
Before I go to a custom ROM (CM7, ICS, etc), I always like to check out the factory ROM to see what its all about.
Obviously, AT&T is hounding me to upgrade to .141, which is something I would like to do just to see any changes/improvements.
If I upgrade to .141, I see there's a new way to root the phone (well, it looks new anyway) -- how about installing custom ROMs, am I still able to do that if I go to .141? I've been trying to read as much as I can. It appears there are issues with going to .141 if you have a unlocked bootloader, but that isn't me (yet!).
Thanks,
Chris

I would unlock the bootloader first then flash a fruitcake of the new update. The fruitcake will be the same as if you updated normally but you will maintain your unlocked bootloader and root without the risk of bricking your phone. That way if you don't like it you can switch to a custom ROM. As far as I'm aware you can't unlock the bootloafer once you update. I could be wrong about that though.
Sent from my MB860 using XDA App

1. +1, it would make more sense to just flash a fruitcake
2. Yes, you can unlock the bootloader if you have updated to .141, but I have only read it working for people who had previously unlocked it.
jadwv2210 said:
I would unlock the bootloader first then flash a fruitcake of the new update. The fruitcake will be the same as if you updated normally but you will maintain your unlocked bootloader and root without the risk of bricking your phone. That way if you don't like it you can switch to a custom ROM. As far as I'm aware you can't unlock the bootloafer once you update. I could be wrong about that though.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse

Thanks to you both for responding -- I'm still trying to read up on the Atrix, so having this info really helps. I will go ahead and unlock/root with .91 and then do a Fruitcake upgrade (and then eventually do a real ROM! )
Thanks again guys for your replies. I really like the phone so far -- screen is just the right size, battery life is very nice (a huge plus), and its thin and light. Good stuff!
Chris

[Q] MB860 on 2.2.2 - Where do I start

Hi,
I recently purchased an Atrix 4G for cheap and am now trying to update it to a more recent firmware version.
I currently have a:
MB860
on Android 2.2.2
running Version.4.4.20.MB860.Retail.en.DE
Checking for system updates through the phone doesn't yield any results. Threads on the web or this forum often lead to dead links or warnings about RAM problems or the possibility of bricking my device.
I'm not technologically retarded (as in I can jailbreak and install packages on an iPhone) but most of the update/flashing instructions aren't really helpful for someone who's just getting into android.
Where do I start?

I would start with the sticky at the top of this section (http://forum.xda-developers.com/showthread.php?t=1984381), or skip to the 4th sticky (http://forum.xda-developers.com/showthread.php?t=1302423).
It is written step by step.

I'm not trying to unlock my bootloader on 2.3.4, because my phone isn't running 2.3.4. I can't find any info regarding help for people still stuck on FroyoYo there, either.

The bootloader is irrespective of the version of Android you are running. Follow the directions to unlock it first, install an alternate recovery and then flash whatever you like.

TGHI said:
The bootloader is irrespective of the version of Android you are running. Follow the directions to unlock it first, install an alternate recovery and then flash whatever you like.
Click to expand...
Click to collapse
Thanks for the info. So doing this allows me to install Custom ROMs on my Atrix? While that is indeed useful, it doesn't really answer my initial question.
Is there a way to update my phone to 2.3.4 without rooting or unlocking first? I'm currently just looking for a stable webtop experience and decent battery life. If I get that on Stock 2.3.4, I might wait with the flashing experiments.

Go to settings, about, and check for updates. (if memory serves me correctly)
エイトリックス から 送ります

you need to go to motorola website and download system updater....
Sent from my MB860 using xda app-developers app

thesummoner101 said:
Go to settings, about, and check for updates. (if memory serves me correctly)
Click to expand...
Click to collapse
This tells me that my device is up-to-date.
you need to go to motorola website and download system updater....
Click to expand...
Click to collapse
The threads in the development forum warn about installing official updates. Do I risk bricking my device if I install a custom rom after using the system updater?

Placeb00 said:
Thanks for the info. So doing this allows me to install Custom ROMs on my Atrix? While that is indeed useful, it doesn't really answer my initial question.
Is there a way to update my phone to 2.3.4 without rooting or unlocking first? I'm currently just looking for a stable webtop experience and decent battery life. If I get that on Stock 2.3.4, I might wait with the flashing experiments.
Click to expand...
Click to collapse
You DO NOT want the latest stock update if you're planning on doing tinkering down the road. As far as I understand it, one of the latest OTAs pretty much blocks you from unlocking the bootloader. (Same for the Photon)
With this phone, if you put your faith on Motorola, you get royally screwed. I would break from the shackles sooner rather than later.

littleemp said:
As far as I understand it, one of the latest OTAs pretty much blocks you from unlocking the bootloader. (Same for the Photon).
Click to expand...
Click to collapse
Where are you getting this from?

A little update:
Rooted, unlocked my bootloader, flashed a 2.3.6 ROM. Everything works fine, and I'm really happy with my new phone/netbook combo.

Placeb00 said:
A little update:
Rooted, unlocked my bootloader, flashed a 2.3.6 ROM. Everything works fine, and I'm really happy with my new phone/netbook combo.
Click to expand...
Click to collapse
Could you post link where did you tutorial. I have retail Eu version and don't know where to start.
On samsung or sony its much simpler.
Or I have become more stupid
Thanks
Sent from my MB860 using xda app-developers app

http://forum.xda-developers.com/showthread.php?t=1302423
This is the tutorial I used.

Placeb00 said:
http://forum.xda-developers.com/showthread.php?t=1302423
This is the tutorial I used.
Click to expand...
Click to collapse
Thank you.
Sent from my MB860 using xda app-developers app

revdep-rebuild error
For what it's worth:
Editing /usr/bin/revdep-rebuild.sh with nano and changing 2 instances of /var/cache to /preinstall/var/cache resolved all my problems.
More specificly:
line 262: "$WORKING_DIR" != "/var/cache/${APP_NAME}"
and
line 559: local tmp_target=var/cache/${APP_NAME}
Good luck.

just follow the official CM guide for atrix. that's the best