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.
Related
Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.
A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.
zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.
Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse
So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.
same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?
zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:
We updated the phone to 4.4.3 her phone is a plain vainilla N5, locked and unrooted. when it finished, the phone restarted and it was like we turn on the phone for the first time. the welcome and initial setup screen appeared. Since I sideloaded mine(mine is working fine). I didnt know if this was normal or not.
After the phone started. Two little notification icons appeared on the top left of the screen which I have never seen before. I tried to take a screenshot, but there was an error telling me I couldnt take a screenshot
http://imgur.com/3psmPCi [1]
One of the icons says there's no much space left. So I look at the storage screen and now the phone only has 128Mb of total space available
http://imgur.com/ewJDeOA [2]
everything is missing, photos, apps, contacts, everything. I tried to do a factory reset, but the final button is not working. it doenst do anything.
I tried to start the recovery through the bootloader and I get the sick android screen.
http://i.imgur.com/AwEo5tk [3]
I dont know what to do. I dont know if should flash a stock image or something. But I dont know what's the deal with the flash drive total space.
Any else has run into this? Any ideas?
EDIT:
I tried unlocking the bootloader and installing a custom recovery. No luck. After rebooting to into the custom recovery. The phone locks the bootloader again and there's no custom recovery anymore.
Also, everytime I turn off and on the phone. The initial setup screen comes up every time.
The device locks the bootloader again after unlocking it? Sounds like the eMMC chip is busted.
Try to flash a factory image, if that doesn't work you are screwed
vin4yak said:
The device locks the bootloader again after unlocking it? Sounds like the eMMC chip is busted.
Click to expand...
Click to collapse
Is that replaceable? How did that happen?
Sent from my Nexus 5 using Tapatalk
elgranchuy said:
Is that replaceable? How did that happen?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You could try unlocking the bootloader again and see if it unlocks?? If not, the motherboard needs to be swapped. No idea how it happened, it's a random hardware failure very common with the Nexus 5. I've seen lots of devices with a busted eMMC chip. It's strange that you can still boot into your OS. May be the chip is partly damaged. Anyways, it needs to be replaced.
vin4yak said:
You could try unlocking the bootloader again and see if it unlocks?? If not, the motherboard needs to be swapped. No idea how it happened, it's a random hardware failure very common with the Nexus 5. I've seen lots of devices with a busted eMMC chip. It's strange that you can still boot into your OS. May be the chip is partly damaged. Anyways, it needs to be replaced.
Click to expand...
Click to collapse
What are my options then? A couple of months ago we had to replace the screen through a third-party. Should I do an RMA with Google/LG. How do I explain this situation to them? Would they notice that I replace the screen?
elgranchuy said:
What are my options then? A couple of months ago we had to replace the screen through a third-party. Should I do an RMA with Google/LG. How do I explain this situation to them? Would they notice that I replace the screen?
Click to expand...
Click to collapse
If you've bought the device from google play store, then contact google and explain them your situation. I'm not sure whether they will notice it or not. If they open up the device, they might notice it.
If you've bought it elsewhere then visit a LG Service center and let them take a look at the device.
As per warranty guidelines, any 3rd Party repairs performed on the device voids the warranty. So, there's a strong possibility that you/your gf might need to pay up.
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?
My Asus Zenfone 5z suddenly stopped fast charging i know its not the charger thats the problem, ive used it on several different phones and it still works. Now comes another problem, when i charge my phone and restart it while plugged in the charging symbol doesnt appear but i know its charging but slowly via ampere app. I need to unplug then plug it again then it shows the charging symbol. My PC's and Laptops cant detect the phone but charges it. I have the bootloadeer unlocked, but when i charge my phone powered off it pops up every few seconds and the LED indicator doesnt light up. I tampered with something then it fast charges all of a sudden, i even moved the phone around to ensure that the charger isnt faulty. Then when i went to go and charge my phone is slowly charges up again.
Any help? Do i just go to a technician? its harder because its lockdown where im from. Is it my charging pin thats faulty??
Maybe cleaning it can help, use isopropyl alcohol and a tooth brush or cotton swabs.
XDHx86 said:
Maybe cleaning it can help, use isopropyl alcohol and a tooth brush or cotton swabs.
Click to expand...
Click to collapse
I echo what @XDHx86 has stated. At times, your charging port can be clogged up with dirt, lint, dust, etc... Cleaning it might resolve the issue. However, be sure not to use anything but isopropyl alcohol, preferably 70%+ solution.
Could be a charger port (PBC) failure if cleaning doesn't help.
Could also be a battery failure. Check for any signs of battery swelling.
Unlikely it's software.
blackhawk said:
Could be a charger port (PBC) failure if cleaning doesn't help.
Could also be a battery failure. Check for any signs of battery swelling.
Unlikely it's software.
Click to expand...
Click to collapse
no battery swelling, but i might go to a technician and see if they find a problem. As for now im trying everything before going. I did something, forgot what it was but it fast charged then i wiggled my charger around to see if it stops but it didn't. Tried plugging again and again but after a few hours it didn't fast charge again. Anyways what's a PBC failure?????
The charging port is mounted on a seperate printed circuit board in many phones.
blackhawk said:
The charging port is mounted on a seperate printed circuit board in many phones.
Click to expand...
Click to collapse
know any fix? and why does my bootloader warning always pop up every few seconds when i charge my phone powered off?
sweatypeaches said:
know any fix? and why does my bootloader warning always pop up every few seconds when i charge my phone powered off?
Click to expand...
Click to collapse
You replace the port PCB. The port PCB can effect other seemingly unrelated systems when it fails depending on the manufacturer.
What warning? It may be a firmware or hardware issue. Normally the firmware doesn't go corrupt for no reason.
Possible mobo failure.
There's also the possibility of a rootkit infection.
If running on Android 8 this becomes more likely and if so it may need to be reflashed to purge it.
Is there any other kinds of unusual behavior when running?
You need a tech who is very familiar with this make.
sweatypeaches said:
know any fix? and why does my bootloader warning always pop up every few seconds when i charge my phone powered off?
Click to expand...
Click to collapse
You replace the port PCB. The port PCB can effect other seemingly unrelated systems when it fails depending on the manufacturer.
What warning? It may be a firmware or hardware issue. Normally the firmware doesn't go corrupt for no reason.
Possible mobo failure.
There's also the possibility of a rootkit infection.
If running on Android 8 this becomes more likely and if so it may need to be reflashed to purge it.
Is there any other kinds of unusual behavior when running?
You need a tech who is very familiar with this make.
blackhawk said:
You replace the port PCB. The port PCB can effect other seemingly unrelated systems when it fails depending on the manufacturer.
What warning? It may be a firmware or hardware issue. Normally the firmware doesn't go corrupt for no reason.
Possible mobo failure.
There's also the possibility of a rootkit infection.
If running on Android 8 this becomes more likely and if so it may need to be reflashed to purge it.
Is there any other kinds of unusual behavior when running?
You need a tech who is very familiar with this make.
Click to expand...
Click to collapse
im running on Android 10. I'm talking about the warning when you power on your phone(image attached) Yes, i have some unusual behavior that's been running for the past few days such as: When i restart my phone when plugged in the LED light turns off when its powered off then turn on during the booting screen, then it will completely off once the phone is open BUT my battery percentage isn't going down. I still see it charging via ampere app. The charging symbol also doesnt show(i need to unplug then plug again for it to show) The phone still charges but very very slow.
blackhawk said:
You replace the port PCB. The port PCB can effect other seemingly unrelated systems when it fails depending on the manufacturer.
What warning? It may be a firmware or hardware issue. Normally the firmware doesn't go corrupt for no reason.
Possible mobo failure.
There's also the possibility of a rootkit infection.
If running on Android 8 this becomes more likely and if so it may need to be reflashed to purge it.
Is there any other kinds of unusual behavior when running?
You need a tech who is very familiar with this make.
Click to expand...
Click to collapse
and this phone was also given to me with an unlocked bootloader didn't know what it was then but i know now. I probably can fix it if its some software problem with the help of this website as I'm very familiar with PC's. Thanks for the help if ever.
sweatypeaches said:
im running on Android 10. I'm talking about the warning when you power on your phone(image attached) Yes, i have some unusual behavior that's been running for the past few days such as: When i restart my phone when plugged in the LED light turns off when its powered off then turn on during the booting screen, then it will completely off once the phone is open BUT my battery percentage isn't going down. I still see it charging via ampere app. The charging symbol also doesnt show(i need to unplug then plug again for it to show) The phone still charges but very very slow.
Click to expand...
Click to collapse
I'm no expert on this, but is that a normal warning if you unlock the boot loader?
I'm not advising you to lock it as that may cause other issues but doesn't having unlock increase security risks?
In any event if it does have a rootkit* a factory reset should purge it. If it has custom rom, I have zero experience with them.
I don't like using factory reset as it's best to find the root cause instead. In your case it may not help at all if the root cause is hardware. You need to observe the symptoms and use the process of elimination.
This is one of the reasons I run a stock Android, in some respects it simplifies troubleshooting.
* be careful with all downloads especially side loaded apps. Playstore downloads aren't without risk though.
Email downloads are high risk; keep it all in the cloud whenever possible.
Check the download folder regularly for odd behavior and unauthorized downloads.
sweatypeaches said:
and this phone was also given to me with an unlocked bootloader didn't know what it was then but i know now. I probably can fix it if its some software problem with the help of this website as I'm very familiar with PC's. Thanks for the help if ever.
Click to expand...
Click to collapse
You're welcome. Sorry I couldn't help you more.
I be very careful about locking the boot loader.
Make sure you know the full implications before doing so.
You might consider flashing it to it's stock rom especially since the boot loader was unlocked when you got it.
Make sure it's functional enough to take a flash though, last thing you need now is to brick it.
If it's a hardware issue this should be corrected first.
blackhawk said:
I'm no expert on this, but is that a normal warning if you unlock the boot loader?
I'm not advising you to lock it as that may cause other issues but doesn't having unlock increase security risks?
In any event if it does have a rootkit* a factory reset should purge it. If it has custom rom, I have zero experience with them.
I don't like using factory reset as it's best to find the root cause instead. In your case it may not help at all if the root cause is hardware. You need to observe the symptoms and use the process of elimination.
This is one of the reasons I run a stock Android, in some respects it simplifies troubleshooting.
* be careful with all downloads especially side loaded apps. Playstore downloads aren't without risk though.
Email downloads are high risk; keep it all in the cloud whenever possible.
Check the download folder regularly for odd behavior and unauthorized downloads.
Click to expand...
Click to collapse
I've tried factory resetting 2 times to no avail. It's a normal warning sign, its part of the booting process. But if i power off my device then charge it keep popping up every few seconds. Would a custom rom fix this? or do i just go to a technician now? Also for some reason only Type A to C chargers work. Ive tried my sibling's charger that's Type C to C and it doesn't work, but Type A to C works for them. Also my phone charges on my PC but it doesn't detect it despite having my phone on file transfer mode. I'm trying everything as it's hard to go to a technician especially during covid
blackhawk said:
You're welcome. Sorry I couldn't help you more.
I be very careful about locking the boot loader.
Make sure you know the full implications before doing so.
You might consider flashing it to it's stock rom especially since the boot loader was unlocked when you got it.
Make sure it's functional enough to take a flash though, last thing you need now is to brick it.
If it's a hardware issue this should be corrected first.
Click to expand...
Click to collapse
Yeah, bricking it would be a bummer. I'm still researching on bootloaders and custom Roms in general. Tips on it would be great tho. And no need to be sorry. And I saw this reply late, I've replied to your previous comment.
sweatypeaches said:
Yeah, bricking it would be a bummer. I'm still researching on bootloaders and custom Roms in general. Tips on it would be great tho. And no need to be sorry. And I saw this reply late, I've replied to your previous comment.
Click to expand...
Click to collapse
The unlocked boot loader is suspicious.
Like I said if it's hardware is stable enough to do a reflash I would. Go with the OEM rom it originally came with for now so you have a known good rom loaded... it will simplify troubleshooting.
Error on the conservative side.
Letting a good experienced tech look it over is the safest route.
Finding one may be difficult. One that's does rooting may be more helpful.
On the PC try accessing it in drive management, try the rescan drives command.
The PC not detecting it maybe a driver issue.
In hardware management try updating or rolling back the driver. Try another port.
Reboot...
Look at Event Viewer for error messages after trying to connect the device.
If it's not the PC it maybe the phone's port PCB has failed.
Inspect the phone port carefully with a good light source and magnification. Look for signs of damage, corrosion or debris.
Try gently cleaning as mentioned with anhydrous (99%) isopropyl alcohol and a soft bristle toothbrush. Allow to dry in a low humidity room before using. Isopropyl alcohol is hygroscopic so it will grab moisture out of the air to some extant plus the cooling tend to do so all well.
A blower bulb or fan helps speed drying.
blackhawk said:
The unlocked boot loader is suspicious.
Like I said if it's hardware is stable enough to do a reflash I would. Go with the OEM rom it originally came with for now so you have a known good rom loaded... it will simplify troubleshooting.
Error on the conservative side.
Letting a good experienced tech look it over is the safest route.
Finding one may be difficult. One that's does rooting may be more helpful.
On the PC try accessing it in drive management, try the rescan drives command.
The PC not detecting it maybe a driver issue.
In hardware management try updating or rolling back the driver. Try another port.
Reboot...
Look at Event Viewer for error messages after trying to connect the device.
If it's not the PC it maybe the phone's port PCB has failed.
Inspect the phone port carefully with a good light source and magnification. Look for signs of damage, corrosion or debris.
Try gently cleaning as mentioned with anhydrous (99%) isopropyl alcohol and a soft bristle toothbrush. Allow to dry in a low humidity room before using. Isopropyl alcohol is hygroscopic so it will grab moisture out of the air to some extant plus the cooling tend to do so all well.
A blower bulb or fan helps speed drying.
Click to expand...
Click to collapse
Thanks very much, Ill try and do what you said but in the events thats its the port, do i go to the technicians now?
sweatypeaches said:
Thanks very much, Ill try and do what you said but in the events thats its the port, do i go to the technicians now?
Click to expand...
Click to collapse
If don't have the skillset it be probably the best plan. Ask about experience and pricing upfront.
If you can see the techs working and using ESD mats/wrist straps that's a good sign.
blackhawk said:
If don't have the skillset it be probably the best plan. Ask about experience and pricing upfront.
If you can see the techs working and using ESD mats/wrist straps that's a good sign.
Click to expand...
Click to collapse
blackhawk said:
If don't have the skillset it be probably the best plan. Ask about experience and pricing upfront.
If you can see the techs working and using ESD mats/wrist straps that's a good sign.
Click to expand...
Click to collapse
it looks like this when i restart it by the way. Mind you the Charger is secured. And at the end i unplugged then plugged it again then it charges. I've tried using the phone while charging to see if it stops charging but it doesn't, so i ruled the charger out of the problem. Thanks again.
sweatypeaches said:
it looks like this when i restart it by the way. Mind you the Charger is secured. And at the end i unplugged then plugged it again then it charges. I've tried using the phone while charging to see if it stops charging but it doesn't, so i ruled the charger out of the problem. Thanks again.
Click to expand...
Click to collapse
You shouldn't need power it off to recharge.
So it won't charge unless powered off?
To give some context, my S10e (Verizon SM-G970U) decided to boot loop out of nowhere. Since this happened, I have factory reset the phone, no success. I brought it to a local repair shop who said they couldn't fix it. Now I have flashed the phone with Odin and despite the phone being flashed it STILL is boot looping. At this point, I'm assuming something went wrong with the hardware but I don't even know where to start with that. If anyone has any suggestions I would greatly appreciate them.
Firmware used :
Download Samsung Galaxy S10e SM-G970U VZW USA (Verizon) G970USQU5GUBH firmware
Fast download latest Samsung Galaxy S10e firmware SM-G970U from USA (Verizon) with G970USQU5GUBH and Android version 11
www.sammobile.com
Vivala8955 said:
... it STILL is boot looping...
Click to expand...
Click to collapse
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
MrGoodtunes said:
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
Click to expand...
Click to collapse
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Vivala8955 said:
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Click to expand...
Click to collapse
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
MrGoodtunes said:
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
Click to expand...
Click to collapse
I haven't tried charging the phone when it's on. Only when it's off and has returned to room temperature. Seems to me that about an hour in the fridge equals about 5 minutes of screen on time until the phone heats up again.
As for the internal component's you bring up a good point. Even if I were to determine what is causing the issue, I don't have the will/technical know how to buy the parts and do it myself. Outside of just replacing everything, in which I'd just buy a new phone haha.
Vivala8955 said:
... I'd just buy a new phone ...
Click to expand...
Click to collapse
That's what I did. Look'd at lots of possibilities, ended up buying another S10e.