I'm scared that I may have lost one
I rooted with z4root, which seemed to go well. I downloaded rom manager (paid version) and flashed cwm. I had some trouble booting into cwm so i did a little investigating and ended up downloading bootstrapper as well. After enabling boot strapper I was able to get into CWM and do a nandroid backup.
I downloaded and flashed to newest CM nightly (8 I believe), and my phone seemed to be happy (it did want to power cycle when I was signing on to my google account at first, but after skipping the step in the set up wizard of the phone and just adding the account after it worked fine.).
I went to bed and did not plug the phone in. I woke up and saw that it was on still and proceeded to play a video game. I heard it beep across the room an hour later (no one around it) and figured it was getting low on battery since it had not been charged. When I picked it up to check the time, it would not start up. I have pulled the battery several times, tried to boot into cwm to flash my back up (could only get into the factory recovery), and I seem to be getting less and less response as time progresses. My power button doesn't seem to be producing any effect now and I can only get the screen to come up and display the big moto "m" if I plug the phone into a charging dock. I did charge my battery in my brothers OG droid since I heard that it wont charge the battery if it doesn't start up.
I'm by no means an expert, but I've had very successful rooting experiences with my Dinc (even soft bricked my Dinc, had a heart attack, then brought it back from the brink with help from this web site), a Thunderbolt, and a couple of fascinates. Never imagined a nightmare like this. Best part is this D2 is a loaner from my boss while I wait for my Charge to come in the mail!
Any help would be immensely appreciated.
ps. The only oddball variable that I can think of in this mix is that I'm using my micro SD card from my Dinc which had at least one nandroid left on it (which I deleted in Rom manager). I wonder if rom manager (or me... most likely me) got confused and possibly tried to flash cm7 for the Dinc from my SD card. User error, the story of my life.
try plugging the phone into a wall charger and leave it for a while. the charge window will come up
Yeah, battery power seems to be the simple answer to my power button not being responsive. I hijacked my brother's battery and my D2 powered up to the "M" screen and froze with just the power button press, or will boot into stock recovery (holding X on the keyboard while depressing the power after a battery pull), though I don't seem to be able to do anything effective from there. My battery is currently in my brothers droid charging as I continue to look for a solution/hope for more leads from this thread. Being able to consistently get a response from the phone is a step in the right direction though.
Have you tried powering up the phone into bootloader? That'd be a quick way to know if your data is corrupt. I went through that whole process last week. Only thing is that your battery can't charge in bootloader so make sure your battery isn't low.
Sent from my DROID2 using XDA App
If you're talking about holding the X key and power, then yes. This will bring me to the stock recovery menu. If there's an action that can be preformed from the stock recovery that will help me, I'm unaware of it. I know from cwm I would have the option to restore from a back up that I made (I have a stock back up and a back up from as soon as I got the phone up and running with a cm nightly rom).
I'm hoping that when I plug the phone into my computer it will be recognized. I read the instructions on how to run rsdlite here and aside from being able to navigate my phone menus to put it into usb mode, I should be able to take care of everything else. So now my real questions are; If my computer sees my device, is running the rsdlite program my best solution, and what's the next step if my computer does not see my phone?
try this
your phone will gharge if you put it in bootloader mode i know because ive done it now if you phones rom is jacked then flash it back to stock with rsd lite you can get the a955 stock rom from here this web site or my droid world also it will work there is noting wrong with your phone take care chris
Related
I did search, both here and google, and have not come across a similar problem.
I picked up a nexus s 4g recently and unlocked the bootloader using fastboot oem unlock, flashed clockwork mod recovery on, and installed cyanogen 7. I then found out I'm a complete idiot because that rom was made for the GSM phone, and the radio doesn't work.
Tried to use fastboot to load an original rom back on, which failed, so found a windows machine and installed Odin, followed a tutorial on how to flash back to stock, Odin reported a pass, but the phone will no longer turn on.
No amount of taking the battery out, button combos, or charging has changed this.
I had about 70% battery when I tried to flash with Odin, so I'm fairly sure it's not a battery issue.
I also tried to adb devices with the phone hooked up, and nothing was found, so it shouldnt be an unresponsive screen.
Help?
did you make a nand?
I did not. Not sure if it would help, because I can probably download someone elses nand but I don't know how to do anything with it with my phone not powering on
I could be completely wrong about that, not very familiar with nandroid.
You can't get it into download mode?
Correct.
Essentially the phone is dead, it will not respond to anything.
Very similar to the battery not being installed, but I know for certain the battery has a charge.
I just checked the battery, and I retract my previous statements. 560mAh and 3.08 volts. Would that be low to the point of it not taking a charge through the charger?
I have it on a special charger directly on the terminals right now, I will post results once its through.
Read in the fascinate forum that a guy purposely flash a rom from a different device ans used Odin to revert back, also he gave a tip that one should keep trying to use Odin if the first try didn't work. Not sure if this will help never happened to me...
Sent from my Nexus S 4G using XDA App
Fully charged battery did not help
Try what they used to suggest with the epic when it was stubborn. Remove the battery. Plug the usb cable into the phone then into the computer. Try to put it into download mode. If that doesn't work, I can't think of anything else. If you have insurance, maybe they'll swap it when they see it's dead for a refurb. Be nice and play dumb. Tell them something like it froze one time and you pulled the battery and after that it wouldn't turn back on.
I could use my insurance, but its $100 bucks now. Sprint really changed their policy on that.
I also don't really want a refurb phone, when mine was NIB 3 days ago. I realize it's my fault but still.
Need a little help here. The other day I turned on our old D2 BC I need aa replacement phone and its given me hell. First boot it went into the Liberty boot animation and wouldn't stop looping. My girl rebooted into recovery and flashed Liberty again and apparently it was working fine which I did not know. When she did this she didn't tell me so I was under the impression I needed to do what she did. I went to recovery, wiped and flashed Liberty, I believe its 2.0. Now I can't get it to even go into recovery. The only thing that happens is sometimes when I plug it in to a power source it will go straight to a liberty screen and just sit there. Not even an animation. Any ideas? I'm fixing my Ubuntu right now so maybe I can access ADB commands from there. It won't detect on Windows.
Sent from my Nexus S 4G using xda premium
update: I finally got this phone to do something and idk how? I have tried to let it charge for a few days now and I'm thinking that 'somehow'(???) the battery got f'd up because just now when I plugged it in to finally try to connect through ADB, a black screen popped up. at top it Read: Bootloader > next line > D2.37 then at the bottom two lines that read Battery Low, Unable to Program. ....any thoughts? other than a new battery?
you need to get the battery charged with another phone or an external charger (stay away from homemade chargers as they can mess up stuff). What happened is the battery got too low to either start or finish sbf'ing so it went to bootloader and the phone won't charge without software so until you charge or buy a charged battery you are stuck. It's very fixable but you are stuck.
Hey, so I have the infuse 4g on JB 4.2.2, and I want to get it back to a stock 2.3.5. I have looked at every forums, but I want to know if it's possible to do so without a computer. Is there a .zip package that I can just flash as a normal rom to make it go back to normal?? Thanks!!
You have to have a computer to return to stock because ICS and newer use different partitions for everything than gingerbread. Flashing with Odin on a computer includes a file that tells the phone the old partitions and allowing it to run gingerbread.
Sent from my MB300 using xda app-developers app
I am running my phone with the 1.275 release of the Beanstalk. Last month I forgot my phone in my pocket when going in the sea (I believe this is a common problem among people recently). After it got wet, it didn't work at all for over 12 hours. I took it apart and made sure I dried everything. I cleaned all connections with alcohol and put it back together. It booted and it took a while to settle. I didn't expect it to go without issues. All works great except two things:
1. It takes a long time to wake up when pushing the power button. Sometimes I miss calls because the screen stays dark too long and by the time it wakes up, I have already missed the call.
2. When a USB cable is plugged in, it is not responsive. I found a way around it - right before plugging it I wake it up and hold my finger on the screen. Then connect it with the cable and luckily it stays awake during the whole time.
I decided to upgrade to a newer release of Beanstalk and did that by flashing 1.275. I was hoping that this will fix it. Unfortunately everything stayed the same.
Next idea - return to stock and make my way to the Beanstalk again. Well, I can't make it go in Download Mode and two computers couldn't recognize it. I used different cables including the original one, but without any luck. Then I installed a reboot widget from the play store and was hoping that it will reboot in download mode, but no luck again.
Does anyone have any other suggestions? At this point I am not certain if this is just a software issue. It could be a hardware problem as well.
Any help will be greatly appreciated.
First post. Tried searching for the desired info, to no avail. Braving any potential flame spray and asking anyway. Besides... this may entertain you. I've also posted this same question to a couple other forums, to no avail.
I have a P3113 that I had on me when I was caught in a rain storm. I was wearing a rain coat, and the tab was in one of the pockets. The pocket was zipped closed, so I thought the tab would be safe. It wasn't.
I did the regular stuff of turning it completely off right away, then put it in a bag full of rice for about 16 hours or so. When I tried to restart it, no dice. About a day later, it did turn on. It stayed on for about an hour letting me play Fruit Ninja. Then it shut itself down on low battery. I couldn't get it to charge at all during this period. I left it on the charger over night... didn't charge. At that point, I sort of wrote it off, but didn't pitch it.
Fast forward about 2 years. I get bored one night, pop the back off and wire the outermost wires to a freshly charged 3.7V battery from an OG Droid phone. Hit the power button... and it booted up!
While it was running, it wouldn't get very good WiFi, even sitting next to my router. It wouldn't open the Play Store app, and when I managed to log into Play through the browser, Play wouldn't recognize the device. That kept me from being able to download any app updates or any new apps.
Then the machine started running v e r y s l o w. At that point, I decided to throw caution to the wind (I did, after all write this thing off about 2 years ago) and do a factory reset.
Now, when I have the device in recovery mode, and I tell it to reboot, it will shut off and never turn back on. If I manually power on with the power button, it starts up in recovery mode.
The device isn't rooted, and I can't root it at all. At this point, I'm not even sure where the data cable is, not to mention it would never interface with a PC after the initial incident. I have, still, tried to do "apply update from external storage," using a few different roms I have found here and elsewhere. Most recently, I used Tab2Lite_P3113_RC2.zip, but it failed at about 75% complete and gave me a "signature verification failed" error message. In fact, I get the same message for every rom I've tried.
Anyone have any idea at all how to recover this thing? I'm only curious if I can get it running just to play games. I plan on getting a Tab 4 8.0 in March.
So you are using a different battery?
shsagnik said:
So you are using a different battery?
Click to expand...
Click to collapse
Electrically speaking, I'm running 2 batteries in parallel. The OG Droid battery is wired to the factory Tab battery. I can disconnect the Droid battery and the Tab still runs, but still doesn't reboot as it should.
When I select reboot, it powers down, and stays that way until I push the power button. Then it boots right into recovery mode.'
Sorry I can't help you as I don't have requisite knowledge
Sounds like you have a Frankenstein tab,you need a new tab. Time to put it out of its misery.
Pp.
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys