Database Info

[Q] D2 (A955) won't power up/boot up... did I kill it?

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

[Q] Please help, bricked Nexus S 4G

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.

[Q] Nexus S (i9023) won't start. Need help

Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.

Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?

Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc

Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.

Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...

I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.

Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...

He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.

Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...

As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.

My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!

Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.

Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.

Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!

Missing OS

I am hoping someone can help me here.
My notepro was working fine, except for the screen flicker issue. I wanted to root it in order to adjust voltage and a few other things to try and prevent the flicker.
I was able to install TWRP, and SU and verified it was now rooted. I then went and tried to install a custom ROM http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
Everything seemed to install fine, the kernel, ROM, all that. However, when I restarted the device, i got stuck on the bootloader with the seanandroid red warning message. It would not load past this. So, i wiped and reinstalled everything several times over, and still no fix. I searched online and found a zip you could flash to fix the booting issue, but no help. I wiped everything except the extsd and reinstalled ROM and everything. Now TWRP says no OS and I am still stuck on the bootloader screen. i cannot do anything at this point.
After a bit it started flashing and flashing faster and faster. This was after sitting with the bootloader screen showing for a while. I assume battery ran out, but every time I tried to charge it, it either tries to show the battery charging from the off screen, but just gets frozen, and then starts to flash again.
I am letting it sit right now. I am thinking the temp or voltage spiked due to low battery power, but I am not sure.
Can anyone offer some advice?

I am thinking at this point it might be the motherboard.
After it started flashing, it would get so bad that the screen would fade out and then back in. Now, it wont do anything, and wont even indicate charging. Sometimes it did, but would just show the battery icon with a loading circle in the middle and never actually show it charging. now its just dead.
There is no way that rooting and installing a rom could have done this. i am thinking it is a hardware issue.
My choice now is to part out the pieces that work and scrap the mobo or to replace the mobo

Have you opened it up and taken a look at the battery connector to see if resoldering would help?
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk

batt connector seems fine. It seems that if I let the device sit for a white it will spark a little life and then die off again. Its rather odd.

disconnected the battery and plugged it in. was able to boot into recovery temporarily. however, it only works for a few min. tried to flash stock kernel and it had an issue, reloaded twrp itself and then would not read anything on the extsd and died.
i was to flash stock, but the stock file I have is .zip and odin will not recognize it to flash in download mode.
Ive rooted and flashed many devices before, but its been a long while since I did. A year at least, and not on this device.
At this point I am assuming that the mobo is the issue, but I am not sure. It was having the screen flicker issue before, which seemed to be heat or voltage related.
If I cannot fix this, i will likely just sell it off for parts. The screen, batt, all that should be fine otherwise.

Random restarts

Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks

OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?

I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor

I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.

harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...

Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.

Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.

I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.

Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/