These are the steps that I took to finally get systemless root and xposed. Android pay works now. I thought I would share this. It took me over 5 days of many many wipes and restores. I will also discuss some of my phone quirks in here. The reason why I am discussing these quirks is to explain that every phone is very very unique and if people do not have enough experience, they will end up with very different results
Standard disclaimer: Not responsible for anything that goes wrong with your phone
I also would consider this to be moderate difficulty, its not really for beginners due to multiple pre reqs and terminology
I would consider this very early beta at best, sometimes xposed does not stick, so far I think I finally figured out how to make it stick with every reboot.
I- My phone:
I have V10_H901_V20J_Stock_Custom_2e-signed , so obviously I had to go through the pain of understanding that thread. If your phone is already on that rom , then you must have TWRP in place by now. That of course is a prerequisite.
II- Visit the following threads, Credit goes to all the developers there, I am merely putting it as a write up.
A- This is the main thread, honestly, didn't love the instructions there, hence why I am doing this.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
you will need to download the following from that thread ( but I put in the links to the right files)
There is no need to place in any specific folder, I usually put every thing on my external SD
1- Magisk: http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get
Place it anywhere you can easily access it.
Edit added 09/11/11: magisk controller app : http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
2- PHH systemless SU: http://forum.xda-developers.com/attachment.php?attachmentid=3847928&stc=1&d=1471642336
PHH super user app to work with systemless root :
https://play.google.com/store/apps/details?id=me.phh.superuser
B: Xposed systemless thread: here is the main thread
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
1- Download Systemless xposed: xposed-v86.5-sdk23-topjohnwu.zip form : http://forum.xda-developers.com/attachment.php?attachmentid=3847909&d=1471640756
2- download the xposed material design app to control xposed:
http://forum.xda-developers.com/devdb/project/dl/?id=19668&task=get
Steps - This is what worked best for me, I have heard numerous times on the v10 stock rom thread that our roms come in with systemless root. I can never get that to work systemless. If you know a better way, feel free to share the knowledge.
1- Back up ! use TWRP, Here is quirk number one from my very special phone: TWRP restores fail if the phone is hot. They do not restore properly. Do what you need to do to keep your phone cool if you need to restore. I have tested this about 5-8 times in the past 3 days. If my phone is pre-cooled ( use your imagination ), it restores 100 % without missing apps or errors. If it gets hot, then I get app crashes, errors, and all sorts of corruption.
2- Uninstall xposed if you have it running on your device - THIS IS A MUST make sure you use the official uninstaller that came with your xposed version
3- unroot your phone. use SuperSU app to unroot your phone: Do restore the system boot when prompted, do NOT restore original recovery, you need twrp obviously.
4- Boot into recovery manually: Now I feel like this is most confusing part about LG phones, and its never really well written:
Power down the phone
hold the volume down
with the volume down being held ( do not let go) , press the power button, until the LG logo appears, as soon as that happens, let go for 1/2 second then press the power button again ( this whole time the volume down button should be pressed ). You will get two prompts of warning, if you are successful, about the device being erased, it will not get erased You will simply just boot into TWRP
5- Flash the following in order , do not queue, TWRP is finicky at best for our phones , never queue
- Magisk from step A - 1
-phh super user A - 2
6- reboot phone. Your phone is now systemless rooted, the root can be turned on/off on demand.
You will find magisk app on your phone, do not start , it will simply crash
you will need to install the PHH super user app from step A- 2 , this is a simple apk from the play store.
then you can mess with magisk if you would like, I will explain it's options later
7- Uninstall whatever xposed controlled app you used to have, install the material design xposed app controller from B-2
8- now that you have root, reboot to recovery, using whatever app you use to simple reboot into recovery (quirk alert: I can never find a way to include reboot to recovery from the power menu, no matter what mods I have)
9- flash systemless xposed from B -1 . wipe dalvik/cache 3 x , wait for your phone for 500 years to boot up
10- you are now systemless. go into the xposed app and check all the modules to re-enable them
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
09/25/16 : update. Xposed now trips safety net. Even if it's systemless. Some reports also say Magisk will trip it. Sorry but this guide is now obsolete.
Great guide works perfect!!!
I'm running this systemless train [powered by magisk] really smooth. I'm running rooted stock MM with no issues at all. I can reboot with G4tweakbox mod, Xposed sticks every time and is very stable.
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
No
johnwayne007 said:
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
Click to expand...
Click to collapse
Not really
Here are the problems we faced with MM onwards
1- LG disabled the flash commands with MM, even though its is an unlocked bootloader. Hence why you have other threads with instructions on how to circumvent the good old fastboot flash commands.
2- TWRP needs compatibility with the v20J update. I am not sure if we have any devs working on that
So we are in an appleisk like situation with the newest update. No dev = no further progress, unless you want to loose root and recovery . You have the wonderful people here at XDA to thank for that, who constantly b**** at developers for that.
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
jmichaels1982 said:
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
You need to power down your phone fully. Then power up . That is my personal experience. and I have tried it over 5 times and now it sticks with every boot.
Click to expand...
Click to collapse
just wondering if you could elaborate on Xposed not "sticking"?
dimm0k said:
just wondering if you could elaborate on Xposed not "sticking"?
Click to expand...
Click to collapse
It will say in the xposed app that xposed is installed but not active.
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
It will say in the xposed app that xposed is installed but not active.
Click to expand...
Click to collapse
Are you using the layers app with hydra installed? Removing it might help you out. Once I did that I had no issues keeping Xposed to stick and may be a bug with v3
This was very well written and easy to follow. Systemless root and xposed are running perfectly! Thank you
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
apologies
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Sorry man , I fixed all the links.
I feel like an idiot....I've been trying this for 2 days and no success. Used KDZ to get to bone stock J build, then used the .tot updrade to get TWRP and rebooted, now I have an unrooted stock rom with twrp. I adb reboot into recovery and successfully flash magisk and then successfully flash phh superuser but after I reboot I don't have root.....Can anyone assist?
EDIT: Nevermind.....apparently I was flashing Magisk v3 and not v6...not sure how that happened. I rebooted into TWRP, flashed magisk v6 and then phh superuser and I now have root.
Thank you for the guide.
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Trying opening the link outside of xda labs app. I loaded the link in Firefox and now it downloads properly
Can some one provide me an explanation of what it means to have a systemless setup and the benefits of that!?
I installed as you instructed and It mostly works great. Thank you. May I ask what settings you use for Viper4Android (External Speakers)? I am not sure on how to get it working. I installed the systemless version you posted. I am also using the same ROM you are. However when I enable Viper4Android, I notice no difference whatsoever in the sound of my external speakers... Just playing an mp3 via Google play music. Any info would be greatly appreciated. Thank you.
Blur
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
nookie1916 said:
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
Click to expand...
Click to collapse
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Actually found out Google updated safenet the other night where it stopped working with xposed installed with magisk. Without xposed everything still passes. Had to use the other method of not using magisk and using suhide and that method still works with everything.
jmichaels1982 said:
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
Click to expand...
Click to collapse
It'll have to be a Nexus 6p, or older because the Pixel phones will supposedly have locked bootloader.
Thanks for the great step-by-step directions!!! Had been reading all of these related threads trying to make sure I knew what order to do everything. Followed the steps as written. Checked when I got root, before installing xposed, and SafetyNet showed green. Installed xposed and rebooted - only issue I had here was when it finished updating apps and got back to my home screen - all of my app shortcuts on all screens were gone, including the bottom line. The widgets I had previously were still there. So it just took a few minutes to re-do all my screens - not that big a deal to get all this done!
But then I had the same problem as nookie1916, SafetyNet and Android Pay would not work now. So I tried turning off the xposed framework and rebooting, and that worked - SafetyNet showed green again and I was able to load my Chase Visa onto Android Pay. Then turned xposed back on and rebooted.
So it's not quite the way I wanted it - but I use xposed features much more than I need Android Pay.
Thanks for your help!!!!!
Related
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Stefan Baumann said:
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Click to expand...
Click to collapse
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rootSU said:
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
Cool. I haven't seen this anywhere
rootSU said:
Cool. I haven't seen this anywhere
Click to expand...
Click to collapse
I think it was in the Q&A thread for Xposed lol
Since nobody knows how to use adb to push
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Stefan Baumann said:
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Click to expand...
Click to collapse
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Lethargy said:
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Click to expand...
Click to collapse
Ok, it seems I did the button pressing the wrong way. After looking at the thread posted by rootSU and especially at this post I was able to do it (I pressed both volume buttons repetitively instead of just one). So, now I was able to boot the Nexus - what next?
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Lethargy said:
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Click to expand...
Click to collapse
Ok, I disabled all of them and it booted now . I saw, that there are a lot of updates for my available (xposed installer, app settings, burnt toast, customshare, gravitybox, holo themer, wanam, xblast, xposed additions and youtube adaway). Should I install those before reactivating the modules?
Up to you
Lethargy said:
Up to you
Click to expand...
Click to collapse
Ok, I updated all the modules, enabled them one by one (with a restart after every one) and now, everything is working again. Thank you very much for your help :good:.
I installed marshmallow yesterday through Odin, using one of the walkthroughs on XDA. I was going from a custom ROM to marshmallow. The OP in the guide I was following said he didn't completely wipe his phone beforehand. I didn't either and everything installed perfectly fine, when I booted up everything seem to be fine. But then 30 seconds passed and I started to receive incessant notifications letting me know that several apps we're not responding and had to close. In total there are about 20 to 25 apps that were not responding or working or opening. I figured out though that it's a simple fix if you have this issue. Just a simple uninstall and reinstall could fix the issue if it's just happening with one app. If this happens to you though and it's like my case where it's a bunch of apps, you can simply just back everything up with titanium backup and simply restore all the apps you backed up... no uninstalling necessary. No issues since then. I don't know if I'm the only one who had this issue but hopefully this can help someone.
Also kind of off topic, does anyone know if Xposed for marshmallow on our phones is available.
I cannot say if this warrant a new thread, should have posted it in the threat you follow and let the users who will be following that guide about what you went through.
Honestly, everyone I know (especially those rooted) typically wipe their phone and more specifically ODIN the latest update before and not just dirty odin / flash it.
In my many ODIN guide you will see, they usually recommend a wipe after odin there is a reason for that, to avoid what you just went through. Permissions get all jacked up, apps FCs, wont start up, phone locks up, yadi...yada....
WIPE
P.S xpose for marshemellow been available eons ago, just look around xda.
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
ariazad said:
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thank you ariazad!
Hi guys. First of all sorry if i'm writing in the wrong section. I have a problem with my Honor 8 (FRD-L09) updated to Nougat. Today i've decided to unlock the bootloader and root it. I managed to unlock the phone via Huawei official unlock bootloader method, then i've pushed the latest twrp (3.1.0-1-frd) by cmd. All was going fine. After that i've probably downloaded an old version of Superuser, the phh SuperUser r275 and installed it. I've downloaded Phh's Supersu application from playstore, installed busybox (by Jrummy) and i was able to use various apps that required supersu just fine. But i faced a lot of problems when trying to uninstall system apps. For example, i wished to uninstall "Maps" with System app remover and it shows me that the app was correctly uninstalled and in fact it disappeared from the list, then i rebooted and the app was still there! Tried again with System app remover with the same app and this time even if the app showed "successfully uninstalled" it was still there. Then i tried Root Essentials, Titanium Backup, Root Explorer, SD Maid but i was unlucky with them all. Always problems and errors. In particular, Root Explorer, after mounted the system for r/w, shows "unable to delete the file". These problems appears with all the system apps. I don't know what's going on, i've never had this problems with my old S2 plus. Hope some of you can help me. What i have to do? Uninstall phh's superuser? If yes how can i do it? Can't find any uninstaller zip around the web. Or i need to install "SuperSU-v2.79-201612051815-EMUI5.0" attached in the TWRP post? Can i overwrite phh's superuser script with this? Is safe? Will it work? I'm very desperate, please help me.
P.S. I basically followed this guide: "http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/" but using the new twrp. Don't ask me why...i can't explain why i did this stupid thing.
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
SolarisSixth said:
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
Click to expand...
Click to collapse
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Giuskiller said:
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Click to expand...
Click to collapse
That is a product of unlocked bootloader and happens on every phone no matter the brand. It can't be removed
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk