Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.
Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.
Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).
The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.
I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.
Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.
I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.
The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!
I always have to sbf my dx twice, I always boot loop the first time.
Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)
Related
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
erica_renee said:
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
Click to expand...
Click to collapse
I might try that soon, gonna keep at it. It's not a heat issue; it only runs a few secs before it shuts down. I know it's got something to do with me formating the data and not finishing the reset.
Have to ask, but is the bat flat or does it do it plug in.
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
SmittyRN said:
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
Click to expand...
Click to collapse
Well, I let it sit for a while, and instead of holding down the "-" key, I plugged in the keyboard and pressed the home key. Nothing seemed to happen, but when I turned it back on after that it booted up and let me go through the setup screen. Strange, but at least it's working.
shaun298 said:
Have to ask, but is the bat flat or does it do it plug in.
Click to expand...
Click to collapse
Yeah, sorry, I have no idea what you are asking.
tkirton said:
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
Click to expand...
Click to collapse
Yeah, it would say that the recovery key was pressed or whatever, just for about 1 sec, the shut off.
Hello, so my atrix was perfect like 2 hours ago. I ad neutrinos rom gt+ on it for like 2 days days and everything was perfect. But ! well i was playing a bit with it and deleted some stuff in the android folder of my internal sd, it was only real racing 2 game files and some other stuff. I played some more with it and my screen started flashing strangely and doing weird stuff. I closed the screen, i opened back same thing. The phone shutted down itself. I tried rebooting and now im stuck at the red m logo with unlocked in the top left corner. i tried to access recovery by doing a battery pull and rebooting but i dont have access to the little menu. Anybody can help me fix this?
Silly question but are you holding down the volume down rocker button during boot? Do you get the prompt for fastboot, android recovery, etc ?
If it pops up scroll down using volume down to android recovery and hit the volume up to select it.
Should be able to fix it from there.
When i hold down volume down button there is absolutely no prompt pf any kind =\ i already installed some stuff with cwm and i had to go through there, but now i have nooothing =(
pyfviperx said:
When i hold down volume down button there is absolutely no prompt pf any kind =\ i already installed some stuff with cwm and i had to go through there, but now i have nooothing =(
Click to expand...
Click to collapse
Did you update to the latest firmware? If so it might be wise to see about reflashing that same firmware again with RSD. It's a pain in the arse and you might have to do it a few times to get it to work right, but it is possible. I had the latest build CM7 on my atrix and I reflashed to stock just to see if I could.
I'm not kidding though when I say it's a painful process, the phone might get stuck in a boot loop (where it goes to the M Dual Core logo and just reboots). If that happens you're still okay cause you can just keep reflashing the stock .sbf file till it takes (just don't downgrade).
Your call though.
Meh today its completely dead, i checked it today and all ihave is green led =(
Edit: Plugged it in wall charge instead of computer, back to M logo =(
Unlocked bootloader so best not to use RSD. Can you get fastboot? Reboot and hold volume up instead of down.
Sent from my MB860 using xda premium
Just tried, my battery is completely dead. So i pressed power and volume up then i putted battery in ( at this point i still didnt had any boot) and i plugged in my usb charger, nooothing... Just the red m logo and the nice little unlocked in the top left corner...
pyfviperx said:
Just tried, my battery is completely dead. So i pressed power and volume up then i putted battery in ( at this point i still didnt had any boot) and i plugged in my usb charger, nooothing... Just the red m logo and the nice little unlocked in the top left corner...
Click to expand...
Click to collapse
Find a friend with an Atrix and use their phone to charge your battery, or try going into an AT&T store and asking if you can charge it there on a display phone.
Im in canada =/ but one of my friend got an atrix, ill charge the battery with his phone BUT back when my battery was still charged i still couldnt get to fastboot/recovery power+up and power+down didnt worked neither. Is it hard bricked?
Il also ordered stuff to make a motorola factory cable, think i will be able to do anything with this?
Still seeking help guys! I loved my atrix please help me to recover it :/
pyfviperx said:
Still seeking help guys! I loved my atrix please help me to recover it :/
Click to expand...
Click to collapse
Well, if you can't get into either recovery, fastboot, or rsd mode you won't be able to fix it. Make sure you're pressing the volume down button as you boot the phone, and keep it held down until the options come up.
Sent from my MB860 using xda premium
Help me, XDA Developers, you're my only hope. I've tried everything else, and no luck. It just keeps getting worse.
First off, my girlfriend and I recently purchased a used Motorola Defy to replace her broken G1. When the guy we bought it from showed it to us, it was working perfectly. We put her SIM card in, and it was fine. So we paid for it, brought it home, and everything was fine. We set up the phone, and quickly realize that the old owner's account was still registered, and the only way to unregister them was to reset to factory defaults. And this is where everything went to hell.
Shortly afterwards, the phone became very irratic. It would only turn on when it decided to. The LED light would SOMETIMES light up when it's plugged in, but not all the time. And when we managed to get it to turn on, it'd either get stuck at the Motorola logo, or go all the way in and then freeze up about two minutes later. I figured it might be the firmware. Maybe the original owner had installed a custom ROM without telling us, and resetting to factory default had messed up somehow. So I decided to (possibly re-)root the phone, and install Cyanogen. After 500 startup attempts, which was just enough to get it to turn on 3 times, and configure root setup and install the bootloader, I am now completely unable to get the phone past bootloader. What's worse is, even though I've got the Cyanogenmod install file on the microSD, Clockworkmod can't mount the card. At all. It is now taking even more attempts to turn on, and it refuses to get past the recovery console/clockworkmod.
TL;DR: It keeps getting worse. I'm half expecting it to turn into a pile of dust by the time I'm done trying to fix it, and everything I do that SHOULD make it better just makes it worse. Please help D:
Update: The phone will no longer even turn on... In order to get the LED to turn on, I have to remove the battery, unplug the phone from the USB, replace the battery, then replace the USB. I don't think that's helping...
See you have a full battery and try to flash stock froyo sbf.
The sbf: http://forum.xda-developers.com/showthread.php?t=966537 (chose any froyo sbf form there fe CEE DEBLUR)
How: somewhere here http://forum.xda-developers.com/showthread.php?t=1216982
After the flashing with RSlite go to stock recovery and wipe data(factory reset) from there. (see how in above threat)
It could well be that he had an outdated custom rom that wasn't able to do a good factory reset from settings. Tho I advice you to take a look at CM7 or a MIUI ROM cause it is really much better then the stock rom's. Everything takes less time and on the CM7.2.0 stable release there are less bugs than in the official rom.
Please report back
Still trying to get it to turn back on. But if I do, I will try that. thank you.
Try pressing Press power+Vol up. You should get into bootloader mode. If you don't get white tekst, your battery is to low. The easiest way to solve that is to find someone with a defy and loan it's battery for a day. Then do the Press power+Vol up and connect to rds lite... (read further is all-in-one defy beginners guide).
If you can't find someone with a defy, you can go McGyver (There is a link in the Wiki page or just google)
Well, I *was* getting the error on the bootloader saying battery too low. So I left it to charge for a bit, now I'm getting absolutely nothing. Not even lighting up anymore... -sigh- I don't think there's any hope for this thing...
UPDATE: Well, after leaving it for a few minutes, I managed to get it to light up. Right back to the "Battery Low Cannot Program" message. -_-
Another update: Won't charge. Still getting the same damn error.
MacGyver'd the **** out of it. Got to the bootmenu, successfully installed Nordic, now running beautifully. Thank you so much for your help, I was about ready to test this thing's physical durability. D:<
DJLols said:
Well, I *was* getting the error on the bootloader saying battery too low. So I left it to charge for a bit, now I'm getting absolutely nothing. Not even lighting up anymore... -sigh- I don't think there's any hope for this thing...
UPDATE: Well, after leaving it for a few minutes, I managed to get it to light up. Right back to the "Battery Low Cannot Program" message. -_-
Another update: Won't charge. Still getting the same damn error.
Click to expand...
Click to collapse
You need to get a fully charged battery, i've heard of people cutting their wires or something to charge the battery, but once it has enough of a charge you can flash it with RSDlite like labsin said,
I had this problem too. RSDlite is the only thing that'll get it to boot up again, and then
"You need to do a data wipe. Press vol- and power. You will get an exclamation mark and android. It is the stock recovery. Next press both vol+ and vol- together. You will enter custom recovery. Do a data wipe from there.. That should help.. "
Good luck!
That's exactly what I did, actually, and it worked like a charm. Thank you, though. ^_^
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Kippyyy said:
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Click to expand...
Click to collapse
Yup just rsd the sbf back. You will lose everything however so hopefully you've got a backup somehow. Here's the sbf
http://db.tt/H2RuCD8h
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
I've had a similar problem as you with my flipside. Are you sure you're using the right key combination to get into rsd mode? If you can at the very least get it into bootloader mode by holding down the volume + key while holding the power button, I'm sure you can get it into rsd mode.
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
Theres a post here somewhere that has the combo of keys needed to get into bootloader mode. Sorry dont have it saved. Just do a search for it
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Kippyyy said:
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Click to expand...
Click to collapse
Did you by any chance have the stock launcher app frozen and using a different launcher? Just seems if you are seeing the backlight that possibly it is on the home screen but the launcher is corrupt? Not sure.
I'm not entirely sure. I assume it's stuck in the bootloop because when I power it on the backlight changes shades and then vibrates to signal the screen past the motorola M. Then I can touch the screen and feel a vibration to simulate to slide to unlock and if my usb cable is attached my computer makes the noise to signal it sees my device, but moments later my computer dings to signal device disconnected and my phone goes through the above process again.
I feel as if I can get to the factory reset screen and such because if I time it right I can stop it from doing anything mentioned above and it just hangs as if in a menu of some sort. The downfall is I see nothing and the backlight only appears.
I may just have to scrap it and say well done phone. I can't seem to find a similar issue anywhere on the internet. All the other issues can make the bootloader screen appear and that appears to be my number on problem.
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Kippyyy said:
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Click to expand...
Click to collapse
Yes like straight out the box. The backlight issue just seems to me like a launcher problem but that wouldn't explain why you can't get into bootloader mode. Hmmm strange. Here is another way I just thought of. If it connects to the computer (you said you hear the beep) reflash it via Motorola's site. All the instructions should be there (if they still support it)
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Kippyyy said:
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Click to expand...
Click to collapse
Yup that sounds like hardware failure. Haven't ever heard of the screen going out on the flipside but the atrix forums are full of them. Maybe you can get your upgrade early. Good luck
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.