Related
Hi everyone, I'm new to this forum (first post), I've owned my Continuum for a few months now happily with no problems. I actually love the phone! But recently I ran into a pretty big problem...
Let me give you a little background on my phone first, I have used SuperOneClick on it, to grant super user permissions, I've used the program to grant me access to the phone tethering apps that are out (currently using Open Garden), and the AdFree app in the market. I havn't used anything else in regards to 'hacking' my phone so I'm a bit confused as to why I'm getting trouble.
Anyways here's my problem, lol! Well the other day I turned off my phone and tried turning it back on and I would get a grey battery with the spinning disk, and it wouldn't turn on :\! I tried holding all the buttons, for over 10 seconds, no avail. It still turned on to the battery and nothing. I tried taking the battery out for a whiiiile and nothing. Eventually I plugged in my phone to the wall and it magically worked. Actually that's the only way I've been able to get my phone to turn on lately. It works fine once it's on but every time I turn it off the same thing happens .
So that's truly why I'm here... Is my phone 'bricked', or are these some symptoms of being 'bricked'? Are there any fixxes I can go about taking to you know...fix the problem ?
Any help would be Greatly appreciated,
Thanks everyone,
-Matt
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
Can you try taking out the battery, then putting it back in...
Then hold down the volume down key as you power it back on?
I would try un-rooting and doing a factory reset... that should eliminate software issues... If you're still having issues then take it to VZW and let them give you a new one.
This is not "bricking"... If a phone is "bricked", it does nothing, absolutely nothing, and the only way to make it useful is to use it to build something.
Sure, right now it says "Downloading... Do not turn off Target!!!".
Thanks for letting me know it's not bricked, that's a little reassuring .
After a while I just took out the battery and stuck it back in and attempted to turn on the phone the usual way, and it turned on just fine. I'm guessing it's fixed and hopefully it won't do that again.
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
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. ^_^
I was headed home today and my Sprint Galaxy S4 shutoff. It would not come back on, so i removed the battery. When i reinsert the battery, my phone does a quick vibrate, then the white Samsung Galaxy S4 logo screen appears, then disappears, then thats it. Nothing else happens. I have tried different chargers, a different battery, tried download and recovery mode. Nothing has worked so far to get me any further. When i try to go into recovery, blue writing shows in the top left that says Booting Recovery, then it shuts off and nothing else happens. When i plug into a computer, the phone does not connect to the computer.
I am usually pretty good with anything to do with a phone, but this has me stumped.
I have not downloaded any new apps or any different roms or kernels anytime recently. My phone is rooted but still on the stock rom. This phone was rooted about a year ago when i got it, and as far as roms or programming or anthing, nothing has been done to it since then.
Does anyone have any ideas?
Ok so i was wrong, the phone will boot into download mode, but only for about 2 secs, then it goes blank and off again. So it seems like some sort of power issue with the phone itself, as in hardware. Not sure that there is too much that i can do about that, but does anyone have any ideas?
I just read something on here about Samsung having a bad batch of batteries. If I were you I would take my battery to someone that could test it to see if it is holding a charge.
Had the same issue. The dude at sprint said it was a bad update that went out but not sure how true that is due to the fact that i was running a custom rom and recovery. I was running clockword mod recovery and latest CM11 nightly. If you have the insurance I'd say bring it back and they should replace it.
Any fix?
I have just been experiencing this problem as well. My s4 was working fine then all of the sudden the power button would become very sensitive and would think I would want to turn the phone off. I would click the back arrow but the phone would still either turn itself off or reboot. Then it got worse and would get stuck in bootloops. Now I have to reinsert the battery every time for it to turn on. It gets to the samsung logo and then shuts off. I can get into recovery for about 2 seconds and then it shuts off as well. My s4 is not rooted at all. Can someone please help me? I really don't want to pay at least 70 dollars for samsung just to look at it.:crying:
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.