Can somebody tell me what happened to my motorola atrix?It just suddenly turned white screen...i only got it for at least 2 weeks...it's like the lcd has been damaged but i haven't dropped it not even once...
have u rebooted it?
Can you post a pic of what it looks like?
I already have rebooted it...I did the restore factory setting and even did the hard reset..nothing works...
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place. Have you considered flashing the phone back to stock?
http://forum.xda-developers.com/showthread.php?t=991072&highlight=sbf+flash
which one do i download?the 1.2.6 or 1.5.2? or is it both?
By the way my phone was pre-rooted when i bought it..may i ask how would i know what drivers should i use?32bit or 64 bit?thanks
Use 32 bit if you have a 32 bit computer, or 64 for 64. And flash 1.2.6 with rsd life, ota to 1.5.7, then ota to 1.8.3
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
OTA is over-the-air (no computer required). What I suggest is a fresh data factory wipe along with flashing of 1.8.3 SBF (or if you want 1.5.7 to OTA). Whatever suits your fancy.
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
Follow the directions in my previous post to flash your phone back to completely stock software. Once that is done, go to Settings -> About Phone (bottom of the list) -> System Updates. You must be on wifi to download the updates. First, it will download an update to 1.57 (I don't think it goes straight to 1.83). Download and install that update following the prompts. Once that is done, do it again to get the 1.83 update. Now you have a fully up-to-date, and hopefully functioning screen, Motorola Atrix.
Since you are flashing back to stock, I recommend using gladroot to obtain root on the phone. This will avoid the formatting of your internal and external storage that gingerbreak rooting method would require. Gladroot files and instructions here: http://forum.xda-developers.com/showthread.php?t=1016060
Basically these are your steps:
Flash 1.26 SBF
Run gladroot.bat
OTA update to 1.57
run afterupdate.bat
OTA update to 1.83
run afterupdate.bat again
The batch files I referenced are in the gladroot download.
jimbush3 said:
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place.
Click to expand...
Click to collapse
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
GoodFoot said:
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
Click to expand...
Click to collapse
Quite true. I was thinking of an impacted screen and not so much of design/production issues. I'm curious to see the outcome now too.
It didn't work...is there any other way?by the way my phone became unrooted after the process
by the way not all of it is white...during the opening of the phone where the logo of motorola comes up the line is colored purple and the icon of contacts when somebody is calling the line is also purple..
It sounds defective. Did you say you bought it rooted? Somebody might have dumped off a bum phone on you.
Sent from my MB860 using XDA App
I dont think there's something wrong when i bought it...It's still fine for 2 weeks..is there any other way?can overcharging did it?there's time that i charge it overnight..
Two things:
I have replaced 4 screens on my girlfriend's Motorola a1200 and 3 years later is still working. Screens go bad AND the internal cable can loosen over time and cause your problem. eBay usually has new screens for under $20.00 and you can Google for instructions on how to do it. It's actually fairly simple and you probably just need to re-seat your current screen cable. I seriously doubt it's anything other than a loose cable or worn out screen.
Sent from my SAMSUNG-SGH-I897 using XDA App
Can't be worn out screen...i just got it for at least 2 weeks..by the way whenever i browse my phone not all have this white screen like when i access the messaging page
I guess i'll just have to stick with it for a while...btw i found a useful apps that help me on my phone..it's called screen filter..while its activated the white screen can't be seen that clear and i read that it help conserve battery so it's like hitting 2 birds with one stone..anyway thanks for the help guys.
Related
For the most part I have read that the replacement phones are not harware locked. The few that come back that are hareware locked are the exception to the norm. Is this true from those of you who have gotten a replacement phone?
I'm curious about this as well since I have one on the way...any ideas?
Sent from my SGH-T959 using XDA App
I soft-bricked my phone that was hardware locked and had to order a replacement. My new one is not hardware locked.
bigragu said:
I soft-bricked my phone that was hardware locked and had to order a replacement. My new one is not hardware locked.
Click to expand...
Click to collapse
can you tell if it's a new or refurbished one?
No. Do you know how I could tell?
Hey there! First post and maybe I get to help someone?
I haven't replaced my phone yet, but it started out unlocked and ended up hardware locked after rooting using the OCLF V2+ and then un-rooting by reversing the procedure (was in a panic regarding the OTA update).
Not sure if that's an "unintended feature" or just something boneheaded I did, but I don't think it had anything to do with the JI6 update as I haven't seen any notifications yet - seem to still be JFD.
I found out I was hardware locked when I tried to re-root again later in hopes of making a backup should catastrophe strike OTA. Resumed panic mode until I found this thread: forum.xda-developers.com/showthread.php?t=802763&page=2
The files posted by untermensch there reportedly resolve a hardware lock.
I was trying figuring out how to actually use these files in the stickies when I stumbled across this alternate method of rooting, and opted to try it out first. Easy-peasy: forum.xda-developers.com/showthread.php?t=786877
So now I'm rooted and was able to perform a nandroid backup , though I checked and I'm still hardware-locked... I reckon if the day comes I want to fix that for some other purpose I'll sleep easy knowing that method linked above is there to fall back on.
[EDIT]: apologies for the formatting above... evidently I'm not permitted to post links to within the forums yet
in case you're wondering, there IS a fix for hardware lock in the dev section.
Heres the thread:http://forum.xda-developers.com/showthread.php?t=804305
I just swapped my sim and sd to my replacement phone. It is definitely not hardware locked.
The only thing different I've noticed is the sticker underneath the battery cover looks different than the one on my original vibrant. It looks sort of generic. I remember the original having a samsung graphic on it, where as this looks very plain, with just a minimal amount of text on it.
It did get the ota software update minutes after I swapped over. Runs decent.
Sent from my SGH-T959 using XDA App
allthrottle said:
I just swapped my sim and sd to my replacement phone. It is definitely not hardware locked.
The only thing different I've noticed is the sticker underneath the battery cover looks different than the one on my original vibrant. It looks sort of generic. I remember the original having a samsung graphic on it, where as this looks very plain, with just a minimal amount of text on it.
It did get the ota software update minutes after I swapped over. Runs decent.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
cool good to know I have read some ppl have had problems running the hardware fix. It would be nice to have a excape plan lol. Is there any way to tell if that one was refurbished I only ask because you brought up the sticker issue. Either way it is a lot better than my bricked phone
So I had originally put the leaked non-rooted GB update on my X2 with no issues. I had been running that for a few days when I decided to replace it with the p3 pre-rooted version. I did an SBF back to Froyo without issue, did the Gingerbreak, etc. The pre-rooted version went on fine with no errors, but then when it came up, the digitizer was unresponsive.
I did several factory resets, SBF back to Froyo again (several times), but the digitizer is still unresponsive....I now can't get past the setup screen. I also noticed that the emergency dial button has a blue highlight around it, and when I press the power button, the "Power Off" item in the menu has a blue highlight around it....almost like if I had a trackball or arrow keys, I could move the highlight....I wonder if it knows the digitizer is not functioning?
Has anyone else seen this? I see one thread on the Motorola site where two people have the same issue after updating the GB (presumable the OTA version since they are posting on that site), but no helpful responses.
My phone is only 3 weks old, so I am tempted to just SBF and try to get a replacement out of Verizon, but thought I would check here first in case I can fix it....or figure out what went wrong so it doesn't happen again.
i'm 1 of the people thats having the SAME EXACT problem as your having............ive sbf'ed like 100 times (no joke) and factory reset about as much............i'm just goin to take it back and hope i can get a replacement..............
I called Verizon and I was on my exact "30 day" since I bought it, so they are shipping me out a new one overnight. I have insurance, so I could have gone through them I suppose if it was after 30 days, but at least I'm getting a brand new one. Now I just have to decide if I'm willing to try it again.
So if more than one person has this issue, I'm guessing it is NOT a hardware problem. However, it is odd to me that doing the SBF doesn't fix it. I wonder what could be happening, maybe someone with more knowledge about this will be able to shed some light.
Unless we figure out what happened and how to potentially fix it, this seems pretty close to a bricked phone. I wonder it is something in the GB update in general, or something going wrong in the manual update!?!?!
Don't these phones have some type of manufactures warranty?
Edit: The phones carry a one year warranty wether or not you purchase insurance. If the hardware fails, as it has in your cases, they will replace it for free.
Sent from my DROID X2 using XDA App
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
blickley said:
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Not All Android Phones Are Built The Same.
I noticed you didn't say you factory reset after you sbf to 2.2.2 in your original post. I don't claim to know for sure but some people are not following this direction, and it MAY be one of the problems. It is recommended that all directions are followed exactly for a successful update. The only way to tell if there is a problem with the method is if everyone follows it to the letter.
Sent from my DROID X2 using XDA App
Thanks, yes I did factory reset after the SBF. Oh well, this doesn't seem to be widespread and I got a brand new X2 out of it.
I just received my phone and noticed an odd screen issue after updating the firmware:
Notice the slight line around the screen. The odd part is that I do not see the line when I have a white screen, I also do not see it when I am in clockworkmod nor do I see the lines when the boot screen is loading.
Is my screen going out or what?
I had this problem with my first Atrix and I searched high and low with no workable solution. Some say it is a firmware issue. Honestly, there's no fix to my knowledge, without forking over some cash for a new digitizer. Only option is to get another one or another phone Lord willing. Apologies. Well, unless you can bear with it. It doesn't effect performance from what I saw, but it's annoying and no matter what I couldn't ignore it as if it wasn't there.lol
#Sent from my God given Atrix 4G
phreshy said:
I had this problem with my first Atrix and I searched high and low with no workable solution. Some say it is a firmware issue. Honestly, there's no fix to my knowledge, without forking over some cash for a new digitizer. Only option is to get another one or another phone Lord willing. Apologies. Well, unless you can bear with it. It doesn't effect performance from what I saw, but it's annoying and no matter what I couldn't ignore it as if it wasn't there.lol
#Sent from my God given Atrix 4G
Click to expand...
Click to collapse
Well I can deal with it as I got a pretty good deal on the phone (off contract via ebay) but it is still very annoying. If I can deal with it till November, I am eligible for an upgrade from ATT (with some money of course).
I would definitely blame it on the firmware. If you are getting crazy lines all the way through you could probably blame it on the video. I see this all the time at my work. Try a hard reset, back up your data.
Cheers
Burrito
Burrito Bandit said:
I would definitely blame it on the firmware. If you are getting crazy lines all the way through you could probably blame it on the video. I see this all the time at my work. Try a hard reset, back up your data.
Cheers
Burrito
Click to expand...
Click to collapse
Thanks!! I will try to fully upgrade the firmware to 4.5.141 instead of stopping at 4.5.91.
How would you go about upgrading the firmware if you already unlocked the bootloader and rooted the device? If this is indeed a firmware issue, how would I go about this. I searched the forum and found a lot of conflicting answers. If you could provide me with a good link, I would appreciate it.
Thanks
I am thinking about following this in the morning when I have my phone fully charged and I was wondering if you see any issue with running this?
http://www.android-advice.com/2012/fix-bricked-motorola-atrix-after-ota-update/
My phone is not bricked but I want to revert to stock (locked bootloader, remove root, etc) to see if the issue is indeed a firmware issue. Then I can re-unlock the bootloader, enable root again and restore or reinstall CM9.
Thanks
comhack said:
I am thinking about following this in the morning when I have my phone fully charged and I was wondering if you see any issue with running this?
http://www.android-advice.com/2012/fix-bricked-motorola-atrix-after-ota-update/
My phone is not bricked but I want to revert to stock (locked bootloader, remove root, etc) to see if the issue is indeed a firmware issue. Then I can re-unlock the bootloader, enable root again and restore or reinstall CM9.
Thanks
Click to expand...
Click to collapse
You will not ever lock the bootloader once unlocked. All you can do is hide the unlocked text. It is a fuse that gets burned when unlocking the bootloader.
pre4speed said:
You will not ever lock the bootloader once unlocked. All you can do is hide the unlocked text. It is a fuse that gets burned when unlocking the bootloader.
Click to expand...
Click to collapse
Ok, I am not worried about the unlocked text, all I want to do is update to the official firmware.
comhack said:
Ok, I am not worried about the unlocked text, all I want to do is update to the official firmware.
Click to expand...
Click to collapse
Can't help there. I'm done with crapblur. Staying on cm roms now. You could go with nottachrix, his rom is based off 2.3.6 and you can choose full blur or blur removed when installing.
Well I think I hardbricked my phone anyway --
Failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot protocol support
Battery is too low to flash
Click to expand...
Click to collapse
Granted the battery did run out of juice but not until I finished upgrading the firmware:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
I made sure not to flash lower than the original 4.5.91
Pretty much before I got a chance to install clockworkmod again, the battery died. When I went to restart the phone to go into SBF, I got the above message. I tried booting the phone without the battery in it and it says the "Failed to boot 1" (since I do not have a rom installed yet) but if I try to run fastboot, I get the battery is too low to flash.
I am not for sure if this is a hardbrick or if my battery is just dead but I have charged it for about an hour so far with the same message.
I ordered another battery before this incident so I should get another next week but I am so worried that I hardbricked my device and I will not be able to recover.
Frick!!!
I am so screwed...... I cannot get it turn on with just the battery in but I can disconnect the power cable and the screen stays at Failed to boot 1.
I am at a loss as I have read a ton of threads here on the "battery too low to flash" but none of them are same as my issue. I really do not know what I can do as I bought the phone on ebay for $200 and just received it yesterday.
Well now I have it plugged into my computer and the screen is off but now the green charging light is on again. The computer recognized it as a usb device called MOBOOT and the Motorola USB Networking driver miniport is showing up in Device Manager.
Any ideas?
I am using this method (post 2) DIY active micro-usb cable to battery posts (post #2 method) to charge the battery for a few hours:
http://forum.xda-developers.com/showthread.php?t=1528729
Then I will will try to continue the OP's method to recover my device.
I cannot believe it, this method fixed my issue with "Battery is too low to flash"!!!
I am now in the process of flashing the firmware via RSD Lite.
I had an issue with the Bluetooth and wifi radios on my original atrix so I bought a used one. the used one had an issue similar to yours though not as severe.
I finally got around to replacing the actual LCD with the good one and problem is gone... I don't think it's firmware related, more than likely, hardware is the culprit.
xandr115 said:
I had an issue with the Bluetooth and wifi radios on my original atrix so I bought a used one. the used one had an issue similar to yours though not as severe.
I finally got around to replacing the actual LCD with the good one and problem is gone... I don't think it's firmware related, more than likely, hardware is the culprit.
Click to expand...
Click to collapse
Actually the screen is really not that bad as the camera I used shows the lines much more than they appear.
BTW how much did the lcd cost and where did you buy it from?
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
From what I gather, you can SBF back down to 2.3.4 with no problem. There may be a certain way you have to do it though. I have never been on stock 2.3.5 so I cant tell you from experience. But Everyone says it's possible.
That's my question in a nutshell
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Excolo said:
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Click to expand...
Click to collapse
So you have never used an SBF file? If you would have used it on your broken Droid X2 when it wasnt acting right, it might have fixed your phone. An SBF file simply wipes everything of your phone (excluding your SD card) and flashes brand new software on it. The SBF files are provided by Motorola so its not like you are using something made by a dev and can break your phone easily. You should be able to use RSD lite to flash the 2.3.4 SBF file and you should be fine. But then again, I have never SBF'd from 2.3.5 to 2.3.4 personally so I would feel bad saying go ahead with no worries and something bad happen. So wait for someone else to respond first.
Thanks!
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Excolo said:
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Click to expand...
Click to collapse
Yeah, it does sounds like it was a hardware problem. Actually, I never thought about if motorola had a list of sbf files somewhere or if they were just leaked or what. I always downloaded them from threads like these. I just know they are made by motorola. You got me curious now. hmmm...
Duh
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Excolo said:
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Click to expand...
Click to collapse
What's An SBF File?
• SBF Is A File Leaked By Motorola That Is The System Image Flashed By RSDLite.
Taken from the Motorola Droid X2 FAQ page here
Excolo said:
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
Click to expand...
Click to collapse
bro, you wont have any problems downgrading/sbfing back to 2.3.4, i did it without any problems
i used sbf_flash through linux though idk about RSDLite
I have a Droid Razr that had a small accident that left the lcd screen shattered, but the Gorrilla glass intact. I now use this phone with my Lapdock and it works perfectly. My problem is that I have been trying to find a way to upgrade the phone to JB with the leaked version that got released on Christmas Eve.
The screen doesn't not work at all. The soft buttons work fine and so do the external buttons. Both ports work as well. The screen does not light up nor does it accept any input. The lapdock will start up as soon as the phone gets completely booted.
My question is there a way to upgrade the phone from ICS to JB without using the recovery menu. I can't navigate the recovery menu, so I can't install the zip file. If I had the two original files that came from the cache system folder, I could just reboot the phone and it would upgrade, right? If that is the case, does anyone have those original files that I could download?
I would love to upgrade this phone now instead of waiting for the OTA. Newer is always better.
By the way the phone got slammed in the house door and the frame is bent, so there is no fixing the phone at this point. The only use is to use it as a permanent dock on my lapdock 500.
Thanks to anyone that helps me or for even reading this post!
Do you suspect that you are able to select the options however can't see what you're doing? in that case I would search a video tutorial for a generic similar installation and simply follow the same steps using their screen as your guide.
joemas said:
Do you suspect that you are able to select the options however can't see what you're doing? in that case I would search a video tutorial for a generic similar installation and simply follow the same steps using their screen as your guide.
Click to expand...
Click to collapse
I thought of that and tried it without success. I don't know how far through the process I get, cause I can't see the screen, but I suspect it might be when I am trying to get from the Android to the recovery menu. I really don't know if I get to it on the first try or not. It is such a crap shoot. You just don't know if you make a mistake or not. very frustrating. Thanks for the reply.