[DISCUSSION] CM13 for Moto X 2014 (victara) - X 2014 Q&A, Help & Troubleshooting

This is a discussion thread for Official CM13 Nightly for victara (Motorola Moto X 2014). Note that I'm not a CM13 contributor or dev, I'm an user just like you.
If you wanna try CM13 on our beloved phone, this is the official download link: http://get.cm/?device=victara
->I'm not responsible for bugs (neither the devs, it's a nightly after all) and for bricking your phone in the installation process.
If you wanna know the nightlies changelog or what's to come on the next one, see: http://www.cmxlog.com/13/victara/
Here we can discuss about the ROM development, bugs, workarounds, doubts about CM's and Android's new version, etc.

Limitations on Official CM13 for Moto X 2014 (victara):
-Casting with Chromecast isn't working;

Why we cannot delete unuseful posts?​

Only the jedis can see this secret:
You can't see this secret.

music player is fc too on 24/11 build,downloading 25/11 build to see that issue is resolved

kleytonhunter said:
music player is fc too on 24/11 build,downloading 25/11 build to see that issue is resolved
Click to expand...
Click to collapse
Working fine on 25/11, at least it opens without crashes. I don't have any .mp3 file to test it, tho.
Sent from my XT1095 using Tapatalk

11/25 update fixed Snapchat and Google Camera FC for me (I don't use FB apps but word is they work now too), though it wasn't easy to update. 11/24 seems to have issues with booting to recovery.
Here is a workaround to update to 11/25:
1) Download your favorite recovery.img to your computer
2) Download 11/25 CM update from "About Device" section
3) Reboot to bootloader
4) In terminal on computer, run "fastboot boot recovery.img". This will cause the phone to load the recovery image into RAM and boot from there
5) Navigate to the CM update and flash as usual
6) You're now on 11/25 build and can access recovery regularly
Cheers!

Still cant write in system folder, i can use adb to gain access so adaway can overwrite the host file
any alternative to adaway???

lucasdeeiroz said:
Working fine on 25/11, at least it opens without crashes. I don't have any .mp3 file to test it, tho.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
the fc occurs when you tap artists tab and and then an artist,fc in 25/11 too,is only me?

awacker89 said:
11/25 update fixed Snapchat and Google Camera FC for me (I don't use FB apps but word is they work now too), though it wasn't easy to update. 11/24 seems to have issues with booting to recovery.
Here is a workaround to update to 11/25:
1) Download your favorite recovery.img to your computer
2) Download 11/25 CM update from "About Device" section
3) Reboot to bootloader
4) In terminal on computer, run "fastboot boot recovery.img". This will cause the phone to load the recovery image into RAM and boot from there
5) Navigate to the CM update and flash as usual
6) You're now on 11/25 build and can access recovery regularly
Cheers!
Click to expand...
Click to collapse
You're right. Last update fixed Snapchat, Facebook and Facebook Messenger. Google Camera is still forcing close, tho. I will test Netflix and report back here.
Sent from my XT1095 using Tapatalk

kleytonhunter said:
the fc occurs when you tap artists tab and and then an artist,fc in 25/07 too,is only me?
Click to expand...
Click to collapse
Yeah, I can confirm that. It crashes when you select one artist. But you can always use Play Music instead.
Sent from my XT1095 using Tapatalk

gianboy said:
Still cant write in system folder, i can use adb to gain access so adaway can overwrite the host file
any alternative to adaway???
Click to expand...
Click to collapse
System still in read-only mode. Nothing that we can do for now.
Sent from my XT1095 using Tapatalk

OP updated. Snapchat, Facebook and Facebook Messenger fixed. Music, Netflix and Google Camera still on the issues list.
Sent from my XT1095 using Tapatalk

The linked twrp worked! Thank you!

lucasdeeiroz said:
Known bugs on Official CM13 for Moto X 2014 (victara):
-[FIXED]Official Facebook and Facebook Messenger apps FC;
-Netflix app won't load any video;
-[FIXED]Snapchat app FC;
-SuperSU not working (use CM's root method instead, see post #4);
-Latest Google Camera app crashes on Video Recorder mode (Moto Camera works tho, you can install it via Play Store);
-CM's Music app will FC when you select an artist (use Play Music instead);
-Maybe you have to use the ROM in English language. Some people are reporting FC's on another languages.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I'm having problems with the audio recording of whatapp. Did a clean install of the new cm13 and even then the error persisted. I tested the whatapp downloaded via platform via apk beta and apk mod, all with the same error.

cm13 is not good. so many bug[emoji55]
Sent from my XT1085 using Tapatalk

妹妹你好胸 said:
cm13 is not good. so many bug[emoji55]
Sent from my XT1085 using Tapatalk
Click to expand...
Click to collapse
Relax! Initial nightlies are expected to be buggy. Wait a few weeks for a fairly stable build.

Joiner22 said:
I'm having problems with the audio recording of whatapp. Did a clean install of the new cm13 and even then the error persisted. I tested the whatapp downloaded via platform via apk beta and apk mod, all with the same error.
Click to expand...
Click to collapse
I saw some people complaining about this problem, but honestly WhatsApp audio is OK here for me... I don't know what's different.
Sent from my XT1095 using Tapatalk

twrp backup
hi,i have made a backup with twrp of my stock 6.0 and after flash cm 13 and it seems a little bug yet, iam restored that backup and now my phone is stuck on motorola logo with restarts but it ever stay stuck on moto logo,every time i flash cm13 all works fine,restored 2 times before and no problem,but when i restored today get stuck, someone know how to fix?

kleytonhunter said:
hi,i have made a backup with twrp of my stock 6.0 and after flash cm 13 and it seems a little bug yet, iam restored that backup and now my phone is stuck on motorola logo with restarts but it ever stay stuck on moto logo,every time i flash cm13 all works fine,restored 2 times before and no problem,but when i restored today get stuck, someone know how to fix?
Click to expand...
Click to collapse
Did you wipe system partition? Try it and see if that works.
If you have a problem with your backup, you can flash latest firmware from Motorola (deleting two lines from flashfile.txt), making a downgrade. After that you can upgrade by OTA to 6.0. Note that you have to flash the LATEST firmware, you can't flash the pre-patched stagefright firmware, because with two OTA updates you will get a hard brick.
Step-by-step in Portuguese: http://motox-brasil.blogspot.com.br/2015/11/tutorial-moto-x-all-como-fazer.html?m=1
Or even better, you can flash a clean backup: http://motox-brasil.blogspot.com.br/2015/11/backup-twrp-moto-x2-60-backup-do-twrp.html?m=1
Sent from my XT1095 using Tapatalk

Related

problems

Hey all
I've had my vivid for a while, I'm running CM10 with sultan kernel (http://forum.xda-developers.com/showthread.php?p=39590429). The other day I rebooted my phone and it took longer to boot than usual, it randomly reset itself and I lost everything (luckily I had a backup ). for some reason the kernel had downgraded itself, went from beta 14 to beta 12. I restored it from my backup but then it kept resetting itself, all the while I stayed on beta 12. Now I've decided to start a fresh, reinstalled CM10 to find that its not installing google play, another weird thing is that my kernel wont change, it stays as beta 12 even after following the instructions fully to upgrade. I need the newer kernel because it has some fixes I need. Also I need ideas as to why google play isn't installing. Any help/ideas are appreciated
Thanks in advance
SlugBoy7691 said:
Hey all
I've had my vivid for a while, I'm running CM10 with sultan kernel (http://forum.xda-developers.com/showthread.php?p=39590429). The other day I rebooted my phone and it took longer to boot than usual, it randomly reset itself and I lost everything (luckily I had a backup ). for some reason the kernel had downgraded itself, went from beta 14 to beta 12. I restored it from my backup but then it kept resetting itself, all the while I stayed on beta 12. Now I've decided to start a fresh, reinstalled CM10 to find that its not installing google play, another weird thing is that my kernel wont change, it stays as beta 12 even after following the instructions fully to upgrade. I need the newer kernel because it has some fixes I need. Also I need ideas as to why google play isn't installing. Any help/ideas are appreciated
Thanks in advance
Click to expand...
Click to collapse
The kernel didn't downgrade android1-7 just never updated the info for the kernel. I'm running beta14 as well but is says 12...so your okay there.
On the other issue what recovery are you using?
thanks for the reply
i use TWRP since CWM stopped working randomly and wont flash back
SlugBoy7691 said:
thanks for the reply
i use TWRP since CWM stopped working randomly and wont flash back
Click to expand...
Click to collapse
Which version of TWRP ?
latest i believe
The disappearing apps is because of a problem with sultan kernel... it seems to corrupt the file system if you reboot at a certain time... I have no idea what causes it to corrupt
The play store problem is from you doing a full wipe without installing GAPPS...
Sent from my Vivid 4G using Tapatalk 2
Really? I didn't think CM10 needed gapps. I just tried a standalone install of play store 4.0.26 and it installed, but it just crashes when I try open it
That's cause you need other files from GAPPS for it to work
And the play store MUST be a system app
Sent from my Vivid 4G using Tapatalk 2
ok thanks, will try that
Trust rignfool he knows what he's talking about lol. And yes you do need gapps for cm10. The only problem with cm10 that I have is very poor in call volume. Since I'm speaking of it. @ rignfool do you know a fix for that? (very low in call volume)
Sent from my Vivid 4G using xda app-developers app

Xposed Framework On Stock 5.0.2 L90 D415

Have anyone succesfully got Xposed Framework running on stock 5.0.2 L90 D415??
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
I flashed the zip file, wiped cache, and reboot. My phone booted up but i got com.android.phone force closing. Weather app also force closes. And since com.android.phone force closes you get no signal.
My experience...did the lollipop ota for tmo, didn't really care for it much. Used one click root, added flashify and twrp custom recovery and did a nandroid backup. Installed xposed arm zip and it just stuck on the lg logo for quite a long time. Second attempt i did the wipe after installing xposed and it made it past lg logo to tmo boot and hung up. In my reading, saw something about xposed will not work on stock firmware. But isn't xposed for people that want to mod stock roms? Main thing is...back up before anything. Have already used mine 4 times.
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
If you're going to do it, BACK UP BEFORE YOU INSTALL. I cannot get it to work, reason why? I do not have the logs but if you install liveboot and activate it, then install the zip and reboot, liveboot will show you a command that is supposed to activate but fails and retries. Its essentially a bootloop but without the reboot. It will not allow you to boot without that feature being activated. Do it for yourself but remember to back up all system partitions and restore them. When you reboot after restore, the system will do the whole 'optimizing apps 1 out of 200' thing so don't worry if it takes a while to boot. Will have more on this when I get home to my laptop.
Xblackberryuser said:
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
Click to expand...
Click to collapse
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Warimation said:
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Click to expand...
Click to collapse
Here you go.
Found another one from March and April, but I haven't tried them.
Xblackberryuser said:
Here you go.
Found another one from March and April, but I haven't tried them.
Click to expand...
Click to collapse
I tried the one you suggested and I successfully rebooted. However, Lollipop ran slower and then I opened the alpha apk that came on the official thread. It said alpha 3.0 was installed but not activated. So I just decided to restore to before I installed. Xposed is being worked on and its in its alpha stage. Its bound to have bugs. Since THE D415 already has root, I'm fine to wait for an official version of Xposed that works to come out. Also, Even though I had 2 Gigs of data left on internal, there was a notification pestering me saying there was little to no storage left on my phone. Otherwise, no app crashes.
jesuita said:
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Flashing the ROM again will only wipe/remove xposed.
It's a known fact that lg weather doesnt work on xposed lollipop i also found that file manager didnt work during my period of testing, i don't know if i experienced com.android.phone force closing since I restored from my backup but xposed is definitely not usable on stock lollipop.
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Where can I download the newest version at because all of them up to this point are not stable on my lg 90 415d , I tried v71 and everytime I try to open my gmail Google Play services force closes
Sent from my LG-D415 using XDA Premium 4 mobile app
jbonilla51 said:
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Click to expand...
Click to collapse
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
krchi said:
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
Click to expand...
Click to collapse
There are newer versions of xposed that fix compatibility issues with LG's encrypted apps (weather, etc) since my post, so they should work with the newer versions of xposed. I only recommended version v68 because I never really use LG apps so I went ahead with such an update. Hope this helps!
Xposed for visually impaired users
Hi, everyone!
I'm visually impaired and I've been "adapting" and customizing my stuff (for a better, more comfortable usability) since 1998 (for Win and Mac) and 2010 for mobile devices, with great success.
I could install the Xposed framework to my Galaxy Tab 3 running KK 4.4.2 (Serbian Stock) back in 2012. But I cannot find a way to install it to my LG L90 D410 running Lollipop 5.0.2.
The option for those specific brands and models in based on the need for good cost-benefit ratio pieces of equipment, so that anyone can benefit from my findings, even those running on a low budget.
I'm preparing a podcast and an YouTube channel on accessibility.
All that put, I'd appreciate any input on how to make the Xposed framework to work on the LG L90. Suggestions o modules that can be useful for vision impaired people will be very welcome too.
Thanks in advance for any help I can get.

Install & run Android Marshmallow on the M7 - VanirAOSP ROM - UPDATED 4/24/16

There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.

[ROM] Chinese Marshmallow ROM for ZTE Axon Elite (A2016) international

I was able to install Chinese ZTE Axon Elite (A2015) Marshmallow rom to my international version of Axon Elite (A2016). Wifi, mobile data network and calling works. All Google apps are working too, Chinese rom has google services installed but those are needed to be activated by allowing them run in a background. Only Chinese and English languages available, but system is working in your local language after installing More Locale 2 from Google Play.
This ROM is not rooted, so you need to install Super User in TWRP right after installing this ROM.

Changes:
Added modem files (modem.b00-modem.b22, modem.mdt) from international B06 NON-HLOS.bin.
Minor build.prop changes (e.g. changed English as default language).
Removed stock recovery.
Added Google Play, Google Contact sync, Google Calendar sync, Google Gmail, Google Exchange sync, Google Phone, More Locale 2.
Removed all possible Chinese ZTE bloatware (over 200MB). I had to leave Mi-Assistant so that it can be used for allowing apps running in a background (example Google Play, Super SU).
[*]Added stock Marshmallow boot animation and removed boot sound.
Features:
Latest Google Security patch
MiFavor UI 4.0 with new themes and fonts
Applications Avatar (I have no idea what it is)
Toolbox - including compass, noise test, ruler, protractor, level meter, paintings
Calendar, shows weather for five next days
New Desktop backup and recovery capabilities
Long screenshots
More system Sleep functions
Smoother UI animations
SMS two-finger zoom
New power limits
Enhanced ZTE lock screen
...and some more which might not be useful in other countries than China (please check more details from: http://www.myzte.cn/thread-270646-1-1.html)
Working:
Wifi, mobile network, mobile data, bluetooth.
Fingerprint scanning.
Google Play services + other Google apps are working too (like Calendar, Contacts sync), but must be activated in Mi-Assistant Auto-start manager and allowing permissions in apps. Please see attached images for example.
Bugs and limitations:
NFC doesn't work.
Only Chinese and English languages, but it is possible to use More Locale 2 app (included in ROM) to change locale settings. Then apps (and part of the system) are working on your defined language. On my opinion it works just like in B06. More Locale requires Root access and executing ADB command (app shows the needed command) to change locale.
Download (B15M beta, updated 09.09.2016):
Mega https://mega.nz/#!cRAXTbqQ!UYTEzWb4AH5yZbcI4fK_09QBM5TYgvCCMMl1uTijetE
Based on the tip from @martas.vavra, I removed stock Chinese recovery so TWRP is not deleted after installing this rom.
Working Super user can be downloaded here https://cloud.tapatalk.com/s/57550023717f4/SuperSU_V2.62-3.zip. Thanks again @martas.vavra.
Quick steps:
(optional) Backup all apps by using ZTE own backup/restore app. It's then possible to restore apps after rom installation.
Install TWRP+root by using the method by @acer73: http://forum.xda-developers.com/zte-axon/development/zte-axon-elite-a2016-twrp-root-t3237760
Copy ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 to SD card.
Boot to TWRP recovery.
Do full backup in TWRP.
Do factory reset in TWRP.
Install ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 from SD card in TWRP. NOTE! Status bar is not progressing at all when installation is ongoing! Don't panic. Just wait, it will complete.
Install Super User .zip again.
Reboot. Please be patient, first boot will take minutes to complete.
After first boot is complete, start Mi-Assistant and enable apps (Google Play, Google Contacts, SuperSU... etc) in Auto-run Manager.
Enable app permissions for Calendar, Contacts, Phone, SMS, Storage in Settings -> Apps, App permissions.
Reboot.
(optional) Restore apps by using ZTE own backup/restore app. ZTE has removed Backup/restore app but here's download link for backup/restore app from B12M: https://mega.nz/#!hZQ2HTbb!IvTJu17kjibXGSJBsRUutz0wwPZL0XlruDVAyExqsC8
Note to users: I'm not responsible if you brick your phone, so please be careful!
Thank you for your efforts! Great to hear that there are only minor bugs. :fingers-crossed:
Leaves me thinking about why ZTE does not provide this update by themselves if there are only few things needed to be adjusted in order to make this work...
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
martas.vavra said:
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
Click to expand...
Click to collapse
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
This is great! Thanks a lot
GalaxyFan88 said:
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
Click to expand...
Click to collapse
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Dapalm said:
This is great! Thanks a lot
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Click to expand...
Click to collapse
You can read here. Its not just about the radio partition.
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
suunnittelija said:
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
Click to expand...
Click to collapse
I think that copying that files, modules and apps would be possible, from one to another, won't you? I have no idea of how to doing it, but maybe it is easy for someone experimented in rom's modding.
@suunnittelija how about the batttery life?
Mononitoto said:
how about the batttery life?
Click to expand...
Click to collapse
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
suunnittelija said:
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
Click to expand...
Click to collapse
What would be necessary to do, to port fingerprint scanner etc to this rom?
Mononitoto said:
What would be necessary to do, to port fingerprint scanner etc to this rom?
Click to expand...
Click to collapse
Probably it's nothing to do with fingerprint scanner. I checked logcat file and settings will force close before that. Settings will force close right after trying to enable PIN code lock.
Code:
FATAL EXCEPTION: AsyncTask #3
Process: com.android.settings, PID: 8191
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.NullPointerException: Attempt to read from field 'int com.android.server.LockSettingsStorage$CredentialHash.version' on a null object reference
With cyanogenmod there has been similar issues with some devices and error has been caused by wrong baseband (https://forum.cyanogenmod.org/topic/118507-cant-enable-screen-lock/?page=3), which means that users have not been updating the baseband before updating the latest version of cyanogenmod. This might be the same issue, I used lollipop baseband to get this work.
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
suunnittelija said:
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
Click to expand...
Click to collapse
Continue your great work !
How to restore 5.0.1 ?
kacsa105 said:
How to restore 5.0.1 ?
Click to expand...
Click to collapse
Easiest and the best way is to take full twrp backup first before installing this rom. Then it can be restored in twrp and phone is restored to the state it was before.
If backup is not made, then stock B05 update.zip needs to be installed in recovery (in stock or twrp).
@kacsa105 pointed out that adb root method doesn't work anymore with B10M. I didn't notice it because I installed recovery + supe su in right after I installed B10M in twrp.
If you are now in stock Chinese recovery, then follow these steps to restore stock B05 in stock (Chinese) recovery:
1. download B05 from:
http://download.ztedevice.com/UpLoadFiles/product/643/6549/soft/2016042111364202.zip. Unzip it and find update.zip
2. place update.zip to phone internal SD card
3. shut down your phone
4. reboot to recovery: Press and hold Volume up button then Press and hold Power button. When ZTE logo appears, stop pressing Power button but continue pressing Volume up until it goes to recovery.
5. It should be now in stock Chinese recovery. You need to use volume up/down buttons and move it to the selection where is written something on Chinese but with letters SD (which means your internal SD card). Press Power button to select it.
6. Use vol down to navigate until you see update.zip and choose it with power button. If I remember correctly, you need to confirm Yes (it should be in English if I remember it correctly).
7. After it has been updated, recovery asks something again in Chinese. Don't change the selection, just use power button to select what it proposes, and system will boot.
Just wait until your phone boots back to system. If it keeps crashing, just power it down and reboot again to recovery. Recovery should be in English now. Then clear cache and dalvik (or was it factory reset?) and boot to system again.
Google play crashed, when download big data games. Solution pls
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
hik4ru said:
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
Click to expand...
Click to collapse
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
How to flash recovery in recovery? I have tried to flash it via ADB, but there was stock recovery after reboot. And when I flash supersu zip the system won't boot.
Odesláno z mého ZTE A2016 pomocí Tapatalk
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
What modules are you using with Xposed?
Enviado desde mi ZTE A2016 mediante Tapatalk

[Firmware] Huawei P8 GRA-L09 B393 27/02/17

New firmware with Google Security Patch updated at March:
Changelog is here {only Google security patch update to March}: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v77480/f1/full/changelog.xml
File OTA here: unusable so no link
Full update here: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v77480/f1/full/update.zip
Enjoy
Found with Firmware Finder
I'm happy that at least we get the appropriate google security updates.
Anybody installed this? Is it ok?
Flashed from 390 to 393. Works fine!
hidralazina said:
Anybody installed this? Is it ok?
Click to expand...
Click to collapse
Yes stable
I failed to flash from 390 using the dialer method.
Flashed over B392, no problems so far.
Used dialer method.
Sent from my HUAWEI GRA-L09 using XDA Labs
Last ROMs (B392 and B393) fail when updating using dialer method. But they do update, at 100% it shows an error "update failed", when restarted it does optimization of a system and boots and then in settings it shows the correct version (B393 currently).
Strange
flamelab said:
I'm happy that at least we get the appropriate google security updates.
Click to expand...
Click to collapse
thats the least they can do, minimum of work, still very dissapointed by not getting EMUI 5, by the time i was buying this phone i considered this as a sure thing, but i didnt know what huawei is really about
My phone fails to update using the dialer method. Re-trying now using the power+volup+voldown method.
ITzAndry said:
My phone fails to update using the dialer method. Re-trying now using the power+volup+voldown method.
Click to expand...
Click to collapse
How did it go?
ITzAndry said:
My phone fails to update using the dialer method. Re-trying now using the power+volup+voldown method.
Click to expand...
Click to collapse
not using CM 13 anymore? is it bad? im thinking about give it a try
potworny said:
How did it go?
Click to expand...
Click to collapse
All clear, i just redownloaded the update cuz it was damaged.
00471 said:
not using CM 13 anymore? is it bad? im thinking about give it a try
Click to expand...
Click to collapse
nononono, i was just re-trying the stock system for some experiments. The CM13 is fine, and it works very well, but sometimes third-part apps (downloaded via apk or play store) crash.
nononono, i was just re-trying the stock system for some experiments. The CM13 is fine, and it works very well, but sometimes third-part apps (downloaded via apk or play store) crash.
Click to expand...
Click to collapse
thanks for reply, i will wait till its more stable
ITzAndry said:
The CM13 is fine, and it works very well, but sometimes third-part apps (downloaded via apk or play store) crash.
Click to expand...
Click to collapse
I've tried CM13 ROM but the crashes were very annoying. Opera browser was crashing couple of times per hour, Swype keyboard was crashing when I was typing, a lot of games were crashing at launch, Google Translate was crashing when tried to use camera. I would love to have CM13 instead of Huawei firmware but for now it's unusable.
Topic: successful update from B321 to B393 using dialer method.
Guys,
How do I get stock recovery from this version of the ROM?
On B390 I installed TWRP, replaced the HOSTS file with one that blocks ads, removed some unnecessary system apps and replaced TWRP with stock recovery.
Do you think that using B391 recovery (https://www.androidfilehost.com/?fid=529152257862705190) is a good idea?
I don't want to root the phone because I don't feel it's necessary.
potworny said:
Guys,
How do I get stock recovery from this version of the ROM?
On B390 I installed TWRP, replaced the HOSTS file with one that blocks ads, removed some unnecessary system apps and replaced TWRP with stock recovery.
Do you think that using B391 recovery (https://www.androidfilehost.com/?fid=529152257862705190) is a good idea?
I don't want to root the phone because I don't feel it's necessary.
Click to expand...
Click to collapse
Huawei update extractor thread ok XDA
to me seems to be improved both camera.. especialy front camera, the back looks that he used more agressive smoth procedure
version runs great on my wifes p8. however the background changes in the window of a smart cover is still broken
Works fine
Works fine on my P8
Thanks :good:

Categories

Resources