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

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

Related

[SCRIPT] Debloater for KitKat, JB & ICS

I no longer have this phone!
---
** Debloater for KitKat **
I decided to create a Debloater script for those that want a clean system.
I've used bits from NoMoto - Stock ROM Debloat Scripts (Moto G) by lost101
As with my previous debloater for JB, I've kept the stock launcher (and circle widget + weather).
Steps:
Prepare/flash your preferred KitKat Stock ROM
Flash + Boot into latest TWRP recovery
Flash Moto Razr i XT890 KitKat Debloater - v0.1.zip (attached below)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you should end up with after rebooting:
Have fun!
I no longer have this phone!
---
** Debloater for JB & ICS Stock ROMs **
This debloater was created using scripts from arman68's infiniROM Debloater v2 and bits from Motorola launcher remover v2.
I've also used a few bits & bobs from Razri-Cleaner v0.7, by GalaxyUser.
Steps:
Prepare your preferred JB Stock ROM to flash using RSD Lite (See here and here)
Boot into fastboot and flash custom recovery - I use the latest TWRP
Make a backup of the untouched stock ROM (so you don't have to keep using RSD Lite)
Flash Razr i [XT890] - Stock Lite 4.1.2.zip (attached in first post)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you will end up with after rebooting:
Enjoy. :good:
~
Note:
This works with Omar's ROM. :good:
This will also work for ICS. If you're using the Xposed Framework, you will get a Segmentation Fault upon installing the framework - You will need this.
~
I decided it would be best to keep the stock launcher (and circle widget + weather).
They can be disabled if you're using another launcher. If you disable gallery, you will need to install an alternative.
The following are safe to freeze/disable:
thanks buddy,what browser do you suggest?chrome is really laggy...
Try Dolphin Browser.
hi ! can i use it on an "used" ROM? i dont want to deleite muy files
Script in Kit Kat
Thankx ! :good:
it works in my Kit Kat , all appz working...
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Azurael said:
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Click to expand...
Click to collapse
I'm in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
aben.dc said:
Im in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
Click to expand...
Click to collapse
Had it last with mine too. Clear the cache of Google services. Of try to format cache in recovery.
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
aben.dc said:
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
Click to expand...
Click to collapse
hmm, strange.
Non off the stuff the script deletes is from google play services. So sry, i dunno then
Hi,
I am (was) a beta tester for the KitKat update release. During my test I also tried your KK debloater, I'm a big supporter of debloated roms.
I was on the last KK beta (before final) when I applied the debloater zip: all it was ok (super fast phone!), but when final OTA came out, the debloated KK rom did not receive any update. I wait till today and it is clear that the update will never come. I reinstalled the last Kk beta without debloating and the update came immediately.
I'have done more times the test and I can confirm that the KK debloater inhibits the Motorola updates.
OK, now final KK has been released...but if Moto decided to release another update (like small bugfix), with a debloated KK rom you do not never know the update is ready. The problem is not the installation (it is clear that is better to apply the update on a stock rom), the problem is that you do not receive any notification that tell you a new update is ready.
Do you have any idea how to fix the debloater script in order to be able to still receive system update notification?

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.

Xposed/TWRP issues.

I am having an issue installing xposed-v87-sdk23-arm.zip with the recent dailies of CM 13. It seems to happen no matter the CM daily or version of Xposed(v85/v86/v87). All it does is get stuck during boot and causes the battery to heat to ridiculous levels. I end up having to reboot into recovery and flash the Xposed uninstaller and this allows the phone to boot.
I'm not sure if this issue is Xposed based or TWRP based as when I install SuperSu and attempt to update the binary using TWRP I get the same thing, stuck during boot and hi-temp battery. In this case I reflash the last daily and this fixes it.
I have tried just about every variation of installing/wiping dalvik/cache(or not) and rebooting I can think of but always the same results.
Any further information or directions to look in would be appreciated.
Sent from my DROID Turbo using XDA-Developers mobile app
You read this that I posted in the CM13 thread, right?
http://forum.xda-developers.com/showpost.php?p=69637739&postcount=223
ChazzMatt said:
FYI for anyone running Xposed modules:
http://forum.xda-developers.com/showpost.php?p=69636994&postcount=875
Click to expand...
Click to collapse
CM13 made security changes which cause bootloops with xposed. Xposed V87 is supposed to fix that. You definitely do NOT want v85/v86.
At this point have you uninstall xposed framework entirely (using the uninstaller file), and booted in CM13 successfully? Only after doing that would I then attempt to re-install xposed (v.87, or newer for future readers) and any modules.
You mention TWRP. Not sure how that would be involved, but are you on the newest version?
twrp-3.0.2-0-Mod_04-quark.img
https://www.androidfilehost.com/?fid=529141701856462150
I'm on Resurrection Remix 6.x for all Quark which is based on CM13 (Marshmallow). I am using xposed v87 with three different modules on that ROM. If you can't get CM13 running successfully, perhaps switch to RR 6.x as a test -- even temporarily? You have TWRP, so you can make a backup...
(When I switch to a new ROM, I let Google Play restore my apps. Then I use Titanium Backup to restore data only to user apps that need it (Nova launcher, email apps, etc), but not to restore any system apps. It's relatively painless, just takes a little time. Titanium Backup remembers all the configurations, passwords -- and you are not switch OS versions, you would still be on Marshmallow, just a different ROM.)
It's possible it's something else besides the November security patches. How long have you had this problem?
Thanks for the reply ChazzMatt, I had not seen that, thanks for sharing.
As I said, I have tried most any uninstall and reinstall combo possible, including completely uninstalling using the uninstaller.zip and reinstalling as normal. Same issue.
I bring up TWRP because I have seen previous issues with it, such as not being able to decrypt partitions even with the correct password. I was not sure if this was another such bug in TWRP.
I have been having this issue since November, so it could very well be something related to the security update you mentioned.
Sent from my DROID Turbo using XDA-Developers mobile app

Stock [ROM] debloated and Pre-root stock MM MOB31E [Sept16]

Nothing is more stable than Stock ROM with Stock kernel. so I've debloated stock ROM (Sept 2016 Updates) and added SuperSu to it. Result is stable and faster 295mb ROM
Changes made to MOB31E:
1. Removed Google Apps; for more space and less RAM usage.
2. @Chainfire's SuperSu added; No need to root; just flash the ROM.
3. Added Amaze file manager; Preloaded with root browser. Thanks to https://github.com/arpitkh96/AmazeFileManager
4. Added android browser (2mb); works like charm
5. Added E-mail app replacing G-mail; Gmail still works.
6. Replaced prebuilt keyboard app with another; No need to download language after fresh install.
see Screenshots attached;
Thanks to @Ali_Hasan, Pakistan for guidance ! :good:
Thanks to https://plus.google.com/+JosephGodslave for Stock ROM Zips.
Hope this will be useful
Link for Download:
https://drive.google.com/file/d/0BzM_54MLRSxkdDM3RHg1cGFNcUk/view?usp=sharing
Wew, Nice. :good:
Old debloated thread did not had September, thanks a lot (with thanks pressed too)
hp5942 said:
Old debloated thread did not had September, thanks a lot (with thanks pressed too)
Click to expand...
Click to collapse
I'm glad you liked it.
this rom is sprout 4 or sprout 8 ??
i flashing the rom, but error popup always appear in setup wizard. how to resorve it?
You replaced the default keyboard with what keyboard?
Sent from my Micromax AQ4501 using XDA-Developers Legacy app
svckid said:
this rom is sprout 4 or sprout 8 ??
i flashing the rom, but error popup always appear in setup wizard. how to resorve it?
Click to expand...
Click to collapse
Which language do you use ? I think it's because I've deleted prebuilt Korean and hindi keyboard apps. I'll try to fix this. :good:
I replaced Google keyboard with Google keyboard. Different version. Old app needed to download language pack every time after reset or fresh install.:laugh:
I tried your rom, it's clean and faster, thank you. But though you say supersu is included, still it says not rooted (supersu launcher is not present). I had to install supersu zip from the recovery. It worked
A stock rom without google play & google apps (Including google launcher, use CM launcher instead) and other apps or with pico gapps without any apps would be more leaner and faster, Let the user install the apps from the play store. I would appreciate if you try to make a barebone version with the above requirements
thank you
DNA_Uncut said:
I tried your rom, it's clean and faster, thank you. But though you say supersu is included, still it says not rooted (supersu launcher is not present). I had to install supersu zip from the recovery. It worked
A stock rom without google play & google apps (Including google launcher, use CM launcher instead) and other apps or with pico gapps without any apps would be more leaner and faster, Let the user install the apps from the play store. I would appreciate if you try to make a barebone version with the above requirements
thank you
Click to expand...
Click to collapse
Very nice of you to reply. Good suggestions. I would like to work on that. Currently caught up in preparation on exams. Very tight schedule.
How's the battery life in this rom?
kushal9968 said:
How's the battery life in this rom?
Click to expand...
Click to collapse
Haven't tried it yet, but it's safe to assume that this rom as same as stock rom, Cuz he removed the bloatware and its pre-rooted.
Flash a custom kernel and tweak it
sachin n said:
Haven't tried it yet, but it's safe to assume that this rom as same as stock rom, Cuz he removed the bloatware and its pre-rooted.
Flash a custom kernel and tweak it
Click to expand...
Click to collapse
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
kushal9968 said:
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
Click to expand...
Click to collapse
Working fine with others and me.
kushal9968 said:
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
Click to expand...
Click to collapse
Eww.
Just turn off your device and enter into recovery mode, wipe data / system /cache /dalvik cache except SD card & flash a rom.
That's the step to get rid off bootloop.
Or only wipe dalvik / Cache and try booting your device, if it's boots then you're good.
after I plug stock rom debloated why internal memory and sd card is unreadable please help me
rom not installing on spice dream uno ..stuck on installing in recovery
Hi
can you add galery apps in this debloated stock rom?
btw nice rom. thanks
Good try to present here this debloated rom, earlier i used almost all roms after then i was on snapshot for two months...but after flashing this i must say ..very smooth..
Just checked download link... So this won't work for sprout8?

[ROM] AOSP 8.1.0 for Sailfish

I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
This is my first ROM and there could be issues I'm not aware of.
Not Working:
Dialer keeps crashing when making or recieving phone calls
Working:
Camera and Flash
Speaker
Fingerprint sensor
LTE
Wi-Fi
Bluetooth
Auto brightness
If you encounter any other issues, please tell me and we can try to resolve them.
Requirements:
Unlocked bootloader
Newest fastboot installed and set up correctly
Stock 8.1.0 should be installed prior to flashing this
This will delete all your data, make backups of everything
Download:
https://drive.google.com/open?id=1vQRNRpSYQP2BrlCpzIpQpQNQrmlBYvTb
Installation:
Reboot your phone into bootloader
Open a terminal where the AOSP-sailfish-v1.zip is located
fastboot -w update AOSP-sailfish-v1.zip
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
What I want to figure out now is why the dialer crashes when making calls and also how to make this TWRP flashable.
I also plan to update the ROM every month as new security patches become available, just like on the stock ROM.
If anyone wants to replicate the build, I just used the main 8.1.0 repo and the 8.1.0 driver images:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-8.1.0_r1 --depth=0
https://developers.google.com/android/drivers#sailfishopm1.171019.011
Any testing and help would be greatly appreciated.
Thanks.
Great effort! Gonna try and flash it and then possibly help you debug the dialer problem.
I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?
computercarl said:
I really want to flash this, but I cant be w/o a functional dialer. Can you try disabling the stock dialer and sideloading the dialer from the play store?
Click to expand...
Click to collapse
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.
HeavyHDx said:
There's no Google apps available for 8.1 as far as I know, so no play store. I installed Dialer2 from F-Droid but it seems like third party apps can't replace the actual calling interface that pops up when you make or receive a call.
And I wouldn't install this on a device that you plan on relying on just yet. Wait a few days until the issues are fixed. As far as I can tell from my use these past couple hours, the only major issue is the dialer.
Click to expand...
Click to collapse
try https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-14-0-176716531-release/ ? Sure it's not optimal, but, might get a functional dialer for the time being, until the real issue can be resolved.
It needs bunch of dependencies which cannot be installed this way. Eg Dialer framework
It appears though if this https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412
works better. You do get few crashes, but only once, the second time you try same thing, it works.
Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.
just wondering, why would I want to use this over stock?
jmiller3342 said:
just wondering, why would I want to use this over stock?
Click to expand...
Click to collapse
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.
pavanmaverick said:
Couple of questions:
1. When you say this will delete all data, do you mean that internal storage will also be wiped?
2. Is it rootable? And if so, any idea whether SuperSU or Magisk is needed?
Thanks.
Click to expand...
Click to collapse
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
HeavyHDx said:
I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Not sure which version you tested, but https://forum.xda-developers.com/pi...-12-5-2017-t3715120/post74749046#post74749046 talks about what ver seems to work on 8.1 stock.
HeavyHDx said:
1. Yes this will wipe everything. Back up all files that you want to keep.
2. I've tried SuperSU which fails at patching sepolicy and Magisk which results in a bootloop.
Click to expand...
Click to collapse
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?
pavanmaverick said:
Ah, thanks for the update. Do you think it'll be okay if I use TWRP to wipe Cache, Data and System, and then install this ROM, but without the "-w" option? The internal storage shouldn't affect the ROM, right?
Click to expand...
Click to collapse
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)
Any plans of a Marlin release?
HeavyHDx said:
Yeah should work just fine. Just delete the userdata.img from the zip (there's basically nothing in there anyway)
Click to expand...
Click to collapse
All right! Gonna try it out over the weekend. Will report back...
AlexBrookes said:
Any plans of a Marlin release?
Click to expand...
Click to collapse
I can build and upload it real quick, but I wouldn't be able to test anything.
HeavyHDx said:
I can build and upload it real quick, but I wouldn't be able to test anything.
Click to expand...
Click to collapse
I'd be willing to test it. Thanks!
computercarl said:
No additional services running, no gapps prerolled in, bare minimum. Think of this as LineageOS 15.
My plans are to run it, install the smallest gapps I can to get gmail and calendar working, install Elemental X and Magisk to hide unlocked bootloader.
Fast and Lean.
Click to expand...
Click to collapse
oh cool . thanks brah
Have you guys tried going to the default apps section and setting Phone as the default dialer? Fixed it for a few other ROMs i've tried that ran AOSP bases for other devices, might be applicable here.
EDIT: No-go, wierd.
HeavyHDx said:
I successfully built 8.1.0 AOSP from source for Pixel (Sailfish).
I recommend installing F-Droid as gapps for 8.1 aren't available yet.
Thanks.
Click to expand...
Click to collapse
Gapps are kicking around now...
Check 'em from here ( https://forum.xda-developers.com/pi...os-15-1-pixel-xl-marlin-t3725985/post74976717 )

Categories

Resources