Possibly bricked phone - Motorola Droid 4

So I tried to safestrap cm10.1 onto my Droid 4. But, I was much more familiar with a previous version, not with the touch interface and stuff. I did what I thought I had to do: Create a partition, install the zip to it, reboot.
But, to my horror, when I rebooted, I was greeted with a black screen (backlit). I couldn't turn off the phone by holding down the power button either. I had this problem once with my Droid 3, and I 'solved' it by just taking the battery out. But I know things are much more 'locked-down' back there with the Droid 4, so I didn't want to do that.
After a little while, the thing just ran out of batteries. I was hoping to charge it up again. When I plugged it into a wall, I got the little battery icon, which I thought was definitely good news. But now I can't even turn it on, or get my computer to charge it!
UPDATE: I'm going to try using fastboot

Have you tried booting into fastboot and then flashing the stock firmware to the phone?
Also to reboot the phone when it freezes, you can hold the power button and volume down together for about 10 seconds.

Related

[Q] Strange Reboot Loop, searched forum Not Addressed

Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD

Captivate is freezing after trying to disable voodoo lagfix

When I tried to disable the voodoo lagfix my phone froze, after about 20 minutes i decided to pull the battery and now the phone freezes when trying to boot and even after plugging in the charger, it freezes on the battery load symbol. Unfortunately, the 3 button way to get to the recovery menu doesn't work. help me please??
I'm having the same problem - phone just hung on the kernel load screen (firebird 2) after trying to shut off lagfix - although I can get to a red recovery mode menu. Not that it's helping at this time. It would be nice if I could recover without a clean wipe of the phone.
Anyone have any ideas. I'll be scouring the threads...
You could try making a jig and flashing to stock http://forum.xda-developers.com/showthread.php?t=841512
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
I'd really like to do this without hardware, but making a jig kinda sounds like a fun project and i do have a soldering iron in storage somewhere...
xsamxoxo said:
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
Click to expand...
Click to collapse
I'm afraid not. This happened to someone I know and they told samsung the OTA update bricked it and AFAIK they fixed it for free. They never tried using a jig though, so if you don't want to wait to replace it or anything you could try a jig since it might work and the parts are pretty easy to get (and if you'd be replacing the phone, a jig is ALWAYS good to have anyway)
Just another note to throw in there, the computer recognizes the phone, but strangely my computer freezes while trying to read the media storage drives. I can't tell if the internal sd is mounted because of the ever-lasting wait but i'm almost positive its not.
Do adb commands work?
Sent from my SGH-I897 using XDA App
Thnikk said:
Do adb commands work?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, it says "error device is offline"
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
avgjoegeek said:
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
Click to expand...
Click to collapse
it connects even though the phone is frozen. I'm heading over to "The Shack" pretty soon and just making a jig.
Thanks for all your help everyone.
Edit: Just confirming that with much dedication and a steady hand I finally have my captivate up and running with the help of the resistors. I also flashed the 3 button fix stock rom.
Well, I kept trying the least invasive methods first. Tried to reflash Firebird. Then went adb and such. In the end, it was pretty clear that it had hung at the lagfix correction, and I was dealing with a file system error. I was eventually able to get into download mode. The hardest discovery was finding that I had gotten the wrong drivers from samsung. The ones in the [stock rom] odin master clear page were what I should have been using. When I loaded those, the computer recognized that I had a phone and not a "serial gadget" and then I knew I was close. Odin finally saw the phone, and a couple tries at "light" re-stocking failed at file analysis, so I did the repartition (aha, file system error), and it shot through the whole process and I had my phone back and flashed to Serendipity in about 20 minutes.
But I would like to know about the red menu. That was unexpected (blue for standard, green for cwm).
No need for a jig. I had access to some phone functions, most importantly, download mode.

[Q] HELP!! Stuck in LG boot logo!!!

Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
tchabalie said:
Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
Click to expand...
Click to collapse
Did you install Clockwork on it, or just rooted?
If you only rooted it, try performing a factory reset.
This can be accomplished by holding volume down and power until you see the screen change to "Clear data and factory reset?".
Press power to confirm.
You will lose your data, but your phone should return to normal.
Just rooted, no clockwork. I will give it a try! thanks!
Tried your suggestion...just keeps flashing and vibrating. Any other suggestions?
Did you ever see the factory reset screen?
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
tchabalie said:
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
Click to expand...
Click to collapse
make sure you are holding it long enough. You have to continue to hold the power and vol button for sometime before you get the recovery screen.
As rooting will generally not brick a phone (it is the recovery mod that generally bricks), if you cannot get it, take it back tell them you woke up and it was on the charger like this. They should exchange it with out issue. (Do not mention that you rooted the phone)
It sounds to me like your phone is defective, it happens.
Another option is here: http://forum.xda-developers.com/showthread.php?t=1120062 .
I can walk you through it on IRC tonight if you're on around 12PM Pacific Time...
If not, there are guides for using LGNPST on the internet.
Good luck!
Thanks! Held the buttons down for a full 3 minutes and nothing. Is that long enough? Read through the other info you posted and boy does that look scary! LOL! I will try tomorrow when I have more time. Or maybe I should just return it since I have only had it for 12 days
try pulling the battery and holding the power key for about 30 seconds. my original droid use to do this from time to time and it always worked for me.
Thanks. Tried but it did not work. Ended up just returning it and getting a new one. Now I can start over! LOL Just came from the Samsung Fascinate and was pretty proficient in flashing roms and kernels. But I have to admit that I am a little confused with the process on the Revolution.
Not sure boot problem is related to root
I've had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen in the morning.
It seems a number of non-root users have this problem.
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
This morning is the first time, however, that I have this exact problem. For a few times this morning I was able to get to clockwork and restore different ROMs, but always to the same blank loop during boot. Now not even able to get to Clockwork or Factory Reset. I'm headed in to Verizon to try for a replacement. I'll let you know if they make any noises about rooting.
Getting back into Clockwork
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.
Returning Rooted Phone to Verizon
FYI, I returned a rooted, stuck in boot loop phone to Verizon yesterday. In the store they arranged the return and did not ask about or look for rooting in any way.
They did try a factory reset, which was not working in any case, so no signs of Clockwork.
Same problem, different results.
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
timus5 said:
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
Click to expand...
Click to collapse
Please don't necro threads....

[Solved] Hardware issue with power button

Build date 1007 - in service August 2010.
I've been running Pinnacle 1.2 (been on it since v1.0).
Just moments ago I've found the power button to be unresponsive. This happened after I rebooted into recovery, sticking me there for a while.
I was stuck in a recovery loop- pull batt, reinstall batt, automatic boot back into recovery.
Somewhere in the process of trying different combinations of battery pulls with cable installs and volume up/down holds (trying for download mode) I ended up finally launching the ROM, but w/o a power button all I can do is pull the battery, and the moment I do, the phone automatically wakes w/o even touching the power button (which is totally new to me).
Any input would certainly be appreciated.
My first order of business is to flash to stock (JF6, bootloaders and all if all else failed) but being that it automatically boots when the battery is installed I don't think even a jig would help...or is the beer steering me wrong?
I am confused. You can go back to stock or no?
I cannot get into download mode. The only way to power the phone off is via battery pull.
I cant flash anything from recovery because it says the power button is disabled (it is).
As I put the battery back in the phone boots immediately...I mean the at&t screen lights up my palm before I put the cover on or even flip the phone over.
Use an app from market to enter download mode? system toolbox free is one
Used Odin to go back to stock KF1 and still no power button. Now System Toolbox won't work w/o root/busybox. lol
Once my phone falls asleep I can't wake it back up.
It may seem obvious that the power button is physically broken but I don't know why the phone boots up as soon as the battery is installed...that was never the case before this issue came up.
watsa? Anyone?
Can anyone else shed some light on what would make the phone boot when the battery is inserted (happened at the same time the power button became unresponsive), essentially denying me the opportunity to get to download mode.
beyond this point I am consfused myself. I initially blamed Pinnacle and thought going back to stock might fix it which obviosly didn't happen.. It seems like your power button is always "pushed" so as soon as you pop your battery in phone reboots..
watsa said:
beyond this point I am consfused myself. I initially blamed Pinnacle and thought going back to stock might fix it which obviosly didn't happen.. It seems like your power button is always "pushed" so as soon as you pop your battery in phone reboots..
Click to expand...
Click to collapse
On a second thought if it was the case then power button should have messed up functioning of your phone even after powering on. So I am consfused more. Need a hardware expert here
I'm preparing myself to deal with my beloved phone finally letting me down after all the success we've had...it's just really bad timing as I'm currently unemployed, broke and only 13ish months into a 48 month contract.
Ok, so after a physical tear down it seems to be in the external plastic of the button itself?
After removing the outer case and reinserting the battery I noticed it did not automatically boot up. I pressed the actual power switch/button that is connected to the board and the phone then powered up. I let it finish booting and held the power button down and the power options menu popped up. I clicked Power Off and it shut down fine.
This means it certainly isn't Pinnacle ROM (never thought it was, personally), or software related at all. Now to figure out what is going on between the plastic external power button and the power switch on the board.
Edit: Nothing was there? I blew out the dust reassembled the phone and now it works fine. Weird.

[Q] stuck at "dual core" but now can't even fastboot?!

I bought one of the refurb'd bionic's a couple months ago. I've rooted and masked the wifi tether, but nothing else, no custom ROMs or anything. phone's been working great for the past seveal weeks since those changes were made, several reboots, etc. no problems until last weekend.
I randomly found my phone stuck on the "dual core" screen one morning. it must have rebooted overnight and been that way for several hours as it was quite hot. I did a battery pull and tried to turn it back on, got nothing. plug it in to the charger, nothing, no leds, nothing. several battery pulls later, still nothing. try to enter fastboot/bootloader by pressing power + volume up/done, nothing. plug it into the computer, nothing.
I'm sorta fearing its been hard bricked (though I have no idea why... i wasn't loading ROMs), except, the other day, after leaving the battery out all night, I was able to get it to turn on, it booted up to the home screen, but before it was usable, rebooted and was stuck on "dual core" again. messing with it some more, I eventually got to the bootloader screen. I wish I had siezed that moment, but i didn't. Messed with it some more yesterday, saw the 'dual core' screen again, but couldn't get it into fastboot. its very hit or miss and I can't do it consistantly, but on rare occasion, it does seem to want to come back to life.
any advice on what happened? where to go from here? and if it can get it back into fastboot? I'm hoping i can and rsdlite will recognize it and I'll try loading 902 fxz back on it, but sure could use some advice to save this phone... no insurance and it was a refurb thats been rooted, I don't think verizon will be too much help.
THanks
-Rob
Try this
Little known hidden key (actually button) sequence: press and hold both volume up & down then hold the power button ten seconds (five should work, but ten always gets it). You should boot into fastboot mode, then flash 902 using a USB cable. You do NOT need to delete data! Check the batch file and REM out or remove any line that says it will. Worst case, Motofail after that will give you access to your latest CWM backup, assuming you have one, just restore that once you have root.
What he said and also you may need to charge your battery.
Sent from my DROID BIONIC using Tapatalk 2
It could just be a dying phone, I came across an Atrix basically in the same situation. The radio in it had died, so the only way to boot the phone was to skip booting the radio, but if you hit the phone application it would crash the phone.

Categories

Resources