Database Users

I need some serious help.

My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.

Help?
Please?

Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?

Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.

well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.

Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.

Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.

Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.

uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.

ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping

Bleh. I'll just have to wait and see. I'll contact HTC.

tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...

Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?

Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.

Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.

Did you tell them you have an unlocked bootloader?

uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em

lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.

How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?

Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.

Phone won't charge and won't turn on. Suggestions?

I don't know what just happened.
My phone has syndicaterom 1.1 and visionkernel 1.2. The phone was hanging for some reason so I held the power button down and pressed reboot. It isn't turning on. The red light doesn't come on when I plug it in.
Does anyone have any suggestions?
I have the tep. Will they replace it without me paying anything, even though its rooted and romed? Can they even tell now?

fhurricane said:
I don't know what just happened.
My phone has syndicaterom 1.1 and visionkernel 1.2. The phone was hanging for some reason so I held the power button down and pressed reboot. It isn't turning on. The red light doesn't come on when I plug it in.
Does anyone have any suggestions?
I have the tep. Will they replace it without me paying anything, even though its rooted and romed? Can they even tell now?
Click to expand...
Click to collapse
I had same issue...but with the power off instead of reboot..but it might be related...Ive pulled battery plenty of times with no issue..but this once i decided to poweroff and this happened :/

If it were me I would yank out the battery for a minute then put it back in. Next, I would either try to boot it or put it into download mode and flash stock back in and see if it boots. If a fresh install from odin of a stock rom doesn't fix it then I suspect the phone is hosed. I don't think that's the case if I had to guess. Stock recovery and kernel and rom. Like I said, if that happened to me, that would be my next step to troubleshoot myself if the phone is bricked or what. If that doesn't fix it then I would think that it might be permanently bricked. If that was the case I would take it to a sprint repair center and tell them the phone locked up while trying to turn it off. I pulled the battery out for a minute or two and tried booting it up but nothing happened. Before you get there, take out your memory card. Don't offer any more information and don't act like you know what's going on. I did that and it worked for another phone. Be brief in explanation of what's going on, don't try and help them, keep my mouth shut and only answer questions if asked. Don't go into great details. Have a old backup phone with you to activate if they want to keep the phone to test or send back. If not, you might be without a phone for a few days.
When the replacement comes, power it up and play with it for a minute before leaving to make sure everything works and looks good. If there's a problem with the replacement phone, it would be best to point that out before leaving otherwise you will have to go through this all over again. Sometimes refurbs have flaws or stuff that doesn't work so cover yourself.

See the other thread in general about this, other people with the same problem, running the same rom/kernel configuration. Unfortunately nothing fhurricane suggested for troubleshooting worked for me. Time to go down to the Sprint store!

Please see the other thread on this topic, and please note that the ROM has absolutely nothing to do with it. Thanks!

Possibly Hard-bricked?

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!)

[Q] Defy Won't Boot, Options Exhausted: You Are My Last Resort.

I originally posted this over on the MotorolaDefy.com forums, but it seems to be pretty dead, so I'm going to quote over my post and then update it with what I have tried since.
Generally, I don't like to post on forums asking for assistance, I know how many repeat problems you guys probably have to read, but I don't know what else to do at this point. I've had my Defy running Cyanogen Mod for months, and earlier today I noticed the Wifi wasn't connecting properly, so I rebooted it. Lo and behold, it became stuck at the Cyanogen Mod screen, it might have something to do with me installing BusyBox earlier in the day. In anycase, I followed this guide: (link removed, since this is my first post - not really important since I figured out the McGyver trick) to attempt to fix the problem. Now the phone won't boot at all, I can't even get to the boot loader screen. RSD Lite still recognizes the phone when it is plugged in, and the white light still comes on when it is charging. I'm scared ****less to take any further actions without input from somebody with more experience. I have to head out to work now, but I wanted to post this before I left. If anybody has a solution to my problem (and I'd be grateful), then I'll attempt it in a few hours. All I'm trying to do is reset it to factory default so that I may reload Cyanogen Mod onto it. The phone worked beautifully up until this point. I am on Telus and I live in Canada, if that is at all relevant. Thanks!
Click to expand...
Click to collapse
So, since then, I've gotten my screen working again, I had to use the McGyver trick (gypsy-rigged usb cable to the contacts of the battery) to jump start the bootloader, and I managed to flash in the Froyo 2.2, 3.4.2-179 sbf. It ran! Thank god in heaven! But... it got stuck at the T-Mobile logo consistently. Next, I tried flashing in Froyo 2.2, 3.4.2-177 sbf. Again, it miraculously boots but it hangs at the pulsing Motorola logo.
That brings me to where I am currently, which is; I have absolutely no idea what to do next. All I want is to get my Defy up and running with a stable version of Cyanogen Mod again. It ran flawlessly before and I loved my phone, best phone I've ever had. I'm stressing out pretty hard, and I've tried all I can find on the internet. Please, XDA, help me!
Edit: I doubt this is relevant, but more information can't hurt, so I'll add that my Defy is one of the newer ones with the red-lense.

Have you remembered to wipe data and cache (factory reset) in stock recovery?^^
If you still have that data from when you ran cm7, and you're trying to boot stock, it could prevent you from booting! Happened to me once and i just couldn't see what the problem was! Really annoying.

That sounds like it could be the issue, you're supposed to be able to do that by holding volume down while powering it up, correct? Because that doesn't seem to do anything for me.

Not working? Strange. Hold volume down before pressing power button and keep it pressed untill you se a warning triangle. Then hit both volume keys to enter the recovery. Still not working?

Sorry, I should have been more specific, I can get to the little Android guy and exclamation mark, but when I touch the bottom right corner, no menu comes up. I've never actually had to access the stock recovery before, Cyanogen made it so simple. Am I supposed to be doing something other than tapping the screen?

Update: Google is my friend. I found a suggestion that I hit the up and down volume buttons at the same time, and the menu appeared! I wiped the cache and all the use data (important stuff is on a memory card anyway, I'll just have to get my contacts back). I did get an error, reading: "E:Can't mount CACHE:recovery/log". I rebooted the system regardless and IT BOOTED!
Thanks for pointing me down the right path, I owe you and this forum a great debt!
I'm now going to charge this bad boy back to full before I attempt to reload Cyanogen. (Since having wires hang out the back is starting to get old.)

I managed to short out something doing the McGyver trick, because I'm getting the question mark battery problem. Hopefully it's an issue with the battery and not the phone. I'm incredibly disappointed, the phone is fairly new and I loved it, and don't have the money to drop replacing it since there are more urgent things to attend to. I guess all I can do is hope for the best.
As of now, it won't even boot. I'm going to try the battery in a friends phone and his in mine to try to identify the problem.

Lunk23 said:
I'm going to try the battery in a friends phone and his in mine to try to identify the problem.
Click to expand...
Click to collapse
I always recommend THIS solution over the McGyver method. Defy is farely often owned phone, so guys... first of all, don't let the battery drain completely; second - if this happens, don't rush into jump starting it. Try all other options first, ask somebody to recharge your battery and don't do McGyver, unless you've run out of other options.
Now try connecting your phone to the wall charger and don't try to start it for at least an hour. I've had plenty of cases when brand new Defy, Defy+ or Atrix, that have never been rooted, leave alone jump started, show the battery with "?" in it when battery drains completely and takes some thirty minutes or so of charging until the phone is able to start again.
Good luck, my friend!

I had made this. .... just in case it can help you
http://forum.xda-developers.com/showthread.php?t=1551472

Motorola Droid RAZR/Cyanogen mod problem?

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.