Related
This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.
--- reserved ---
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
StupidIdea said:
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
Click to expand...
Click to collapse
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Chainfire said:
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Click to expand...
Click to collapse
No pressure. Its up to you if you decide to publish it before L release or not but I will be glad to test it on L and report if functions that I use in my apps work with it. As for xposed in theory these 5 points rovo89 posted should work with "permissive" but I guess he will verify it himself.
Of topic: I understand its beyond su binary but did you even thought about adding an option to start activity in system or root process? Benefits are simpler interaction with system services and improved service life (faster restarts). Let me know if question is not clear.
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
cioce said:
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
Click to expand...
Click to collapse
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Have you tried completely removing the com.sec.knox.seandroid package from your device?
MasterMind33 said:
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
Click to expand...
Click to collapse
The reason device default theme is not selected by default is because a lot of OEMs have some godawful themes set by default that everybody would nag me about ...
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
MikeRL100 said:
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
Click to expand...
Click to collapse
#realworldproblems
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Chainfire said:
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Click to expand...
Click to collapse
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Chainfire said:
Have you tried completely removing the com.sec.knox.seandroid package from your device?
Click to expand...
Click to collapse
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
cioce said:
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Click to expand...
Click to collapse
I'm not talking about not having root at all. The problem (as I understand it) is caused by having any packages at all in a "disabled" state. This may ultimately cause a crash which triggers a reboot.
At the same time, keeping that package enabled in combination with root, will break various root commands, which you may not even notice (root apps will just appear to randomly fail and be unreliable) which in turn is also known to cause reboots.
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
Click to expand...
Click to collapse
Just because you haven't noticed the issue doesn't mean it isn't there. As for using it, having root prevents KNOX from working anyway.
...
The point is, solving this problem is not as easy as making that popup optional.
dhampire said:
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Click to expand...
Click to collapse
Please clarify what happens in the following circumstances:
- in-app binary update: normal, and reboot
Keeps saying binary needs updating? Or also results in bootloop?
- in-app binary update: TWRP/CWM
Bootloop?
- latest flashable ZIP with TWRP/CWM
Also bootloop?
It's strange if they don't all result in bootloops...
I know testing is very annoying for you because you need to reflash your system every failed test, but if you want to help solve this problem it's going to require some work.
First test:
- If you have SuperSU 1.94 installed, use the "full unroot" option from settings to remove it.
- Reboot into CWM/TWRP
- Install the latest BETA ZIP but do not reboot
- Adb shell into the device
- "mount /system"
- "ls -l /system/xbin/*su*", post the output here
- "ls -lZ /system/xbin/*su*", post the output here
- Remove /system/app/Superuser.apk
- Reboot into Android
- See if there is a bootloop
Sorry for my poor english. not bootloop. never bootloop. but su binary update loop -> need su binary update again on every boot after update su binary....continue...keep saying need update.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
If 1.9.4, there are no problem like that. but only twrp use su binaly update. normal update makes unroot.
dhampire said:
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
Click to expand...
Click to collapse
Not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
dhampire said:
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
Click to expand...
Click to collapse
Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
...
Please:
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Frank
Frank Westlake said:
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Click to expand...
Click to collapse
No it was not a busybox issue, it was an odd bug somewhere in the binary
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
dhampire said:
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
Click to expand...
Click to collapse
Please confirm the app actually says 2.06
This logcat does not list the output I expect. Did you open SuperSU again after rebooting?
How did you make the logcat? "adb logcat > logcat.txt" ?
Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on most zenfone series.
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v78 arm64.
Xposed
Work perfect! Thanks!!!
Perfect work. Thanks
rajlko said:
Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on ZenFone 2 2.20.40.13x and ZenFone Selfie 1.13. 40.661
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v76 arm64.
Click to expand...
Click to collapse
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
post updated.
Works great !
edit1
Snapprefs works now
roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
sometime pop up for root rights delay due to some mismatch, like you are using patched firmware or boot image of any other system.
Pop window for root right will works well if you have original kernel installed in your phone.
e.g. if you have ze551kl & you are using boot image of ze550kl for root your phone, then you will have this issue.
In patched firmware you may face this issue due to same issue.
Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk
yvg107x said:
Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
Not at all,
it happens some time.
sometime you need to open super user & after that window popup for root right, it happens due to su also.
dose it working with new version .763
BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
Yes
roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
I had the same issue.. But i fixed it by going to auto start manager... in pre-loaded apps... And switching 'Super Su'option to 'on'...
I think as the app didnt had the the permission to auto start... Prompt only comes only when we go tp app manually.... Anywayzz it worked for me...
BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
yes.
flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl
not working?
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work
thefallenghost said:
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work
Click to expand...
Click to collapse
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.
---------------------------------------
rajlko said:
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.
Click to expand...
Click to collapse
Ok. When you say I have the apk in my phone, where exactly is it?! I cannot find it... Edit: Nevermind, I had forgotten to run the installer (faceapalm). Sorry...
hi
I can't reboot from Xposed Installer
When I try and reboot through the Xposed Framework I get the following error message everytime:
tmp-mksh: <stdin>[5]: /data/data/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed. Please use the device's normal reboot function.
I had busybox installer.
Not sure what else I'm doing wrong?
pedrazadixon said:
flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl
Click to expand...
Click to collapse
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!
ericpeacock79 said:
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!
Click to expand...
Click to collapse
Last version v85. Work fine.
Only flash the lasted zip.
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.
Root Issue Reporting - "Could not access the package manager.Is the system running?"
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
kevinkoo said:
Hi All, not sure whether I should request help here.. This is to report the root issue, I followed Z5 Rooting method here and use that rootkernel tool to modify and generate my Boot.img for X Performance F8132, then use Flashtool under fastboot mode to inject this modified new kernal into Original stock ROM - F8132_35.0.A.1.238_HK.tft, after rebooting, I got Rooted phone with DRM well maintained.
Everything is perfect working of Root, Greenify/Busybox... Until I found issue with My Android Tools Pro, though I've authorized it in SuperSU, My Android Tools Pro still advised error msg like Can't obtain Root access. I activated SuperSU logging and found it advised "Could not access the package manager.Is the system running?" for this App. I contacted with My Android Tools Pro developer and this issue seems should never occur in real phone as it's a common error under Development environment. So now it seems like SuperSU issue with Incomplete Root after all these investigations..
I'm looking for help to resolve this issue and if it's posted in wrong place, plz don't be hesitated to let me know and I would move the post to appropriate forum, thanks!!
Click to expand...
Click to collapse
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
bkk99213 said:
Maybe this issue.
http://www.mobile01.com/topicdetail.php?f=569&t=4861581#60965299
The New SuperSU folder have different locale.
If the app isn't update, they not work.
Click to expand...
Click to collapse
Thanks man! I just resolved this issue, actually it's quite easy.. I just unchecked the option "Mount namespace seperation" in SuperSU, then everything works fine now!
Hello,
I'm using MIUI 8 on my phone, its based on marshmallow 6.0.1. I rooted my device using supersu stable 2.78 as systemless mode. The problem is all need-root apps take long time to call supersu at first time it launched. Sometimes need-root app crash if it does not get superuser access for long time. The culprit is on systemless supersu, Superuser.apk installed inside /data partition instead of /system so it won't load on system start. Although i already add SuperSU in startup list, but it was not much help. I did not get this issue on CM13 based rom. Temporary solution is I need to open SuperSU first before open need-root apps for first time.
How to get rid from this issue?
Cc: @Chainfire
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
herecomesmaggi said:
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
Click to expand...
Click to collapse
Yes. Use phh superuser + magisk latest version. :good:
actually this is not the right answer, wrong thread
Hi
I'm sorry for bumping old thread, I've same issue with very same ROM, MIUI 8 8.1.6 run on mi4W device, magisk 13.3
how I managed to solve this is somewhat ridiculously simple yet make me wandering over the internet for about 4 hours in 2AM,
I forgot to activate the "install from unknown source". after that everything run like magic.
FYI: I've done everything via adb shell via TWRP before the "what if" idea come to my head
Click to expand...
Click to collapse