Has anyone else have a problem with bootloops happening during updates of the Signal Messenger app?
Rom is CM13(fefifofum, onano, Luffy.d, TheStrix ) with no kernel patches/tweaks.
After uninstalling the app, google updates runs properly.
I found out that the issue is not due to Signal Messenger but probably something with the rom. I think the customized rom does not monitor the thermal levels as well as the stock rom and throttle the cpu and that will cause the phone to crash and bootloop when it is too hot, which will happen when updating of many apps at once happens.
Running fstrim from the terminal window frequently after manually updating a few apps at a time seems to help avoid the issue.
I am also getting similarisue on my redmi 1s, on resurrection remix marshmallow
initially after updating an app, the app was not working and there were some crashes in settings app,
I did the hard reset from twrp, after that installing app is causing bootloop, some apps got installed and smoothly but some are causing bootloop(apps like whatsapp),
I guess the apps that were installed prior to the reset cause bootloop
i have tried hard reset, reflashing the rom and flashing the same rom , currently i have installed aicp rom, and it is doing the same thing , but in aicp it came out of bootloop after some time automatically and not i cant open the app, it show "app stopped running"
i was using phantom kernel with underclocked cpu with resurrection remix previously....
please help,
thank you.
Try to flash latest stock miui firmware 8.2.1
Do u have to try flash stock firmware?
ankush26 said:
I am also getting similarisue on my redmi 1s, on resurrection remix marshmallow
initially after updating an app, the app was not working and there were some crashes in settings app,
I did the hard reset from twrp, after that installing app is causing bootloop, some apps got installed and smoothly but some are causing bootloop(apps like whatsapp),
I guess the apps that were installed prior to the reset cause bootloop
i have tried hard reset, reflashing the rom and flashing the same rom , currently i have installed aicp rom, and it is doing the same thing , but in aicp it came out of bootloop after some time automatically and not i cant open the app, it show "app stopped running"
i was using phantom kernel with underclocked cpu with resurrection remix previously....
please help,
thank you.
Click to expand...
Click to collapse
My problem was bootloops from playstore updates and I didn't not have any crashes in the settings app or had to do a hard reset prior to the bootloop issue.
I think the problem has got to do with a bug in Cynogenmod all the way back from KK which have not been patched in custom roms. So all roms based on Cynogenmod/Lineage which includes R-Remix, AICP, etc will have the same problem.
See this thread:
https://forum.xda-developers.com/redmi-1s/help/help-crash-bootloop-logcat-included-t3737427
Stock firmware miui8 or 9 is fine. Or you could upgrade to LineageOS 14.1 which I did and it doesn't have this bootloop issue.
barrack1 said:
My problem was bootloops from playstore updates and I didn't not have any crashes in the settings app or had to do a hard reset prior to the bootloop issue.
I think the problem has got to do with a bug in Cynogenmod all the way back from KK which have not been patched in custom roms. So all roms based on Cynogenmod/Lineage which includes R-Remix, AICP, etc will have the same problem.
See this thread:
https://forum.xda-developers.com/redmi-1s/help/help-crash-bootloop-logcat-included-t3737427
Stock firmware miui8 or 9 is fine. Or you could upgrade to LineageOS 14.1 which I did and it doesn't have this bootloop issue.
Click to expand...
Click to collapse
I tried installing LineageOS14.1 and resurrectrion remix Nougat also(previously it was resurrection remix marshmallow) using twrp recovery, for both the roms while installing it shows "Signature verification failed error" or some error related to signature (sorry do not remember exactly), I have rechecked the rom zip files, files are alright , also checked md5 hash of rom files that is also correct,
any idea where the error is lying(also tried installing by disabling zip verification from twrp before installation)....?
and if I flash stock miui firmware (miui 8 or 9), will previously installed twrp recovery be lost after flash..??
I do not want mi recovery..
ankush26 said:
I tried installing LineageOS14.1 and resurrectrion remix Nougat also(previously it was resurrection remix marshmallow) using twrp recovery, for both the roms while installing it shows "Signature verification failed error" or some error related to signature (sorry do not remember exactly), I have rechecked the rom zip files, files are alright , also checked md5 hash of rom files that is also correct,
any idea where the error is lying(also tried installing by disabling zip verification from twrp before installation)....?
and if I flash stock miui firmware (miui 8 or 9), will previously installed twrp recovery be lost after flash..??
I do not want mi recovery..
Click to expand...
Click to collapse
Haven't came across the problem you described. You could try asking in Lineage rom thread. I would've thought that the TWRP settings for signature verification is the cause of the problem.
Theres 2 versions of the stock MIUI rom. The recovery version will not install anything on the recovery partition and will leave TWRP alone I think but I'm not sure and haven't tried it. I usually just use the fastboot version and reinstall TWRP.
Related
Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)
Copy important files to computer. Factory reset. Set it up as new device.
ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?
jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova
https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
I am using TWRP 3.1.1 on my redmi 1s and was using AOSP Extended Rom v4.4 .I thought of trying the phone encryption option but the device went into bootloop. Now only MIUI rom is working and all other ROMs' flashes result into bootloop. Recovery is fine. Is encryption the problem.
First, flashing custom roms requires firmware: get it at https://forum.xda-developers.com/showpost.php?p=73812026&postcount=2
2nd some roms has problems within zip files causing some bootloops or error while flashing
for example AOSP EXTENDED ROM, there is a work around for that get it here: https://forum.xda-developers.com/showpost.php?p=72648733&postcount=223
EmanzzKie said:
First, flashing custom roms requires firmware: get it at https://forum.xda-developers.com/showpost.php?p=73812026&postcount=2
2nd some roms has problems within zip files causing some bootloops or error while flashing
for example AOSP EXTENDED ROM, there is a work around for that get it here: https://forum.xda-developers.com/showpost.php?p=72648733&postcount=223
Click to expand...
Click to collapse
But I had previously flashed several ROMs without any problem they worked fine(even AOSP Ext).The glitch came after trying to encrypt my phone after which it went into bootloops. Strangely MIUI roms are working fine and recovery also looks good. could anyone please suggest what is the problem.I really hate MIUI.
pkrajpur said:
But I had previously flashed several ROMs without any problem they worked fine(even AOSP Ext).The glitch came after trying to encrypt my phone after which it went into bootloops. Strangely MIUI roms are working fine and recovery also looks good. could anyone please suggest what is the problem.I really hate MIUI.
Click to expand...
Click to collapse
remove encryption on your phone, can u do that?
EmanzzKie said:
remove encryption on your phone, can u do that?
Click to expand...
Click to collapse
Disabling Encryption is not an option ROM is already damaged.
I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'
Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.
my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM
Hey there,
I've been using an old beta of OmniROM Oreo for months now, but wanted to try the 9.0 ROMs that are out there. I followed the instructions in both the Lineage and Omni threads and updated to the TWRP that's needed, then flashed the chiron firmware that's needed, then wiped all and formatted data, then installed the ROM. When I went to flash the rom, TWRP told me that my filesystem was read only and suggested I leave it that way for security. I said OK, everything installed fine, but when it restarts it fails to boot the OS and then reboots into recovery (TWRP). I have tried flashing the firmware, different ROMs, etc., but not getting anywhere.
I'm assuming this is related to leaving the filesystem read-only, but not really sure.
Anyone know what I did wrong? And how to fix it?
Thanks