Database Info

Wireless charging stopped working

After almost a year of flawless operation, the wireless charging on my Nexus 5 stopped working. Over a period of 4 days or so, it became intermittent and then stopped working completely. I have multiple wireless chargers and it fails to charge on all of them. Similarly, my N7 charges fine on all chargers, so I concluded my phone was bad.
After doing a TWRP backup, I did a warranty exchange with Google. Wireless charging initially worked fine on the replacement phone and I restored my TWRP backup. Again, over a few days, wireless charging became intermittent and then stopped completely. Again, my N5 fails on all of my chargers while my N7 works on all my chargers.
What could cause this? Could a rouge app be doing this? I'm planning to install a factory image to see if it charges then, but I haven't had time to do so yet.
Any thoughts? Thanks.

FletchF said:
After almost a year of flawless operation, the wireless charging on my Nexus 5 stopped working. Over a period of 4 days or so, it became intermittent and then stopped working completely. I have multiple wireless chargers and it fails to charge on all of them. Similarly, my N7 charges fine on all chargers, so I concluded my phone was bad.
After doing a TWRP backup, I did a warranty exchange with Google. Wireless charging initially worked fine on the replacement phone and I restored my TWRP backup. Again, over a few days, wireless charging became intermittent and then stopped completely. Again, my N5 fails on all of my chargers while my N7 works on all my chargers.
What could cause this? Could a rouge app be doing this? I'm planning to install a factory image to see if it charges then, but I haven't had time to do so yet.
Any thoughts? Thanks.
Click to expand...
Click to collapse
Have you tried pressing down on the back of the phone in case some contacts are loose?

Lethargy said:
Have you tried pressing down on the back of the phone in case some contacts are loose?
Click to expand...
Click to collapse
Yeah worth doing this if it's been dropped or compressed in any way. There are various contact clips that need to be in place around the back. I had an issue when I removed my back. I had to push it down firmly around the edges and centre to get it working again. Although if it stopped again after a restore, it could well be software and a reset will determine that

Thanks guys. Yes, I have tried squeezing the back with no success. I am aware that there is an additional clip near the upper middle of the phone. It appears to be properly clipped in place. I should add that since this is a new (refurbished) phone, I have never removed the back or dropped the phone, so I haven't done anything that would loosen any of the contacts on the back cover.

Does it work when the phone is switched off? That should eliminate any software issues.

krs360 said:
Does it work when the phone is switched off? That should eliminate any software issues.
Click to expand...
Click to collapse
Ah, of course!
I just tested both while off and while booted into recovery and it does not charge. So, the question is, am I really unlucky enough to get a phone with a bad charging mechanism after just returning a phone with the same fault? Or am I doing something to damage the phone? Is it possible that one of my wireless chargers is defective in a way that damages the phones charging circuit?

FletchF said:
Ah, of course!
I just tested both while off and while booted into recovery and it does not charge. So, the question is, am I really unlucky enough to get a phone with a bad charging mechanism after just returning a phone with the same fault? Or am I doing something to damage the phone? Is it possible that one of my wireless chargers is defective in a way that damages the phones charging circuit?
Click to expand...
Click to collapse
That does sound pretty unlucky!
What current does each of your wireless chargers use? Mine is 1.2A, never tried a stronger charger. Not sure if a stronger current could damage it though.
Have you had a read of this thread? There's some pretty detailed testing done there.
Maybe @Datsun.510 might know?

krs360 said:
What current does each of your wireless chargers use? Mine is 1.2A, never tried a stronger charger. Not sure if a stronger current could damage it though.
Click to expand...
Click to collapse
I don't know. My primary chargers are a Nokia DT-900 and DT-910. I think there are many people using those with the Nexus 5.

I finally called Google and they think I just got a bad replacement unit. I'm skeptical, but they're sending me another one, so we'll see.

FletchF said:
I finally called Google and they think I just got a bad replacement unit. I'm skeptical, but they're sending me another one, so we'll see.
Click to expand...
Click to collapse
For the benefit of anyone with the same problem who reads this:
I've been using the 2nd replacement unit for almost 2 weeks now, and wireless charging still works fine. I still find it unlikely that I just happened to get a replacement with bad Qi charging, but I'm glad I requested another replacement. As expected, Google offered to replace it with no questions asked. Great customer service. (I thought I read somewhere that each purchase is only eligible for one warranty exchange. I suppose in my case, if they really sent me a bad one, I'd be upset if they refused.)

FletchF said:
Great customer service. (I thought I read somewhere that each purchase is only eligible for one warranty exchange. I suppose in my case, if they really sent me a bad one, I'd be upset if they refused.)
Click to expand...
Click to collapse
Google is much better than any other company when it comes to these things

Wifi Problem - freezes sometimes and cant disable. Have to restart. LP & KK

Hi guys,
I have a problem that I've never seen or heard of before. So here is the situation:
Power button didn't work, so RMA'd phone. Got different phone back and instantly rooted/installed custom rom. Didn't notice anything until a month later. My phone would randomly just lag out and the wifi would stop. It would still show connected and that there was uploading activity, but that is all. When I clicked it to disable, nothing would happened. I would have to restart the phone, disable it for a while then re-enable it. I though it was the rom so I switched. Noticed the same thing is happening. I decided to play around with my sim, so I took it out and then put it back in, and it somehow fixed the problem. So I was assuming it was the sim causing the problem. Worked perfect for a week then started happening again. I did the thing with the sim and it didn't work this time. I still have the problem now.
Basically, my wifi would just stop working, when I click on it the phone lags out and freezes. I have to restart the phone and it will work. Sometimes Itll work for a full day then all of a sudden just stop. Sometimes it happens just a few minutes after restarting. I mostly find that it happens when the battery is less than 20%. Right now I am running stock LP, locked bootloader. I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?

s.hack said:
I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Click to expand...
Click to collapse
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
s.hack said:
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?
Click to expand...
Click to collapse
Try a different radio version. If it doesn't change anything then you have a hardware problem.

Elluel said:
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
Try a different radio version. If it doesn't change anything then you have a hardware problem.
Click to expand...
Click to collapse
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.

s.hack said:
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.
Click to expand...
Click to collapse
You mentioned that you only ran into issues after a month. During that month a hardware issue could have possibly developed and the device was fine when you initially received it.

Known LP bug.. Thats why i still stay with kk
Sent from my Nexus 5 using XDA Free mobile app

Random reboots only while the screen is off!!!

I am on stock ROM MOB30P. (No root,no restored apps,unlocked bootloader)
Whenever I keep the device aside(lock the screen and keep on a table or anywhere) or even if it's in my hand but locked screen, IT REBOOTS!. This doesnt happen when I use the device, it works just fine. But as soon as I don't use it, reboots occurs. And I say reboot"s" because it will keep rebooting until my phone has drained completely . the repair center is very far from my place. So what could be the problem. My wild guess is the flex cable, could it be? I don't want to "try" changing the flex cable because if that isn't the case I will just waste my money.
I need help ASAP!

Anyone??

pratik rai said:
Anyone??
Click to expand...
Click to collapse
Hi Pratik,
I am facing the exact same problem from today morning. I have recently changed the flex cable (around 1 month back) due to screen flicker issue. Looks like this issue which we are facing, is not due to flex cable. I tried to do factory reset of the phone, but that did not work. the problem still persists.
I am not sure, but i think this might be because of the July Security update which was released by google (I got it on Friday (15th July 2016) morning). There are few forums which are reporting issues specifically for nexus 5 users due to this security update. These are not exact same, but none the less they are issues.
I am trying to work my way around this issue. Will keep you posted.
Cheers.

sgrusr said:
Hi Pratik,
I am facing the exact same problem from today morning. I have recently changed the flex cable (around 1 month back) due to screen flicker issue. Looks like this issue which we are facing, is not due to flex cable. I tried to do factory reset of the phone, but that did not work. the problem still persists.
I am not sure, but i think this might be because of the July Security update which was released by google (I got it on Friday (15th July 2016) morning). There are few forums which are reporting issues specifically for nexus 5 users due to this security update. These are not exact same, but none the less they are issues.
I am trying to work my way around this issue. Will keep you posted.
Cheers.
Click to expand...
Click to collapse
Thank you so much for notifying me that. I was one day away from changing my flex cable.
I have tried everything that I could think of.
Last idea is locking the bootloader. (It's unlocked right now).
What do you think?.

Any updates bro?

Bootloops

My Pixel 3 randomly restarts and gets stuck in long bootloops. The frequency is completely random, ranging from three times a day (rarely) to once a week or two (more common). There is no trigger, sometimes I have it in my hand, doing stuff, and it does that, sometimes it does it when it's sleeping.
The bootloop is always the same.
I see the bootloader message, then th Google logo, and the phone restars after about one second. I never counted to loops but sometimes it must be tens of them. There doesn't seem to be a way to stop them, or at least I am not awaer of any key combinations.
I presume the phone eventually boots into safe mode or something.
I've had it for several months, bought it used in good condition off Ebay, and other than this I never noticed anything off.
This is extremely frustrating and I have no idea what to do.
Does anyone have any idea?

I really hope it never been inside water. Try updating your OS, or change to Custom ROM. If it still occurs, then that's a big problem.

It's most probably an app that's causing this, try disabling/uninstalling some apps that you don't need.
Booting into safe mode is also an option, that way you can make sure if an app is actually causing this.

I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.

WalrusInAnus said:
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
Click to expand...
Click to collapse
It's highly unlikely for it to be hardware problem, unless you have water/dust/humid damage.
Or maybe your phone heats really fast and therefore some pin inside the motherboard gets shortened due to the heat. But what are the chances of this happening?
But just to be sure, what happens when you connect your device to a charger with output more than 2 amp?
Did you modify your device in anyway whatsoever? Anything the previous owner noted about the device?

I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm

WalrusInAnus said:
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
Click to expand...
Click to collapse
Yeah, just flash some different ROM on your device and we're good.
Make sure you backup everything through TWRP and that you're flashing your device specific ROM.

As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.

WalrusInAnus said:
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
Click to expand...
Click to collapse
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.

XDHx86 said:
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
Click to expand...
Click to collapse
But I said I flashed the stock ROM before with no luck. You're suggesting I do the same again. That makes very little sense.

What about the Google camera and LOS btw?

"your device is corrupted and cannot be trusted"

Hi all. I have a 2016 Sony Xperia XZ running on Android 8.0 Oreo. My battery got swollen and I try to replace it with newer battery.
The process went normally, but when I try to boot the device, the phone just shutdown and after its reboot, I got a message said "your device is corrupted and cannot be trusted".
It's weird, it never happened before. And when I shut off the phone, it didn't even charge. My question is;
1.Did I messed up the battery connector, I try using my old battery(swollen, but still has good health), but it got the same issue, and it wouldn't charge.
2.If I messed up the battery connector, for sure it wouldn't boot up, but the phone boots, but after 1 second it shut off.
3.Does sub-par BMS chip can cause the motherboard goes haywire? Or it just a firmware/software issues?
4.I use a Japan secondhand set(SOV34 KDDI AU), the bootloader is can't be unlock, but I already enable USB debugging on developer option, can I use any firmware flasher on Windows?

Try a factory reset.
You may have damaged the display and/or mobo assuming it has power.
The brick alone doesn't supply enough current to boot.

blackhawk said:
Try a factory reset.
You may have damaged the display and/or mobo assuming it has power.
The brick alone doesn't supply enough current to boot.
Click to expand...
Click to collapse
Thanks for your reply, I will try it. My phone is a Japan secondhand set with bootloader status unlock: no, but I still can use Flashtool or Sony Companion right?

faizikari said:
Thanks for your reply, I will try it. My phone is a Japan secondhand set with bootloader status unlock: no, but I still can use Flashtool or Sony Companion right?
Click to expand...
Click to collapse
The firmware shouldn't be corrupted. It rarely happens. If you flash go with a stock rom although with an unlocked bootloader you have more flexibility. Try to rule out a hardware issue first.
A factory reset wouldn't be the first option I would until I was confident it wasn't a hardware caused failure. Flashing be my last resort. I never had to flash any of my Androids in over a decade due to corruption. Usually it's the user partition that gets corrupted or more likely a 3rd party app screws it up. A factory reset would set back to its default settings*.
The bootloader being unlocked plus running on Android 8 make it much more susceptible to rootkits and malware... bare that in mind. Android 9 is a more secure OS. 10 is sort of a pain and uses more resources.
*Android 8 and lower are suspectable to partition worming rootkits like Xhelper. If infected with that it can be purged without a reflash now, I believe. If present it would need to be addressed though...

blackhawk said:
The firmware shouldn't be corrupted. It rarely happens. If you flash go with a stock rom although with an unlocked bootloader you have more flexibility. Try to rule out a hardware issue first.
A factory reset wouldn't be the first option I would until I was confident it wasn't a hardware caused failure. Flashing be my last resort. I never had to flash any of my Androids in over a decade due to corruption. Usually it's the user partition that gets corrupted or more likely a 3rd party app screws it up. A factory reset would set back to its default settings*.
The bootloader being unlocked plus running on Android 8 make it much more susceptible to rootkits and malware... bare that in mind. Android 9 is a more secure OS. 10 is sort of a pain and uses more resources.
*Android 8 and lower are suspectable to partition worming rootkits like Xhelper. If infected with that it can be purged without a reflash now, I believe. If present it would need to be addressed though...
Click to expand...
Click to collapse
I saw lots of Pixel and few Sony, LG and Moto also had that issue. In terms of Sony, I did saw Xperia XZ2 did had that issues.
But my phone can turn on, it went to the lockscreen and less than second it shut off. I'm quite scared if its a hardware issue, it couldn't charge, but the battery connection looks okay to me. Does low quality BMS chip can cause some haywire to the motherboard?
My bootloader unlock status is no, because it's rare to found a Japan import set that can unlock its bootloader.

faizikari said:
I saw lots of Pixel and few Sony, LG and Moto also had that issue. In terms of Sony, I did saw Xperia XZ2 did had that issues.
But my phone can turn on, it went to the lockscreen and less than second it shut off. I'm quite scared if its a hardware issue, it couldn't charge, but the battery connection looks okay to me. Does low quality BMS chip can cause some haywire to the motherboard?
My bootloader unlock status is no, because it's rare to found a Japan import set that can unlock its bootloader.
Click to expand...
Click to collapse
Is the battery known to be good? What voltage is it showing? That's not a load test though.
I know it's new, but...
A new battery should have somewhere between a 30-70% charge on it when recieved. So if good it should have enough to boot it even if not charged. If not charging and especially if the power state is unknown flashing firmware is unwise.
If there's no indication of charging it could be anything from the outlet, brick, cable, port, connector(s), battery or mobo. The SOC is a BGA chipset and can be damaged by excessive board flexing as can other chipsets.
Can you get into the recovery menu?

blackhawk said:
Is the battery known to be good? What voltage is it showing? That's not a load test though.
I know it's new, but...
A new battery should have somewhere between a 30-70% charge on it when recieved. So if good it should have enough to boot it even if not charged. If not charging and especially if the power state is unknown flashing firmware is unwise.
If there's no indication of charging it could be anything from the outlet, brick, cable, port, connector(s), battery or mobo. The SOC is a BGA chipset and can be damaged by excessive board flexing as can other chipsets.
Can you get into the recovery menu?
Click to expand...
Click to collapse
I've read review of the seller of that battery, mostly positive, and I bought my past battery from the same seller and it didn't had any issues other than swollen after 1 year of usage. The battery arrived I think at 40%.
I've read on some thread that when Android phones got corrupted like mine, it can't be charge at its off state, unless if it's enter flashmode, then it can be charge. But I couldn't remember what thread that was, it might be XZ2 thread. On Pixel and OnePlus thread that I found also said the same thing.
Can I know how to enter recovery mode for Sony Xperia XZ? For the time being I unable to access to any Windows PC, so I can't try charging my phone via flashmode.

faizikari said:
I've read review of the seller of that battery, mostly positive, and I bought my past battery from the same seller and it didn't had any issues other than swollen after 1 year of usage. The battery arrived I think at 40%.
I've read on some thread that when Android phones got corrupted like mine, it can't be charge at its off state, unless if it's enter flashmode, then it can be charge. But I couldn't remember what thread that was, it might be XZ2 thread. On Pixel and OnePlus thread that I found also said the same thing.
Can I know how to enter recovery mode for Sony Xperia XZ? For the time being I unable to access to any Windows PC, so I can't try charging my phone via flashmode.
Click to expand...
Click to collapse
I don't know if that's true or not. Try some Goggle searches. It's a handful.
It shouldn't have gone corrupted unless there was physical damage as flash memory retains its data for many years without power.
ESD damage is also a possibility. If you can't bring up recovery it's essentially bricked... I think.
The battery seems isolated from the mobo. Check the C port pcb for damage. The display is in harm's way. I had a battery fail on my N10+, because of the case I didn't notice the bulging rear cover. I was very lucky the display wasn't damaged.
Maybe someone else here has a better plan.

blackhawk said:
I don't know if that's true or not. Try some Goggle searches. It's a handful.
It shouldn't have gone corrupted unless there was physical damage as flash memory retains its data for many years without power.
ESD damage is also a possibility. If you can't bring up recovery it's essentially bricked... I think.
The battery seems isolated from the mobo. Check the C port pcb for damage. The display is in harm's way. I had a battery fail on my N10+, because of the case I didn't notice the bulging rear cover. I was very lucky the display wasn't damaged.
Maybe someone else here has a better plan.
Click to expand...
Click to collapse
Oh, I'm sorry, I forgot to mention that my older sister phone, Sony Xperia X Performance, also use Snapdragon 820 and Android 8.0 Oreo also had that same issue as mine once when I swap a new battery, but it happened once and now that phone just run normally without any issues.
It's totally weird why I saw lots of Pixel device got the same issue as mine, and most of it said they never open their phone and never even disturb its bootloader or some sort.
I think the last resort is for me to use Sony PC Companion to repair my phone, or flash the whole firmware using Flashtool. If it still had that issue, it must be I messed up the board or something.
Thanks so much for your help, I really appreciate it a lot.

faizikari said:
Oh, I'm sorry, I forgot to mention that my older sister phone, Sony Xperia X Performance, also use Snapdragon 820 and Android 8.0 Oreo also had that same issue as mine once when I swap a new battery, but it happened once and now that phone just run normally without any issues.
It's totally weird why I saw lots of Pixel device got the same issue as mine, and most of it said they never open their phone and never even disturb its bootloader or some sort.
I think the last resort is for me to use Sony PC Companion to repair my phone, or flash the whole firmware using Flashtool. If it still had that issue, it must be I messed up the board or something.
Thanks so much for your help, I really appreciate it a lot.
Click to expand...
Click to collapse
You're welcome.
If it's a known issue than it maybe exactly that.
Sorry I couldn't be of more help to you.

blackhawk said:
You're welcome.
If it's a known issue than it maybe exactly that.
Sorry I couldn't be of more help to you.
Click to expand...
Click to collapse
Oh not at all, I'm totally glad that someone reply my post. I'd just found the thread that I mentioned, it's from Sony Xperia 1 II thread. This person had the similiar issue as mine. Hopefully it's a software issue consider their phone did successful to boots up.
1. Phone got corrupt.
2. Battery is low and can't charge when it's off.
3. Only charge if it's in flashmode.
Bootloop - Your Device is Corrupt
Yesterday I flash SEA firmwear to Xperia 1 ii via Flasher which result to constant boot loop with error message "Your device is corrupt. It can't be trusted and will not boot" I have attempted to repair the phone via Xperia Companion, however...
forum.xda-developers.com

Sometimes it takes a while to get replies especially with older phones.
Yeah I found this. Hope that gets it for you.
Try Google searches like: "Sony Xperia XZ, your device is corrupted and cannot be trusted"
Google searches are the easiest and probably the best way to search the XDA forum
The Google web crawlers never sleep... they don't find everything though even with precise key words. You may dig up some more useful information as it is out there by now.
Cross platforming works many times; it doesn't need to be that exact Sony model. Many issues are long standing and are found on to several models even years apart. Use whatever comes in handy...

Woah, thanks a bunch for posting link for that thread, I keep Googling it but never found that thread on Sony's forum yet.
I did found some Xperia XZ2 that had the same issue as mine. I totally curious what cause the software to be corrupt like that, bad apps maybe? I did uses a few cracked apps that I sideload the APK, maybe that one of the reason.

faizikari said:
Woah, thanks a bunch for posting link for that thread, I keep Googling it but never found that thread on Sony's forum yet.
I did found some Xperia XZ2 that had the same issue as mine. I totally curious what cause the software to be corrupt like that, bad apps maybe? I did uses a few cracked apps that I sideload the APK, maybe that one of the reason.
Click to expand...
Click to collapse
Bad apps can screw up the user partition data and sometimes cause a boot loop. They normally can't corrupt the system partition though... they shouldn't be able to.
There's the little monster xhelper. Android 8 and lower are vulnerable to it. Always scan any side loaded apps first with Virustotal. A seemingly good app could also latter download its payload.
If any doubt exists do not install it.