Develop Bugs

[Q] Black screen of death?

Here is what happened on my month new Galaxy Nexus.
1. Listening to mp3 via Bluetooth headset
2. Playing a game
3. Standing up
4. On a train
Sound stopped working across everything, in the game and on the mp3. Tried killing the applications and reloading, the mp3 player refused to even start the mp3.
Rebooted the phone, well, I turned it off. It has never turned back on. Tried removing the battery, all that, nothing.
Got home, tried plugging in the USB into a PC. Nothing. Tried booting into recovery mode, nothing, other than the PC claiming to have found a new device.
I haven't plugged it into a PC in recovery mode before. I haven't even seen recovery mode on the Galaxy Nexus.
I was running OTA Vodafone UK 4.0.2 I hadn't even considered rooting it or anything.
Anyone know if this is salvageable or had the same happen to them?

Hi. If popping the battery does no good I'd get it replaced without any further investigation. Sounds like hardware fail, so long as you are sure you have not got it wet or caused any damage to it.
Sent from my Galaxy Nexus using XDA App

If you cant bring it back on after a battery pull then its a dead phone for sure

I had the same problem last month. An usb jig solved the problem.

USB Jig?
Any more details? Something you can point me at?
Cheers
Found this:
http://forum.xda-developers.com/showthread.php?p=20504509
Appropriate?

So does the phone show anything at all? Does the screen come up for any amount of time? Can you get into bootloader?

So for completeness I have exactly this issue:
http://forum.xda-developers.com/showthread.php?t=1384415
Basically this paragraph:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Click to expand...
Click to collapse
Sounds like a USB Jig might do it. But in this case its back to vodafone and jumping through those hoops.
For the record I hadn't done anything at all to the phone than a normal consumer would. i.e. no rooting, hacking, booting, fruiting or cheesing.
It just died.

[Q] Help Dealing with Unresponsive Screen/Buttons (Probable Water Damage)

On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.

install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do

My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2

ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)

bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2

[Q] Battery doesn't seem to charge, can't get into Odin

I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?

jonnierod said:
I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?
Click to expand...
Click to collapse
The easy options are to borrow a battery from a friend with a s2 phone, or get a charger off ebay, or buy a new battery from the store which will probably come with a partial charge.
Sounds like your usb port may have died. That happens sometimes.

I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk

jonnierod said:
I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
It is possible. I had a phone that the data burnt out on, but would still charge. Just one pin needs to be bad to cause some issues, but not break everything.
Could just be the battery is totally empty too. Getting a known good battery with a charge is the first step to troubleshoot this.

I have encountered this problem a time or two before when testing some of my many attempted multiwindow mods, the device will in fact charge, but it is going to take forever. After a double shift I would imagine you'd have enough charge to flash properly, so try it again afterwards. Also have you attempted to return to recovery? If Odin only partially completed, your custom recovery may still be there and you might be able to use the power off option from recovery, while the device is plugged in, and possibly tricking it into not powering on to the error screen.
WARNING! Everything in blue is simply conjecture and has not been proven to work, it is simply a working theory. If it does not work don't say I didn't warn you.

Nokia 6.1 completely dead after updating to pie

I just tried to install the pie update manually by downloading the zipped update, renaming it and placing it in the root and dialing the code. The installer started and took about 10 minutes to complete and asked to reboot at the end. Now after the reboot the phone shows absolutely no signs of life anymore.
The phone soesn't turn on, doesn't respond when i connect the charger (it doesn't even get warm) and nothing happens when i try to connect it to my pc. Did i mess something up? Does anyone know a way to bring it back to life?

Faranite said:
I just tried to install the pie update manually by downloading the zipped update, renaming it and placing it in the root and dialing the code. The installer started and took about 10 minutes to complete and asked to reboot at the end. Now after the reboot the phone shows absolutely no signs of life anymore.
The phone soesn't turn on, doesn't respond when i connect the charger (it doesn't even get warm) and nothing happens when i try to connect it to my pc. Did i mess something up? Does anyone know a way to bring it back to life?
Click to expand...
Click to collapse
This happened to me after a day of updating to pie.
I noticed that my phone is charging very slowly.I used ampere app from play store to measure the current...and found that current coming through charger is too low(about 100 milli amphour) and i thought it might be my charger fault.
Then i used another charger and got same result....i was totally shocked.!!
I don't know if it is a software problem or hardware.
So today i'm giving my device to Nokia service center......and lets see what exactly the problem is..
I think this is my last Nokia device....i'm completely dissapointed by Nokia!!
BTW...i didn't do it manually i got an ota update.

Hi,
this probably will not help much, think i have the same issue.
i have had my ta-1050 get stuck on bootloader? ~3 times now over maybe 6 months of ownership, the last time was my update this weekend to Pie.
rather frustrating .
Can see the device is stuck in bootloader when i plug the handset in to my windows computer\device manager, can see and under com ports the is a QDloader 8006.
then need to wait ~2days for the battery to go completely flat, then plug into fast charger and it boots up again.
if take device to nokia, pretty sure i will get no fault found by the time they look at it.

Pixel selective charging and won't connect to PC

A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A

Same problem
Jank4AU said:
A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A
Click to expand...
Click to collapse
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.

ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
Mine sees a Samsung device!

Jank4AU said:
Mine sees a Samsung device!
Click to expand...
Click to collapse
My PC keeps trying to install a Samsung device driver for some reason.

I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.

Thanks
boe323 said:
I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.
Click to expand...
Click to collapse
Thanks I was going to start your procedure but I hesitate. I had a second laptop that I had just restored to factory default and the phone communicates fine with it. In fact I am transferring music files to the phone as I write. So this leads me to the computer being the problem. On my working laptop the phone shows up as a portable device\Pixel 3 XL. On my problem laptop it is showing as an ACER Device\ACER ADB Interface and I have tried to update & uninstall this device but it always returns when I do a scan for hardware changes.

Had a very similar problem where all of a sudden all of my chargers would only slow charge except for the type C fast chargers, it wouldn't recognize the headphone jack adapter and my phone wouldn't deep sleep at all due to a kernel wakelock that only applies to when a cable is plugged into the phone (can't remember the exact name of it).
Multiple fresh flashes including one with a complete wipe and fresh start would not fix it. I even tried blocking the wakelock and nothing.
Unfortunately the problem has fixed itself randomly and hasn't shown up again so I have no clue what caused it and what fixed it. I thought it was maybe a bad charger port or something got stuck in there but no clue. The only remnant is that the phone will say charging slowly when it gets to around 80-85%.
Forgot to add that I'm actually on the last update for Android 9 instead of 10 but figured I'd chime in just in case