deleted - Xiaomi Mi A1 Questions & Answers

Deleted

Mine too doesn't deep sleep on any 8+ ROMs. On Nougat (7.xyz) it works, but on LOS, RR, Oreo 8.0+, whatever, it doesn't, not even after a fresh and clean instalation.
I'm starting to think there's something more serious going on (at least in my case), because when I'm on Nougat there's another battery related problem that's weird:
Most of the times when I'm going to charge the phone, it doesn't charge. It shows it's plugged, but battery % does not change. When I try to reboot or turn off the phone, it gets stuck on the "Turning off" or "Rebooting" animation.
The temporary fix I found is to hard reset (hold power button for 10s), and then it starts charging normally, but if I take too long to plug it, the problem will resurface, and another hard reset will be needed.
So...
On Nougat it doesn't charge, and doesn't turn off/reboots.
On any 8+ ROM, it doesn't deep sleeps (charging ok, turning off ok, reboots ok).
Goodluck finding your problem. If you wanna check if it's the "same case", I suggest using a nougat official ROM for like 3 days, to see if the problems I told also happen.

Related

Factory Mode LOOP

Hi! Every time i turn off my p6800, when turn on don't see "samsung glalaxy tab 7.7" and the boot animation but start the "factory mode". I i turn off it turn automatically on after 4-5 seconds and visualize the "factory mode".
I try to flash with odin, but for the first boot it's ok, if i turn off the device and turn on the problem is the same.
anyone have this problem or know its fix?
I had this happen. I found that fully draining the battery fixed it, I haven't found what makes it happen in the first place though.
To completely drain the battery you'll have to turn it back on after it turns off from low power. I'd recommend doing the first big drain by flashing something in odin to get it booted (I just flashed recovery instead of the whole rom), then running it down till it turns off. Then power it back on, just the factory mode screen is okay now and wait till turns off again. This is to avoid having it on the factory mode screen for hours on end, which would probably cause burn-in.
Once it gives no response to pressing the power button, plug it in to charge, hopefully when it's charged a bit you can turn it on and it will be working again.
This problem made me really wish for a removable battery.
My son had this issue for some time ago. And draining battery didn't help indeed. But after about a week of this looping, it randomly became possible to boot through the loop holding the power button. And after a month or so, I can say that the device is almost self-cured the disease, and the "factory mode" is quite rare seen now=)

Phone wont lasted 10 seconds without plugging in ,But not battery problem.

Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4

[input Needed] Possible getaway from HARD-BRICK [A300FU]

Hi Guys,
Before i move on, my phone literary died today, and randomly, managed to get it back to life.
Let me explain my case first.
I have a Samsung A3 2015 (SM-A300FU) which i have constantly updated with new builds, and lately am on a custom rom (with modem and BL updated). Obviously, rooted, custom recovery, custom kernel.
This setup was perfect so far, no issues, at least nothing majorly resetting my phone or ending on a shutdown.
Today i made it at work with 0% battery, plugged it on my charger, and left it to charge until 46%. Turned it on (yes, i charged with phone off), browsed a bit...and just as i was to hit the power button for sleep, the phone got unresponsive and just powered down. I initially thought that somehow an app in the background is delaying things so i even left it see if it recovers, just to see that the phone completely died.
By DEAD, i mean:
1. It wouldn't cold-reset with Vol Down + Power Button.
2. It wouldn't power on obviously.
3. No download mode...how could it work, if the above two didnt work.
4. No what so ever detection in USB from Windows, no qualcomboot or whatever that boot mode is.
I literary left it in the charger for half an hour, no signs of charging, no heat, nothing. Took it out, tried whatever not method with what ever amount of time required to hold whatever button, nothing worked.
For weird reasons, i thought LET'S CONNECT THE CHARGER, WHILE I AM ACTUALLY HOLDING VOL DOWN + POWER BUTTON, AND VOILA, IT BOOTED.
I booted successfully, to find out that the battery is at 0%.
It is impossible to discharge 46% that fast, so the only possible explanation is that it never charged to begin with. What powered it down, probably the same reason, no juice.
To all the HARD BRICKED lads here, can you try the above in BOLD AND RED?
To mods, feel free to axe the thread if things dont get as expected.
You dont know what a hard brick is. What you encountered wasnt it.
Mind you mate, input needed, it is literary the first words of the subject.
Try to correct, and not belittle, and try at least to elaborate.

[Q] wiped data by itself

happened on two different roms (RR and LOS)
battery < 10%
plug phone in to charge overnight (wall outlet)
find the phone bootlooping in the morning (probably after 4-6 hour charge) maybe not bootlooping, but stuck on boot animation
unplug, hold power to turn off and turn on
phone boots, but all app data has been wiped
really annoying problem that i hadnt had in over a month with RR as daily driver. switched to LOS and just happened again
I have a feeling this is hardware related now... and not necessarily related to the low battery state when plugged in... seems like battery charges up and then this occurs, but im unsure how to diagnose the issue... google has failed me on this one :crying:
Finally figured this out, hopefully helps someone else
After phone has rebooted on its own and is stuck on the boot animation, unplug the USB adapter. It will eventually boot and then reboot again on its own. Once it does boot the second time, it will be fine
The wiping was happening because I was holding down power to force the reboot. Should not do this
Very surprised that I am the only one reporting this on this device and that no one else has even heard of this. But ok

Stock X727 stuck in bootloop

Stock .21 firmware. Never tried any other ROMs. Battery went down to 1% last night, charged it on stock charger to 30% then moved it to a different charger. An hour after that I got a call, I hanged up and about 1 hour later I heard the phone buzzing every 30 sec or so, I looked at it and realized it's in bootloop. If I press Vol- and Power I can get it in fastboot and with Vol+ and Power in Recovery. Can't figure out what to do from there though.
Update: Pressed -+ and left it the whole day in that mode. Came home, and it booted up and looked fine for about 3 minutes then it shut down by itself. It seems to me that there's some sort of memory/storage corruption. Any suggestions on how to proceed from here?
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
nwaves said:
Phone booted normally and I was able to use it for about 12 hours. I was doing a Whatsapp backup this morning when it shut down and got into the bootloop again.
Click to expand...
Click to collapse
If you are using stock, immediately get rid of your usb c cable and buy a new one. There could be an issue with the cable that is causing problems with your battery.
Try to keep the charge percentage between 20% and 80%
Finally, your battery stats may be off. To resolve a battery stats issue you will need to reset the phone. Which again, if you are using stock and have never used a custom rom. You should definitely do a factory reset.
Same issue on 2 different chargers with 2 different cables that used to work well until now. None of the cables are stock. One of the chargers is stock, the other one aftermarket. My wife's S3 doesn't have any issues using the same cables and chargers. Issue seems to be happening when battery is full or almost full. Phone gets into a soft reset bootloop. I let it drain yesterday and was able to get in and do a factory reset. I then added my account and left it installing and updating apps overnight, while connected to the charger. Woke up with the phone off and after pressing power for 12 sec it got into the bootloop again. As you can imagine, it's impossible to keep the battery under 80%. Would it help if I try a custom rom? Maybe a new battery? I'm open to any suggestions as I really like this phone and can't find anything similar at a reasonable price.
So phone still reboots when battery is high. I can however get into Fastboot Mode and Tool All-In-One detects it. Tried to unlock the bootloader in the tool but it failed. I'm willing to try anything to get the phone back up and running but not sure where to start. Would really appreciate some guidance.
It really sounds like the battery is bad. You can buy a new battery for $8 .
If you replace the battery : Do NOT use a hairdryer to remove the screen. You will need a heat gun, they cost 7 dollars at harbor freight.
With a heat gun the lcd screen will practically fall off into your gloved hand.
I was going to offer to connect remotely and help with unlocking the bootloader and installing TWRP, Root and a Rom. But I sincerely believe that you need to get a new battery first.

Categories

Resources