my Samsung galaxy j7 core would suddenly freeze es its screen and stay unresponsive for what seems like no fixed amount of time before blacking out, now if i try to long press the power button in order to wake it up it wouldn't respond instead what would only work with it is force reboot (power+vol down).
everything on my phones was official. no sketchy apps installed nothing to pin down this newfound perturbance to. such occurrences would strike untimely, they dont seem to be triggered by a specific task that i do they just happen whenever, sometimes even if my phone is idle/not being used. i have tried doing a factory reset-tried stress testing-tried clearing cache partition. nothing seems to stop this although its worth mentioning that the factory reset seems to have lessened the rate at which the freezes would happen. any ideas as to what might be causing this?
Welcome to XDA
Is the battery in excellent condition?
If not replace.
Only thing left after that is to reflash to the stock rom.
If that doesn't get it you have a hardware failure likely the mobo.
blackhawk said:
Welcome to XDA
Is the battery in excellent condition?
If not replace.
Only thing left after that is to reflash to the stock rom.
If that doesn't get it you have a hardware failure likely the mobo.
Click to expand...
Click to collapse
hey thanks for the reply! id guess my battery is in quite good shape although not optimal. what made me think about ruling out hardware failures is the fact that the problem seemingly started to happen overnight, with no changes made to the phone whatsoever except for that security patch update. oh and i forgot to mention that the recovery shows an error message E: unable to erase BCB message failed to locate /misc partition something along those lines
marmoh said:
hey thanks for the reply! id guess my battery is in quite good shape although not optimal. what made me think about ruling out hardware failures is the fact that the problem seemingly started to happen overnight, with no changes made to the phone whatsoever except for that security patch update. oh and i forgot to mention that the recovery shows an error message E: unable to erase BCB message failed to locate /misc partition something along those lines
Click to expand...
Click to collapse
If it has fallen to >80% of its original capacity it's degraded and should be replaced.
Any swelling is a battery failure, replace asap.
Flash rom shouldn't become corrupted unless there's a hardware failure. A reflash may "fix" this.
A rootkit are another possibility. If not running on Android 9 or higher a reflash may be needed to purge it, otherwise the factory reset should've been sufficient.
Related
Hello XDA, i've heard (and know) that you guys are quite good with phones, and was hoping someone would be able to help me out, i can't find anybody with the same problem.
So here it is:
Since i've been skiing, often when i lock my phone the screens keeps on coming on and staying on the lock screen, and just won't turn off, so it's an obvious baterry drainer and pontentially dangerous for the screen, so i've resosrted to putting a black background image.
Also when the battery gets "critically low" my phone comes up with the message and also vibrates, but keeps on repeating in, just doesn't stop !
I've also noticed that when this problem occurs when i go into battery saver in options the second box constantly flashes as does the estimate remaining time and time since last charge.
My battery is now really bad when this happens, but supprisingly is ok when this doesnt happen.
Has anybody else had this problem, or something similar? and could someone give me some advice (factory reset? which i don't really want to have to do :/ )
Thank You
and my phone is generaly a bit buggy when this happens, like suddenly turning off etc.
Since this happened after skiing, I'm guessing your phone got a bit wet, probably around either the power button or the battery (or both). You can try drying it out by putting it in some warm dry rice (an excellent dessicant) but that's something you do within minutes of it getting wet, not days, if you want to avoid permanent damage.
You could also try taking the battery out and carefully inspecting it, comparing it with the battery from another phone, etc. If it appears damaged in any way (swollen, discolored, corrosion on the contacts, etc.) you could try replacing the battery and seeing if that helps. You could also replace the phone, of course, but you'll probably have to buy it at retail price unless you've got insurance that covers liquid damage.
You could try a factory reset before replacing the phone, since you'll lose all your data anyhow, but this doesn't sounds nearly as much like a software problem as it does like a hardware problem. However, getting your data off is actually possible, using a tool like WP7 Root Tools (which is really awkward to use for backup, but it can be done). If you wait the next however-long for Heathcliff74 to release a version of Root Tools that supports elevating other apps, you'll be able to use a data backup tool that I wrote last year and am modifying to work via any full-permissions access.
Thank you for the reply.
The same problem actually happened in November also, but quickly went back to normal, but it's been a week now so it's getting a bit annoying.
I just rang samsung and she obviously said do a reset, so i think i'll do this but this will erase everything, i would just like to keep my contacts and messages tbh.
Havn't got time do research that yet but i'll look after, unless someone points me to something first, and i'll post back.
Thanks
You can make a backup of the phone before hard-reset. That way, if the reset doesnt' fix anything, at least you can restore the backup and be back where you were before deciding on your next step.
I can't get the Backup program to work, http://forum.xda-developers.com/showthread.php?t=1103011
Keep getting "Le format de la chaîne d'entrée est incorrect."
And if i try the in the command prompt i just get a an error saying "updatewp.exe stopped working"
is there any other way of backing it up?
Thanks
Hello great people of XDA,
About one month ago, my digitizer cracked, and I ordered a new screen & digitizer combo from ebay.
Two days ago the replacement arrived and the whole process went smoothly! Everything was working fine, except one thing. The Battery Percentage went crazy. It shows the remainder percentage in thousands.
eg. 3603 % and it always appear full! As soon as i put the phone to charge it appears as "Charged" but thankfully, the battery does indeed charge.
Check the screenshots in the attachments below.
The last screenshot (from the app Battery Stats Plus) says "Charging" but the phone is unplugged. Actually it's pretty obvious that all readings all wrong!
A friend of mine has also a Nexus 5, I tried replacing my battery with his, but the problem remains. Even with a different battery, the readings and percentage are wrong!
It's pretty frustrating. I tried solving one issue, then another came along. Do you have ANY ideas? Oh and one more thing. The "Battery" option from Settings is nowhere to be found!! I have to tap in the battery icon in notification drop-down to enter Battery settings.
Thank you in advance for your time!
Are you running a custom kernel on a stock ROM?
audit13 said:
Are you running a custom kernel on a stock ROM?
Click to expand...
Click to collapse
Hey audit13. Thank you for your reply.
I'm running Stock rooted ROM 6.0.1 (MMB29V) & stock kernel
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
audit13 said:
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
Click to expand...
Click to collapse
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
I also think it is software related which is why I suggested flashing a stock rom. If it was hardware related,flashing would not fix the issue.
Gonik said:
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
Click to expand...
Click to collapse
It only takes like 60 seconds to flash a stock rom and ten more to log into your google account once its booted and everything it restored for you pretty much. Its the easiest way to fix software issues for the most part.
Hi all
I have an annoying issue just started to happen yesterday
I have BKL09 Version with latest stock EMUI 9.1 AND patches
Suddenly the device is rebooting randomly just after 3 to 5 min of use ..it may reboot now while I'm writing this !
I have tried to uninstall the last 5 apps or so that may have contributed into this but no luck
I can also try to do factory reset but it's a pain as I have lots of apps and data to backup
Just wondering if anyone has faced the same situation or what else I can look for before factory reset ?
Thank you
Reboots If not under use?
Reboots If battery full or empty or both?
Before reboots IT shows Something on the screen?
Hopefully is a software problem. Try to backup your data an reset everything. If that didnt work, hopefully is the battery.
The worst case the problem may be some chip on the motherboard(cpu, memory, some electronic) that has aged or water damage or purely bad luck.
I had a Nexus 5X with the well know "soldering problems" that did the dame thing; sudden reboots.
slvjpn said:
Reboots If not under use?
Reboots If battery full or empty or both?
Before reboots IT shows Something on the screen?
Hopefully is a software problem. Try to backup your data an reset everything. If that didnt work, hopefully is the battery.
The worst case the problem may be some chip on the motherboard(cpu, memory, some electronic) that has aged or water damage or purely bad luck.
I had a Nexus 5X with the well know "soldering problems" that did the dame thing; sudden reboots.
Click to expand...
Click to collapse
Thank you for the response
It reboots randomly while in use and not in use
When it reboots , battery is always have juice never empty or low charged
It's just hang for few seconds then reboot itself
I have tried wipping the cash partition as advised by support when I called them over the phone but it didn't help
Next I'm going to monitor for few days then try a factory reset
But if it's battery ..how can I get it replaced ?
Sent from my Honor View 10 using XDA Labs
If You opened a phone before, battery in this model is prety simple to be replaced. You should be carefull with batteries as they might be dangerous. If You never did IT, You should find a service that can do that for You.
A replacement battery is 15$ dollars in my country and the service should be around another 15-20$ as it's not so hard to replace IT. This phone s are not glued - You can check IT on YouTube.
i also have the same issue from mid march and it has progressively worsened only. did you find any solution
Got this Xiaomi Redmi 10 and once in a day the display turns static (like an old tv without cable) but goes away by simply putting it in lockscreen using the power button and everything works great, I'm just worried if it's a hardware or a software issue because i wanna know if it's gonna get worse in long term using the phone as it is.
Judging by myself i think it's a software issue because it fixes itself just putting it in the lockscreen and it's not like one of those crazy issues where the display turns static in everyplace etc (in recovery, boot) or it stays static forever and being unresponsive.
I just want a little help figuring this if it's not a big deal by observing what i said.
Thanks in advance!!
Hassanmad said:
Got this Xiaomi Redmi 10 and once in a day the display turns static (like an old tv without cable) but goes away by simply putting it in lockscreen using the power button and everything works great, I'm just worried if it's a hardware or a software issue because i wanna know if it's gonna get worse in long term using the phone as it is.
Judging by myself i think it's a software issue because it fixes itself just putting it in the lockscreen and it's not like one of those crazy issues where the display turns static in everyplace etc (in recovery, boot) or it stays static forever and being unresponsive.
I just want a little help figuring this if it's not a big deal by observing what i said.
Thanks in advance!!
Click to expand...
Click to collapse
I agree that it may be a software issue. Have you tried going to recovery mode and wiping ONLY the cache partition then rebooting? It could be caused by some faulty data that needs to be wiped, it may even require factory resetting the device or even flashing the stock firmware to correct the software faults.
Droidriven said:
I agree that it may be a software issue. Have you tried going to recovery mode and wiping ONLY the cache partition then rebooting? It could be caused by some faulty data that needs to be wiped, it may even require factory resetting the device or even flashing the stock firmware to correct the software faults.
Click to expand...
Click to collapse
I tried factory resetting the device from the settings but it didn't help, i guess i just have to flash it and see!
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.