Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
krakout said:
Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
Click to expand...
Click to collapse
I'm on latest beta 4 using a IN2025 OP8Pro. I used the full ROM not the incremental update to upgrade from OB3. I am rooted also. No issues you are experiencing. Sounds like you need to flash the full ROM from fastboot mode and complete wipe for a clean install and start from there.
./
Thanks for the input. How big is the partial update? Because the one I flashed was almost 3GB...
So, no real way to downgrade to OB3 again?
3gb is full ROM not the incremental update.
So that's not the explanation then... I wonder if factory resetting will fix the problem?
Any ideas anyone?
Related
I got a Nexus 5 been using CM on it for a while now. Currently i have 11-20140708-SNAPSHOT-M8
the build date is july 8. I've been getting CM update for a new version for like a month now, tried installing it a couple of times, when i press to reboot and install it says it installed it, and after the phone reboots, it's still the same old version, and i keep getting the notification to upgrade, but i can't.
So I waited for another new build, thinking this is just some bug in the update. Yesterday a new version prompted for a update, but the same happened. So i tried to download the zip from CM website and flash it on recovery manually. And i got an error:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
I used to update with no problems, but I seem to be stuck on the july 8 build.
Anyone else dealing with this, or know how to fix this?
Is your bootoader up-to-date? CM often require you to have latest bootloader
No. I haven't upgraded it. I've found multiple threats about it, I'm not sure which one is the right to do so. As i'm not really familiar with this kind of stuff.
EDIT: My BL version is HHZ11K. From what i gathered it's the most recent one.
TheSidiO said:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
Click to expand...
Click to collapse
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Wakamatsu said:
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Click to expand...
Click to collapse
Was thinking if I can salve the problem without doing that. But i did a factory reset and it fixed the problem.
Thanks for the responses.
problems updating monthly snapshots of CM
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
acf150 said:
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
Click to expand...
Click to collapse
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
updating CM snapshot monthly problems
TheSidiO said:
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
Click to expand...
Click to collapse
Almost what I did, i l always do a nandroid backup before flashing anything in recovery, I downloaded the snapshot and the gapps, wiped, and installed snapshots along with gapps. So your telling me to just do a backup in recovery before updating that it cleans my files, then without wiping to try to update just the CM update from either my phone or their website? No gapps? Will try next time thanks.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hi everybody,
I'm back with a new problem in my Honor 8 (FRD-L04)... I was one of the user who installed the faulty version 15.0 of the Magisk update, so as you can imagine my phone went into bootloop and had to go all over from a backup I did the past September. I was running the firmware version B385, and because I lost many important things for no backing up lately, I decided I would just update to the firmware version B389. My phone was rooted, so I had to flash a stock recovery and do a full package download for the update. Everything went smooth and the update worked well. I had to do a full wipe because after the update the bootloader locked and I unlocked it to root the phone once again. This happened 2 days ago, and today I tried to use the camera and this is were everything started going down. The camera simply doesn't load, if I clear the data and cache of the app and reopen the app, it shows the initial screen where you need to swipe it to start using the camera but after that it goes in some kind of opening closing loop, until finally it closes. When I try to open it again, it stays in a black screen until it closes. I have restarted the phone and cleared the dalvik/cache in TWRP but the problem persists. I don't know if this is important, but after starting the camera app and failing launching it, the flashlight stops working too. If i restart the phone, and start the flashlight it works well. I have been thinking in reinstalling the camera app, but I can't find the apk for it.
Hope somebody can help me with this small issue, so thanks in advanced
Rommco05 said:
Try to downgrade to an older version
Click to expand...
Click to collapse
Thanks for replying Rommco05... You mean to downgrade to the B385 update? or rollback to B381?
I have found the update.zip file for the B389 upgrade here http://gsmtube.com/android-tips-tri...89-android-7-0-nougat-update-europe-9747.html but the links appear to be broken..
Rommco05, can you help me how to downgrade? I'm a noob at this and your help would be greatly appreciated! thanks
Hey all,
Over the last few months, I haven't been able to get Google assistant to make phone calls or send text messages. All other functions work.
When I say, 'call my wife', or 'send text message to wife', it tells me that function is unavailable.
It used to work flawlessly.
I have changed nothing to cause it. I just woke up one morning and it didn't work.
So far I have tried:
-Factory reset
-clear cache, etc
-Magisk hide on assistant app, call manager, Google play services and google text to speech
I am on latest stable Oos with latest XxX Rom.
The issue started around 3 months ago.
Where should i be looking to fix this?
Thanks in advance for any help.
Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.
Do you know what day this happened?
spr33 said:
Do you know what day this happened?
Click to expand...
Click to collapse
I'm not sure. It was roughly 3 months ago.
cubic25 said:
Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.
Click to expand...
Click to collapse
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you
J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files
3. Flash latest oos either 9.0.9 or beta Q is up to you
4. Flash twrp
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.
J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
Don't think this will be useful, this is an Assistant issue, reflashing the ROM probably won't help.
cubic25 said:
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.
Click to expand...
Click to collapse
Can you check in the settings, under Apps, and Default Apps, if you correctly have a Phone app and an SMS app set as default ? Or maybe the Google App does not have the permissions it needs (Phone Calls and SMS permissions), you could also check that. This is probably a little thing like this, it's 99% sure it's an app or configuration issue.
Both apps are set as default and all apps have all permissions ticked.
I too have the issue and have tried several things with no luck.
I've also been experiencing this. It's been pretty frustrating when trying to use the assistant with android auto.
What ROM are you guys running? I wonder if there is any similarities between our devices.
cubic25 said:
What ROM are you guys running? I wonder if there is any similarities between our devices.
Click to expand...
Click to collapse
I'm on beta 28
Well today I installed Android Auto, I was also able to install Google speech to text and bam, I'm able to use Okay Google to text and call again.
So anyone else having random restart issues no matter what firmware you are running?
I am having this issue even after updating the firmware (yes I managed to get it updated lol didn't realize need to do it in increments rather straight to the latest).
I found a work around sort of but it requires having my hotspot on and another device connected at all times to keep the phone from restarting randomly.
Has anyone else ran into this issue and have a fix? Could it be a battery optimization setting?
Thanks
i got it when i update the rog 5 to latest version so i factory reset it then worked well
messhary said:
i got it when i update the rog 5 to latest version so i factory reset it then worked well
Click to expand...
Click to collapse
Ok thank you for replying, I just finished backing up with Migrate and going to do a factory wipe and then restore all my apps. Hopefully that solves my issues.
I have the same problem for last two firmware updates, for each update I need to do a full factory reset in order to let it work again!