The phone just died for the battery ( i have the battery problem of this phone, it dies on 20% battery like you disconnect the same) and I charged a little (20%) and when I boot it up, the phone is soft bricked (just ROM boot screen and vibrates occasionally).
I have last LineageOS Nightly for the phone, root, and busybox.
I had this problem a few times in the past and i successfully solved it by erasing data in TWRP, but its REALLY FRUSTATING format all the apps and start again without previous backup.
I want to find the way to solve it without formating the /data.
Hope help of any of you, thanks<3.
PD: Sorry for my bad English.
Hi friend,
i have the same problem with Ressurection Remix V5.8.2 (Moto X 2014), i found a "fix" without lose any data, simple re-flash with before version of the rom (and clean cache) (in my case Ressurection Remix V5.8.1) and start phone, after boot (ignore some app errors) quick reboot in recover mode and re-flash with the actual version of rom you use (clean again cache) (in my case Ressurection Remix V5.8.2).
Good lock.
Fabiano Souza
Hey bro,
I have the same issue when I have opengapps installed. So it may be fixed with uninstalling opengapps.
It works on ViperOS v2.1 although brings inconvenience
Good luck
Same problem here (for the second time) and occurred on 31st July 2017
zureau said:
Same problem here (for the second time) and occurred on 31st July 2017
Click to expand...
Click to collapse
you try the tips in the post? Same problem after try?
Related
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
vite0150 said:
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
Click to expand...
Click to collapse
This is not common at least not for CM11.
I've been running CM11 nightlies since they started to roll out, currently running 20/12 without issues.
I would recommend going to recovery, back up, and erase system, data, cache and dalvik, then flashing CM11 nightly to start clean.
I've been running CM11 and Validus13 ROMs since they became available and never had this issue.
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
I don't recall wiping Cache, Dalvik, or Data after installing 4.4 ROMs.
vite0150 said:
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
Click to expand...
Click to collapse
You should totally clean cache and dalvik when flashing new roms (CM usually does this by itself anyways). Make sure you're cleaning these, won't hurt at all anyways.
Ok, make a factory reset after flashing... Also i see in some roms that i gotta mount system and other things, i never did that (i didn't saw that in the instructions of the two roms that I've tried...)
Also I used for this couple of days the stock rom just to check that it wasn't a hardware problem... worked flawless...
Right now i'll try valadus... I'll let you know how it goes
Update: valadus gave me a lot of errors... Something like it couldn't write on storage/cwm... And when it was aborted it says that cache can't be mounted... So i ended up installing cm11 (the same that i flashed before)
You're running the latest CWM or Philz recovery?
Philz
It's strange because I'm running the latest CWM and I can install the latest Validus13, Cyanfox, CM11, and Probam without a problem.
Flashed probam last night, and it survived the night! Only thing I changed from before was wiping again after flashing...
Thanks for ur help
Update:
In the morning i connected the phone to the charger, and now i went to see if it was fully charged and surprise!!! It happened again!
Maybe is the charger cause I'm using a generic, but why it doesn't happen on stock rom?
At this moment i will just leave it stock and put it for sale, don't want to keep dealing with this...
Hi guys,
A couple days ago i noticed that on stock (att) rom i wasn't getting bsod but i do was getting reboots when charging the phone (i don't know how i didn't noticed it before)...
So maybe someone can tell what are the specs of the original power brick (amps, input, output) to find a similar one and see if that can solve the problem
Edit:
Nvm i found a samsung charger... Now everything is working flawless on OSE rom
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
picles said:
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
Click to expand...
Click to collapse
Boot into recovery and restore a backuped rom , you can also use Odin to flash a fresh stock rom
Here there's a usefull q&a thread, have a look
http://forum.xda-developers.com/showthread.php?t=2313363
Sorry to resurrect an old thread but the same thing is happening to me. Clean install, wipe data, format system and it's still there. It seems that this problem only pops up after installing Gapps. But as far as I know, it's Gapps for 4.4.4. using this particular CM11 build. http://download.androidarmv6.org/_builds/cooper/stable/ RC10.
key board and menu, back buttons not working inmy ace after flasing with rc14
CMAceS5830 said:
key board and menu, back buttons not working inmy ace after flasing with rc14
Click to expand...
Click to collapse
You need to install correctly the ROM... which procedure have you followed to flash the ROM?
i have used the CWM-6.0.5.3_1-cooper to flash the rc 14 after clearing the cache dalvik and data.factory reset. and after flashingi have installed the minigoogle apps. i have tried the rc13 ,14 nd the stable release released today. all of them behave the same. Please let me know how i have to enable the keyboard. i am unable to connect to wifi also as unable to type the password in the prompt.
let me know if there is any other process to be followed while flashing the files.
i have used the CWM-6.0.5.3_1-cooper to flash the rc 14 after clearing the cache dalvik and data.factory reset. and after flashingi have installed the minigoogle apps. i have tried the rc13 ,14 nd the stable release released today. all of them behave the same. Please let me know how i have to enable the keyboard. i am unable to connect to wifi also as unable to type the password in the prompt.
let me know if there is any other process to be followed while flashing the files.
can you please post the complete process , that you think would flash the rom normally..
picles said:
Hello people o/
I've downloaded a CM11 rom for my galaxy ace and i'm having some problems with it.
As soon as I installed everything(gapps, cmlogin) the phone turned on normally, but now I can't use neither the volume button or the back/options button, and just to add up there's no keyboard installed on my phone anymore.
Can someone please help me with it? It's really frustrating
Click to expand...
Click to collapse
The solution for my my problem was:
Wipe data/factory reset AND
Clear cache and Dalvik cache AND
Format system partition
This can be done using ClockworkMod using various menus.
share
improve this answer
edited Oct 10 '14 at 13:34
Valerio Bozz
1032
answered Mar 19 '14 at 14:21
TaronAM
22113
Set as solution. Maybe you want to add the software you used for these steps. – davidbaumann May 20 '14 at 4:42
1
There is no additional software involved, other than booting into Recovery. – Matthias Urlichs Sep 13 '15 at 10:16
1
I also had to install CM again after these steps, but maybe because I said "No" to rooting the phone again on a reboot, and perhaps CM does that anyway (yes this is not the most intellectual comment) – Matthias Nov 25 '16 at 16:44
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
kernel problem
guccimcilroy said:
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I am not sure 100% but it may be kernel problem as support for xt1254 from stock kernel is added 3 days back in cm12.1 and RR is based of cm12.1
possible solution
1) try clean flash RR
2) if first does not solve flash CM12.1 (running very smooth without any bugs) until RR team update their ROM
It's probably RR rom. I had an issue with my Droid Ultra on dirty unicorns. Went back to cm 12 and it worked fine.
Sent from my XT1254 using Tapatalk
I am running resurrection remix fine on my droid turbo. For two days now I have had no issues. What I did is, in twrp, I did a factory reset, wiped dalvik and then cache. Then I flashed the ROM and then gapps. No more wipes. I booted it up from there and I've been stable ever since.
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
guccimcilroy said:
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
Click to expand...
Click to collapse
Yeah, freeze motogeofences in Titanium Backup and install TopNTP.
See this post:
http://forum.xda-developers.com/showpost.php?p=64109692&postcount=306
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
guccimcilroy said:
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
Click to expand...
Click to collapse
do you have "high accuracy" turned on?
Yeah. I turned it off when I froze it though
All you have to do is freeze georef then download TopNTP then reboot? Or am I missing a step
Do I have to go into stock to download topntp for it to work then flash cm 12.1 again?
Hello guys...
I need a help. First, I will not gonna blame anyone for spreading the beta/alpha ROM links here.
I believe that many of Mi3w users are very exciting to hear that their device will get an upgrade. And I, one of them who want to be the first to taste Android M on Mi3, officially with MIUI.
The problem is, when updating from 6.1.12 to 6.1.21, suddenly my Mi3w experiencing short bootloop. Normally, boot process will display android text below MI.com, this short bootloop only display MI.com for about 2 seconds and after that, my device turn off, and on again with the same symptom. This process will drain battery very-very fast.
I tried several times to flash fastboot (yes, I still can access the fastboot via vol down + power), at the end of the process, the bootloop happens again and again.
If I kind of lucky, I can access recovery. I tried also to wipe all data, after I reboot, the bootloop happens again and again.
I have search the MIUI forum and found that many, not only me, experiencing the same. Is it possible that this is an error, a weakness, faulty the Mi3 devices have? If so, it was so shameful since Mi3 is one of their flagship.
Oh, anyway... Is there anybody here who can help me fix this problem?
Same for me. Flashed twrp via fastboot and installed ivans 6.0 for now because of the new partition table. Waiting for fix.
Hello everyone, I am writing this post because I have a problem with the charge of my g800F with LineageOS 14.1; when I start charging the phone off it freezes and I have to remove the battery to turn it on. How can I fix? Sorry for the incorrect English
Try a clean flash (Deleting all partitions -data, system, cache, dalvik cache-)
Solved thank you
Hello - I'm new here.
I have the same problem with my S5 mini. After installing lineage 14.1 my phone freezes when charged in "off" state. Only the battery symbol appears and then nothing happens. If you unplug the charger the symbol remains and you have to take out and in the battery to restart. As posted before a clean reinstall with deleting everything TWRP offers results in the same problem. What do I do wrong? Thanks.
bitcube said:
Hello - I'm new here.
I have the same problem with my S5 mini. After installing lineage 14.1 my phone freezes when charged in "off" state. Only the battery symbol appears and then nothing happens. If you unplug the charger the symbol remains and you have to take out and in the battery to restart. As posted before a clean reinstall with deleting everything TWRP offers results in the same problem. What do I do wrong? Thanks.
Click to expand...
Click to collapse
You do not have to do anything not wipe or format! to restart the smartphone press vol down and power; for more info read the dedicate post for lineage os 14.1
bitcube said:
Hello - I'm new here.
I have the same problem with my S5 mini. After installing lineage 14.1 my phone freezes when charged in "off" state. Only the battery symbol appears and then nothing happens. If you unplug the charger the symbol remains and you have to take out and in the battery to restart. As posted before a clean reinstall with deleting everything TWRP offers results in the same problem. What do I do wrong? Thanks.
Click to expand...
Click to collapse
#2 - have the same issue - battery must be taken out...
Andi46 said:
#2 - have the same issue - battery must be taken out...
Click to expand...
Click to collapse
Read this post
I have the same issue with my galaxy G800F
Please read previous post!!!! This issue is normal unfortunally; to reset your phone press vol down + power button
Problem solved
There is a new update: lineage-14.1-20170219-UNOFFICIAL-kminilte.zip.
Now the battery problem is solved .
Many thanks to hennymcc for the great work for us G800F owners!
Problem is up again
Now there is a new build from 20170422. I was very happy to have new one - but- the problem with charging in off-state is back again. Means if the phone gets charged when it is off - you now have a new icon in lineage style- but it freezes a few moments after you plug in the charger. To get out of this you have to put out the battery again or press the side button very long.
Thats very disappointing and hope we get this solved asap. I'm considering to move back the previous build. But that should not be solution.....
Anyone else with the same issue? Thanks
I flashed 4 different xiaomis with clean flash.All of them have charging issues with lineage os 14.Tried many chargers and cables the problem persist.any advice? thanks