Database Users

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.

Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?

lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...

The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...

I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.

BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...

I wonder if it found one of those radios and did something with it?

For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.

hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.

lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Phone keep restarting by itself ??

Ok so my hero keep turning off by itself. This is not the first time it happen, it'll be on then it will just turn off by itself. Even worse sometimes the led light will be flashing for a new message and when I press the menu button to unlock it, it restart automatically. It mostly restarts itself when the screen is dark and i always press menu to bring up the light or to unlock it. Is this mean my phone is now defective ? I mean this happened before on some other 2.1 ROM too so idk what it is. Can someone tell me how to fix this????? I've tried almost all 2.1 Roms Aloysius, DC 2.07.2, Trevs Damage, ZenHero , RegawMod (themed) and Fresh 2d. the only rom that didnt restart my phone was the Fresh 2d with the very first audio fix by Avalaunchmods but i already erased that out of my computer.

Hmmm, not much to go on. I had experienced a similar issue back on early ROMs, but it was so infrequent I never really cared.
Try a Nandroid Backup and then flash to a 1.5 ROM and see if it continues, if so then yes the phone may be defective.
Also try different 2.1 ROMs here, and let us know if anything changes.

Dude, seriously do you need to have such a big font? Its not necessary....

i didn't catch that, what did you say?

lol mr big font
this happened to me last night, i wasnt even touching the phone and this happened, but its been the only time and ive been using 2.1 roms for a while now...i think this even happened once or twice when i was on stock...
coming from windows mobile, im used to things like this.

This happens on my sisters stock phone frequently I don't really care to look at it though.
Big fonts aren't nice. Stop using them

Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi

danknee said:
Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi
Click to expand...
Click to collapse
My sis's is on stock, and she has the problem
Funny thing is my phone is the only one without problems, and it's the only one that's rooted.

i don't know what we're yelling about loud noises

i got it fixed now, i think, i've had Fresh 2.0d for a few days and this problem is gone. oh and sorry for the big font lol i did this post in class on my phone and i didnt preview or look at what font i was using

Why does my phone shutoff?

Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.

If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD

patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.

Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.

Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant

I can't seem to find Damagedtrev 2.01
So I can't test it.

Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.

Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.

Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?

Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.

Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.

reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation

kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.

That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.

patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221

Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.

Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?

I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd

screen problem

hey everybody I'm not sure if i am putting this in the right section, but here goes. I am currently on deployment with the army in Djibouti Africa, but i still use my hero a lot (obviously just over wifi). i have come up with a strange problem regarding the screen when the phone gets warm the screen becomes unresponsive, when i go into hboot it tests out as failed. Am i just hosed and need a new screen or does anyone have any ideas about a fix. again I am in Djibouti Africa and as such repair tools and materials are severely limited. '
thanks in advance.

Might want to add what rom,recovery,kernel and extra mods your running firerats or data2ext. Also if your s-off and if so what method and what radio/baseband and prl are you on. And what service provider are you with. Also what are have your tried to fix the issue and what are you doing when the phone gets warm and the screen becomes unresponsive. Also if you have access to adb or not. This info will help members assist you in solving your issue.
#Root/Hack-Mod_Always*

hmm let me see i nandroided between about 10 different rom/ kernal variations yesterday seeing if that was the problem, none of it helped. right now i left it on cyaqnogen 7.0 RC2 with the cyanogen kernal. radio version 2.42.02.10.29 my recovery is the latest clockwork and as for s off i really dont remember. i have had this phone since it was very first introduced so i cant remember if that is something ive done or not.

it could be overheating maybe i know when im out biking and my screen gets sweat on it itll become unresponsive for a minute or so but after i wipe it down its good.

Are you running an overclock app???
#Root/Hack-Mod_Always*

Atrix lagging......what can I do?

Ever since the Gingerbread update my phone has had a noticable amount of lag. This occurs between screens, apps, button presses and even typing. Sometimes it wont do anything for a couple of seconds and then type the whole word I was trying to type.
I have also noticed a very long boot time when I power it off and back on. Takes several minutes...
My phone is rooted with Gingerblur.
Any ideas of what I can do to fix this?

1)Unlock bootloader
2)Flash a diff non-doodoo ROM, there are plenty of them
3)??????
4)Profit
Sent from my MB860 using XDA App

kisnerct said:
1)Unlock bootloader
2)Flash a diff non-doodoo ROM, there are plenty of them
3)??????
4)Profit
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thank you for the response : )
Number 3? Not sure what you mean on that one....
Is this a common problem? Does anybody else recommend to do what was mentioned above?

Exchange before warreny is void
Tenacious--M said:
Thank you for the response : )
Number 3? Not sure what you mean on that one....
Is this a common problem? Does anybody else recommend to do what was mentioned above?
Click to expand...
Click to collapse
#3 is did it fix your problem. The answer will be no its not going to. I work for at&t and have sold this phone with the update and it is a reported problem. My suggestion flash the stock gingerbread sbf and exchange with a device support center near you.

[email protected] said:
#3 is did it fix your problem. The answer will be no its not going to. I work for at&t and have sold this phone with the update and it is a reported problem. My suggestion flash the stock gingerbread sbf and exchange with a device support center near you.
Click to expand...
Click to collapse
I bought this phone from at&t WITH the update and had 0 problem unlocking rooting flashing etc. I haven't even had a single experience with lag yet. Doodoo Motoblur is the source of the lag.
Sent from my Atrix 4g (MB860) using XDA app.

I hate doodoo
Wtf is WP7

Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?

Tenacious--M said:
Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?
Click to expand...
Click to collapse
I'll just share my experience with you.
Whenever I get a new phone I'm not quick to root/flash etc. as I like to play around with it to be sure I really want to flash it. Plus, this was my first experience with motoblur so I wanted to give it a shot.
This phone was garbage IMO without a ROM. So much worthless bloat and a LOT of lag problems. The speed of this phone (for it's hardware) was extremely disappointing and I was seriously regretting my purchase. I was coming from a captivate, so to say I was disappointed (which coming from that phone) is huge. Lag between screens, god-awful boot up times, and confusing motoblur had me ready to return this and wait for something else. That being said, decided to give the ROMs a chance. I was coming from the latest software and I don't know if I just got lucky but I had 0 problems rooting, unlocking, and flashing....a lot less problems than I had with my captivate. Went with cm7 and haven't looked back. Aside from a few relatively minor bugs with cm7 (which WILL be fixed), I am now extremely pleases with this phone...I guess the better term would be in love with it. Its blazing fast, good battery life, and just feels smooth all-around.
It really a shame that we have to go through these kind of hoops to unleash the phones potential...so many users that will never know how great of a phone they have.
Sent from my Atrix 4g (MB860) using XDA app.

Make a nandroid
Unlock your bootloader
flash cm7
I PROMISE you won't regret it!!
I've been using Android for a while now & the only competition that cm has is miui (and that isn't even available yet)

Tenacious--M said:
Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?
Click to expand...
Click to collapse
i got my first phone from AT&T and bricked it unfortunately, went back into the AT&T store and explained my situation to the rep and asked how much it would be to replace it, but he gave me a new one free of charge.
after i got my second one, i updated it to GB right away and was satisfied with the phone, the AT&T rep played with it showing me all sorts of things about Android since it's my first Android phone. after about 30 minutes of showing me all sorts of cool things i could do with it, he said he was confident that the phone was bug free so i walked out of the store and updated it right there. i noticed a lag increase with gingerbread that wasn't there in his froyo presentation, which was kind of disappointing. after i got home and rooted my phone though, i was able to tweak things and get the ball rolling, only slight lag on certain transitions and games. (still disappointing with these specs though)
shortly after, i unlocked the bootloader and flashed ninja speed freak, which cleared up almost all my lag problems. i didn't experience any real lag in transitions, but every once in a while i'd get slight lag in games.
then CM7 came out, and i installed it, and i'm experiencing 10-15 second boot screen times, compared to multiple minute boot times on stock. no lag with any animation or game i've played so far, great quality videos and extremely satisfied all around. the different without motoblur is extremely noticeable. i can't wait for it to be finished so all our wonderful devs can go back to their own little side projects, and we can see what this phone is really capable of

Flash a newer Rom.
If you like the blur features use homebase.
Cm7 is GREAT! But not If you like blur.
Alien rom was my favorite rom till cm7 tho.
You wont regret flashing eaither of those.
Sent from my CM860

tenacious--m said:
ever since the gingerbread update my phone has had a noticable amount of lag. This occurs between screens, apps, button presses and even typing. Sometimes it wont do anything for a couple of seconds and then type the whole word i was trying to type.
I have also noticed a very long boot time when i power it off and back on. Takes several minutes...
My phone is rooted with gingerblur.
Any ideas of what i can do to fix this?
Click to expand...
Click to collapse
cyanogenmod 7!

read op wrong fist post
Cm7 is the answer

I gave thanks to all of you! I very much appreciate the feedback. CM7 is what I have been researching as well and it sounds like the bomb!
However, I am really spinning my wheels here on getting the bootloader unlocked. Getting CM7 on there is not hard at all. Ive done that kind of stuff before on other phones, but Im not getting sucess on the bootloader.
Im running 2.3.4 if that makes any difference and am rooted.
When I attempt to unlock the bootloader I get a message on cmd saying "oem unlock is not implemented"
Can one of you guys/gals gently walk me through unlocking this guy? Maybe Im missing one little thing? I have spend two days researching and trying the different methods and keep coming up against this wall.
Thank you so much in advance! : )

I am on stock GB and experienced a little lag. But after I installed SGS TOUCHSCREEN BOOSTER and bought ADW EX I've never had a problem. When I used Zedge to download wallpapers my Atrix crashed and rebooted. So uninstalled that and I'm good again.
Stock Motorola Atrix 4G

Tenacious--M said:
When I attempt to unlock the bootloader I get a message on cmd saying "oem unlock is not implemented"
Can one of you guys/gals gently walk me through unlocking this guy? Maybe Im missing one little thing? I have spend two days researching and trying the different methods and keep coming up against this wall.
Thank you so much in advance! : )
Click to expand...
Click to collapse
It would help if we knew what method you were using to try and unlock .
Sent from my MB860 using XDA App

Sorry... : )
Ive tried this version. Automatic unlocker
http://forum.xda-developers.com/showthread.php?t=1182871
Ive tried the BriefMobile version
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader]
And I tried the IHOP Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
Ive flashed ROMs on several phones, made nandroid backups etc... I just dont have alot of experience with cmd or bootloader unlocking. I tried over and over and did the instructions to the letter, unless Im missing something. Being new, Im sure im missing something small.

Ok, finally! I got it done and flashed to CM7. WOW! I love it!
I did notice some differences so I will post my experience here. I will highlight the differences I found that worked for my 2.3.4 Rooted Atrix. Maybe it will help other newbs like me : )
By the way, credit to BriefMobile and the2dcour for the original guide
***I marked the differences I noticed when unlocking my 2.3.4 unlocked At&t Gingerbread***
How To: Unlock the Atrix 4G Bootloader
Prerequisites
• Backed up /data partition
You will lose all of your /data during this process!
• Unlock SBF file [Mirror]
• RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]
• Fastboot package [Mirror]
Also found in the Android SDK tools folder
Instructions
1. If you’re on Gingerbread, skip to step 13. (I was on 2.3.4 Gingerbread and I also had to do all the steps. Dont skip!!!)
2. Power down your Motorola Atrix
3. Take out your microSD card and SIM card for the flashing process
4. While turning the phone on, hold the Volume Up button until it acknowledges RSD
5. Your device will say “Starting RSD protocol support”
6. Run “RSD Lite” on your computer
7. Press the “. . .” button next to the box labeled “Filename”
8. Load up the SBF file
The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .zip file on your computer
9. Plug your device into your computer
Use the USB ports on the back side of your computer for safety
10. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” (Mine said SE Flash Olympus, not NS)
11. Press the “Start” button
12. Be patient while the phone reboots. It will take a long time. (Phone didn’t reboot. It went to a menu and said “5 seconds to select Fastboot”. You have to use Vol down to move in the menu and the Vol up button to select “Fastboot”)
13. Open and extract the Fastboot package from above
14. Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
15. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package) (I extracted mine to the C:\ drive. Then you don’t have to type so much. Just cd C:\fastboot )
cd your directory here
16. Power down your Atrix device
17. Hold the power button and the downward volume button until you see “Fastboot”
18. Let go of the buttons and press the upward volume button once
19. You will now see “Starting Fastboot protocol support”
20. Plug your device into a USB port in the back slot of your computer
Front slots sometimes do not have enough power to stay connected to the device.
21. Type the following command:
fastboot oem unlock
22. You will now receive a warning along with a unique device ID
23. Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
24. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader! (Mine said “unlocked” in upper left hand corner, but didn’t reboot. I pulled the battery and restarted. Been working fantastic ever since!)
Source: the2dcour