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.
Dear xda-community,
my galaxy S2 is driving me nuts for some days because of a very weird problem.
After flashing NeatROM 5.3.1 some weeks ago my phone screen suddenly started to stutter for some seconds with losing signal strength. After losing the signal it stuttered again but suddenly crashed and I couldn't start it up again unless I remove the battery and place it back again. Then I went back to Stock ROM after my phone bootlooped for no reason. As I tested stock ROM to ensure the problem does not occur, the screen stuttering happened once again. I just flashed JellySNAP ROM and thought it was over, but here I am with the same problem.
The odd thing is that it only occurs as soon as my phone is losing signal, searching for an available network to connect or going into airplane mode and waiting some moments.
What I did:
Reflash ROM
Wipe cache + Dalvik cache
Full wiped before flashing Custom ROM
Wipe everything and flash Stock ROM
But none of these things helped me fix my problem.
Is there any solution to this problem or does anyone have similar problems?
yomama163 said:
Dear xda-community,
my galaxy S2 is driving me nuts for some days because of a very weird problem.
After flashing NeatROM 5.3.1 some weeks ago my phone screen suddenly started to stutter for some seconds with losing signal strength. After losing the signal it stuttered again but suddenly crashed and I couldn't start it up again unless I remove the battery and place it back again. Then I went back to Stock ROM after my phone bootlooped for no reason. As I tested stock ROM to ensure the problem does not occur, the screen stuttering happened once again. I just flashed JellySNAP ROM and thought it was over, but here I am with the same problem.
The odd thing is that it only occurs as soon as my phone is losing signal, searching for an available network to connect or going into airplane mode and waiting some moments.
What I did:
Reflash ROM
Wipe cache + Dalvik cache
Full wiped before flashing Custom ROM
Wipe everything and flash Stock ROM
But none of these things helped me fix my problem.
Is there any solution to this problem or does anyone have similar problems?
Click to expand...
Click to collapse
Clean fully using GS2RomNuke @hawkerpaul then flash a new rom - it's got to be worth a try :good:
Try nuke scrpt.If that doesn't work either,then it must be a hardware issue,which means service center.
Jimsilver73 said:
Clean fully using GS2RomNuke @hawkerpaul then flash a new rom - it's got to be worth a try :good:
Click to expand...
Click to collapse
Just tried this out and flashed my ROM again. Somehow froze just right after boot, so I restarted it. But then it stuttered after going into Wi-Fi-Connection screen at the start. Luckily no crash, but I am still worrying about my phone... Gonna report after one day of usage
yomama163 said:
Just tried this out and flashed my ROM again. Somehow froze just right after boot, so I restarted it. But then it stuttered after going into Wi-Fi-Connection screen at the start. Luckily no crash, but I am still worrying about my phone... Gonna report after one day of usage
Click to expand...
Click to collapse
yep - reflash stock and use trianglaway to reset flash counter to zero and take back under warranty:good:
Okay guys, thank you very much for helping me out! :good: It looks like the problem still occurs, but at least I know when. Best example: I had about 28% battery lifetime left as this once happened. I just rebooted it and it suddenly told me that I only had 1% of battery left. So I think this is because of my faulty battery stat or even my faulty batteries. Gonna try a new battery just for reference.
Jimsilver73 said:
yep - reflash stock and use trianglaway to reset flash counter to zero and take back under warranty:good:
Click to expand...
Click to collapse
Well... I wish I could, the problem is, that I got it as a present some months ago and the real owner of this phone bought the Korean SHW-M250S version some years ago so I don't have any warranty anymore... Perhaps I should just use it until it dies (or the new motorola block phone project is released )
Hello,
My Xperia Mini started to reboot continuously and the only way to stop it is to remove battery. I think this have something common with battery, because after this happened battery charges very slow (about 5% per hour) but when I plug the charge cable it works fine.
I tryed to flash another rom and kernel but this doesn't helped.
Before that happened it was another issue, when I was turning on the phone battery sometimes was showing 100% (after restart it was fine).
I have unlocked bootloader and root.
When this reboots started I was staying under the sun, can it be caused by overheat? Does anybody know how to solve this problem?
Thanks.
This continuous reboot is called bootloop. You may have installed an incompatible mod before or well, something just happened. This should not have anything in common with battery. Reflash your choice of rom then wipe dalvik cache. If still doesn't work, wipe data.
fundre said:
This continuous reboot is called bootloop. You may have installed an incompatible mod before or well, something just happened. This should not have anything in common with battery. Reflash your choice of rom then wipe dalvik cache. If still doesn't work, wipe data.
Click to expand...
Click to collapse
I already flashed another rom with kernel (inlcusive stock) and wiped dalvik cache, also made a hard reset and formatted the flash card but still no luck . I think is caused by bad battery becase when is plugged it works fine, it's like battery doesn't charge anymore (it doesn't get warm) and always shows 100%. I will try to replace it and say the result.
mag3nta said:
Hello,
My Xperia Mini started to reboot continuously and the only way to stop it is to remove battery. I think this have something common with battery, because after this happened battery charges very slow (about 5% per hour) but when I plug the charge cable it works fine.
I tryed to flash another rom and kernel but this doesn't helped.
Before that happened it was another issue, when I was turning on the phone battery sometimes was showing 100% (after restart it was fine).
I have unlocked bootloader and root.
When this reboots started I was staying under the sun, can it be caused by overheat? Does anybody know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
hi,
I had the same problem with my mini pro.... the problem was a faulty battery.... maybe its the same for you... (here I'm referring only to the 100% battery problem... not the bootloop)
romikavinda said:
hi,
I had the same problem with my mini pro.... the problem was a faulty battery.... maybe its the same for you...
Click to expand...
Click to collapse
If there is problem in battery then phone wont even boot to get in bootloop
& BTW GOOGLE is solution go there
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.
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
ThorosPWNZ said:
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
Click to expand...
Click to collapse
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
BarryPooter said:
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
Click to expand...
Click to collapse
After several hard resets the problem has gone, i don't know for how long though. So i have no idea is it a hardware issue or not. May it be a flash memory problem?