Hi there,
after accidentially doing a factory reset in bootloader, i had to set up my device from scratch.
My configuration:
Device: Moto G (2013) XT1032
Bootloader: 41.18 (sha-99084d5, 10/29/2014 23:54:18)
Recovery: TWRP 2.8.7.0
ROM: CM13 Nightly from 03/01/2016
Gapps: Open Gapps Mini from 25/12/2015
Everything worked fine, until I made a backup in TWRP. I rebooted, and after the android boot logo disappeared it ended on a black screen with only the status bar and "back-button" on the bottom right showing up. Restoring didn't change anything, as well as clearing data/cache/dalvik-cache. Flashing the same rom over the existing configuration did work, but only for about 1 day.
I made a new backup and this time, system started regular. But the next day during normal use, the home button suddenly stopped working, and after rebooting, i got the same issue (black screen with only status bar and back button). Again, neither restoring backup didn't resolve the issue, nor flashing the same rom. This time, clearing data brought me back a working system (but without apps, manual settings, etc).
Did anyone experience the same issues or got a hint what could be wrong?
Not the backup imo... :/
---------- Post added at 16:08 ---------- Previous post was at 16:07 ----------
bug with cm maybe ???
I have exactly the same issue here.
But the back button is in the left side.
ismavolk said:
I have exactly the same issue here.
But the back button is in the left side.
Click to expand...
Click to collapse
You're right! I was never really good at distinguishing left and right.
So has anyone an explanation for this issue? I would like to update my CM13 to a newer nightly, but don't want to waste a half day if the same issue happens again...
Related
Hi all,
I just flashed latest nightly CM12.1 for Xperia Z2 Tablet, however all my apps, screen, etc everything is in phone mode. That means apps like telegram only use 1/3th of the screen en the slider with all the settings is in the middle of the screen instead right top. I've been trying different launchers/settings to correct this, but couldn't fix it so far. Is this a bug in the rom? I already wiped everything and redownloaded and reinstalled everything.
Thanks!
marvel79 said:
Hi all,
I just flashed latest nightly CM12.1 for Xperia Z2 Tablet, however all my apps, screen, etc everything is in phone mode. That means apps like telegram only use 1/3th of the screen en the slider with all the settings is in the middle of the screen instead right top. I've been trying different launchers/settings to correct this, but couldn't fix it so far. Is this a bug in the rom? I already wiped everything and redownloaded and reinstalled everything.
Thanks!
Click to expand...
Click to collapse
Weird.. CM12.1 works flawlessly for me.
Perhaps it would help to post some screenshot...
Hello, Hopefully some one is still checking this forum that can help me. I got a DNA with CM 11 on it, while I wait for the first Verizon snapdragon 820 with SD card, as my LG G2 started failing miserably (dead spots in screen and no loger connects to Wi-Fi or Bluetooth)
I wanted to clear it out and to go to a 5.x.x ROM. so I made my backups and went to the 5.1 google play edition ROM and fastboot-ed the latest firmware as instructed in the post. at first the capacitive navigation buttons seem to work, but in about half a day they become flaky and sometimes work and sometimes don't. whatever app I am in at the time seems to work fine, just can't exit without the nav keys unless I reboot or force another app to open from the lock screen. I have also tried a 5.0.1 and and now on a stock ODEX debloat 4.4.2 all with the exact same issue. I use TWRP and do a factory reset in TWRP before each flash. How is this issue following the flashing of each ROM? Any one have any ideas for me to try?
Thank you
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
I have a Moto E first gen, i keep getting bootloop, i've already tried lineage and stock rom, the phone works normally but in a day or two apps start to fail and after this when the phone reboots it gets stuck in bootloop, what is weird is that i went back to stock, flash all the motorola stock files with adb and the phone was working i even turn on and off several times and there was no issue, then again today whatsapp was crashing i reboot the phone and now is in bootloop again. Do you think it could be a hardware failure?
maujavier91 said:
I have a Moto E first gen, i keep getting bootloop, i've already tried lineage and stock rom, the phone works normally but in a day or two apps start to fail and after this when the phone reboots it gets stuck in bootloop, what is weird is that i went back to stock, flash all the motorola stock files with adb and the phone was working i even turn on and off several times and there was no issue, then again today whatsapp was crashing i reboot the phone and now is in bootloop again. Do you think it could be a hardware failure?
Click to expand...
Click to collapse
Flash stock KitKat or marshmallow ROMs
I'm getting the same problem here... in two or three days after ROM installation it gets stuck in a bootloop... I tried stock rom, lineageOS and Mokee... same thing happens every time.... Now I'm downloading the Official Pixel Experience and going to see what happens. I'll update here after a couple of days.
rafaelmaltez said:
I'm getting the same problem here... in two or three days after ROM installation it gets stuck in a bootloop... I tried stock rom, lineageOS and Mokee... same thing happens every time.... Now I'm downloading the Official Pixel Experience and going to see what happens. I'll update here after a couple of days.
Click to expand...
Click to collapse
So, it's been two days since I installed Official pixel experience and the ROM is great! But the problem persists...just now my moto e got into a boot animation loop....
Same issue
I am also facing same issue. From 6 months. I am on lineage and also tried Oreo ROMs. I think our device is old now and can't enough to handle nougat , Oreo ROMs.
I am now thinking to bury it in grave yard with respect.
Solved
So people,
I was reading an article on the forum, later I'll put the reference here... but it was about moto e rebooting... and that was a problem tha I was also facing. The explanation was that moto e first gen has a phisical problem on the power button, so the solution to avoid constant rebooting was to activate volume keys to be used to turn on the screen and activate the option to double tap the home button to turn off the screen. I did it and the rebooting problem was solved and it's been six days and I got no bootloop this time. I don't know how to explain but I think that the power button problem was related with the phone getting into the bootloop...
It's not about power button
rafaelmaltez said:
So people,
I was reading an article on the forum, later I'll put the reference here... but it was about moto e rebooting... and that was a problem tha I was also facing. The explanation was that moto e first gen has a phisical problem on the power button, so the solution to avoid constant rebooting was to activate volume keys to be used to turn on the screen and activate the option to double tap the home button to turn off the screen. I did it and the rebooting problem was solved and it's been six days and I got no bootloop this time. I don't know how to explain but I think that the power button problem was related with the phone getting into the bootloop...
Click to expand...
Click to collapse
We are already using volume button/ double tap for power on/off but lineage ROM causes this issue at anytime.
praveen139 said:
We are already using volume button/ double tap for power on/off but lineage ROM causes this issue at anytime.
Click to expand...
Click to collapse
I forgot to mention. I flashed stock rom via ADB Fastboot, reflashed twrp, and after that I flashed LineageOS14.1 and gapps via twrp, maybe this was the real issue. It's ok now. Today I'm instaling aosp extended to see how it works, and I'm going to flash the stock rom again before doind that
Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...