Related
so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)
can you select to boot normally from fastboot? or hboot
nope...i can't move selection while in fastboot... i'm pressing vol+- but nothing happens... probably because it thinks trackball is pressed all the time...
I had the same thing happen with my power button. I had to send the phone back to be repaired and it took almost two weeks.
I don't know if anything has been posted yet but I remember someone saying the N1 has the same trackball as one of the blackberries. Maybe there is a guide on swapping them or even just disassembling it to clean.
well... sending it back (from serbia to usa) is definitely not an option, partly because it would probably take at least month to get it back, partly because i don't want to risk having to pay duty&tax when it comes back.
disassembling, however, is an option, and i will do it if no one has better idea
thanks for replies anyway...
alt+64 said:
so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)
Click to expand...
Click to collapse
When you press it does it make the clicking noise? if it doesn't, replacing the trackball wont fix your issue. The trackball popple that registers the click when a short is made is depressed fully and is always making a short. you either have to rebend this popple or replace it entirely. You need something similar to this
When you press it does it make the clicking noise?
Click to expand...
Click to collapse
yes it does... click, feedback... everything is exactly the same as it was...
btw... i'm at home now, so i connected it to usb and managed to boot with "fastboot reboot"... problem is that it boots into safe mode (i guess it does it if you hold trackball during whole boot process) so i cant open any 3rd party apps which makes it kinda unusable...
btw2... scrolling with trackball is working normally.. clicking does not
i guess ill take it apart and try to disconnect trackball completely..
any last thoughts before disassembling?
some witchcraft happened today, and my trackball is kinda working now, but phone keeps booting to safe mode...
taking battery out for 2 minutes, as some suggested, didn't help, and neither did holding trackball while booting... any other idea?
did you try factory reset?
yes... no luck...
so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm
tried ur methode on my bricked magic ... no luck
did u have the blue led with no hboot or recovery ...make sure ur battery is charge some
thatruth132 said:
so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm
Click to expand...
Click to collapse
I can't understant why doing that the device has unbricked, I probably must do the same.
anyone else tried?
is this really working???
can anyone other than the OP confirm this works? what showed up on the screen when it was bricked? Did it have the 'arrow coming out of the box' symbol, when the phone was switched on?
i did nt get big arrow or anything my phone wouldnt boot period all i kept getting was a blue light no fastboot or adb would work until i did this the only reason i tried it was because someone mentioned to me to replace the track ball i dont know why but it worked
Did you happen to remove the little battery when you did this?
no i only disconnected the cable leading to track ball the if u look where the track ball is you can pry and pop out the track ball i did it just to look around in there ...i am not a tech but i do have a basic understanding of somethings and i think for some reason in my situation it may have reset something i really dont know but my phone was a brick for half a day with me trying to use google as my friend typing away at fastboot and adb commands only to get nothing ..but when one person told me i may need a new track ball i just decided to look inside on how that a bad flash would effect the track ball but i did what i did and i am back using my phone but i did notice one thing today i had put my phone in fastboot and the normally when it loads those command or whatever about loading img. ...its now saying no image
Thanks, I will try this. Unfortunately I gave away my battery and cable... I still have doubts about this helping me, as I flashed the wrong radio. Where as you just flashed a bad update.
did u use a 32b radio
thatruth132 said:
did u use a 32b radio
Click to expand...
Click to collapse
hi,
quick question. my friend rooted the phone and then flashed hardSPL but i think it was the wrong one. the last thing we saw was a box with a arrow on it and the phone has been dead ever since.
was this the same for you ? we would love to be able to unbrick his phone.
brick
hi,
i have a 32b magic, and since yesterday it just doesn't startup anymore.
i just get a black screen, with backlight on. (also no adb/fb/recovery)
if i hold trackball while power on, i get the blue led
i've searched, but haven't found any similar problem, cause i don't get that box with an arrow.
to unbrick this, you just disconnected the trackball?
pls be more specific
HEEEELLPPP!
fakecaker said:
i just get a black screen, with backlight on. (also no adb/fb/recovery)
Click to expand...
Click to collapse
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287
The OP likely had a stuck trackball.
Holding the trackball when you power on puts you in the blue-led mode and doesn't let you do anything else. Being in blue-led mode doesn't mean you are bricked, it's just a mode in which the phone can start up. If the op's trackball got "stuck", it would explain his problem. Replacing the faulty trackball likely is what solved his problem.
It would be nice if the OP could update the first entry to reflect as much.
If your phone isn't voluntarily going into blue-led mode on it's own, this "fix" likely won't do anything for you. You still have a brick... like me
ezterry said:
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287
Click to expand...
Click to collapse
hi terry ...
quick question.
the jtag de-bricking that everyone is mentioning is said to work with g1/dream/g2 ... is this also possible with the magic(sapphire) 32A ?
like i said my friend bricked his loading hardSPL and the phone is charging and i can get into the blue led mode no problem.
if it is possible would the pinouts be the same or similar for the magic? i am quite keen to give it a bash if i can be pointed in the right direction.
thanx in advance.
Thank for you response
but i didn't flash any new spl or something else.
i had my phone working fine with spl/radio/rom.
but then i shut down, and after that i couldn't power up
i reboot my working magic with froyo and then is dead.
its keeps rebooting and no fastboot or recovery mode only if i press trackball and on the phone i got blue led, any solutions ???
Regards Sn00py
But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?
ale922 said:
But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?
Click to expand...
Click to collapse
Who are you asking, the OP? They just had a stuck trackball, so they couldn't boot normally.
It doesn't matter, just continue.
hello all, i need help again this time.
let's get to the point.
this morning, i tried to charge my G1 because the battery has yellow color.
when i charged the phone, after around 5 minutes, suddenly my G1 restart itself and then after the "G1" logo, the screen go all black, sometimes not all black but there's a little glitch (white-green-purple-all little colors.)
the phone got heated on the bottom part everytime i power-on it, even just on battery (not charged).
i tried "Camera + Power", it's only getting to that red-blue-green-white screen that shows :
"DREA100 PVT 32B
HBOOT - 0.95.0000
CPLD-4
Radio-2.22.23.02
Sep 2 2008
Serial0"
Click to expand...
Click to collapse
and it stops there for AGES . won't do anything.
i tried "Home + Power", i tried to hold down that two buttons for 25 second more, but it keeps normal boot, shows G1 logo, and then black screen again.
i tried "Menu + Power", it just the same as "Home + Power"
my G1 has never been rooted, it's all original, i haven't done any system upgrading-downgrading things.
the charger is the original one, original from htc
the battery is new, i've just changed it one month ago.
that's all the informations that i can give.
so, anyone can help me solving this problem?
if its not rooted or anything than that means its HTC's fault not yours. and since you cant access the recovery menu to flash a new rom or recover a nandroid backup, it sounds like you're up ****s creek with a turd for a paddle.... unless somebody has developed a way of flashing without recovery. in other words; get a new phone or send it in to t-mobile.
Get an SD card reader an put a DREIMG.nbh on your sdcard to downgrade to RC29 (push power+camera, select confirm), then wait for the OTA to push you to DMD64. You will loose all your data but at least your phone will work.
Alternatively, after downgrading to RC29 you can exploit the bluetooth bug to gain root access, and after that install CM5.0.8 and be twice as happy with you chunky old G1.
mejorguille said:
Get an SD card reader an put a DREIMG.nbh on your sdcard to downgrade to RC29 (push power+camera, select confirm), then wait for the OTA to push you to DMD64. You will loose all your data but at least your phone will work.
Alternatively, after downgrading to RC29 you can exploit the bluetooth bug to gain root access, and after that install CM5.0.8 and be twice as happy with you chunky old G1.
Click to expand...
Click to collapse
okay, i think i'll try this one.
just another information, i've tried another combination of buttons, such as hold down together "Call + Menu + Power" and then slide quickly to Home button, but it's giving no effect too
dioadi said:
okay, i think i'll try this one.
just another information, i've tried another combination of buttons, such as hold down together "Call + Menu + Power" and then slide quickly to Home button, but it's giving no effect too
Click to expand...
Click to collapse
Call+Menu+Power is for a reboot while the phone is on lol. Only other way is "blue light mode" which is trackball and power, but I don't feel like explaining it to you=p.
mejorguille said:
Call+Menu+Power is for a reboot while the phone is on lol. Only other way is "blue light mode" which is trackball and power, but I don't feel like explaining it to you=p.
Click to expand...
Click to collapse
ohh, to be honest, i've tried the Call + TrackBall + Power too, yes the LED light up blue, and then nothing happened while the LED still light blue.
dioadi said:
ohh, to be honest, i've tried the Call + TrackBall + Power too, yes the LED light up blue, and then nothing happened while the LED still light blue.
Click to expand...
Click to collapse
Nothing is supposed to happen unless you have a JTAG afapter. And why the hell post in two different forums?
mejorguille said:
Nothing is supposed to happen unless you have a JTAG afapter. And why the hell post in two different forums?
Click to expand...
Click to collapse
wow, i guess JTAG Adapted would be another long explanation, huh?
yes i made two posts. You know that sometimes, some people prefer to go to just specific thread/subforum, ignoring the other thread/subforum.
but who know if that people can help me?
hey, i'm back.
after days to days downloading DREAIMG.nbh again and again, finally i got the right DREAIMG.nbh, not corrupted one.
and yes, i successfully update, all stuff are signed "OK" , and then i press the action (trackball) button, restart the phone, and guess what? it turns back to the beginning problem, still. "G1" logo, and then turn to whole black screen.
so, now what?
am i bricked?
or is it hardware problem? (remember i said that everytime i turn on the phone, the down part, near sim card, is always getting heated)
the only screen that can be accessed is that rainbow screen and the update screen (Camera + Power).
dioadi said:
hey, i'm back.
after days to days downloading DREAIMG.nbh again and again, finally i got the right DREAIMG.nbh, not corrupted one.
and yes, i successfully update, all stuff are signed "OK" , and then i press the action (trackball) button, restart the phone, and guess what? it turns back to the beginning problem, still. "G1" logo, and then turn to whole black screen.
so, now what?
am i bricked?
or is it hardware problem? (remember i said that everytime i turn on the phone, the down part, near sim card, is always getting heated)
the only screen that can be accessed is that rainbow screen and the update screen (Camera + Power).
Click to expand...
Click to collapse
im pretty sure the heat issue comes from the processor, not the sim card. mine does that too. its nothing to worry about as long as you havent overclocked your device (mine is overclocked and works great aside from gettin warm during heavy usage.) what happens when you plug the phone into usb? does it show the SD card or can you get into the android sdk? its a long shot as i doubt you can get into debug mode without having a uncorrupted os, but i guess its worth a shot.
BuddhaTeh1337 said:
im pretty sure the heat issue comes from the processor, not the sim card. mine does that too. its nothing to worry about as long as you havent overclocked your device (mine is overclocked and works great aside from gettin warm during heavy usage.) what happens when you plug the phone into usb? does it show the SD card or can you get into the android sdk? its a long shot as i doubt you can get into debug mode without having a uncorrupted os, but i guess its worth a shot.
Click to expand...
Click to collapse
the phone can't get into the home screen, it's always going blank after Tmobile-G1 logo.
so when i plug the phone into usb, it's just charging, no SD card recognizing on my computer.
And how can i get into Android SDK ?
Google is your best friend.
Sent from my HTC Dream using XDA App
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!)
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.