Hi guys,
I was using Miui in mi pad 1 but it was really laggy IN VIDEOS and many apps including netflix wont even load in 4.4.4.
I moved to lineage 14.1 shield and apart from camera all were good.
i thought of upgrading to oreo and in middle i broke the device.
I went back to stock rom but i choose latest Chinese build 9.2.4.0 and use mi flash tool to boot it up. I was able to boot fine.
Again i went to custom rom dotos 2.5 and could see on locksreen showing phone charging slowly.
I kept for 3 hours and still same. I thought issue with the rom. WIPE EVERYTHING and again install lineage 15.1. It was able to boot fine but still no charging.
I kept my pad for hours to charge but still red light blinking, not booting up.
I removed the backpanel to remove battery (connector) and insert it again but still same.
I am not sure what to do now. If it will boot up i can go back to stock but it is not even booting to fastboot.
PLEASE HELP.
THANKS
Mont1jack said:
I removed the backpanel to remove battery (connector) and insert it again but still same.
Click to expand...
Click to collapse
Hello Is your problem fixed as I'm also experiencing the same
This also happened to me too in the past, my MiPad 2 is just in storage, still don't know how to fix it. Anyone here fixed this problem?
Related
I flashed the latest builds from both Coffebeans - http://forum.xda-developers.com/showthread.php?t=1547778 and Pershoot - http://droidbasement.com/galaxy/roms/cm9/p4wifi/ and I'm having the same issue with both of them. The problem is my Tab will randomly reboot then get stuck on the boot animation and just sit there forever. It's already happened twice now where my Tab rebooted sometime at night and sat at the boot animation until the battery was dead. I did do a full wipe before flashing.
Does anyone else have this issue?
Thanks.
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
foliage green said:
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
Click to expand...
Click to collapse
I came from Task650's version 14, but I've been flashing the CM9 KANGs for a while and haven't had this issue.
i have had some strange reboots...but never gotten stuck on the boot animation like that..thats the bad part about not having a battery to yank unfortunately
Sent from a Gtab 10.1 running Build 30
Well whenever I can't get something to work right, I Odin stock firmware on it and restart the custom rom process from scratch. Having a clean slate is time consuming and might not even be necessary but it's the only full proof way I can get things to work.
I wiped everything and also formatted /system in CWM and then flashed Coffeebeans latest build from 4/8. I haven't had the reboot and stuck boot animation issue, but now I'm having an issue where every time I charge the tab fully it won't wake up. I have to hold the power button to reboot it. It seems like it's the deep sleep issue, but it's been fine leaving it overnight as long as it's not connected to the charger.
Hello guys,
I've recently bought a Redmi Note 3 Pro (3GB RAM) and the first time I booted it up it showed that it has -2% battery life. Since this seemed strange I tried to charge for several hours, but no change was noticed. I then tried with a battery calibration app, tried factory reset and restarting the phone, but nothing helped. I am also not able to go in recovery mode for hard reset as it states that there is no charge ...
The strange thing is that the phone is working for now and I am using for a second day with still the same bug. This leads me to believe that the problem is most likely caused by incorrect battery stats saved on the phone, but I am not sure. I am also not willing to root it or flash it since it is brand new and I might lost the warranty.
Can you guys suggested me a solution for this or the problem is not easily recoverable?
Thank you for the time and answers!
I have the exact same problem, tried resetting everything, I suspect it is a hardware problem.
awedxz said:
Hello guys,
I've recently bought a Redmi Note 3 Pro (3GB RAM) and the first time I booted it up it showed that it has -2% battery life. Since this seemed strange I tried to charge for several hours, but no change was noticed. I then tried with a battery calibration app, tried factory reset and restarting the phone, but nothing helped. I am also not able to go in recovery mode for hard reset as it states that there is no charge ...
The strange thing is that the phone is working for now and I am using for a second day with still the same bug. This leads me to believe that the problem is most likely caused by incorrect battery stats saved on the phone, but I am not sure. I am also not willing to root it or flash it since it is brand new and I might lost the warranty.
Can you guys suggested me a solution for this or the problem is not easily recoverable?
Thank you for the time and answers!
Click to expand...
Click to collapse
Try updating, I had this issue with custom ROM's something certain boot images have this bug.
I flashed a new boot image and bug was gone but had no wifi reverted back to latest global stock via MiFlash.
If you have TWRP try the ROM here https://xiaomi.eu/community/threads/6-7-7-11.32639/ it seems ok.
Did anyone find a fix for this issue. I have the same problem. Battery percentage shows negative 2% and I can't get into recovery because of that. When I press Power and Volume + It shows the battery icon in red and won't let me into recovery. I have the Redmi Note 3 Pro Snapdragon version.
I tried flashing a couple of ROMs via MiFlash with no positive results.
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
5t4m said:
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
Click to expand...
Click to collapse
What rom are you using?
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
The Radon V1.8 Kernel actually causes this bug on MIUI based roms, so don't flash the kernel.
Radon Version 1.9 will resolve the battery bug on MIUI and other roms.
Talking about cm/aosp I tried almost all combination kernel/rom.
No success except for this particular cm with camera patch.
Same problem with battery, showing -2% but phone is working... Plz provide solution asap
If u run MIUI, just download FASTBOOT ROM, restart phone to FASTBOOT MODE and flash ROM using this tool. But if u run custom ROM just flash custom kernel (like RADON).
5t4m said:
Maybe a bit late, but the "camera fix" in this Thread fixed my "-2%"-Battery
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Just flash with TWRP.
Click to expand...
Click to collapse
Fixed the -2% Bug on latest CM13-Snapshot for me!
You Sir are awesome
flashed the latest global firmwareware(not developer one) solved my issue, also now my phone updates OTA.
Use only the official rom. custom that sellers flash usually is a junk just with additional options for menu's language!
Same problem with battery, showing -2% but phone is working... Plz provide solution asap what to do. .. mobile automatically switch off too
Geeta_ghai said:
Same problem with battery, showing -2% but phone is working... Plz provide solution asap what to do. .. mobile automatically switch off too
Click to expand...
Click to collapse
Flash the latest miui ROM in edl mode using miflash. That is the answer.
No
No that is not the answer it's a hardware issue short circuit in motherboard
induna said:
Flash the latest miui ROM in edl mode using miflash. That is the answer.
Click to expand...
Click to collapse
androidnandroid said:
No that is not the answer it's a hardware issue short circuit in motherboard
Click to expand...
Click to collapse
Hmm, well flashing an official ROM in edl mode has fixed this problem for many people, including myself. So it would seem that in most cases at least it IS a software issue that can be fixed by flashing.
My phone came from Banggood and a vendor ROM that wouldn't even support my FP reader, Goodix, and which booted up with the -2% battery bug out of the box. Flashing the official global stable ROM, 8.0.2.0 at that time, fixed all of the issues.
Hmmm may be sir but that doesn't seem to fix mine although mine is from xiaomi only and the problem came after using 6 month suddenly without any reason one morning
Ok guys there are 2 solutions to this problem one is drain your battery and don't charge it for 2 3 days drain it like he'll coz after switch off still some juice is left you have to drain completely and other rapid method is open your redmi note 3 and disconnect battery cable and reconnect it... The problem is not software its hardware where battery reading stuck at minimal which is - 2 ... Thinking minus two hours coz at zero still some battery left for edl and fastboot mode time and alarm... Fixed my redmi note 3 hope it will help you.. Coz tried all method format... 10 times flash all roms through fastboot mode Coz updater mode won't work coz of low battery reading... Enjoy guys
I am having a same issue with redmi note 3 SD version. Tried everything Global BETA ROM, STABLE ROMs but didnt solved my issue. Showing -2% bettery in every ROM which i have flashed.
I am facing a similar problem where my phone showed -2 as battery level but my phone is not booting at all without any charger attached. and even when the chargr is connected it boots upt the Mi Logo and then displays an empty battery which wont charge even when tried for hours. Please help
razy111 said:
I am facing a similar problem where my phone showed -2 as battery level but my phone is not booting at all without any charger attached. and even when the chargr is connected it boots upt the Mi Logo and then displays an empty battery which wont charge even when tried for hours. Please help
Click to expand...
Click to collapse
I had the exact same problem like this one on xiaomi redmi note 3 pro sd. I tried flashing fastboot miui 10 official but the problem still there. I also tried changing the usb charging port but still the same. I tried plug in the charger and hold power and + volume and it stuck at mi logo.
I want to know if anyone fix this?? Please help.
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .
Just few days after installing miui 12, got this problem. The phone is stuck on a boot loop. If I pattern unlock the phone, I get a toast saying "find device stopped unexpectedly". Unfortunately, I don't have a backup. :crying:
Is there any way to save my phone? or may be get a backup?
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Dhamo200694 said:
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Click to expand...
Click to collapse
Use an Intel pc. Amd has issues with mi flash unlock too l. Run as admin. Turn off all anti virus/ firewall applications.
Having the exact same issue on my POCO F1, recently updated to MIUI 12. It was working pretty well up until 10 mins ago.
Battery went under 5% and the device went into ultra power saving mode, then restarted. Now every time I unlock the pattern, the toast pops up "Find my device..." and it goes into bootloop.
Now there isn't even a pop up, device immediately goes into bootloop.
bro, i just now facing this.. can you help me out
Well, MIUI 12 is not going good in poco F1.
If anyone who has not updated to MIUI 12, don't update the phone. Currently there are many bugs in the update
Long story short -
Some are unable to boot up the phone, some stuck in bootloop, some unable to use their passwords, some unable to set up new password, Second space not working, etc etc ...
I also updated to MIUI 12 and was unaware of the bugs.
But the device booted up and password (both fingerprint and face unlock) was working fine but I was unable to change it. Second space was working too. So I was happy that there is not much issue.
But then come the buggy part.
I started playing COD m after update and battery drained like hell 100 to 30 in 1.5 hour. I was shocked by this.
After charging I started to play again but this time (with battery issue) screen freezing happened and then happened at regular intervals. So the gaming experience on MIUI 12 was ruined.
Then I just find MIUI 9 for it and flashed it. (Ya, factory reset in this process too ?) But it is working fine now. Got fast charging module and custom thermal for gaming and it worked.
Currently no issue at all.
But I am still finding a custom kernel for poco F1 to overclock cpu and GPU (not able to find any till now).
Nearly every kernel is ment for MIUI 11 and 10 only. So I am digging deep for now to find a kernel for MIUI 9.
At last just one message - Don't update untill mi release a stable and bug free MIUI 12 version.
If MIUI 12 is working fine on your poco F1, either you are lucky or you have not encountered a bug till yet.
Without data loss, is this method come back to normal as before for poco f1 mobile?
Without data loss, is this method come back to normal as before for poco f1 mobile?
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
arulprakash2000 said:
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
Click to expand...
Click to collapse
If you don't want to loose your data, try flashing the rom using mi flash tool. But nothing can guarantee data security. You should back up your data regularly, waiting for a mishap or trusting on a single electronic device is just foolish, do make multiple copies of important data, if you want it to be secure.
I also have this problem. Updated my POCO F1 to miui 12 and it is in bootloop all the time. The bootloader is locked but I cannot unlock it now with no access to the device. How can I flash again a lower version?
If I don't mind losing the data how can I go back to previous version?
No brother, I encountered the same issues you mentioned. I stuck with MIUI logo loop after that I did a hard reset to mobile phone working condition.
Hi all,
I updated my Mi A3 to the official Android 11 fastboot ROM, after installing and rebooting the phone stuck on Android One logo for about 2 minutes then it switched off automatically and not booted again, when I click any button nothing happen expect the white led start flashing for about a minute then stops flashing, any way to fix this problem please?
I never rooted my phone and never installed any 3d party rom.
Best Regards
Meky22 said:
Hi all,
I updated my Mi A3 to the official Android 11 fastboot ROM, after installing and rebooting the phone stuck on Android One logo for about 2 minutes then it switched off automatically and not booted again, when I click any button nothing happen expect the white led start flashing for about a minute then stops flashing, any way to fix this problem please?
I never rooted my phone and never installed any 3d party rom.
Best Regards
Click to expand...
Click to collapse
Your device is dead so far.you cant do anything for this time .
Is xiaomi fault with a killer update.
you can use qfile with service rom
i repair my xiaomi a3 briked with it
see videos on youtube and remamber to remove bettary jak and test point with every patch 0/1/...5 then add betrary and power the phone