Related
I know I have Few or no posts at all... but I am quite experienced with Android OS... I wish i could have contributed more to this forum before asking for help on such an INTRICATE problem.. Anyways
The rundown is this, in the sequence in which the things occured... Today i set my phone down, (Droid X, Rooted, Running Apex 1.4.1) and it was working perfectly fine. I then pick it up, absolutely nothing had been done to it between me setting it down and picking it up, and the hard buttons (Menu, Home, Back, Search, Volume Rockers, Camera Button) all not working, only the lock button on top. So, I think like I always do, Battery pull time. I preform a pull, and turn the phone back on, then it's stuck on "M", just stays there. I pull again, stuck again, nothing, one more time and it goes to stock recovery mode just the Android and Exclamation triangle, (I have clockworkmod installed) but of course, no hardbuttons are working so it's false hope. I press buttons over and over out of frustration and I bring up the menu, but that's all i can do, and i have to hold the Volume rocker down, and search to even do that, but besides that i can do nothing more. So I'm stuck at what I see as a dead end, can't move through recovery because buttons aren't working for whatever reason, so i can't flash SBF, or stock reset... So I'm asking for help, please.
wunsung said:
I know I have Few or no posts at all... but I am quite experienced with Android OS... I wish i could have contributed more to this forum before asking for help on such an INTRICATE problem.. Anyways
The rundown is this, in the sequence in which the things occured... Today i set my phone down, (Droid X, Rooted, Running Apex 1.4.1) and it was working perfectly fine. I then pick it up, absolutely nothing had been done to it between me setting it down and picking it up, and the hard buttons (Menu, Home, Back, Search, Volume Rockers, Camera Button) all not working, only the lock button on top. So, I think like I always do, Battery pull time. I preform a pull, and turn the phone back on, then it's stuck on "M", just stays there. I pull again, stuck again, nothing, one more time and it goes to stock recovery mode just the Android and Exclamation triangle, (I have clockworkmod installed) but of course, no hardbuttons are working so it's false hope. I press buttons over and over out of frustration and I bring up the menu, but that's all i can do, and i have to hold the Volume rocker down, and search to even do that, but besides that i can do nothing more. So I'm stuck at what I see as a dead end, can't move through recovery because buttons aren't working for whatever reason, so i can't flash SBF, or stock reset... So I'm asking for help, please.
Click to expand...
Click to collapse
have you tried getting it into bootloader mode?
hold vol - + camera + search while powering the device on
if you can get into bootloader mode than you can flash an sbf file
If you tried everything you can think of and still can't get it to do anything take it back to verizon. If you can't get it to work I doubt most of the employees at verizon would be able to get it to work either
Did you try a long battery pull. 30 seconds or more?
Sent from my Droid
Pull the battery and then.plug the phone into.the wall charger. Then put the battery back in, and when the phone boots up it should boot to clockwork
Sent from my DROIDX using XDA App
Did this work?
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
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!)
Hello everyone!
I have a Samsung Galaxy S Vibrant, and I had successfully flashed Onecosmic's ICS_4.0.3.0(RC3.1)_Vibrant_Full.zip.
It worked fine for about a month, sometimes it did just black out and I had to remove battery and reboot it, but nothing serious.
But tonight it just went black and now when I try to power it on this is what happens...
1) "Vibrant" and "SAMSUNG" appear for about 2 seconds
2) Blacks out for about a second
3) "Vibrant" and "SAMSUNG" reappear for about 5 seconds
4) Blacks out. The bottom "buttons" light up if I touch them, and if I keep the power button pressed for 10 seconds it does reboot, but it doesn't boot up Android.
I dont know what I should do, if any of you know a way I could boot it up at least once more to backup some stuff, that would be great.
Any help will be appreciated... Thanks!
Try going to recovery and flash from again.
iPhone killer!!!
Yea, I might do that, I just didn't wanna lose all my data, and some recently-added phone numbers =/
Don't factory reset
iPhone killer!!!
BrKiller said:
Hello everyone!
I have a Samsung Galaxy S Vibrant, and I had successfully flashed Onecosmic's ICS_4.0.3.0(RC3.1)_Vibrant_Full.zip.
It worked fine for about a month, sometimes it did just black out and I had to remove battery and reboot it, but nothing serious.
But tonight it just went black and now when I try to power it on this is what happens...
1) "Vibrant" and "SAMSUNG" appear for about 2 seconds
2) Blacks out for about a second
3) "Vibrant" and "SAMSUNG" reappear for about 5 seconds
4) Blacks out. The bottom "buttons" light up if I touch them, and if I keep the power button pressed for 10 seconds it does reboot, but it doesn't boot up Android.
I dont know what I should do, if any of you know a way I could boot it up at least once more to backup some stuff, that would be great.
Any help will be appreciated... Thanks!
Click to expand...
Click to collapse
did you make a nandroid? you could just use the advance recovery an put back the system without touching the data
or if you didn't you could make a backup the flash the Tom again then advance recover from cmw and put back the data
hope it helps, good luck
And as far as numbers go, you really should be syncing them with your Google account. Than You will never worry about this again.
Sent from my Touchpad using xda premium
And you really should learn to use odin.... and read
sent from the xda app on my android smartphone.
BrKiller said:
Hello everyone!
I have a Samsung Galaxy S Vibrant, and I had successfully flashed Onecosmic's ICS_4.0.3.0(RC3.1)_Vibrant_Full.zip.
It worked fine for about a month, sometimes it did just black out and I had to remove battery and reboot it, but nothing serious.
But tonight it just went black and now when I try to power it on this is what happens...
1) "Vibrant" and "SAMSUNG" appear for about 2 seconds
2) Blacks out for about a second
3) "Vibrant" and "SAMSUNG" reappear for about 5 seconds
4) Blacks out. The bottom "buttons" light up if I touch them, and if I keep the power button pressed for 10 seconds it does reboot, but it doesn't boot up Android.
I dont know what I should do, if any of you know a way I could boot it up at least once more to backup some stuff, that would be great.
Any help will be appreciated... Thanks!
Click to expand...
Click to collapse
You will probably need to Odin it back to stock. Read this thread. And while you are Odin'in check to make sure you are following each stop to the letter. As you probablly flashed a GB bootloader, to get your ViBrick into download you need to: Open Odin. Then connect your usb cable to your phone and computer. While the USB is plugged in and Odin running press and hold volume down + Home + Power. Once the black screen comes (flashes) release the Power Button. Then it should get into download mode. After that use Odin accordingly to flash back to stock.
Sometimes that just happens. Try letting it sit for a little while(10 minutes should be plenty). This happens to me sometimes and after a while it will randomly boot. It's very strange.
Sent from my SGH-T959 using XDA App
I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?
It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.
It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.
Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!
Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.