Database Users

brick?

i was running fission rc1 on my d2g, used frm to download stock d2g deodexed blah blsh, flashed it, stuck on motorola m screen. cant get it to boot to bootstrap recovery for ****. only regular recovery...i could cry
edit: omg im gonna throw up. please tell me theres something i can do.
EDIT: ok...so if it is bricked and i have the $1.99 or $2.99 insurance, whatever....can i get it replaced...and if not, what if hypothetically speaking...it was smashed by a car...could i then get it replaced?

I am no expert, but lets try this, start the phone and as soon as the M appears, immediately pull the battery, and the put back in and start the phone. Lets see if the phone goes into ClockworkMod, and if it does, you can do a restore. Let me know how you make out.
MICP1480

no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.

botnryan said:
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
Click to expand...
Click to collapse
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.

This just means moto needs to release the sbf for the D2G so we can fix them instead of moto/verizon getting a bunch of returned devices.
Sent from my DROID2 using XDA App

miketoasty said:
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
Click to expand...
Click to collapse
really? and how will they know if its all messed up and wont even boot? plus i did a data and cache wipe of the phone thru the regular recovery, will that not kinda wipe away anything incriminating? Not to mention the last rom i flashed was the stock d2g rom, just deodexed and such

When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.

leobg said:
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
Click to expand...
Click to collapse
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?

botnryan said:
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
Click to expand...
Click to collapse
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.

newk8600 said:
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
Click to expand...
Click to collapse
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol

botnryan said:
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
Click to expand...
Click to collapse
Just checking I didn't see you tried that specifically glad you got your replacement now you know to be very careful as the sbf isn't out yet.

sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?

botnryan said:
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
Click to expand...
Click to collapse
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.

newk8600 said:
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
Click to expand...
Click to collapse
alrights, thanks man. i feel they probably wont be able to find anything out but im still going to use up my 10 day period i have to send the phone in just in case the sbf is magically released in that time period.

Updating MYNS and BRICKED my phone in the process. Anyone else?

I was installing the new Myn's Warm lastnight upgrading from the previous version. It did not install properly and COMPLETELY BRICKED my phone. It won't turn on, can't connect to computer via USB, nothing at all! Anyone else have this problem? OR any solutions other than taking to Sprint?

I doubt that your phone is bricked. Hopefully you DO have a rooted EVO though. I would plug it in and let it charge. Then take out the battery and put it back in and turn it on while holding down power and volume down keys to boot into recovery. Also hopefully you made a nandroid backup so restore that and go from there. I had no problems with flashing RLS5 at all. Hopefully this helps. Otherwise maybe someone with a little more knowledge can help you...
Sprint is DEFINITELY not the answer...

do a battery pull and try to get it to hboot. then try and run the RUU. if not you may have to take it to sprint.

The phone won't charge, won't turn on, can't hboot. I do have backups if I could get it to turn on I could restore it. Had no problems before. I will attempt to charge it as you have suggested but I even put a different fully charged battery in and the phone does not even make at attempt to turn on. I agree I doubt that Sprint is the answer

did you flash any radio updates? any prls, I've never heard of flashing a rom making a phone brick, but definitely heard of radio updates bricking devices.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk

i really doing think his update bricked your phone

This means that while installing Warm you bricked your phone. Don't give his ROM a bad name.
I would recommend trying to charge it and maybe try a different battery, but then just run the RUU and go from that. I had the same problem with RLS 4.
Sent from my EVO using XDA App

If you used the package to update the pri, radio, etc then that may be the problem, hopefully you aren't bricked.
Sent from my PC36100 using XDA App

Are you sure that you didn't flash the radio? I flashed Myn's rom last night and I didn't run into any issues, in fact I've never heard of a rom bricking a phone, that usually happens when a radio flash goes terribly wrong. Anyhow, you can take it back to Sprint since it's still under warranty and they will replace it for $35.

CheesyNutz said:
i really doing think his update bricked your phone
Click to expand...
Click to collapse
ive heard several people say it has in fact jacked their phones up. hence why i have not upgraded to it yet.

I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.

the radio update isn't included with the rom.
it's also been highly advised in the warm thread itself to flash just the radio, then just the wimax, then perhaps the nv/pri, because so many people have been having trouble with the pri update.
the radio combo pack isn't bundled with anything else and, right now, many think it should be avoided for reasons just like this.
not a solution, just clarification and friendly advice for anyone else who's curious about possible trouble with the upgrades.

I updated my radio/pri/wimax and all that jazz before the last Fresh update, so I had no need to this go around. I simply wiped data/dalvik/cache and flashed the RLS 5, with no problems. I did run into issues after I tried restoring my apps + data, but that was a Titanium Backup issue

arcurtis said:
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
Click to expand...
Click to collapse
Just my 2 cent.. often times we flash before reading the thread and then complain about a kernel,ROM or theme.
After reading what you said I can only come to the conclusion that you and all the others complaining about the radio update are obviously impatience. All who have had problem with the update on the radio all stated their phone sat on the white screen and they did a battery pull.
Yet the radio update thread says it will/can take up to 30 min to flash. The best way to check your phone would be to use another battery. I have never heard a bricked phone that doesn't cut on. That's a battery issue.
What kernel were you using before flashing?
What ROM?
What's your hboot?
Sent from my PC36100 using XDA App

I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.

arcurtis said:
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
Click to expand...
Click to collapse
Does the phone attempt to charge when you plug it in?
Sent from my PC36100 using XDA App

I can confirm brick.
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.

Nope the phone will not even charge. I've changed batteries and chargers. I am assuming I am one person who has just had extremely bad luck with a random flash. I was running Myn release and did a backup and wipe then phone would not reboot and completely shut down. I got the android guy with the arrow and then it went completely dead and won't turn back on.

dth4310 said:
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Click to expand...
Click to collapse
That is almost exactly what happened to me. I considered doing the same thing but don't really want to chance getting busted for a rooted phone

i've never flashed a radio update, i'm too chicken lol.
the quickest way to brick any phone is a f'ed up radio flash. or pulling the battery while flashing a radio.
i would take it to sprint and tell them you accepted a over-the-air update and then your phone shut off and this is what happened.

Help!!! Phone wont power up!

all i did was install CM7 nightly 41 after a full wipe, all went well. then installed titanium backup, restored all apps, then went to recovery and installed gapps, powered back up, and it tried to sync and it froze up, so after a while i pulled battery and pow no power!!! uh oh? any ideas?

Does it light up when you charge it?
Sent from my HTC Desire Z/G2 Using XDA Premium App

nope. i think its a total brick.
when i plugged it into computer the computer did attempt to install software (bubble on lower right of screen near clock that pops up saying new hardware found) but failed to install properly

holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more

tackleberry said:
holy crap tmo takes up to 7 days for an exchange to be shipped!!!! wtf???
verizon gives free 2 day exchange via fedex. tmo does it for 20 bucks for 3-5 days!! unreal. im starting to hate tmo more and more
Click to expand...
Click to collapse
Yea.. I hate that too. It doesnt really take that long though. You should get it in 5 days the latest.
Sent from my HTC Desire Z/G2 Using XDA Premium App

yea i bought a nokia prepaid X2 as a spare so i can at least get email. my old spare isnt great its a nokia 6310i lol. it works great as a phone but nothing more.
according to ups ground, its 4 days from texas to me, so tuesday i should see my refurb crap again lol.
just irritating, they wanna charge 20 bucks for 3 day shipping....verizon charged 10 for overnight and free for 2 day. unreal. i just dont understand how it failed like that. i did nothing different when changing roms! my phone was running like crap after i wiped and installed virtuous sense on it, so i wiped again and flashed CM back on, and it just bugged the hell out! any idea why it would brick like that?

Holding power+volume down doesn't work?

This may sound silly. But have you tried a battery pull?

You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App

ionic7 said:
You seem kind of stupid, you supposedly brick your phone and before anyone can try to help you call tmobile and tell them to replace it, then complain about how long it takes them to replace your screw up.
Sent from my HTC Desire Z/G2 using XDA App
Click to expand...
Click to collapse
And in the process make the cell phones and rate plans cost more for everyone else cause yet another a-hole wants there warranty honored when they knowingly VOIDED the warranty. Getting so tired of this. Between people bypassing paying for tethering and OVERLY taking advantage, and bull**** like returning phones that you KNOWINGLY VOIDED THE WARRANTY WHEN YOU ROOTED AND INSTALLED THAT CUSTOM ROM on it, it is ZERO wonder why they all want to sign the god dam bootloader anymore. These may be evil corporations were dealing with, but there is still a difference between right and wrong. These few on xda will ultimately be our downfall. This thread is all kinda fail.
Edit: sorry for sounding so harsh but you could have waited for at least a LITTLE bit of help first. it sounds like something not that out of our league to have fixed.
Sent from my HTC Vision using XDA Premium App

Edit: double post. Everytime I go to edit on the new xda prem app I accidentally hit quote!

battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.

We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
tackleberry said:
battery pull yes, vol down and pwr nothing. charged it overnight, and led didnt even power up, tried 2 different batteries, etc. nothing.
i dont know why it bricked, i did nothing different than what was done before to it. any time i ever did have problems was with the bootanimation screen would stay on and device would never boot, but i was still able to fix that with a full wipe and fresh reinstall. this was maybe a hardware failure of some sort? ive done all the same stuff to my mt4g (went from iced glacier to CM7, been on CM7 since nightly 6 or 8 with that one), and for a longer amount of time now and no issues at all. funny thing is i dont even flash nightly, or weekly...usually about 10-14 days ill flash an updated newer rom. now i know some of you people here are major fanatics about flashing nightly, changing radios constantly, kernels, amongst other things...i do half of that stuff and at probably a tenth of the rate that some of you hardcore folks do. so before you wanna pass judgement, i have been doing this same stuff since november on 3 different phones and never had a problem since yesterday at random. so i dont know why some of you get pissed when people have defective equipment. id guess if my hinge broke you would be telling me it was because of flashing roms too??? my rom was already flashed, working, and then when email was syncing it locked up, did a battery pull and nothing worked since. get a grip folks, crap happens. its not like i improperly flashed a non sense rom direct over a sense rom then back again with no wiping, clearing cache, data, etc etc etc then flash 3 incorrect kernels and bad themes and so on. if my device at least would power up, i wouldnt have decided to have it exchanged under warranty because i probably would have been able to fix it somehow since there are write ups about semi bricked devices. even plugging it into the computer does nothing now.
Click to expand...
Click to collapse

Loaded rubiX, freaked out, now am i FUBAR?

Alright so I flashed rubiX, but it started going haywire. Volume started flipping balls, then it kept going in and out of honeycomb (when you press home and it zooms out). Also my home and menu button lights were really dim and flickering. So I SBF'd it back to stock, so I was then running a completely stock, new, fresh droid x. I began to root via z4 and since my battery door was off it accidentally came off. Now I m stuck on the motoroala M bootscreen. I can get into bootloader, i can SBF, but even after SBF flashing, nothing. Holding Home+Power button does nothing. Help me out fellows! I shouldn't be rooted at this point since the battery came out during rooting. Ideas? I need my phone for tomorrow, I will be up all night.

Should I take it back to Verizon? I need to know before I get off work. It never rooted, but the z4 root app is on there. Will the void because of that?
LET ME KNOW!

If it doesn't boot they wont be able to tell. I would recommend taking it to Verizon

Thank you sir. I mean it is literally completely stock, bootstrapper and z4 apps are on it, but i sdf'd it 5 or 6 times. Just going to cross my fingers and bring it to verizon

Yes I have gotten my phone to a point like that in the past. I took it to Verizon, and they didn't even ask what happened they just gave me a new one

You sir are a scholarly gentleman. Leaving work now.

Thank you very much. I do try

Isnt it "a gentleman and a scholar"? Lol
Sent from my DROIDX using XDA App

haha I guess. So I will be taking it back to Verizon tomorrow. If they ask if i rooted ill be like wtf is that?
THe sbf should have cleared everything, right?

Yes the sbf should clear everything. And if the employee knows enough to ask about rooting, they are usually sympathetic as they probably do it themselves. So you are all set

Sounds good. Leaving for verizon store right now, ill tell you whats up when i get home

Got it coach! They're overnighting it, will be here monday!

Sbf'd 2.3.4 and now stuck on bootloop

Need to take my phone back to att for a faculty gps and after reading around here i found out it might hard brick it.
Well i didn't hard brick, but i am stuck on boot loop.
Any help?
It goes to the att boot animation, then goes back to the Motorola logo one...
I used a File called 2.3.4_pudding_preroot or something like that.
I had a similar problem once and re flashing fixed it, which ill try when i get home from errands, but i wanted to post and ask for suggestions i til I get back to try it.
Im gonna stop at an att store and see if they can give me a replenished one, but i doubt that...
There is probably a thread related to this somewhere too, but im posting from Tapatalk so its hard to look around. Lol
Thanks in advance!
Sent from my Xoom using Tapatalk
Sent from my Xoom using Tapatalk

At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App

yokozuna82 said:
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Is there a number for motorola warranty you have? How do I start the process?
Sent from my Xoom using Tapatalk

Just left the att store. There is apparently a DSC (device support center) about 10 miles from here and they'll just replace the phone on the spot. Hopefully they won't say anything about the 'unlocked' text.
Let you know what happens
Sent from my Xoom using Tapatalk

In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!

CSharpHeaven said:
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
Click to expand...
Click to collapse
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk

Got a new phone. GPS works. Gonna have to sbf again for Unlock and pre root now. Hopefully this one will work out. Lol...
Is there a way to Unlock and root without sbf??
Sent from my Xoom using Tapatalk

razorseal said:
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Good to hear that. Please make sure you will read the following thread once you got your new Atrix. I get GPS lock in the UK within seconds. I even managed to get GPS lock indoors. A must for every handset really.
http://forum.xda-developers.com/showthread.php?t=1239713